HPE MSA 2061 SAS >> upgrade to Fibre Channel?

[adamburtonlatch]

Hello community,

1 x HPE MSA 2062 SAS, dual controller each with 4 x 12Gb SAS port

4 x HPE DL 380 Gen 10, ESXi 8, each fitted with a dual port smart array E208e-p

The cabling is all point to point.

I want to set up shared storage but its seems that I need Fibre Channel to enable 'Clustered VMDK', the model I have is SAS.   Is it possible to modify the MSA to use Fibre channel?

It's all modular so perhaps i can purchase some FC GBICs and enable using the CLI?  Here's hoping!

Thanks

Adam

[JonPaul]

@adamburtonlatch 

To quickly answer your question, you can not change the protocol of an MSA system as there is no way to purchase the controllers.  Along with that the support will follow the SAS system you purchased and not FC controllers.

To get to your real question, "Why can't I used the MSA 2060 SAS to create a shared/clustered VMDK?"
There is no reason why what I believe you are trying to do would not work.  The MSA SAS system is capable of presenting a LUN to multiple hosts same as an FC or iSCSI system.  
Is the volume mapped to all the hosts?
CLI>  show initiators
CLI>  show host-groups
CLI>  show maps

Please provide a little more information on the errors you are receiving. Thanks.

[adamburtonlatch]

Hello JonPaul

Finally some real help,  thank you.  The HPE support team were not helpful.

I will reply shortly with answers.

Adam

[adamburtonlatch]

Hi @JonPaul,

Yes the volume is mapped to all hosts and I'm not seeing any errors or problems in the environment.

When i try to create a datastore using a new volume created on the MSA the column 'Clustered VMDK supported' says No

Thanks

Adam

[adamburtonlatch]

Hi @JonPaul,

I didn't mention in my previous post but i ran all the commands without error, do you have some news for me please?

Thanks

Adam

[John Kufrovich]

Hello Adam, 

I would like to review the MSA logs, do you have a support case?

Somethings to check. The ESXi hosts should be using nmp for sas targets. 

#esxcli storage nmp device list
#esxcli storage hpp device list

Regards,

John

[adamburtonlatch]

Hi John

Thanks so much for picking this up.

Yes :  case number 5390065902, I have uploaded the command outputs you suggested, MSA Event history, ESXi host 'VM12' storage devices screen shot and MSA logs.

The command #esxcli storage nmp device list  does list the two volumes which exist on the MSA.

Kind regards

Adam

[John Kufrovich]

Hello Adam,

I just read your update and see the case.    I reviewed the MSA logs and not seeing any problems on the MSA.  The Controller A MC is hitting a bug in IN210P001, where the IP address will report as 157.x.x.x.  This issue is fixed in IN210P002.  Services will provide action plan to clear that error condition.   I also, asked to verify your SAS HBA firmware and driver.  

If the ESXi hosts are running supported HBA fw and driver, can I get a copy of ESXi support logs from the nodes.  I am going to assume, that your volume 'test' was when you attempted the set 'cluster vmdk' in vCenter

Regards,

John

[adamburtonlatch]

Hello John

The SAN was installed and configured by HPE in Sept 2024, I paid for technical services.   Since then I have applied updates to ESXi 8 and vCentre. and installed some additional NICs in the vHosts.   Just before the SAN install I patched the server firmware using Gen 10 Service Pack for Proliant 2024.04.

I have not updated the SAN controller firmware since the SAN went in to production in Oct 2024.

Unfortunately the production volume  'HPE-MSA-VOL1'  consumes the entire storage space but it is thin provisioned so i was able to create a new volume 'test', so yes to answer your question, 'test' is created for this project.

I have just uploaded 4 x System logs, one for each vHost, using vCenter Export System Logs... and accepting the defaults.

It sounds like you may have found a fault/bug, I and a few engineers have been working on this for about 4 months so thanks again for your assistance.  I am looking forward to the next steps!

Adam