[Contents] [Prev] [Next] [Index] [Report an Error]

fate-sharing

Syntax



fate-sharing {
group group-name;
cost value;
from address <to address>;
}

Hierarchy Level



[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information

Statement introduced before JUNOS Release 7.4.

Description

Specify a backup path in case the primary path becomes unusable.

You specify one or more objects within a group. 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 LSP until the next CSPF reoptimization. The fate-sharing database does affect fast-reroute detour path computations.

Options

group group-name—Each fate-sharing group must have a name, which can be up to 32 characters long and can contain letters, digits, periods (.) and hyphens (-). You can define up to 512 groups.
cost value—Cost assigned to the group.
from address—Address of ingress router.
to address—Address of egress router. For point-to-point link objects, you must specify both a from and a to address.

Usage Guidelines

See the JUNOS MPLS Applications Configuration Guide.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

[Contents] [Prev] [Next] [Index] [Report an Error]