Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Binding VMkernel ports to the Software iSCSI Initiator fails with the error: Failed to add nic (2006627)

Symptoms

  • Cannot bind a VMkernel interface to the Software iSCSI adapter
  • Binding a VMkernel interface to the Software iSCSI adapter fails
  • Running the # esxcli swiscsi nic add -n vmk0 -d vmhba33 command in ESX 4.0 fails
  • Running the #esxcfg-vmknic -a -i <ipaddress> <portgroupname> command in ESX 4.1 fails
  • You see the error: 

    Failed to add nic 
  • When trying to list the current iSCSI adapter bindings, you may see duplicate bindings, as well as VMkernel interfaces that may no longer exist

    For example:

# esxcli swiscsi vmknic list -d vmhba33
vmk1
vmknic name: vmk1
mac address: 00:50:56:77:c8:3d
mac address settable: NO

vmk1
vmknic name: vmk1
mac address: 00:50:56:77:c8:3d
mac address settable: NO

Purpose

This article provides information on removing all dynamic and static discovery targets from the Software iSCSI adapter.

Resolution

To resolve this issue, ensure that all incorrect or duplicate bindings are removed and then remove all dynamic and static discovery targets from the Software iSCSI adapter.
 
To remove incorrect or duplicate bindings, run this command:
 
In ESX 4.0 – # esxcli swiscsi vmknic remove -n vmk1 -d vmhba33
 
In ESX 4.1 – # esxcfg-vmknic -d -p <pgName>
 
To remove all dynamic and static discovery targets from the Software iSCSI adapter: 
  1. In the vSphere Client, select the host and click the Configuration tab.
  2. In Hardware, click Storage Adapters.
  3. In the list of storage adapters, click Software iSCSI adapter.
  4. In the Details pane, click Properties.
  5. Click the Dynamic Discovery tab and remove all listed entries.
  6. Click the Static Discovery tab and remove all listed entries.
  7. Click Close.
  8. Attempt to to bind the vmkernel ports to the Software iSCSI adapter.

Additional Information

If the issue persists, it is possible that the iSCSI configuration is corrupt. For more information, see Software iSCSI LUNs disappear after rebooting or upgrading the ESX/ESXi host (1038065).

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings
Actions
KB: