OID reference

fsMIY1731DefectConditionTrap

1.3.6.1.4.1.29601.2.7.0.2

Description

This object specifies the a MEP having 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. If a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.7.0 (fsMIY1731Notifications)
Node code
2
Node name
fsMIY1731DefectConditionTrap
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.29601.2.7.0.2
URN notation
urn:oid:1.3.6.1.4.1.29601.2.7.0.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 7 0 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731Notifications(0) fsMIY1731DefectConditionTrap(2)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/7/0/2
  • /ISO/Identified-Organization/6/1/4/1/29601/2/7/0/2
  • /ISO/3/6/1/4/1/29601/2/7/0/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/org/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/org/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731Notifications/fsMIY1731DefectConditionTrap

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

Show 2 published definitions

fsMIY1731DefectConditionTrap · current

fsMIY1731DefectConditionTrap NOTIFICATION-TYPE
    OBJECTS     { fsMIY1731ContextName,
                  fsMIY1731ErrorLogType
                }
    STATUS      current
    DESCRIPTION
        "This object specifies the a MEP having 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.

        If a defect 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 fsMIY1731ErrorLogType
        variable in the notification:

           fsMIY1731MegIndex - Also the index of the MEP's
                              Maintenance Entity Group table entry
                              (fsMIY1731MegTable).
           fsMIY1731MeIndex - Also an index (with the MEG table index)
                              of the MEP's Maintenance Entity
                              table entry (fsMIY1731MeTable).
           fsMIY1731MepIdentifier - MEP Identifier and final index
                              into the MEP table (fsMIY1731MepTable)
       "
 
    ::= { fsMIY1731Notifications 2 }

fsMIY1731DefectConditionTrap · current

fsMIY1731DefectConditionTrap NOTIFICATION-TYPE
    OBJECTS     { fsMIY1731ContextName,
                  fsMIY1731ErrorLogType
                }
    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.

        If a defect 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 fsMIY1731ErrorLogType
        variable in the notification:

           fsMIY1731MegIndex - Also the index of the MEP's
                              Maintenance Entity Group table entry
                              (fsMIY1731MegTable).
           fsMIY1731MeIndex - Also an index (with the MEG table index)
                              of the MEP's Maintenance Entity
                              table entry (fsMIY1731MeTable).
           fsMIY1731MepIdentifier - MEP Identifier and final index
                              into the MEP table (fsMIY1731MepTable)
       "
 
    ::= { fsMIY1731Notifications 2 }

Meaning

Descriptions

2 unique

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

Description 1

This object specifies the a MEP having 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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable)

Sources for this description

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

See 1 matching source record

Description 2

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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable)

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

2 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)1 record · 1 source

Description 1

fsMIY1731DefectConditionTrap · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: fsMIY1731DefectConditionTrap

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "fsMIY1731DefectConditionTrap",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "fsMIY1731ContextName",
    ",",
    "fsMIY1731ErrorLogType",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the a MEP having 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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable) \"",
    "::=",
    "{",
    "fsMIY1731Notifications",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "fsMIY1731ContextName",
        "fsMIY1731ErrorLogType"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the a MEP having 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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable)"
    ],
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

fsMIY1731DefectConditionTrap · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsMIY1731DefectConditionTrap

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "fsMIY1731DefectConditionTrap",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "fsMIY1731ContextName",
    ",",
    "fsMIY1731ErrorLogType",
    "}",
    "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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable) \"",
    "::=",
    "{",
    "fsMIY1731Notifications",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "fsMIY1731ContextName",
        "fsMIY1731ErrorLogType"
      ]
    ],
    [
      "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. If a defect 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 fsMIY1731ErrorLogType variable in the notification: fsMIY1731MegIndex - Also the index of the MEP's Maintenance Entity Group table entry (fsMIY1731MegTable). fsMIY1731MeIndex - Also an index (with the MEG table index) of the MEP's Maintenance Entity table entry (fsMIY1731MeTable). fsMIY1731MepIdentifier - MEP Identifier and final index into the MEP table (fsMIY1731MepTable)"
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.7.0.1 fsMIY1731FrameLossTrap00
1.3.6.1.4.1.29601.2.7.0.3 fsMIY1731TstRecivedWithErrorTrap00
1.3.6.1.4.1.29601.2.7.0.4 fsMIY1731FrameDelayTrap00
1.3.6.1.4.1.29601.2.7.0.5 fsMIY1731TxFailTrap00