VMware Solutions Discussions

Initiators not logging in to FAS2050

mattmullen
17,960 Views

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

11 REPLIES 11
Public