To Configure Individual Devices With Sun StorageTek Traffic Manager Software

This sample procedure uses fabric-connected host ports c0 and c2 to configure fabric devices as multipath devices on a host that has the Sun StorageTek Traffic Manager software enabled.

The cfgadm -c configure command for fabric devices is the same regardless of whether multipathing is enabled.

1. Log in as root (su - root)..
2. Identify the port WWN of the device to be configured as the Sun StorageTek Traffic Manager software device.

   Look for devices on a fabric-connected host port marked as fc-fabric. These devices are the devices you can configure with the cfgadm -c configure command.

   # cfgadm -al
   Ap_Id                 Type      Receptacle  Occupant     Condition
   c0                   fc-fabric  connected   unconfigured unknown
   c0::50020f2300006077 disk       connected   unconfigured unknown
   c0::50020f23000063a9 disk       connected   unconfigured unknown
   c1                   fc-private connected   configured   unknown
   c1::220203708b69c32b disk       connected   configured   unknown
   c1::220203708ba7d832 disk       connected   configured   unknown
   c1::220203708b8d45f2 disk       connected   configured   unknown
   c1::220203708b9b20b2 disk       connected   configured   unknown
   c2                   fc-fabric  connected   unconfigured unknown
   c2::50020f2300005f24 disk       connected   unconfigured unknown
   c2::50020f2300006107 disk       connected   unconfigured unknown

   In the above example, the c0::50020f2300006077 and c2::50020f2300006107 Ap_Ids represent the same storage device with different port WWNs for the storage device controllers. The c0 and c2 host ports are enabled for use by the Sun StorageTek Traffic Manager software.

3. Configure the fabric device and make the devices available to the host.

   # cfgadm -c configure c0::50020f2300006077 c2::50020f2300006107

4. Verify that the selected devices are configured.

   # cfgadm -al
   Ap_Id                 Type      Receptacle  Occupant     Condition
   c0                  fc-fabric   connected   configured   unknown
   c0::50020f2300006077 disk       connected   configured   unknown
   c0::50020f23000063a9 disk       connected   unconfigured unknown
   c1                  fc-private  connected   configured   unknown
   c1::220203708b69c32b disk       connected   configured   unknown
   c1::220203708ba7d832 disk       connected   configured   unknown
   c1::220203708b8d45f2 disk       connected   configured   unknown
   c1::220203708b9b20b2 disk       connected   configured   unknown
   c2                   fc-fabric  connected   configured   unknown
   c2::50020f2300005f24 disk       connected   unconfigured unknown
   c2::50020f2300006107 disk       connected   configured   unknown

   Notice that the Occupant column of c0 and c0::50020f2300006077 specifies configured, which indicates that the c0 port has at least one configured occupant and that the c0::50020f2300006077 device is configured. The same change has been made in c2 and c2::50020f2300006107.

   When the configure operation has been completed without an error, multipathing-enabled devices are created on the host. If the physical device represented by c0::50020f2300006077 and c2::50020f2300006107 has multiple SCSI LUNs configured, each LUN is configured as a Sun StorageTek Traffic Manager software device. The example below shows that two LUNs are configured through c0::50020f2300006077 and c2::50020f2300006107. Each Ap_Id is associated with a path to those Sun StorageTek Traffic Manager software devices.

   # cfgadm -al -o show_SCSI_LUN c0::50020f2300006077\ c2::50020f2300006107
   Ap_Id                  Type    Receptacle   Occupant     Condition
   c0::50020f2300006077,0 disk    connected    configured   unknown
   c0::50020f2300006077,1 disk    connected    configured   unknown
   c2::50020f2300006107,0 disk    connected    configured   unknown
   c2::50020f2300006107,1 disk    connected    configured   unknown

   The example above shows that the following two multipathing-enabled devices are created for the device represented by c0::50020f2300006077 and c2::50020f2300006107: