Itanium Memory Monitor (Events)

Note: An exclamation point (!) in the text will be replaced by a value in the text when actually displayed in an event message. For example: "The memory component: !" might actually appear in an event message as: "The memory component: Ext 1 DIMM 0A"

Event 103

• Severity: Information
• Event Summary: Test event
• Event Class: Memory
• Problem Description:
  This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.
• Probable Cause / Recommended Action:
  No action required.
• Automated Recovery: None.
• Event Generation Threshold: Every occurrence.

Event 1000

• Severity: Informational
• Event Summary: A memory page has been deallocated and entered into the Page Deallocation Table (PDT).
• Event Class: Memory
• Problem Description:
  Correctable single bit memory errors have been detected resulting in the deallocation of a memory page.
• Probable Cause / Recommended Action:
  The occasional deallocation of memory pages is to be expected. No action is required. Should the rate of pages being deallocated become excessive, an event of higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: Never
• Event Details: None

Event 1100

• Severity: Major Warning
• Event Summary: A memory page has been deallocated and entered into the Page Deallocation Table (PDT).
• Event Class: Memory
• Problem Description:
  !The Page Deallocation Table (PDT) is !% full.
  
  PDT Entries Used: !
  PDT Entries Free: !
  PDT Total Size: !
  
  A large number of memory pages have been deallocated due to excessive correctable single bit errors being detected.
• Probable Cause / Recommended Action:
  Although the PDT is not in immediate danger of overflowing, it may be advisable to monitor the situation. If pages continue to be deallocated, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: PDT usage is at or above 70% but below 80% full.
• Event Details: None.

Event 1200

• Severity: Serious
• Event Summary: A memory page has been deallocated and entered into the Page Deallocation Table (PDT).
• Event Class: Memory
• Problem Description:
  !The Page Deallocation Table (PDT) is !% full.
  
  PDT Entries Used: !
  PDT Entries Free: !
  PDT Total Size: !
  
  An excessive number of memory pages have been deallocated due to excessive correctable single bit errors being detected.
• Probable Cause / Recommended Action:
  Although the PDT is not in immediate danger of overflowing, it is advisable to monitor the situation. If pages continue to be deallocated, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: PDT usage is at or above 80% but below 90% full.
• Event Details: None.

Event 1300

• Severity: Critical
• Event Summary: A memory page has been deallocated and entered into the Page Deallocation Table (PDT).
• Event Class: Memory
• Problem Description:
  !The Page Deallocation Table (PDT) is !% full.
  
  PDT Entries Used: !
  PDT Entries Free: !
  PDT Total Size: !
  
  An excessive number of memory pages have been deallocated due to excessive correctable single bit errors being detected. Although the errors are being corrected, this condition indicates a potential problem.
• Probable Cause / Recommended Action:
  The Page Deallocation Table (PDT) is in danger of overflowing; it is strongly advisable to closely monitor the situation. Although the errors are being corrected, this condition can indicate a potential problem. Contact your memory vendor support representative to check the memory boards.
• Automated Recovery: None
• Event Generation Threshold: PDT usage is at or above 90% full.
• Event Details: None.

Event 1400

• Severity: Fatal
• Event Summary: A memory page has been deallocated and entered into the Page Deallocation Table (PDT).
• Event Class: Memory
• Problem Description:
  !The Page Deallocation Table (PDT) is !% full.
  
  PDT Entries Used: !
  PDT Entries Free: !
  PDT Total Size: !
  
  All the memory pages have been deallocated due to excessive correctable single bit errors being detected. This condition indicates a problem and will result in loss of information.
• Probable Cause / Recommended Action:
  The Page Deallocation Table (PDT) is full and will overflow. If pages continue to be deallocated, data loss may result. Contact your HP support representative to check the memory boards.
• Automated Recovery: None
• Event Generation Threshold: PDT usage is almost 100% full.
• Event Details: None.

Event 3000

• Severity: Informational
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! has generated a single bit memory error and the error information has been logged in the memlog file.
• Probable Cause / Recommended Action:
  The occasional correctable single bit memory error is to be expected. No action is required. Should the rate of single bit errors become excessive, an event of higher severity will be generated.
• Automated Recovery:None.
• Event Generation Threshold:Never.
• Event Details: None.

Event 3005

• Severity: Information
• Event Summary: Correctable memory error event. A correctable memory error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component : !/! has generated a correctable memory error and the error information has been logged in the memlog file.
• Probable Cause / Recommended Action:
  The occasional correctable memory error is to be expected. No action is required. Should the rate of double bit errors become excessive, an event of higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 3100

• Severity: Major Warning
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing correctable single bit errors at the same address on the same component. Since the page has not been deallocated and is still active, this indicates the address is located in kernel or reserved memory.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it may be advisable to evaluate whether the system should be rebooted. Rebooting the system may allow the memory page to be deallocated so it is no longer referenced. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 65 occurrences within 24 hours
• Event Details: None.

Event 3200

• Severity: Serious
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing higher than expected correctable single bit errors at the same address on the same component. Since the page has not been deallocated and is still active, this indicates the address is located in kernel or reserved memory.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is advisable to evaluate whether the system should be rebooted. Rebooting the system may allow the memory page to be deallocated so it is no longer referenced. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 120 occurrences within 48 hours
• Event Details: None.

Event 3300

• Severity: Critical
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing an excessive number of single bit errors (SBE) at the same address on the same component. Since the page has not been deallocated and is still active, this indicates the address is located in kernel or reserved memory.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is strongly advisable to evaluate whether the system should be rebooted. Rebooting the system may allow the memory page to be deallocated so it is no longer referenced. Although the errors are being corrected, this condition can indicate a potential problem.
• Automated Recovery: None
• Event Generation Threshold: 180 occurrences within 72 hours
• Event Details: None.

Event 4000

• Severity: Major Warning
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing correctable single bit errors (SBE) on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it may be advisable to monitor the situation. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 40 occurrences within 24 hours
• Event Details: None.

Event 4005

• Severity: Major Warning
• Event Summary: Correctable memory error event. A correctable memory error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component : ! is experiencing correctable memory errors on a single component.
• Probable Cause / Recommended Action:
  Although the memory errors are being corrected, it may be advisable to monitor the situation.
• Automated Recovery: None
• Event Generation Threshold: 20 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 20 occurrences within 24 hours

Event 4100

• Severity: Serious
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing a high rate of correctable single bit errors on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is advisable to monitor the situation. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 60 occurrences in 24 hours
• Event Details: None.

Event 4200

• Severity: Critical
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing an excessive rate of single bit errors on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is strongly advisable to monitor the situation. This condition can indicate a potential problem. Contact your memory vendor support representative to check the memory boards.
• Automated Recovery: None
• Event Generation Threshold: 80 occurrences in 24 hours
• Event Details: None.

Event 4300

• Severity: Major Warning
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing correctable single bit errors (SBE) on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it may be advisable to monitor the situation. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 220 occurrences within 7 days
• Event Details: None.

Event 4400

• Severity: Serious
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing a high rate of correctable single bit errors on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is advisable to monitor the situation. If an excessive rate of single bit errors occurs, an event with higher severity will be generated.
• Automated Recovery: None
• Event Generation Threshold: 270 occurrence in 7 days
• Event Details: None.

Event 4500

• Severity: Critical
• Event Summary: Single bit error (SBE) event. A correctable single bit error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The memory component: ! is experiencing an excessive rate of correctable single bit errors on a single component.
• Probable Cause / Recommended Action:
  Although the single bit errors are being corrected, it is strongly advisable to monitor the situation. This condition can indicate a potential problem. Contact your memory vendor support representative to check the memory boards.
• Automated Recovery: None
• Event Generation Threshold: 320 occurrences in 7 days
• Event Details: None.

Event 5000

• Severity: Information
• Event Summary: Double Chip Sparing has been invoked.
• Event Class: Memory
• Problem Description:
  Corrected memory errors have been detected. Double Chip Sparing has been invoked upon the memory bank for the following memory component: !
• Probable Cause / Recommended Action:
  System firmware has detected and corrected memory errors. Double Chip Sparing has been invoked to mitigate this condition. On the next reboot, system firmware will test the specified memory components, and may take them offline if the errors persist. Contact your HP support representative to check the specified memory components at your next scheduled downtime.
• Automated Recovery: None.
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 5100

• Severity: Information
• Event Summary: Double Chip Sparing has been invoked.
• Event Class: Memory
• Problem Description:
  Corrected memory errors have been detected. Double Chip Sparing has been invoked upon the memory bank for the following memory component: !
• Probable Cause / Recommended Action:
  System firmware has detected and corrected memory errors. Double Chip Sparing has been invoked to mitigate this condition. On the next reboot, system firmware will test the specified memory components, and may take them offline if the errors persist. Contact your HP support representative to check the specified memory components at your next scheduled downtime.
• Automated Recovery: None.
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 5200

• Severity: Major Warning
• Event Summary: Double Chip Sparing has been invoked.
• Event Class: Memory
• Problem Description:
  Corrected memory errors have been detected. Double Chip Sparing has been invoked upon the memory bus for the following memory component(s): !
• Probable Cause / Recommended Action:
  System firmware has detected and corrected memory errors. Double Chip Sparing has been invoked to help mitigate this condition. It is advisable to monitor the situation and contact your HP support representative to check the specified memory board(s) and/or the cell board containing these memory components. If system firmware detects a large number of errors during a future reboot, the affected echelons may be deallocated.
• Automated Recovery: None.
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 5300

• Severity: Major Warning
• Event Summary: Double Chip Sparing has been invoked.
• Event Class: Memory
• Problem Description:
  Corrected memory errors have been detected. Double Chip Sparing has been invoked upon the memory bus for the following memory component(s): !
• Probable Cause / Recommended Action:
  System firmware has detected and corrected memory errors. Double Chip Sparing has been invoked to help mitigate this condition. It is advisable to monitor the situation and contact your HP support representative to check the specified memory board(s) and/or the cell board containing these memory components. If system firmware detects a large number of errors during a future reboot, the affected echelons may be deallocated.
• Automated Recovery: None.
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 5400

• Severity: Critical
• Event Summary: Multiple Double Chip Sparing have been invoked.
• Event Class: Memory
• Problem Description:
  Corrected memory errors have been detected. Multiple Double Chip Sparing have been invoked on the following cell: !.\n
• Probable Cause / Recommended Action:
  System firmware has detected and corrected memory errors. Multiple Double Chip Sparing have been invoked to help mitigate this condition. Although the memory errors are corrected and multiple Double Chip Sparing have been invoked, this condition may indicate a potential problem. Monitor the situation and contact your HP support representative to check the affected hardware.
• Automated Recovery: None.
• Event Generation Threshold: Never
• Fault Notifier Event Generation Threshold: Never

Event 6100

• Severity: Serious
• Event Summary: Correctable memory error event. A correctable memory error has been detected and logged.
• Event Class: Memory
• Problem Description:
  The system is experiencing a high rate of correctable memory errors on a single component.
• Probable Cause / Recommended Action:
  Although the memory errors are being corrected, it may be advisable to monitor the situation.
• Automated Recovery: None
• Event Generation Threshold: 24 occurrences within 24 hours
• Fault Notifier Event Generation Threshold: 24 occurrences within 24 hours

Top of Page / Diagnostics HOME