Taken from http://www.zamaanonline.com/funny-fishing-cartoon-4026
For information on the state in doubt messages, please see KB 1022026
Emulex logging options can be tricky. Please refer to KB 1005576
Trying to echo these options has not always proven to be successful. It may depend on driver type, version, or other factor.
The Invalid metadata status indicates that the content of the heartbeat region is not correct.
The Invalid metadata status indicates that the content of the heartbeat region is not correct.
The Invalid metadata status indicates that the content of the heartbeat region is not correct.
The exception to this type of this standard vmkernel log would be the addition of ALERT or WARNING
The lock at offset 4292608 gets stolen incorrectly by another other host, thus we PSOD
VI Client logs are found under C:\\Documents and Settings\\USERNAME\\Local Settings\\Application Data\\VMware\\vpx
In the previous slide we saw a message that contained a value of “FPe”. When referencing it in this table we can see the description for this event is “FCP traffic history”. FCP traffic history messages would related to anything traffic related like aborts, timeouts, etc.
I have downloaded this package, moved it to my home directory on scripts, and extracted it. This allows me to use tools such as grep to search for strings in the driver code.
A popular Vmware blog website known as VMProfessional.com has a SCSI sense data decode utility