| |
|
|
standby-for
Configures a tunnel to be standby for the specified tunnels.
Syntax: [no] standby-for tunnelNames
tunnelNames
Specifies one or more tunnel names for this tunnel to be configured as 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-for 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 It is recommended that you use the standby-for command for configuring standby tunnels in an MPLS TE ECMP environment. The standby command is primarily supported for backwards compatibility.
All specified tunnels must already exist. 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 command is used in this tunnels context, no attempt is made for this tunnel to be disjoint with another 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.
Expressions are supported delineated by square brackets that may contain a set of single characters or a range. The following two examples represent the same values: nyc[0123] or nyc[0-3]. A full set of wild card expressions are not currently supported.
Use the standby-for command, specifying one or more pre-existing tunnels this tunnel will protect, in any tunnel configuration mode to specify the tunnels this standby will attempt to be disjoint with.
Use the no standby-for command to delete the standby for configuration for this tunnel context.
Use the show mpls te tunnel command to display standby configuration information.
Factory Default: N/A.
Command Mode: Traffic engineering parameter-set, traffic engineering tunnel defaults, and traffic engineering tunnel-name.
Example 1: In the following example, the oc48toBosStdBy tunnel is configured to be disjoint and standby with the oc48toBos1, oc48toBos2, oc48toBos3, and oc48toBos4 tunnels:
router(config)#mpls te ospf
router(config-te)#tunnel oc48toBosStdBy
router(config-te-tunnel)#standby-for oc38toBos2 oc38toBos3 oc38toBos4 oc38toBos1
router(config-te-tunnel)#end
router#
Example 2: In the following example, the oc48toBosStdBy tunnel standby-for configuration is removed:
router(config)#mpls te ospf
router(config-te)#tunnel oc48toBosStdBy
router(config-te-tunnel)#no standby-for
router(config-te-tunnel)#end
router#
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%20Commands91.html
Last Updated: 12/19/04 at 14:56:07