SAN switch migration

[ThomasN]

Hello,

       I have Proliant DL360 Gen9 servers in a Windows 2019 Hyper-V cluster.  The SANs are Nimble AF3000 and HF40.  We are upgrading our SAN switches from Cisco Nexus 9K to Fortinet 2048F SAN switches.  The Nexus and Fortinet switches are uplinked together and are seen as a logical switch stack.  I have tested connectivity to the SAN from the Fortinet switch to the Nexus 9K to be working.  When a server SAN connection is moved from the Nexus 9k to the Fortinet SAN switch, Nimble connection manager has an issue connecting to the FN switch.  Status is reconnecting on the moved port.  Only after a server reboot the connection is established by NImble Connection manager.  Is this normal behavior for NCM? Has anyone done a SAN switch upgrade with Nimble SANs and can they share their experience or script?  Thank you.  

[Satish04 · Accepted solution]

Hi ThomasN,

It appears that there may be a problem with the way the HPE Nimble Connection Manager (NCM) manages the switchover.
Although NCM is meant to handle connections to HPE Nimble arrays automatically.

You may be able to troubleshoot and maybe fix this issue by following these procedures and considerations.

Verify that your servers have NCM setup properly. It may occasionally require certain updates or changes in order to detect new SAN pathways without requiring a reboot.
Make sure the multipathing settings on the server are configured correctly. It is important to check the Multipath I/O (MPIO) settings in Windows in order to make sure that the new paths are recognized.
Make sure the Fortinet 2048F SAN switches are configured correctly. To ensure seamless communication between servers and HPE Nimble arrays, ensure that zoning and other relevant settings are configured correctly.
Ensure that your HBA firmware and drivers are up-to-date. Sometimes, newer firmware or drivers can resolve connectivity problems.
The HPE Nimble OS on your arrays and the HPE Nimble Connection Manager should be updated, as updates often fix connectivity issues and improve multipath handling.

For more information on why the connection cannot be established until after a reboot, check both the HPE Nimble arrays and the server's logs.

Hope this helps.!

Regards,
Satish