OID reference

sleMplsTpOamMegInfoEntry

1.3.6.1.4.1.6296.101.16.17.1.1.1

Description

An entry in this table represents MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM Framework. When a new entry is created with sleMplsTpOamMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP is LSP_ID and MEG_ID for PW is PW_…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6296.101.16.17.1.1 (sleMplsTpOamMegInfoTable)
Node code
1
Node name
sleMplsTpOamMegInfoEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6296.101.16.17.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.6296.101.16.17.1.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6296 101 16 17 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpOam(17) sleMplsTpOamMeg(1) sleMplsTpOamMegInfoTable(1) sleMplsTpOamMegInfoEntry(1)}
OID-IRI notation
  • /1/3/6/1/4/1/6296/101/16/17/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/6296/101/16/17/1/1/1
  • /ISO/3/6/1/4/1/6296/101/16/17/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/enterprise/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/enterprises/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/enterprises/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/enterprise/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/enterprise/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/enterprises/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/enterprises/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/vendor-objects/6296/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • /iso/org/dod/internet/private/vendor-objects/dasan/sleMgmt/sleMpls/sleMplsTpOam/sleMplsTpOamMeg/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry
  • Additional combinations skipped.

SNMP properties

Value type
SleMplsTpOamMegInfoEntry
Maximum access defined by MIB
read-only
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.

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

sleMplsTpOamMegInfoEntry OBJECT-TYPE
			SYNTAX SleMplsTpOamMegInfoEntry
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
				"An entry in this table represents MPLS-TP MEG.
				An entry can be created by a network administrator
				or by an SNMP agent as instructed by an MPLS-TP OAM
				Framework.
				
				When a new entry is created with
				sleMplsTpOamMegOperatorType set to ipCompatible (1),
				then as per [RFC6370] (MEG_ID for LSP is LSP_ID and
				MEG_ID for PW is PW_Path_ID), MEP_ID can be
				automatically formed.
				
				For co-routed bidirectional LSP, MEG_ID is
				A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
				Node_ID::Tunnel_Num}::LSP_Num.
				
				For associated bidirectional LSP, MEG_ID is A1-
				{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-
				{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
				
				For LSP, MEP_ID is formed using,
				Global_ID::Node_ID::Tunnel_Num::LSP_Num
				
				For PW, MEG_ID is formed using AGI::A1-
				{Global_ID::Node_ID::AC_ID}:: Z9-
				{Global_ID::Node_ID::AC_ID}.
				
				For PW, MEP_ID is formed using
				AGI::Global_ID::Node_ID::AC_ID
				
				MEP_ID is retrieved from the sleMplsTpOamMegServicePointer
				object based on the sleMplsTpOamMegServiceType value.
				ICC MEG_ID for LSP and PW is formed using the objects
				sleMplsTpOamMegIdIcc and sleMplsTpOamMegIdUmc.
				
				MEP_ID can be formed using MEG_ID::MEP_Index."
			REFERENCE
				"1. RFC 5860, Requirements for OAM in MPLS Transport
				Networks, May 2010.
				2. RFC 6371, Operations, Administration, and Maintenance
				Framework for MPLS-Based Transport Networks,
				September 2011.
				3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers.
				4. MPLS-TP Identifiers Following ITU-T Conventions
				[TP-ITUIDS]."
			INDEX { sleMplsTpOamMegInfoIndex }
			::= { sleMplsTpOamMegInfoTable 1 }

Meaning

Descriptions

1 unique

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

An entry in this table represents MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM Framework. When a new entry is created with sleMplsTpOamMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be automatically formed. For co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num. For associated bidirectional LSP, MEG_ID is A1- {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- {Global_ID::Node_ID::Tunnel_Num::LSP_Num} For LSP, MEP_ID is formed using, Global_ID::Node_ID::Tunnel_Num::LSP_Num For PW, MEG_ID is formed using AGI::A1- {Global_ID::Node_ID::AC_ID}:: Z9- {Global_ID::Node_ID::AC_ID}. For PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID MEP_ID is retrieved from the sleMplsTpOamMegServicePointer object based on the sleMplsTpOamMegServiceType value. ICC MEG_ID for LSP and PW is formed using the objects sleMplsTpOamMegIdIcc and sleMplsTpOamMegIdUmc. MEP_ID can be formed using MEG_ID::MEP_Index.

Sources for this description

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

Description 1

sleMplsTpOamMegInfoEntry · currentDASAN Networks MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: sleMplsTpOamMegInfoEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sleMplsTpOamMegInfoEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "SleMplsTpOamMegInfoEntry",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An entry in this table represents MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM Framework. When a new entry is created with sleMplsTpOamMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be automatically formed. For co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num. For associated bidirectional LSP, MEG_ID is A1- {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- {Global_ID::Node_ID::Tunnel_Num::LSP_Num} For LSP, MEP_ID is formed using, Global_ID::Node_ID::Tunnel_Num::LSP_Num For PW, MEG_ID is formed using AGI::A1- {Global_ID::Node_ID::AC_ID}:: Z9- {Global_ID::Node_ID::AC_ID}. For PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID MEP_ID is retrieved from the sleMplsTpOamMegServicePointer object based on the sleMplsTpOamMegServiceType value. ICC MEG_ID for LSP and PW is formed using the objects sleMplsTpOamMegIdIcc and sleMplsTpOamMegIdUmc. MEP_ID can be formed using MEG_ID::MEP_Index.\"",
    "REFERENCE",
    "\"1. RFC 5860, Requirements for OAM in MPLS Transport Networks, May 2010. 2. RFC 6371, Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks, September 2011. 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 4. MPLS-TP Identifiers Following ITU-T Conventions [TP-ITUIDS].\"",
    "INDEX",
    "{",
    "sleMplsTpOamMegInfoIndex",
    "}",
    "::=",
    "{",
    "sleMplsTpOamMegInfoTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "SleMplsTpOamMegInfoEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An entry in this table represents MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM Framework. When a new entry is created with sleMplsTpOamMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be automatically formed. For co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num. For associated bidirectional LSP, MEG_ID is A1- {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- {Global_ID::Node_ID::Tunnel_Num::LSP_Num} For LSP, MEP_ID is formed using, Global_ID::Node_ID::Tunnel_Num::LSP_Num For PW, MEG_ID is formed using AGI::A1- {Global_ID::Node_ID::AC_ID}:: Z9- {Global_ID::Node_ID::AC_ID}. For PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID MEP_ID is retrieved from the sleMplsTpOamMegServicePointer object based on the sleMplsTpOamMegServiceType value. ICC MEG_ID for LSP and PW is formed using the objects sleMplsTpOamMegIdIcc and sleMplsTpOamMegIdUmc. MEP_ID can be formed using MEG_ID::MEP_Index."
    ],
    [
      "REFERENCE",
      "1. RFC 5860, Requirements for OAM in MPLS Transport Networks, May 2010. 2. RFC 6371, Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks, September 2011. 3. RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers. 4. MPLS-TP Identifiers Following ITU-T Conventions [TP-ITUIDS]."
    ],
    null,
    [
      "INDEX",
      [
        [
          0,
          "sleMplsTpOamMegInfoIndex"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6296)

Lee Wonhee

Direct children (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6296.101.16.17.1.1.1.1 sleMplsTpOamMegInfoIndex00
1.3.6.1.4.1.6296.101.16.17.1.1.1.2 sleMplsTpOamMegInfoName00
1.3.6.1.4.1.6296.101.16.17.1.1.1.3 sleMplsTpOamMegInfoOperatorType00
1.3.6.1.4.1.6296.101.16.17.1.1.1.4 sleMplsTpOamMegInfoServiceType00
1.3.6.1.4.1.6296.101.16.17.1.1.1.5 sleMplsTpOamMegInfoMegLevel00
1.3.6.1.4.1.6296.101.16.17.1.1.1.6 sleMplsTpOamMegInfoOperStatus00