Enable/Configure FC-AL/SAN Devices with cfgadm in Solaris

Solaris 9 requires some tinkering to play with SANs. This tech-recipe describes the procedure.

Note: These steps are not required for Solaris 10 which includes everything you need to connect to a SAN, even to boot from it. If you cannot see your SAN from Solaris 10, check your connections and the SAN. (Doing a probe-scsi-all from the ok prompt will let you know if the host can see the SAN. If it cannot, then Solaris will never be able to see it.)

The Sun StorEdge SAN Foundation Suite must be download and installed first.

Once that is installed and the host is rebooted, do not be sad that you still cannot see your SAN. It is downhill from here. Running the cfgadm command allows you to see your system devices and manage them. Here is sample output:

# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 fc-private connected configured unknown
c1:1 disk connected configured unknown
c1:1 disk connected configured unknown
c2 fc-fabric connected unconfigured unknown
c2:1 array-ctrl connected unconfigured unknown
c2:9 array-ctrl connected unconfigured unknown
c2:d array-ctrl connected unconfigured unknown
c3 fc-fabric connected unconfigured unknown
c3:8 array-ctrl connected unconfigured unknown
c3:c array-ctrl connected unconfigured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb0/4 unknown empty unconfigured ok

Note the c2 and c3 entries (of type fc-fabric). These are unconfigured (and therefore inaccessible). In this case, there are two FC-AL host adapters in the system connected to the SAN fabric, and these must be configured as with the following commands:

cfgadm -c configure c2
cfgadm -c configure c3

The commands you run (the device Ap_id you need to use) will vary, depending on host configuration. After running these commands, the output of cfgadm -al will show these devices and the corresponding LUNs as configured. Running format will now show these devices, and you will be ready to rock and newfs. If you see errors spewing out on the console about these new devices, do not worry. You will need to label these devices. (You will be prompted to so when selecting each disk in format.) That should quiet the errors.

 

About Quinn McHenry

Quinn was one of the original co-founders of Tech-Recipes. He is currently crafting iOS applications as a senior developer at Small Planet Digital in Brooklyn, New York.
View more articles by Quinn McHenry

The Conversation

Follow the reactions below and share your own thoughts.

  • VAIBHAV

    how to connect HP EVA 4100 SAN + 8 HDDs san switch to M4000

  • Anonymous

    Thanks for your post! sometimes you forget the basics caught up with the more complex HBA FCAL drivers!

    FYI: I also like to use the following to make sure I’ve scanned the bus and device tree thoroughly:

    ok> probe-scsi-all
    # luxadm -e forcelip
    # luxadm insert_device
    # drvconfig&&disks
    # luxadm probe
    # devfsadm
    # cfgadm -al

    Hope this help those of you lost within the SAN frabic like meee!! eeek!

    Merry Christmas and seasons greetings!