Status in source: obsolete.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tBgpInstanceIgpShortcut",
"OBJECT-TYPE",
"SYNTAX",
"BITS",
"{",
"te",
"(",
"0",
")",
",",
"ldp",
"(",
"1",
")",
",",
"ip",
"(",
"2",
")",
",",
"mpls",
"(",
"3",
")",
",",
"mpls-bgp",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"obsolete",
"DESCRIPTION",
"\"The bits of tBgpInstanceIgpShortcut identify the Layer-2 tunneling mechanisms used for IGP shortcuts. If a bit is set, the corresponding tunneling mechanism will be used to resolve paths to BGP next-hops. The tunneling mechanisms represented by each bit are: te(0) - RSVP Traffic Engineering ldp(1) - LDP /32 Route Forwarding Equivalence Class (FEC) ip(2) - IP (IP-in-IP or GRE) mpls(3)- MPLS mpls-bgp(4)- MPLS with BGP label-route tunnel eligibility Evaluation of tunnel preference is based on the following order, in descending priority: 1. Traffic Engineered Shortcut (RSVP-TE) 2. LDP /32 Route FEC Shortcut 3. IP Shortcut (IP-in-IP or GRE) 4. Actual IGP Next-Hop. The 'mpls' option instructs BGP to first attempt to resolve the BGP next-hop to an RSVP LSP. If no RSVP LSP exists or the existing ones are down, BGP automatically searches for the LDP LSP with a FEC prefix corresponding to the same /32 prefix in the tunnel table and resolves the BGP next-hop to it. The 'mpls-bgp' option allows BGP to resolve the BGP next-hop using BGP tunnels in TTM, but the order of preference (which cannot be changed) is RSVP then LDP then BGP. This object was obsoleted in release 13.0.\"",
"DEFVAL",
"{",
"{",
"}",
"}",
"::=",
"{",
"tBgpInstanceEntry",
"56",
"}"
],
"syntax_tree": [
[
"BITS",
[
[
"te",
0
],
[
"ldp",
1
],
[
"ip",
2
],
[
"mpls",
3
],
[
"mpls-bgp",
4
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"obsolete"
],
[
"DESCRIPTION",
"The bits of tBgpInstanceIgpShortcut identify the Layer-2 tunneling mechanisms used for IGP shortcuts. If a bit is set, the corresponding tunneling mechanism will be used to resolve paths to BGP next-hops. The tunneling mechanisms represented by each bit are: te(0) - RSVP Traffic Engineering ldp(1) - LDP /32 Route Forwarding Equivalence Class (FEC) ip(2) - IP (IP-in-IP or GRE) mpls(3)- MPLS mpls-bgp(4)- MPLS with BGP label-route tunnel eligibility Evaluation of tunnel preference is based on the following order, in descending priority: 1. Traffic Engineered Shortcut (RSVP-TE) 2. LDP /32 Route FEC Shortcut 3. IP Shortcut (IP-in-IP or GRE) 4. Actual IGP Next-Hop. The 'mpls' option instructs BGP to first attempt to resolve the BGP next-hop to an RSVP LSP. If no RSVP LSP exists or the existing ones are down, BGP automatically searches for the LDP LSP with a FEC prefix corresponding to the same /32 prefix in the tunnel table and resolves the BGP next-hop to it. The 'mpls-bgp' option allows BGP to resolve the BGP next-hop using BGP tunnels in TTM, but the order of preference (which cannot be changed) is RSVP then LDP then BGP. This object was obsoleted in release 13.0."
],
null,
null,
null,
[
"DEFVAL",
[]
]
]
}