NMIS Event List
- Keith Sinclair (Deactivated)
- John Sinclair
Owned by Keith Sinclair (Deactivated)
Table of Contents
Event Configuration
NMIS includes a feature "Event Configuration" which allows users to individually manage the events and alerts NMIS generates, this can be accessed in the NMIS GUI at "System -> System Configuration -> Event Configuration".
When you access the screen you can edit a given event and decide how you would like NMIS to handle it. To prevent an event from being actioned by NMIS or opEvents, you would edit the event.
For example we want to stop getting the BGP Peer Down alert. Edit the event and change "Notify on Event" and "Log on Event" to false and "edit (save)" your change. If you did not want this event to contribute to the node becoming degraded you would change "Status Summary" to false as well.
Event List
The following events can be generated by NMIS, because NMIS is handling events statefully, the Event is cancelled by a "Cancelling Event".
| Event | Type | Stateful | Cancelling Event | Description |
| Alert "Custom Alert Name" *** | Fault | Yes | Alert "Custom Alert Name" Closed | This is the catch all for custom alerts. More details about Custom Alerts for SNMP MIB Polling can be found at Alerts - Using models to generate custom events |
| Alert: BGP Peer Down | Fault | Yes | Alert: BGP Peer Down Closed | A BGP Routing Protocol Peer has been detected to be down. |
| Alert: GE Alarm Active | Fault | Yes | Alert: GE Alarm Active Closed | A GE Alarm is active on the node. |
| Alert: High Disk Usage | Fault | Yes | Alert: High Disk Usage Closed | The node has high disk usage (disk is getting full) |
| Alert: High Memory Usage | Fault | Yes | Alert: High Memory Usage Closed | The node has high memory utilisation. |
| Alert: High Number of System Processes | Fault | Yes | Alert: High Number of System Processes Closed | A high number of system processes has been detected on the node. |
| Alert: High Oper Completion Time | Fault | Yes | Alert: High Oper Completion Time Closed | The Cisco IPSLA operation has high completion time. |
| Alert: High Swap Usage | Fault | Yes | Alert: High Swap Usage Closed | The node has high SWAP Memory utilisation. |
| Alert: High TCP Connection Count | Fault | Yes | Alert: High TCP Connection Count Closed | The node has a high number of TCP connections. |
| Alert: RTT Completion Status Not OK | Fault | Yes | Alert: RTT Completion Status Not OK Closed | The Cisco IPSLA operation has not completed correctly. |
| Alert: Virtual Machine not Powered On | Fault | Yes | Alert: Virtual Machine not Powered On Closed | The Virtual Machine is NOT powered on, this may or may not be a desirable state. |
| Interface Down | Fault | Yes | Interface Up | An interface NMIS is managing has gone down (physical or logical outage). |
| NMIS runtime exceeded | Admin | No | N/A | Indicating that the NMIS polling cycle is going too long. |
| Node Down | Fault | Yes | Node Up | A node is down, stopped responding to ICMP or SNMP packets for longer than the timeout. |
| Node Failover | Fault | No | N/A | A redundant node pair has failed over, typically a Cisco PIX or ASA. |
| Node Reset | Fault | No | N/A | A node reset has been detected, the operating system has restarted. |
| Node Configuration Change | Config | No | N/A | A configuration change has been detected on this node. |
| Proactive Calls Utilisation | Threshold | Yes | Proactive Calls Utilisation Closed | There are too many calls, and you need more lines. |
| Proactive CPU | Threshold | Yes | Proactive CPU Closed | The configured CPU threshold of the node has been exceeded. |
Proactive CPU User | Threshold | Yes | Proactive CPU User Closed | The User CPU utilisation threshold has been exceeded. |
| Proactive CPU System | Threshold | Yes | Proactive CPU System Closed | The System CPU utilisation threshold has been exceeded. |
| Proactive CPU IO Wait | Threshold | Yes | Proactive CPU IO Wait Closed | The IO (Input/Output) Waiting for CPU threshold has been exceeded. |
| Proactive CPU Idle | Threshold | Yes | Proactive CPU Idle Closed | The Idle CPU utilisation has fallen below the configured threshold. |
| Proactive Dead Modem | Threshold | Yes | Proactive Dead Modem Closed | A modem is dead and probably should be put out to pasture. |
| Proactive Interface Availability | Threshold | Yes | Proactive Interface Availability Closed | The configured interface availability threshold of the node has been exceeded. |
| Proactive Interface Discards Input Packets | Threshold | Yes | Proactive Interface Discards Input Packets Closed | The configured threshold for INPUT packets being discarded by the interface. |
| Proactive Interface Discards Output Packets | Threshold | Yes | Proactive Interface Discards Output Packets Closed | The configured threshold for OUTPUT packets being discarded by the interface. |
| Proactive Interface Error Input Packets | Threshold | Yes | Proactive Interface Error Input Packets Closed | The configured threshold has been exceeded for INPUT packets with errors being received by the interface. |
| Proactive Interface Error Output Packets | Threshold | Yes | Proactive Interface Error Output Packets Closed | The configured threshold has been exceeded for OUTPUT packets with errors being sent by the interface. |
| Proactive Interface Input Utilisation | Threshold | Yes | Proactive Interface Input Utilisation Closed | The configured interface INPUT utilisation threshold of the node has been exceeded. |
| Proactive Interface LOW Input Utilisation | Threshold | Yes | Proactive Interface LOW Input Utilisation Closed | The interface has very LOW INPUT utilisation. |
| Proactive Interface Output Utilisation | Threshold | Yes | Proactive Interface Output Utilisation Closed | The configured interface OUTPUT utilisation threshold of the node has been exceeded. |
| Proactive Interface LOW Output Utilisation | Threshold | Yes | Proactive Interface LOW Output Utilisation Closed | The interface has very LOW OUTPUT utilisation. |
| Proactive Memory Free | Threshold | Yes | Proactive Memory Free Closed | The available free memory is below the configured threshold. |
| Proactive Memory Utilisation | Threshold | Yes | Proactive Memory Utilisation Closed | The memory utilisation has exceeded the configured threshold. |
| Proactive Heap Utilisation | Threshold | Yes | Proactive Heap Utilisation Closed | The heap utilisation has exceeded the configured threshold. |
| Proactive Modem Utilisation | Threshold | Yes | Proactive Modem Utilisation Closed | The modems are being overused, and should probably be retired now. |
| Proactive Reachability | Threshold | Yes | Proactive Reachability Closed | The overall reachability of the node has has fallen below the threshold. |
| Proactive Response Time | Threshold | Yes | Proactive Response Time Closed | The response time threshold of the node has been exceeded. |
| Proactive Temp | Threshold | Yes | Proactive Temp Closed | The configured threshold for temperature of the node has been exceeded. |
| RPS Fail | Fault | No | N/A | The redundant power supply has failed. |
| SNMP Down | Fault | Yes | SNMP Up | SNMP communication to the node has a problem. |
| Service Down | Fault | Yes | Service Up | A service NMIS is managing has failed to respond. |