There’s a growing demand for qualified analysts who can make sense of Big Data. With an MS in Data Analytics, you can become the data mining, management, mapping, and munging expert that today’s leading corporations desperately need.
Change Cisco 9148s F port into FL port failed
Hi, everyone,
I am trying to configure a Cisco MDS 9148s fiber channel switch. Everything looks good:
For Interface fc1/11 and fc1/12, each has fiber cable connected to the storage HP MSA 2052 controller( The MSA has two controller:A and B)
Based on my past experience and this link below:
https://overlaid.net/2014/08/16/fibre-channel-fc-basics-for-ccie-dc/
The fc1/11 and fc1/12 should be configured as FL mode instead of F mode though the Switch auto negotiated into F.
Now I am trying to change it from F mode into FL mode:
The service obviously was interruped.
When I set the mode back to AUTO, the service was recovered.
My questions is: Why would the interface fc1/11 and fc1/12 become "notConnected" after changing them into FL mode? isn't FL the right mode for these two interfaces? (because they both are connected to the controller of the storage.)
The reason I want to do this change is becaues the MSA 2052 only see 5 of the HOST WWN, but I actually connected 10 servers to 4 switches, should have 20 HOST WWN show up in the MSA 2052. I feel the fc1/11 and fc/12 interfaces might be the problem because my old SAN which use two MDS 9124 configured fc1/7 and fc1/8 as the FL mode.
Anyone has experience to configure both this Cisco MDS 9148s and HP MSA 2052 storage?
I am trying to configure a Cisco MDS 9148s fiber channel switch. Everything looks good:
cisco9148s51# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 auto on up swl F 16 --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
For Interface fc1/11 and fc1/12, each has fiber cable connected to the storage HP MSA 2052 controller( The MSA has two controller:A and B)
Based on my past experience and this link below:
https://overlaid.net/2014/08/16/fibre-channel-fc-basics-for-ccie-dc/
The fc1/11 and fc1/12 should be configured as FL mode instead of F mode though the Switch auto negotiated into F.
Now I am trying to change it from F mode into FL mode:
cisco9148s51# config t
Enter configuration commands, one per line. End with CNTL/Z.
cisco9148s51(config)# interface fc1/11
cisco9148s51(config-if)# switchport mode FL
cisco9148s51(config-if)# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 FL -- notConnected swl -- -- --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
The service obviously was interruped.
fc1/11 2 FL -- notConnected swl -- -- --
When I set the mode back to AUTO, the service was recovered.
My questions is: Why would the interface fc1/11 and fc1/12 become "notConnected" after changing them into FL mode? isn't FL the right mode for these two interfaces? (because they both are connected to the controller of the storage.)
The reason I want to do this change is becaues the MSA 2052 only see 5 of the HOST WWN, but I actually connected 10 servers to 4 switches, should have 20 HOST WWN show up in the MSA 2052. I feel the fc1/11 and fc/12 interfaces might be the problem because my old SAN which use two MDS 9124 configured fc1/7 and fc1/8 as the FL mode.
Anyone has experience to configure both this Cisco MDS 9148s and HP MSA 2052 storage?
Who is Participating?
LVL 57
no zoneset name zoneset1 vsan 2 to get rid of it completely and then copy/paste it back after changing with notepad?
Not really my area, but generally, port operation mode depends on what is port type on the other end.
Cisco MDS 9000 Family Fabric Manager Configuration Guide - Interface Configuration
F Port
In fabric port (F port) mode, an interface functions as a fabric port. This port may be connected to a peripheral device (host or disk) operating as an N port. An F port can be attached to only one N port. F ports support class 2 and class 3 service.
FL Port
In fabric loop port (FL port) mode, an interface functions as a fabric loop port. This port may be connected to one or more NL ports (including FL ports in other switches) to form a public arbitrated loop. If more than one FL port is detected on the arbitrated loop during initialization, only one FL port becomes operational and the other FL ports enter nonparticipating mode. FL ports support class 2 and class 3 service.
Cisco MDS 9000 Family Fabric Manager Configuration Guide - Interface Configuration
The drawing doesn't relate to your scenario, it has a JBOD which is a box full of individual disks without controller which sit in a loop and each disk has its own WWN. A loop is for multiple devices to attach to (like Token Ring or Thick Ethernet if you remember them)
Your MSA has a controller in it so it is an individual device with one WWN*, It is not a JBOD. it doesn't sit in a loop with other devices. It should be F port.
You say you have 4 switches but I see no E ports connecting the switches together, if you have four fibre** channel switches then I would expect them to be in two domains so the ISLs between them (fiber** cable) should show as E ports.
*or one WWN per controller.
**Note the correct spelling of fibre channel and the glass fiber.
Your MSA has a controller in it so it is an individual device with one WWN*, It is not a JBOD. it doesn't sit in a loop with other devices. It should be F port.
You say you have 4 switches but I see no E ports connecting the switches together, if you have four fibre** channel switches then I would expect them to be in two domains so the ISLs between them (fiber** cable) should show as E ports.
*or one WWN per controller.
**Note the correct spelling of fibre channel and the glass fiber.
Handy,
Thank you for the comment, I do have another old setup by using two MDS 9124 fiber switches (switch57 and switch59) connect to one MSA 2132 which has two controllers. It's been running for 10 years in production. The interface speed is 4G, and the 4 new switches are an upgrade in terms of the speed and port numbers.
In this old setup, the interface fc1/7 is plugged into controller A, and fc1/8 is plugged into controller B of the MSA 2132, and both interface are in FL mode, this is the only difference I could find when comparing the old setup with the new setup. that's why I assume it might work to change the new setup configuration based on the old setup?
Since I want individual multiple path from each of the host server HBA to the MSA SAN storage, I prefer not to use E port to connect all the switches together such that one switch failure will not bother any other switches, only need to unplug the cables on the failed switch and plug into any of the rest three good switches. The switch did fail twice in the past 10 years, that's one of the major reasons why I buy 4 switches instead of 2 to give myself some extra capacity for emergency situation.
Thank you for the comment, I do have another old setup by using two MDS 9124 fiber switches (switch57 and switch59) connect to one MSA 2132 which has two controllers. It's been running for 10 years in production. The interface speed is 4G, and the 4 new switches are an upgrade in terms of the speed and port numbers.
In this old setup, the interface fc1/7 is plugged into controller A, and fc1/8 is plugged into controller B of the MSA 2132, and both interface are in FL mode, this is the only difference I could find when comparing the old setup with the new setup. that's why I assume it might work to change the new setup configuration based on the old setup?
switch57# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 F off up swl F 4 --
fc1/2 2 F off up swl F 4 --
fc1/3 2 F off up swl F 4 --
fc1/4 2 F off up swl F 4 --
fc1/5 2 F off up swl F 4 --
fc1/6 2 F off up swl F 4 --
fc1/7 2 FL -- up swl FL 4 --
fc1/8 2 FL -- up swl FL 4 --
fc1/9 1 F off sfpAbsent -- -- --
fc1/10 1 F off sfpAbsent -- -- --
fc1/11 1 F off sfpAbsent -- -- --
fc1/12 1 F off sfpAbsent -- -- --
fc1/13 1 F off sfpAbsent -- -- --
fc1/14 1 F off sfpAbsent -- -- --
switch59# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 4 --
fc1/2 2 auto on up swl F 4 --
fc1/3 2 auto on up swl F 4 --
fc1/4 2 auto on up swl F 4 --
fc1/5 2 auto on up swl F 4 --
fc1/6 2 auto on up swl F 4 --
fc1/7 2 auto on up swl FL 4 --
fc1/8 2 auto on up swl FL 4 --
fc1/9 1 auto on sfpAbsent -- -- --
fc1/10 1 auto on sfpAbsent -- -- --
fc1/11 1 auto on sfpAbsent -- -- --
Since I want individual multiple path from each of the host server HBA to the MSA SAN storage, I prefer not to use E port to connect all the switches together such that one switch failure will not bother any other switches, only need to unplug the cables on the failed switch and plug into any of the rest three good switches. The switch did fail twice in the past 10 years, that's one of the major reasons why I buy 4 switches instead of 2 to give myself some extra capacity for emergency situation.
Loop mode was default for the old MSA2000. Newer one defaults to point-to-point which is more sensible. There is a "set host-parameters" CLI command to change it or I think it's exposed in the SMU GUI too but better to use point-to-point (F port) anyway.
It was a weird kludge on the original one (Host Port Interconnects) that connected controller 1's A port to controller 2's B port but they don't do that on newer models so no need to use loop.
If you don't want the new system to see the old system then no ISLs / dual fabric is good.
It was a weird kludge on the original one (Host Port Interconnects) that connected controller 1's A port to controller 2's B port but they don't do that on newer models so no need to use loop.
If you don't want the new system to see the old system then no ISLs / dual fabric is good.
Handy, thanks for explanation. Below is my switch topology drawing and the MSA 2052 host page, do you think that it might be the configuration problem of the MSA to cause it only show 5 host WWN instead of 20 WWN? (10 servers connected to the 4 switches, each server has one HBA with dual port)
cisco9148s51# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 auto on up swl F 16 --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
fc1/15 1 auto on sfpAbsent -- -- -- --
cisco9148s53# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 auto on up swl F 16 --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
fc1/15 1 auto on sfpAbsent -- -- -- --
cisco9148s55# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 auto on up swl F 16 --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
fc1/15 1 auto on sfpAbsent -- -- -- --
fc1/16 1 auto on sfpAbsent -- -- -- --
fc1/17 1 auto on sfpAbsent -- -- -- --
fc1/18 1 auto on sfpAbsent -- -- -- --
fc1/19 1 auto on sfpAbsent -- -- -- --
cisco9148s57# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 2 auto on up swl F 16 --
fc1/2 2 auto on up swl F 16 --
fc1/3 2 auto on up swl F 16 --
fc1/4 2 auto on up swl F 16 --
fc1/5 2 auto on up swl F 16 --
fc1/6 2 auto on sfpAbsent -- -- -- --
fc1/7 2 auto on sfpAbsent -- -- -- --
fc1/8 2 auto on sfpAbsent -- -- -- --
fc1/9 2 auto on sfpAbsent -- -- -- --
fc1/10 2 auto on sfpAbsent -- -- -- --
fc1/11 2 auto on up swl F 16 --
fc1/12 2 auto on up swl F 16 --
fc1/13 1 auto on sfpAbsent -- -- -- --
fc1/14 1 auto on sfpAbsent -- -- -- --
fc1/15 1 auto on sfpAbsent -- -- -- --
fc1/16 1 auto on sfpAbsent -- -- -- --
You need to look at the interfaces on the MSA to make sure they are set to FC rather than 10Gb Ethernet as they support both. You also need to check the zoning on the switches to make sure the hosts are allowed to see the new SAN.
All interfaces on the MSA are set to FC.
and all the switch zoning have been confirmed to be correct.
All four switches(51, 53, 55, 57) configurations are exactly the same by cloning except the hostname and ip addresse.
and all the switch zoning have been confirmed to be correct.
cisco9148s51# show zoneset
zoneset name zoneset1 vsan 2
zone name zone1to11 vsan 2
interface fc1/1 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone1to12 vsan 2
interface fc1/1 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone2to11 vsan 2
interface fc1/2 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone2to12 vsan 2
interface fc1/2 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone3to11 vsan 2
interface fc1/3 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone3to12 vsan 2
interface fc1/3 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone4to11 vsan 2
interface fc1/4 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone4to12 vsan 2
interface fc1/4 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone5to11 vsan 2
interface fc1/5 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone5to12 vsan 2
interface fc1/5 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone6to11 vsan 2
interface fc1/6 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone6to12 vsan 2
interface fc1/6 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone7to11 vsan 2
interface fc1/7 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone7to12 vsan 2
interface fc1/7 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone8to11 vsan 2
interface fc1/8 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone8to12 vsan 2
interface fc1/8 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone9to11 vsan 2
interface fc1/9 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone9to12 vsan 2
interface fc1/9 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
zone name zone10to11 vsan 2
interface fc1/10 swwn 20:00:00:de:fb:94:19:c0
interface fc1/11 swwn 20:00:00:de:fb:94:19:c0
zone name zone10to12 vsan 2
interface fc1/10 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
cisco9148s51#
cisco9148s51#
cisco9148s51#
All four switches(51, 53, 55, 57) configurations are exactly the same by cloning except the hostname and ip addresse.
That zoning doesn't make sense to me (although I really know Brocade not Cisco).
I would expect
to see something like
zone name server1storage2
member swwn 20:01:00:e0:8b:39:a9:07
member swwn 20:00:00:20:37:af:a5:93
where two or more WWNs are members of the zone.
20:00:00:de:fb:94:19:c0 is a Cisco WWN, I wouldn't expect to see that in the config at all.
I would expect
to see something like
zone name server1storage2
member swwn 20:01:00:e0:8b:39:a9:07
member swwn 20:00:00:20:37:af:a5:93
where two or more WWNs are members of the zone.
20:00:00:de:fb:94:19:c0 is a Cisco WWN, I wouldn't expect to see that in the config at all.
Oh I get it, port zoning.
You did change the swwn after cloning?
zone name zone8to12 vsan 2
interface fc1/8 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
means connect port 8 of the switch that has WWN of 20:00:00:de:fb:94:19:c0 to port 12 of the switch that has the WWN 20:00:00:de:fb:94:19:c0
You did change the swwn after cloning?
zone name zone8to12 vsan 2
interface fc1/8 swwn 20:00:00:de:fb:94:19:c0
interface fc1/12 swwn 20:00:00:de:fb:94:19:c0
means connect port 8 of the switch that has WWN of 20:00:00:de:fb:94:19:c0 to port 12 of the switch that has the WWN 20:00:00:de:fb:94:19:c0
As a reference, I copied the currently working config of the old two switches below for comparison, doesn't look like there is much difference
switch57# show zoneset
zoneset name zoneset1 vsan 2
zone name zone1to7 vsan 2
interface fc1/1 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone1to8 vsan 2
interface fc1/1 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
zone name zone2to7 vsan 2
interface fc1/2 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone2to8 vsan 2
interface fc1/2 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
zone name zone3to7 vsan 2
interface fc1/3 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone4to7 vsan 2
interface fc1/4 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone3to8 vsan 2
interface fc1/3 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
zone name zone4to8 vsan 2
interface fc1/4 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
zone name zone5to7 vsan 2
interface fc1/5 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone5to8 vsan 2
interface fc1/5 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
zone name zone6to7 vsan 2
interface fc1/6 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/7 swwn 20:00:00:0d:ec:aa:df:40
zone name zone6to8 vsan 2
interface fc1/6 swwn 20:00:00:0d:ec:aa:df:40
interface fc1/8 swwn 20:00:00:0d:ec:aa:df:40
switch57#
switch59# show zoneset
zoneset name zoneset1 vsan 2
zone name zone1to7 vsan 2
interface fc1/1 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name zone1to8 vsan 2
interface fc1/1 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
zone name zone2to7 vsan 2
interface fc1/2 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name zone2to8 vsan 2
interface fc1/2 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
zone name znoe3to7 vsan 2
interface fc1/3 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name znoe3to8 vsan 2
interface fc1/3 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
zone name znoe4to7 vsan 2
interface fc1/4 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name znoe4to8 vsan 2
interface fc1/4 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
zone name znoe5to7 vsan 2
interface fc1/5 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name znoe5to8 vsan 2
interface fc1/5 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
zone name znoe6to7 vsan 2
interface fc1/6 swwn 20:00:00:0d:ec:93:af:40
interface fc1/7 swwn 20:00:00:0d:ec:93:af:40
zone name znoe6to8 vsan 2
interface fc1/6 swwn 20:00:00:0d:ec:93:af:40
interface fc1/8 swwn 20:00:00:0d:ec:93:af:40
switch59#
20:00:00:de:fb:94:19:c0 is one of your old switches, 20:00:00:0d:ec:aa:df:40 is the other old one. Did you change the swwn in those statements to match on the new ones?
Handy, I think you probably find where the problem is. I just did a quick check, looks like all new four switches has the same wwn for each port zoning.
So how can I change all the wwn in a quick way? I certainly can wipe off switch 53, 55, and 57, and do the manual configuration from the scratch instead of cloning to cause this problem.
So how can I change all the wwn in a quick way? I certainly can wipe off switch 53, 55, and 57, and do the manual configuration from the scratch instead of cloning to cause this problem.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
