Upgrading from MDS 9396S to MDS 9396T.

[manoj-singh]

When I set a unique Domian ID on the new switch, create an ISL between the old and the new, why isn't the complete configuration such as zonesets, zone and fcalias copy over from old to new san switch? why do I have to manually create Fcalias/zones and Zonesets.

[Jason Mooney]

Hi Manoj-Singh,

I'm not sure what type of errors your are getting.

• Make sure your VSANs exist on your new switch show vsan
• Check the reason why the zoning didn't come over show zone status
  • The reason should also be logged in show logging logfile at the time of the attempted merge.
• Try bringin the zoning information over again.  Use the zoneset import interface <interface_id> vsan <vsan_id> command to import the zone set from the adjacent switch connected through the specified interface and VSAN.
  
  • For example: zoneset import interface fc1/3 vsan 2-5 would import the zone set from the switch connected through the fc1/3 interface for VSANs 2 through 5. 

This document may seem old, but all the concepts are the same for troubleshooting zone issues. https://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/troubleshooting/guide/ts_zones.pdf

[manoj-singh]

Thanks for your response Jason, I have created the high-level steps, please validate if they make sense, my understanding is with Enhanced VSAN the complete config including Zoneset and FCALIAS must flow from old switch to new. 

1. Confirm all active VSAN and IDS in MDS 9396S
2. Zoneset details n MDS 9396S
3. Interfaces in use like F and E in  MDS 9396S
4. Take screenshot of WWNs connected per port by running show flogi database - MDS 9396S
5. Document the Domain ID per VSAN - MDS 9396S
6. Firmware  to be upgraded - MDS 9396T.
7. Make a note of ports connected to Storage, Host and San Switch - MDS 9396S
8. Backup configuration - MDS 9396S
9. Configure unique Enhanced VSANs & Static Domain ID on the new San Switch - MDS 9396T and enable Enhanced VSAN in old Switch MDS 9396S.
10. Pre-create Interfaces & Trunking - switchport mode E - MDS 9396T.
11. Migrate Devices Port-by-Port -
12. Physically move cable to same port on 9396T
13. On New Switch - Verify device login

show flogi database

show interface fc1/9

1. Start with test or dev hosts, then production. Avoid bulk movement.
2. Remove ISL
3. Power Off the old switch MDS 9396S.

[Jason Mooney]

I always recommend collecting a show tech-support details | no more before you start any migration.  You can either capture the output in your terminal window and write it to a file, or redirect the output to a file on bootflash:/.  Here's an example show tech-support details > bootflash:/$(SWITCHNAME)-$(TIMESTAMP)_sh-ts-det.txt This will automatically populate the switchname and time it was taken.  The show tech will include your config, zoning, flogi's at the time, and many other detailed logs that are useful in troubleshooting if you run into an issue.

For #6 Firmware  to be upgraded - MDS 9396T.   Because this is a new switch the recommendation is to be running 9.4(2a).  I would also make sure to apply the 9.4(2a) EPLD upgrade.  This is disruptive, and this is the perfect time to make sure the one from the factory has the latest updates and fixes.

I would do the same thin on the 9396T after your migration so you have a good baseline record.

[manoj-singh]

I am migrating from 9396S to 9396T and this is an example, 9396S suppose has VSAN1 in enhanced zone with some valid zones, In the 9396T I shall create VSAN1 and change the zone type to Enhanced ? I believe this is expected, this has to be same for E port to come up, but what am I worrying is 9396T has zero zones or zonesets, while enabling the ISL, will there be any reverse action ? meaning I expect zone to be pulled from 9396S to 9396T and am assuming the same would happen and zones do not get wiped away..

[Jason Mooney]

Hi Manoj,

Yes, you are correct — both switches need to have the same VSANs created and the zoning mode (Basic or Enhanced) configured before bringing up the ISL. If they mismatch, the E-Port or port-channel will flap or stay down due to a zone merge failure.

However, even when zoning mode and VSANs match, zone sets and aliases do not automatically copy from one switch to another just by forming an ISL. The zoning database only synchronizes after a successful zone merge occurs — and only the active zoneset is propagated.

When a new switch (like your 9396T) with an empty zoning database connects via ISL to an existing fabric (like your 9396S), it will receive the zoning information — but only if the merge is successful. If there are mismatches in settings (e.g., Enhanced vs Basic zoning, conflicting zone DBs, or differing default zoning policies), the merge fails and the zoning does not propagate.

Important: The zoning database on the new switch (even if empty) will not overwrite the existing zoning on the old switch. Cisco MDS enforces merge logic that ensures the fabric with an active zoneset retains control.

To manually pull the zoning information from the existing switch, you can use the following command:

zoneset import interface fcX/Y vsan Z

This will import the active zoneset from the adjacent switch connected to the specified interface and VSAN.

Summary:

• Yes, zoning mode (Enhanced) and VSANs must match on both switches.
• The zoning DB won’t copy unless a zone merge is successful.
• An empty zoning DB on the new switch will not wipe anything on the existing switch.
• You can manually import the zoning if needed using the zoneset import command.

After bringing up the ISL, validate the merge result with:

show zone status
show logging logfile | include zone

Let me know if you’d like help reviewing the zoning config before enabling the ISL — I’m happy to assist.

Best regards,
Jason

---

Disclaimer: These are my personal responses and do not represent official guidance from Cisco Systems, Inc.

[Mant1978]

a new SAN switch to an existing fabric and setting a unique Domain ID, configurations like zonesets, zones, and fcalias are not automatically copied from the old switch to the new switch. Cuyahoga County Auditor You need to manually configure these elements on the new switch. This is because SAN switch fabrics operate with a distributed zoning architecture, and each switch maintains its own zoning information.