Working with Sync Bonds

The Sync Interface is a special Bond used for these and other synchronization and control tasks:

• To send CCP packets to other SGMs
• To share policies and configuration files amongst SGMs
• Connection state synchronization
• Packet forwarding
• Firewall synchronization
• Daemon synchronization
• Monitor and control commands (gclish, asg) that get information from many SGMs

A Sync Interface has one or two slave interfaces, based on the number of SSMs in each Chassis. The system automatically creates the slave interfaces based on this algorithm:

Notes:

• A Chassis with one SSM always uses eth1-Sync. eth2-Syncs not assigned.
• A chassis with two or more SSMs always uses these slave interfaces:
  • eth1-Sync
  • eth2-Sync
  • Sync ports on SSM3 and SSM4 are not used when there are more than two SSMs
• The system automatically creates the Sync Bond during installation and assigns these IP addresses:
  • SGM1_1 - 192.0.2.1
  • SGM1_12 - 192.0.2.14
  • SGM2_1 - 192.0.2.15
  • SGM2_12 - 192.0.2.28

  No manual configuration is necessary.

• The system automatically assigns the Sync slave to port 8 on SSM1 and SSM2.
• The system sets the Sync slave port speed to 10 Gb by default. We recommend that your do not change this parameter.
• Sync Bonds support both LR and SR transceivers.
• The Sync Bond uses the XOR mode.
• The default network (192.0.2.X) is defined by the applicable RFC as a private network for documentation. It is unlikely to cause collisions with user networks.

Limitations:

• LACP is not supported.
• VLANs are not supported for Sync slave interfaces.
• A Sync Bond can have up to two slave interfaces.
• Sync ports cannot be changed to data ports. This is true for both Single and Dual Chassis systems.