Preventing the Addition of Egress Router Addresses to Routing Tables

You must configure an address using the to statement for all RSVP LSPs. This address is always installed as a /32 prefix in the inet.3 or inet.0 routing tables. You can prevent the egress router address configured using the to statement from being added to the inet.3 and inet.0 routing tables by including the no-install-to-address statement.

Some reasons not to install the to statement address in the inet.3 and inet.0 routing tables include the following:

• Allow CSPF RSVP LSPs to be mapped to traffic intended for secondary loopback addresses. If you configure an RSVP tunnel, including the no-install-to-address statement, and then configure an install pfx/ <active> policy later, you can do the following:
  • Verify that the LSP was set up correctly without impacting traffic.
  • Map traffic to the LSP in incremental steps.
  • Map traffic to the destination loopback address (the BGP next hop) by removing the no-install-to-address statement once troubleshooting is complete.
• Prevent CCC connections from losing IP traffic. When an LSP determines that it does not belong to a connection, it installs the address specified with the to statement in the inet.3 routing table. IP traffic is then forwarded to the CCC remote endpoint, which can cause some types of PICs to fail.

To prevent the egress router address configured using the to statement from being added to the inet.3 and inet.0 routing tables, include the no-install-to-address statement:

You can include this statement at the following hierarchy levels:

• [edit protocols mpls label-switched-path lsp-name]
• [edit logical-routers logical-router-name protocols mpls label-switched-path lsp-name]