Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 150)

126 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Setting up signaled LSPs
1
Modifying a path
Once the user has created a path, the user can insert or delete nodes from it. For example, to
delete a node from the sf_to_sj path defined above.
Brocade(config-mpls)# path sf_to_sj
Brocade(config-mpls-path)# delete loose 10.1.1.1
Brocade(config-mpls-path)# exit
Syntax: [no] delete strict | loose ip address
To insert a node into a path.
Brocade(config-mpls)# path sf_to_sj
Brocade(config-mpls-path)# insert strict 10.150.1.1 before 10.150.1.2
Brocade(config-mpls-path)# exit
Syntax: [no] insert strict | loose ip address before ip address
The insert command allows a new node to be inserted in front of an existing node within the path.
In this example, the insert strict 10.150.1.1 before 10.150.1.2 command assumes that 10.150.1.2
is already in the path and inserts 10.150.1.1 before it.
NOTE
When the user modifies a path, the changes are not carried over to active LSPs that see the path
until the LSPs are deactivated and reactivated. For example, path sj_to_sf may be used by an LSP
called lsp1. After lsp1 has been activated, any changes to path sj_to_sf do not cause the route
followed by lsp1 to be modified. To get the LSP to use the modified path, the user must deactivate
and then reactivate lsp1.
Deleting a path
To delete an entire path from the LSRs configuration, enter a command such as the following.
Brocade(config-mpls)# no path sf_to_sj
Syntax: [no] path path name
Configuring signaled LSP parameters
Once the user has configured a path, the user can configure signaled LSPs that see it. An LSPs
configuration can specify not only the path that label-switched packets follow in a network, but also
the characteristics of the path, the resources allocated along the path, and actions applied to the
packets by the ingress or egress LERs.
The user can perform the following tasks when configuring a signaled LSP:
• Performing a Commit for an LSP
• Creating the LSP
• Specifying an egress LER for the LSP
• Specifying a primary path for the LSP (optional)
• Configuring secondary or hot-standby paths for the LSP (optional)