fate-sharing
Syntax
fate-sharing {
group group-name {
cost value;
from address <to address>;
use-for-post-convergence-lfa; }
}
Hierarchy Level
[edit logical-systems logical-system-name routing-options], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit routing-options], [edit routing-instances routing-instance-name routing-options]
Description
Specify a backup path in case the primary path becomes unusable.
You specify one or more objects with common characteristics within a group. All objects are treated as /32 host addresses. The objects can be a LAN interface, a router ID, or a point-to-point link. Sequence is insignificant.
Changing the fate-sharing database does not affect existing established LSPs until the next CSPF reoptimization. The fate-sharing database does affect fast-reroute detour path computations.
Options
cost value—Cost
assigned to the group.
Range: 1 through 65,535
Default: 1
from address—Address of
the router or address of the LAN/NBMA interface. For example, an Ethernet
network with four hosts in the same fate-sharing group would require
you to list all four of the separate from addresses in
the group.
group group-name—Each
fate-sharing group must have a name, which can have a maximum of 32
characters, including letters, numbers, periods (.), and hyphens (-).
You can define up to 512 groups.
to address—(Optional)
Address of egress router. For point-to-point link objects, you must
specify both a from and a to address.
use-for-post-convergence-lfa—Use this fate-sharing group as a constraint for the backup path computed by topology-independent loop-free alternate (TI-LFA).
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.