Reference record for OID 1.3.6.1.4.1.9.9.604.0.1


parent
1.3.6.1.4.1.9.9.604.0 (cdot1agNotifications)
node code
1
node name
cdot1agFaultAlarm
dot oid
1.3.6.1.4.1.9.9.604.0.1
type
NOTIFICATION-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cdot1CfmMIB(604) cdot1agNotifications(0) cdot1agFaultAlarm(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/cdot1CfmMIB/cdot1agNotifications/cdot1agFaultAlarm
  • Description by mibdepot

    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 cdot1agMepHighestPrDefect
    variable in the notification:

    cdot1agMdIndex - Also the index of the MEP's
    Maintenance Domain table entry
    (cdot1agMdTable).
    cdot1agMaIndex - Also an index (with the MD table index)
    of the MEP's Maintenance Association
    table entry (cdot1agMaTable).
    cdot1agMepIdentifier - MEP Identifier and final index
    into the MEP table (cdot1agMepTable).

    Parsed from file IEEE8021-CFM-MIB.my.txt
    Company: None
    Module: IEEE8021-CFM-MIB

    Description by cisco

    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 cdot1agMepHighestPrDefect
    variable in the notification:

    cdot1agMdIndex - Also the index of the MEP's
    Maintenance Domain table entry
    (cdot1agMdTable).
    cdot1agMaIndex - Also an index (with the MD table index)
    of the MEP's Maintenance Association
    table entry (cdot1agMaTable).
    cdot1agMepIdentifier - MEP Identifier and final index
    into the MEP table (cdot1agMepTable).

    Information by mibdepot

    cdot1agFaultAlarm NOTIFICATION-TYPE OBJECTS { cdot1agMepHighestPrDefect } 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 cdot1agMepHighestPrDefect variable in the notification: cdot1agMdIndex - Also the index of the MEP's Maintenance Domain table entry (cdot1agMdTable). cdot1agMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (cdot1agMaTable). cdot1agMepIdentifier - MEP Identifier and final index into the MEP table (cdot1agMepTable). " REFERENCE "802.1ag clause 12.14.7.7" ::= { cdot1agNotifications 1 }

    Information by cisco

    cdot1agFaultAlarm NOTIFICATION-TYPE OBJECTS { cdot1agMepHighestPrDefect } 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 cdot1agMepHighestPrDefect variable in the notification: cdot1agMdIndex - Also the index of the MEP's Maintenance Domain table entry (cdot1agMdTable). cdot1agMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association table entry (cdot1agMaTable). cdot1agMepIdentifier - MEP Identifier and final index into the MEP table (cdot1agMepTable). " REFERENCE "802.1ag clause 12.14.7.7" ::= { cdot1agNotifications 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.