Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 614)

590 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
LDP route injection
5
Because global next-hop MPLS remains enabled and the LSP metrics are no longer a factor, all the
LSPs are displayed in the routing table because BGP considers them to have equal cost.
Brocade(config-bgp)# no next-hop-mpls compare-lsp-metric
Brocade(config-bgp)# show ip route
Total number of IP routes: 5
Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric
ISIS Codes - L1:Level-1 L2:Level-2
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link
Destination Gateway Port Cost Type Uptime
1 10.1.1.1/32 DIRECT loopback 1 0/0 D 12m58s
2 10.2.3.3/32 DIRECT loopback 2 0/0 D 12m58s
3 10.5.5.5/32 10.1.1.10 eth 1/1 1/1 S 12m47s
4 10.8.8.1/32 10.1.1.2 lsp to2 20/0 B 0m1s
10.8.8.1/32 10.1.1.2 lsp to22 20/0 B 0m1s
10.8.8.1/32 10.10.1.2 lsp to2_sec 20/0 B 0m1s
5 10.8.8.2/32 10.1.1.2 lsp to2 20/0 B 0m1s
10.8.8.2/32 10.1.1.2 lsp to22 20/0 B 0m1s
10.8.8.2/32 10.10.1.2 lsp to2_sec 20/0 B 0m1s
Syntax: [no] next-hop-mpls [compare-lsp-metric]
Disabling global next-hop MPLS
Disable global next-hop MPLS and check the RTM to see that native IP-forwarding is restored.
Brocade(config-bgp)# no next-hop-mpls
Brocade(config-bgp)# show ip route
Total number of IP routes: 5
Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric
ISIS Codes - L1:Level-1 L2:Level-2
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link
Destination Gateway Port Cost Type Uptime
1 10.1.1.1/32 DIRECT loopback 1 0/0 D 9m46s
2 10.2.3.3/32 DIRECT loopback 2 0/0 D 9m46s
3 10.5.5.5/32 10.1.1.10 eth 1/1 1/1 S 9m35s
4 10.8.8.1/32 10.1.1.2 eth 1/1 20/0 B 0m1s
10.8.8.1/32 10.10.1.2 eth 1/2 20/0 B 0m1s
5 10.8.8.2/32 10.1.1.2 eth 1/1 20/0 B 0m1s
10.8.8.2/32 10.10.1.2 eth 1/2 20/0 B 0m1s
Syntax: [no] next-hop-mpls [compare-lsp-metric]
LDP route injection
An MPLS edge router is typically connected to a customer network that is not configured for MPLS.
When the edge router is then connected to the MPLS core through LSP tunnels that have been
created by LDP, only routes to the loopback address of the edge router are available for routing
through the LSP tunnels. In practice, this means that routes to and from the customer network are
unavailable to the MPLS network.