Overview of Monitored Events

This section describes:

Types of Events and Alarms Reported
How Servers Report Alarms and Events

Types of Events and Alarms Reported

The LSMS monitors itself for the types of events and alarms shown in Table 1 . When one of these events occurs, the LSMS does one or more of the following:

Displays a notification on the graphical user interface (GUI notification)
Posts a Surveillance notification at a certain frequency to the administration console by default, or to the second serial port if so configured
Sends a trap to a Network Management System (NMS) if you have installed the optional Remote Monitoring feature

Every GUI notification and Surveillance notification contains its associated event number. Traps contain a trap ID, which is explained in Overview of Traps.

Notification Event Number Categories
Event Number Range	Category	Description
0000–1999	EMS	Events that pertain to an Element Management System (EMS). The EMS is a process that runs on the Multi-Purpose Server (MPS) at a network element.
2000–3999	NPAC	Events that pertain to a Number Portability Administration Center (NPAC)
4000–5999	Platform and switchover (some of these events do not produce GUI notifications)	Events that pertain to system resources, such as disks, hardware, memory, central processing unit (CPU) utilization and to switchover functions
6000–7999	Main LSMS processes	Events that pertain to one of the following main LSMS processes: lsman, supman, npacagent, or eagleagent
8000–8999	Applications	Events that pertain to LSMS applications that are feature or application dependent, such as LNP Database Synchronization, Service Assurance, or NPA Split Administration

How Servers Report Alarms and Events

The LSMS servers perform the following functions to monitor and report events:

The standby server:
- Monitors itself only for:
  - Platform events (see Platform Alarms)
  - Switchover-readiness events, such as those that describe database replication or critical network interfaces
- Controls the appropriate AlarmLED (Critical, Major, or Minor) on the front of the server by illuminating the LED when one or more platform alarm in that category exists and turning off the LED when no platform alarms in that category exist
- Sends any notification to its Serial Port 3 and logs the notification in its Surveillance log
- Sends the notification to the active server
The active server performs the following functions:
- Monitors itself for both platform events and application events
- Controls the appropriate AlarmLED (Critical, Major, or Minor) on the front of the server by illuminating the LED when one or more platform alarm in that category exists and turning off the LED when no platform alarms in that category exist
- Sends all platform events for itself, events reported from the standby server, and appropriate application events for itself to its Serial Port 3 and also logs the event as appropriate in its Surveillance log (some event notifications are reported repeatedly; for more information about which events are reported repeatedly, see the individual event descriptions)
  - Alarms that originate from the active server contain the alarm text with no hostname
  - Alarms that originate from the standby server contain the alarm text preceded by the standby server’s hostname
    Note: Although all events are reported through SNMP traps and all platform alarms are reported through Surveillance notifications, not all application alarms are reported both through the GUI and through Surveillance notifications; for more information about which alarms are reported in which way, see the individual event descriptions.
- Displays one time on the GUI each platform or application event for itself and each platform event received from the standby server:
  - Alarms that originate from the active server display the alarm text with no hostname
  - Alarms that originate from the standby server display the alarm text preceded by the standby server’s hostname
- Sends one Simple Network Management Protocol (SNMP) trap for each platform or application event for itself and for each platform event received from the standby server. Each trap contains the IP address of the server from which the notification originated.