Resolve an IP route with an LSP and install into inet.0

By default the Junos software installs LSPs into the inet.3 routing table for next hop resolution of MPLS VPN routes. MP-BGP will always look into inet.3 by default (if it doesn’t see a route it will look into inet.0) and uses LSPs as the next hop for the purpose of PE to PE transport.

In addition to the default behaviour Junos can also manually add static routes into inet.3 that use LSPs as a next hop. The install <prefix> feature can be configured within the MPLS label-switched-path hierarchy to install a static IP route into the inet.3 table and resolve that route using the LSP.

The purpose of this feature is to allow certain traffic to be steered into an LSP for subnets or hosts that are not reachable via an MPLS VPN or need to be reachable via the global routing tables.

In addition to the above there’s also the option to install the static route into inet.0, which is configured using the active knob. The purpose of this feature is to allow IGPs (that operate in inet.0) to access the route with the potential to scale to larger amounts of IP routes that can be transported over a next hop LSP.

The following configuration depicts the addition of the active knob which moves the LSP resolved route into inet.0.

Removing the active knob maintains the route in the inet.3 table only.

protocols {
mpls {
label-switched-path {
R1-to-R4 {
to 172.25.0.4;
install 172.26.0.20 active;
}
}
}
}

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