OID reference

dot1agCfmFaultAlarm

1.3.6.1.4.1.3902.3.120.0.1

Description

A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault No…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.3.120.0 (dot1agNotifications)
Node code
1
Node name
dot1agCfmFaultAlarm
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.3902.3.120.0.1
URN notation
urn:oid:1.3.6.1.4.1.3902.3.120.0.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3902 3 120 0 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxr10(3) zxr10cfmMIB(120) dot1agNotifications(0) dot1agCfmFaultAlarm(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/3/120/0/1
  • /ISO/Identified-Organization/6/1/4/1/3902/3/120/0/1
  • /ISO/3/6/1/4/1/3902/3/120/0/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zxEnterpriseMib/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/vendor-objects/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/vendor-objects/zte/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/vendor-objects/zxEnterpriseMib/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/org/dod/internet/private/enterprise/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/org/dod/internet/private/enterprise/zte/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/org/dod/internet/private/enterprise/zxEnterpriseMib/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • /iso/org/dod/internet/private/enterprises/3902/zxr10/zxr10cfmMIB/dot1agNotifications/dot1agCfmFaultAlarm
  • Additional combinations skipped.

The displayed source records contain one distinct definition. Compare its source records.

dot1agCfmFaultAlarm NOTIFICATION-TYPE
                  OBJECTS { dot1agCfmMepHighestPrDefect
                           }
                  STATUS current
                  DESCRIPTION
                           "A MEP has a persistent defect condition. A notification
                           (fault alarm) is sent to the management entity with the OID
                           of the MEP that has detected the fault.
                           Whenever a MEP has a persistent defect,
                           it may or may not generate a Fault Alarm to warn the system
                           administrator of the problem, as controlled by the MEP
                           Fault Notification Generator State Machine and associated
                           Managed Objects. Only the highest-priority defect, as shown
                           in Table 20-1, is reported in the Fault Alarm.
                           If a defect with a higher priority is raised after a Fault
                           Alarm has been issued, another Fault Alarm is issued.
                           The management entity receiving the notification can identify
                           the system from the network source address of the
                           notification, and can identify the MEP reporting the defect
                           by the indices in the OID of the dot1agCfmMepHighestPrDefect
                           variable in the notification:
                           dot1agCfmMdIndex - Also the index of the MEP's
                           Maintenance Domain table entry
                           (dot1agCfmMdTable).
                           dot1agCfmMaIndex - Also an index (with the MD table index)
                           of the MEP's Maintenance Association
                           table entry (dot1agCfmMaTable).
                           dot1agCfmSessionId - MEP Identifier and final index
                           into the MEP table (dot1agCfmMepTable).
                           "
                  REFERENCE
                           "802.1ag clause 12.14.7.7"
                  ::= { dot1agNotifications 1 }

Meaning

Descriptions

1 unique

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

A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (dot1agCfmMaTable). dot1agCfmSessionId - MEP Identifier and final index into the MEP table (dot1agCfmMepTable).

Sources for this description

ZTE 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 1ZTE MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

dot1agCfmFaultAlarm · currentZTE MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: dot1agCfmFaultAlarm

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "dot1agCfmFaultAlarm",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "dot1agCfmMepHighestPrDefect",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (dot1agCfmMaTable). dot1agCfmSessionId - MEP Identifier and final index into the MEP table (dot1agCfmMepTable). \"",
    "REFERENCE",
    "\"802.1ag clause 12.14.7.7\"",
    "::=",
    "{",
    "dot1agNotifications",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "dot1agCfmMepHighestPrDefect"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (dot1agCfmMaTable). dot1agCfmSessionId - MEP Identifier and final index into the MEP table (dot1agCfmMepTable)."
    ],
    [
      "REFERENCE",
      "802.1ag clause 12.14.7.7"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3902)

Xianlin Luo