Assigns a specific IP route to use a named LSP.
Note
To create a static IP route that does not use a specific named LSP as an mpls-next-hop, use the following command: configure iproute add [ipNetmask | ip_addr mask] gateway {metric} {multicast | multicast-only | unicast | unicast-only} {vr vrname} .ipaddress | Specified an IP address. |
netmask | Specifies an IP address/prefix length. |
ipNetmask | Specifies an IP address/prefix length. |
lsp_name | Specifies a named MPLS LSP to be used to reach the route. |
metric | Specifies a cost metric. |
multicast | Adds the specified route to the multicast routing table. |
multicast-only | Adds the specified route to the multicast routing table. This option is provided for backward compatibility with releases prior to ExtremeXOS Release 12.1. |
unicast | Adds the specified route to the unicast routing table. |
unicast-only | Adds the specified route to the unicast routing table. This option is provided for backward compatibility with releases prior to ExtremeXOS release 12.1. |
vrname | Specifies the virtual router to which the route is added. |
N/A.
This command assigns a named LSP to a specific IP route. Once configured, all IP traffic matching the configured route is forwarded over the specified LSP. For an RSVP-TE LSP, the correct label information is only associated with the route if the LSP is active. If the RSVP-TE LSP is disabled or is withdrawn, the label information is removed from the route table and the route entry is marked down. If multiple LSPs are added to a route and ECMP is enabled using route-sharing command, only one LSP is used to forward IP traffic.
Note
IP routes can only be assigned to named LSPs in the VR in which MPLS is configured to operate.The following command adds a static address to the routing table:
configure iproute add 10.1.1.0/24 lsp lsp598
This command was first available in ExtremeXOS 11.6.
This command is available only on the platforms that support MPLS as described in the Switch Engine 32.3 Feature License Requirements document.