Fix “Failed to Claim Physical NICs” Error in VxRail

Introduction

During a VxRail node expansion, I encountered an issue where the process failed due to a network-related error. If you are facing the same problem, this guide will help you diagnose and resolve it efficiently.

Error Message

The following error appeared during the expansion process:

Failed to claim physical NICs on virtual switch for host: xxxxxxx
Failed to claim physical NICs on virtual switch for host: xxxxxxx
Failed to claim physical NICs on virtual switch for host: xxxxxxx

Troubleshooting Steps

1. Verify Driver and Firmware Compatibility

Before escalating the issue, I ensured the node had the correct configuration by checking:

• Driver version – Matches other nodes in the cluster
• Firmware version – Consistent across all nodes

Despite these checks, the issue persisted.

2. Investigating License Status

After confirming the node’s configuration, I contacted Dell EMC VxRail support for further analysis. The support team identified that the issue was caused by an expired vSphere license on the host.

3. Recommended Solution

The support team suggested a RASR (Recovery and Smart Rebuild) reset, which would require reinstalling the node (min 2h of work). However, I explored an alternative approach to resolve the issue more efficiently.

Alternative Fix: Apply a Temporary vSphere License

Instead of reinstalling the node, I followed these steps:

1. Configured the IP address via Direct Console User Interface (DCUI)
2. Logged into the vSphere Web Client as root
3. Applied a temporary vSphere license to the ESXi host
4. Remove the IP address via Direct Console User Interface (DCUI)

Once the license was added, I restarted the VxRail expansion process, and it completed successfully.

Conclusion

If you encounter the “Failed to claim physical NICs on virtual switch for host” error during a VxRail node expansion, first check for configuration mismatches. If everything appears correct, verify the vSphere license status before proceeding with a full node reset. Applying a temporary license can often resolve the issue without the need for a complete reinstall.

This solution saved significant time and effort, preventing unnecessary wait time. If you have experienced similar issues, feel free to share your insights in the comments.