Solved!
Go to SolutionCisco MDS 9216i migration to Cisco MDS 9222i
I plan to migrate all our Windows and VMWare ESX Hosts from two Cisco MDS 9216i fabric switches to two new Cisco MDS 9222i switches.
I have two question
Can I backup the VSAN zones on each of the MDS9216i switches and restore them to new VSans and zonesets that I create in the MDS9222i switches in order to recreate the same zoneset configuration with zones,storage and device aliases?
You can simpily create equivelent VSAN on new 9222i switches, then make TE port on 9216i and 9222i, TE port will
carray forward exist VSAN configuration from 9216i to 9222i, also ZONE and ZONESET configuration. after that, you can plug and attach FC cables from 9216i to new 9222i. if you have IVR or FCIP running on 9216i, there will be other consideration while perform the migration.
Dynamox and doob,Thank you for your response. The MDS9216i zoneset was created on VSAN1,the default VSAN,I would like to change that on the new MDS9222i since it is not recommended by both Cisco and EMC to use VSAN1 for production so propagating the VSAN from the MDS9216i to the MDS9222i via ISL would not achieve the desired result.I will be able to edit the backup file of VSAN1 before restoring it to the new MDS9222i switch as a different VSAN,so backup and restore might work best in this situation unless there is something I am missing? The other question is should I create a different VSAN on MDS9222i switch two? In other words,create VSAN20 on MDS9222i switch 1 and VSAN21 on MDS9222i switch 2? The old switches are currently not connected together and we do not have any ISL links or IVR running.I noticed that the 2 old switches have zonesets on VSAN1,this could pose a problem if we decide to connect the two switches together via ISL and poropage the VSANs.
christopher_ime
6 Operator
•
1962 Posts
531
0
Posted March 10th, 2012 01:00
JoeO,
I am curious, how did your switch migration go? You bring up a good point about using this opportunity to stop using the default VSAN on the new switches which as you point out makes you ineligible for an ISL.
Did you have any issues with your Windows and ESX servers?
dynamox
11 Legend
•
20419 Posts
•
87439 Points
924
0
Posted December 7th, 2011 14:00
you could that but you could also ISL 9222i's to 9216i, allow all zoneset/zones to propagate to 9222is and then as you migrate systems/storage to 9222i, decommissions 9216i's. Take a look at Cisco documentation, specifically full zoneset distribution.