sleMplsTpOamMegInfoEntry

SLE-MPLS-TP-OAM-MIB · .1.3.6.1.4.1.6296.101.16.17.1.1.1

Object

row
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.

Context

MIB
SLE-MPLS-TP-OAM-MIB
OID
.1.3.6.1.4.1.6296.101.16.17.1.1.1
Type
row
Status
current
Parent
sleMplsTpOamMegInfoTable
Table
sleMplsTpOamMegInfoTable
Children
6

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Child Objects
Indexes