WLM with Serviceguard and TiCAP

[Lana Klosterman]

WLM has been setup in the active/passive mode to only turn on additional CPU's on the passive node using the fixed allocation policy. All of that is working fine. What is not working is seeing the additional CPU's active on that passive node in glance. Glance only shows CPU 100% when it should be CPU 200% because WLM added a second CPU. Any ideas why glance is miss reporting?

[Duncan Edmonstone]

Not at a system right now, but if I recall correctly, 'glance' always stays at 100% regardless of the number of CPUs - isn't it 'top' that changes to 200%, 300% etc as more CPUs are in a system...

Or maybe I'm just getting forgetful.

Duncan

[Lana Klosterman]

Not true. Before introducing WLM into the mix we've been doing benchmark tests to determine how many CPU's the customer should out right purchase and than keep the rest as TiCAP and during those tests when we issued the icapmodify to turn on CPU's glance reflected the changes almost immediatley.

[Duncan Edmonstone · Accepted solution]

Lana,

So I'm at a system with iCAP now and if I run glance, the bar for CPU always stays at 100%. However if I run 'glance -c' and look at the number of active CPUs at the bottom of the page, this changes as WLM (or in my case gWLM) moves CPUs around.

Please see attached image...

HTH

[Mark Coffey_2]

Both WLM and gWLM use the icapmodify command to activate/deactive TiCAP processors, so any updates seen in Glance as a result of running an icapmodify should show up with WLM/gWLM as well.

[Lana Klosterman]

Duncan & Mark - good tip on where to look in glance to see the WLM CPU's using glance -c. Problem is my glance -c still reports only 1 CPU. This is 11.23 on an rx8640????