Setting up a SAN Tape device on Solaris

Use the following procedure to configure a Solaris system to utilise fabric tape.
  1. Install Sun StorEdge SAN Foundation Software packages (6.1.2 or later),
  2. Install the latest st driver patch,

    Refer to for the latest SFK packages and driver patches.

    Refer to patch README files for dependency and install order information.
  3. Verify the presence of the following line in the
    /kernel/drv/st.confname="st" parent="fp" target=0;
  4. Install SANbox-II switch GUI software and firmware

    Refer to the SAN Components page for switch software, firmware and appropriate patches.
  5. Configure the drives for Fabric topology

    Using the front panel menu button on the STK tape drives, enter the Port Configuration menu and set the Hard PA option to N for the port or ports that will be used.
  6. Configure the Switch Ports and Zoning

    Referring to the documentation provided on the SAN Components page, configure each of the switch ports that the tape drives, library, and host adapters are connected to as needed. See the FC-Tape Topology Support and What Works With What matrices for guidelines on supported port types. In the event of any conflicts, the What Works With What matrix shall take precedence.

    Using the switch GUI, add a Zone Set to include zones to be defined. Note that the Orphan Zone Set cannot be used.

    Select the desired Zone Set and add new Zone or Zones as needed. Configure tape devices, library, and host adapter port(s) in these zones. It is recommended that World Wide Name (WWN) zoning be used.

    Once zones are defined, activate the zone set as described in the switch User's manual.
  7. Configure host adapter device nodes

    If new host adapters have been installed in the machine, device nodes must be created before the operating system is able to communicate with devices attached to these hba ports. To create the necessary device nodes, boot the system with the '-r' option, or run the following command:
    # devfsadm
  8. Verify devices are functional

    Use the cfgadm command to list attached controller ID(s), and to determine which are Fibre Channel adapters. Fibre Channel Fabric adapter ports will appear as Type fc-fabric.

    For each controller ID, use the luxadm command to view devices that are communicating properly. For example, if controller c2 is a fc-fabric device type, run the following command:
    # luxadm -e dump_map /dev/cfg/c2
    Pos Port_ID Hard_Addr Port             WWN Node         WWN Type
     0  10c00   0         500104f0004b493c 500104f0004b493b 0x1 (Tape device)
     1  10d00   0         500104f0004b48c4 500104f0004b48c3 0x1 (Tape device) 
     2  10eef   0         500104f00045decb 500104f00045d96a 0x8 (Medium changer device)
     3  10000   0         210000e08b056763 200000e08b056763 0x1f (Unknown Type,Host Bus Adapter)
  9. Run cfgadm

    Once the appropriate controller ID(s) are identified, use the cfgadm command to configure the necessary device nodes and links. Command syntax is as follows:
    # cfgadm -c configure c2
    Devices can now be accessed using standard device links in the /dev/rmt directory.

    NOTE: Use the -o force_update option when configuring library devices or device nodes will not be preserved after a system reboot.
  10. Install ISV patch, as appropriate
    • Netbackup 4.5 patch 112407-01 is required for Fabric attached Tape devices.
    • Solstice 6.1 patch TBD is required for Fabric attached Tape devices.