OID reference

fsMIEcfmFaultAlarm

1.3.6.1.4.1.2076.160.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.2076.160.0 (fsMIEcfmNotifications)
Node code
1
Node name
fsMIEcfmFaultAlarm
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.2076.160.0.1
URN notation
urn:oid:1.3.6.1.4.1.2076.160.0.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 160 0 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsMIEcfmMIB(160) fsMIEcfmNotifications(0) fsMIEcfmFaultAlarm(1)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/160/0/1
  • /ISO/Identified-Organization/6/1/4/1/2076/160/0/1
  • /ISO/3/6/1/4/1/2076/160/0/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprises/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/org/dod/internet/private/enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/org/dod/internet/private/enterprises/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/org/dod/internet/private/ldap-enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/org/dod/internet/private/vendor-objects/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-organization/dod/internet/private/enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-organization/dod/internet/private/enterprises/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/fsMIEcfmMIB/fsMIEcfmNotifications/fsMIEcfmFaultAlarm

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

fsMIEcfmFaultAlarm NOTIFICATION-TYPE
    OBJECTS     {
                 fsMIEcfmContextName, 
                 fsMIEcfmMepHighestPrDefect
                }
    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 fsMIEcfmMepHighestPrDefect
        variable in the notification:

           fsMIEcfmMdIndex - Also the index of the MEP's
                              Maintenance Domain table entry
                              (fsMIEcfmMdTable).
           fsMIEcfmMaIndex - Also an index (with the MD table index)
                              of the MEP's Maintenance Association
                              table entry (fsMIEcfmMaTable).
           fsMIEcfmMepIdentifier - MEP Identifier and final index
                              into the MEP table (fsMIEcfmMepTable).
       "
    REFERENCE
       "802.1ag clause 12.14.7.7"
    ::= { fsMIEcfmNotifications 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 fsMIEcfmMepHighestPrDefect variable in the notification: fsMIEcfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (fsMIEcfmMdTable). fsMIEcfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (fsMIEcfmMaTable). fsMIEcfmMepIdentifier - MEP Identifier and final index into the MEP table (fsMIEcfmMepTable).

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs

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), Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 2 sources

Description 1

fsMIEcfmFaultAlarm · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs2 sources

Status in source: current.

Names: fsMIEcfmFaultAlarm

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "fsMIEcfmFaultAlarm",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "fsMIEcfmContextName",
    ",",
    "fsMIEcfmMepHighestPrDefect",
    "}",
    "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 fsMIEcfmMepHighestPrDefect variable in the notification: fsMIEcfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (fsMIEcfmMdTable). fsMIEcfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (fsMIEcfmMaTable). fsMIEcfmMepIdentifier - MEP Identifier and final index into the MEP table (fsMIEcfmMepTable). \"",
    "REFERENCE",
    "\"802.1ag clause 12.14.7.7\"",
    "::=",
    "{",
    "fsMIEcfmNotifications",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "fsMIEcfmContextName",
        "fsMIEcfmMepHighestPrDefect"
      ]
    ],
    [
      "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 fsMIEcfmMepHighestPrDefect variable in the notification: fsMIEcfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (fsMIEcfmMdTable). fsMIEcfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (fsMIEcfmMaTable). fsMIEcfmMepIdentifier - MEP Identifier and final index into the MEP table (fsMIEcfmMepTable)."
    ],
    [
      "REFERENCE",
      "802.1ag clause 12.14.7.7"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.160.0.2 fsEcfmMepDefectTrap00