Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 7
Registered: ‎09-15-2010

Why some wwns not visible in the Access Gateway are visible in the switch Fabric

Hello everybody,

I will appreciate any input that help me to understand what is happening in the following issue :

I have an IBM  Blade Center working with NPIV connected to a Brocade switch configured as Access Gateway and the N port 15 connected to a Fabric formed for two Brocade 5000 switches .

Last week one of Virtual servers of this Blade Center lost one of its paths to the storage ( IBM SVC) .

The WWN c0:50:76:02:e1:4d:00:18 seems like it’s logged in the fabric However  it does not appear in the Access Gateway , obviously the Storage is not able to see it.

It looks like the nodefind and portshow command are showing incorrect information regarding some WWNs .

lib_bc4100_s1:admin> nodefind c0:50:76:02:e1:4d:00:18

Local:

Type Pid    COS     PortName                NodeName                 SCR

N    011e47;      3;c0:50:76:02:e1:4d:00:18;c0:50:76:02:e1:4d:00:18; 0

    Fabric Port Name: 20:1e:00:05:1e:04:96:cf

    Permanent Port Name: 20:0f:00:05:1e:bf:a3:3e

    Device type: NPIV Unknown(initiator/target)

    Port Index: 30

    Share Area: No

    Device Shared in Other AD: No

    Redirect: No

    Partial: No

    Aliases: encke

As you can see that wwn doe not appear in the AG , in fact the port where it used to be it does not appear ( I presume it is damaged).

Fabric Information :

        Attached Fabric Name            N_Ports

        ---------------------------------------------

        10:00:00:05:1e:04:96:cf         0;15;16

        ---------------------------------------------

N_Port information :

        Port  PortID        Attached PWWN        FO  FB   IP_Addr     F_Ports

        ---------------------------------------------------------------------

          0  0x010000  20:00:00:05:1e:04:96:cf   1   1    162.94.135.16   None

         15  0x011e00  20:1e:00:05:1e:04:96:cf   1   1    162.94.135.16   1;3;5;                                                                      7;8;9;10;11;12;13;14;

         16  0x011d00  20:1d:00:05:1e:04:96:cf   1   1    162.94.135.16   None

        ---------------------------------------------------------------------

F_Port information :

        Port  PortID     Attached PWWN          N_Port   Preferred N_port

        -------------------------------------------------------------------

          1  0x011e3d  21:00:00:1b:32:92:b4:22  15        None

          3  0x011e19  21:00:00:1b:32:93:7c:3d  15        None

          5  0x011e34  21:00:00:1b:32:9b:9e:89  15        None

          7  0x011e3b  21:00:00:1b:32:9c:52:9c  15        None

          7  0x011e3e  c0:50:76:02:e1:4c:00:04  15        None

          8  0x011e3c  21:00:00:1b:32:9c:a6:97  15        None

         10  0x011e09  21:00:00:1b:32:9c:6b:97  15        None

         11  0x011e39  21:00:00:24:ff:21:61:fa  15        None

         11  0x011e4b  c0:50:76:03:2c:af:00:08  15        None

         11  0x011e47  c0:50:76:03:2c:af:00:04  15        None

         11  0x011e08  c0:50:76:03:2c:af:00:26  15        None

         11  0x011e05  c0:50:76:03:2c:af:00:10  15        None

         11  0x011e07  c0:50:76:03:2c:af:00:18  15        None

         11  0x011e05  c0:50:76:03:2c:af:00:10  15        None

         11  0x011e29  c0:50:76:03:2c:af:00:10  15        None

         11  0x011e07  c0:50:76:03:2c:af:00:18  15        None

         11  0x011e08  c0:50:76:03:2c:af:00:26  15        None

         11  0x011e47  c0:50:76:03:2c:af:00:04  15        None

         11  0x011e2b  c0:50:76:03:2c:af:00:26  15        None

         11  0x011e2c  c0:50:76:03:2c:af:00:04  15        None

         11  0x011e46  c0:50:76:03:2c:af:00:18  15        None

         12  0x011e3a  21:00:00:24:ff:21:62:40  15        None

         12  0x011e4c  c0:50:76:03:2c:af:00:0a  15        None

         12  0x011e50  c0:50:76:03:2c:af:00:0c  15        None

         12  0x011e51  c0:50:76:03:2c:af:00:00  15        None

         12  0x011e48  c0:50:76:03:2c:af:00:06  15        None

         12  0x011e50  c0:50:76:03:2c:af:00:0c  15        None

         12  0x011e2a  c0:50:76:03:2c:af:00:0c  15        None

         13  0x011e3f  21:00:00:24:ff:21:62:58  15        None

         14  0x011e40  21:00:00:24:ff:21:65:56  15        None

        -------------------------------------------------------------------

And this is the switchshow  and portshow output of the fabric where the AG is connected.

login as: admin

Server refused our key

admin@162.94.135.16's password:

lib_bc4100_s1:admin> switchshow

switchName:     lib_bc4100_s1

switchType:     32.0

switchState:    Online

switchMode:     Native

switchRole:     Principal

switchDomain:   1

switchId:       fffc01

switchWwn:      10:00:00:05:1e:04:96:cf

zoning:         ON (lib_s1)

switchBeacon:   OFF

FC Router:      OFF

FC Router BB Fabric ID: 1

Address Mode:   0

Index  Port Address  Media Speed  State     Proto

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

  0   0   010000   id    N4   Online      FC  F-Port  20:00:00:05:1e:bf:a3:3e

  1   1   010100   id    N4   Online      FC  F-Port  50:05:07:68:01:40:4b:4a

  2   2   010200   id    N4   Online      FC  F-Port  21:00:00:e0:8b:93:5d:83

  3   3   010300   id    N4   No_Light    FC

  4   4   010400   id    N4   Online      FC  F-Port  50:05:07:68:01:4f:ff:f2

  5   5   010500   id    N4   Online      FC  F-Port  50:05:07:68:01:40:5a:d5

  6   6   010600   id    N4   Online      FC  F-Port  50:01:43:80:00:c5:55:5a

  7   7   010700   id    N4   No_Light    FC

  8   8   010800   id    N4   Online      FC  F-Port  50:05:07:63:09:03:85:a4

  9   9   010900   id    N4   Online      FC  F-Port  50:05:07:63:09:08:85:a4

10  10   010a00   id    N4   No_Light    FC

11  11   010b00   id    N4   No_Light    FC

12  12   010c00   id    N4   No_Light    FC

13  13   010d00   id    N4   Online      FC  F-Port  50:05:07:68:01:1f:ff:f2

14  14   010e00   id    N4   Online      FC  F-Port  50:05:07:68:01:10:5a:d5

15  15   010f00   id    N4   No_Light    FC

16  16   011000   id    N4   Online      FC  F-Port  50:06:01:60:41:e0:0a:db

17  17   011100   id    N4   No_Light    FC

18  18   011200   id    N4   Online      FC  F-Port  50:06:01:68:41:e0:0a:db

19  19   011300   id    N4   Online      FC  F-Port  10:00:00:00:c9:78:28:67

20  20   011400   id    N4   Online      FC  F-Port  50:05:07:68:01:40:4b:16

21  21   011500   id    N4   Online      FC  E-Port  50:00:51:ec:16:88:2e:7e "f                              cr_fd_160" (downstream)

22  22   011600   id    N4   Online      FC  F-Port  50:05:07:68:01:10:4b:4a

23  23   011700   id    N4   Online      FC  E-Port  10:00:00:05:1e:90:52:90 "l                              ib_bc5000_s3" (downstream)

24  24   011800   id    N4   No_Light    FC

25  25   011900   id    N4   Online      FC  F-Port  50:05:07:68:01:10:4b:16

26  26   011a00   id    N4   No_Light    FC

27  27   011b00   id    AN   No_Sync     FC

28  28   011c00   id    N4   Online      FC  F-Port  10:00:00:00:c9:9d:46:cd

29  29   011d00   id    N4   Online      FC  F-Port  20:10:00:05:1e:bf:a3:3e

30  30   011e00   id    N4   Online      FC  F-Port  1 N Port + 25 NPIV public

31  31   011f00   id    N4   Online      FC  E-Port  10:00:00:05:1e:90:52:90 "l                              ib_bc5000_s3"

lib_bc4100_s1:admin>

lib_bc4100_s1:admin> portshow 30

portIndex:  30

portName:

portHealth: No Fabric Watch License

Authentication: None

portDisableReason: None

portCFlags: 0x1

portFlags: 0x20b03       PRESENT ACTIVE F_PORT G_PORT NPIV LOGICAL_ONLINE LOGIN NOELP ACCEPT

portType:  10.0

POD  Port: Port is licensed

portState: 1    Online

Protocol: FC

portPhys:  6    In_Sync         portScn:   32   F_Port

port generation number:    0

state transition count:    0

portId:    011e00

portIfId:    4302001c

portWwn:   20:1e:00:05:1e:04:96:cf

portWwn of device(s) connected:

        21:00:00:1b:32:9c:6b:97

        21:00:00:1b:32:9c:8b:9c

        c0:50:76:02:e1:4d:00:00

        c0:50:76:02:e1:4d:00:10

        c0:50:76:02:e1:4d:00:08

        c0:50:76:02:e1:4d:00:18

        c0:50:76:03:2c:af:00:18

        21:00:00:24:ff:21:65:56

        21:00:00:24:ff:21:62:58

        c0:50:76:02:e1:4c:00:04

        21:00:00:1b:32:9c:a6:97

        21:00:00:1b:32:9c:52:9c

        c0:50:76:03:2c:af:00:04

        c0:50:76:03:2c:af:00:26

        c0:50:76:03:2c:af:00:0c

        c0:50:76:03:2c:af:00:10

        21:00:00:1b:32:93:7c:3d

        c0:50:76:03:2c:af:00:00

        c0:50:76:03:2c:af:00:0a

        c0:50:76:03:2c:af:00:08

        c0:50:76:03:2c:af:00:06

        21:00:00:1b:32:92:b4:22

        21:00:00:24:ff:21:62:40

        21:00:00:24:ff:21:61:fa

        21:00:00:1b:32:9b:9e:89

        20:0f:00:05:1e:bf:a3:3e

Distance:  normal

portSpeed: N4Gbps

Regular Contributor
Posts: 178
Registered: ‎04-21-2008

Re: Why some wwns not visible in the Access Gateway are visible in the switch Fabric

Hi -

Very strange that WWN is found in nameserver and not visible in AG switch ... I understand it's a virtual host and you are using nested NPIV, what kind of hypervisor are you using, and on which blade (= which internal port) is it running ? If you are dual fabric connected and after being sure multipathing is well configured on hypervisor, I would try to disable/enable hypervisor port on AG switch.

Could you provide switchshow / version on AG ?

Kind regards,

--

david

Occasional Contributor
Posts: 7
Registered: ‎09-15-2010

Re: Why some wwns not visible in the Access Gateway are visible in the switch Fabric

Hello David,

I have uploaded the Access Gateway supportshow in the first page of this thread and I am investigating about the hypervisor.

Thanks,

Martin

Regular Contributor
Posts: 178
Registered: ‎04-21-2008

Re: Why some wwns not visible in the Access Gateway are visible in the switch Fabric

I don't find wwn c0:50:76:02:e1:4d:00:18 in any portshow on AG ... It may be an hypervisor issue which doesn't "show" it anymore

Kind regards,

--

david

Occasional Contributor
Posts: 7
Registered: ‎09-15-2010

Re: Why some wwns not visible in the Access Gateway are visible in the switch Fabric

Yes the WWN c0:50:76:02:e1:4d:00:18 does not appear but If you see the port 9 in the AG is been showed as G port , I suspect that WWN used to be there. I also believe that this is a Blade issue and we are making arrangements to reboot that Blade , However my main concern is why that WWN appears  logged in the switch Fabric.I think  this WWN should not be logged in the switch fabric since is not present in the AG.  Obviously This wwn is not visible for the Storage array. Please correct me If I am wrong. 

Thanks a lot and kind regards

Martin

Regular Contributor
Posts: 178
Registered: ‎04-21-2008

Re: Why some wwns not visible in the Access Gateway are visible in the switch Fabric

That's why I asked you on which blade was running the hypervisor ... You don't seem to be sure where the wwn used to be, it's a little bit confusing : if you know which hypersivor is hosting your VM, you know on which blade it's running, thus on which internal port VM's wwn should appear.

Before rebooting blade, it may be useful to disable / enable internal port 9 (if it's the right one !) and then see if wwn c0:50:76:02:e1:4d:00:18 appears on AG port 9 (portshow) after new FLOGI/PLOGI.

Hope this helps

Kind regards,

--

david

Join the Community

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