Fibre Channel (SAN)

Reply
New Contributor
Posts: 2
Registered: ‎08-09-2008

FC routing question

Hi! My first post over here

I got this strange issue I experience on a core formed of DCXs.

I've replaced some of the fields to be compliant with my company policy.

DCX_CORE_A:user_name> lsanzoneshow -w 21:00:00:1b:32:83:25:9d -s      
Fabric ID: x1 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  EXIST                                  
        50:05:07:68:01:20:38:6e  EXIST                                  
        50:05:07:68:01:20:39:2b  EXIST                                  
Fabric ID: x3 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  EXIST                                  
        50:05:07:68:01:20:38:6e  Imported                               
        50:05:07:68:01:20:39:2b  Imported                             

For the other adapter of the server, I've got the normal output, "Exist" in the edge fabric where is cabled and "Imported" in the other edge fabric:

DCX_CORE_B:user_name> lsanzoneshow -w 21:00:00:1b:32:83:e8:95 -s      

Fabric ID: y1 Zone Name: LSAN_server_name_HBA1_storage_name_ZONE
        21:00:00:1b:32:83:e8:95  Imported                               
        50:05:07:68:01:10:38:6e  EXIST                                  
        50:05:07:68:01:10:39:2b  EXIST                                  
Fabric ID: y3 Zone Name: LSAN_server_name_HBA1_storage_name_ZONE
        21:00:00:1b:32:83:e8:95  EXIST                                  
        50:05:07:68:01:10:38:6e  Imported                               
        50:05:07:68:01:10:39:2b  Imported                             

I know that devices should be in one of the following states. But I do not understand why an HBA appear with EXIST in both edge fabrics.

Did anybody experienced this, or have an explanation for it ?

Unfortunately I do not have access on server - but Administrator is telling that he have rescaned paths, adapters, disabled/enabled/ rebooted - everything. No need to mention that paths through the 21:00:00:1b:32:83:25:9d do not appear, and in the edge fabric which appear above as "Fabric ID: x1" I cannot find the WWPN with nodefind command.

                 Configured - Device is configured to be in an   

                 LSAN, but the device is not imported nor does it

                 exist in this fabric.

                 EXIST - Device exists in this fabric (the fabric

                 of the zone entry).

                 Initializing - Device is in an intermediate

                 state. It is not yet imported into the fabric.

                 Imported - Device has been imported (proxy

                 created) into this fabric.

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

Re: FC routing question

Hi -

answer's in your question : as WWPN cannot be found by nodefind in its (edge) fabric, device can't be imported. See fcrproxydevshow. No dev, no proxy. No proxy, no FCR.

Before answering FC routing question, you should consider answering simple SAN question : why device isn't logged in fabric ?

Check SFP/cable/port/HBA and have WWPN found by nodefind, no more issue with FC routing then

Hope this helps

Kind regards,

--

david

New Contributor
Posts: 2
Registered: ‎08-09-2008

Re: FC routing question

Hi David!

Sorry if my initial question was misleading. I thought I stated that in the device originating edge fabric - things look fine, while in the edge fabric where it should be Imported , device do not appear. I'll do some investigation to show why this seem a strange case:

Originating edge fabric ( Fabric ID: x3 in Core)

Edge_Fabric_A :user_name> nodefind 21:00:00:1b:32:83:25:9d
Local:
Type Pid    COS     PortName                NodeName                 SCR
N    2dca00;      3;21:00:00:1b:32:83:25:9d;20:00:00:1b:32:83:25:9d; 3
    FC4s: FCP
    NodeSymb: "QLE2460 FW:v4.04.09 DVR:v8.02.01-k1-vmw48"
    Fabric Port Name: 20:ca:00:05:1e:36:24:02
    Permanent Port Name: 21:00:00:1b:32:83:25:9d
    Device type: Physical Initiator
    Port Index: 202
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Aliases: FAB_server_name_HBA2
Edge_Fabric_A :user_name> lsanzoneshow -w 21:00:00:1b:32:83:25:9d -s
Fabric ID: 1 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  EXIST
        50:05:07:68:01:20:38:6e  Configured
        50:05:07:68:01:20:39:2b  Configured
Edge_Fabric_A :user_name> switchshow | grep 202
202    7   26   2dca00   id    N4   Online           F-Port  21:00:00:1b:32:83:25:9d
Edge_Fabric_A :user_name> portloginshow 7/26
Type  PID     World Wide Name        credit df_sz cos
=====================================================
  fe  2dca00  21:00:00:1b:32:83:25:9d     3  2048   8  scr=3
  ff  2dca00  21:00:00:1b:32:83:25:9d     0     0   8  d_id=FFFFFA
  ff  2dca00  21:00:00:1b:32:83:25:9d     0     0   8  d_id=FFFFFC

Core Fabric :

DCX_CORE_A:user_name> lsanzoneshow -w 21:00:00:1b:32:83:25:9d -s      
Fabric ID: x1 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  EXIST                                   <-- here should have been Imported
        50:05:07:68:01:20:38:6e  EXIST                                  
        50:05:07:68:01:20:39:2b  EXIST                                  
Fabric ID: x3 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  EXIST                                  <-- correct
        50:05:07:68:01:20:38:6e  Imported                               
        50:05:07:68:01:20:39:2b  Imported 

Edge Fabric where the Storage resides ( Fabric ID: x1 in Core)

Edge_Fabric_B :user_name> nodefind 21:00:00:1b:32:83:25:9d
No device found
Edge_Fabric_B :user_name> lsanzoneshow -w 21:00:00:1b:32:83:25:9d -s
Fabric ID: 1 Zone Name: LSAN_server_name_HBA2_storage_name_ZONE
        21:00:00:1b:32:83:25:9d  Configured                    <<--weird ?
        50:05:07:68:01:20:38:6e  EXIST
        50:05:07:68:01:20:39:2b  EXIST

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

Re: FC routing question

Sorry for misunderstanding Florin

both targets 50:05:07:68:01:20:38:6e  & 50:05:07:68:01:20:39:2b  are in "Configured" state in Edge Fabric A, so I don't think it's weird to have initiator 21:00:00:1b:32:83:25:9d in the same state in Edge Fabric B. "Configured" state  seen _on edge fabrics_ is OK.

On both edge fabrics, could you provide us a zoneshow extract from active configuration with LSAN_server_name_HBA2_storage_name_ZONE (showing aliases / WWPNs)

On Core fabric, could you provide us fcrfabricshow, fcrproxydevshow, fcrproxyconfig & fcrresourceshow ?

Are you able to access storage in local Edge Fabric A from initiator 21:00:00:1b:32:83:25:9d ?

Kind regards,

--

david

Join the Community

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