Wlm modify a initial Vpar configuration ......

[gigiz]

We have a npar with 7 vpars.
Cpu configuration on these vpars is not omegeneous(4 cpu bound and 1 unbound on first vpar and 2 cpu bound and 1 unbound on remaining vpars). when we start wlm, cpu are rebalanced between vpars apparently without a reason (no failing slo, no priority, no load on vpars).Our wlm configuration is about slo Other with goal usage _cpu and different priorities on vpars.
Questions:
1) Is it correct that WLM, at the start, rebalances cpu vpar configurations? And if this is correct, what is the criteria ?
2)Is it possible force the initial wlm vpar configuration to a desired vpar configuration,
and there is a documentation about this?

[Robert Bennett_3]

I'm in the learning mode on this - but here are some URLs that have been helpful -
Good luck

http://docs.hp.com/en/B8844-90006/B8844-90006.pdf
http://docs.hp.com/en/B8733-90011/B8733-90011.pdf
http://www.hp.com/go/wlm
http://www.hp.com/go/prm

[D Block 2]

check out the link:
http://www.hp.com/products1/unix/operating/docs/vpars.resizing.with.wlm.pdf

you can activate a config file, to move CPUs (unbound) between vPars.

[Bennie Lau]

hi:

Very hard to answer your question with sending us your WLM configuration?

1) Can you define when do you mean by at the start? After reboot or just wlmd -a wlm configuration file or what.

By default, if you have configured it to auto start WLM, the various SLO will be in affect, but with NO CPU usage unless all your apps bounded by the various SLOs are also started.

2)
You can play with your vparmodify command, but isn't it defeating your sole purpose of using WLM to do it for you.

[gigiz]

ok