OID reference

optixMplsTpOamMod

1.3.6.1.4.1.2011.2.25.4.50.4

Description

This module is used to configure and manage the MPLS-TP OAM based on Y.1731. The MPLS-TP OAM is used to maintain and manage MPLS-TP networks, which caneffectivelydetect, identify, and locate faults of the MPLS-TP network and quickly perform a protection switching when the link is defective or faulty. The MPLS-TP netwo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2011.2.25.4.50 (optixProvisionPtn)
Node code
4
Node name
optixMplsTpOamMod
Numeric OID
1.3.6.1.4.1.2011.2.25.4.50.4
URN notation
urn:oid:1.3.6.1.4.1.2011.2.25.4.50.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2011 2 25 4 50 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) products(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) hwProducts(2) transmission(25) optixProvision(4) optixProvisionPtn(50) optixMplsTpOamMod(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/2/25/4/50/4
  • /ISO/Identified-Organization/6/1/4/1/2011/2/25/4/50/4
  • /ISO/3/6/1/4/1/2011/2/25/4/50/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/products/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/hwProducts/transmission/optixProvision/optixProvisionPtn/optixMplsTpOamMod
  • Additional combinations skipped.

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

optixMplsTpOamMod MODULE-IDENTITY
        LAST-UPDATED "201204170000Z"
        ORGANIZATION
            "Huawei Technologies co.,Ltd."
        CONTACT-INFO
            "R&D Building
            Huawei Technologies Co., Ltd.
            Bantian, Longgang District
            Shenzhen, P. R. China
            http://www.huawei.com
            Zip:518129
            E-mail:support@huawei.com"
        DESCRIPTION
            "This module is used to configure and manage the MPLS-TP OAM based on Y.1731. The MPLS-TP OAM is used to maintain and manage MPLS-TP networks, which caneffectivelydetect, identify, and locate faults of the MPLS-TP network and quickly perform a protection switching when the link is defective or faulty. The MPLS-TP network can be classified into three layers: section, LSP, and PW.The section layer is the server layer of the LSP layer which is the server layer of the PW layer. The PW layer is the server layer of the service layer. In other words, the LSP layer is the client layer of the section layer, the PW layer is the client layer of the LSP layer, and the service layer is the client layer of the PW layer.The MPLS-TP OAM is applied to the section, LSP, and PW layers of the MPLS-TP network to detect, identify, and locate faults."
        REVISION "201204170000Z"
        DESCRIPTION
            "Initial version of this MIB module"
        ::={ optixProvisionPtn 4 }

Meaning

Descriptions

1 unique

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

This module is used to configure and manage the MPLS-TP OAM based on Y.1731. The MPLS-TP OAM is used to maintain and manage MPLS-TP networks, which caneffectivelydetect, identify, and locate faults of the MPLS-TP network and quickly perform a protection switching when the link is defective or faulty. The MPLS-TP network can be classified into three layers: section, LSP, and PW.The section layer is the server layer of the LSP layer which is the server layer of the PW layer. The PW layer is the server layer of the service layer. In other words, the LSP layer is the client layer of the section layer, the PW layer is the client layer of the LSP layer, and the service layer is the client layer of the PW layer.The MPLS-TP OAM is applied to the section, LSP, and PW layers of the MPLS-TP network to detect, identify, and locate faults.

Sources for this description

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

Description 1

optixMplsTpOamMod · unspecifiedHuawei MIB copies (LibreNMS/Observium Community)1 source

Status in source: unspecified.

Names: optixMplsTpOamMod

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "optixMplsTpOamMod",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313230343137303030305a22"
    ],
    "ORGANIZATION",
    "\"Huawei Technologies co.,Ltd.\"",
    "CONTACT-INFO",
    "\"R&D Building Huawei Technologies Co., Ltd. Bantian, Longgang District Shenzhen, P. R. China http://www.huawei.com Zip:518129 E-mail:support@huawei.com\"",
    "DESCRIPTION",
    "\"This module is used to configure and manage the MPLS-TP OAM based on Y.1731. The MPLS-TP OAM is used to maintain and manage MPLS-TP networks, which caneffectivelydetect, identify, and locate faults of the MPLS-TP network and quickly perform a protection switching when the link is defective or faulty. The MPLS-TP network can be classified into three layers: section, LSP, and PW.The section layer is the server layer of the LSP layer which is the server layer of the PW layer. The PW layer is the server layer of the service layer. In other words, the LSP layer is the client layer of the section layer, the PW layer is the client layer of the LSP layer, and the service layer is the client layer of the PW layer.The MPLS-TP OAM is applied to the section, LSP, and PW layers of the MPLS-TP network to detect, identify, and locate faults.\"",
    "REVISION",
    [
      "literal",
      "223230313230343137303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module\"",
    "::=",
    "{",
    "optixProvisionPtn",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201204170000Z"
    ],
    [
      "ORGANIZATION",
      "Huawei Technologies co.,Ltd."
    ],
    [
      "CONTACT-INFO",
      "R&D Building Huawei Technologies Co., Ltd. Bantian, Longgang District Shenzhen, P. R. China http://www.huawei.com Zip:518129 E-mail:support@huawei.com"
    ],
    [
      "DESCRIPTION",
      "This module is used to configure and manage the MPLS-TP OAM based on Y.1731. The MPLS-TP OAM is used to maintain and manage MPLS-TP networks, which caneffectivelydetect, identify, and locate faults of the MPLS-TP network and quickly perform a protection switching when the link is defective or faulty. The MPLS-TP network can be classified into three layers: section, LSP, and PW.The section layer is the server layer of the LSP layer which is the server layer of the PW layer. The PW layer is the server layer of the service layer. In other words, the LSP layer is the client layer of the section layer, the PW layer is the client layer of the LSP layer, and the service layer is the client layer of the PW layer.The MPLS-TP OAM is applied to the section, LSP, and PW layers of the MPLS-TP network to detect, identify, and locate faults."
    ],
    [
      "Revisions",
      [
        [
          "201204170000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module"
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.2.25.4.50.4.1 optixMplsTpOamObject24230
1.3.6.1.4.1.2011.2.25.4.50.4.2 optixMplsTpOamTrap240
1.3.6.1.4.1.2011.2.25.4.50.4.3 optixMplsTpOamGroup11

Siblings (40)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.2.25.4.50.1 optixAtmImaMod2178
1.3.6.1.4.1.2011.2.25.4.50.2 optixCesMod190
1.3.6.1.4.1.2011.2.25.4.50.3 optixEthSrvMod2701
1.3.6.1.4.1.2011.2.25.4.50.5 optixPWApsMod235
1.3.6.1.4.1.2011.2.25.4.50.6 optixPWMod3253
1.3.6.1.4.1.2011.2.25.4.50.7 optixPWOamMod120
1.3.6.1.4.1.2011.2.25.4.50.8 optixTunnelApsMod231
1.3.6.1.4.1.2011.2.25.4.50.9 optixTunnelMod393
1.3.6.1.4.1.2011.2.25.4.50.10 optixTunnelOamMod122
1.3.6.1.4.1.2011.2.25.4.50.11 optixPktDcn239
1.3.6.1.4.1.2011.2.25.4.50.12 optixQinqLink120
1.3.6.1.4.1.2011.2.25.4.50.13 optixPktptpclock4154
1.3.6.1.4.1.2011.2.25.4.50.14 optixPktQosWred118
1.3.6.1.4.1.2011.2.25.4.50.15 optixCfmoam1128
1.3.6.1.4.1.2011.2.25.4.50.16 optixPktLinkSearch116
1.3.6.1.4.1.2011.2.25.4.50.17 optixEfmoam126
1.3.6.1.4.1.2011.2.25.4.50.18 optixEtyPort19
1.3.6.1.4.1.2011.2.25.4.50.19 optixL2Lag263
1.3.6.1.4.1.2011.2.25.4.50.20 optixL2Lpt1123
1.3.6.1.4.1.2011.2.25.4.50.21 optixPktSynClock13
1.3.6.1.4.1.2011.2.25.4.50.22 optixPktMirror130
1.3.6.1.4.1.2011.2.25.4.50.23 optixPktArp225
1.3.6.1.4.1.2011.2.25.4.50.24 optixPktCesAcr164
1.3.6.1.4.1.2011.2.25.4.50.25 optixPktCosMap249
1.3.6.1.4.1.2011.2.25.4.50.26 optixPktErps173
1.3.6.1.4.1.2011.2.25.4.50.27 optixPktLLDP262
1.3.6.1.4.1.2011.2.25.4.50.28 optixPktLmsp244
1.3.6.1.4.1.2011.2.25.4.50.29 optixPktPpp113
1.3.6.1.4.1.2011.2.25.4.50.30 optixPktQosClassifier241
1.3.6.1.4.1.2011.2.25.4.50.31 optixPktQosPoint171
1.3.6.1.4.1.2011.2.25.4.50.32 optixPktQosPolicy191
1.3.6.1.4.1.2011.2.25.4.50.33 optixPktSdhAlmClksw117
1.3.6.1.4.1.2011.2.25.4.50.34 optixPktSdhOh149
1.3.6.1.4.1.2011.2.25.4.50.35 optixpktSYSsyn233
1.3.6.1.4.1.2011.2.25.4.50.36 optixSEPMod198
1.3.6.1.4.1.2011.2.25.4.50.37 optixPktSsm15
1.3.6.1.4.1.2011.2.25.4.50.38 optixL2Igmp1136
1.3.6.1.4.1.2011.2.25.4.50.40 optixPktMstp199
1.3.6.1.4.1.2011.2.25.4.50.52 optixPktPort1397
1.3.6.1.4.1.2011.2.25.4.50.53 optixPktIPPING180