Configuring Fibre Channel Devices With COMSTAR

You can set up and configure a COMSTAR target on a SPARC system or x86 system in a FC network environment and make it accessible to the storage network. Ensure the following prerequisite step has been completed:

• How to Create a Logical Unit

Configuring Fibre Channel Ports With COMSTAR

The Fibre Channel (FC) port provider can use the same HBAs that are used for the FC initiators. A given FC port can be used as an initiator or as a target, but not as both. You can also configure a dual port or quad port FC HBA so that a subset of the HBA ports is in target mode and the rest of the ports are in initiator mode.

The procedures in this section are specific to QLogic HBAs. The driver to use with HBAs in initiator mode is qlc, which is a Qlogic driver. The qlc driver works only in initiator mode, and cannot be used for target mode. The COMSTAR driver for a target QLogic 4G HBA is qlt.

Because initiator mode and target mode use different drivers, the driver you attach to an HBA port defines its function as a target or initiator. You can specify a driver for all the ports by specifying the PCI device ID of the HBA. Or, you can configure the driver on a port-by-port basis. Both methods use the update_drv command and are described in this section. For more information, see update_drv(1M).

How to Display Existing FC Port Bindings

Before making changes to the HBA ports, first check the existing port bindings.

1. Become an administrator.
2. Display what is currently bound to the port drivers.

   In this example, the current binding is pciex1077,2432.

   # mdb -k
   Loading modules: [ unix krtld genunix specfs ...
   > ::devbindings -q qlc
   30001617a08 pciex1077,2432, instance #0 (driver name: qlc)
   300016177e0 pciex1077,2432, instance #1 (driver name: qlc)
   > $q

How to Set All FC Ports to a Specific Mode

This procedure changes all ports on all HBAs with a specific PCI device ID to target mode. The PCI device ID number binds a driver to a port, thereby setting all the HBA ports with that PCI device ID, for example, all QLogic 4G PCI express HBAs, to target mode.

1. Become an administrator.
2. Remove the current binding.

   In this example, the qlc driver is actively bound to pciex1077,2432. You must remove the existing binding for qlc before you can add that binding to a new driver. Single quotation marks are required in this syntax.

   # update_drv -d -i 'pciex1077,2432' qlc
   Cannot unload module: qlc
   Will be unloaded upon reboot.

   This message does not indicate an error. The configuration files have been updated but the qlc driver remains bound to the port until the system is rebooted.

3. Establish the new binding.

   In this example, qlt is updated. Single quotes are required in this syntax.

   # update_drv -a -i 'pciex1077,2432' qlt
   devfsadm: driver failed to attach: qlt
   Warning: Driver (qlt) successfully added to system but failed to attach

   This message does not indicate an error. The qlc driver remains bound to the port, until the system is rebooted. The qlt driver attaches when the system is rebooted.

4. Reboot the system to attach the new driver. Then, recheck the bindings.

   # init 6
   .
   .
   .
   # mdb -k
   
   Loading modules: [ unix krtld genunix specfs dtrace ...
   > ::devbindings -q qlt
   30001615a08   pciex1077,2432, instance #0 (driver name: qlt)
   30001615e0    pciex1077,2432, instance #1 (driver name: qlt)
   > $q

5. Verify that the target mode framework has access to the HBA ports.

   # stmfadm list-target -v
   Target: wwn.210100E08BA54E60
   Operational Status : Offline
   Provider Name : qlt(1)
   Alias : -
   Sessions : 0
   Target: wwn.210100E08BA54E60
   Operational Status : Offline
   Provider Name : qlt(0)
   Alias : -
   Sessions : 0

How to Set Selected FC Ports to Initiator or Target Mode

This procedure uses path-based bindings. It shows you how to use a specific device path to bind a port to a driver that is different from the driver to which it is currently bound.

1. Become an administrator.
2. Display a list of the HBA ports and their respective device paths.

   This example shows the device paths for a single HBA with two ports.

   # luxadm -e port
   /devices/pci@780/QLGC,qlc@0,1/fp@0,0:devctl CONNECTED
   /devices/pci@780/QLGC,qlc@0/fp@0,0:devctl CONNECTED

3. Set the top port to target mode, and leave the bottom port in initiator mode.

   Remove the initial /devices portion of the path, and include everything up to /fp@0.... The path with the /devices portion removed is the path to which the system binds the qlt driver.

   Single quotation marks are required in this syntax.

   # update_drv -a -i '/pci@780/QLGC,qlc@0,1' qlt
   devfsadm: driver failed to attach: qlt
   Warning: Driver (qlt) successfully added to system but failed to attach.

   This message does not indicate an error. The qlc driver remains bound to the port until reboot. The qlt driver attaches during reboot.

4. Reboot the system to attach the new driver. Then, recheck the bindings.

   You should see that the port changed from initiator mode (qlc) to target mode (qlt).

   # init 6
   .
   .
   .
   # mdb -k
   .
   .
   .
   > $q

5. Verify that the target mode framework has access to the HBA ports.

   # stmfadm list-target -v

Making Logical Units Available for FC and FCoE

Simply registering a logical unit (LU) with the STMF framework does not make it available to hosts (initiators) on the network. You must make logical units visible to initiator hosts for Fibre Channel and FCoE configurations by mapping the logical unit. To determine which method to use and how to map the logical unit, see How to Make a Logical Unit Available to All Systems. Both methods use the stmfadm command. The additional steps below are for FC and FCoE configurations.

How to Make Logical Units Available for FC and FCoE

This procedure makes the LU available to all hosts or selected hosts for FC or FCoE configurations on a storage network. The steps are run on the host.

1. Become an administrator.
2. Make a LU available to hosts.

   Obtain the global unique identification (GUID) number for the LU.

   # sbdadm list-lu
   # stmfdm list-lu -v

   Identify the WWNs for the FC or FCoE ports of the host.

   # fcinfo hba-port
   HBA Port WWN: *210000e08b83378d*
   OS Device Name: /dev/cfg/c4
   Manufacturer: Qlogic Corp.
   Model: QLA2462
   Firmware Version: 4.0.27
   Fcode/BIOS Version: N/A
   Type: N-port
   State: online
   Supported Speeds: 1Gb 2Gb 4Gb
   Current Speed: 4Gb
   Node WWN: 210000e08b83378d
   HBA Port WWN: *210100e08ba3378d*
   OS Device Name: /dev/cfg/c5
   Manufacturer: Qlogic Corp.
   Model: QLA2462
   Firmware Version: 4.0.27
   Fcode/BIOS Version: N/A
   Type: N-port
   State: online
   Supported Speeds: 1Gb 2Gb 4Gb
   Current Speed: 4Gb
   Node WWN: 210100e08ba3378d

3. Add a view and perform mapping.

   Follow the instructions in How to Make a Logical Unit Available to All Systems.

4. Verify that the LU is visible on an Oracle Solaris initiator host by running the following script.

   #!/bin/ksh
   fcinfo hba-port |grep "^HBA" | awk '{print $4}' | while read 1n
   do
           fcinfo remote-port -p $1n -s >/dev/null 2>&1
   done

   All subsequent LUNs appear in the format output, because the script forces the initiator to touch all the LUNs through all the ports. If you do not see the LUNs, run the format command again. If you still do not see the LUNs, ensure that the service is enabled on the target by using the svcs stmf command. Also ensure that you added view entries for the LU, as described in How to Make a Logical Unit Available to All Systems.

5. Verify that the LU is visible on other systems.

   • For a Linux initiator host, verify that the LU is visible by running the utility provided by the HBA vendor. The utility scans for configuration changes.

   • For a Windows initiator host, verify that the logical unit is visible by selecting Control Panel → Administrative Tools → Computer Management → Disk Management. Then, from the Action menu, choose Rescan Disks.