cancel
Showing results for 
Search instead for 
Did you mean: 

EMS notification

AbhilashPaul
Advisor

EMS notification

In my Box rx2660 only one powersully is connected, last time the server restarted because of power failure and it send EMS notification as normal. Now every day at the same time its sending the EMS notification that "its powersully 2 is failure....etc " Pls some help..
9 REPLIES
Steven E. Protter
Exalted Contributor

Re: EMS notification

Shalom,

Need the exact text of the message.

I suspect however that one of the power supplies on the system is damaged and requires replacement.

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
Michal Kapalka (mikap)
Honored Contributor

Re: EMS notification

Hi AbhilashPaul,

in my case, i recieve every day this messages on RP and som RX servers, where only one PowerSuply is installed, it's something as a BUG ( combination of Firmware and EMS ).

mikap

example :

kmsemng1:/>5042 -r /system/events/ia64_corehw/core_hw -n 173015356 -a <

CURRENT MONITOR DATA:

Event Time..........: Wed May 13 03:14:36 2009
Severity............: CRITICAL
Monitor.............: ia64_corehw
Event #.............: 104011
System..............: kmsemng1

Summary:
Power Unit : Redundancy lost or not present.


Description of Error:

The number of Power supplies has gone from N+1 (redundant) to N
(non-redundant) if a Power supply was removed, or the number of Power
supplies is < N+1.

Probable Cause / Recommended Action:

The minimum number of power supplies required to power the unit is
currently installed and operating. There are no redundant I/O power
supplies available in case of failure. If redundancy is desired another
Power supply should be added.

For information on the sensor that generated this event, refer to FRU ID
in Event Details section.

Additional Event Data:
System IP Address...: 10.36.64.120
Event Id............: 0x4a0a1efc00000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_ia64_corehw.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/rp3440
EMS Version.....................: A.04.20
STM Version.....................: A.59.00
System Serial Number............: DE61300118
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ia64_corehw.htm#104011

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


Event Details :

Event Date .............: Thu Dec 27 11:10:00 2007
Sensor Number ..........: 0x4f
Sensor Type ............: Power Unit
Sensor Class ...........: Discrete (type 0Bh)
Sensor Reading/Offset...: 0x02 (Sensor Reading)
Event Type.............: Not Applicable
Entity ID ..............: 19
Generic Message.........:
Power Unit : Redundancy lost
Entity FRU Id Info......:
power unit / power domain (Sensor ID: Power Redundancy)
RajuD
Frequent Advisor

Re: EMS notification

Hi,

Download Support Tools Bundle, update in your system and check.
“Education is our passport to the future, for tomorrow belongs to those who prepare for it today.”
AbhilashPaul
Advisor

Re: EMS notification

hi Michal,

My case is same like yours..
in my box only one powrsully is connected..
2 weeks back its restarted ,then its started to send mails daily..
Thanks for the reply..
AbhilashPaul
Advisor

Re: EMS notification

hi Steven ,
this is the error i am getting.. daily..

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Sun May 24 19:14:53 2009

rxdev2 sent Event Monitor notification information:

/system/events/ia64_corehw/core_hw is >= 3.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Sun May 24 19:14:53 2009
Severity............: CRITICAL
Monitor.............: ia64_corehw
Event #.............: 103001
System..............: rxdev2

Summary:

Power Supply : Failure is detected.

Description of Error:

The system has detected that one of the power supplies has failed.

Probable Cause / Recommended Action:

The power supply has failed. Contact your HP support representative to
check the power supply.

For information on the sensor that generated this event, refer to
FRU ID in Event Details section.

Additional Event Data:
System IP Address...: 10.10.240.73
Event Id............: 1030011220090524191449
Monitor Version.....: B.07.00.02
Event Class.........: System
Client Configuration File............:
/var/stm/config/tools/monitor/default_ia64_corehw.clcfg
Client Configuration File Version....: A.01.00
Qualification criteria met.
Number of events: 1
Associated OS error log entry id(s)
None
Additional System Data:
System Model Number.............: ia64 hp server rx2660
EMS Version.....................: A.04.20
STM Version.....................: NA
System Serial Number............: SGH47531DE
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ia64_corehw.htm#E103001


v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


Event Details :

Event Date ...................: Tue May 19 11:04:59 2009
Sensor Number .................: 0x40
Sensor Type ...................: Power Supply
Sensor Class ..................: Sensor specific
Sensor Reading/Offset .........: 0x1 (Sensor Reading)
Event Type ...................: Assertion
Entity ID .....................: 0xa
Generic Message ...............:
Power Supply Failure detected
Entity FRU Id Info ............: (Sensor ID 0())

Error Details:

Additional information on this event can be obtained from evweb
logviewer (Refer SFM User Guide) with the following log id: 761



>---------- End Event Monitoring Service Event Notification ----------<
Jeeshan
Honored Contributor

Re: EMS notification

this may sometimes comes when STM/EMS version is too old.

Check with HP about STM/EMS software upgradation. If anythinggoes wrong with your hardware than it will come.
a warrior never quits
mobidyc
Trusted Contributor

Re: EMS notification

Hello,

sometimes, EMS keep old alerts.

to fix this problem :
mv /var/stm/logs/monitor/remindersel.dat /var/stm/logs/monitor/remindersel.dat.old

and restart diags:
/sbin/init.d/diagnostic stop
/sbin/init.d/diagnostic start

Regards,
cedrick Gaillard
Best regards, Cedrick Gaillard
Viktor Balogh
Honored Contributor

Re: EMS notification

you can delete the old messages with the monconfig tool too:

1. stop EMS

# /etc/opt/resmon/lbin/monconfig

a And then "k" for Kill

2. remove file /var/stm/logs/monitor/remindersel.dat

3. start EMS

# /etc/opt/resmon/lbin/monconfig

a And then "e" for enable

After that, check if the date is correct on the Management Port:


MP> cm

> date
****
Unix operates with beer.
DHINESHBABU
Advisor

Re: EMS notification

Hi,


try to fix power supply in other slots, and check if the error continues update MP firmware or replace MP card


KSD