Change multipathing policy to RoundRobin on ESXi 5.x

1.       Select an ESXi host you want to modify, and click the Configuration tab.
2.       Click Storage.
3.       Select a datastore or mapped LUN.
4.       Click Properties.
5.       In the Properties dialog, select the desired extent, if necessary.
6.       Click Extent Device > Manage Paths and obtain the paths in the Manage Path dialog.
7.       Under the Policy section, select the desired multipathing policy from the dropdown.

8.       Click Change to confirm the change in path policy.

How to find the HBA details in ESXi 5.1 server

How to find the HBA details in ESXi 5.1 server

1.  from /proc/scsi

~ # cd /proc/scsi/qla2xxx/

/proc/scsi/qla2xxx #

/proc/scsi/qla2xxx # ls

3  4

/proc/scsi/qla2xxx # cat 3 | head -3

QLogic PCI to Fibre Channel Host Adapter for HPAK344A:

        FC Firmware version 5.06.05 (90d5), Driver version 934.5.6.0-1vmw

Here,
FC firmware version is - 5.06.05 (90d5),
Driver version is - 934.5.6.0-1vmw

2.  run the following command 

~ # esxcfg-scsidevs -a

 # esxcfg-scsidevs -a
vmhba0  hpsa              link-n/a  sas.500xxxxxxxxxxxxx                    (0:2:0.0) Hewlett-Packard Company Smart Array P420i
vmhba1  qla2xxx           link-up   fc.500xxxxxxxxxxxd9:500xxxxxxxxxxxd8    (0:xx:x.x) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba2  qla2xxx           link-up   fc.500xxxxxxxxxxx99:500xxxxxxxxxxx98    (0:xx:x.x) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA


-- you can see the driver as qla2xxx  for QLogic HBA card
-- now to find driver version execute the following command

~ # vmkload_mod -s qla2xxx |grep Version
 Version: Version 934.5.6.0-1vmw, Build: 472560, Interface: 9.2 Built on: Sep 21 2012

HP Storage P2000 G3 MSA - Delete a vdisk and create a new vdisk

One of the vdisk on the HP Storage P2000 G3 MSA was showing fault.
I got an error message saying that "The virtual disk is offline. Disks may be down or missing. Data may be lost".

We had 2 hdd failed in the vdiks, we had this failed hdd's replaced.
The 2 hdd failure has caused the raid 5  vdisk to fail.


Now I couldn't re-add the new disk because of the raid failure.

So I had to delete the vdisk and create a new vdisk and volumes under the vdisk.