[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Bypass LSPs

You can configure specific bandwidth and path constraints for a bypass LSP. You can also individually configure each bypass LSP generated when you enable multiple bypass LSPs. If you do not configure the bypass LSPs individually, they all share the same path and bandwidth constraints (if any).

If you specify the bandwidth, hop-limit, and path statements for the bypass LSP, these values take precedence over the values configured at the [edit protocols rsvp interface interface-name link-protection] hierarchy level. The other attributes (subscription, no-node-protection, and optimize-timer) are inherited from the general constraints.

To configure a bypass LSP, include the bypass statement:




bypass bypass-name {

bandwidth bps;

class-of-service  cos-value;

hop-limit number;

no-cspf;

path address <strict | loose>;

priority setup-priority reservation-priority;
to address;
}

You can include this statement at the following hierarchy levels:

[edit protocols rsvp interface interface-name link-protection]
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-protection]

If you configure a bypass LSP, you must also configure the to statement. The to statement specifies the address for the interface of the immediate next-hop node (for link protection) or the next-next-hop node (for node-link protection). The address specified determines whether this is a link protection bypass or a node-link protection bypass. On multiaccess networks (for example, a LAN), this address is also used to specify which next-hop node is being protected.

[Contents] [Prev] [Next] [Index] [Report an Error]