Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 7
Registered: ‎01-26-2017

Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

We migrated from a 4B to 8B SAN Switch by creating an XISL link and getting the configs to probagate to the new switch including the logical switches(FAB A). We created different domain IDs on the new switch and zones propagated successfully. We then shutdown the old switch, removed the fibre cables and connected the new 8b replacement connecting the fibre cables afterwards. Powered switch back on and moved the ports to the respective logical switches and enabled the ports.

What we then noticed was that most of the hosts are still connected via a single path along FAB B. However when we go to the hosts, we see dual paths as should be. The storage ports however are all connected.

For VMware connected via XtremIO, we had to reboot the VM's to login properly via both paths, but for the Unix hosts, connected to VMax 200k reboot did not resolve the issue. See sample of one such Unix host. Zones are in place as well. We also have connections to VNX array which are impacted as well. Any ideas.

We have done the following

 

shutdown the modules and powered them backup

Move the ports to the default switch and back to the logical switch

disabled and enabled the ports

deleted and created sone zones manually

created new zones for new hosts and issue is the same.

 

We believe it might be some setting on the switch, but can't figure out what this might be.

 

root@dominodr # symaccess -sid 536 list logins | egrep -i "ff057af1|f057a8f"            
21000024ff057af1 Fibre dominodr          hba2-B            3dab00 Yes    Yes
21000024ff057af1 Fibre dominodr          hba2-B            3dab00 Yes    Yes

 

root@dominodr # fcinfo hba-port
HBA Port WWN: 21000024ff057af1
        OS Device Name: /dev/cfg/c1
        Manufacturer: QLogic Corp.
        Model: QLE2560
        Firmware Version: 05.06.04
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 2.21;
        Serial Number: RFD1107M01650
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000024ff057af1
HBA Port WWN: 21000024ff057a8f
        OS Device Name: /dev/cfg/c2
        Manufacturer: QLogic Corp.
        Model: QLE2560
        Firmware Version: 05.06.04
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 2.21;
        Serial Number: RFD1106M00672
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000024ff057a8f

 

root@dominodr # luxadm -e port
/devices/pci@0,600000/pci@0/pci@8/QLGC,qlc@0/fp@0,0:devctl         CONNECTED
/devices/pci@1,700000/pci@0/pci@9/QLGC,qlc@0/fp@0,0:devctl         CONNECTED

 

Symmetrix ID: 000296700536

        Device Name            Dir                  Device               
---------------------------- ------- -------------------------------------
                                                                      Cap
Physical               Sym   SA Smiley Tongue   Config        Attribute    Sts   (MB)
---------------------------- ------- -------------------------------------
c1t5000097550086005d1* 0006E 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d2* 0006F 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d3* 00070 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d4* 00071 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d5* 00072 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d6* 00073 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d7* 00074 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d8* 00075 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d9* 00076 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086005d1* 00077 01D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d1* 0006E 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d2* 0006F 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d3* 00070 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d4* 00071 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d5* 00072 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d6* 00073 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d7* 00074 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d8* 00075 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d9* 00076 03D:005 TDEV          N/Grp'd      RW       6
c1t5000097550086085d1* 00077 03D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086004d0* 00001 01D:004 TDEV          N/Grp'd ACLX WD       6
c2t5000097550086045d1* 0006E 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d2* 0006F 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d3* 00070 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d4* 00071 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d5* 00072 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d6* 00073 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d7* 00074 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d8* 00075 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d9* 00076 02D:005 TDEV          N/Grp'd      RW       6
c2t5000097550086045d1* 00077 02D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d1* 0006E 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d2* 0006F 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d3* 00070 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d4* 00071 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d5* 00072 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d6* 00073 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d7* 00074 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d8* 00075 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d9* 00076 04D:005 TDEV          N/Grp'd      RW       6
c2t50000975500860C5d1* 00077 04D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower19c  00077 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower20c  00076 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower21c  00075 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower22c  00074 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower23c  00073 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower24c  00072 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower25c  00071 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower26c  00070 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower27c  0006F 01D:005 TDEV          N/Grp'd      RW       6
/dev/rdsk/emcpower28c  0006E 01D:005 TDEV          N/Grp'd      RW       6

 

 

 

 

Brocade Moderator
Posts: 258
Registered: ‎08-31-2009

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

Hello,

 

Please can you provide the results of the commands from the switches for the impacted devices (specify port#):

switchshow

portloginshow

nszonemember -n

nsshow -r

 

 

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Occasional Contributor
Posts: 7
Registered: ‎01-26-2017

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

i will send the list of 3 impacted hosts below

=========

crane

=========

switch_50:FID50:admin> zoneshow crane_VMAX3_536_2D_P5_A
 zone:  crane_VMAX3_536_2D_P5_A
                21:00:00:24:ff:49:ec:a5; 50:00:09:75:50:08:60:45

switch_50:FID50:admin> nodefind 21:00:00:24:ff:49:ec:a5
Local:
 Type Pid    COS     PortName                NodeName                 SCR
 N    34d800;      3;21:00:00:24:ff:49:ec:a5;20:00:00:24:ff:49:ec:a5; 0x00000003
    FC4s: IPFC FCP
    Fabric Port Name: 20:9f:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 21:00:00:24:ff:49:ec:a5
    Device type: Physical Initiator
    Port Index: 159
    Share Area: Yes
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No
    Aliases: crane_hba_S7_P21_A
switch_50:FID50:admin> switchshow | grep 159
 159    2   31   34d800   id    N8         Online      FC  F-Port  21:00:00:24:ff:49:ec:a5
switch_50:FID50:admin> portloginshow 2/31
Type  PID     World Wide Name        credit df_sz cos
=====================================================
  fe  34d800 21:00:00:24:ff:49:ec:a5     5  2048   8  scr=0x3
  ff  34d800  21:00:00:24:ff:49:ec:a5     0     0   8  d_id=FFFFFC 
switch_50:FID50:admin> nszonemember -n | more

Port: 2/31      Pid: 0x34d800
        Zoned Members: 3 devices
                Pid: 0x34d800
                Pid: 0x34ed00
                Pid: 0x34ca40

 N    34d800;      3;21:00:00:24:ff:49:ec:a5;20:00:00:24:ff:49:ec:a5; 0x00000003
    FC4s: IPFC FCP
    Fabric Port Name: 20:9f:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 21:00:00:24:ff:49:ec:a5
    Port Index: 159
    Share Area: Yes
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No

 

==============

P2EDRHDBPP02

==============

switch_50:FID50:admin> zoneshow P2EDRHDBD02_VNX5500_SPB0_A
 zone:  P2EDRHDBD02_VNX5500_SPB0_A
                10:00:00:00:c9:8b:f7:de; 50:06:01:68:3d:e0:08:f7

switch_50:FID50:admin> nodefind 10:00:00:00:c9:8b:f7:de
Local:
 Type Pid    COS     PortName                NodeName                 SCR
 N    34ad00;    2,3;10:00:00:00:c9:8b:f7:de;20:00:00:00:c9:8b:f7:de; 0x00000003
    FC4s: IPFC FCP
    PortSymb: [34] "Emulex PPN-10:00:00:00:C9:8B:F7Smiley Very HappyE"
    NodeSymb: [51] "Emulex LPe1150-E FV2.82A4  DV7.2.20.006 P2EDRHDBD02"
    Fabric Port Name: 2e:4b:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 10:00:00:00:c9:8b:f7:de
    Device type: Physical Initiator
    Port Index: 331
    Share Area: Yes
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No
    Aliases:

 

switch_50:FID50:admin> switchshow | grep 331
 331    9   43   34ad00   id    N4         Online      FC  F-Port  10:00:00:00:c9:8b:f7:de

Port: 9/43      Pid: 0x34ad00
        Zoned Members: 5 devices
                Pid: 0x34ad00
                Pid: 0x34bb40
                Pid: 0x34d8c0
                Pid: 0x34ec00
                Pid: 0x34da40

 N    34ad00;    2,3;10:00:00:00:c9:8b:f7:de;20:00:00:00:c9:8b:f7:de; 0x00000003
    FC4s: IPFC FCP
    PortSymb: [34] "Emulex PPN-10:00:00:00:C9:8B:F7Smiley Very HappyE"
    NodeSymb: [51] "Emulex LPe1150-E FV2.82A4  DV7.2.20.006 P2EDRHDBD02"
    Fabric Port Name: 2e:4b:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 10:00:00:00:c9:8b:f7:de
    Port Index: 331
    Share Area: Yes
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No

 

============

DOMINODR

============

switch_50:FID50:admin> switchshow | grep 23
  23    2    7   34fa00   id    N8         Online      FC  F-Port  21:00:00:24:ff:05:7a:8f

 

switch_50:FID50:admin> portloginshow 2/7
Type  PID     World Wide Name        credit df_sz cos
=====================================================
  fe  34fa00 21:00:00:24:ff:05:7a:8f     5  2048   8  scr=0x3
  ff  34fa00  21:00:00:24:ff:05:7a:8f     0     0   8  d_id=FFFFFC 

 

 N    34fa00;      3;21:00:00:24:ff:05:7a:8f;20:00:00:24:ff:05:7a:8f; 0x00000003
    FC4s: IPFC FCP
    Fabric Port Name: 20:17:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 21:00:00:24:ff:05:7a:8f
    Port Index: 23
    Share Area: Yes
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No

 

Port: 2/7       Pid: 0x34fa00
        Zoned Members: 7 devices
                Pid: 0x34fa00
                Pid: 0x34fd00
                Pid: 0x34ed00
                Pid: 0x34ca40
                Pid: 0x34b880
                Pid: 0x34cbc0
                Pid: 0x34ad80

 

============

falcondr - This one works

============

switch_50:FID50:admin> zoneshow Falcondr_VNX5500_SPB0_A
 zone:  Falcondr_VNX5500_SPB0_A
                10:00:00:90:fa:18:15:04; 50:06:01:68:3d:e0:08:f7

switch_50:FID50:admin> nodefind 10:00:00:90:fa:18:15:04
Local:
 Type Pid    COS     PortName                NodeName                 SCR
 N    340209;      3;10:00:00:90:fa:18:15:04;20:00:00:90:fa:18:15:04; 0x00000003
    FC4s: IPFC FCP
    PortSymb: [34] "Emulex PPN-10:00:00:90:FA:18:15:04"
    NodeSymb: [48] "Emulex MC-FC82E FV2.00A4  DV7.2.50.007 FALCON-DR"
    Fabric Port Name: 20:90:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 20:16:00:05:1e:9a:a9:db
    Device type: NPIV Unknown(initiator/target)
    Port Index: 144
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
    LSAN: No
    Aliases:
switch_50:FID50:admin> switchshow | grep 144
 144    2   16   340200   id    N8         Online      FC  F-Port  1 N Port + 6 NPIV public
switch_50:FID50:admin> portloginshow 2/16
Type  PID     World Wide Name        credit df_sz cos
=====================================================
  fd  34020f 10:00:00:00:c9:87:87:b0     8  2112   8  scr=0x3
  fd  34020a 10:00:00:00:c9:df:41:e2     8  2112   8  scr=0x3
  fd  340209 10:00:00:90:fa:18:15:04     8  2112   8  scr=0x3
  fd  340207 10:00:00:00:c9:9b:70:fa     8  2112   8  scr=0x3
  fd  340206 10:00:00:90:fa:76:2f:7c     8  2112   8  scr=0x3
  fd  340205 10:00:00:90:fa:18:15:1a     8  2112   8  scr=0x3
  fe  340200 20:16:00:05:1e:9a:a9:db     8  2112   8  scr=0x0
  ff  34020f  10:00:00:00:c9:87:87:b0    12  2048   c  d_id=FFFFFC 
  ff  34020a  10:00:00:00:c9:df:41:e2    12  2048   c  d_id=FFFFFA 
  ff  34020a  10:00:00:00:c9:df:41:e2    12  2048   c  d_id=FFFFFC 
  ff  340209  10:00:00:90:fa:18:15:04    12  2048   c  d_id=FFFFFC 
  ff  340207  10:00:00:00:c9:9b:70:fa    12  2048   c  d_id=FFFFFC 
  ff  340206  10:00:00:90:fa:76:2f:7c    12  2048   c  d_id=FFFFFC 
  ff  340205  10:00:00:90:fa:18:15:1a    12  2048   c  d_id=FFFFFC 
  ff  340200  20:16:00:05:1e:9a:a9:db     0     0   8  d_id=FFFFFA 
switch_50:FID50:admin>

 N    340200;      3;20:16:00:05:1e:9a:a9:db;10:00:00:05:1e:9a:a9:db; 0x00000000
    Fabric Port Name: 20:90:c4:f5:7c:1d:2b:a2
    Permanent Port Name: 20:16:00:05:1e:9a:a9:db
    Port Index: 144
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Partial: No

 


Port: 2/7       Pid: 0x34fa00
        Zoned Members: 7 devices
                Pid: 0x34fa00
                Pid: 0x34fd00
                Pid: 0x34ed00
                Pid: 0x34ca40
                Pid: 0x34b880
                Pid: 0x34cbc0
                Pid: 0x34ad80

 

Brocade Moderator
Posts: 258
Registered: ‎08-31-2009

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

What FOS level are you using?

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Occasional Contributor
Posts: 7
Registered: ‎01-26-2017

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

New 8B Switch is

 

Kernel:     2.6.14.2
Fabric OS:  v7.3.1d
Made on:    Wed Nov 11 21:15:02 2015
Flash:      Thu Dec 8 18:48:08 2016
BootProm:   1.0.16

 

Old 4B Switch was

 

Kernel:     2.6.14.2
Fabric OS:  v7.3.1
Made on:    Thu Dec 11 21:25:09 2014
Flash:      Thu Feb 4 13:19:35 2016
BootProm:   1.0.16

 

This is got from FAB B which is yet to be migrated to 8B.

 

 

Brocade Moderator
Posts: 258
Registered: ‎08-31-2009

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

[ Edited ]

Ok, I'm thinking this issue could be relative to defect # 590946. See release note from 7.4.1e attached (page 46).

Check the condition if it match with yours operations or something around and try to apply recovery indicated.

 

 

 

 

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Occasional Contributor
Posts: 7
Registered: ‎01-26-2017

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

Also, i 've also been notified that now all the Unix (Solaris hosts) are impacted

Brocade Moderator
Posts: 258
Registered: ‎08-31-2009

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

In that case, I'm thinking that logs of the switches need to be analyzed.

Have you reported those issues to the technical support of your OEM?

 

 

 

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Brocade Moderator
Posts: 216
Registered: ‎03-29-2011

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

Hi,

 

are you able to share the output from the name server (nodefind) for a few of the disk which are not accessible from the hosts, please?

 

 




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
External Moderator
Posts: 4,880
Registered: ‎02-23-2004

Re: Interesting issue here. We migrated one of our SAN Fabrics from a DCX 8510 (4b) to a DCX 8510 (8b),

@Delingerr

 

I don't want to put the salt in the soup, but as per my opinion you problem is mainly related to WWN Based Persistent PID, wich is mandatory required by some EMC Storage, - and AIX OS - !

 

Such issue is know in AIX environments however I noticed you use as OS Unix "Solaris", and to be honest I'm not sure if Solaris required that the Switch must be set such WWN Based Persistent PID.

 

at this point I would suggest to check first if such Settings are required by Solaris.

 

 

 

 

TechHelp24

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.