NSCRTV-EPON-ALARM-MGM-MIB: View SNMP OID List / Download MIB

Alarm TRAP definition

Event TRAP definition

Alarm instance, indicates the detailed managed object, which detects faults.

The unique sequence number for the alarm to be cleared, for alarm clearing. Set to 0 for alarm reporting

Additional info to the alarm, for further desciption of the alarm. The format of it shall be related to each kind alarm defined in alarm reference table

A unique sequence number for each trap generated by node. The sequence number shall be reset to 1 when node restarts. The alarm sequence number shall be independent of the event sequence number. Each shall be self-governed. -------------------------------------------------------------------------------- The sequence ID of alarm shall be assigned from the order of transmitting trap to the NMS, instead of the order of alarm occurance. Therefore the NMS will receive the continuous sequence ID. 1. When device is in active/standby mode, sequence ID shall be synchronized between active and standby control module. 2. When control module switchover takes place, the current sequence ID shall keep the synchronized value. 3. When device restarts, sequence ID shall start from 1. 4. It shall be increased per alarm trap including both alarm raising and clear. 5. Non-zero value shall be used. When reaches the maximum number, it shall roll back to 1. -------------------------------------------------------------------------------- The sequence ID of event shall be assigned from the order of transmitting trap to the NMS. Therefore the NMS will receive the continuous sequence ID. 1. When device is in active/standby mode, sequence ID shall be synchronized between active and standby control module. 2. When control module switchover takes place, the current sequence ID shall keep the synchronized value. 3. When device restarts, sequence ID shall start from 1. 4. It shall be increased per event trap. 5. Non-zero value shall be used. When reaches the maximum number, it shall roll back to 1.

Active alarm table The device shall maintain this table, to maintain all outstanding (not cleared) alarms generated by the device, including: 1. Not hit device local alarm filter. That means had been reported to trap receiver (NMS or EMS) 2. Hit local alarm filter. That means not trap is reported to trap receiver for the alarm. The device shall maintain two numbers: 1. Alarm sequence number: As described in eponTrapSequenceNumber, it is initially set to 1 when device restarts, increases per trap reported to trap receiver, and rollover to 1 once it reaches the maximum value. From NMS's view, traps received from a nodes will be consecutive, by identifying the alarm sequence number carried in alarm trap. If breaks, means some trap may be lost, since packet loss between NMS and NE. 2. Alarm raising number: This is maintained by NE internally and does not intend for being acknowledged by external manage system. It is designed to uniquely indentify each alarm raised by NE, excluding duplicates. Once one alarm raised, despite whether it is hit by alarm filter, NE shall assign a raising number to it. So, it major functionality is to uniquely identify alarms hit NE local alarm filter, since this kindly alarm will not be reported to NMS, and hence no alarm sequence number is assigned to it. It is initially set to 1 when device restarts, increases per alarm generation ( excluding duplicates), and rollover to 1 once it reaches the maximum value. FUNCTION DESCRIPTION OF ACTIVE ALARM TABLE: ALARM RAISING ---------------------- 1. When NE detects one fault and associates to one kind of alarm, it shall check whether there is same alarm in active alarm table, which is indexed by alarm code and alarm instance. If hits, it means duplicates, update the corresponding entry of the table. Otherwise, 2. The alarm is not a duplicate. Assign an alarm raising number. Check whether the alarm hits local alarm filters. If hits, set alarm sequence number to 0. Create an entry into active alarm table. Otherwise, 3. Assign an alarm sequence number to the alarm. Create an entry into active alarm table. Report the alarm trap to all trap receivers. ALARM CLEARING ---------------------- 1. When NE detects one fault is cleared and associates to one kind of alarm, it shall check whether there is corresponding alarm in active alarm table, which is indexed by alarm code and alarm instance. If no hit, escape this clear event. Upon a hit, if the alarm sequence number is 0, move the active alarm entry to history alarm table and update the corresponding fields. At this case, historyAlarmCorrelationId and historyAlarmSeqNum will be set to 0. Otherwise, 2. Assign an alarm sequence number to the clear trap. Report the alarm clear trap to all trap receivers. Move the active alarm entry to history alarm table and update the corresponding fields. At this case, activeAlarmSeqNum shall be copied to historyAlarmCorrelationId, and historyAlarmSeqNum shall be set to the new alarm sequence number for the clear trap. ALARM SYNCHRONIZATION BETWEEN NE AND NMS --------------------------------------------- 1. Once NMS finds the alarm sequence number in reported alarm traps is not continuous, it will walk active or history alarm table of the NE for the lost seuqence number.

Alarm sequence number The definition refered to the description of activeAlarmTable

Alarm instance, indicates the detailed managed object

Alarm raising number. The definition refered to the description of activeAlarmTable

The time stamp when alarm occurs, which triggered to create the active alarm entry.

The time stamp when alarm occurs, where the alarm is duplicated with existed active alarm entry, and it was the latest one.

Number of repeated alarms for this active alarm entry

Node shall not clear an active alarm, upon the confirmation of the active alarm, but just mark an acknowledged status. An alarm will only be cleared once the clear condition hits.

Additional info to the alarm, for further desciption of the alarm. The format of it shall be related to each kind alarm defined in alarm reference table

History alarm table. The device shall maintain this table, to maintain all cleared alarms generated by the device, including: 1. Not hit device local alarm filter. That means had been reported to trap receiver (NMS or EMS) 2. Hit local alarm filter. That means not trap is reported to trap receiver for the alarm. The number of history alarm enteries in the table could be device-specific. However, it is recommended no less than 200 entries. The detailed function definition refers to that given in description of activeAlarmTable.

Alarm sequence number The definition refered to the description of historyAlarmTable

Alarm instance, indicates the detailed managed object

Alarm raising number. The definition refered to the description of historyAlarmTable

The time stamp when alarm occurs, which triggered to create the history alarm entry.

The time stamp when alarm occurs, where the alarm is duplicated with existed history alarm entry, and it was the latest one.

Number of repeated alarms for this history alarm entry

It is the corresponding sequence ID of the alarm that to be cleared.

Additional info to the alarm, for further desciption of the alarm. The format of it shall be related to each kind alarm defined in alarm reference table

Define when the alarm was cleared

Event log table. The device shall maintain this table, to maintain all events had be reported by the device, including: 1. The event table shall be saved in RAM memory and shall be flushed when OLT restarts. 2. The event log table shall support no less than 200 entries. When the event log table is full, the oldest entry in the table shall be removed first. 3. When OLT is configured with control module redundancy, active controller shall automatically synchronize the events in event log table b/w active and standby.

Event sequence number The definition refered to the description of eponTrapSequenceNumber

Event instance, indicates the detailed managed object

The time stamp when event occurs

Additional info to the event, for further desciption of the event. The format of it shall be related to each kind event defined in event reference table

A table of transport addresses to be used in the generation of SNMP messages.

A transport address to be used in the generation of SNMP operations. Entries in the snmpTargetAddrTable are created and deleted using the snmpTargetAddrRowStatus object.