Vsan disappeared during Zones verification

[jjpeyrache]

Configuration

MDS9500 MDS9500

VSan3 Vsan1 Vsan4

isl

Vsan1 is for management purpose only

all zones has been created on VSAN3

then copied to Vsan4

during zones verifications on Vsan4

all zones dissapeared and also vlan4 disappeared ?

is it a normal behaviour since WWN are identical

on both vsan ?

thanks

JYP

[mrfrase]

Your VSAN 4 should not disappear. And the WWN's are ok in the different VSAN's

Are you using the copy Zone tool from Fabric Manager?

[jjpeyrache]

yes iused copy zone tool

JYP

[mrfrase]

I have tried this out in my lab on 2.0 code and I do not see the problem nor have I seen an issue like this in the past on earlier code. If you have the capability to recreate this issues please open a case with Cisco Support so we can get it properly documented

[jjpeyrache]

i will try and let you know result

JYP

[jjpeyrache]

reproduced with vsan 10 vsan 20 and vsan 1

attached logs

JYP

[mrfrase]

I have tried to make some sense of the process of what your going through with the copy of the zones to new VSAN. I see it in the logs the VSAN getting deleted. I see you are using FWWN based zoning which is not recommended but that is a different subject. I did build up a configuration using much of your same aliases and FWWNs and copied them to a new VSAN without problems. I recommend you go through the HP/Cisco TAC case process and open a issue with this to determine if this is a corner case or a bigger issue with code on the MDS.

[jjpeyrache]

thanks for your reply , i can open a TAC case but

i will not enable to do some test on MDS configuration because my customer is now starting

production and won't to stop it for test

so are they enough informations for working on ?

also let me know why FWWN based zoning is not recommended ?

thanks

JYP

[mrfrase]

FWWN is tied to Chassis, if you ever need to replace chassis of switch, you will need to start over with your zoning. WWN zoning is the the method to use for it gives you most flexability of moving devices around and abilities to use other security features in the MDS.

[jjpeyrache]

when you said chassis , this is hardware piece

that are completly passive ? or including mds

processor ?

restrictions for WWN zoning is when you need

to replace HBA then you need to replay with zoning

so in case of 300 HBA should be tricky to pay

with WWN zoning agree ?

JYP

[mrfrase]

The FWWN's are taken from the WWN of the SPROM on chassis. replace of Chassis results is change of SPROM, all FWWN's would change. For a 9216 or 9100 switch if you have a issue with supervisor that means chassis replacement.

Anytime a HBA is replaced in most SAN networks the Switch adminis involved anyway because of mapping on the storage, so allowing the new HBA into default zone to get WWN and zone to proper place is noe a big deal. I am not a SAN admin but 99% of the MDS switches I see at customers are by WWN, wonder why that is :-)

[jjpeyrache]

are they any best pratice document for zoning

implamentation of zoning on mds available ?

JYP