Alarm History
EMS Alarm History
To view the alarm history in the EMS, select the alarm, right click and select Details. The EMS Alarm history allows you to view the history of alarms that have occurred in the system.
The Alarm Details will display the known information about the alarm.
The alarm history log files are located on the EMS server in /opt/bbmgr/server/data/JLogger. These are American Standard Code for Information Interchange (ASCII) text files. The latest log file is named alarm.log. All previous alarm log files contain a prefix of "alarm-timestamp.backup".
The rules that determine when to generate a new backup log file are:
- Each log file can have a maximum file size of 5Mb. A new backup file is created when the maximum file size has been reached.
- A new backup file is created when the EMS server is restarted.
- Up to 40 log files of the same type can be kept in the Logger directory, including the backup files. When this limit is reached, the oldest backup file is deleted to make room for the new backup file.
- With this type of configuration, up to 200Mb of alarm history can be maintained on the server.
- Both the maximum number of log files and the maximum file size can be customized via a property file.
Alarm History Log Files
The alarm log files have the same general format as shown in the Alarm History user interface. This log file can be utilized for historical purposes to preserve the alarm history. In the alarms history log, each field is separated with a semi-colon (;). Field descriptions, and a sample entry, are shown below. Table 1 provides a description of each of the alarm log field definitions.
Field Definition
| ThreadName;TimeLogged;IP;TID;PGID;PairCount;TimeProcessd;SourceOID;CardType; NMSProbableCau se;PhysicalLocation;NEProbableCause;AdditionalText;Severity;Status; AID;ServiceAffecting |
| Field Definition | Description |
| ThreadName |
The name of the thread responsible for logging the alarm (used for debugging). |
| TimeLogged | The time the alarm was written to the log (used for debugging). |
| IP | The NE Internet Protocol (IP) address. |
| TID | The target identifier (TID) of the shelf associated with the alarm. |
| PGID | The Pair Gain Identifier (PGID) of the shelf associated with the alarm. |
| PairCount | The pair count of the DSL line (or -1 if the alarm is not for an DSL line). |
| TimeProcessed > | For Ethernet OLTs, this is the date and time the alarm was set or cleared, including the time zone code. Note: The OLT uses the UTC time (from the NTP server) and the daylight savings time setting to determine the local OLT time. The OLT sends the UTC time with the alarm. EMS converts the UTC time to the local EMS server time (including the daylight savings time adjustment). The result is indicated in this field. For ATM OLTs, this is the time EMS processed the alarm. |
| SourceOID | Simple Network Management Protocol (SNMP) Object Identifier (OID) of the source associated with the alarm. Note: This value is always N/A for Ethernet OLT alarms. |
|
CardType |
The card type associated with the alarm for ATM OLTs. Note: For Ethernet NEs, this field does not apply, and the value is always -1. |
| NMSProbableCause | The Network Management Station (NMS) probable cause Joint Procurement Consortium (JPC) value. |
| PhysicalLocation | The physical location associated with the alarm. |
| NEProbableCause | The OLT probable cause (SNMP value). |
| AdditionalText | Any additional information associated with the alarm. |
| Severity | The severity of the alarm (critical, major, minor, etc.). |
| Status | ACTIVE or CLEARED. |
| AID | The access identifier (AID) indicating the equipment location. For details, see Alarm AIDs. |
| ServiceAffecting | Indicates whether the alarm condition is service-affecting (SA) or non-service-affecting (NSA) for Ethernet OLT alarms. Note: For ATM OLTs, this field always indicates NSA because the ATM OLT does not support this feature. |
Alarm Log File Entry Example
| RMI TCP Connection(40)-172.28.99.44;Tue Dec 13 14:39:23 CST 2005;172.28.127.18; TID18;fdsa;-1;Wed Dec 31 18:02:39 CST 1969;N/A;-1;lossOfSignal;1/19/1/2; lossOfSignal; ;critical;ACTIVE;MDS1-ESUA-2;SA |