Pure storage support

[mikejdunphy]

Does this HPE Morpheus kvm hypervisor support pure storage on a fiber SAN?

https://hpevm-docs.morpheusdata.com/en/latest/vme_getting_started/vme_getting_started.html#id15

shows that HPE Alletra and MSA are supported and Netapp and Dell.

[CalvinZito]

I'd say keep your eye on the Compatibility Matrix  and note that it does list a couple of Pure arrays in the latest version. And keep your eye on my Welcome message on this board as I have tons of resources listed there, especially my LinkedIn article "Essentials for HPE Morpheus VM Essentials" that I have lots of content listed. 

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

[mikejdunphy · Accepted solution]

I mapped the lun from the pure array to each of the nodes, ran a scsi scan  and created a gfs2 with the gui og the vm essentails console and it working great.

[Ste7N]

Hi mikejdunphy,

could you please explain the steps you accomplished or provide some documentation reference please?

Thank you.

[mikejdunphy]

My trial of the software was run on 3
SY 480 Gen10 Plus 3 blades in a HP Synergy chassis

Each blade was had 2 fiber HBA's connected to the brocade chassis switch which then
was connected up to a edge switch. There are 2 fabrics A and B

I zoned and mapped the WWPN's to the switches and pure array using peer zoning
(easily derived from pure and brocade documentation )

Here are my specific notes.

For fc datastore:
Present lun to all hosts.
Verify with lsblk on the hosts. You should see your disk and the multipathing.

Create cluster in vme.
Add gfs2 lun from in the cluster screen (not main storage screen)
It will do the full cluster config for you. No need to fiddle with corosync.
Edit datastore and enable heartbeat.

note after rescan scsi bus there are 4 devices

root@hp-vmessential1:~# multipath -ll
3624a9370678e444ef0404df200096272 dm-1 PURE,FlashArray
size=10T features='0' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 0:0:0:254 sdc 8:32 active ready running
|- 3:0:0:254 sdd 8:48 active ready running
|- 0:0:1:254 sde 8:64 active ready running
`- 3:0:1:254 sdf 8:80 active ready running

[Ste7N]

Thank you for your quick reply.

Unfortunately, I am currently working with the iSCSI protocol and facing difficulties configuring the protocol binding on the VME host network adapters as an initial step.

Guess Pure setup will be the easy part.

[mikejdunphy]

for the network to the blades we have 2 25gb ethernets to each blade with all the vlans we need. ISCSI definitely makes it more complex. FC is much easier, less overhead and easy to manage however it is more expensive.