Subscribe

Initiators not logging in to FAS2050

Hi all,

Just want to start off by saying I'm a somewhat new user to NetApp and SAN in general,  so it's very possible I am missing something simple here.   We have a FAS2050 in our lab and I am having some difficulty getting the system to log in any initiators.  I have managed to bring up the FCP service,  and the adapters appear to be functioning in target mode.  I have also created an initiator group and mapped it to a LUN.  Here is the output...

NETAPP1> fcp status
FCP service is running.
NETAPP1> fcp show adapter
Slot:                    0a
Description:             Fibre Channel Target Adapter 0a (Dual-channel, QLogic 2432 (2462) rev. 2)
Adapter Type:            Local
Status:                  ONLINE
FC Nodename:             50:0a:09:80:88:8c:5b:bc (500a0980888c5bbc)
FC Portname:             50:0a:09:81:88:8c:5b:bc (500a0981888c5bbc)
Standby:                 No

Slot:                    0b
Description:             Fibre Channel Target Adapter 0b (Dual-channel, QLogic 2432 (2462) rev. 2)
Adapter Type:            Local
Status:                  ONLINE
FC Nodename:             50:0a:09:80:88:8c:5b:bc (500a0980888c5bbc)
FC Portname:             50:0a:09:82:88:8c:5b:bc (500a0982888c5bbc)
Standby:                 No

NETAPP1> igroup show
    initiator_group_1 (FCP) (ostype: vmware):
        21:00:00:1b:32:80:36:16 (not logged in)
        10:00:00:00:c9:76:ff:b9 (not logged in)
        21:01:00:1b:32:a0:36:16 (not logged in)
        20:42:00:0d:ec:b2:2a:c0 (not logged in)

NETAPP1> lun show -m
LUN path                            Mapped to          LUN ID  Protocol
-----------------------------------------------------------------------
/vol/MyVol/Datastore1               initiator_group_1        0       FCP

As you can see above,  none of the initiators are logged in.  However on the MDS that the 0a and 0b ports are connected to,  I see both the initiators and the target ports logged into the fabric:

zoneset name ALL_ZONES vsan 2000
  zone name Fabric_A vsan 2000
  * fcid 0xb40000 [pwwn 50:0a:09:81:88:8c:5b:bc]   <----  0a
    pwwn 10:00:00:00:c9:f1:fd:c3
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0xb40100 [pwwn 21:00:00:1b:32:80:36:16]
    pwwn 10:00:00:00:c9:93:f9:a3
    pwwn 21:00:00:c0:dd:11:bb:21
  * fcid 0xb40010 [pwwn 10:00:00:00:c9:76:ff:b9]

zoneset name ALL_ZONES vsan 2001
  zone name Fabric_B vsan 2001
  * fcid 0x400004 [pwwn 50:0a:09:82:88:8c:5b:bc]   <------ 0b
    pwwn 10:00:00:00:c9:f1:fd:c1
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0x400100 [pwwn 21:01:00:1b:32:a0:36:16]
    pwwn 10:00:00:00:c9:93:f9:a1
    pwwn 21:00:00:c0:dd:11:bb:23

Are there any additional configuration steps that I am missing?  Is there any other diagnostic information that I could look at to see why the initiators might be prevented from logging in?   Every so often,   I see a message:  "Tue Apr 26 00:02:33 GMT [NETAPP1: sysconfig.sysconfigtab.openFailed:notice]: sysconfig: table of valid configurations (/etc/sysconfigtab) is missing."   and also "NETAPP1> Tue Apr 26 00:50:00 GMT [NETAPP1: mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.3.1.1.8O: No such file or directory"   Could this have anything to do with the problem? 

Thanks,

Matt

Re: Initiators not logging in to FAS2050

If zoning is correct , please check u r igroup whether u have the correct host vmware hba wwns ... ?

Re: Initiators not logging in to FAS2050

Please run this command on filer to see weather host has connectivity to filer or not
Fcp show initiator //. U should see u r hba wwn here

Re: Initiators not logging in to FAS2050

Here are the PWWNs for one of the initiators:

21:00:00:1b:32:80:36:16

21:01:00:1b:32:a0:36:16

NETAPP1> igroup show
    initiator_group_1 (FCP) (ostype: vmware):
        21:00:00:1b:32:80:36:16 (not logged in) <----
        10:00:00:00:c9:76:ff:b9 (not logged in)
        21:01:00:1b:32:a0:36:16 (not logged in)  <----
        20:42:00:0d:ec:b2:2a:c0 (not logged in)

NETAPP1> fcp show initiator
Initiators connected on adapter 0a:
        None connected.

Initiators connected on adapter 0b:
        None connected.

I have also uploaded a screen shot of the storage adapters pane in vCenter.

Re: Initiators not logging in to FAS2050

when you ran the

fcp show initiator

NO iniators are connected so this tells zoning is not correct.

please check the zoning & see weather the created zone are active or not.

Re: Initiators not logging in to FAS2050

Zoning looks ok to me.  Zone is active and both the target and initiators are logged into the fabric...

zoneset name ALL_ZONES vsan 2000
  zone name Fabric_A vsan 2000
  * fcid 0xb40000 [pwwn 50:0a:09:81:88:8c:5b:bc]  <--- NetApp 0a
    pwwn 10:00:00:00:c9:f1:fd:c3
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0xb40100 [pwwn 21:00:00:1b:32:80:36:16]  <----- Initiator port A
    pwwn 10:00:00:00:c9:93:f9:a3
    pwwn 21:00:00:c0:dd:11:bb:21
  * fcid 0xb40010 [pwwn 10:00:00:00:c9:76:ff:b9]

zoneset name ALL_ZONES vsan 2001
  zone name Fabric_B vsan 2001
  * fcid 0x400004 [pwwn 50:0a:09:82:88:8c:5b:bc]    <---- NetApp 0b
    pwwn 10:00:00:00:c9:f1:fd:c1
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0x400100 [pwwn 21:01:00:1b:32:a0:36:16]  <---- Initiator port B
    pwwn 10:00:00:00:c9:93:f9:a1
    pwwn 21:00:00:c0:dd:11:bb:23

Re: Initiators not logging in to FAS2050

But in your zone names i am not seeing the below members in the zone's u created...

21:00:00:1b:32:80:36:16 (not logged in) <----
      
        21:01:00:1b:32:a0:36:16 (not logged in)  <----

Re: Initiators not logging in to FAS2050

Here they are...

DCN-9120# show zoneset active
zoneset name ALL_ZONES vsan 2000
  zone name Fabric_A vsan 2000
  * fcid 0xb40000 [pwwn 50:0a:09:81:88:8c:5b:bc]
    pwwn 10:00:00:00:c9:f1:fd:c3
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0xb40100 [pwwn 21:00:00:1b:32:80:36:16]  <-----
    pwwn 10:00:00:00:c9:93:f9:a3
    pwwn 21:00:00:c0:dd:11:bb:21
  * fcid 0xb40010 [pwwn 10:00:00:00:c9:76:ff:b9]

zoneset name ALL_ZONES vsan 2001
  zone name Fabric_B vsan 2001
  * fcid 0x400004 [pwwn 50:0a:09:82:88:8c:5b:bc]
    pwwn 10:00:00:00:c9:f1:fd:c1
    pwwn 28:36:00:0c:29:00:00:07
    pwwn 28:36:00:0c:29:00:00:08
  * fcid 0x400100 [pwwn 21:01:00:1b:32:a0:36:16]  <-------
    pwwn 10:00:00:00:c9:93:f9:a1
    pwwn 21:00:00:c0:dd:11:bb:23

Re: Initiators not logging in to FAS2050

Are these adapters serving LUNs to another hosts ?

If not, try offline then online adapters and check if the initiators looged in properly.

Also, check the active configuration on the switch side.

on the switch check if fcping to the initiatiators and hosts  responds well.

Re: Initiators not logging in to FAS2050

I have a very similar issue on my system, albeit with a slight extra layer of complexity.

I'm running a FAS2040 A/A (8.0.1 RC2 7-Mode) with 2 x DS4243 shelves running 24 x 450GB SAS dries each.I also have a SATA shelf hanging off this system.

Each shelf is for a seperate internal department.

The NetApp is connected into a Cisco MDS 9124 fabric switch with uplinks to two seperate MDS 9124 switches, located in seperate racks.

On each MDS, I have 6 x HP360 G7 ESXi 4.1 hosts, each with HP 8GB HBA storage adapters.

My issue is that I am unable to see any LUN's created on my NetApp through my ESXi hosts.

FCP service is running and here is the output of some commands:

fcp status


FCP service is running.


UKNETAPP2> fcp show adapter


Slot:                    0b


Description:             Fibre Channel Target Adapter 0b (Dual-channel, QLogic 2432 (2462) rev. 2)


Adapter Type:            Local


Status:                  ONLINE


FC Nodename:             50:0a:09:80:88:7d:27:f0 (500a0980887d27f0)


FC Portname:             50:0a:09:81:88:7d:27:f0 (500a0981887d27f0)


Standby:                 No


UKNETAPP2> fcadmin config

                  Local  


Adapter Type      State                  Status


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


  0a   initiator  CONFIGURED.            online


  0b   target     CONFIGURED             online

UKNETAPP2>  lun show -m


LUN path                            Mapped to          LUN ID  Protocol


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


/vol/Engineering/Engineering        WB_ENG_ESXi_01          0       FCP


UKNETAPP2> fcp show initiator


Initiators connected on adapter 0b:


Portname                  Group


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


50:01:43:80:09:ae:d4:ae   FCP_uk-pthomas7-lp2; WB_IT_ESXi_01

UKNETAPP2> igroup show


    FCP_uk-pthomas7-lp2 (FCP) (ostype: vmware):


        50:01:43:80:09:ae:d4:ae (logged in on: 0b, vtic)       


    WB_ENG_ESXi_01 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d4:80 (not logged in)


    WB_ENG_ESXi_02 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d4:a6 (not logged in)


    WB_ENG_ESXi_03 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d4:1c (not logged in)


    WB_ENG_ESXi_04 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d3:a8 (not logged in)


    WB_IT_ESXi_01 (FCP) (ostype: vmware):


        50:01:43:80:09:ae:d4:ae (logged in on: 0b, vtic)       


    WB_TRN_ESXi_01 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d3:e6 (not logged in)


        50:01:43:80:09:ac:cf:12 (not logged in)


    WB_TRN_ESXi_02 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d3:cc (not logged in)


        50:01:43:80:09:ac:ce:88 (not logged in)


    WB_TRN_ESXi_03 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d3:cc (not logged in)


        50:01:43:80:09:ac:ce:88 (not logged in)


        50:01:43:80:09:ac:d3:e6 (not logged in)


    WB_TRN_ESXi_04 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:d3:8e (not logged in)


        50:01:43:80:09:ac:cf:12 (not logged in)


        50:01:43:80:09:ac:d3:cc (not logged in)


    WB_TRN_ESXi_05 (FCP) (ostype: vmware):


        50:01:43:80:09:ac:cf:12 (not logged in)


        50:01:43:80:09:ac:ce:88 (not logged in)


        50:01:43:80:09:ac:d3:cc (not logged in)


UKNETAPP2> fcp show initiator


Initiators connected on adapter 0b:


Portname                  Group


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


50:01:43:80:09:ae:d4:ae   FCP_uk-pthomas7-lp2; WB_IT_ESXi_01


UKNETAPP2> fcp topology show


Switches connected on adapter 0b:


Mon Jun 13 00:07:33 GMT [UKNETAPP2: scsitarget.ispfct.mserr:warning]: The Fibre Channel fabric Management Server request (GID_PN) sent from adapter 0b failed with reason code 0x5 (Server busy/cannot perform operation), explanation code 0x0 (No additional data), and response code 0x8001.

   Switch Name: WB-FSW9124-020


Switch Vendor: Cisco Systems, Inc.


Switch Release: 4.1(3a)


Switch Domain: 111


    Switch WWN: 20:04:00:05:73:c5:cf:41

Port    Port WWPN                State    Type     Attached WWPN           Port ID


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


1/5     20:05:00:05:73:c5:cf:40  Online   F-Port   50:0a:09:81:98:7d:27:f0        -


1/6     20:06:00:05:73:c5:cf:40  Online   F-Port   50:0a:09:81:88:7d:27:f0        -


1/7     20:07:00:05:73:c5:cf:40  Online   F-Port   50:01:43:80:09:ae:d4:ae        -

UKNETAPP2> Mon Jun 13 00:07:33 GMT last message repeated 2 times

UKNETAPP2>

WB-FSW9124-020# show zoneset active
zoneset name ZONESET_V1 vsan 1
  zone name Z_FC1_5_FC1_1_V1 vsan 1
     interface fc1/5 swwn 20:00:00:05:73:c5:cf:40
     interface fc1/1 swwn 20:00:00:05:73:c5:cf:40

  zone name Z_FC1_6_FC1_2_V1 vsan 1
     interface fc1/6 swwn 20:00:00:05:73:c5:cf:40
     interface fc1/2 swwn 20:00:00:05:73:c5:cf:40

  zone name Z_FC1_7_FC1_5_V1 vsan 1
     interface fc1/7 swwn 20:00:00:05:73:c5:cf:40
     interface fc1/5 swwn 20:00:00:05:73:c5:cf:40

  zone name Z_FC1_7_FC1_6_V1 vsan 1
     interface fc1/7 swwn 20:00:00:05:73:c5:cf:40
     interface fc1/6 swwn 20:00:00:05:73:c5:cf:40

  zone name $default_zone$ vsan 1

zoneset name Zoneset1 vsan 4
  zone name Zone1 vsan 4
  * fcid 0x6f0100 [pwwn 50:0a:09:81:98:7d:27:f0] [UKNETAPP1]
  * fcid 0x6f0200 [pwwn 50:0a:09:81:88:7d:27:f0] [UKNETAPP2]
  * fcid 0x6f0000 [pwwn 50:01:43:80:09:ae:d4:ae] [WB_IT_ESXi_01]

  zone name $default_zone$ vsan 4
WB-FSW9124-020#

Im going round on this and am still waiting for NetApp to call back.

Any heplp would be appreciated!

Thanks.