HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: WLM not resizing vpars on the fly problem
Operating System - HP-UX
1833762
Members
2565
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2003 04:10 AM
10-23-2003 04:10 AM
WLM not resizing vpars on the fly problem
I am trying to setup WLM on a box which contains 2 vpars, each vpar has 1 cpu bound with a total of 2 cpu'd unbound/floating. I can manually move them between vpars but after configuring WLM I can not get WLM to automatically move the cpus as needed.
In the msglog I have the following error after it says its ready to receive data:
No data received from partition par1
No data received from partition par2
My wlmpard config file is as follows:
vpar {
partitions = par1 : host1, par2 : host2;
interval = 5;
weight = par1: 1;
port = 3701;
wlmpardstats_size_limit = 3;
}
I appreicate any help someone with experince in this can provide. Thanks in advance..
Eric
In the msglog I have the following error after it says its ready to receive data:
No data received from partition par1
No data received from partition par2
My wlmpard config file is as follows:
vpar {
partitions = par1 : host1, par2 : host2;
interval = 5;
weight = par1: 1;
port = 3701;
wlmpardstats_size_limit = 3;
}
I appreicate any help someone with experince in this can provide. Thanks in advance..
Eric
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2003 09:53 AM
11-19-2003 09:53 AM
Re: WLM not resizing vpars on the fly problem
Hi, Eric
I know the WLM team helped you directly.
I wanted to post a message here as well to let other readers know what was happening.
As you know, when configuring WLM to manage partitions, there are WLM configuration files on each partition. By default, the WLM instance on each partition works on a 60-second interval. In one partition, you also need a WLM global arbiter (wlmpard) configuration file.
If the interval for wlmpard is smaller than the intervals for the WLM instances, the msglog will be filled with entries of the form you saw:
No data received from partition par1
So, it is recommended that the wlmpard's configuration file set its interval to a value greater than any of the intervals used by the WLM instances.
The example WLM configurations available from http://www.hp.com/go/wlm have been updated to stress this point. Also, the intervals have been shortened so that CPU movement occurs more quickly.
Scott
I know the WLM team helped you directly.
I wanted to post a message here as well to let other readers know what was happening.
As you know, when configuring WLM to manage partitions, there are WLM configuration files on each partition. By default, the WLM instance on each partition works on a 60-second interval. In one partition, you also need a WLM global arbiter (wlmpard) configuration file.
If the interval for wlmpard is smaller than the intervals for the WLM instances, the msglog will be filled with entries of the form you saw:
No data received from partition par1
So, it is recommended that the wlmpard's configuration file set its interval to a value greater than any of the intervals used by the WLM instances.
The example WLM configurations available from http://www.hp.com/go/wlm have been updated to stress this point. Also, the intervals have been shortened so that CPU movement occurs more quickly.
Scott
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP