[Prev][Next][Report an Error]

Configuring FEB Redundancy Groups with Quick Configuration

To improve interface availability, configure Forwarding Engine Board (FEB) redundancy by using FEB redundancy groups. A FEB redundancy group is a named collection of two or more FEBs.

Select check boxes to include FEBs in the group. Each FEB can belong to only one redundancy group. Each group must include a backup FEB and can optionally include a primary FEB.

Alternatively, use the edit chassis redundancy feb redundancy-group < group-name> command to create or edit redundancy groups.

Note: A manual switchover to any FEB is even faster than an automatic failover to a primary FEB. To perform a manual switchover, select Monitor>Chassis>FEB Redundancy.

Table 97: FEB Redundancy Quick Configuration Fields

Field	Values
Name	A unique name of up to 39 characters.
No Auto-Failover	Automatic failover is enabled by default. Select this check box to disable automatic failover and prevent an automatic failover to the backup FEB if an active FEB in the redundancy group fails. For example, you might disable auto-failover before removing a FEB.
Yes	Select this check box to include the FEB in the redundancy group as neither the primary nor backup FEB.
Primary	Select this check box to specify this as the primary FEB for this redundancy group. Each FEB redundancy group can, optionally, contain one primary FEB. Automatic failover to a primary FEB is faster and results in less packet loss than a failover to a nonprimary FEB because the state of the backup FEB is aligned with the primary FEB. The duration of traffic loss during an automatic failover to a primary FEB is less than 10 seconds (if the backup FEB is ready before the switchover), while failover to a nonprimary FEB might take up to several minutes (depending on the number of interfaces and size of the routing table). Note: If the redundancy group has a primary FEB, a failover to a nonprimary FEB causes the backup FEB to reboot and take the interfaces on the failed FEB offline. If the group does not have a primary, the backup FEB does not reboot, and the interfaces on the failed FEB remain online during failover. This situation might result in black hole traffic during the failover. If black hole traffic is a concern, designate one of the FEBs in the group as primary.
Backup	You must specify one (and only one) FEB in the redundancy group as the backup for all the FEBs in the group. Automatic failover to the backup FEB occurs if any FEB in the redundancy group fails or is removed. You can design your redundant FEB configuration to provide backup on a one-to-one basis, or you can provide one backup for multiple FEBs. After a failover or switchover, a backup FEB is no longer available for the redundancy group. After resolving the problem that caused the failover, you can manually revert to the primary FEB from the Monitor>Chassis>FEB Redundancy page. Note: You cannot specify a connection between an FPC and a backup FEB.

To apply the configuration, click Apply or OK.

[Prev][Next][Report an Error]