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

Products

• VMware vSphere ESXi

Issue/Introduction

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

Symptoms:

• You 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 ip_address portgroup_name 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 nic list -d vmhba33
  vmk1
  vmknic name: vmk1
  mac address: xx:xx:xx:xx:xx:xx
  mac address settable: NO
  
  vmk1
  vmknic name: vmk1
  mac address: xx:xx:xx:xx:xx:xx
  mac address settable: NO

Environment

VMware ESXi 4.0.x Installable
VMware ESXi 4.1.x Embedded
VMware ESX 4.1.x
VMware ESXi 4.1.x Installable
VMware ESX 4.0.x
VMware ESXi 4.0.x Embedded

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).Software iSCSI LUNs disappear after rebooting or upgrading the ESX/ESXi host
Considerations for using software iSCSI port binding in ESX/ESXi