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
Last modified date: 07-13-2023