This chapter describes the RSVP-TE bypass commands for facility backup protection

Use this command to select the bypass trunk bandwidth support type.

Bypass trunks of dedicated bandwidth type will serve only bandwidth protections requested LSPs. The total bandwidth requirement of served LSPs will be less than or equal to the bandwidth configured on the bypass trunk. If an LSP with bandwidth protection and higher setup priority requests protection and bypass doesn't have sufficient bandwidth available, then LSPs with lower hold priority will be preempted to serve the LSP with higher setup priority.

Use the no parameter to remove configured backup bandwidth type.

The default backup bandwidth type for bypass tunnel is best-effort.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to reserve the bypass bandwidth in bits per second for the current trunk.

Each LSP has an associated bandwidth attribute. The bandwidth value is included in the sender's RSVP Path message and specifies the bandwidth to be reserved for the LSP. It is specified in bits per second, with a higher value indicating a greater user traffic volume. A zero bandwidth reserves no resources, although exchanges labels.

Use the no parameter to remove configured bandwidth information.

 

The default bandwidth is 0 bits per second, which allows data to flow through but does not reserve bandwidth.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to set the interval at which bypass trunk must query CSPF for LSP address. This mechanism ensures to update bypass trunk LSP addresses regularly so that, it can verify regularly if it can protect any LSP requesting protection.

Use the no parameter with this command to reset the interval to default value.

By default, interval is set to 60 seconds.

Router mode

This command was introduced in OcNOS version 3.0.

Use this command to specify the number of retries that CSPF should carry out for a request received from RSVP.

Use the no parameter with this command to disable this configuration.

By default, retry-limit is 0 which means infinite retry.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify the time between each retry that CSPF might carry out for a request received from RSVP. Use the no parameter with this command to disable this configuration.

By default, retry-timer is 0

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to set the filter to the fixed or shared style for an LSP.

Use the no parameter to reset the configured filter to the default.

By default, bypass filter is shared-explicit.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to configure the hold priority value for the selected bypass trunk. In case of insufficient bandwidth, remove less important existing LSPs to free up a portion of the bandwidth. This can be done by preempting one or more of the signaled LSPs. Hold priority determines the degree to which an LSP holds onto its reservation for a session after the LSP has been configured successfully. When the hold priority is high, the existing LSP is less likely to give up its reservation.

Use the no parameter to reset the trunk to the default hold-priority value.

The default hold-priority value is 0, which is the highest. Once a session is configured with a hold priority of 0, no other session can preempt it.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify a limit of hops for an RSVP bypass trunk. Hop-limit data is sent to the CSPF server if CSPF is used.

Upon configuration of an arbitrary hop-limit, the hop-limit is compared with the number of hops configured in the bypass path, if a bypass path has been configured. If the number of hops in the bypass path exceeds the hop-limit configured, no Path messages are sent, and any existing session is torn down. If no bypass path is configured, the bypass trunk is processed normally and Path messages are sent.

Use the no parameter to reset the bypass trunk to the default hop-limit value.

By default, bypass hop limit is 255

Bypass mode

This command was introduced in OcNOS version 3.0

Use this command to record all labels exchanged between RSVP-enabled routers during the reservation setup process.

Use the no parameter with this command to turn off recording.

None

By default, bypass label record is disabled

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to disable recording of the route taken by Path and Reservation Request (Resv) messages to confirm establishment of reservations and identify errors. Routes are recorded by means of the Route Record Object (RRO) in RSVP messages.

Use the record command to return to the default settings.

None

By default, routes are recorded

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify an RSVP path to be used. The PATHNAME in this command is the string (name) used to identify an RSVP path defined for the node (refer to rsvp-path command).

Use the no parameter with this command to remove a configured RSVP path.

By default, bypass path is disabled

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to configure preemption type which decides the criteria to be considered in case of preemption.

Use the no parameter to remove configured preemption type.

By default, preemption type is set to less-lsp-preempted.

Router mode

This command was introduced in OcNOS version 3.0.

Use this command to enable recording of the route taken by Path and Reservation Request (Resv) messages to confirm establishment of reservations and identify errors. Routes are recorded by means or the Route Record Object (RRO) in RSVP messages.

Use the no record command to disable recording of routes.

None

By default, routes are recorded

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify a retry count this RSVP bypass Trunk.

If a session is in a nonexistent state due to a path error message, the system tries to recreate the LSP for the number of times specified by the retry-limit command.

Although the same retry command controls both the trunk and the session, the retry-limit value affects only the session and not the trunk. If the trunk is in an incomplete state, the code keeps trying forever to bring it to a complete state regardless of the retry-limit value.

Use the no parameter with this command to revert to the default retry-limit value.

By default, the retry-limit value is 0, and the trunk and session try to create the LSP indefinitely.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify a retry interval for an RSVP bypass Trunk. When an ingress node tries to configure an LSP and the setup fails due to the receipt of a Path Error message, the system waits for the time configured with this command, before retrying the LSP setup process.

Use the no parameter with this command to revert to the default retry-time value.

By default, retry-timer value is 30 seconds.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to use the updated Route Record List as an Explicit Route (with all strict nodes) when a path message is sent out at the next refresh.

The ERO list contains the hops to be taken to reach the egress from the current LSR. If CSPF is not available, to place an ERO with all strict routes, use this command to modify the ERO after receiving the Resv message. The future Path messages have the ERO with all strict nodes, identifying each and every node to be traversed.

Use the no parameter with this command to disable the use of the Route Record List as the explicit route.

None

By default, reuse route record is disabled

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to create a new RSVP bypass trunk. When the bypass trunk is created, the attributes required to configure an explicitly-routed or traditionally-routed LSP are set. Once a trunk is configured with the required attributes, an RSVP bypass session (and PSB) is created for this trunk, which enables the exchange of messages and completes the LSP setup.

This command also modifies an existing RSVP path to configure an explicitly-routed or traditionally-routed LSP.

Use the no parameter with this command to remove an RSVP bypass trunk and all configured attributes.

By default, rsvp bypass trunk is disabled

Configure mode

This command was introduced in OcNOS version 3.0.

The command prompt changes from config to config-bypass as illustrated below:

Use this command to configure a setup priority value for a trunk. In case of insufficient bandwidth, users must remove less important LSPs to free up the bandwidth. This can be done by preempting one or more of the existing LSPs. The primary setup priority determines if a new LSP can preempt an existing LSP.

The setup priority of the new LSP must be higher than the hold priority of an existing LSP for the existing LSP to be preempted. Note that for a trunk, the setup priority should not be higher than the hold priority.

Use the no parameter with this command to revert to the default primary setup priority value.

By default, setup priority is 7, which is the lowest.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify an IPv4 egress for a bypass LSP. When configuring an LSP, you must specify the address of the egress router by using this command in the bypass node. An egress definition is a mandatory attribute; no RSVP session is created when an egress is not defined.

Use the no parameter with this command to unset the configured egress address.

None

The operator must specify an egress for LSP initialization to begin.

Bypass mode

This command was introduced in OcNOS version 3.0.

Use this command to specify the traffic type for this RSVP bypass Trunk.

Use the no parameter with this command to reset the configured traffic type.

By default, primary traffic type is controlled-load

Bypass mode

This command was introduced in OcNOS version 3.0.