You can configure network redundancy through port bonding on 4-port DNS/DHCP Server appliances only.
For most scenarios, BlueCat recommends enabling network redundancy using Address Manager when adding or replacing a server (for details, refer to Enabling DNS/DHCP Server network redundancy from the Address Manager user interface). However, if you want to configure port bonding with VLAN tagging, BlueCat recommends configuring a bonding interface from the DNS/DHCP Server Administration Console.
Attention: You must configure bonding prior to placing the DNS/DHCP Server under Address Manager control. Once the DNS/DHCP Server is taken under Address Manager control, bonding can't be created and the Primary Service IP address can't be changed.
Attention: Customers that require VLAN tagging on top of port bonding must set VLANs immediately after configuring the bonding interface. If you have configured VLAN interfaces to your DNS/DHCP Server before enabling port bonding, refer to Enabling port bonding when VLANs are already created.
Supported bonding modes
DNS/DHCP Server appliances support:
- Failover— Active/Backup bonding where only one interface in the bond is active (Primary). This allows the secondary interface (eth3) to take over transparently if the Primary interface (eth0) fails.
- Load Balancing—Active/Active bonding using industry
standard 802.3ad aggregation protocol, where aggregation groups share the same speed and
duplex settings. Each interface shares the throughput and each interface is active;
neither interface is a primary nor a secondary.Note: Active/Active (802.3ad) load balancing must be enabled from the Address Manager user interface when adding or replacing a DNS/DHCP Server. If enabling Active/Active load balancing, you must first enable Active/Active on the DNS/ DHCP Server from Address Manager, then configure Active/Active (802.3ad) on your network switch. This protects against loss of connectivity with the DNS/DHCP Server.