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

Configuring Ingress PE Redundancy

You configure one or more PEs as part of a backup PE group to enable ingress PE redundancy. You do this by configuring the IP addresses of the backup PEs (at least one backup PE is required) and the local IP address used by the local PE.

Note: You must also configure a full mesh of P2P LSPs between the primary and backup PEs. You must also configure these LSPs with BFD. These configuration steps are not discussed in this section. For more information about mesh LSPs and BFD configuration, see the JUNOS MPLS Applications Configuration Guide.

To configure ingress PE redundancy for multicast traffic streams, include the backup-pe-group statement:




backup-pe-group group-name {

backups [ addresses ];

local-address address;
}

For a list of the hierarchy levels at which you can include this statement, see the statement summary section for this statement.

After you configure the ingress PE redundancy backup group, you must also apply the group to a static route on the PE. This makes sure that the static route is active (installed in the forwarding table) when the local PE is the designated forwarder for the configure backup PE group. You can only associate a backup PE group with a static route that has the p2mp-lsp-next-hop statement configured. For more information about the p2mp-lsp-next-hop statement, see the JUNOS MPLS Applications Configuration Guide.

You must also configure a full mesh of P2P LSPs between the PEs in the backup group. A full mesh is required so that each member of the group can make an independent decision about the health of the other PEs and determine the designated forwarder for the group. This configuration also requires a BFD configuration for the LSP and the associate-backup-pe-groups statement. An LSP with this statement set monitors the health of the router at the other end of the LSP. You can configure multiple backup PE groups that contain the same router's address. Failure of this LSP indicates to all of these groups that the destination PE router is down. So the associate-backup-pe-groups statement is not tied to any specific group but applies to all groups that are monitoring the health of the LSP to the remote address.

If there are multiple LSPs with the associate-backup-pe-groups statement to the same destination PE, then the local router picks the first LSP to that PE for detection purposes.

Note: We do not recommend configuring multiple LSPs to the same destination. If you do, you should make sure that the LSP parameters (for example, liveliness detection) are similar in order to avoid false failure notification even when the remote PE is up.

For more information about the associate-backup-pe-groups statement, see the JUNOS MPLS Applications Configuration Guide.

For a complete example of ingress PE redundancy configuration, see Example: Ingress PE Redundancy.

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