Operating System - HP-UX
1752821 Members
4062 Online
108789 Solutions
New Discussion

Re: Issue with ia64_corehw on 11.31 missing

 
Michele Albertone
Occasional Contributor

Issue with ia64_corehw on 11.31 missing

Hi,

 

I have an rx4640 running 11.31 and:

OnlineDiag                            B.11.31.16.02

I used to see messages related to ia64_corehw monitor in the event.log file, and the ia64_corehw process was running in 11.23.

After moving to 11.31 could not find anymore the binary file even if the man page still references:

/usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw

which used to be the proper path in 11.23.

 

Is there anythink I should install on top of the OnlineDiag package?


Thanks!

Mike

3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: Issue with ia64_corehw on 11.31 missing

Shalom,

 

I suspect the depot OnlineDiag itself

 

swverify OnlineDiag

 

swverify \*

 

You may wish to  swremove and swinstall anew.

 

Post command results for more detailed assistance.

 

SEP

Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Dennis Handly
Acclaimed Contributor

Re: Issue with ia64_corehw on 11.31 missing

I suppose the man page could be stale and ia64_corehw replaced on 11.31?  It did have a zombie problem and they could have rewritten it?

 

If you have that depot, you can use "swlist -l file" to see if it is even there.

Michele Albertone
Occasional Contributor

Re: Issue with ia64_corehw on 11.31 missing

Hi Steven, Dennis, sorry for replying late on this.

 

Understood EMS is going to move to SFM in our platforms so that this may eventually fix the issue with monitoring.

 

I checked many of our systems and it seems a bug on the EMS.

I noticed that removing the power from one of the power supplies the ILO was firing the expected event, but there was no notification to the syslog, nor to the EMS.

2536  ILO             2  204EA1137F021382 FFFF000B4F090400 POWER_REDUNDANCY_REGAINED

                                                           21 Oct 2011 06:38:55

2535  ILO             2  204EA1137F021381 FFFF03EF40080400 POWER_SUPPLY_AC_RESTORED

                                                           21 Oct 2011 06:38:55

2534  ILO             2  204EA1108F021380 FFFF010B4F090400 POWER_REDUNDANCY_LOST

                                                           21 Oct 2011 06:26:23

2533  ILO            *3  204EA1108F02137F FFFF036F40080400 POWER_SUPPLY_AC_LOST

                                                           21 Oct 2011 06:26:23

 

Had a chance to look a bit more in it and found that

 

/var/opt/resmon/log/event.log shows the event properly:

While the monconfig shows:

  EVENT MONITORING IS CURRENTLY ENABLED.

  The current monitor configuration is:

   1) Send events generated by all monitors

      with severity >= MAJOR WARNING to SYSLOG

   2) Send events generated by all monitors

      with severity >= INFORMATION to TEXTLOG /var/opt/resmon/log/event.log

   3) Send events generated by all monitors

      with severity >= MAJOR WARNING to EMAIL root

but the syslog was not showing anything.

 

Will close this one for the time being while waiting for SFM to be available in our nodes.

 

Thanks to both