This chapter describes the RSVP-TE commands.

Use this command to configure an explicit IPv4 route sub-object as either loose or strict. A list of sub-objects specifies an explicit route to the egress router for an LSP.

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

By default, A.B.C.D is disabled

Path mode

This command was introduced before OcNOS version 1.3.

Use this command to reset either all or specified sessions originating from a specific ingress and terminating on the specific egress.

Exec mode and Privileged Exec mode

This command was introduced before OcNOS version 1.3.

Use this command to clear an RSVP trunk or to clear all RSVP trunks.

Clearing a trunk also kills any session associated with the trunk. This command is useful when a trunk is missing required data such as routing information. When data is missing, the trunk is in an incomplete state, and clearing it correctly re-initializes the session.

Privileged Exec mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the use of Constrained Shortest Path First (CSPF) server for all RSVP sessions. If CSPF is turned off globally, it cannot be enabled for any LSP.

The CSPF server computes paths for LSPs that are subject to various constraints such as bandwidth, hop count, administrative groups, priority, and explicit routes. When computing paths for LSPs, CSPF considers not only the topology of the network and the attributes defined for the LSP but also the links. It attempts to minimize congestion by intelligently balancing the network load.

Use the no cspf command to disable this configuration.

None

By default, CSPF server is enabled

Router mode

This command was introduced before OcNOS version 1.3.

This example shows using the no cspf command in Router mode to disable CSPF for all RSVP sessions.

Use this command to enable all debugging options for an RSVP daemon.

Use the no parameter with this command to stop logging all debugging information.

None

Privileged Exec mode and Configure mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the exchange of debugging messages between the RSVP module and the CSPF module.

Use the no parameter with this command to stop logging CSPF debugging information.

None

Privileged Exec mode and Configure mode

This command was introduced before OcNOS version 1.3.

Use this command to enable debugging of events that were generated from an RSVP daemon.

Use the no parameter with this command to stop logging RSVP debugging information.

None

Privileged Exec and Configure modes

This command was introduced before OcNOS version 1.3.

Use these commands to enable debugging of events related to RSVP finite state machines (FSM). Commands are available to log debugging information for the egress FSM, the ingress FSM, the transit FSM, the transit upstream FSM, or the transit downstream FSM.

Use the no parameter with these commands to stop logging FSM debugging information.

None

Privileged Exec and Configure modes

This command was introduced before OcNOS version 1.3.

Use this command to enable the hexdump debugging option for an RSVP daemon.

Use the no parameter with this command to stop logging hexdump debugging information.

None

Privileged Exec and Configure modes

This command was introduced before OcNOS version 1.3.

Use this command to enable the NSM debugging option for an RSVP daemon.

Use the no parameter with this command to stop logging NSM debugging information.

None

Privileged Exec and Configure modes

This command was introduced before OcNOS version 1.3.

Use this command to enable packet debugging options for an RSVP daemon. Using the in option command enables debugging for incoming packets. Using the out option command enables debugging for outgoing packets.

Use the no parameter with these commands to stop logging debugging information.

None

Privileged Exec and Configure modes

This command was introduced before OcNOS version 1.3.

Use this command to add a description to the rsvp-bypass or update an existing description.

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

By default, rsvp bypass description is empty.

Rsvp-bypass mode

This command was introduced in OcNOS version 6.4.1.

Use this command to add a description to the rsvp-path or update an existing description.

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

By default, rsvp path description is empty.

Rsvp-path mode

This command was introduced in OcNOS version 6.4.1.

Use this command to add a description to the rsvp-trunk or update an existing description.

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

By default, rsvp trunk description is empty.

Rsvp-trunk mode.

This command was introduced in OcNOS version 6.4.1.

Use this command to disable RSVP message exchange on an interface.

RSVP can be enabled using the enable-rsvp command.

None

By default, RSVP message exchange is disabled on an interface.

Interface mode

This command was introduced before OcNOS version 1.3.

Use this command to enable RSVP message exchange on an interface.

See disable-rsvp to undo the effects of this command.

None

By default, RSVP message exchange is disabled.

Interface mode

This command was introduced before OcNOS version 1.3.

Use this command to share the load across multiple members of a LAG port in the core of an MPLS network by using entropy labels.

Use the no form of the command to disable the use of entropy labels

None

By default, entropy labels are not used.

Router mode

This command was introduced before OcNOS-SP version 1.0.

Use this command to send explicit-null labels to upstream router, instead of implicit-null labels.

If php is enabled then implicit-null label is advertised, then the penultimate hop removes the label and sends the packet as a plain IP packet to the egress router. The explicit-null command advertises label 0 and retains the label so the egress router can pop it. For details about usage of explicit-null, please refer to RFC 3032.

Use the no parameter with this command to stop sending explicit-null labels for directly-connected FECs to upstream router and resume sending non reserved labels.

None

By default, no-php is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to configure an extended-tunnel identifier as an IPv4 address. These identifiers are used in RSVP messages. If no extended-tunnel ID is specified, the LSR-ID for the router is used as the extended-tunnel ID for all LSPs. The extended-tunnel ID is a simple way of identifying all LSPs belonging to the same trunk.

Use the no parameter with this command to remove a configured extended-tunnel ID.

By default, the LSR-ID of the router is used as the extended-tunnel ID for all sessions.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a “from” IPv4 address for the RSVP daemon. This command can be invoked from either the router rsvp mode or from the rsvp-trunk mode. In the RSVP router mode, this command defines the source address as an IPv4 packet sent out by the RSVP daemon. In the RSVP trunk mode, this command indicates a sender’s address in the sender template object that is used in path messages.

Use the no parameter with this command to revert to the default settings.

By default, from A.B.C.D is enabled

Router or Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable RSVP-TE Graceful Restart capability on a router. This is a global parameter. RSVP-TE

determines whether or not to send the graceful restart capability object in its hello message. However, this capability

also depends on support for graceful restart on the neighbor router.

The following conditions must be met in order to activate RSVP-TE Graceful Restart:

None

Graceful restart is disabled by default

Router mode

This command was introduced before OcNOS-SP version 5.0.

Use this command to set a recovery time for an RSVP-TE graceful restart configuration.

Use the no parameter with this command to reset the recovery time.

Default value is 360000 ms.

Router mode

This command was introduced before OcNOS-SP version 5.0.

Use this command to set a restart time for an RSVP-TE graceful restart configuration.

Use the no parameter with this command to reset the restart time.

Default value is 180000 ms.

Router mode

This command was introduced before OcNOS-SP version 5.0.

Use this command to set an interval between Hello packets.

Used as a global command, this value is over-ridden by the hello-interval set on the interface (see rsvp hello-interval). For optimum performance, set this value no more than one-third of the hello-timeout value.

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

By default, hello interval is 2 seconds

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the receipt of Hello messages from peers.

Use the no parameter with this command to disable the exchange of Hello messages.

None

By default, hello receipt is disabled

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to set the RSVP hello timeout. If an LSR has not received a hello message from a peer within the number of seconds set with this command, all sessions shared with this peer are reset. The hello-timeout determines how long an RSVP node waits for a hello message before declaring a neighbor to be down.

Use the no parameter with this command to set the default hello timeout value.

By default, hello-timeout value is 7 seconds.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to configure the constant to be used to calculate a valid reservation lifetime for a Labeled Switched Path (LSP).

The refresh time and keep multiplier are two interrelated timing parameters used to calculate the valid reservation lifetime for an LSP. Use the following formula to calculate the reservation lifetime for an LSP:

The router sends refresh messages periodically so that the neighbors do not timeout.

Use the no parameter with this command to return to the default keep-multiplier setting.

By default, keep-multiplier value is 3

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to turn on loop detection for Path and Reservation messages exchanged between LSRs.

Use the no loop-detection command to return to default settings.

None

By default, loop detection is enabled

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to set LSP absolute metric or relative metric for IGP Shortcut use

Use the no parameter along with this command to unset the LSP metirc for IGP shortcut.

 

RSVP Trunk mode

 

Use this command to set the re-optimization interval timer.

Use the no parameter with this command to set the default re-optimization interval (5 minutes).

By default, the re-optimization timer interval is 5 minutes.

RSVP router mode

This command was introduced before OcNOS version 1.3.

Use this command to map a route using an IPv4 to an RSVP trunk. If the primary LSP for a trunk goes down, all mapped routes are sent automatically to a secondary LSP configured as backup for a primary LSP.

Use the no parameter with this command to unmap routes from specified trunks.

By default, map route A.B.C.D/M is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to designate a neighbor IPv4 address to use when exchanging hello messages. Any neighbor hello message that is not explicitly identified is rejected.

Use the no parameter with this command to remove an IP neighbor from the system.

None

By default, neighbor A.B.C.D is disabled

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to designate a neighbor IPv6 address to use when exchanging hello messages. Any neighbor hello message that is not explicitly identified is rejected.

Use the no parameter with this command to remove an IP neighbor from the system.

None

By default, neighbor X:X::X:X is disabled

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to disable the use of the Constrained Shortest Path First (CSPF) server for all RSVP sessions. Disable CSPF when no nodes support the required traffic engineering extensions.

When this command is executed in Router mode, CSPF is disabled for all configured RSVP sessions, and all RSVP sessions configured from this point forward. If the default CSPF per RSVP session is enabled, it will be disabled. The CSPF status for RSVP sessions can be verified using the show rsvp session command with the detail option.

Use the cspf command to revert to the default settings.

None

By default, no cspf is disabled

Router mode

This command was introduced before OcNOS version 1.3.

This example shows using the no cspf command in Router mode to disable CSPF for all RSVP sessions.

 

Use this command to disable Interior Gateway Protocol (IGP) shortcut.

None

Trunk mode

 

Use this command to turn off loop detection for Path and Reservation messages exchanged between LSRs. When a Path or Resv message is received, the primary IP address of the incoming interface is compared with the received route record list.

Use the loop-detection command to revert to default settings.

None

By default, no loop detection is disabled

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to disable Penultimate-Hop-Popping (PHP) for the router. An egress router sends neither implicit null label nor explicit null for LSPs. When no-php command is used, the egress router sends non-reserved labels (those labels in the label pool range allotted to RSVP) to the upstream router and retains the labels till the egress router.

None

By default, no php is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

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

None

Routes are recorded by default.

RSVP Bypass mode

(config-bypass)#no record

 

Use this command to disable parsing of Refresh PATH messages received from upstream nodes. Enable this command to minimize message processing by RSVP, if you are sure that a particular router does not need to parse Refresh-PATH messages to check for changes because LSPs passing through this router are not required to be updated, simultaneously.

Use the refresh-path-parsing command to revert to the default settings.

None

By default, refresh-path-parsing is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to disable parsing of Refresh RESV messages received from upstream nodes. Enable this command to minimize message processing by RSVP, if you are sure that a particular router does not need to parse Refresh RESV messages to check for changes because LSPs passing through this router are not required to be updated simultaneously.

None

By default, refresh reservation parsing is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to enable Penultimate-Hop-Popping for the router. An egress router send an implicit-null label (3) to the upstream router.

Use the no php command to revert to the default setting.

None

By default, no-php is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to configure primary administrative groups. Administrative groups are manually assigned attributes that describe the color of links, so that links with the same color are in one class. These groups are used to implement different policy-based LSP setups. Administrative group attributes can be included or excluded for an LSP or for a path’s primary and secondary paths.

Use the no parameter to remove a previously configured group from an administrative group list.

By default, primary admin group name is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable sending of session attribute objects with resource affinity data.

Use the no primary affinity command to disable sending of session attribute objects.

None

By default, primary affinity is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to reserve the primary 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.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the use of Constrained Shortest Path First (CSPF) server for an explicit route to the egress, or all RSVP sessions. When CSPF is turned off globally, it cannot be enabled for any LSP.

The CSPF server computes paths for LSPs that are subject to constraints such as bandwidth, hop count, administrative groups, priority, and explicit routes. When computing paths for LSPs, CSPF considers not only the topology of the network and the attributes defined for the LSP, but also the links. It attempts to minimize congestion by intelligently balancing the network load.

Use the no primary affinity command to revert to the default settings.

None

By default, primary cspf is enabled

Trunk mode

This command was introduced before OcNOS version 1.3.

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.

Trunk mode

This command was introduced before OcNOS version 1.3.

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

Trunk mode

This command was introduced before OcNOS version 1.3.

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, primary filter is shared-explicit.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure the hold priority value for the selected 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.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a limit of hops for an RSVP 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 primary path, if a primary path has been configured. If the number of hops in the primary path exceeds the hop-limit configured, no Path messages are sent, and any existing session is torn down. If no primary path is configured, the trunk is processed normally and Path messages are sent.

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

By default, primary hop limit is 255

Trunk mode

This command was introduced before OcNOS version 1.3.

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, primary label record is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the local repair of explicit routes for which this router is a transit node.

Use the no parameter with this command to disable local repair of explicit routes.

None

By default, primary local protection is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to disable the use of sending out session attribute objects with resource affinity data.

Use the primary affinity command to return to the default settings.

None

By default, primary no affinity is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to disable the use of Constrained Shortest Path First (CSPF) server for an explicit route to the egress, or all RSVP sessions. When CSPF is turned off globally it cannot be enabled for any LSP. If used per LSP, it can be used to turn off CSPF computation for a specific LSP.

Disable CSPF when all nodes do not support the required traffic engineering extensions, and configure LSPs manually to use an explicit path. The LSP is then established only along the path specified by the operator.

Use the primary cspf command to enable this setting.

None

By default, no primary cspf is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.

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 primary record command to return to the default settings.

None

By default, routes are recorded

Trunk mode

This command was introduced before OcNOS version 1.3.

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, primary path is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

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 primary record command to disable recording of routes.

None

By default, routes are recorded

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a retry count this RSVP 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.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a retry interval for an RSVP 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.

Trunk mode

This command was introduced before OcNOS version 1.3.

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, primary reuse route record is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

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.

Trunk mode

This command was introduced before OcNOS version 1.3.

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

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

By default, primary traffic type is controlled-load

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure RSVP refresh interval timer. The timer specifies the interval after which Path and/ or Reservation Request (Resv) messages will be sent out.

The refresh time and keep multiplier are two interrelated timing parameters used to calculate the valid Reservation Lifetime for an LSP. Refresh time regulates the interval between Refresh messages which include Path and Reservation Request (Resv) messages. Refresh messages are sent periodically so that reservation does not timeout in the neighboring nodes. Each sender and receiver host sends Path and Resv messages, downstream and upstream respectively, along the paths.

Use the no parameter with this command to return to the default refresh-time interval.

By default, refresh-time interval is 30 seconds

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to disable parsing of Refresh PATH messages received from upstream nodes. Use this command to minimize message processing by RSVP when you are sure that a particular router does not need to parse Refresh-PATH messages to check for changes, because LSPs passing through this router are not required to be updated simultaneously.

Use the no refresh-path-parsing command to disable this setting.

None

By default, refresh-path-parsing is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to disable parsing of Refresh RESV messages received from upstream nodes. Use this command to minimize message processing by RSVP when you are sure that a particular router does not need to parse Refresh RESV messages to check for changes because LSPs passing through this router are not required to be updated simultaneously.

Use the no refresh-resv-parsing command to disable this setting.

None

By default, refresh reservation parsing is enabled.

Router mode

This command was introduced before OcNOS version 1.3.

Use this command to enable re-optimization of the RSVP primary LSP with the rsvp-trunk force-reoptimize command.

Use the no parameter with this command to disable re-optimization of the RSVP primary LSP.

None

Trunk mode

This command was introduced in OcNOS version 1.3.4.

 

Use this command to restart RSVP gracefully.

To restart RSVP gracefully, you must give the graceful-restart command to enable graceful restart capability on the device in RSVP router mode.

None

Privileged Exec mode

This command was introduced before OcNOS-SP version 5.0.

Use this command to enter router mode from configure mode and to enable the RSVP daemon, if it is not already enabled.

Use the no parameter with this command to disable RSVP on the node.

None

RSVP is started only if this command is executed.

Configure mode

This command was introduced before OcNOS version 1.3.

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

Use this command to enable the sending of Hello packets on the interface and to set the interval value between successive Hello packets to neighbor. For optimum performance, set this value to less than one-third the value of the configured RSVP hello-timeout. See the rsvp hello-timeout command for more information.

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

By default, RSVP hello interval is 2 seconds

Interface mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the receipt of hello messages from peers connected through this interface. This is an interface-specific command and when not used, the global hello-receipt command applies.

Use the no parameter with this command to disable the exchange of hello messages for this interface.

None

By default, rsvp hello receipt is disabled

Interface mode

This command was introduced before OcNOS version 1.3.

This command determines how long an RSVP node should wait for a hello message before declaring a neighbor to be down. If an LSR does not received a hello message from a peer connected to an interface within the specified duration, the LSR resets all sessions that are shared with this particular peer. This is an interface-specific command and when not used, the global hello-timeout command applies.

Use the no parameter to revert to the default hello timeout value.

By default, hello-timeout value is 7 seconds

Interface mode

This command was introduced before OcNOS version 1.3.

This command sets the constant for calculating a valid reservation lifetime for an LSP, which allows messages to be exchanged through this interface. This is an interface-specific command and when not specified, the global keep-multiplier command applies.

Reservation lifetime is the duration of bandwidth reservation for the LSP. The refresh time and keep multiplier are two interrelated timing parameters used to calculate the valid reservation lifetime for an LSP. Use the following formula to calculate the reservation lifetime for an LSP:

Refresh messages are sent periodically so that neighbors do not timeout.

Use the no parameter with this command to return to the global keep-multiplier value.

By default RSVP keep-multiplier value is 3

Interface mode

This command was introduced before OcNOS version 1.3.

Use this command to configure RSVP refresh interval timer for the current interface. This is an interface-specific command and when not used, the global refresh-time command applies.

The refresh time and keep multiplier are two interrelated timing parameters used to calculate the valid reservation lifetime for an LSP. Refresh time regulates the interval between refresh messages that include path and reservation request (Resv) messages. Refresh messages are sent periodically so that the reservation does not timeout in the neighboring nodes. Each sender and receiver host sends path and resv messages, downstream and upstream respectively, along the paths.

Use the no parameter with this command to revert to the refresh-time value set in RSVP mode.

By default, refresh interval is 30 seconds

Interface mode

This command was introduced before OcNOS version 1.3.

Use this command to create a new RSVP path or to enter the Path command mode. In this mode, you can add or delete paths and also specify the path to be loose or strict.

Use the no parameter with this command to delete the path and its specified hops.

By default, rsvp path is disabled

Configure mode

This command was introduced before OcNOS version 1.3.

Use this command to create a new RSVP trunk. When the 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 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. In addition, this command can be used to set the address family (IPv4) of an RSVP trunk. If no address family is assigned, the default value is used. If the address family is already set, a check is made to see whether the address family configured and the one already in the database are the same. An error message is returned if the two do not match.

Use the no parameter with this command to remove an RSVP trunk and all configured attributes, except the primary path.

By default, rsvp trunk is disabled

Configure mode

This command was introduced before OcNOS version 1.3.

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

Use this command to force re-optimize a particular primary LSP. Re-optimization of the LSP must have been enabled with the reoptimize command.

NA.

Execute mode

This command was introduced before OcNOS version 1.3.

Use this command to force switchover a secondary LSP. This command is recommended for limited use on a stable system when there is a need for software upgrade without traffic impact.

NA.

Execute mode

This command was introduced before OcNOS version 1.3.

Use this command to restart the RSVP trunk. This command “kills” an existing LSP and restarts the LSP setup process.

None

By default, rsvp trunk restart is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure secondary administrative groups. Administrative groups are manually assigned attributes that describe the color of links, so that links with the same color are in one class. These groups are used to implement different policy-based LSP setups. Administrative group attributes can be included or excluded for an LSP or for a path’s primary and secondary paths.

Use the no parameter to remove a previously set group from an administrative group list.

By default, secondary admin group name is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to reserve the 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 set in bits per second, with a higher value indicating a greater user traffic volume. A zero bandwidth reserves no resources, although label exchanges are possible.

Use the no parameter with this command to unset the configured bandwidth information.

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

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the use of Constrained Shortest Path First (CSPF) server for an explicit route to the egress, or all RSVP sessions.

The CSPF server computes paths for LSPs that are subject to constraints such as bandwidth, hop count, administrative groups, priority, and explicit routes. When computing paths for LSPs, CSPF considers not only the topology of the network and the attributes defined for the LSP, but also the links. It attempts to minimize congestion by intelligently balancing the network load.

Use the no secondary cspf command to revert to the default settings.

None

By default, secondary cspf is enabled

Trunk mode

This command was introduced before OcNOS version 1.3.

This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.

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 remove this configuration.

By default, no retry limit for CSPF route calculations is configured, so the value is 0.

Trunk mode

This command was introduced before OcNOS version 1.3.

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 remove this configuration.

By default, no retry-timer configuration is defined for CSPF calculations, so the value is set to 0.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to set the filter to fixed or shared filter style for RSVP trunk.

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

By default, secondary filter is shared-explicit.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure the hold priority value for the selected trunk.

In case of insufficient bandwidth, the user must remove any less important existing LSP to free up 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 revert to the default hold-priority value.

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

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a limit of hops for an RSVP trunk.

Upon configuration of an arbitrary hop-limit, the hop-limit is compared with the number of hops configured in the primary path, if a primary path has been configured. If the number of hops in the primary path exceed the hop-limit configured, no path messages are sent out and any existing session is torn down. If no primary path is configured, the trunk is processed normally and the path messages are sent out. The hop-limit data is sent to the CSPF server, if CSPF is being used.

Use the no parameter to revert to the default hop-limit value.

By default, secondary hop limit is 255

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to record all labels exchanged between RSVP enabled routers during the reservation setup process. This command records all labels exchanged for an LSP from the ingress to the egress, and helps with debugging.

Use the no parameter to turn off recording.

By default, secondary label record is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to enable the local repair of explicit routes for which this router is a transit node.

Use the no parameter with this command to disable local repair of explicit routes.

None

By default, secondary local protection is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to disable the use of sending out session attribute objects with resource affinity data.

Use the secondary bandwidth command to revert to the default settings.

None

By default, no secondary affinity is disabled.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to disable the use of Constrained Shortest Path First (CSPF) server for an explicit route to the egress, or all RSVP sessions.

If CSPF is turned off globally, it cannot be enabled for any LSP. If used per LSP, it can be used to turn off CSPF computation for a specific LSP. The CSPF server computes paths for LSPs that are subject to various constraints such as bandwidth, hop count, administrative groups, priority, and explicit routes. When computing paths for LSPs, CSPF considers not only the topology of the network and the attributes defined for the LSP, but, also the links. It attempts to minimize congestion by intelligently balancing the network load.

Disable CSPF when all nodes do not support the required traffic engineering extensions and configure LSPs manually to use an explicit path. The LSP is then established only along the path specified by the operator.

Use the secondary cspf command to revert to the default settings.

None

By default, secondary no cspf is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.

This command is used to disable recording of the route taken by path and resv messages and confirms the establishment of reservations and to identify errors. Routes are recorded by means of the route record object (RRO) in an RSVP message.

Use the secondary record command to revert to the default settings.

None

By default, routes are recorded

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify an RSVP path to be used.

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

By default, secondary path is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a RSVP path to be used for a specific priority secondary.

Use the no parameter with this command to remove a configured secondary-priority.

Secondary Priority value.

Secondary-priority can only be configured along with a path. Other attributes can only be associated post this command.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure the hold priority value for the secondary-priority lsp.

In case of insufficient bandwidth, the user must remove any less important existing LSP to free up 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 revert to the default hold-priority value.

Secondary Priority value.

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

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure a setup priority value for the secondary-priority lsp.

In case of insufficient bandwidth, the user must remove any less important LSPs to free up bandwidth. This can be done by preempting one or more of the existing LSPs. The setup priority determines whether a new LSP that preempts an existing LSP may be established. 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 setup priority value.

Secondary Priority value.

By default, setup value is 7 (the lowest).

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to record all labels exchanged between RSVP enabled routers during the reservation setup process. This command records all labels exchanged for an LSP from the ingress to the egress, and helps with debugging.

Use the no parameter to turn off recording.

Secondary Priority value.

By default, label record is disabled for secondary-priority.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a limit of hops for a secondary-priority lsp.

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

Use the no parameter to revert to the default hop-limit value.

Secondary Priority value.

By default, hop limit is 255.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to reserve the 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 set in bits per second, with a higher value indicating a greater user traffic volume. A zero bandwidth reserves no resources, although label exchanges are possible.

Use the no parameter with this command to unset the configured bandwidth information.

Secondary Priority value.

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

Trunk mode

This command was introduced before OcNOS version 1.3.

This command is used to enable recording of the route taken by path and resv messages to confirm the establishment of reservations and to identify errors. Routes are recorded by means of the route record object (RRO) in RSVP messages.

Use the no secondary record command to revert to the default settings.

None

By default, routes are recorded

Trunk mode

This command was introduced before OcNOS version 1.3.

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

If a session is in a nonexistent state due to the receipt of a path error message, it tries to recreate the LSP for the number of times specified by primary retry-limit. 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 to bring it to a complete state, irrespective of the retry-limit value.

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

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

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to specify a retry interval for an RSVP Trunk. When the ingress tries to configure an LSP and the setup fails due to the receipt of a path error message, the system waits for the time configure by this command before retrying the LSP setup process.

Use the no parameter to revert to the default.

By default, retry time is 30 seconds

Trunk mode

This command was introduced before OcNOS version 1.3.

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.

An explicit route object (ERO) list contains the hops to be taken to reach the egress from the current LSR. If CSPF can not place an ERO with all strict routes, then this command helps modify the ERO after receiving resv messages. Future path messages have the ERO with all strict nodes, which identify each and every node to be traversed.

Use the no parameter to disable the use of the route record list as the explicit route.

None

By default, secondary reuse route record is disabled

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to configure a setup priority value for this trunk.

In case of insufficient bandwidth, the user must remove any less important LSPs to free up bandwidth. This can be done by preempting one or more of the existing LSPs. The setup priority determines whether a new LSP that preempts an existing LSP may be established. 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 setup priority value.

By default, setup value is 7 (the lowest).

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to identify the traffic type for this RSVP Trunk.

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

Controlled load is the default traffic type.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to restart SNMP in Resource Reservation Protocol -Traffic Engineering (RSVP-TE)

None

By default, snmp restart rsvp is disabled

Configure mode

This command was introduced before OcNOS version 1.3.

Use this command to specify an IPv4 egress for an LSP. When configuring an LSP, you must specify the address of the egress router by using this command in the trunk 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.

Trunk mode

This command was introduced before OcNOS version 1.3.

Use this command to change the method of updating attributes for sessions (primary/ secondary) for this trunk.

Use the no parameter with this command to remove an update type.

By default, make-before-break types of updates are carried out.

Trunk mode

This command was introduced before OcNOS version 1.3.