CISCO-IETF-MPLS-TE-EXT-STD-03-MIB Table View

This table allows the administrator to map a node or
LSR Identifier (IP compatible [Global_Node_ID] or ICC)
with a local identifier.
          
          
This table is created to reuse the existing
mplsTunnelTable for MPLS based transport network
tunnels also.
Since the MPLS tunnel's Ingress/Egress LSR identifiers'
size (Unsigned32) value is not compatible for
MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and
ICC of size 6 bytes, there exists a need to map the
Global_Node_ID or ICC with the local identifier of size
4 bytes (Unsigned32) value in order
to index (Ingress/Egress LSR identifier)
the existing mplsTunnelTable.

This read-only table allows the administrator to retrieve
the local identifier for a given Global_Node_ID in an IP
compatible operator environment.
          
This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR identifier
(Local Identifier) from Src-Global_Node_ID
or Dst-Global_Node_ID and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
          
This table returns nothing when the associated entry
is not defined in mplsNodeConfigTable.

This read-only table allows the administrator to retrieve
the local identifier for a given ICC operator in an ICC
operator environment.
          
This table MAY be used in on-demand and/or proactive
OAM operations to get the Ingress/Egress LSR
identifier (Local Identifier) from Src-ICC
or Dst-ICC and the Ingress and Egress LSR
identifiers are used to retrieve the tunnel entry.
This table returns nothing when the associated entry
is not defined in mplsNodeConfigTable.

This table represents MPLS-TP specific extensions to
mplsTunnelTable.
          
As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based
co-routed bidirectional tunnel,
          
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num
          
LSP_ID for IP based associated bidirectional tunnel,
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
          
mplsTunnelTable is reused for forming the LSP_ID
as follows,
          
Source Tunnel_Num is mapped with mplsTunnelIndex,
Source Node_ID is mapped with
mplsTunnelIngressLSRId, Destination Node_ID is
mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
mplsTunnelInstance.
          
Source Global_Node_ID and/or ICC and Destination
Global_Node_ID and/or ICC are maintained in the
mplsNodeConfigTable and mplsNodeConfigLocalId is
used to create an entry in mplsTunnelTable.

This table extends the mplsTunnelTable to provide
per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel.  It can be seen as
supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable.
          
For links that do not transport packets, these packet
counters cannot be maintained.  For such links, attempts
to read the objects in this table will return
noSuchInstance.