Fate-Sharing - Juniper JUNOS OS 10.3 - SOFTWARE Manual

Related
Documentation

fate-sharing

Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
Copyright © 2010, Juniper Networks, Inc.
autonomous-system on page 1734
local-as on page 1847
Enabling Multiprotocol BGP
fate-sharing {
group group-name {
cost value;
from address <to address>;
}
}
[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]
Statement introduced before Junos OS Release 7.4.
Specify groups of objects that share characteristics resulting in backup paths to be used
if primary paths fail. All objects are treated as
more objects within a group. The objects can be LAN interfaces, router IDs, or
point-to-point links. The sequence is insignificant.
—Cost assigned to the group.
cost value
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
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.
—(Optional) Address of egress router. For point-to-point link objects, you must
to address
specify both a from and a
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Configuring the Ingress Router for MPLS-Signaled LSPs
Chapter 73: Configuration Statements for Layer 3 Protocols
host addresses. You specify one or
/32
addresses in the group.
from
to address.
1789