Print | Rate this content

Advisory: HP Network Teaming - Network Traffic May Fail Between Teamed HP NICs When a Network Team is Captured and Deployed Across Many Servers or a VC Profile is Swapped Because the System Image Registry Contains the Same Team MAC Address

SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: c03087066

Version: 1

Advisory: HP Network Teaming - Network Traffic May Fail Between Teamed HP NICs When a Network Team is Captured and Deployed Across Many Servers or a VC Profile is Swapped Because the System Image Registry Contains the Same Team MAC Address
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.

Release Date: 2011-11-14

Last Updated: 2011-11-14


DESCRIPTION

If a NIC Team is created using Network Configuration Utility (NCU) and the system image is captured and deployed across many servers on the same network, the system image registry will contain the same Team MAC address and the network traffic may not flow between NIC teams. A Virtual Connect (VC) profile also contains the Team MAC address; therefore will also have this same issue.

If a VC profile is swapped, network traffic will not flow between any teamed Network Interface Controllers (NICs) installed in an HP c-Class BladeSystem server if the NIC team is paired prior to performing the VC profile swap. When this occurs, errors and timeouts may be observed when attempting to ping the network. This can occur because the teamed MAC address that is reported by VC is not a member MAC address. The HP Network Configuration Utility for Windows (NCU) will incorrectly report a "transmit MAC addresses" message for some NICs in the team.

When a NIC Team is created by using the Network Configuration Utility (NCU), the team MAC address used is the MAC address of one of the component NICs or an LAA, if used, is applied. This Team MAC address is written to the registry where it will be retrieved and set during any subsequent Teaming driver initialization whether it be a disabling/enabling of the Local Area Connection or a system reboot.

For example, if a Team is created and uses 00-00-01-33-44-32 as the Team MAC address, the value 00-00-01-33-44-32 is written to the registry. Upon the next driver initialization, 00-00-01-33-44-32 will be read from the registry and set as the Team MAC address. If this image is captured and deployed to 100 servers, all 100 servers will attempt to use 00-00-01-33-44-32 as the Team MAC address and this will result in an error since MAC addresses must be unique on a layer 2 network.

SCOPE

Any HP teamed NIC using the HP Network Configuration Utility for Windows (all versions) on the following operating systems:

  • Windows Server 2003
  • Windows Server 2003 x64
  • Windows Server 2008
  • Windows Server 2008 x64
  • Windows Server 2008 R2

IMPORTANT: This includes NIC teams configured in a Virtual Connect environment (all firmware versions).

RESOLUTION

To ensure network traffic flows properly between NICs that are configured for NIC teaming using the Network Configuration Utility for Windows (NCU), the operating system image that includes the teaming information should NOT be captured and deployed to a different server configured with different NICs. The NIC team must be initialized using the same NICs as when the team was originally created.

In a VC environment, perform either of the following actions:

When creating a network team, do not include the network team in a VC profile.

OR

After the VC profile swap occurs, dissolve the network team and recreate another network team.



RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HP Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: http://www.hp.com/go/myadvisory

NAVIGATION TIP : For hints on navigating HP.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document .

SEARCH TIP : For hints on locating similar documents on HP.com, refer to the Search Tips document .

To search for additional advisories related to Network Teaming NICs following search string:

+Advisory +ProLiant -"Software and Drivers" +NCU

KEYWORDS: NCDE, network teaming, VC, NCU, timeouts, errors, MAC address


Hardware Platforms Affected: HP BladeSystem Dual NC370i Multifunction Network Adapter, HP NC325m PCI Express Quad Port Gigabit Server Adapter, HP NC326i Integrated Dual Port PCI Express Gigabit Server Adapter, HP NC373i Integrated Multifunction Gigabit Server Adapter, HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter, HP NC522m Dual Port 10GbE Multifunction BL-c Adapter, HP NC532i Dual Port 10GbE Multifunction BL-c Adapter, HP NC532m Dual Port 10GbE Multifunction BL-c Adapter, HP NC542m Dual Port Flex-10 10GbE BL-c Adapter, HP NC550m 10Gb 2-port PCIe x8 Flex-10 Ethernet Adapter, HP NC551i Dual Port FlexFabric 10Gb Network Adapter, HP NC551m Dual Port FlexFabric 10Gb Converged Network Adapter, HP NC552m 10Gb 2-port Flex-10 Ethernet Adapter, HP NC553i 10Gb 2-port FlexFabric Converged Network Adapter, HP NC553m 10Gb 2-port FlexFabric Adapter, HPE Virtual Connect Enterprise Manager Software
Operating Systems Affected: Microsoft Windows Server 2003, Microsoft Windows Server 2003 Enterprise x64, Microsoft Windows Server 2008, Microsoft Windows Server 2008 R2, Microsoft Windows Server 2008 R2 Enterprise Edition
Software Affected: Not Applicable
Support Communication Cross Reference ID: IA03087066
©Copyright 2016 Hewlett Packard Enterprise Company, L.P.
Hewlett Packard Enterprise Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HPE nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett Packard Enterprise Company and the names of Hewlett Packard Enterprise Company products referenced herein are trademarks of Hewlett Packard Enterprise Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!