Have a 3par 7200 running fw: 22.214.171.124
I have connected vCenter 6 on a HP BL460 G9 running vSphere to the 3PARs VASA url. However I cannot get the PE to be visible to the ESXi host. I run the following command:
esxcli storage core device list -–pe-only
And no PEs show up.
In Log Insight I am seeing these warnings:
WARNING: ScsiPath: 679: Sanity check failed for path vmhba34:C0:T1:L256. The path to a VVol PE comes from adapter vmhba34 which is not PE capable. Path dropped.
The G9 blade is using the 536FLB CNA.
Any help would be appreciated.
I am getting the errors of a fresh install of 6, with the latest VMware and HP Patches. I have a QL HBA ISP2532 (HP 82Q). I found this
I take it we are all waiting for right combination of HP and VMware patches.
If I am reading this correct:
There are only 2 supported CNAs:
If this is correct any BL-460G9 using the onboard CNA to Flex modules will most likely not be supported. I have a 630FLB in a new server and it does not support the Secondary LUNID function which appears to be required for vVOLs:
I have also the same warning (sanity check failed...) with HP BL660c and FlexFabric 534FLB (Broadcom) with fresh installed vSphere 6 although I updated the lastest driver 534FLB from HP web site.
But with HP BL660c and Flex Fabirc 554FLB (Emulex) operated normally. I think maybe this bug from HP driver.
I need to Mask all traffic coming from specific iSCSI or specific protocol type
/var/log # esxcli storage core claimrule list
Rule Class Rule Class Type Plugin Matches
---------- ----- ------- --------- --------- ----------------------------------------
MP 0 runtime transport NMP transport=usb
MP 1 runtime transport NMP transport=sata
MP 2 runtime transport NMP transport=ide
MP 3 runtime transport NMP transport=block
MP 4 runtime transport NMP transport=unknown
MP 101 runtime vendor MASK_PATH vendor=DELL model=Universal Xport
MP 101 file vendor MASK_PATH vendor=DELL model=Universal Xport
MP 200 runtime location MASK_PATH adapter=vmhba33 channel=0 target=0 lun=0
MP 200 file location MASK_PATH adapter=vmhba33 channel=0 target=0 lun=0
MP 65535 runtime vendor NMP vendor=* model=*
/var/log # esxcli storage core claimrule add --rule 380 -P NMP -t target -R iscsi --iqn iqn.1998-01.com.vmware:esx02-48f816e4 --lun 1
/var/log # esxcli storage core claimrule add --rule 390 -P NMP -t target -R iscsi --iqn iqn.1998-01.com.vmware:esx02-48f816e4 --lun 2
/var/log # esxcli storage core claimrule load
/var/log # esxcli storage core claimrule run
Check the following best practices:
HP 3PAR support
HP 3PAR OS 3.2.1 MU2Patch 12
vSphere 6.0, vCenter Server 6.0
HP 3PAR MC 4.6.x
vSphere Web Client 6.0
HP 3PAR 3.2.1 CLI
esxcli (vSphere 6.0)
HP 3PAR Virtual Copy
vSphere Standard license
HP 3PAR Thin Provisioning
vCenter Server Standard
The above table summarises the requirements. First and most obviously you need vSphere 6 and this needs to be licenced at vSphere Standard level. From the 3PAR side of things you need to be running 3PAR OS 3.2.1 MU2 or above, this effectively means that VVOLs are only available on the 7000 and 10,000 series models. Patch 12 for 3.2.1 is also a mandatory requirement for VVOLs, this patch ensures the consistency of the VM’s
Follow the KB http://kb.vmware.com/kb/2114975
Alright, burrowed around some more and here's the arrangement, the drivers you need on the worker side for some model CNAs in HP workers to help VVOLs with vSphere 6 have not yet been remembered for the HP pictures that are accessible for vSphere 6. Anyway they are remembered for the stock ESXi picture that you can download direct from VMware. So on the off chance that you utilize the VMware ESXi picture rather you ought to have the option to utilize VVOLs with 3PAR with no issues.