MSA Storage
1819556 Members
2737 Online
109603 Solutions
New Discussion юеВ

second MSA2040 SAS with ESX ?

 
Theo_dor
Advisor

second MSA2040 SAS with ESX ?

Hello,
can I add a second MSA to my vsphere cluster ?
currently every server has two dual port SAS controller card.
one controller card is connected to MSA controller A , the other card to MSA Controler B.

I could connect a second MSA to all second ports of SAS cards in all esx servers.

will this work ?
what about LUNs ? (the second MSA will have same LUNs ?)

2 REPLIES 2
sbhat09
HPE Pro

Re: second MSA2040 SAS with ESX ?

Hello @Theo_dor,

2nd MSA may be added to the vsphere cluster. But both the MSA's are in replication relationship, both will have same volumes. If they are independent, they will have different volumes.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
JonPaul
HPE Pro

Re: second MSA2040 SAS with ESX ?

@Theo_dor 

When a LUN is mapped it has a unique Initiator (host SAS HBA), Target (Array Port ID) and LUN ID configuration making all LUNs unique.  So an MSA Volume mapped from a different MSA will have a different unique Array Port ID and be seen as unique.
@sbhat09   went to the next step where a VMware Volume has a unique ID on the file system and is how VMware recognizes the ESX Volume.  IF that volume is replicated then the VMware Volume ID is also replicated and that can add complication to the discovery for the OS.  Since the MSA SAS systems do not have a replication feature, I don't think this is a problem. 

I work for HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]