Home > FAS3040, Hardware, Home Lab, NetApp > NetApp: Can’t find any disk shelves? How to switch your FC ports to Initiator from Target.

NetApp: Can’t find any disk shelves? How to switch your FC ports to Initiator from Target.

If you’re following my Home Lab quest, you’ll note that I’ve picked up a couple of FAS3040’s.  The first goal is to try to get some surplus disk shelves working on it.  I have another post about the trials and tribulations associated with “BAD RAID LABEL” issues.  However, LONG before I got to that, I had an issue with not being able to see the disks at all.

The FAS3040 comes with 4 on board FC ports – 0a/0b/0c/0d.  So I figured I’d take a DS14MK2 disk shelf and connect it, boot, and find the shelves and sort out any ownership type of issues.  I didn’t anticipate not being able to find any disks.

Below is a sample of what you might see if you boot normally:

Phoenix TrustedCore(tm) Server
Copyright 1985-2004 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 2.2.0
Portions Copyright (c) 2006 Network Appliance, Inc. All Rights Reserved
CPU= AMD Opteron(tm) Processor 250 X 2
Testing RAM
512MB RAM tested
4096MB RAM installed
Fixed Disk 0: STEC    NACF1GM1U-B11

Boot Loader version 1.6
Copyright (C) 2000-2003 Broadcom Corporation.
Portions Copyright (C) 2002-2008 NetApp

CPU Type: AMD Opteron(tm) Processor 250

Starting AUTOBOOT press Ctrl-C to abort…
Loading x86_64/kernel/primary.krn:………….0x200000/42699096 0x2ab8958/15834456 0x39d26b0/4665549 0x3e4577d/3 Entry at 0x00202018
Starting program at 0x00202018
Press CTRL-C for special boot menu
Sun Aug  4 21:20:25 GMT [nvram.battery.state:info]: The NVRAM battery is currently ON.
Sun Aug  4 21:20:38 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1b.
Sun Aug  4 21:20:38 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1d.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1c.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1a.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4a.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4b.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4c.
Sun Aug  4 21:20:39 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4d.

NetApp Release 7.3.1.1: Mon Apr 20 22:45:56 PDT 2009
Copyright (c) 1992-2008 NetApp.

As you can see, there are some “Initialization failed” on various ports.  From the listing, you can tell that I have a u nit with a couple of extra 4 port FC HBA’s.   If you choose to boot into Maintenance Mode, and run “fcadmin config” you’ll see:

*> fcadmin config

                  Local
Adapter Type      State                  Status
—————————————————
0a   target      CONFIGURED.            offline
0b   target      CONFIGURED.            offline
0c   target      CONFIGURED.            offline
0d   target      CONFIGURED.            online

 

So no big deal.  They’re set as Target ports so that hosts can connect to them.  Great.  Except we want them to connect OUT to a shelf.  So we need to switch them. 

You might try to run “fcadmin config -t initiator 0a”.  However, you may get a notice saying that you “cannot perform this task” due to something like “FCP is not running, cannot change configuration without FCP”.  Great.  So we can’t run FCP because we have no bootable/running OnTAP because we have no disks.  So we can’t run the command we need because we have no disks, so that we can attach disks and install the OS.  And that sucks.

https://communities.netapp.com/thread/3922 in this thread, I found my answer.  Looks like “rkaramchedu1” had a similar situation.  Apparently if you issue a “set-defaults” at the LOADER> prompt, the system will return to defaults.  Specifically, FC adapters 0b/0d will be set as INITIATOR.

After running “set-defaults”, reboot the unit, and go back into maintenance mode and “fcadmin config” should now show:

*> fcadmin config

                  Local
Adapter Type      State                  Status
—————————————————
0a   target      CONFIGURED.            offline
0b   initiator   CONFIGURED.            offline
0c   target      CONFIGURED.            offline
0d   initiator   CONFIGURED.            online

Now, you should be able to hook up your shelf and proceed with setup.  Now of course, you COULD use some of the other HBA’s if they happen to be INITIATOR ports.  But let’s assume that the surplus unit you might be using, has been stripped of all its goodies.

 

Advertisements
Categories: FAS3040, Hardware, Home Lab, NetApp
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: