OID reference

activeAlarmTable

1.3.6.1.4.1.17409.2.2.11.2.1

Description

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 …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.17409.2.2.11.2 (eponAlarmObjGroup)
Node code
1
Node name
activeAlarmTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.17409.2.2.11.2.1
URN notation
urn:oid:1.3.6.1.4.1.17409.2.2.11.2.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 17409 2 2 11 2 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvEponEocTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvFTTxTree(2) alarmsIdent(2) eponAlarmTree(11) eponAlarmObjGroup(2) activeAlarmTable(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/17409/2/2/11/2/1
  • /ISO/Identified-Organization/6/1/4/1/17409/2/2/11/2/1
  • /ISO/3/6/1/4/1/17409/2/2/11/2/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/17409/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprise/17409/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprise/nscrtvRoot/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprise/nscrtvRoot/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprises/17409/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprises/17409/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprises/nscrtvRoot/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/enterprises/nscrtvRoot/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/17409/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/17409/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nscrtvRoot/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nscrtvRoot/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/17409/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/17409/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nscrtvRoot/nscrtvEponEocTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nscrtvRoot/nscrtvFTTxTree/alarmsIdent/eponAlarmTree/eponAlarmObjGroup/activeAlarmTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF ActiveAlarmEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

activeAlarmTable · current

activeAlarmTable OBJECT-TYPE
      SYNTAX SEQUENCE OF ActiveAlarmEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
        "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.
        "
      ::= { eponAlarmObjGroup 1 }

activeAlarmTable · current

activeAlarmTable OBJECT-TYPE
			SYNTAX SEQUENCE OF ActiveAlarmEntry
			MAX-ACCESS not-accessible
			STATUS current
			DESCRIPTION
				"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.
				"
			::= { eponAlarmObjGroup 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)FS.COM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

activeAlarmTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: activeAlarmTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "activeAlarmTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "ActiveAlarmEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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. \"",
    "::=",
    "{",
    "eponAlarmObjGroup",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "ActiveAlarmEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.17409)

Chen Zhiguo

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.17409.2.2.11.2.1.1 activeAlarmEntry1010

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.17409.2.2.11.2.2 historyAlarmTable112
1.3.6.1.4.1.17409.2.2.11.2.3 eventLogTable16