Configuring the JNI or AMCC HBA (SPARC only)

After you have installed the JNI or AMCC host bus adapter (HBA) and the driver, you must configure the HBA.

1. Edit the jnic146x.conf file to set up the HBA connection to the switch fabric so that the file contains the following settings:

   automap=1; (dynamic binding)
   FcLoopEnabled=0;
   FcFabricEnabled=1; 
   TargetOfflineEnable=0; 
   LunDiscoveryMethod=1;  (this is typically the default)
   LunRecoveryInterval=10000;

   Note: If you are using the subsystem device driver (SDD) or are SAN booting the machine, you must use static port binding. Otherwise, use dynamic binding.
2. Modify the sd.config file (in the /kernel/drv/ directory) to inform the Solaris operating system about the new SCSI target device and LUNs. For example, if you had four LUNs, you would add lines similar to the following example lines:

   name="sd" class="scsi" target=0 lun=0;
   name="sd" class="scsi" target=0 lun=1;
   name="sd" class="scsi" target=0 lun=2;
   name="sd" class="scsi" target=0 lun=3;

3. Register the HBA ports and map virtual disks (VDisks) to the host using the following steps.
   Note: If a monitor is attached to the host, the user interface will display. If no monitor is attached, you must use an xhost capable client with an attached monitor.
   1. Log on to the attached console of the Sun or the remote host with xhost capability.
   2. Start the EZ Fibre configuration utility by entering the following:

      /opt/jni/ezfibre/standalone/ezf

      The user interface will display a list with both adapters listed, and all of the connected remote ports listed as targets.

   3. Use the SAN Volume Controller command-line interface or the SAN Volume Controller Console to register the HBA ports with the SAN Volume Controller.
   4. Create the necessary VDisks and map them to the host.
      Note: You can obtain the HBA worldwide port name (WWPN) from the /var/adm/messages file, the EZ Fibre utility, the SAN Volume Controller candidate HBA port list, or by using the Solaris prtconf tool.
   5. When the VDisks are created and mapped, restart the host with the reboot -- -r command.
4. After the host has been restarted, restart the EZ Fibre configuration utility. It should show all of the available VDisks under the listing of their corresponding HBA targets.
5. Decide if you want to use dynamic port binding or static (persistent) port binding. If you are using the subsystem device driver (SDD) or are SAN booting the machine, you must use static port binding. Otherwise, use dynamic binding.
6. If you decide to use static binding, use the following steps to map the SAN Volume Controller controlled VDisks to the host with persistent bindings:
   1. Using the EZ Fibre utility, select an HBA.
   2. Select the third tab on the HBA panel.
   3. Click Select All.
   4. Click Commit.
   5. Click Activate Changes.
   6. Select the same HBA.
   7. On the first panel, change the Dynamic Binding tab to Disabled.
   8. Click Commit.
   9. Click Activate Changes.
   10. Repeat steps 6.a through 6.i until you have performed it on all of the HBAs.
       Attention: The EZ Fibre configuration utility appends any changes to the end of the /kernel/drv/jnic146x.conf file. After multiple reconfigurations, this file can become very large. Make a copy of the jnic146x.conf file after installing the driver and restore it before making any configuration changes.
7. Restart the host and examine the /var/adm/messages file to ensure that the HBA is set up as a switch-fabric connection.