
standby
Configures standby tunnels.
Syntax: standby [non-disjoint]
no standby
Description: A standby LSP is a pre-signaled LSP that replaces a primary when the standby-trigger configuration is met for the number of composite-paths member failures to the protected egress. A tunnel configured as standby attempts to use a link disjoint path from the active primary tunnel or equal cost composite-paths to the same egress. A standby tunnel only carries traffic activated by the standby-trigger configuration, even if the standby tunnel has a lower metric value relative to another primary. Should the primary tunnel reroute and make the standby link disjoint property no longer valid, resilience will activate and recompute a new disjoint standby path if possible.
NOTE This command is supported for purposes of backward compatibility. It is recommended that you use the standby-for command for configuring standby tunnels in an MPLS TE ECMP environment.
A standby tunnel can be associated with one or more specific tunnels to the same or different egresses using the standby-for command.
The standby tunnel is by default link disjoint relative to the primary tunnel. If the non-disjoint option is specified, path computation is based solely on the constraints configured for the tunnel itself, just like any other tunnel. With non-disjoint specified, links used by the primary tunnel may be included in the standby tunnel.
A primary path can be protected by both the fast reroute and standby features, but a standby tunnel can not be protected by fast reroute. The inuse-resilience, node-disjoint, and srlg configurations normally associated with fast reroute, are also valid configurations for standby tunnels.
Use the standby command in any tunnel related command mode to configure that command mode for standby tunnels. Use the no standby command in that mode to remove the standby configuration.
Use the show mpls te tunnel command to display standby configuration information.
Factory Default: None.
Command Mode: Traffic engineering parameter-set, traffic engineering tunnel defaults, and traffic engineering tunnel-name.
Example 1: The following example configures tunnel defaults to set the default tunnel for standby and node-disjoint:
router>enable
router#configure terminal
router(config)#mpls traffic-engineering isis
router(config-te)#tunnel default
router(config-te-tunnel-default)#standby
router(config-te-tunnel-default)#node-disjoint
router(config-te-tunnel-default)#exit
router(config-te)#
Example 2: The following example configures tunnel defaults to set the default tunnel for standby non-disjoint:
router>enable
router#configure terminal
router(config)#mpls traffic-engineering isis
router(config-te)#tunnel default
router(config-te-tunnel-default)#standby non-disjoint
router(config-te-tunnel-default)#exit
router(config-te)#
Related Commands: show mpls te tunnel
Copyright © 2004
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori, Composite Links, SSR, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: TE%20Commands.fm
HTML File Name: TE%20Commands90.html
Last Updated: 12/19/04 at 14:56:07