Hi Wdey, Thanks for writing back. We are yet to refresh our fabric environment as it is still in planning phase but we will certainly follow best practices like Set Zone distribution to full and enhanced and static Domain ID's for each VSAN. Currently Device Alias zoning is used where the Alias for WWPN (World Wide Port Number) of the Initiator and target ports are added as the members to a zone. In our case due to Capex constraints we will be replacing SAN switches in different phases per quarter basis. 1st Quarter: Refersh Site B & C SAN Fabric followed by decommissioning of old switches. 2nd Quarter : Refresh Site A & D SAN Fabric followed by decommissioning of old switches. Do you have any documented procedure or best practice doc to implement the same ? Do you foresee any specific challenge with the introduction of new MDS 9710 in the Fabric except compatibility of NX-OS 5.2(1) and 6.2(1) which I had already verified ?
... View more
In the current setup I have 12 MDS 9513 switches (NX-OS 5.2(1)), 6 per fabric (Mesh Topology). Switches are distributed across different sites in following manner: 1) SIte A : 2 switches in Odd fabric and 2 switches in Even Fabric 2) Site B : 1 switch in Odd Fabric and 1 switch in Even Fabric 3) Site C : 1 switch in Odd Fabric and 1 switch in Even Fabric 4) Site D : 2 switches in Odd fabric and 2 switches in Even Fabric Odd Fabric : Production VSAN (100), Backup VSAN (300) Even Fabric : Production VSAN (200), Backup VSAN ( 400) Port Channel with 4 ISL links is configured between all the switches in each fabric. Site B and C are adjacent to each other separated by a wall, whereas Site A and D are 300 metres apart. Synchronous replication is configured between Site B<->C and Site A<->D. We need to replace all MDS 9513 with same number of MDS 9710 (16 Gbps) switches running at 6.2(1). Can someone please guide me to a step by step process for adding a new MDS 9710 switch (16 Gbps) switch in existing Mesh Topology fabric ?
... View more