Unsolved
This post is more than 5 years old
1 Rookie
•
30 Posts
0
1259
July 14th, 2014 22:00
Cisco settings
Hi All,
We have access to 4 core switches of the customer. 2 switches in Fab A and 2 switches in Fab B. All these 4 switches are MDS-9513 switches with version 5.2.8d.
There are around 14 more switches in both Fab A and Fab B for which we dont have the access. It is managed by the customer directly which are the edge switches and principal switches for the fabric.
Also the core switch is different and principal switch is different. We have access to only the core switches and no access to principal switches.
With this setup we need to do 2 things :
Point 1 : In Global zone policies, the propagation mode is currently set to Active zoneset but this needs to be changed to Full zoneset for all the switches in the fabric (including core,principal and edge switches)
Current setup :
Fabric Switch Zone Behaviour Propagation Mode Smart ZoningBehaviour
Fabric A site A -9521ca deny activeZoneset disable
Fabric A site B -9521ca deny activeZoneset disable
Fabric B site A -9522cb deny activeZoneset disable
Fabric B site B -9522cb deny activeZoneset disable
To be changed to :
Fabric Switch Zone Behaviour Propagation Mode Smart ZoningBehaviour
Fabric A Site A - 9521ca deny fullZoneset disable
Fabric A Site B - 9521ca deny fullZoneset disable
Fabric B Site A - 9522cb deny fullZoneset disable
Fabric B Site B - 9522cb deny fullZoneset disable
Point 1 : Queries :
~ Is this a non-disruptive change ?
~ What is the commands or steps to change this ?
~ Can we do this from Core switches or principal switches first ?
~ Will the changes be propagated to all switches in the fabric when we do from core or principal switches ?
~ Is this changes on the vsan wide or not ?
~ Also will the changes will propagate using any of the CFS applications mentioned here. If so which CFS application will spread the changes to all switches in the fabric ?
show cfs application
----------------------------------------------
Application Enabled Scope
----------------------------------------------
ntp No Physical-fc-ip
fscm Yes Physical-fc
role Yes Physical-fc-ip
rscn No Logical
radius No Physical-fc-ip
tacacs Yes Physical-fc-ip
fctimer No Physical-fc
syslogd No Physical-fc-ip
callhome Yes Physical-fc-ip
fcdomain No Logical
fc-redirect Yes Physical-fc
device-alias Yes Physical-fc
Total number of entries = 12
Point 2 :
In Domain Manager Configuration :
The Config Domain ID should be changed to the value currently running and to be static. Contiguous Allocation could be changed to FALSE
Current setup:
Fabric Switch VSAN Id Enable Running DomainId Config DomainId
Fabric A site A-9521ca TRUE 0x30(48) 0
Fabric A site B-9521ca TRUE 0xb6(182) 0
Fabric B site B-9522cb 1 TRUE 0x23(35) 0
Fabric B site B-9522cb 1 TRUE 0xde(222) 0
Fabric B site B-9522cb 20 TRUE 0x29(41) 0
Fabric B site A-9522cb 20 TRUE 0x12(18) 0
Fabric B site B-9522cb 40 TRUE 0x50(80) 0
To be Changed to :
Fabric Switch VSAN Id Enable Running DomainId Config DomainId Config Type
Fabric A site A-9521ca TRUE 0x30(48) 48 static
Fabric A site B-9521ca TRUE 0xb6(182) 182 static
Fabric B site B-9522cb 1 TRUE 0x23(35) 35 static
Fabric B site A-9522cb 1 TRUE 0xde(222) 222 static
Fabric B site B-9522cb 20 TRUE 0x29(41) 41 static
Fabric B site A-9522cb 20 TRUE 0x12(18) 18 static
Fabric B site B-9522cb 40 TRUE 0x50(80) 80 static
Point 2 : Queries :
~ Is this a non-disruptive change ?
~ What is the commands or steps to change this ?
~ Can we do this from Core switches or principal switches first ?
~ Will the changes be propagated to all switches in the fabric when we do from core or principal switches ?
~ Is this changes on the vsan wide or not ? Because domain id is different for different vsan eventhough the switch is the same.
~ Also will the changes will propagate using any of the CFS applications mentioned here. If so which CFS application will spread the changes to all switches in the fabric ?
can anyone please reply to this.
Daries
1 Rookie
•
30 Posts
0
July 16th, 2014 06:00
Hi,
Thank you for the reply.
As per your reply,
Option 1 :The zone database propagation is triggered only during the next zoneset activation for that particular VSAN. So you will need to be careful and find out which physical switch has the most up-to-date local zone database for each VSAN and copy the zoning database to all other switches that are inconsistent. Once the zoning database is consistent on all the switches, you could enable the zoneset distribution to FULL.
Option 2 : You could also enable zoneset distribution to FULL on the switch which has the most up-to-date zoning database and wait for the next zoneset activation (from the same switch). This will trigger propagation to all other switches. Then check if the zoning database is consistent on all the switches and then enable the zoneset distribution to FULL for the other switches. Please do keep in mind that this has to be done for each VSAN separately.
In our case, we dont have access to the principal switches and right now we are using only the core switches for Zoning changes and this core switch has the latest up to date full zone DB.
So i believe the core switch will be the best candidate to start with, by following option 2 of your reply
Right now we have this setting in place : This is the core switch
css9521ca# show zone status vsan 10
VSAN: 10 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
rscn-format: fabric-address
Default zone:
qos: none broadcast: unsupported ronly: unsupported
Full Zoning Database :
DB size: 436676 bytes
Zonesets:8 Zones:658 Aliases: 202
Active Zoning Database :
DB size: 48508 bytes
Name: Fabric_A Zonesets:1 Zones:644
Status:
So when I run the below command :
conf t
zoneset distribute full vsan 10 (where X is the vsan number)
exit
show zone status Vsan 10
copy run start
On this particular switch for this vsan 10, it should show as below. Could you please confirm this ?
css9521ca# show zone status vsan 10
VSAN: 10 default-zone: deny distribute: full Interop: default
mode: basic merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
rscn-format: fabric-address
Default zone:
qos: none broadcast: unsupported ronly: unsupported
Full Zoning Database :
DB size: 436676 bytes
Zonesets:8 Zones:658 Aliases: 202
Active Zoning Database :
DB size: 48508 bytes
Name: Fabric_A Zonesets:1 Zones:644
Status:
So by running this command, we are only making the vsan 10 to distribute fully on that particular core switch.
As of now we are using only the core switch to do the zoning changes and not using any other edge switches for zoning.(there are around 14 more edge switches and a principal switch in the same fabric)
For eg : if we have 2 switches in a same fabric:
css9521ca# show vsan
vsan 1 information
name:VSAN0001 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
vsan 10 information
name:VSAN0010 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:up
vsan 4079:evfp_isolated_vsan
vsan 4094:isolated_vsan
nss9521ca# show vsan
vsan 1 information
name:VSAN0001 state:active
interoperability mode:default
loadbalancing:src-id/dst-id
operational state:up
vsan 10 information
name:VSAN0010 state:active
interoperability mode:default
loadbalancing:src-id/dst-id
operational state:up
vsan 30 information
name:VSAN0030 state:active
interoperability mode:default
loadbalancing:src-id/dst-id
operational state:up
vsan 4079:evfp_isolated_vsan
vsan 4094:isolated_vsan
Queries :
~ Now when I run the command on switch css9521ca (first switch) then it means I am changing the vsan distribute mode to full only for vsan 10 on css9521ca ?
~ This willnot make any changes to the switch nss9521ca(second switch) - vsan 10 though this is part of the same fabric itself ?
~ If it doesnot change then I need to execute the same commands on this nss9521ca switch also for vsan 10 again ?
~ Do I need to do this change on vsan 1 also or not ?
~ As we are doing all the zoning changes only from the core switches - 4 switches for which we have the access for, do we really need to execute these commands on each and every switch because we willnot do any zoning changes other than those 4 switches.
Also regarding Point 2 of my initial query :
~ Can we do this from Core switches or principal switches first?
You could do it in any order you prefer. Make sure you take Config backups before you start.
So we need to take the backup of the vsan and also the running config. Is this sufficient to proceed ?
Thanks & Regards,
Sri Brindha Ravi
Managed Services
Bangalore,India
Email : sri.ravi@emc.com
Office : +91-80-67375753
EMC²
where information lives
All information in this email should be considered EMC Confidential Information.
The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorized to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited