Using WLM to migrate CPU's within Vpars.

[Mark Nierth]

I've got 2 Superdomes, each with multiple Npars and Vpars and I'm using WLM to migrate CPU's within the vpars. SD #1 is HP 11.i with WLM A.02.02, Vpar 1.2 and PRM C.02.02. CPU migration works fine on this dome. SD #2 is HP 11i with WLM A.03.00.01, Vpar 1.3 and PRM C.03.00.
Based on the release notes of WLM A.03.00.01 and the vpar examples in /opt/wlm/examples/wlmconf, I changed my WLMPARD and WLMD files as suggested.
After starting WLMPARD and WLMD on the primary host and WLMD on the other servers, I see no migration and wlminfo par returns nothing. Also, a message in msglog says WLM thinks I'm trying to use ICOD. Anyone have any experience with resizing vpars using WLM A.03.00.01 ?

[Steven E. Protter]

Shalom,

Wait, you had a working system and could move cpu's around with WLM.

Then you changed your configuration to meet some text book or pdf doc's specifications and now it doesn't work?

Do you see whats wrong with this picture?

Change the configuration back or explain why it had to change because from here it looks like something was working and you broke it.

I did that today and got 3 hours of unneeded overtime for my trouble.

SEP

[Mark Nierth]

Hey Steven,

SD#1 with WLM A 02.02 works fine and CPU's are being migrated.
SD#2 with WLM A.03.00.01 doesn't migrate. The release notes, etc, say the partition statements in the wlmpar file are obsolete and well as the prm statement in the WLMD file is no longer needed. I used the exact file statements that are in /opt/wlm/examples/wlmconf/vpar** and no migration. When I issue the wlminfo par command, it returns nothing. I just opened a ticket with HP on this.

[Mark Coffey_2]

Hi Mark,
Were there any messages in the msglog indicating that the wlmd/wlmparc processes were not communicating with the wlmpard process? WLM A.03.00.01 includes secure communications between the wlmd/wlmparc processes on the partitions and the wlmpard processes.

Note that when the prm statements are not used in the wlmd configuration file, the entire partition is considered a single workload.

Regarding iCOD, WLM A.03.00.01 will discover the iCOD resources available on the system by running the iCOD commands. Messages about this will be displayed in the msglog. WLM A.03.00.01 discovers the iCOD resources because it is capable of migrating CPU resources across nPars and vPars at the same time.

[Mark Nierth]

Hey Mark,
The only error messages I see in the msglog from the primary host is the warning messages about ICOD. On SD#1 that's running WLM A.02.02, I see messages like "connection established and connection accepted" to the other servers, but none of these messages are seen on SD#2.
Right now I'm not concerned about setting up additional SLO's, so you're right, I'm treating the entire vpar as a single workload.
I saw a similiar posting on the forum about WLM A.03.00.01 and his fix was to upgrade to WLM A.03.02.
The WLM guys at HP are still researching.

[Mark Nierth]

Hey guys,
I'm not sure what the problem is with WLM A.03.00.01, but once I upgraded to A.03.02, everything is working fine and CPU's are being migrated between vpars.

I'll give Steven and Mark points just for responding..