NSCRTV-EPON-ALARM-MGM-MIB Table View

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.

activeAlarmEntry row .1.3.6.1.4.1.17409.2.2.11.2.1.1

Indexes

activeAlarmSeqNum activeAlarmRaisingNumber

Column	Syntax	OID
activeAlarmSeqNum Alarm sequence number The definition refered to the description of activeAlarmTable	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.1.1.1
activeAlarmCode ?澯???룬????¼C	NSCRTV-EPONEOC-EPON-MIBEponAlarmCode Type Constraints: range: 1..65535 Description: Alarm codes, uniquely indentifies each kind of alarm. Refer to EPON alarm definition table	.1.3.6.1.4.1.17409.2.2.11.2.1.1.2
activeAlarmInstance Alarm instance, indicates the detailed managed object	NSCRTV-EPONEOC-EPON-MIBEponAlarmInstance Type Constraints: range: 8 Description: Alarm instance, which define the detailed management object reported the alarm. For example, OLT device 1, slot 2, port 3 reports a port down alarm. It is represents in OCTET STRING format. 1. The first four OCTET has s…	.1.3.6.1.4.1.17409.2.2.11.2.1.1.3
activeAlarmSeverity ?澯???س̶ȡ?	NSCRTV-EPONEOC-EPON-MIBEponSeverityType Type Values: 1 critical 2 major 3 minor 4 warning 5 info 6 clear Description: ?澯???س̶?	.1.3.6.1.4.1.17409.2.2.11.2.1.1.4
activeAlarmRaisingNumber Alarm raising number. The definition refered to the description of activeAlarmTable	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.1.1.5
activeAlarmFirstOccurTime ?澯??ʼ??????ʱ?? The time stamp when alarm occurs, which triggered to create the active alarm entry.	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.1.1.6
activeAlarmLastOccurTime The time stamp when alarm occurs, where the alarm is duplicated with existed active alarm entry, and it was the latest one.	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.1.1.7
activeAlarmRepeats Number of repeated alarms for this active alarm entry	SNMPv2-SMICounter32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.1.1.8
activeAlarmConfirm ?澯ȷ?? 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.	SNMPv2-TCTruthValuer/w Type Values: 1 true 2 false Description: Represents a boolean value.	.1.3.6.1.4.1.17409.2.2.11.2.1.1.9
activeAlarmAdditionalText 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	OctetString Constraints: range: 0-256	.1.3.6.1.4.1.17409.2.2.11.2.1.1.10

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.

historyAlarmEntry row .1.3.6.1.4.1.17409.2.2.11.2.2.1

Indexes

historyAlarmSeqNum historyAlarmRaisingNumber

Column	Syntax	OID
historyAlarmSeqNum Alarm sequence number The definition refered to the description of historyAlarmTable	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.2.1.1
historyAlarmCode ?澯???룬????¼C	NSCRTV-EPONEOC-EPON-MIBEponAlarmCode Type Constraints: range: 1..65535 Description: Alarm codes, uniquely indentifies each kind of alarm. Refer to EPON alarm definition table	.1.3.6.1.4.1.17409.2.2.11.2.2.1.2
historyAlarmInstance Alarm instance, indicates the detailed managed object	NSCRTV-EPONEOC-EPON-MIBEponAlarmInstance Type Constraints: range: 8 Description: Alarm instance, which define the detailed management object reported the alarm. For example, OLT device 1, slot 2, port 3 reports a port down alarm. It is represents in OCTET STRING format. 1. The first four OCTET has s…	.1.3.6.1.4.1.17409.2.2.11.2.2.1.3
historyAlarmSeverity ?澯???س̶ȡ?	NSCRTV-EPONEOC-EPON-MIBEponSeverityType Type Values: 1 critical 2 major 3 minor 4 warning 5 info 6 clear Description: ?澯???س̶?	.1.3.6.1.4.1.17409.2.2.11.2.2.1.4
historyAlarmRaisingNumber Alarm raising number. The definition refered to the description of historyAlarmTable	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.2.1.5
historyAlarmFirstOccurTime ?澯??ʼ??????ʱ?? The time stamp when alarm occurs, which triggered to create the history alarm entry.	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.2.1.6
historyAlarmLastOccurTime The time stamp when alarm occurs, where the alarm is duplicated with existed history alarm entry, and it was the latest one.	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.2.1.7
historyAlarmRepeats Number of repeated alarms for this history alarm entry	SNMPv2-SMICounter32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.2.1.8
historyAlarmCorrelationId It is the corresponding sequence ID of the alarm that to be cleared.	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.2.1.9
historyAlarmAdditionalText 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	OctetString Constraints: range: 0-256	.1.3.6.1.4.1.17409.2.2.11.2.2.1.10
historyAlarmClearTime Define when the alarm was cleared	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.2.1.11

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.

eventLogEntry row .1.3.6.1.4.1.17409.2.2.11.2.3.1

Indexes

eventSeqNum

Column	Syntax	OID
eventSeqNum Event sequence number The definition refered to the description of eponTrapSequenceNumber	SNMPv2-SMIUnsigned32 Type Constraints: range: 0..4294967295	.1.3.6.1.4.1.17409.2.2.11.2.3.1.1
eventCode ?¼????룬????¼C	NSCRTV-EPONEOC-EPON-MIBEponAlarmCode Type Constraints: range: 1..65535 Description: Alarm codes, uniquely indentifies each kind of alarm. Refer to EPON alarm definition table	.1.3.6.1.4.1.17409.2.2.11.2.3.1.2
eventInstance Event instance, indicates the detailed managed object	NSCRTV-EPONEOC-EPON-MIBEponAlarmInstance Type Constraints: range: 8 Description: Alarm instance, which define the detailed management object reported the alarm. For example, OLT device 1, slot 2, port 3 reports a port down alarm. It is represents in OCTET STRING format. 1. The first four OCTET has s…	.1.3.6.1.4.1.17409.2.2.11.2.3.1.3
eventOccurTime The time stamp when event occurs	SNMPv2-TCDateAndTime Type Constraints: range: 8 range: 11 Description: A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month …	.1.3.6.1.4.1.17409.2.2.11.2.3.1.4
eventAdditionalText 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	OctetString Constraints: range: 0-256	.1.3.6.1.4.1.17409.2.2.11.2.3.1.5

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

eponManagementAddrEntry row .1.3.6.1.4.1.17409.2.2.11.3.1.1

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

Indexes

eponManagementAddrName

Column	Syntax	OID
eponManagementAddrName EMS???ܽڵ??????	OctetString Constraints: range: 1-32	.1.3.6.1.4.1.17409.2.2.11.3.1.1.1
eponManagementAddrTAddress ???ܽڵ?Ĵ?????ַ??TRAP UDP?˿ںš?	NSCRTV-EPONEOC-EPON-MIBTAddressr/w Type Constraints: range: 8 Description: First four octets sames definition of IpAddress, stands for NMS IP address The last four octets same definition of INTEGER, stands for trap UDP port	.1.3.6.1.4.1.17409.2.2.11.3.1.1.2
eponManagementAddrCommunity ????TRAP??Community??	OctetStringr/w Constraints: range: 0-64	.1.3.6.1.4.1.17409.2.2.11.3.1.1.3
eponManagementAddrRowStatus ????ɾ??һ??EPON??????ַ??	SNMPv2-TCRowStatusr/w Type Values: 1 active 2 notInService 3 notReady 4 createAndGo 5 createAndWait 6 destroy Description: The RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of …	.1.3.6.1.4.1.17409.2.2.11.3.1.1.4