Follow-IGP metrics when next-hop MPLS is enabled

When you enable next-hop MPLS with the follow-IGP metrics option, BGP uses the native IGP metric for the BGP next hop resolved through IP route table, instead of the MPLS LSP metrics. BGP ignores all LSP metrics in the BGP decision process. However, the MPLS metric remains the same and is not overridden. Then the IGP cost of each next hop is compared, and only paths with the lowest values are considered for ECMP.

The advantage of using the IGP cost in a network is when this cost is significant throughout the local domain and all routing protocols, and you want to use it as a tie-breaker rather than use MPLS-specific metric value. This option works best when the MPLS LSP metrics follow the IGP cost, providing full advantage of both routing protocols and MPLS to select the best path. The advantage of doing this is that the BGP decision process on IGP cost is purely based on the IGP cost to a different next hop. MPLS tunnel is treated as a relay service.

Consider the following when enabling the use of IGP metrics instead of LSP metrics:



Mixed ECMP of LSP and native IGP paths is not supported. For a given prefix, if there are multiple BGP next hops with equal IGP cost, BGP prefers the next hop using the LSP path over the IGP path.