EMS Event Notification

[Philemon_2]

Hi,

Any one please suggest me what is the impact of this error. I receive this once in a day daily. Please explain me the fix.

SYSLOG Report.

Jan 30 11:04:03 hputil01 EMS [2872]: ------ EMS Event Notification ------ Valu
e: "SERIOUS (4)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold
: >= " 3") Execute the following command to obtain event details: /opt/res
mon/bin/resdata -R 188219394 -r /system/events/ipmi_fpl/ipmi_fpl -n 188219434 -a

EVENT LOG REPORT>

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

Notification Time: Wed Jan 30 11:04:03 2008

hputil01 sent Event Monitor notification information:

/system/events/ipmi_fpl/ipmi_fpl is >= 1.
Its current value is SERIOUS(4).



Event data from monitor:

Event Time..........: Wed Jan 30 11:04:03 2008
Severity............: SERIOUS
Monitor.............: fpl_em
Event #.............: 325
System..............: hputil01.it.hughessupply.com

Summary:
Cannot add PDT entry--PDT full


Description of Error:

The memory page deallocation table (PDT) is full.

Probable Cause / Recommended Action:


C: Excessive memory errors A: Contact HP Support personnel to troubleshoot the
problem
-


Additional Event Data:
System IP Address...: 11.224.21.59
Event Id............: 0x47a09ff300000000
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fpl_em.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 rx2600
EMS Version.....................: A.04.10
STM Version.....................: C.46.00
System Serial Number............: US34374015
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#325

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


IPMI event hex: 0xa08000d800e021d0 000000000000000000
Time Stamp: Wed Jan 30 16:00:42 2008
Event keyword: MEM_PDT_TABLE_FULL
Alert level name: Critical
Reporting vers: 1
Data field type: Data field unused
Decoded data field:
Reporting entity ID: 0 ( Cab 0 Cell 0 CPU 0 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 216 (0xd8)


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

Thanks'
Philemon

[Steven E. Protter]

Shalom,

Hardware problem.

I think you should forward this message to your response center and run diagnostics with cstm mstm or xstm

sEP

[Zeev Schultz]

Could be due to RAM problems. Run :

echo "selclass qualifier memory;in;wait;il" | cstm

from command line and see if it reports errors in memory log.

[Robert-Jan Goossens]

Hi,

have a look at this thread.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1104216&admit=109447626+1201711662853+28353475

Regards,
Robert-Jan

[Andrew Merritt_2]

Almost certainly problems with (physical) memory. I would expect you are also getting EMS events warning about bad memory.

As suggested, you should contact HP about getting the hardware fixed.

You should also upgrade the OnlineDiags, since you have an old version (C.46.00, from September 2004; the current version is C.58.00 from December 2007).

Andrew

[Ramesh S]

Hi

As per the Error description

"The memory page deallocation table (PDT) is full"

You could try clearing the PDT by,

There are several ways of clearing the PDT.

On systems that have a PDT enabled, the PDT is cleared automatically upon reboot, when a memory card is replaced,or when the configuration has been changed.

On systems that do not have a PDT enabled but are running MPD, MEMLOGP should be cleared using Memclr from LOGTOOL, prior to replacing the memory card.

On your system, which has PDT enabled, a reboot did not solve the problem, indicating a memory problem. Follow these steps to resolve this:

1. Reboot the system, but interrupt the boot sequence by pressing any key within 10 seconds. This willbring up the Main Menu Screen.
2. From the Main Menu, go to the Boot Code Handler BCH) Service Menu, and enter:

SERvice

3. From the Service Menu, enter:

PDT

which will show the PDT table. From this table you can see which SIMM has the problem.

4. From the Service Menu, enter:

PDT clear

to clear the PDT.

5. Now power off the system and replace the defective SIMM.

6. Power the system on and all should be fine.

If the issue persist, it could be a hardware issue.

I hope it may help you.

Thanks & Regards

Ramesh

[Torsten.]

Not necessarily a hardware problem, but maybe.

First you should update the diagnostics and the firmware if the version is not current!

Second action would be a reboot.

Now watch the PDT (with cstm - see above), next steps will depend if you get new entries there.