In a network using tagged VLAN configuration or NIC teaming software, the VCS NIC agent may monitor an incorrect network interface, if the interfaces have same MAC address.

Problem

In tagged VLAN network configurations, there are multiple independent logical network interfaces that are created within a physical network interface or a teamed network interface. Each of these logical network interfaces may have the same MAC address. During the application service group configuration, the VCS application configuration wizard enables you to select an interface for each VCS cluster system and internally sets the MAC address of the selected interface as the value of the "MACAddress" attribute of the NIC agent. While selecting the interface, if you choose any of the logical interfaces that share the MAC address with other logical interfaces, then the NIC agent may begin to monitor an interface other than the selected one. 

This issue occurs because the NIC agent uses the MAC address of the interface to monitor and determine the status. Since the MAC address of all the logical interfaces is identical, the agent may fail to identify the selected interface.
 

Error Message

The NIC agent will not probe or come online by default in this configuration.

Cause

In a network using tagged VLAN configuration, the VCS NIC agent may monitor an incorrect network interface if the interfaces have same MAC address.

Solution

The NIC agent currently uses the MAC address specified in the "MACAddress" attribute to monitor and determine the interface status. The agent is now enhanced to use either the MAC address or the interface name to monitor and determine the status.To monitor the interface based on its name, you must edit the "MACAddress" attribute of the NIC agent, after you configure the application service group. Use the VCS Java Console to edit the "MACAddress" attribute and enter the interface name instead of the MAC address. You must enter the interface name in double quotes. For example, MACAddress = "InterfaceName"

This issue has been identified and a private fix is available below.

Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.

This hotfix is available in 5.1 SP2 CP20 for SFW-HA and VCS.

SFW-HA : https://sort.Veritas.com/patch/detail/8345

VCS for Windows : https://sort.Veritas.com/patch/detail/8344
 

 The Hotfix is also available for SFW-HA version 6.0.2

     https://sort.Veritas.com/patch/detail/8052

Please contact Veritas Technical services if a Publix hotfix is not available for your version.

Applies To

Storage Foundation for Windows High Availability versions 5.1 SP2 and 6.x versions.

Veritas Cluster Server 5.1 SP2 and 6.x versions.

This updated NIC agent will work with native Windows 2012 teaming modes of Static and Switch independent.

On Windows 2008 and Windows 2012, third party NIC teaming may cause same symptoms, address by this patch.

This patch is yet not integrated with VCS Wizards.

 Issue may occur with native Windows teaming software or third party teaming software.