topic Query: Add new esxi host to MSA 2050 in MSA Storage

Add new esxi host to MSA 2050

Uraken007 — Wed, 03 Jan 2024 09:03:14 GMT

Hi all,

I have two hpe gen 10 proliant servers currently connected to my MSA 2050 via DAS cables, everything works perfectly well and has done for a few years, because it was set up by gurus.., i now want to add a new HPE gen 11 server with esxi on it to the HPE MSA 2050, i have the correct cables and assumed i could just connect two the two cables to port 3 on both controllers and then i would appear it the MSA 2050 and i could add it to the host group, however when i did this weird things began to happen and clients began to complain that some vms were not accesible. I have since been told this may have been becase the new gen 11 server was switched on at the time.

So my question is does anyone know the correct procedure for adding a new host to the MSA, do i need to create an initiatior with wwn names first or will the MSA just detect them and i can simple add them to the existing host group?

I have scoured the internet and apologies in advance if i have missed a document or guide that would of saved this post.

Any help gratefully recieved.

Thanks in advance

Uraken

Re: Add new esxi host to MSA 2050

Uraken007 — Sun, 31 Dec 2023 16:19:18 GMT

ok found this https://www.hpe.com/psnow/doc/a00017707en_us which suggests that the initiators are created by the MSA 2050 when the host boots up, does anyone know if that is indeed the case?

I then have to create nicknames for them and i can then add them to a host group. I know i have to pull the trigger on this at some point otherwise there will be no progress but i am still worried as to why the existing vms on the existing hosts seem to have a wobble when i connected the last time?

Anyone with any input would be great.

Query: Add new esxi host to MSA 2050

support_s — Sun, 31 Dec 2023 16:22:50 GMT

System recommended content:

1. HPE MSA 2050 Controller VL100R004 Firmware Release Notes

2. HPE MSA 2050 User Guide

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

Thank you for being a HPE valuable community member.

Re: Add new esxi host to MSA 2050

JonPaul — Tue, 02 Jan 2024 22:08:39 GMT

@Uraken007
Your experience is unfamiliar to me. Connecting the new host should not affect the existing hosts.
One thing I would suggest is to run the MSA Healthcheck https://www.hpe.com/storage/MSAHealthcheck
This will point out any anomalies with hosts or port mapping.

You stated "DAS Cables", I'm assuming that means the MSA is a SAS system. SAS systems sometimes have difficulty finding the first SAS volume but that would not explain the experience you had. Hot plugging the host should not cause any problems whether the host is on or off.

Your experience sounds like the new host tried to take ownership of 1 or more volumes but that should not happen as the new SAS HBA would have a different unique identifier and the MSA 2050 should only allow explicit mapping, only present the LUN to a specific set of unique identifiers. You could validate that the volumes are NOT mapped to port 3 before you connect the new server. That should further reduce the chance of the new server taking over the presented LUNs.

For Fibre Channel and SAS systems when the cable is connected the HBA will attempt a login to the devices attached and the MSA management would show a new unique identifier. With iSCSI you need to initiate the login from the iSCSI initiator (host software). So yes the article is correct for a SAS system. You can't really move forward until the new server is connected but the 'wobble' you experienced would be worrisome.

Re: Add new esxi host to MSA 2050

Uraken007 — Wed, 03 Jan 2024 11:36:16 GMT

@JonPaul firstly this is a really helpful and your time is appreciated thank you.

So it turns out that it was a physical cabling issue, not quite seated correctly, the initators are now automajically appearing in the mSA 2050 without your input this wouldn't have been the case so thank you.

This also confirms that the glitch we experienced previously was purely coincidental as the cables were not connected correctly at this point.

Is it just a case of scanning the hba on the esxi server itself now to have it appear as a host in the MSA? giving the initiator a nickname adding to the new host?