Symantec Continuous Availability out of the box does NOT support teams of NICs and requires additional steps when installing with teamed NICs present. Teams of NICs can appear in a large matrix of configurations covering cardinality, manufacturer, management software, load balancing type and fault tolerance type.
If there is a requirement to run Continuous Availability on a server that uses teamed NICs, the following procedure should be used. An exception to this rule are NIC's teamed using Broadcom or HP teaming software on Windows Server 2008 and later. For Windows Server 2008 and later, see Knowledgebase article 2214 - Symantec Continuous Availability 2011 Installation When Using Broadcom NICs or HP NICs With Broadcom Chipset Capable Teaming on Windows Server 2008 and Later.
Note: This does not guarantee a successful installation of the full Symantec Continuous Availability product but should allow installation of the Symantec Continuous Availability Packet Filter driver on teamed NICs.
On the server designated to be the Primary active server running with teamed NICs:
- Dissolve the NIC team using the vendor supplied software.
- Install Continuous Availability including the Symantec Continuous Availability Engine Packet Filter.
- Check that the packet filter is installed on all NICs making sure each Principal (Public) connection has the packet filter enabled and each Symantec Channel connection has it disabled.
- Recreate the teamed NICs using the vendor software supplied.
- If you intend to upgrade or uninstall Symantec Continuous Availability 2011 you must first break the NIC team prior upgrading or uninstalling Symantec Continuous Availability 2011. Failure to break the NIC team prior to upgrading or uninstalling Symantec Continuous Availability 2011 will result in a hung state.
- The NIC team must be broken prior to performing a backup of the System State for restoration to a remote machine.
Continuous Availability REFID-2161