Supported Platforms
Configuring the Ingress and Egress Router Addresses for LSPs
The following sections describe how to specify the addresses of an LSP’s ingress and egress routers:
Configuring the Ingress Router Address for LSPs
The local router always is considered to be the ingress router, which is the beginning of the LSP. The software automatically determines the proper outgoing interface and IP address to use to reach the next router in an LSP.
By default, the router ID is chosen as the address of the ingress router. To override the automatic selection of the source address, specify a source address in the from statement:
You can include this statement at the following hierarchy levels:
- [edit protocols mpls label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name]
The outgoing interface used by the LSP is not affected by the source address that you configure.
Configuring the Egress Router Address for LSPs
When configuring an LSP, you must specify the address of the egress router by including the to statement:
You can include this statement at the following hierarchy levels:
- [edit protocols mpls label-switched-path lsp-name]
- [edit protocols mpls static-label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name]
When you are setting up a signaled LSP, the to statement is the only required statement. All other statements are optional.
After the LSP is established, the address of the egress router is installed as a host route in the routing table. This route can then be used by BGP to forward traffic.
To have the software send BGP traffic over an LSP, the address of the egress router is the same as the address of the BGP next hop. You can specify the egress router’s address as any one of the router’s interface addresses or as the BGP router ID. If you specify a different address, even if the address is on the same router, BGP traffic is not sent over the LSP.
To determine the address of the BGP next hop, use the show route detail command. To determine the destination address of an LSP, use the show mpls lsp command. To determine whether a route has gone through an LSP, use the show route or show route forwarding-table command. In the output of these last two commands, the label-switched-path or push keyword included with the route indicates it has passed through an LSP. Also, use the traceroute command to trace the actual path to which the route leads. This is another indication whether a route has passed through an LSP.
You also can manipulate the address of the BGP next hop by defining a BGP import policy filter that sets the route’s next-hop address.
Preventing the Addition of Egress Router Addresses to Routing Tables
You must configure an address using the to statement for all 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 Constrained Shortest Path First (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 protocols mpls static-label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name]
- [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name]
