Moving inet.3 table into inet.0

It’s possible to take all of the LSP next hops from the inet.3 table and either move or share them with the inet.0 table. There are several options that allow BGP and IGP destinations to use the LSPs as next hops and/or whether the routes are moved or shared.

The ‘bgp’ option is the default as this maintains BGP next hop reachability for MPLS LSPs in inet.3. The ‘bgp-igp’ option moves routes to inet.0, the ‘bgp-igp-both-ribs’ option shares the LSPs with both tables.

protocols {
     mpls {
          traffic-engineering {
               bgp;
          }
     }

}

The ‘mpls-forwarding’ option which maintains copies in both tables for IGP, BGP and VPN route resolution but places the LSP next hops into inet.0 with a hidden lower route preference than the IGP protocols. The LSP next hop is used in the forwarding table but it’s not elected over IGP routes in the route table. This allows policy based routing to function based on next-hop IGP routes being active in the routing table and not overshadowed by the LSP next hops.

The active next hop IGP entry is displayed with an ‘@’ sign and the next hop LSP forwarding entry is shown with a ‘#’

protocols {
     mpls {
          traffic-engineering {
               mpls-forwarding;
          }
     }
}

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s