MPLS-TE-EXT-STD-MIB Table View

This table allows the operator to map a node or
LSR identifier (IP-compatible [Global_ID::Node_ID] or
ICC-based [ICC_Operator_ID::Node_ID]) 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_ID::Node_ID of size 8 bytes and
ICC_Operator_ID::Node_ID of size 12 bytes, there exists a
need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID
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 operator to retrieve
the local identifier for a given Global_ID::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.  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 mplsTunnelExtNodeConfigTable.

This read-only table allows the operator to retrieve
the local identifier for a given ICC_Operator_ID::Node_ID
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.  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 mplsTunnelExtNodeConfigTable.

This table represents extensions to mplsTunnelTable
in order to support MPLS-TP Tunnels.
          
As per MPLS-TP Identifiers (RFC 6370), 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, and LSP_Num is mapped with
mplsTunnelInstance.
          
Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and
Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID
are maintained in the mplsTunnelExtNodeConfigTable.
mplsTunnelExtNodeConfigLocalId is used to create an entry
in mplsTunnelTable.