| |
|
|
disjoint-with
Configures tunnels in this MPLS TE context to be disjoint with the specified tunnels.
Syntax: disjoint-with tunnelNames
no disjoint-with
tunnelNames
Specifies one or more tunnels that tunnels in this MPLS TE context will be disjoint with.
Description: Disjoint tunnels have no common links or interfaces. By default, no consideration is given to whether tunnels in the TE- ECMP set are disjoint or not. Any given LSP can be configured to be disjoint with one or more other LSPs. If an LSP is configured to be disjoint with a second LSP, and that second LSP is not already configured to be disjoint with a third LSP, than the second LSP can be rerouted to make a pair of disjoint paths feasible. In all other cases, failure to find a disjoint path will not cause the second LSP to reroute. Tunnels configured to be disjoint will be identified as non-disjoint in show commands when the disjoint configuration is not feasible. Tunnels configured to be disjoint need not go to the same egress and therefore need not be part of a composite-paths.
All specified tunnels must already exist and can not be deleted until any disjoint relationship using this command is removed. If a specified tunnel is not already specified as disjoint with another tunnel, and it is not fully disjoint with this specification, an attempt will be made to reroute the specified tunnel to achieve full or greater disjointness.
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.
The disjoint-with command negates any previous non-disjoint configuration for this tunnel context.
Use the disjoint-with command, specifying one or more tunnel names, in any MPLS TE command mode to configure tunnels appropriate to the command mode context to be disjoint with the specified tunnels. Tunnels specified are not required to be members of the same composite-paths. In other words, tunnels destined for a different egress can be specified as disjoint.
Use the no disjoint-with command to delete the current disjoint with configuration for this tunnel context. The CLI ignores this command if there is currently no disjoint-with configuration to delete.
Factory Default: None.
Command Mode: Traffic engineering parameter-set, traffic engineering tunnel defaults, and traffic engineering tunnel-name.
Example 1: In the following example, the oc48toBos1 tunnel is configured to be disjoint with the oc48toBos2, oc48toBos3, and oc48toBos4 tunnels using the disjoint-with command in tunnel name mode:
router(config)#mpls te ospf
router(config-te)#tunnel oc48toBos
router(config-te-tunnel)#disjoint-with oc38toBos2 oc38toBos3 oc38toBos4
router(config-te-tunnel)#end
router#
Example 2: In the following example, the previously configured disjoint-with configuration is deleted for the oc48toBos1:
router(config)#mpls te ospf
router(config-te)#tunnel oc48toBos
router(config-te-tunnel)#no disjoint-with
router(config-te-tunnel)#end
router#
Related Commands: multipath
non-disjoint
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%20Commands19.html
Last Updated: 12/19/04 at 14:56:07