Contents

Configuring failover groups· 1

About failover groups· 1

Failover group operating mechanism·· 1

Failover group types· 1

Restrictions and guidelines: failover group configuration· 1

Configuring a failover group· 1

Display and maintenance commands for failover groups· 2

Configuring failover groups

About failover groups

A failover group backs up services (such as NAT) between two CPUs to ensure service continuity. A CPU is called a node in the failover group feature.

Failover group operating mechanism

A failover group contains one primary node and one secondary node. When a failover group is used by a service module, the primary node processes services and backs up service data to the secondary node. The secondary node does not process services, but it takes over the services when the primary node fails. When the primary node is recovered, traffic is switched back to the primary node.

For more information about the service modules that can use a failover group, see the configuration guides for specific modules.

Failover group types

A failover group can be automatically created by the system or manually configured.

Automatic failover group

When a security service module is installed, the system automatically creates a failover group for the security engine on the security service module. The automatic failover group for a security engine uses the security engine as the primary node. Typically, an automatic failover group does not have a secondary node and does not back up services. If multiple security engines are available on the device, you can specify a security engine for a specific service. When the security engine fails, the system automatically allocates services evenly among the other security engines in the same security engine group. For more information about security engines and security engine groups, see the context feature in Virtual Technologies Configuration Guide.

Manual failover group

A manual failover group is manually created, to which you can bind one primary node and one secondary node.

Restrictions and guidelines: failover group configuration

As a best practice, assign two CPUs with similar performance on different cards to a failover group. This operation ensures service continuity after a primary and secondary node switchover.

Configuring a failover group

1.     Enter system view.

system-view

2.     Create a failover group and enter its view.

failover group group-name

By default, one or multiple automatic failover groups prefixed with AutoBackup exist, and no manual failover groups exist.

3.     Assign a node to the failover group.

In standalone mode:

bind slot slot-number cpu cpu-number { primary | secondary }

In IRF mode:

bind chassis chassis-number slot slot-number cpu cpu-number { primary | secondary }

By default, a failover group does not contain nodes.

The primary and secondary nodes in a failover group cannot be the same one. Different failover groups cannot share the same primary node.

Display and maintenance commands for failover groups

Execute display commands in any view.

‌