OID reference

sleMplsTpOamMaintanceEntityInfoEntry

1.3.6.1.4.1.6296.101.16.17.2.1.1

Description

An entry in this table represents MPLS-TP maintenance entity. This entry represents the ME if the source and sink MEPs are defined. A ME is a p2p entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For P2P LSP, one MEG has one ME and this ME is associated two MEPs …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6296.101.16.17.2.1 (sleMplsTpOamMaintanceEntityInfoTable)
Node code
1
Node name
sleMplsTpOamMaintanceEntityInfoEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6296.101.16.17.2.1.1
URN notation
urn:oid:1.3.6.1.4.1.6296.101.16.17.2.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SleMplsTpOamMaintanceEntityInfoEntry
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.

sleMplsTpOamMaintanceEntityInfoEntry OBJECT-TYPE
			SYNTAX SleMplsTpOamMaintanceEntityInfoEntry
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
				"An entry in this table represents MPLS-TP maintenance
				entity. This entry represents the ME if the source and
				sink MEPs are defined.
				
				A ME is a p2p entity. One ME has two such MEPs.
				A MEG is a group of one or more MEs. One MEG can have
				two or more MEPs.
				
				For P2P LSP, one MEG has one ME and this ME is associated
				two MEPs (source and sink MEPs) within a MEG.
				Each sleMplsOamMeIndex value denotes the ME within a MEG.
				
				In case of unidirectional point-to-point transport paths,
				a single unidirectional Maintenance Entity is defined to
				monitor it and sleMplsOamMeServicePointer points to
				unidirectional point-to-point path.
				
				In case of associated bidirectional point-to-point
				transport paths, two independent unidirectional
				Maintenance Entities are defined to independently monitor
				each direction and each sleMplsOamMeServicePointer MIB
				object points to unique unidirectional transport path.
				This has implications for transactions that terminate at
				or query a MIP, as a return path from MIP to source MEP
				does not necessarily exist within the MEG.
				
				In case of co-routed bidirectional point-to-point
				transport paths, a single bidirectional Maintenance Entity
				
				
				
				is defined to monitor both directions congruently and
				sleMplsOamMeServicePointer MIB object points to co-routed
				bidirectional point-to-point transport path.
				
				In case of unidirectional point-to-multipoint transport
				paths, a single unidirectional Maintenance entity for each
				leaf is defined to monitor the transport path from the
				root to that leaf and each leaf has different transport
				path information in sleMplsOamMeServicePointer MIB object."
			INDEX { sleMplsTpOamMaintanceEntityInfoMeIndex, sleMplsTpOamMaintanceEntityInfoMpIndex }
			::= { sleMplsTpOamMaintanceEntityInfoTable 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 maintenance entity. This entry represents the ME if the source and sink MEPs are defined. A ME is a p2p entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For P2P LSP, one MEG has one ME and this ME is associated two MEPs (source and sink MEPs) within a MEG. Each sleMplsOamMeIndex value denotes the ME within a MEG. In case of unidirectional point-to-point transport paths, a single unidirectional Maintenance Entity is defined to monitor it and sleMplsOamMeServicePointer points to unidirectional point-to-point path. In case of associated bidirectional point-to-point transport paths, two independent unidirectional Maintenance Entities are defined to independently monitor each direction and each sleMplsOamMeServicePointer MIB object points to unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from MIP to source MEP does not necessarily exist within the MEG. In case of co-routed bidirectional point-to-point transport paths, a single bidirectional Maintenance Entity is defined to monitor both directions congruently and sleMplsOamMeServicePointer MIB object points to co-routed bidirectional point-to-point transport path. In case of unidirectional point-to-multipoint transport paths, a single unidirectional Maintenance entity for each leaf is defined to monitor the transport path from the root to that leaf and each leaf has different transport path information in sleMplsOamMeServicePointer MIB object.

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

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

Status in source: current.

Names: sleMplsTpOamMaintanceEntityInfoEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sleMplsTpOamMaintanceEntityInfoEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "SleMplsTpOamMaintanceEntityInfoEntry",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An entry in this table represents MPLS-TP maintenance entity. This entry represents the ME if the source and sink MEPs are defined. A ME is a p2p entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For P2P LSP, one MEG has one ME and this ME is associated two MEPs (source and sink MEPs) within a MEG. Each sleMplsOamMeIndex value denotes the ME within a MEG. In case of unidirectional point-to-point transport paths, a single unidirectional Maintenance Entity is defined to monitor it and sleMplsOamMeServicePointer points to unidirectional point-to-point path. In case of associated bidirectional point-to-point transport paths, two independent unidirectional Maintenance Entities are defined to independently monitor each direction and each sleMplsOamMeServicePointer MIB object points to unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from MIP to source MEP does not necessarily exist within the MEG. In case of co-routed bidirectional point-to-point transport paths, a single bidirectional Maintenance Entity is defined to monitor both directions congruently and sleMplsOamMeServicePointer MIB object points to co-routed bidirectional point-to-point transport path. In case of unidirectional point-to-multipoint transport paths, a single unidirectional Maintenance entity for each leaf is defined to monitor the transport path from the root to that leaf and each leaf has different transport path information in sleMplsOamMeServicePointer MIB object.\"",
    "INDEX",
    "{",
    "sleMplsTpOamMaintanceEntityInfoMeIndex",
    ",",
    "sleMplsTpOamMaintanceEntityInfoMpIndex",
    "}",
    "::=",
    "{",
    "sleMplsTpOamMaintanceEntityInfoTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "SleMplsTpOamMaintanceEntityInfoEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An entry in this table represents MPLS-TP maintenance entity. This entry represents the ME if the source and sink MEPs are defined. A ME is a p2p entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For P2P LSP, one MEG has one ME and this ME is associated two MEPs (source and sink MEPs) within a MEG. Each sleMplsOamMeIndex value denotes the ME within a MEG. In case of unidirectional point-to-point transport paths, a single unidirectional Maintenance Entity is defined to monitor it and sleMplsOamMeServicePointer points to unidirectional point-to-point path. In case of associated bidirectional point-to-point transport paths, two independent unidirectional Maintenance Entities are defined to independently monitor each direction and each sleMplsOamMeServicePointer MIB object points to unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from MIP to source MEP does not necessarily exist within the MEG. In case of co-routed bidirectional point-to-point transport paths, a single bidirectional Maintenance Entity is defined to monitor both directions congruently and sleMplsOamMeServicePointer MIB object points to co-routed bidirectional point-to-point transport path. In case of unidirectional point-to-multipoint transport paths, a single unidirectional Maintenance entity for each leaf is defined to monitor the transport path from the root to that leaf and each leaf has different transport path information in sleMplsOamMeServicePointer MIB object."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "sleMplsTpOamMaintanceEntityInfoMeIndex"
        ],
        [
          0,
          "sleMplsTpOamMaintanceEntityInfoMpIndex"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6296)

Lee Wonhee

Direct children (13)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6296.101.16.17.2.1.1.1 sleMplsTpOamMaintanceEntityInfoMeIndex00
1.3.6.1.4.1.6296.101.16.17.2.1.1.2 sleMplsTpOamMaintanceEntityInfoMpIndex00
1.3.6.1.4.1.6296.101.16.17.2.1.1.3 sleMplsOamMaintenanceEntityInfoMeName00
1.3.6.1.4.1.6296.101.16.17.2.1.1.4 sleMplsTpOamMaintanceEntityInfoMpType00
1.3.6.1.4.1.6296.101.16.17.2.1.1.5 sleMplsOamMaintenanceEntityInfoServiceTunnelName00
1.3.6.1.4.1.6296.101.16.17.2.1.1.6 sleMplsOamMaintenanceEntityInfoServiceVcId00
1.3.6.1.4.1.6296.101.16.17.2.1.1.7 sleMplsOamMaintenanceEntityInfoServiceDatalink00
1.3.6.1.4.1.6296.101.16.17.2.1.1.8 sleMplsTpOamMaintanceEntityInfoCcInterval00
1.3.6.1.4.1.6296.101.16.17.2.1.1.9 sleMplsTpOamMaintanceEntityInfoRemoteMpId00
1.3.6.1.4.1.6296.101.16.17.2.1.1.10 sleMplsTpOamMaintanceEntityInfoRemoteCc00
1.3.6.1.4.1.6296.101.16.17.2.1.1.11 sleMplsTpOamMaintanceEntityInfoRemoteIcc00
1.3.6.1.4.1.6296.101.16.17.2.1.1.12 sleMplsTpOamMaintanceEntityInfoRemoteMeg00
1.3.6.1.4.1.6296.101.16.17.2.1.1.13 sleMplsTpOamMaintanceEntityInfoRemoteMpdirection00