02-27-2014 07:44 AM - edited 03-01-2019 11:33 AM
02-27-2014 08:59 AM
The following procedure has been done many times with success
- don't use pinning, it's a management nightmare
- use separate physical links and VSAN's to connect the new SAN
- create additional vhba in the service profile, and move them to the new VSAN
This allows you to migrate, read from the old storage, and write to the new one (e.g. with storage vmotion)
02-27-2014 09:08 AM
I was wondering if this might not be accomplished by using VSANs but wasn't positive. So it is just as simple as you have outlined?
02-27-2014 09:21 AM
Indeed, it's simple, and btw. even works, if the SAN fabrics are Brocade, which doesn't support VSAN's; VSAN's are used UCS internally for routing the traffic, and on exiting fabric interconnect to the Brocade, the VSAN tag is removed.
02-27-2014 09:24 AM
The fabrics are indeed Brocade but that sounds like that is a non issue. Excellent. I will proceed with that and reply about that results.
Thank you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: