- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Losing Host Management
Dear Community,
We are currently experiencing intermittent issues where on one site hosts are becoming unmanageable either from vCenter or the console. Not all the hosts are affected at the same time, the the issue has occurred on every host at least once. Looking through the logs, the symptoms are similar to the All Paths Down (http://kb.vmware.com/kb/1030980) and Permananet Device Loss scenarios (http://kb.vmware.com/kb/2004684).
Here is an excerpt from the log:
2013-03-30T06:30:13.629Z cpu3:8195)ScsiDeviceIO: 2329: Cmd(0x4124030be500) 0x12, CmdSN 0xe541 from world 0 to dev "naa.600508e0000000006892f243e434a30c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2013-03-30T06:32:43.696Z cpu1:8193)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x85 (0x4124003f8f80, 9165) to dev "naa.600508e0000000006892f243e434a30c" on path "vmhba0:C1:T1:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE 2013-03-30T06:32:43.696Z cpu1:8193)ScsiDeviceIO: 2329: Cmd(0x4124003f8f80) 0x85, CmdSN 0x285 from world 9165 to dev "naa.600508e0000000006892f243e434a30c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
As you can see on the timestamp this issue has been going one since the end of March. The same errors are logged for all storage devices including local disks.
Additional Information:
- Running vCentre 5.1 (947673)
- All hosts are the same build and config. Running ESXi 5.1 (1021289)
- Only iSCSI storage has been presented to the hosts.
- The storage system is a NetApp FAS2220
- The other site has seen no occurrence of the problem even though the storage and network configurations are the same. However, the host builds are ESXi5.1 (799733) and the storage system is a NetApp FAS2240
- NetApp support have already looked at logs on the storage system and can see no reason for loss of connectivity.
I understand from the KBs that there were issues in earlier versions of ESXi, which have since had patches released, however, I believe that later versions, which is what we have installed already have the fix applied.
Any assistance with this is greatly appreciated.
Alan