I inherited a SAN environment where both fabric A and B are using VSAN 1 for everything, and this may cause an issue with our path to merging the fabrics into a new FCoE environment. I was wondering if anyone had any experience in moving everything over to a new VSAN, I was thinking of doing the follwoing on each fabric individually:
The hosts can take a path outage, as they are running failover software, but I'm thinking the outage may be brief, if any at all, as all the hosts may have to re-login to the storage once moved.
Any insights would be greatly appreciated.
your VSAN migration plan sounds good but just check the Domain-ID values
some servers like HP-UX create the device-link path /dev/xxx/x.x.x.x based on the domain-id
If you have Solaris, windows, vmware etc... you are set if you have any HPUX or AIX iinvolved you need to keep in mind the Domain ID value as the same from the original VSAN.
Also remember to set the domain-ID static
I hope this helps.
The FCID's WILL change. Different VSAN = different domain ID (unless you want to start changing them around too*), and the domain ID is part of the FCID.
Most hosts should be fine with that, the only 2 I know of that may not be are HP-UX (as Ricardo has mentioned), and AIX where dynamic tracking is not enabled. Either way, both are easy fixes, delete and re-add disks then re-add to whatever multipathing SW you are using.
As I'm sure you know, the GOLDEN rule with any SAN migration (which this is), is to check EVERY host half way through to be sure it's paths are back before you do the 2nd half.
* Which will also cause disruption