OnlineDiag B.11.11.21.04 installation issue

[arkie]

How can I locate the fileset WBEMServices.WBEM-CORE ver A.20.05.%000 or other upcoming requirements in the future?

[Torsten.]

Should be here:

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMSvcs

[arkie]

Since there was a problem with the STM (which was resolved then with a mere diagnostic start), I got an advise from the GSC to go for a proactive upgradation of the OnlineDiag bundle. What I would like to know - is this the normal procedure for a bundle/fileset upgradation. Is there possibly anything in HP-
UX 11iv1 like the yum utility in RHEL5

[Torsten.]

In hp-ux you have software assistant.

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6834AA

[arkie]

The installations had succeeded - WBEMServices, EventMonitoring and OnlineDiag in that order, but when I am running cstm or xstm, I am getting the following error:-

/usr/lib/dld.sl: Can't find path for shared library: libdiagfx.sl
/usr/lib/dld.sl: No such file or directory
/usr/sbin/cstm[24]: 21826 Abort(coredump)

[arkie]

I had to manually copy libdiagfx.sl & libdiagua.sl to /usr/sbin/stm/lib, chmod 555 & chown bin:bin to finally get the cstm> prompt. The version is A.63.05. mapall is displaying the devices.

This is definitely not the recommended way, but the problem is not clear at all. There was no error during the fileset installations.

Will have to be observing for a few more times. But, thanks! Torsten. It was a good learning experience.

[Fabio Ettore]

Hi,

are you sure the OnlineDiag installation was clean?
Those libraries come from the STM product, if they are missing I'd think something was wrong during installation.

I'd suggest trying to reinstall OnlineDiag, I mean using -x reinstall=true.

HTH.

Best regards,
Fabio

[Bill Hassell]

The EMS/Diag products are broken when installed separately. The (undocumented and non-intuitive) way to do this is to create a depot and swcopy both STM and EMS to the depot. Then swinstall everything in the depot at one time. The SD utilities have more than enough capabilities to identify dependencies and interconnections but like any packaging system, the quality depends on understanding what must be checked by the packager.

[Dennis Handly]

>Bill: The (undocumented and non-intuitive) way to do this is to create a depot and swcopy both STM and EMS to the depot.

I thought that is the obvious way, mainly to prevent multiple reboots. (Or to keep swinstall from getting tired. :-)

But documentation helps if it is required.

[Bill Hassell]

> Dennis...undocumented

What is undocumented is that both products must be upgraded at the same time. Simply installing EMS will produce the errors seen above. What is non-intuitive is that the errors are resolved by installing another product (STM).