|
|
|
By default, ClusterXL only monitors two VLANS for failure detection and failover. These are the highest and lowest VLAN tags defined for a given interface.
For example, if the topology for interface eth1 includes several VLAN tags in the range of eth1.10 to eth1.50, ClusterXL only monitors VLANs eth1.10 and eth1.50 for failure. Failures on any of the other VLANs are not detected in the default configuration.
|
Note - The command line option |
When both the highest and lowest VLANs fail, all the VLANs are considered down, and a failover occurs. This means that if a VLAN which is not listed as the highest or lowest goes down, the trunk is still considered "up", and no failover occurs.
There are instances in which it would be advantageous to monitor all the VLANs in the trunk, not just the highest and lowest, and initiate a failover when any one of the VLANs goes down.
To enable monitoring of all VLANs, enable the fwha_monitor_all_vlan property in $FWDIR/boot/modules/fwkern.conf. Change the property to fwha_monitor_all_vlan=1.
The default ClusterXL Control Protocol transport mode is multicast. Use the cphaconf set_ccp command to configure broadcast or multicast mode for the cluster.
To enable broadcast or multicast mode:
cphaconf set_ccp {broadcast|multicast} In VSLS VSX Clusters of version R80.10 and higher, changing the CoreXL configuration or running the cphastop command in the context of VS0 results in failover of all the Active Virtual Systems on that VSX Cluster Member. This behavior is by design. Active Virtual Systems on other VSX Cluster Members do not fail over.