HP ProLiant/tc Series and HP BladeSystem Servers - Team Members Are Not Rejoining NIC Teams Following Upgrade to HP ProLiant Support Pack 7.50 or 7.51 in a Microsoft Windows Environment

Support Center

HP ProLiant/tc Series and HP BladeSystem Servers - Team Members Are Not Rejoining NIC Teams Following Upgrade to HP ProLiant Support Pack 7.50 or 7.51 in a Microsoft Windows Environment ISSUE: Following upgrading to the HP ProLiant Support Pack version 7.50 or 7.51 in a Microsoft Windows environment, NIC team members are degraded in the Network Configuration Utility. Furthermore, there are the following Event Viewer entries in the System Log: Event ID: 270 Source: CPQTeamMP Type: Error Category: None Description: PROBLEM: A Team Member was NOT successfully added to the Team as configured. If at least one Team Member is configured , the Team will initialize (but with a lesser complement of Team Members). ACTION: Rerun the HP Network Teaming and Configuration utility to reconfigure the Team and Team Members. Event ID: 323 Source: CPQTeamMP Type: Error Category: None Description: HP Network Team #1: PROBLEM: An attempt was made to add a team member to a team, but the new team member does not support the Task Offload capabilities offered by the team, and can not operate properly within the team. The Team is more capable than the Team Member. The attempt to join the team has been failed. ACTION: Rerun the HP Network Teaming and Configuration utility to reconfigure the Team and Team Member. Possibly, specifically Disabling all offload capabilities. Or disable and (re-) enable this team's Network Connection on "Network and Dial-up Connections" page. SOLUTION: Check the previous version of the Network Configuration Utility. If it is version 7.80 or earlier, then chances are that the Large Send Offload (LSO) feature is enabled on the team. This prevents certain NICs such as the NC7782 from rejoining the team following an upgrade to the Network Configuration Utility version 8.35 or 8.37. See customer advisory CO041221_CW01 for details. The Network Configuration Utility 7.80 was provided by the HP ProLiant Support Pack 7.20. The issue is resolved by dissolving the team, and then recreating it. The reason is that new teams created with the 7.85 driver and later do not enable the Large Send Offload feature by default. The advisory, however, does not provide an automated remedy for the issue. If a very large number of servers have the Large Send Offload option enabled, manually turning this option off prior to the deployment of the Proliant Support Pack (PSP) can be potentially labor intensive. The reason why the advisory does not offer one is that HP has not constructed a means of changing this value other than with the Network Configuration Utility GUI. The XML files utilized by the scripting utility Cpniccmd.exe does not offer a property for LSO. If the Save button is used within the Network Configuration Utility GUI, the resulting XML file will offer a large number of properties, but not for LSO. The reason is that not all NICs support LSO, so introducing such a property may allow for creating teams with incompatible properties through scripts, with unpredictable consequences. Theoretically, it may be possible to construct a script to change the largesendoffload keys within the registry. However, such a project would entail a potential significant risk to the registry and is not covered by warranty and hardware carepack support. ©Copyright 2025 Hewlett Packard Enterprise Development LP Hewlett Packard Enterprise Development 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 Development and the names of Hewlett Packard Enterprise Development products referenced herein are trademarks of Hewlett Packard Enterprise Development in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

ISSUE:

Following upgrading to the HP ProLiant Support Pack version 7.50 or 7.51 in a Microsoft Windows environment, NIC team members are degraded in the Network Configuration Utility. Furthermore, there are the following Event Viewer entries in the System Log:

Event ID: 270
Source: CPQTeamMP
Type: Error
Category: None

Description: PROBLEM: A Team Member was NOT successfully added to the Team as configured. If at least one Team Member is configured , the Team will initialize (but with a lesser complement of Team Members). ACTION: Rerun the HP Network Teaming and Configuration utility to reconfigure the Team and Team Members.

Event ID: 323
Source: CPQTeamMP
Type: Error
Category: None

Description: HP Network Team #1: PROBLEM: An attempt was made to add a team member to a team, but the new team member does not support the Task Offload capabilities offered by the team, and can not operate properly within the team. The Team is more capable than the Team Member. The attempt to join the team has been failed. ACTION: Rerun the HP Network Teaming and Configuration utility to reconfigure the Team and Team Member. Possibly, specifically Disabling all offload capabilities. Or disable and (re-) enable this team's Network Connection on "Network and Dial-up Connections" page.

SOLUTION:

Check the previous version of the Network Configuration Utility. If it is version 7.80 or earlier, then chances are that the Large Send Offload (LSO) feature is enabled on the team. This prevents certain NICs such as the NC7782 from rejoining the team following an upgrade to the Network Configuration Utility version 8.35 or 8.37. See customer advisory CO041221_CW01 for details.

The Network Configuration Utility 7.80 was provided by the HP ProLiant Support Pack 7.20.

The issue is resolved by dissolving the team, and then recreating it. The reason is that new teams created with the 7.85 driver and later do not enable the Large Send Offload feature by default.

The advisory, however, does not provide an automated remedy for the issue. If a very large number of servers have the Large Send Offload option enabled, manually turning this option off prior to the deployment of the Proliant Support Pack (PSP) can be potentially labor intensive.

The reason why the advisory does not offer one is that HP has not constructed a means of changing this value other than with the Network Configuration Utility GUI. The XML files utilized by the scripting utility Cpniccmd.exe does not offer a property for LSO. If the Save button is used within the Network Configuration Utility GUI, the resulting XML file will offer a large number of properties, but not for LSO. The reason is that not all NICs support LSO, so introducing such a property may allow for creating teams with incompatible properties through scripts, with unpredictable consequences.

Theoretically, it may be possible to construct a script to change the largesendoffload keys within the registry. However, such a project would entail a potential significant risk to the registry and is not covered by warranty and hardware carepack support.

©Copyright 2025 Hewlett Packard Enterprise Development LP Hewlett Packard Enterprise Development 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 Development and the names of Hewlett Packard Enterprise Development products referenced herein are trademarks of Hewlett Packard Enterprise Development in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.