MSA 2060 SAS - Add new initiators to existing host

[MrBeam3255]

I have 2 ESXi Servers currently attached to my MSA 2060 (SAS dual controlers/dual connections to esch server for redundancy).  We are trying to add a 3 server.  Everything is connected and I see the new intiators show up on the MSA controller(s).  When I try to add the two new intiators to my exsisting Host, I get the error:

Failed to add initiators to the host.

The mappings of the initiator are inconsistent with the mappings of the host. Therefore, the initiator cannot be added to the host. - (2023-08-01 12:57:08)

The current Host (4 intiators total) currently has two volumes attached.  How do I confirm the mappings to the two new intiators match the mappings of those four existing initaitors?   It seems the logical path is to create a host, then add intiators, then add volumes to the host.  If I am adding two new intiators to a current host would those intaitors just get the volumes added to them the same as the exsisting intiators?

Thanks in advance for any insight to this.

J 

[venkat_y]

Hello@MrBeam3255,

The error message indicates, there is a mismatch between the mappings of the initiators and host on MSA 2060. So, you must check that the mappings are consistent for all initiators attached to the Host.

Check the existing initiator's port assignments, zoning, and other settings as well.

Verify the new initiators settings that you want to add to the existing host and make sure that port assignments and zoning match the configuration of the existing initiators.

Make sure that both the existing initiators and the new initiators are correctly mapped to the host on MSA 2060. The mappings must be consistent for all initiators belonging to the same host.

If you find any mistakes in mappings, correct, and update the mappings on MSA 2060. And then rescan the initiators on ESXi Servers to make sure they can see the storage correctly.

then add the volumes to the existing host with the two new initiators.

Hope this helps!

Regards,
Venkat

[MrBeam3255]

Where do I find the port assignments and zoning match information on the new intitiators?  I don't see that I can configure anything but nickname on an intitiator until after it is added to a host.

Thanks!

Jim

[MrBeam3255]

After re-reading my question I see it might need some clarification....

When I say I can not add the intiators to my existing host....  Host refers to the existing host setup on the MSA already, which has four intiators mapped (two pathwyas for each existing ESXi server) .

[JonPaul]

@MrBeam3255 
You have stumbled onto an area which is open for opportunity for improvement   There are a couple other threads here about your same problem.
In a nutshell the MSA does not take on the task of auto-mapping the LUNs for the host so leaves that to the user to do when adding a new initiator to a host or a host to a Host-Group (arghhh).
In my opinion, the best way to check the mappings is to use the CLI: show maps    
With few initiators and not many volumes this should not be hard.  In a bigger system you may want to specify the initiator  CLI:  show maps initiator FCS-MAIN.*
This will show just the maps to the host you specified.  Then you need to map the volumes to the new initiators the same as seen.  Same LUN # is key.   You can do the mapping in the WebUI or the CLI.
One thing to point out, it appears that you are adding the initiators from 3 servers into a single HOST.  This is fine but the design was to add only the initiators from a single physical server into a HOST then group the hosts into a HOST-GROUP.  I think what you are doing is direct attached and grouping the HOST with the array side uplink port.  Again fine but may run into limitations if you ever move to a SAN (FC Switch connected)

[Sunitha_Mod]

Hello @MrBeam3255, 

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

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.