Status in source: current.
Names: mplsTunnelTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsTunnelTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"MplsTunnelEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsTunnelIngressLSRId and mplsTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router.\"",
"::=",
"{",
"mplsTeObjects",
"2",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"MplsTunnelEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsTunnelIngressLSRId and mplsTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router."
],
null,
null,
null,
null
]
}