EMS using obsolete information on cloned system

[Carl Houseman]

I cloned a system with Ignite and that all went well except for this - EMS remembers and is using settings from the original system.

For example:

When EMS logs an error that originates on the new system, it writes it to the syslog on the old system, and the E-mail it sends identifies the old system as the source of the problem.

EMS periodically sounds off about "lost connection" to a device (VA disk array) which has a different name for the controller device on the new system.

How can I update EMS to use info about the current system?

thanks.

[Robert-Jan Goossens]

Hi Carl,

The easiest is to remove/install the support tools.

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

Regards,
Robert-Jan

[Ivan Krastev]

Another option is to change only that monitor via monconfig - http://docs.hp.com/en/diag/archive/ems_anat.htm#controlling


regards,
ivan

[Carl Houseman]

monconfig doesn't have any option to specify which host is being monitored.

Problem is it thinks it's still monitoring the host of a different name at a different IP.

[DCE]

I agree with Robert

I have found removing and reinstalling the fastest way to correct the issue

[Carl Houseman]

OK, so I downloaded the March 2007 "OnlineDiag" a.k.a. Support Tools bundle. It's a lot newer than the September 2005 version currently installed. The release notes tell me to:

"Install any patch that is a prerequisite for installing Diagnostic and Support Tools."
and
"Install patches (as applicable) after installing the Diagnostic and Support Tools."

The link given to determine patch requirements is:

http://www.docs.hp.com/en/diag/st/st_read.htm

but that has no information about the (HP-UX 11iv1) March 2007 release. I can go with the December 2006 or June 2007 link, and those two have different patch requirements. Am I the only one to find these gaping holes in HP documentation?

JFG I started the install to see if it would warn about patches needed, and it didn't complain. Should things be OK?

[Torsten.]

To make sure your system is up to date now, consider to select this point from ITRC:

"run a patch assessment" below the patch database link.

http://www8.itrc.hp.com/service/patch/assessSystemsPage.do?BC=main|

BTW, do you have Commandview SDM still installed? I guess you mentioned this earlier. Be aware you probably need to adjust this too.

[Andrew Merritt_2 · Accepted solution]

Hi Carl,
The A.55.00 release (labelled as March 2007) is essentially a re-issue of the A.53.00 (December 2006) release with a fix to the installation scripts, so the patch requirements for the December release apply. Unfortunately, as you noticed, the documentation doesn't make this completely clear; it is explained in the table here - http://www.docs.hp.com/en/diag/stm/stm_upd.htm#table


Andrew

[Carl Houseman]

OK, so I go to remove the existing OnlineDiag support tools bundle, as per documentation where I'm told to

swremove OnlineDiag

and I get a lot of unhappiness and a failure to remove. See attached.

Should I just go ahead and install the newer one, then uninstall that to clear the configuration, and then re-install?

[Carl Houseman]

Never mind, I figured out how to get it to remove...

[Torsten.]

Did you remove ISEE too?

You should install and set up it again!

I guess it will keep the old data too, e.g. serial number and contract ID's of the old system.