09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

esxcli hpssacli cmd -q "controller slot=0 Array G modify led=on”<br />

A very useful command for toggling the LED on a drive to verify that, in the event of<br />

replacing a drive, this is indeed the correct drive. Use the option “modify led=off” to<br />

turn it off again.<br />

esxcli hpssacli cmd -q "rescan”<br />

If the controller does not detect a new/replaced disk drive, you can use this<br />

command to force a rescan.<br />

esxcli hpssacli cmd -q "controller slot=0 create type type=ld drives=2I:1:8<br />

raid=0”<br />

This command will build a RAID-0 logical driver (ld) on the drive found in slot 2I:1:8.<br />

Port is 2I, Box is 1 and Bay is 5. Once this command is run, you should soon start to<br />

see the device appear in ESXi (although if it takes a little while because the autoscan<br />

for devices on ESXi has not run, you can also run the esxcfg-rescan<br />

command against the adapter). The easiest way to do this is to monitor the<br />

vmkernel.log file on ESXi and observe the message related to the device. Here is an<br />

example of a RAID-0 logical volume created on a HP Smart Array controller being<br />

detected by the ESXi host:<br />

2014-11-06T13:25:33.076Z cpu22:8671255)ScsiScan: 976: Path 'vmhba1:C0:T0:L8': Vendor:<br />

'HP ' Model: 'LOGICAL VOLUME ' Rev: '3.66'<br />

2014-11-06T13:25:33.076Z cpu22:8671255)ScsiScan: 979: Path 'vmhba1:C0:T0:L8': Type: 0x0,<br />

ANSI rev: 5, TPGS: 0 (none)<br />

2014-11-06T13:25:33.076Z cpu22:8671255)ScsiScan: 1503: Add path: vmhba1:C0:T0:L8<br />

2014-11-06T13:25:33.077Z cpu22:8671255)ScsiPath: 4695: Plugin 'NMP' claimed path<br />

'vmhba1:C0:T0:L8'<br />

2014-11-06T13:25:33.077Z cpu22:8671255)vmw_psp_fixed:<br />

psp_fixedSelectPathToActivateInt:479: Changing active path from NONE to vmhba1:C0:T0:L8<br />

for device "Unregistered Device".<br />

2014-11-06T13:25:33.077Z cpu22:8671255)StorageApdHandler: 698: APD Handle Created with<br />

lock[StorageApd0x410910]<br />

2014-11-06T13:25:33.077Z cpu22:8671255)ScsiEvents: 501: Event Subsystem: Device Events,<br />

Created!<br />

2014-11-06T13:25:33.077Z cpu22:8671255)VMWARE SCSI Id: Id for vmhba1:C0:T0:L8<br />

0x60 0x05 0x08 0xb1 0x00 0x1c 0x57 0x7e 0x11 0xdd 0x04 0x2e 0x14 0x2a 0x58 0x3f 0x4c 0x4f<br />

0x47 0x49 0x43 0x41<br />

2014-11-06T13:25:33.077Z cpu22:8671255)ScsiDeviceIO: 7456: Get VPD 86 Inquiry for device<br />

"naa.600508b1001c577e11dd042e142a583f" from Plugin "NMP" failed. Not supported<br />

2014-11-06T13:25:33.077Z cpu22:8671255)ScsiDeviceIO: 6187: QErr is correctly set to 0x0<br />

for device naa.600508b1001c577e11dd042e142a583f.<br />

2014-11-06T13:25:33.077Z cpu22:8671255)ScsiDeviceIO: 6684: Could not detect setting of<br />

sitpua for device naa.600508b1001c577e11dd042e142a583f. Error Not supported.<br />

2014-11-06T13:25:33.082Z cpu7:151751 opID=71297a98)World: 14299: VC opID hostd-aa04 maps<br />

to vmkernel opID 71297a98<br />

2014-11-06T13:25:33.143Z cpu22:8671255)ScsiDevice: 3443: Successfully registered device<br />

"naa.600508b1001c577e11dd042e142a583f" from plugin "NMP" of type 0<br />

V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 2 8 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!