After upgrade of HP-UX 11.23 client for RSP, Capacity Advisor collection broke.

[Robert Cook_6]

I have an existing 11.23 CMS(C.05.01) running gWLM (A.03.00.01)and Capacity Advisor (A.03.00.00). I have installed a new windows CMS in prep for upgrade to gWLM and Capacity Advisor and also Remote Support Pack. After upgrading an 11.23 client for RSP the unix cms cannot collect Capacity Advisor data. I get error:
grrapi20.na.steelcase.net: System information is not available from the WBEM provider. Collection from this system cannot proceed until this situation is corrected.
Unable to determine if the HPVM WBEM provider is installed.

As I understand it CA gets data from the client via UtilProvider but I can't find info the newest version (A.01.08.01.01)which is loaded on the problem client.

Any suggestions on what the problem might be?

Thanks,

Bob

[Steven E. Protter]

Shalom,

swlist -l product | grep -i wbem

netstat -an | grep ":80 "

Replace the 80 with the port number wbem is supposedly ruinning on.

It sound a bit like a bug, you might want to sremove capacity advisor and re-install it.

SEP

[Robert Cook_6]

Do you want this info from the client or the cms or both?

[Olivier Masse]

From what I understand, capacity advisor depends on a WBEM module that isn't available anymore. You can try running "cimprovider -ls" on the HP-UX system, and confirm that all the providers are running. If one is stopped, start it (see the cimprovider man page for instructions). If the one used by capacity advisor is not there at all, it will need to be reinstalled; you'll probably have to open a call for this.

[Wade Satterfield_2 · Accepted solution]

Hi Bob,

CapAd collects data from several providers. The utilization data comes from the UtilProvider, but other configuration data comes from the SystemInformation provider, the OperatingSystem provider, and the HPVM provider.

CapAd is not able to connect with at least one of these providers.

This could be caused by a provider being uninstalled from the managed node. I believe the SystemInformation provider, and the OperatingSystem provider are still shipped with WBEM Services. The HPVM provider is only needed on HPVM Hosts and guests. You could check that all of these are still there.

It is also possible that the WBEM authorizations have changed. Where you used to be able to talk to these providers as any user, you might be able to use them only when logging into WBEM as root. The permissions for WBEM can be set by running the cimauth command on the managed system.

A pair of commands like "cimauth -a -u wbem -n root/cimv2/hpvm/pending -R -W" and "cimauth -a -u wbem -n root/cimv2/hpvm" might be needed to allow the user "wbem" to access the HPVM namespace so CapAd can see that the provider isn't there. You might be using some other user account for your WBEM access from SIM.

Wade

[Robert Cook_6]

Wade,
The cimauth for HPVM was the problem.

Thanks,

Bob