Group of Bonds

See the R80.40 Next Generation Security Gateway Guide - Chapter Kernel Debug on Security
Gateway.
The kernel debug shows:
n A physical slave interface goes down/up.
n A Bond interface goes down/up (regardless of a change in the Cluster Member's state).
n A Group of Bonds goes down/up.

Note - These logs are generated only once per event.

Limitations
Specific limitations apply to a Group of Bonds.

List of Limitations

n The maximal length on the text string "<Name for Group of Bonds>" is 16 characters.
n The maximal length on this text string is 1024 characters:

<Name for Group of Bonds>:<List of all Bonds in this Group

separated by comma>

n You can configure the maximum of five Groups of Bonds on a Cluster Member or Virtual System.
n You can configure the maximum of five Bond interfaces in each Groups of Bonds.
n Group of Bonds feature does support Virtual Switches and Virtual Routers. Meaning, do not
configure Groups of Bonds in the context of these Virtual Devices.
n Group of Bonds feature supports only Bond interfaces that belong to the same Virtual System.
You cannot configure bonds that belong to different Virtual Systems into the same Group of
Bonds.
You must perform all configuration in the context of the applicable Virtual System.
n Group of Bonds feature does support Sync interfaces (an interface on a Cluster Member, whose
Network Type was set as Sync or Cluster+Sync in SmartConsole in cluster object).
n Group of Bonds feature does support Bridge interfaces.
n If a Bond interface goes down on one Cluster Member, the "cphaprob show_bond_groups"
command (see "Viewing Bond Interfaces" on page 210) on the peer Cluster Members also
shows the same Bond interface as DOWN.
This is because the peer Cluster Members stop receiving the CCP packets on that Bond interface
and cannot probe the local network to determine that their Bond interface is really working.
n After you add a Bond interface to the existing Group of Bonds, you must install the Access Control
Policy on the cluster object.
n After you remove a Bond interface from the existing Group of Bonds, you must install the Access
Control Policy on the cluster object.

ClusterXL R80.40 Administration Guide      |      130