OcNOS-RON : Multi-Protocol Label Switching Guide : RSVP-TE Command Reference : RSVP-TE Commands
RSVP-TE Commands
This chapter describes the RSVP-TE commands.
cspf
no php
php
A.B.C.D
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.
For the strict type of route addresses, the route taken from the previous router to the current router must be a directly connected path and a message exchanged between the two routers should not pass any intermediate routers. This ensures that routing is enforced on the basis of each link.
For the loose type of route addresses, the route taken form the previous router to the current router need not be a direct path and a message exchanged between the two routers can pass other routers.
Use the no parameter with this command to disable the configuration.
Command Syntax
A.B.C.D
A.B.C.D (loose|strict)
no A.B.C.D
no A.B.C.D (loose|strict)
Parameters
loose
Make this node loose
strict
Make this node strict
Default
By default, A.B.C.D is disabled
Command Mode
Path mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-path mypath
(config-path)#10.10.0.5 strict
clear rsvp session
Use this command to reset either all or specified sessions originating from a specific ingress and terminating on the specific egress.
Note: If the affected session originates from the router where the command is issued, it is stopped and started. If the affected session does not originate from the router where the command is issued, it is stopped and deleted.
Command Syntax
clear rsvp session TUNNEL-ID LSP-ID INGRESS EGRESS
Parameters
TUNNELID
Clear tunnel ID sessions
LSP-ID
Clear LSP ID sessions
INGRESS
Clear ingress sessions
EGRESS
Clear egress sessions
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#clear rsvp session 1 1 1.2.3.4 192.168.1.1
clear rsvp trunk
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.
Note: If this command is given in the session on the ingress router, the session stops and restarts. If this command is given in the session on the egress router, the session is not cleared.
Command Syntax
Note: Use the following commands to clear standard RSVP Trunks:
clear rsvp trunk *
clear rsvp trunk ingress (TRUNKNAME|*)
clear rsvp trunk non-ingress (TRUNKNAME|*)
clear rsvp trunk (TRUNKNAME|*)
clear rsvp trunk (TRUNKNAME|*) primary
clear rsvp trunk (TRUNKNAME|*) secondary
Parameters
*
Clear all RSVP trunks configured
TRUNKNAME
Name of a specific trunk to be cleared
ingress
Clear an RSVP ingress trunk
non-ingress
Clear an RSVP non-Ingress trunk
primary
Clear all primary sessions configured for this trunk
secondary
Clear all secondary sessions configured for this trunk
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#clear rsvp trunk mytrunk
#clear rsvp trunk *
#clear rsvp trunk ingress mytrunk
#clear rsvp trunk ingress *
#clear rsvp trunk non-ingress mytrunk
#clear rsvp trunk non-ingress *
#clear rsvp trunk mytrunk primary
#clear rsvp trunk * primary
#clear rsvp trunk mytrunk secondary
#clear rsvp trunk * secondary
cspf
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.
Note: CSPF server information is not signaled across session and hence sessions in transit and egress nodes will not be aware of the CSPF server. So, in multi CSPF scenarios, neighbor down event from a CSPF server restart all sessions irrespective of which CSPF server sessions were using.
Command Syntax
cspf
Parameters
None
Default
By default, CSPF server is enabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows using the no cspf command in Router mode to disable CSPF for all RSVP sessions.
#configure terminal
(config)#router rsvp
(config-router)#cspf
debug rsvp all
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.
Command Syntax
debug rsvp (all|)
no debug rsvp (all|)
Parameters
None
Command Mode
Privileged Exec mode and Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp all
debug rsvp cspf
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.
Command Syntax
debug rsvp cspf
no debug rsvp cspf
Parameters
None
Command Mode
Privileged Exec mode and Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp cspf
debug rsvp events
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.
Command Syntax
debug rsvp events
no debug rsvp events
Parameters
None
Command Mode
Privileged Exec and Configure modes
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp events
debug rsvp fsm
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.
Command Syntax
debug rsvp fsm
debug rsvp fsm egress
debug rsvp fsm ingress
debug rsvp fsm transit
debug rsvp fsm transit upstream
debug rsvp fsm transit downstream
no debug rsvp fsm
no debug rsvp fsm egress
no debug rsvp fsm ingress
no debug rsvp fsm transit
no debug rsvp fsm transit upstream
no debug rsvp fsm transit downstream
Parameters
None
Command Mode
Privileged Exec and Configure modes
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)#debug rsvp fsm transit upstream
debug rsvp hexdump
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.
Command Syntax
debug rsvp hexdump
no debug rsvp hexdump
Parameters
None
Command Mode
Privileged Exec and Configure modes
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp hexdump
debug rsvp nsm
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.
Command Syntax
debug rsvp nsm
no debug rsvp nsm
Parameters
None
Command Mode
Privileged Exec and Configure modes
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp nsm
debug rsvp packet
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.
Command Syntax
debug rsvp packet
debug rsvp packet in
debug rsvp packet out
no debug rsvp packet
no debug rsvp packet in
no debug rsvp packet out
Parameters
None
Command Mode
Privileged Exec and Configure modes
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#debug rsvp packet in
#debug rsvp packet out
disable-rsvp
Use this command to disable RSVP message exchange on an interface.
RSVP can be enabled using the enable-rsvp command.
Command Syntax
disable-rsvp
Parameters
None
Default
By default, RSVP message exchange is disabled on an interface.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth0
(config-if)#disable-rsvp
enable-rsvp
Use this command to enable RSVP message exchange on an interface.
Note: To use this command, the corresponding interface needs to be enabled for label-switching using the label-switching command.
See disable-rsvp to undo the effects of this command.
Command Syntax
enable-rsvp
Parameters
None
Default
By default, RSVP message exchange is disabled.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth1
(config-if)#enable-rsvp
entropy-label-capability
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
Note: Load balancing is enabled by default for all the parameters. If you enable load balancing manually, then all the parameters enabled by default are reset and you need to enable the parameters based on which traffic should be load balanced.
Command Syntax
entropy-label-capability
no entropy-label-capability
Parameters
None
Default
By default, entropy labels are not used.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS-SP version 1.0.
Examples
#configure terminal
(config)router rsvp
(config-router)#entropy-label-capability
explicit-null
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.
Command Syntax
explicit-null
no explicit-null
Parameters
None
Default
By default, no-php is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#explicit-null
ext-tunnel-id A.B.C.D
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.
Command Syntax
ext-tunnel-id A.B.C.D
no ext-tunnel-id
no ext-tunnel-id
Parameters
A.B.C.D
Extended tunnel identifier for this trunk in IPv4 address format
Default
By default, the LSR-ID of the router is used as the extended-tunnel ID for all sessions.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk t1
(config-trunk)#ext-tunnel-id 10.10.10.30
 
(config)#rsvp-trunk t1
(config-trunk)#no ext-tunnel-id
from A.B.C.D
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.
Command Syntax
from A.B.C.D
no from
Parameters
A.B.C.D
When in trunk mode, this is the IPv4 address of a tunnel ingress node
A.B.C.D
When in router mode, this is the loopback IPv4 address
Default
By default, from A.B.C.D is enabled
Command Mode
Router or Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#from 10.10.0.5
#configure terminal
(config)#router rsvp
(config-router)#from 10.10.0.5
 
graceful-restart
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:
This command is used on the local router.
The neighbor router is explicitly set with a neighbor command (refer to either the neighbor A.B.C.Dor neighborX:X::X:X command for details).
The neighbor router supports Graceful Restart, and it is activated.
Command Syntax
graceful-restart
no graceful-restart
Parameters
None
Default
Graceful restart is disabled by default
Command Mode
Router mode
Applicability
This command was introduced before OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#router rsvp
(config-router)#graceful-restart
(config-router)#no graceful-restart
graceful-restart recovery-time
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.
Command Syntax
graceful-restart recovery-time <60000-3600000>
no graceful-restart recovery-time
Parameters
<60000-3600000>
Recovery time value in milliseconds
Default
Default value is 360000 ms.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#router rsvp
(config-router)#graceful-restart recovery-time 600000
 
 
 
graceful-restart restart-time
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.
Command Syntax
graceful-restart restart-time <10000-600000>
no graceful-restart restart-time
Parameters
<10000-600000>
Restart time value in milliseconds
Default
Default value is 180000 ms.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#router rsvp
(config-router)#graceful-restart restart-time 100000
 
 
 
 
hello-interval
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.
Command Syntax
hello-interval <1-65535>
no hello-interval
Parameter
<1-65535>
The time in seconds after which hello packets are sent
Default
By default, hello interval is 2 seconds
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#hello-interval 5
 
(config)#router rsvp
(config-router)#no hello-interval
hello-receipt
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.
Command Syntax
hello-receipt
no hello-receipt
Parameters
None
Default
By default, hello receipt is disabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#hello-receipt
hello-timeout
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.
Command Syntax
hello-timeout <1-65535>
no hello-timeout
Parameter
<1-65535>
Time in seconds to receive a hello message.
Default
By default, hello-timeout value is 7 seconds.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#hello-timeout 12
 
(config)#router rsvp
(config-router)#no hello-timeout
keep-multiplier
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:
L >= (K + 0.5)* 1.5 * R
K = keep-multiplier
R = refresh timer
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.
Command Syntax
keep-multiplier <1-255>
no keep-multiplier <1-255>
Parameters
<1-255>
The keep-multiplier value
Default
By default, keep-multiplier value is 3
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#keep-multiplier 2
loop-detection
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.
Command Syntax
loop-detection
Parameters
None
Default
By default, loop detection is enabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#loop-detection
lsp-metric
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.
Command Syntax
lsp-metric absolute <1-65535>
lsp-metric relative (<-65535-0>|<1-65535>)
no lsp-metric absolute-metric (<1-65535>|)
no lsp-metric relative (<-65535-0>|<1-65535>|)
Parameters
absolute
Absolute metric
relative
Relative metric
<1-65535>
Metric value
<-65535-0>
The keep-multiplier value
 
Command Mode
RSVP Trunk mode
Examples
#configure terminal
(config)#router rsvp
(config-router)#exit
(config)#rsvp trunk T1
(config-trunk)#lsp-metric absolute 10
(config-trunk)#lsp-metric relative 10
 
 
 
lsp-reoptimization-timer
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).
Command Syntax
lsp-reoptimization-timer <1-240>
Parameter
<1-240>
The interval in minutes after which LSP re-optimization will take place.
Default
By default, the re-optimization timer interval is 5 minutes.
Command Mode
RSVP router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
(config)#router rsvp
(config-router)#lsp-reoptimization-timer 10
(config)#router rsvp
(config-router)#no lsp-reoptimization-timer
map-route A.B.C.D
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.
Command Syntax
map-route A.B.C.D/M
map-route A.B.C.D/M CLASS
map-route A.B.C.D A.B.C.D
map-route A.B.C.D A.B.C.D CLASS
no map-route A.B.C.D/M
no map-route A.B.C.D/M CLASS
no map-route A.B.C.D A.B.C.D
no map-route A.B.C.D A.B.C.D CLASS
Parameters
A.B.C.D/M
Prefix to map, plus mask
A.B.C.D
Prefix to be mapped
A.B.C.D
Prefix mask
CLASS
Incoming DiffServ Class (for example, be, ef, etc.) to map to the RSVP trunk
Default
By default, map route A.B.C.D/M is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#map-route 2.2.2.2/16
neighbor A.B.C.D
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.
Command Syntax
neighbor A.B.C.D
no neighbor A.B.C.D
Parameters
None
Default
By default, neighbor A.B.C.D is disabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#neighbor 10.10.0.5
neighbor X:X::X:X
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.
Command Syntax
neighbor X:X::X:X
no neighbor X:X::X:X
Parameters
None
Default
By default, neighbor X:X::X:X is disabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#neighbor 3ffe::3:34
no cspf
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.
Note: When CSPF is disabled, path is not calculated taking constraints into consideration. Path message is sent to the next hop based on IGP best route. In this case, ERO is not included in path message and all constraints are included.
Command Syntax
no cspf
Parameters
None
Default
By default, no cspf is disabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows using the no cspf command in Router mode to disable CSPF for all RSVP sessions.
#configure terminal
(config)#router rsvp
(config-router)#no cspf
 
no igp-shortcut
Use this command to disable Interior Gateway Protocol (IGP) shortcut.
Command Syntax
no igp-shortcut
Parameters
None
Command Mode
Trunk mode
Example
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no igp-shortcut
 
no loop-detection
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.
Command Syntax
no loop-detection
Parameters
None
Default
By default, no loop detection is disabled
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#no loop-detection
 
no php
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.
Note: Use the show rsvp command to display the status of Penultimate-Hop-Popping.
Command Syntax
no php
Parameters
None
Default
By default, no php is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#no php
no record
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.
Command Syntax
no record
Parameters
None
Default
Routes are recorded by default.
Command Mode
RSVP Bypass mode
Examples
#configure terminal
(config)#rsvp-bypass bypassname
(config-bypass)#no record
 
no refresh-path-parsing
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.
Command Syntax
no refresh-path-parsing
Parameters
None
Default
By default, refresh-path-parsing is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
Router#configure terminal
Router(config)#router rsvp
Router(config-router)#no refresh-path-parsing
no refresh-resv-parsing
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.
Command Syntax
no refresh-resv-parsing
Parameters
None
Default
By default, refresh reservation parsing is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
Router#configure terminal
Router(config)#router rsvp
Router(config-router)#no refresh-resv-parsing
 
php
Use this command to enable Penultimate-Hop-Popping for the router. An egress router send an implicit-null label (3) to the upstream router.
Note: Use the show rsvp command to display the status of Penultimate-Hop-Popping.
Use the no php command to revert to the default setting.
Command Syntax
php
Parameters
None
Default
By default, no-php is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#php
primary ADMIN-GROUP-NAME
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.
Note: A link can be added to a specific Administrative Group via the Network Services Module. Refer to the Network Services Module Command Reference for details.
Use the no parameter to remove a previously configured group from an administrative group list.
Command Syntax
primary (include-any|include-all|exclude-any) ADMIN-GROUP-NAME
primary (include-any|exclude-any) ADMIN-GROUP-NAME
primary (include-any|include-all|exclude-any) ADMIN-GROUP-NAME
primary (include-any|exclude-any) ADMIN-GROUP-NAME
Parameters
include-any
Include any attributes
include-all
Include all attributes
exclude-any
Exclude any attribute
ADMIN-GROUP-NAME
 
Administrative group name
Default
By default, primary admin group name is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary exclude-any myadmingroup
 
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary include-all admingrp2
 
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary include-any admingrp2
primary affinity
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.
Command Syntax
primary affinity
Parameters
None
Default
By default, primary affinity is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary affinity
primary bandwidth
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.
Command Syntax
primary bandwidth BANDWIDTH
no primary bandwidth BANDWIDTH
Parameter
BANDWIDTH
<1-999>k for 1 to 999 kilobits/s
<1-999>m for 1 to 999 megabits/s
<1-100>g for 1 to 100 gigabits/s
Default
The default bandwidth is 0 bits per second, which allows data to flow through but does not reserve bandwidth.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary bandwidth 100m
primary cspf
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.
Note: CSPF server information is not signaled across session and hence sessions in transit and egress nodes will not be aware of the CSPF server. So, in multi CSPF scenarios, neighbor down event from a CSPF server restart all sessions irrespective of which CSPF server sessions were using.
Command Syntax
primary cspf
Parameters
None
Default
By default, primary cspf is enabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary cspf
primary cspf-retry-limit
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.
Command Syntax
primary cspf-retry-limit <1-65535>
no primary cspf-retry-limit
Parameter
<1-65535>
Set the number of times CSPF should retry for this LSP
Default
By default, retry-limit is 0.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#primary cspf-retry-limit 535
 
(config)#rsvp-trunk T1
(config-trunk)#no primary cspf-retry-limit
primary cspf-retry-timer
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.
Command Syntax
primary cspf-retry-timer <1-600>
hno primary cspf-retry-timer
Parameter
<1-600>
Timeout between successive retries, in seconds
Default
By default, retry-timer is 0
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#primary cspf-retry-timer 45
 
(config)#rsvp-trunk T1
(config-trunk)#no primary cspf-retry-timer
primary filter
Use this command to set the filter to the fixed or shared style for an LSP.
The shared filter style identifies a shared reservation environment. It creates a single reservation into which flows from all senders are mixed.
The fixed filter style designates a distinct reservation. A distinct reservation request is created for data packets from a particular sender. The fixed filter style is also used style to prevent rerouting of an LSP and to prevent another LSP from using this bandwidth.
Use the no parameter to reset the configured filter to the default.
Command Syntax
primary filter (fixed|shared-explicit)
no primary filter (fixed|shared-explicit)
Parameters
fixed
Use a fixed filter for this LSP
shared-explicit
 
Use a shared-explicit filter for this LSP
Default
By default, primary filter is shared-explicit.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary filter shared-explicit
primary hold-priority
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.
Command Syntax
primary hold-priority <0-7>
no primary hold-priority
Parameter
<0-7>
Set a hold priority for the LSP
Default
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.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary hold-priority 2
primary hop-limit
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.
Command Syntax
primary hop-limit <1-255>
no primary hop-limit <1-255>
no primary hop-limit
Parameters
<1-255>
Set the number of acceptable hops for the LSP
Default
By default, primary hop limit is 255
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary hop-limit 23
primary label-record
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.
Command Syntax
primary label-record
no primary label-record
Parameters
None
Default
By default, primary label record is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary label-record
primary local-protection
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.
Command Syntax
primary local-protection
no primary local-protection
Parameters
None
Default
By default, primary local protection is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#primary local-protection
no primary affinity
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.
Command Syntax
no primary affinity
Parameters
None
Default
By default, primary no affinity is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no primary affinity
no primary cspf
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.
Command Syntax
no primary cspf
Parameters
None
Default
By default, no primary cspf is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no primary cspf
 
no primary record
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.
Command Syntax
no primary record
Parameters
None
Default
By default, routes are recorded
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no primary record
primary path
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.
Command Syntax
primary path PATHNAME
no primary path
Parameters
PATHNAME
The name of the path to use
Default
By default, primary path is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary path mypath
primary record
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.
Command Syntax
primary record
Parameters
None
Default
By default, routes are recorded
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary record
primary retry-limit
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.
Command Syntax
primary retry-limit <1-65535>
no primary retry-limit
Parameter
<1-65535>
The set number of times the system should try setting up the LSP
Default
By default, the retry-limit value is 0, and the trunk and session try to create the LSP indefinitely.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary retry-limit 256
primary retry-timer
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.
Command Syntax
primary retry-timer <1-6OO>
no primary retry-timer <1-6OO>
no primary retry-timer
Parameter
<1-6OO>
Time in seconds after which the system should retry setting up the LSP
Default
By default, retry-timer value is 30 seconds.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary retry-timer 12
primary reuse-route-record
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.
Command Syntax
primary reuse-route-record
no primary reuse-route-record
Parameters
None
Default
By default, primary reuse route record is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary reuse-route-record
primary setup-priority
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.
Command Syntax
primary setup-priority <0-7>
no primary setup-priority
Parameters
<0-7>
Set the priority value
Default
By default, setup priority is 7, which is the lowest.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary setup-priority 2
primary traffic
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.
Command Syntax
primary traffic (guaranteed|controlled-load)
no primary traffic
Parameters
controlled-load
Controlled loaded traffic
guaranteed
Guaranteed traffic
Default
By default, primary traffic type is controlled-load
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#primary traffic guaranteed
refresh-time
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.
Command Syntax
refresh-time <1-65535>
no refresh-time <1-65535>
no refresh-time
Parameter
<1-65535>
The duration for which messages are sent, in seconds
Default
By default, refresh-time interval is 30 seconds
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#router rsvp
(config-router)#refresh-time 20
refresh-path-parsing
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.
Command Syntax
refresh-path-parsing
Parameters
None
Default
By default, refresh-path-parsing is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
Router#configure terminal
Router(config)#router rsvp
Router(config-router)#refresh-path-parsing
refresh-resv-parsing
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.
Command Syntax
refresh-resv-parsing
Parameters
None
Default
By default, refresh reservation parsing is enabled.
Command Mode
Router mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
Router#configure terminal
Router(config)#router rsvp
Router(config-router)#refresh-resv-parsing
 
reoptimize
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.
Command Syntax
reoptimize
Parameters
None
Command Mode
Trunk mode
Applicability
This command was introduced in OcNOS version 1.3.4.
Examples
(config)#rsvp-trunk t1
(config-trunk)#reoptimize
(config)#rsvp-trunk t1
(config-trunk)#no reoptimize
 
restart rsvp graceful
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.
Command Syntax
restart rsvp graceful
Parameter
None
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS-SP version 5.0.
Example
#restart rsvp graceful
% Warning : You may loose rsvp configuration, if not saved
Proceed for graceful restart? (y/n):y
%% Managed module is down or crashed
router rsvp
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.
Command Syntax
router rsvp
no router rsvp
Parameters
None
Default
RSVP is started only if this command is executed.
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The command prompt changes from config to config-router, as illustrated below:
#configure terminal
(config)#router rsvp
(config-router)#
 
(config-router)#exit
(config)#no router rsvp
rsvp hello-interval
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.
Note: This is an interface-specific command and when not used, the global hello-interval state applies.
Use the no parameter with this command to return to the default hello interval value.
Command Syntax
rsvp hello-interval <1-65535>
no rsvp hello-interval
Parameter
<1-65535>
RSVP hello interval in seconds
Default
By default, RSVP hello interval is 2 seconds
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth0
(config-if)#rsvp hello-interval 110
 
(config)#interface eth0
(config-if)#no rsvp hello-interval
rsvp hello-receipt
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.
Command Syntax
rsvp hello-receipt
no rsvp hello-receipt
Parameters
None
Default
By default, rsvp hello receipt is disabled
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth0
(config-if)#rsvp hello-receipt
rsvp hello-timeout
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.
Command Syntax
rsvp hello-timeout <1-65535>
no rsvp hello-timeout
Parameters
<1-65535>
Time to receive a hello message, in seconds
Default
By default, hello-timeout value is 7 seconds
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth0
(config-if)#rsvp hello-timeout 550
 
(config)#interface eth0
(config-if)#no rsvp hello-timeout
rsvp keep-multiplier
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:
L >= (K + 0.5)* 1.5 * R
K = keep-multiplier
R = refresh timer
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.
Command Syntax
rsvp keep-multiplier <1-255>
no rsvp keep-multiplier <1-255>
Parameter
<1-255>
Set a value for the lifetime constant
Default
By default RSVP keep-multiplier value is 3
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth0
(config-if)#rsvp keep-multiplier 3
 
(config)#interface eth0
(config-if)#no rsvp keep-multiplier 3
rsvp refresh-time
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.
Command Syntax
rsvp refresh-time <1-65535>
no rsvp refresh-time <1-65535>
Parameter
<1-65535>
The duration for which messages are sent, in seconds
Default
By default, refresh interval is 30 seconds
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth0
(config-if)#rsvp refresh-time 5055
 
(config)#interface eth0
(config-if)#no rsvp refresh-time 5055
rsvp-path
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.
Command Syntax
rsvp-path PATHNAME
no rsvp-path PATHNAME
Parameter
PATHNAME
Name of the path
Default
By default, rsvp path is disabled
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-path mypath
(config-path)#
rsvp-trunk
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.
Note: The RSVP trunk’s name (TRUNKNAME) is limited to 32 characters.
Command Syntax
rsvp-trunk TRUNKNAME (ipv4|gmpls)
no rsvp-trunk TRUNKNAME
Parameters
TRUNKNAME
Name to use for the trunk
ipv4
IPv4 address family trunk
gmpls
GMPLS enabled trunk
Default
By default, rsvp trunk is disabled
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
The command prompt changes from config to config-trunk as illustrated below:
#configure terminal
(config)#rsvp-trunk mytrunk ipv4
(config-trunk)#
 
rsvp-trunk force-reoptimize
Use this command to force re-optimize a particular primary LSP. Re-optimization of the LSP must have been enabled with the reoptimize command.
Command Syntax
rsvp-trunk TRUNKNAME force-reoptimize
Parameters
TRUNKNAME
Name of the trunk
Default
NA.
Command Mode
Execute mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#rsvp-trunk t1 force-reoptimize
 
rsvp-trunk force-switchover-secondary
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.
Note: This command is supported on secondary configured tunnels and not on multiple secondary configured tunnels.
Command Syntax
rsvp-trunk TRUNKNAME force-switchover-secondary
Parameters
TRUNKNAME
Name of the trunk
force-switchover-secondary
 
Force switchover to secondary
Default
NA.
Command Mode
Execute mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#rsvp-trunk <Trunk-Name> force-switchover-secondary
 
rsvp-trunk-restart
Use this command to restart the RSVP trunk. This command “kills” an existing LSP and restarts the LSP setup process.
Command Syntax
rsvp-trunk-restart
Parameters
None
Default
By default, rsvp trunk restart is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#rsvp-trunk-restart
secondary ADMIN-GROUP-NAME
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.
Note: A link can be added to a specific Administrative Group via NSM. Refer to the Network Services Module Command Reference for details.
Use the no parameter to remove a previously set group from an administrative group list.
Command Syntax
secondary (include-any|include-all|exclude-any) ADMIN-GROUP-NAME
secondary (include-any|exclude-any) ADMIN-GROUP-NAME
no secondary (include-any|include-all|exclude-any) ADMIN-GROUP-NAME
no secondary (include-any|exclude-any) ADMIN-GROUP-NAME
Parameters
include-any
Include any attribute
include-all
Include all attribute
exclude-any
Exclude any attribute
ADMIN-GROUP-NAME
 
Administrative group name
Default
By default, secondary admin group name is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary exclude-any myadmingroup
 
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary include-any myadmingroup
 
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary include-all myadmingroup
secondary bandwidth
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.
Command Syntax
secondary bandwidth BANDWIDTH
no secondary bandwidth BANDWIDTH
no secondary bandwidth
Parameter
BANDWIDTH
<1-999>k for 1 to 999 kilobits/s
<1-999>m for 1 to 999 megabits/s
<1-100>g for 1 to 100 gigabits/s
Default
By default, bandwidth is 0 bits per second, which allows data to flow through but does not reserve bandwidth.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary bandwidth 100m
secondary cspf
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.
Note: CSPF server information is not signaled across session and hence sessions in transit and egress nodes will not be aware of the CSPF server. So, in multi CSPF scenarios, neighbor down event from a CSPF server restart all sessions irrespective of which CSPF server sessions were using.
Command Syntax
secondary cspf
Parameters
None
Default
By default, secondary cspf is enabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary cspf
secondary cspf-retry-limit
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.
Command Syntax
secondary cspf-retry-limit <1-65535>
no secondary cspf-retry-limit
Parameter
<1-65535>
The number of times CSPF should retry for this LSP
Default
By default, no retry limit for CSPF route calculations is configured, so the value is 0.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#secondary cspf-retry-limit 535
secondary cspf-retry-timer
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.
Command Syntax
secondary cspf-retry-timer <1-600>
no secondary cspf-retry-timer
Parameters
<1-600>
Timeout between successive retries, in seconds
Default
By default, no retry-timer configuration is defined for CSPF calculations, so the value is set to 0.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#secondary cspf-retry-timer 45
secondary filter
Use this command to set the filter to fixed or shared filter style for RSVP trunk.
The shared filter style identifies a shared reservation environment. It creates a single reservation into which flows from all senders are mixed.
The fixed filter style designates a distinct reservation. A distinct reservation request is created for data packets from a particular sender. The fixed filter style is also used style to prevent rerouting of an LSP and to prevent another LSP from using this bandwidth.
Use the no parameter to reset the configured filter to the default style.
Command Syntax
secondary filter (fixed|shared-explicit)
no secondary filter
Parameters
fixed
Use a Fixed Filter for this RSVP Trunk.
shared-explicit
Use a Shared Explicit Filter for this RSVP Trunk.
Default
By default, secondary filter is shared-explicit.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Usage
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary filter shared-explicit
secondary hold-priority
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.
Command Syntax
secondary hold-priority <0-7>
no secondary hold-priority
Parameter
<0-7>
Specify a value for hold priority
Default
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.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary hold-priority 2
secondary hop-limit
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.
Command Syntax
secondary hop-limit <1-255>
no secondary hop-limit <1-255>
no secondary hop-limit
Parameter
<1-255>
The number of acceptable hops
Default
By default, secondary hop limit is 255
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary hop-limit 23
secondary label-record
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.
Command Syntax
secondary label-record
no secondary label-record
Default
By default, secondary label record is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary label-record
secondary local-protection
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.
Command Syntax
secondary local-protection
no secondary local-protection
Parameters
None
Default
By default, secondary local protection is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#secondary local-protection
no secondary affinity
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.
Command Syntax
no secondary affinity
Parameters
None
Default
By default, no secondary affinity is disabled.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no secondary affinity
no secondary cspf
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.
Command Syntax
no secondary cspf
Parameters
None
Default
By default, secondary no cspf is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows using the no cspf command in Trunk mode to disable CSPF for the primary LSP.
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no secondary cspf
no secondary record
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.
Command Syntax
no secondary record
Parameters
None
Default
By default, routes are recorded
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#no secondary record
secondary path
Use this command to specify an RSVP path to be used.
Use the no parameter with this command to remove a configured RSVP path.
Command Syntax
secondary path PATHNAME
no secondary path
Parameters
PATHNAME
The name of the path to be used. PATHNAME is a string (name) used to identify an RSVP path defined for the node (refer to the rsvp-path command).
Default
By default, secondary path is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary path mypath
secondary-priority path
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.
Command Syntax
secondary-priority <1-5> path PATHNAME
no secondary-priority <1-5>
Parameters
<1-5>
Secondary Priority value.
PATHNAME
The name of the path to be used. PATHNAME is a string (name) used to identify an RSVP path defined for the node (refer to the rsvp-path command).
Default
Secondary-priority can only be configured along with a path. Other attributes can only be associated post this command.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk t1
(config-trunk)#secondary-priority 1 path sp1
(config)# rsvp-trunk t1
(config-trunk)#no secondary-priority 1
secondary-priority hold-priority
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.
Command Syntax
secondary-priority <1-5> hold-priority <0-7>
no secondary-priority <1-5> hold-priority <0-7>
no secondary-priority <1-5> hold-priority
Parameters
<1-5>
Secondary Priority value.
<0-7>
Specify a value for hold priority.
Default
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.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)# rsvp-trunk t1
(config-trunk)#secondary-priority 1 hold-priority 4
(config)# rsvp-trunk t1
(config-trunk)# no secondary-priority 1 hold-priority
 
 
secondary-priority setup-priority
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.
Command Syntax
secondary-priority <1-5> setup-priority <0-7>
no secondary-priority <1-5> setup-priority <0-7>
Parameters
<1-5>
Secondary Priority value.
<0-7>
Specify a value for hold priority.
Default
By default, setup value is 7 (the lowest).
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)# rsvp-trunk t1
(config-trunk)#secondary-priority 1 setup-priority 4
(config)# rsvp-trunk t1
(config-trunk)# no secondary-priority 1 setup-priority 4
 
 
secondary-priority label-record
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.
Command Syntax
secondary-priority <1-5> label-record
no secondary-priority <1-5> label-record
Parameters
<1-5>
Secondary Priority value.
Default
By default, label record is disabled for secondary-priority.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)# rsvp-trunk t1
(config-trunk)#secondary-priority 1 label-record
(config)# rsvp-trunk t1
(config-trunk)# no secondary-priority 1 label-record
 
 
secondary-priority hop-limit
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.
Command Syntax
secondary-priority <1-5> hop-limit <1-255>
no secondary-priority <1-5> hop-limit <1-255>
Parameters
<1-5>
Secondary Priority value.
<1-255>
The number of acceptable hops.
Default
By default, hop limit is 255.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)# rsvp-trunk t1
(config-trunk)#secondary-priority 1 hop-limit 123
(config)# rsvp-trunk t1
(config-trunk)# no secondary-priority 1 hop-limit 123
 
secondary-priority bandwidth
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.
Command Syntax
secondary-priority <1-5> bandwidth BANDWIDTH
no secondary-priority <1-5> bandwidth BANDWIDTH
Parameters
<1-5>
Secondary Priority value.
BANDWIDTH
<1-999>k for 1 to 999 kilobits/s
<1-999>m for 1 to 999 megabits/s
<1-100>g for 1 to 100 gigabits/s
 
Default
By default, bandwidth is 0 bits per second, which allows data to flow through but does not reserve bandwidth.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)# rsvp-trunk t1
(config-trunk)#secondary-priority 1 bandwidth 100m
(config)# rsvp-trunk t1
(config-trunk)# no secondary-priority 1 bandwidth 100m
 
 
secondary record
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.
Command Syntax
secondary record
Parameters
None
Default
By default, routes are recorded
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary record
secondary retry-limit
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.
Command Syntax
secondary retry-limit <1-65535>
no secondary retry-limit
Parameter
<1-65535>
The set number of times the system should try setting up the LSP
Default
By default, the retry-limit value is 0 so the trunk and session try to create the LSP indefinitely.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary retry-limit 256
secondary retry-timer
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.
Command Syntax
secondary retry-timer <1-6OO>
no secondary retry-timer
Parameter
<1-6OO>
Interval after which the system should retry setting up the LSP, in seconds
Default
By default, retry time is 30 seconds
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary retry-timer 12
secondary reuse-route-record
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.
Command Syntax
secondary reuse-route-record
no secondary reuse-route-record
Parameters
None
Default
By default, secondary reuse route record is disabled
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary reuse-route-record
secondary setup-priority
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.
Command Syntax
secondary setup-priority <0-7>
no secondary setup-priority
Parameters
<0-7>
The priority value
Default
By default, setup value is 7 (the lowest).
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary setup-priority 2
secondary traffic
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.
Command Syntax
secondary traffic (guaranteed|controlled-load)
no secondary traffic
Parameters
guaranteed
Guaranteed traffic
controlled-load
Controlled load traffic
Default
Controlled load is the default traffic type.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#secondary traffic guaranteed
snmp restart rsvp
Use this command to restart SNMP in Resource Reservation Protocol -Traffic Engineering (RSVP-TE)
Command Syntax
snmp restart rsvp
Parameters
None
Default
By default, snmp restart rsvp is disabled
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#snmp restart rsvp
 
 
to A.B.C.D
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.
Command Syntax
to A.B.C.D
no to
Parameters
None
Default
The operator must specify an egress for LSP initialization to begin.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk mytrunk
(config-trunk)#to 10.10.0.5
update-type
Use this command to change the method of updating attributes for sessions (primary/ secondary) for this trunk.
If make-before-break is configured (default type), a new LSP is created for each attribute update. When the new LSP becomes operational, the original LSP is torn down.
If break-before-make is configured, the existing LSP is torn down and restarted for each attribute update.
Use the no parameter with this command to remove an update type.
Command Syntax
update-type (make-before-break|break-before-make)
no update-type
Parameters
make-before-break
 
Make before break update
break-before-make
 
Break before make update
Default
By default, make-before-break types of updates are carried out.
Command Mode
Trunk mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#update-type break-before-make
 
#configure terminal
(config)#rsvp-trunk T1
(config-trunk)#update-type make-before-break