Table Of Contents

Events Processed

Events Processed

---

Table D-1 lists all possible events you might see in a Device Fault Manager (DFM) Alerts and Activities Detail page, along with the following:

•Description: A summary of the event, including typical causes (if known).

•Trigger: How DFMlearns of the event — either from normal polling, a threshold that was exceeded, or a trap that was received.

•Severity: The severity that DFM assigns to the event—critical, warning, or informational.

•Device Type: The devices, as classified in DFM, on which the event can occur.

•Event Code: The code used by Notification Services to track changes to default DFM event names using the Notification Customization feature. (For more information, see Customizing the Names of DFM Events.)

Event names correspond to what is displayed in the Description column of the Alerts and Activities Detail page.

The events a device can report are determined by the device function. See Configuring Polling and Thresholds for information on device functions.

Table D-1 Events that DFM Supports 

Event	Description, Cause, Severity, and Event Code
BackupActivated	Description: Backup port or interface has come online, indicating that the port or interface it backs up has gone down. Trigger: Polling. Severity: Warning. Device Type: All. Event Code: 1000.
Duplicate	Description: Same IP address is configured on multiple managed systems. Trigger: Polling (often during rediscovery). Severity: Critical. Device Type: All. Event Code: 1001.
ExceededMaximumUptime	Description: A backup or dial-on-demand port or interface has been in the Up state for too long. Trigger: Exceeded Maximum uptime threshold. Severity: Warning. Device Type: All (except Network Management). Event Code: 1002.
ExcessiveFragmentation	Description: System memory is highly fragmented. Trigger: Exceeded Memory fragmentation threshold. Severity: Critical. Device Type: All. Event Code: 1003.
Flapping	Description: Port or interface is repeatedly alternating between Up and Down states over a short period of time. DFM issues this event by monitoring the number of link downs received within the link window for a particular network adapter (using the Link threshold and Link Window parameters). Trigger: Exceeded Link trap threshold for Link trap window; or processed trap (see Processed SNMP Traps, and How DFM Calculates Repeated Restarts and Flapping). Severity: Critical. Device Type: All. Event Code: 1004.
HighBackplaneUtilization	Description: Utilization of the backplane's bandwidth exceeds the Backplane utilization threshold. Trigger: Exceeded Backplane utilization threshold. Severity: Critical. Device Type: All. Event Code: 1005.
HighBroadcastRate	Description: Input packet broadcast percentage exceeds the Broadcast threshold. The input packet broadcast percentage calculates the percentage of total capacity that was used to receive broadcast packets. Trigger: Exceeded Broadcast threshold. Severity: Critical. Device Type: All. Event Code: 1006.
HighBufferMissRate	Description: Rate of buffer misses exceeds the Memory buffer miss threshold. Trigger: Exceeded Memory buffer miss threshold. Severity: Critical. Device Type: All. Event Code: 1007.
HighBufferUtilization	Description: Number of buffers used exceeds the Memory buffer utilization threshold. Trigger: Exceeded Memory buffer utilization threshold. Severity: Critical. Device Type: All. Event Code: 1008.
HighCollisionRate	Description: Rate of collisions exceeds the Collision threshold. Trigger: Exceeded Collision threshold. Severity: Critical. Device Type: All. Event Code: 1009.
HighDiscardRate	Description: A HighDiscardRate event occurs when: •The input packet queued rate is greater than the minimum packet rate, and the input packet discard percentage is greater than the Discard threshold. The input packet queued rate is the rate of packets received without error. The input packet discard percentage is calculated by dividing the rate of input packets discarded by the rate of packets received. •The output packet queued rate is greater than the minimum packet rate, and the output packet discard percentage is greater than the Discard threshold. The output packet queued rate is the rate of packets sent without error. The output packet discard percentage is calculated by dividing the rate of output packets discarded by the rate of packets sent. Trigger: Exceeded Discard threshold. Severity: Critical. Device Type: All. Event Code: 1010.
HighErrorRate	Description: A HighErrorRate event occurs for input or output packets when both of the following thresholds are exceeded: •Error threshold—Percentage of packets in error •Error traffic threshold—Percentage of bandwidth in use Trigger: Exceeded Error threshold and equaled or exceeded Error traffic threshold. Severity: Critical. Device Type: All. Event Code: 1011.
HighQueueDropRate	Description: Number of packets discarded due to input or output queue overflow exceeding the Queue drop threshold. The input (or output) queue overflow is derived by dividing the number of packets designated to be sent (or received) that were discarded due to queue overflow, by the total number of packets in the queue. Trigger: Exceeded Queue drop threshold. Severity: Critical. Device Type: All. Event Code: 1012.
HighUtilization	Description: Current utilization exceeds the utilization threshold configured for this network adapter. (Processor utilization threshold defines the upper limit for CPU utilization and is expressed as a percentage of total CPU capacity.) Note For information on how DFM determines interface duplexity when duplexity is not specified, refer to Utilization threshold. Trigger: Exceeded one of these thresholds: •Processor utilization •Utilization (interface settings) Severity: Critical. Device Type: All. Event Code: 1013.
InformAlarm	Description: An information pass-through trap was generated. Trigger: Pass-through trap. See Pass-Through SNMP Unidentified Traps. Severity: Informational. Device Type: All. Event Code: 1014.
InsufficientFreeMemory	Description: System is running out of memory resources. Also reported if there has been a failure to allocate a buffer due to lack of memory. Trigger: Exceeded Free memory threshold. Severity: Critical. Device Type: All. Event Code: 1015.
MajorAlarm	Description: Critical pass-through trap was generated. Trigger: Pass-through trap. See Pass-Through SNMP Unidentified Traps. Severity: Informational. Device Type: All. Event Code: 1016.
MinorAlarm	Description: Significant pass-through trap was generated. Trigger: Pass-through trap. See Pass-Through SNMP Unidentified Traps. Severity: Informational. Device Type: All. Event Code: 1017.
OperationallyDown	Description: Interface—Card or network adapter's operational state is not normal. System Hardware—Disk's operational state is not normal. Trigger: Polling, or processed trap (see Processed SNMP Traps). Note For interfaces, DFM will only generate an OperationallyDown clear event if the card is reinserted into the same slot, and if the module index is the same before and after the card is reinserted. Severity: Critical. Device Type: All. Event Code: 1018.
OutofRange	Description: Device temperature or voltage is outside the normal operating range. When an OutofRange event is generated, you will normally also see fan, power supply, or temperature events. Trigger: Exceeded one of these thresholds: •Relative temperature threshold •Relative voltage threshold Severity: Critical. Device Type: All. Event Code: 1019.
RepeatedRestarts	Description: System repeatedly restarts over a short period of time. DFM issues this event by monitoring the number of system cold and warm starts received within the restart window (using the Restart threshold and the RestartWindow parameters). Trigger: Exceeded Restart trap threshold for Restart trap window; or processed trap (see Processed SNMP Traps, and How DFM Calculates Repeated Restarts and Flapping). Severity: Critical. Device Type: All. Event Code: 1020.
StateNotNormal	Description: A fan, power supply, temperature sensor, or voltage sensor is not acting normally. When an OutofRange event is generated, you will also see a fan, power supply, or temperature event. Trigger: Polling. Severity: Critical. Device Type: All. Event Code: 1021.
Unresponsive	Description: Device does not respond to ICMP or SNMP requests. Probable causes are: •On a system: ICMP Ping requests and SNMP queries to the device timeout received no response. •On an SNMP Agent: Device ICMP ping requests are successful, but SNMP requests time out with no response. Note A system might also be reported as Unresponsive if the only link (for example, an interface) to the system goes down. Trigger: Polling. Severity: Critical. Device Type: All. Event Code: 1022.