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)
• Setting aliases for the egress LER (optional)
• Setting a Class of Service (CoS) value for the LSP (optional)
• Allocating bandwidth to the LSP (optional)
• Configuring the setup and hold priority for the LSP (optional)
• Setting a metric for the LSP (optional)
• Including or excluding administrative groups from LSP calculations (optional)
• Limiting the number of hops the LSP can traverse (optional)
• Specifying a tie-breaker for selecting CSPF equal-cost paths (optional)
• Disabling the Record-Route function (optional)
• Disabling CSPF path calculations (optional)
• Configure Maximum Packet Size without fragmentation
• Enabling the LSP
• Disabling the LSP
• Generating Traps and Syslogs for LSPs