2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→Storage Monitor Log Entries: Added 0x28
m (→Get NIC Firmware/Driver versions: Udated applicability) |
(→Storage Monitor Log Entries: Added 0x28) |
||
| Line 886: | Line 886: | ||
=== Storage Monitor Log Entries === | === Storage Monitor Log Entries === | ||
How to decode the following type of entries... | How to decode the following type of entries... | ||
Sep 3 15:15:14 | Sep 3 15:15:14 esx1 vmkernel: 85:01:23:01.532 cpu4:2264)StorageMonitor: 196: vmhba1:2:0:0 status = 2/0 0x6 0x2a 0x1 | ||
Sep 3 15:15:32 | Sep 3 15:15:32 esx1 vmkernel: 85:01:23:19.391 cpu4:2253)StorageMonitor: 196: vmhba1:3:9:0 status = 2/0 0x6 0x2a 0x1 | ||
The status message consists of the follow four decimal and hex blocks... | The status message consists of the follow four decimal and hex blocks... | ||
| Line 893: | Line 893: | ||
|- | |- | ||
|''Device Status'' / ''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier'' | |''Device Status'' / ''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier'' | ||
|} | |||
...or in the more recent format (ESX v3.5 Update 4 and above)... | |||
Mar 2 10:04:44 vmkernel: 81:00:00:15.893 cpu8:3258649)StorageMonitor: 196: vmhba0:0:4:0 status = D:0x28/H:0x0 0x0 0x0 0x0 | |||
Mar 2 10:04:44 vmkernel: 81:00:00:15.893 cpu8:4633964)StorageMonitor: 196: vmhba0:0:4:0 status = D:0x28/H:0x0 0x0 0x0 0x0 | |||
{| cellpadding="4" cellspacing="0" border="1" | |||
|- | |||
|<code>D:</code>''Device Status'' / <code>H:</code>''Host Status'' || ''Sense Key'' || ''Additional Sense Code'' || ''Additional Sense Code Qualifier'' | |||
|} | |} | ||
| Line 925: | Line 935: | ||
|- | |- | ||
| 24 || Reservation Conflict || || 24/0 indicates a locking error, normally caused by too many ESX's mounting a LON, wrong config on storage array, or too many VM's on a LUN | | 24 || Reservation Conflict || || 24/0 indicates a locking error, normally caused by too many ESX's mounting a LON, wrong config on storage array, or too many VM's on a LUN | ||
|- | |||
| 28 || Queue full / Task set full || || Indicates the SAN is busy handling write's and is passing back notification of such when asked to handle more data | |||
|} | |} | ||