Environment:
Symptoms:
- VMs on hosts ESX001 and ESX003 are not responding.
- Unable to see any VMs listed for ESX002.
- All LUNS are visible but not responding when accessed.
- IBM iSCSI array logs states that the hosts are just dropping.
Logs:
messages.log
Analysis:
- Notice that there is no pnic attached to vmk2 port group, due to which we are receiving invalid arguments.
ESX build # VMware ESXi 4.1.0 build-348481
Host Hardware DELL PowerEdge R710
Symptoms:
- VMs on hosts ESX001 and ESX003 are not responding.
- Unable to see any VMs listed for ESX002.
- All LUNS are visible but not responding when accessed.
- IBM iSCSI array logs states that the hosts are just dropping.
Logs:
messages.log
Jan 8 04:46:45 iscsid: Could not bind connection 0 to vmk2 (Error=22,Invalid argument)
Jan 8 04:46:45 iscsid: cannot make a connection to 192.168.1.5:3260 (22,Invalid argument)
Jan 8 04:46:46 iscsid: Could not bind connection 0 to vmk2 (Error=22,Invalid argument)
Jan 8 04:46:46 iscsid: cannot make a connection to 192.168.1.6:3260 (22,Invalid argument)
#" esxcli swiscsi nic list -d vmhba41" lists the below info(Truncated):
vmk2
pNic name:
ipv4 address: ::
ipv4 net mask: ::
vmk3
pNic name: vmnic6
ipv4 address: 192.168.100.3
ipv4 net mask: 255.255.255.0
Recommendation:
- Remove vmk2 portgroup using the below command.
# esxcli swiscsi nic remove -n vmk2 -d vmhba41
