OID reference

tmnxDot1agCfmMepFcltyInstance

1.3.6.1.4.1.6527.3.1.2.52.9.3

Description

The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.2.52.9 (tmnxDot1agCfmNotificationObjs)
Node code
3
Node name
tmnxDot1agCfmMepFcltyInstance
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6527.3.1.2.52.9.3
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.2.52.9.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 2 52 9 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxDot1agMIBObjs(52) tmnxDot1agCfmNotificationObjs(9) tmnxDot1agCfmMepFcltyInstance(3)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/2/52/9/3
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/2/52/9/3
  • /ISO/3/6/1/4/1/6527/3/1/2/52/9/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxDot1agMIBObjs/tmnxDot1agCfmNotificationObjs/tmnxDot1agCfmMepFcltyInstance

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
accessible-for-notify
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

tmnxDot1agCfmMepFcltyInstance · current

tmnxDot1agCfmMepFcltyInstance    OBJECT-TYPE
    SYNTAX      DisplayString
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "The value of tmnxDot1agCfmMepFcltyInstance indicates the specific
         facility instance that a facility MEP has affected via a raised
         or cleared event.

         This value is used in combination with its tmnxDot1agCfmMepFcltyType.

         The possible facility types and instance forms are described in the
         following table:

               Facility Type         |  Facility Instance
             ---------------------------------------------
               port                  |  slot/mda/port
               lag                   |  lag-id
               networkInterface      |  interface-name 
               qinqPortTunnelSap     |  sap-id
               qinqLagTunnelSap      |  sap-id
    
         The combined value will appear as in the following examples:
            port 7/2/2
            lag 1
            networkInterface test 
            qinqPortTunnelSap 2/2/2:100.*
            qinqLagTunnelSap lag-1:100.*

          When a facility fault occurs on a QinQ port or lag, the sap executing
          the CFM functional test, the sap will be included as part of the
          event log message.  However, QinQ facility tunnel MEPs on the sap are
          only the detection point for the defect / clear condition.  The QinQ
          facility tunnel is port or lag based and a representative outer tag. 
         "
    ::= { tmnxDot1agCfmNotificationObjs 3 }

tmnxDot1agCfmMepFcltyInstance · current

tmnxDot1agCfmMepFcltyInstance    OBJECT-TYPE
    SYNTAX      DisplayString
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "The value of tmnxDot1agCfmMepFcltyInstance indicates the specific
         facility instance that a facility MEP has affected via a raised or
         cleared event.

         This value is used in combination with its tmnxDot1agCfmMepFcltyType.

         The possible facility types and instance forms are described in the
         following table:

               Facility Type         |  Facility Instance
             ---------------------------------------------
               port                  |  slot/mda/port
               lag                   |  lag-id
               networkInterface      |  interface name
               qinqPortTunnelSap     |  sap-id
               qinqLagTunnelSap      |  sap-id

         The combined value will appear as in the following examples:
            port 7/2/2
            lag 1
            networkInterface test
            qinqPortTunnelSap 2/2/2:100.*
            qinqLagTunnelSap lag-1:100.*

          When a facility fault occurs on a QinQ port or lag, the sap executing
          the CFM functional test, the sap will be included as part of the
          event log message.  However, QinQ facility tunnel MEPs on the sap are
          only the detection point for the defect / clear condition.  The QinQ
          facility tunnel is port or lag based and a representative outer tag."
    ::= { tmnxDot1agCfmNotificationObjs 3 }

Meaning

Descriptions

2 unique

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

Description 1

The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface-name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag.

Sources for this description

Netdisco MIB archive copies

See 1 matching source record

Description 2

The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag.

Sources for this description

Nokia networking MIB copies (LibreNMS/Observium Community)

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 1Netdisco MIB archive copies1 record · 1 source

Description 1

tmnxDot1agCfmMepFcltyInstance · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: tmnxDot1agCfmMepFcltyInstance

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxDot1agCfmMepFcltyInstance",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "accessible-for-notify",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface-name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag. \"",
    "::=",
    "{",
    "tmnxDot1agCfmNotificationObjs",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "accessible-for-notify"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface-name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Netdisco MIB archive copies · Publisher's source file: timetra-ieee8021-cfm-mib.mib

    Vendor MIB copy from the Netdisco archive.

    Module: TIMETRA-IEEE8021-CFM-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'LLDP-MIB': ['LldpChassisIdSubtype'], 'SNMPv2-TC': ['MacAddress', 'RowStatus', 'TruthValue', 'DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'Unsigned32', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Counter32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'TIMETRA-TC-MIB': ['TmnxServId', 'TmnxEnabledDisabled', 'TItemDescription', 'TNamedItem', 'TmnxCreateOrigin'], 'IEEE8021-CFM-MIB': ['dot1agCfmDefaultMdEntry', 'dot1agCfmMaNetEntry', 'dot1agCfmMaCompEntry', 'dot1agCfmMaMepListEntry', 'dot1agCfmMdIndex', 'dot1agCfmMaIndex', 'dot1agCfmMepIdentifier', 'Dot1agCfmMDLevel', 'Dot1agCfmMpDirection', 'Dot1agCfmMepIdOrZero', 'Dot1agCfmMepId', 'VlanIdOrNone', 'Dot1agCfmIdPermission', 'dot1agCfmMepEntry', 'dot1agCfmMepDbEntry', 'dot1agCfmMepTransmitLbmDestMacAddress', 'dot1agCfmMepTransmitLtmSeqNumber', 'dot1agCfmMdEntry', 'Dot1agCfmLowestAlarmPri'], 'TIMETRA-SERV-MIB': ['SdpId'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRObjs', 'tmnxSRConfs', 'tmnxSRNotifyPrefix']}
    · Download timetra-ieee8021-cfm-mib.mib
Records for description 2Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

tmnxDot1agCfmMepFcltyInstance · currentNokia networking MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: tmnxDot1agCfmMepFcltyInstance

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxDot1agCfmMepFcltyInstance",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "accessible-for-notify",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag.\"",
    "::=",
    "{",
    "tmnxDot1agCfmNotificationObjs",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "accessible-for-notify"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxDot1agCfmMepFcltyInstance indicates the specific facility instance that a facility MEP has affected via a raised or cleared event. This value is used in combination with its tmnxDot1agCfmMepFcltyType. The possible facility types and instance forms are described in the following table: Facility Type | Facility Instance --------------------------------------------- port | slot/mda/port lag | lag-id networkInterface | interface name qinqPortTunnelSap | sap-id qinqLagTunnelSap | sap-id The combined value will appear as in the following examples: port 7/2/2 lag 1 networkInterface test qinqPortTunnelSap 2/2/2:100.* qinqLagTunnelSap lag-1:100.* When a facility fault occurs on a QinQ port or lag, the sap executing the CFM functional test, the sap will be included as part of the event log message. However, QinQ facility tunnel MEPs on the sap are only the detection point for the defect / clear condition. The QinQ facility tunnel is port or lag based and a representative outer tag."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Nokia networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Nokia support.

    Module: TIMETRA-IEEE8021-CFM-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'LLDP-MIB': ['LldpChassisIdSubtype'], 'SNMPv2-TC': ['DateAndTime', 'DisplayString', 'MacAddress', 'RowStatus', 'TEXTUAL-CONVENTION', 'TimeInterval', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Gauge32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'TIMETRA-TC-MIB': ['TFCSet', 'TItemDescription', 'TLNamedItem', 'TLNamedItemOrEmpty', 'TNamedItem', 'TmnxCreateOrigin', 'TmnxEnabledDisabled', 'TmnxServId'], 'IEEE8021-CFM-MIB': ['Dot1agCfmInterfaceStatus', 'Dot1agCfmLowestAlarmPri', 'Dot1agCfmMDLevel', 'Dot1agCfmMaintAssocName', 'Dot1agCfmMaintDomainNameType', 'Dot1agCfmMepId', 'Dot1agCfmMepIdOrZero', 'Dot1agCfmMpDirection', 'Dot1agCfmPortStatus', 'VlanId', 'VlanIdOrNone', 'dot1agCfmDefaultMdEntry', 'dot1agCfmMaCompEntry', 'dot1agCfmMaIndex', 'dot1agCfmMaMepListEntry', 'dot1agCfmMaNetEntry', 'dot1agCfmMdEntry', 'dot1agCfmMdIndex', 'dot1agCfmMepDbEntry', 'dot1agCfmMepEntry', 'dot1agCfmMepIdentifier', 'dot1agCfmMepTransmitLbmDestMacAddress', 'dot1agCfmMepTransmitLtmSeqNumber'], 'TIMETRA-SERV-MIB': ['SdpId'], 'TIMETRA-GLOBAL-MIB': ['timetraSRMIBModules', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'tmnxSRObjs']}
    · Download TIMETRA-IEEE8021-CFM-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Marcelo Mourier

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Jason Sterne

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.2.52.9.1 tmnxDot1agCfmNotifySvcId00
1.3.6.1.4.1.6527.3.1.2.52.9.2 tmnxDot1agCfmMepFcltyType00