|
|
Description:
|
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 }
|
|
|
|
