JNI Corporation EZ Fibre Configuration Utility for Solaris OS, version 2.6, 7, 8, and 9 Readme/Release Notes Release Version: 2.2.2 Release Date: July 18, 2003 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= TO PRINT THIS FILE: For optimum formatting (line wrapping, alignment, etc.), print this file with a 10-point, fixed pitch font (such as Courier, Courier New, etc.) on a 76-character line. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= CONTENTS -------- Topic Section ----- ------- o OVERVIEW ...................................................... 1.0 o REQUIREMENTS .................................................. 2.0 o Hardware and Driver Requirements ............................ 2.1 o Software Requirements ....................................... 2.2 o DIRECTORY CONTENTS............................................. 3.0 o INSTALLATION .................................................. 4.0 o Installation Issues ......................................... 4.1 o Installation Procedure ...................................... 4.2 o Silent Installation Procedure ............................... 4.3 o Logging Installation Events ................................. 4.4 o Configuration ............................................... 4.5 o Uninstallation Procedure .................................... 4.6 o Silent Uninstallation Procedure ............................. 4.7 o Logging Uninstallation Events ............................... 4.8 o STARTING EZ FIBRE ............................................. 5.0 o Binding to a Different Port ................................. 5.1 o PATCHES ....................................................... 6.0 o Runtime Library Patches for the EZ Fibre Agent .............. 6.1 o OS Patches for the JRE ...................................... 6.2 o Per Adapter (Device) Configuration Patches .................. 6.3 o FILES MODIFIED ................................................ 7.0 o jnic146x.conf ............................................... 7.1 o jnic.conf ................................................... 7.2 o fcaw.conf ................................................... 7.3 o fca-pci.conf ................................................ 7.4 o sd.conf ..................................................... 7.5 o st.conf ..................................................... 7.6 o ezfagent.prp ................................................ 7.7 o [back up] ................................................... 7.8 o CHANGES SINCE PREVIOUS RELEASE ................................ 8.0 o NEED TO KNOW & KNOWN ISSUES ................................... 9.0 o CONTACTING JNI ............................................... 10.0 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 1.0 OVERVIEW This README file contains last-minute product information about the EZ Fibre configuration utility (EZ Fibre). For installation and configuration instructions, see: o EZ Fibre Configuration Utility Quick Installation Guide =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2.0 REQUIREMENTS 2.1 Hardware and Driver Requirements Make sure that the correct driver version is installed for your host bus adapter (HBA). EZ Fibre supports the following HBAs and has been tested with the following drivers. Drivers later than those shown may work with this version of EZ Fibre, but have not been tested against this release. JNI Host Bus Adapter Driver -------------------- ----------- FC-1063 2.5.9 - 2.5.21 2.6.7 - 2.6.13 and later FCI-1063 2.5.9 - 2.5.21 2.6.7 - 2.6.13 and later FC64-1063 2.5.9 - 2.5.21 2.6.7 - 2.6.13 and later FCE-3210 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE-6410 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE2-6410 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE2-6412 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE-1063 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE2-1063 4.0 4.0.2a - 4.0.2b 4.0.4 - 4.0.6 4.0.4.1 4.1 4.1.1 - 4.1.5 and later 4.1.1.1 FCE-1473 5.0 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCE2-1473 5.0 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCE-6460 5.0 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCE2-6460 5.0 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCC-6460 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCC2-6560 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCE2-6560 5.0.1 - 5.0.3 5.1 5.1.0.1 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCC-6562 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCC2-6562 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCX-6562 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later FCX2-6562 5.1.0 - 5.1.0 E 5.1.1 - 5.1.3 5.2 - 5.2.1 and later 5.3 and later 2.2 Software Requirements The following are the minimum recommended software requirements for this version of EZ Fibre: o Solaris 2.6, 7, 8, or 9. o Video Display, 800 x 600 dpi with a 256-color palette (minimum) o TCP/IP installed and operational o Solaris OS Patches (see PATCHES section below) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 3.0 DIRECTORY CONTENTS The installation directory contains the following files: 1. EZFibre-Sun-Readme.txt This file. It documents this release of the EZ Fibre configuration utility. 2. EZ_Fibre_Install_Guide.pdf The EZ Fibre installation Guide. 3. EZF_222.tar The compressed EZ Fibre installation. The directory contents of the EZF_222.tar 1. EZFibre-Sun-Readme.txt This file. It documents this release of the EZ Fibre configuration utility. 2. install.sh The EZ Fibre installation script. Run this script as "root" to install EZ Fibre. 3. .install.bin The EZ Fibre installation binary. Run install.sh to expand this binary and install EZ Fibre. ________________________________________________________________ Note: Do not use this binary directly. ________________________________________________________________ 4. checkpatches.sh Used to identify any required patches that are missing from your system. This script is automatically run during the installation process. After installation, the EZ Fibre directory contains the following files: 1. EZFibre-Sun-Readme.txt This file. It documents this release of the EZ Fibre configuration utility. 2. ezf The EZ Fibre script. Use this script to start EZ Fibre. This script starts the EZ Fibre client and also the EZ Fibre agent, if it is not already started. 3. ezfagent.sh The EZ Fibre agent script. Use this script to start and stop the agent or to check the status of the agent. Running this script is normally not necessary. Running the EZ Fibre script "ezf" will start the EZ Fibre agent. 4. ezfagent.prp The EZ Fibre agent property file. (See Section 4.3, "Configuration," for details.) 5. EZFibre.jar, OB.jar, jhall.jar The EZ Fibre jar files required by the client. 6. checkpatches.sh Use this script to identify any required patches that are missing from your system. This script is automatically run during the installation process. 7. devices.dat Contains the labels of all devices that have been labeled via the EZ Fibre client. 8. jre The Java Runtime Environment 1.3 directory that the EZ Fibre client uses. 9. port.dat Contains the EZ Fibre client port assignment information (the logical port on which the EZ Fibre client communicates with the EZ Fibre agent). _______________________________________________________________________ Note: See the EZ Fibre help topic, "Port Information," for further information, including how to change this setting for the EZ Fibre client. To change the setting for the EZ Fibre agent, see Section 4.3, "Configuration," and the discussion of the "EZ Fibre Agent" properties. _______________________________________________________________________ 10. target.dat This file contains the labels of all targets that have been labeled via the EZ Fibre client. 11. sparc The location of the 32-bit EZ Fibre agent. 12. sparcv9 The location of the 64-bit EZ Fibre agent. 13. UninstallerData The un-install directory for EZ Fibre. 14. ezfclient.prp The EZ Fibre client property file controlling client behavior. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 4.0 INSTALLATION 4.1 Installation Issues BEFORE installing EZ Fibre, you must: o Verify that the TCP/IP stack has been installed. o Install the appropriate driver for your corresponding HBA(s). See Section 2.2 for the list of drivers supported with your HBA. o Install the Sun Solaris JRE patches. _______________________________________________________________________ Note: For the Java Runtime Environment (JRE) to work, some OS patches are required. See Section 6.0, "Patches," for the required patches, prior to installing EZ Fibre. _______________________________________________________________________ 4.2 Installation Procedure o Download the .tar file from the JNI Web site to a directory on your system, cd to that directory, then follow these steps: 1. Run "tar xvf EZF_222.tar". 2. Run "cd EZF_222". 3. Run "./install.sh". 4. Follow the on-screen instructions. 4.3 Silent Installation Procedure o The EZ Fibre installer supports the ability to do silent or unattended installations. Silent installations are handy if you would like to perform an EZ Fibre installation without any user interaction (i.e. from a script). o By default, the EZ Fibre installer will install EZ Fibre in the directory location "/opt/jni/ezfibre/standalone". If this default is acceptable, execute the following steps to silently install EZ Fibre: 1. Run "tar xvf EZF_22.tar". 2. Run "cd EZF_22". 3. Run "./install.sh -silent". o If you would like to override the JNI EZ Fibre installer default (i.e. install to a different directory location), execute the following steps: 1. Run "tar xvf EZF_22.tar". 2. Run "cd EZF_22". 3. Edit the file "silent_install_options" using an editor such as Vi. Modify the "installLocation" variable specifying the desired directory location. Verify the "license.selection" variable is set to a value of 1. A value of 1 indicates acceptance of the JNI License Agreement. 4. Run "./install.sh -silent silent_install_options". _______________________________________________________________________ Note: The user may also specify EZFibre installation variables on the command line instead of editing the file "silent_install_options". When performing a silent installation, the EZ Fibre installer will accept the terms of the JNI License agreement by default. Thus, including the "license.selection" variable on the command line is optional. After extracting the EZ Fibre installer from the tar file, execute the following command: ./install.sh -silent -P installLocation=/opt/jni/ezfibre/standalone Or: ./install.sh -silent -P installLocation=/opt/jni/ezfibre/standalone \ -W license.selection=1 _______________________________________________________________________ 4.4 Logging Installation Events o The EZ Fibre installer supports the ability to record the installation events in a log file. Logging can be useful for debugging problems that may occur during the EZ Fibre installation. o To initiate installation logging when installing EZ Fibre, execute the following command: ./install.sh -is:log o "" is the full directory pathname and filename of the log file where installation events should be recorded. You should have appropriate access permissions to the directory specified in . For example: ./install.sh -is:log /var/tmp/install_log.txt 4.5 Configuration The "ezfagent.prp" file contains the following properties: (Most of the following explanation is in the "ezfagent.prp" property file.) _______________________________________________________________________ Note: The path is the same as the one in which you installed EZ Fibre. The default path is: /opt/jni/ezfibre/standalone/ezfagent.prp _______________________________________________________________________ o Property: loglevel default value = LOG_USAGE Purpose: Allows you to set the logging level for the ezfagent. Options: LOG_OFF LOG_FATAL LOG_WARNING LOG_USAGE LOG_TRACE LOG_DEBUG1 LOG_DEBUG2 LOG_DEBUG3 Example: logLevel=LOG_USAGE o Property: logFileName default value = ezfagent Purpose: When used with the appropriate values of the "loglevel" and "logFileDir" properties, allows you to set the log file name. If commented out, logging is sent to standard error (stderr). Options: (a) supply a file name or (b) logging is sent to standard error (stderr). Example: logFileName=ezfagent o Property: logFileDir default value = Log Purpose: When used with the appropriate values of the "loglevel" and "logFileName" properties, allows you to set the log file directory. If commented out, the current directory is used. Options: (a) supply a directory name or (b) the current directory is used. Example: logFileName=Log o Property: daemon default value = 0 Purpose: Allows you to run the ezfagent as a daemon. Options: 1 = run ezfagent as a daemon 0 = do not run ezfagent as a daemon Example: daemon=1 o Property: port default value = 10001 Purpose: Allows you to set the port that the ezfagent will bind to. (Note: The EZ Fibre client must be set to the same port.) Range: 5000 to 65535 Example: port=10001 o Property: backupDir default value = Backup Purpose: Allows you to set up the EZ Fibre backup directory. This directory is used to back up any configuration file that is updated by EZ Fibre in the "/kernel/drv" directory. Options: (a) supply a directory name or (b) the current directory is used. Example: backupDir=Backup o Property: backupCount default value = 5 Purpose: Allows you to set up the EZ Fibre backup count. This counter determines how many prior versions of a configuration file will be saved. Range: 1 or greater Example: backupCount=5 o Property: rebootSystem default value = 1 Purpose: Enables the ezfagent API call "rebootSystem". Options: 0 = disables the API call 1 = enables the API call Example: rebootSystem=1 o Property: getHbaList default value = 1 Purpose: Enables the ezfagent API call "getHbaList". Options: 0 = disables the API call 1 = enables the API call Example: getHbaList=1 o Property: getTargetList default value = 1 Purpose: Enables the ezfagent API call "getTargetList". This is useful if you only want to see the adapters and not the adapters with their targets and their LUNs. Options: 0 = disables the API call 1 = enables the API call Example: getTargetList=1 o Property: getLLZList default value = 1 Purpose: Enables the ezfagent API call "getLLZList". Options: 0 = disables the API call 1 = enables the API call Example: getLLZList=1 4.6 Uninstallation Procedure EZ Fibre offers a graphical uninstall process for Solaris and other Unix EZ Fibre installations. However, uninstallation will not proceed properly if the EZ Fibre client or agent is running, as files in use cannot be deleted. To verify that the EZ Fibre agent is not running, check for the ezfagent process using the command: # ps -ef | grep ezfagent | grep -v grep root 3720 1 0 Nov 04 ? 0:05 /opt/jni/ezfibre/ standalone/.ezfagent In this example, the listed process indicates that the agent is running. To verify that the EZ Fibre client is not running, check for the process using the command: # ps -ef | grep 'ezf$' | grep -v grep root 4703 4528 0 10:06:59 pts/6 0:00 /bin/sh ./ezf In this example, the listed process indicates that the client is running. Once you have determined that the EZ Fibre client and agent are not running, use the following steps to uninstall EZ Fibre: 1. Change from the application directory to the UninstallerData subdirectory. 2. Execute the Uninstaller_for_EZ_Fibre binary file. 3. You will see the EZ Fibre Uninstaller Wizard. Follow the on-screen instructions. 4. The process will complete automatically. The installation directory, uninstaller directory, and all files created since the installation will remain in your system. The installation directory and its remaining contents may be deleted if desired. _______________________________________________________________________ Note: The user may circumvent the entire uninstall process by simply deleting the installation directory. There are no dependencies outside of the installation directory and its subdirectories. _______________________________________________________________________ 4.7 Silent Uninstallation Procedure o The EZ Fibre uninstaller supports the ability to perform silent or unattended uninstallations. Silent uninstallations are handy if you would like to perform an EZ Fibre uninstallation without any user interaction (i.e. from a script). Execute the following steps to silently uninstall EZ Fibre: 1. Change from the application directory to the UninstallerData subdirectory. 2. Run "./Uninstaller_for_EZ_Fibre -silent". 4.8 Logging Uninstallation Events o The EZ Fibre uninstaller supports the ability to record the uninstallation events in a log file. Logging can be useful for debugging problems that may occur during the EZ Fibre uninstallation. o To initiate uninstallation logging when uninstalling EZ Fibre, execute the following command: ./Uninstaller_for_EZ_Fibre -is:log o "" is the full directory pathname and filename of the log file where uninstallation events should be recorded. You should have appropriate access permissions to the directory specified in . For example: ./Uninstaller_for_EZ_Fibre -is:log /var/tmp/uninstall_log.txt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 5.0 STARTING EZ FIBRE EZ Fibre uses a client/server architecture. EZ Fibre is comprised of the EZ Fibre client and the EZ Fibre agent. o THE EZ FIBRE CLIENT The EZ Fibre client (EZFibre.jar) was written in Java requiring the use of a JRE. EZ Fibre uses the JRE 1.3. For the JRE to work, some OS patches are required. (See Section 6.0) o THE EZ FIBRE AGENT The EZ Fibre agent was written in C/C++. A 32-bit version is found under the "/sparc" directory and a 64-bit version is found under the "/sparcv9" directory. For the EZ Fibre agent to work, some patches are required. (See Section 6.0) o STARTING BOTH THE CLIENT AND THE AGENT For simplicity, the script "ezf" has been created to start both the EZ Fibre client and the EZ Fibre agent. To run EZ Fibre, cd to the EZ Fibre directory and run the following. # ./ezf 5.1 Binding to a Different Port o EZ Fibre Agent By default, the EZ Fibre agent attempts to bind to port 10001. If the agent cannot bind to port 10001, an error message appears. You can change this port value by editing the "ezfagent.prp" file and changing the PORT value (refer to Section 4.3). # Port on which EZ Fibre agent should bind to. PORT=10001 o EZ Fibre Client By default, the EZ Fibre client searches for the agent on port 10001. If the agent is not on port 10001, the port that the EZ Fibre client searches for the agent on must be changed. This is accomplished by going to the "File" menu and choosing the "Port" menu item. Set the port value to the correct port value. Click OK and the EZ Fibre client should automatically search for the agent on that port. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 6.0 PATCHES This section contains a list of all Solaris patches that are known to be needed by EZ Fibre. Most of these patches may be obtained from the SunSolve's Online public patch download page, located at: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access Some of these patches may not be publicly available and may also require the user to have a support agreement with Sun Microsystems. The information in this section is accurate at the time of this release, but JNI recommends that you check the SunSolve site for updated information, including new patch revisions. Before installing any patch, it is a very good idea to read the revision information included with the patch and check for any possible incompatibilities with the local environment. _______________________________________________________________________ Note: The "checkpatches.sh" script will identify any patches noted in this section that are missing. _______________________________________________________________________ 6.1 Runtime Library Patches for the EZ Fibre Agent Solaris Version Patch ID Note Description ------------- --------- --------- ---- ----------------------- 2.6 (5.6) 105591-18 required 7 (5.7) 106327-17 required 32-bit 7 (5.7) 106300-18 required 64-bit, requires 32-bit version 8 (5.8) 108434-10 required 32-bit 8 (5.8) 108435-10 required 64-bit, requires 32-bit version 6.2 OS Patches for the JRE The installation of EZ Fibre uses JRE 1.3. For proper functioning of EZ Fibre, the patches listed in the table below are required and/or recommended. To see which patches you currently have installed, run "showrev -p". To download the patches, start at http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access and enter the "Patch ID" that you would like to search for. Patch clusters also available which can greatly simplify installation. They are available at: http://sunsolve.sun.com/private-cgi/show.pl?target=patches/patch-access The following information is from the SUN Web site topic "Installing the Solaris SPARC JDK and JRE 1.3"): http://java.sun.com/j2se/1.3/install-solaris-patches.html For the latest patch list please visit the site. The number in parentheses in the "Solaris Version" column is the output from the command 'uname -r' on that version of Solaris. The two-digit number following the dash in each Patch ID is the revision of that patch. The table lists the minimum patch revisions required by this release of the JDK and JRE; later revisions are acceptable. Solaris Version Patch ID Note Description ------------- --------- ----------- ---- ------------------------ 2.6 (5.6) 107733-10 required Linker Patch 2.6 (5.6) 105568-25 required Libthread Patch 2.6 (5.6) 105210-51 required LibC Patch 2.6 (5.6) 106040-18 required X Input & Output Method Patch 2.6 (5.6) 105633-62 required (1,4,5) OpenWindows 3.6: Xsun Patch 2.6 (5.6) 108091-03 required (3) SunOS 5.6: fatal error in ISO8859-01 Locales 2.6 (5.6) 106842-09 required (4) Euro currency support 2.6 (5.6) 106841-01 required (4) Keytables Patch 2.6 (5.6) 105181-34 required Kernel Update (socket close/hang) 2.6 (5.6) 105669-11 recommended CDE 1.2: libDTSvc Patch (dtmail) 2.6 (5.6) 105284-50 recommended Motif 1.2.7: Runtime library patch 2.6 (5.6) 105591-18 required C++ shared library patch 2.6 (5.6) 106125-16 required Patch for patchadd and patchrm 7 (5.7) 107226-19 recommended For CDE window manager. 7 (5.7) 106980-22 required Libthread Patch 7 (5.7) 107636-10 required X Input & Output Method Patch 7 (5.7) 108374-07 required CDE 1.3 patch. 7 (5.7) 108376-42 required (1,5) OpenWindows 3.6.1 Xsun Patch 7 (5.7) 106541-24 required Kernel update 7 (5.7) 107544-03 required To be used with Kernel update patch 7 (5.7) 106950-22 required Linker Patch 7 (5.7) 106327-17 required Shared library patch for C++ 7 (5.7) 106300-18 required Patch for C++ 7 (5.7) 107081-52 required Motif 1.2 and Motif 2.1 patch 7 (5.7) 107656-11 required OpenWindows 3.6.1 libXt Patch 7 (5.7) 107702-12 required CDE 1.3: dtsession patch 8 (5.8) 108652-66 required X11 patch. 8 (5.8) 108921-16 required Spurious FOCUS_LOST and FOCUS_GAINED events. 8 (5.8) 108940-52 required Motif 2.1 patch -- available _______________________________________________________________________ Notes: (1) - required in Asian locales (2) - required to display Traditional Chinese characters in Swing applications (3) - required for any locale that uses the ISO8859-1 or ISO8859-15 character encoding (4) - required for support of Euro currency (5) - required for running Java Compatibility Kit tests JNI recommends that the Libthread patch (105568-17 for Solaris 2.6 or 106980-10 for Solaris 7) be applied last. _______________________________________________________________________ 6.3 Per Adapter (Device) Configuration Patches There is a bug on Solaris that does not allow "per-adapter configurations" to currently work with JNI FCI-1063 PCI adapters on the Ultra-5 and Ultra-10. "Per-adapter configuration" is what EZ Fibre uses to control each adapter's target/LUN mapping and parameter configurations. To fix this problem, the following patches are required. Solaris Version Patch ID Note Description ------------- --------- --------- ---- ------------------------ 2.6 (5.6) 109702-01 required 7 (5.7) 109439-01 required =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 7.0 FILES MODIFIED 7.1 jnic146x.conf This file is located in "/kernel/drv." It is modified each time any of the adapter's (handled by the jnic146x driver) parameters have been modified or when LUN-level zoning (LLZ) is done on this adapter. Each time a "Commit Changes" has been made, this file is re-written. 7.2 jnic.conf This file is located in "/kernel/drv." It is modified each time any of the adapter's (handled by the jnic driver) parameters have been modified or when LLZ is done on this adapter. Each time a "Commit Changes" has been made, this file is re-written. 7.3 fcaw.conf This file is located in "/kernel/drv." It is modified each time any of the adapter's (handled by the fcaw driver) parameters have been modified or when LLZ is done on this adapter. Each time a "Commit Changes" has been made, this file is re-written. 7.4 fca-pci.conf This file is located in "/kernel/drv." It is modified each time any of the adapter's (handled by the fca-pci driver) parameters have been modified or when LLZ is done on this adapter. Each time a "Commit Changes" has been made, this file is re-written. 7.5 sd.conf This file is located in "/kernel/drv." It is modified any time a new a disk or CD-ROM device is LUN-level zoned through EZ Fibre with a target/LUN pair not in this file. This modified file will allow the sd driver to probe for this device on the next reboot. 7.6 st.conf This file is located in "/kernel/drv." It is modified any time a new tape device is LUN-level zoned through EZ Fibre with a target/LUN pair not in this file. This modified file will allow the st driver to probe for this device on the next reboot. 7.7 ezfagent.prp Refer to Section 4.3, "Configuration," for a description of this property file. 7.8 [back up] Refer to discussion of the property, "backupDir" in Section 4.3, "Configuration", for information about backups of configuration files affected by EZ Fibre. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 8.0 CHANGES SINCE PREVIOUS RELEASE Changes since version 2.2.1 o Add support in EZ Fibre to display SCSI Enclosure Service (SES) device mapping information when the device is Lun-Level Zoned. o When "dynamic parameter activation" fails due to the driver instance being busy, the 'jnic146x_busy' command (installed with driver versions 5.3 and later) is called and the output presented in the pop-up error dialog. o updated EZ Fibre Help topics. o Modified the image of the devices to be more user friendly for color-blind users. A mapped devices (green device image) now has a check mark next to the device image. A device mapped more than once (red device image) now has two check marks next to the device image. A mapped disconnected devices (yellow device image) now has a question mark next to it. And device that EZ Fibre can no longer get to (Not Accessible) has a red X over the device. o Added Tool Tips to the devices in the Tree view and LUN-Level Zoning tab. o Added support in EZ Fibre to do multiple row selections in the LUN-Level-Zoning tab to quickly map in groups of LUNs. o Added "Commit All Changes" to the File menu. Use this File menu item to commit all changes on all adapters without having to individually apply the "Commit Changes" button for each adapter. o Added support in EZ Fibre to view disconnected LUN-Level-Zoned devices. This Allows the user remove the devices through the LUN-Level-Zoning tab or to acknowledge a change in the SAN. o Added support in EZ Fibre to set the Default LLZ Binding to either wwnn binding or wwpn binding for targer/adapter LUN (device) combinations that are not mapped in. o Fixed issue with EZ Fibre running out of memory with Show Disconnected Luns enabled on CX600. o Removed binding in .conf updated an some devies still present. o In the HBA Adapter information pane, what was called the Serial Number is now called the WWN id. The serial number is different, and is not available electronically from the HBA. o Agent performance improvements in SAN target/LUN discovery. o Report the full path of the driver instance device. o Added support for command line for silent (non-interactive) installs. o EZ Fibre now supports activating driver configuration changes without a reboot. When configuration changes are made to an HBA model with a driver version that supports this feature, the option to activate the changes instead of rebooting the system is provided. o Changes adding support for the new dynamic binding ('automap') setting of 'Loop'. When dynamic binding is set to 'Loop', only devices that are present on the fibre channel local loop are made dynamically bound. Affects use with Solaris driver versions 5.3 and greater. o Changes adding support of the use of LLZ static binding while the dynamic binding ('automap') driver parameter is enabled. Affects use with Solaris driver versions 5.3 and greater. o When dynamic binding ('automap') is enabled, the LUN icons are now color highlighted to indicate that they are available for I/O by the OS. Solaris driver versions 5.3 and greater. o Only automatically update the sd.conf and st.conf files when needed. Driver versions that support dynamic devices need no per-LUN sd.conf file entries. Affects use with Solaris driver versions 5.3 and greater. o SAN LUN Discovery enhancements by increased use of SCSI Report LUNs command response. Affects use with Solaris driver versions 4.1.3 or greater, and 5.1.1 or greater. o Corrected an issue where problems occurred parsing the st.conf file depending upon how the file was manually edited. o Suppressed driver 4.1.3 SBUS parameters which are no longer used. o Corrected an issue where, in certain cases upon driver parameter commit, the "dynamic parameter activation" option was erroneously offered as an alternative to a "reboot". o Corrected an issue with driver 4.1.3 where the LUN icons were not color highlighted and the LLZ tab was not disabled when the driver "Dynamic Binding" feature was enabled. Changes since version 2.2m o Added EZ Fibre support for Solaris JNIC146x driver version 5.1.2. Changes since version 2.2k o Updated driver support, see Section 2.0. Changes since version 2.2j o Updated driver support, see Section 2.0. Changes since version 2.2i o Updated driver support, see Section 2.0. Changes since version 2.2h o Updated driver support, see Section 2.0. o Added EZ Fibre support for Solaris JNIC146x driver version 5.1.0 E. o Added 3 new ezfagent.prp parameters (See ezfagent.prp). o ignoreProblematicTargets o scsi_cmd_timeout o list_timeout Changes since version 2.2g o Added EZ Fibre support for Solaris JNIC driver version 4.0.6. Changes since version 2.2f o Added EZ Fibre support for Solaris JNIC146x driver version 5.1.0.1. o Added EZ Fibre support for Solaris JNIC driver version 4.0.4.1. Changes since version 2.2e o Updated driver support. See Section 2.1, "Hardware and Driver Requirements." Changes since version 2.2d o Updated driver support. See Section 2.1, "Hardware and Driver Requirements." Changes since version 2.2c o Fixed problem with EZ Fibre not displaying FC-1063, FC64-1063, or FCI-1063, with 2.6.9 driver when ip_compliant parameter is enabled. o Fixed problem with EZ Fibre not reporting the OS device name for tape devices. o Fixed problem with EZ Fibre reporting offline ports for Solaris JNIC driver version 4.1. Changes since version 2.2b o Added EZ Fibre support for Solaris JNIC146x driver version 5.0.2. o Added EZ Fibre support for Solaris JNIC driver version 4.0.5. o Added EZ Fibre support for Solaris JNIC driver version 5.0.3 McDATA. Currently supporting 5.0.3.b.1m. o Added EZ Fibre support for Solaris JNIC146x driver version 4.1. Currently supporting 4.1.b.2. o Updated EZ Fibre support for Solaris JNIC146x driver version 5.1. Currently supporting 5.1.b.7a. o Added support for Dynamic Binding (automap) with the 4.1 JNIC driver. o Added support for Dynamic Binding (automap) with the 5.1 JNIC146x driver. o Fixed problem with EZ Fibre not showing all LUNs from an EMC configured with sparse LUNs. Changes since version 2.2a o Added EZ Fibre support for Solaris JNIC146x driver version 5.0.1. Changes since version 2.2 o Fixed SCR #410, Solaris EZF LUN "OS Mapping" field sometimes strangely missing. o Added EZ Fibre support for Solaris JNIC146x driver version 5.1. Currently supporting 5.1.b.3. o Added EZ Fibre support for Solaris JNIC driver version 4.0.4. o Fixed SCR #400, where assigning target IDs in LLZ tab did not update unmapped target IDs above, causing a target id collision. o Fixed SCR #401, where the LLZ tab Commit and Undo buttons were not being re-enabled properly after changes after a prior Commit without an intervening Refresh. o Fixed a problem with the ezfagent not checking the correct driver for version control. The ezfagent was always checking in "/kernel/drv" for driver in 32/64 kernel modes. Changed it to check in "/kernel/drv" for 32-bit kernel mode and "/kernel/drv/sparcv9" for 64-bit kernel mode. Changes since version 2.1.2 o Added EZ Fibre support for Solaris JNIC146x driver version 5.0 o EZ Fibre now supports the new Emerald IV-based adapters (FCE-6460, FCE2-6460, FCC-6460, FCE-1473, FCE2-1473). Make sure that the correct driver is installed as discussed in the adapter documentation. o When using an HBA model FCE-1473, FCE2-1473, FCE-6460, FCE2-6460, or FCC-6460 that is configured for TCP/IP, it is now no longer necessary to "unplumb" each of them in order to configure them using EZ Fibre. o Added EZ Fibre support for Solaris fca, fcaw and fca-pci driver version 2.5.18. o Added support for HBA model FC-1063 o EZ Fibre now allows the user to choose whether or not to show disconnected LUNs. A new "View" menu item was added. o Added support for driver instances greater than 25. o Added OS Mapping to LUN View for LUNs that are zoned in. o Added user selection of the Target ID value to the LUN-Level Zoning configuration screen. o Added the per-LUN LUN Throttle settings to the LUN-Level Zoning configuration screen. o When EZ Fibre is started, it displays a dialog box showing progress when it is performing its SAN device discovery. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 9.0 NEED TO KNOW & KNOWN ISSUES o Dynamic driver configuration change activation is only supported on driver versions 5.3 and later, and only on Solaris release 2.7 or later. o When attempting to dynamically activate driver configuration changes without a reboot, the driver instance being configured must be idle -- no mounted file systems, TCP/IP or raw I/O running through it. Otherwise, the change activation will fail. The jnic146x_busy command can be used to help idle the driver instance allowing the parameter activation to succeed. This command is installed with the driver and is located in the /opt/JNIC146x directory. This issue applies to HBA models with a driver versions that support the dynamic parameter update feature. o Configuration Issue with FCI-1063 HBA on Ultra-5 and Ultra-10 There is a bug in Solaris that does not allow "per-adapter configurations" to currently work with JNI FCI-1063 PCI adapters on the Ultra-5 and Ultra-10. "Per-adapter configuration" is what EZ Fibre uses to control each adapter's target/LUN mapping and parameter configurations. To fix this problem see Section 6.3. o Client Needs 256-color Palette The EZ Fibre client uses Java swing classes that require a minimum color palette of 256 colors. (A minimum resolution of 800 X 600 pixels is also required.) o EZ Fibre Cannot See HBAs While HBAs are Set Up for TCP/IP When using an HBA model FC64-1063 or FCI-1063 which is set up for TCP/IP, EZ Fibre cannot see the HBA on the system. This restriction does not apply to Emerald IV series adapters such as the FCE-6460 or FCE-1473. To view the hidden HBAs, "unplumb" the HBAs you want to see through EZ Fibre. This can be done with the ifconfig utility. For example, if you have FCI-1063 HBA instance 0 (fca-pci0), enter the following: # ifconfig fca-pci0 unplumb You should now be able to see the HBA through EZ Fibre. Once you are done using EZ Fibre and want to re-enable TCP/IP, enter the following: # ifconfig fca-pci0 fibrepluto1 plumb up Where "fibrepluto1" is a Fibre Channel hostname stored in "/etc/hostname.fca-pci0". Refer to the driver readme file for your driver version for more information. o Device "Flash LED" Button For some RAID devices, the "Flash LED" button on the Device Panel either does not work or works intermittently. This issue is being researched. o Manual Binding / LUN-Level Zoning Issue with CONF Files There are many ways to configure an instance of the driver to do LUN-level zoning. EZ Fibre uses the following method. If you choose to manually edit the configuration file, you MUST conform to this standard if EZ Fibre is to see your LLZ configuration. In the following, X is the driver instance number, Y is the target number, and Z is the LUN number. EZ Fibre uses the following standard in jnic.conf: jnicX_targetY_wwnn = "jnicX"; jnicX_targetY_lunZ_hba = "jnicX"; or jnicX_targetY_wwpn = "jnicX"; jnicX_targetY_lunZ_hba = "jnicX"; EZ Fibre uses the following standard in jnic146x.conf: jnic146xX_targetY_wwnn = "jnic146xX"; jnic146xX_targetY_lunZ_hba = "jnic146xX"; or jnic146xX_targetY_wwpn = "jnic146xX"; jnic146xX_targetY_lunZ_hba = "jnic146xX"; EZ Fibre uses the following standard (per-dev-info) in fcaw.conf: name="DRIVER NAME" parent="LOCATION" reg= REG-ARRAY targetY_wwnn = "fcawX" targetY_lunZ_hba = "fcawX"; or name="DRIVER NAME" parent="LOCATION" reg= REG-ARRAY targetY_wwpn = "fcawX" targetY_lunZ_hba = "fcawX"; EZ Fibre uses the following standard (per-dev-info) in fca-pci.conf: name="DRIVER NAME" parent="LOCATION" unit-address= "SLOT NUMBER" targetY_wwnn = "fca-pciX" targetY_lunZ_hba = "fca-pciX"; or name="DRIVER NAME" parent="LOCATION" unit-address= "SLOT NUMBER" targetY_wwpn = "fca-pciX" targetY_lunZ_hba = "fca-pciX"; o EZ Fibre Installation Directory The EZ Fibre installation and uninstallation process uses temporary disk space to decompress and expand the installation. In most cases, the default directory it uses is appropriate. However, should there be insufficient disk space, the directory used can be overridden using the TMPDIR environment variable. For example, if you wish to use '/var/tmp1', you would set the TMPDIR environment variable using: (csh) setenv TMPDIR "/var/tmp1" (sh, ksh, or bash) TMPDIR="/var/tmp1"; export TMPDIR At the start of the install, the following message would appear: Installer using temporary disk space in '/var/tmp1' (from $TMPDIR). When not overridden, the message would read: Installer using temporary disk space in '/tmp' ($TMPDIR not set). _______________________________________________________________________ Note: The user may also override the temporary default directory on the command line instead of manually setting the $TMPDIR environment variable. For example: ./install.sh -is:tempdir /var/tmp1 or ./Uninstaller_for_EZ_Fibre -is:tempdir /var/tmp1 If the specified overridden temporary directory does not exist, the installer or uninstaller will use the default temporary directory of $temp (/tmp). _______________________________________________________________________ o Rebooting Through EZ Fibre EZ Fibre uses the reboot command to reboot the system. The actual syntax used by EZ Fibre is "sync; reboot -- -r" on Solaris. If this is not the appropriate command for your environment, you may choose to reboot from the command line. o Topology Changes Require Two Reboots The Emerald III adapters require two reboots when going from Private Loop to Fabric or Public Loop. The same is true when going back to Private Loop from Fabric or Public Loop. When you first make this change, you will be prompted to reboot the system. This is not automatic and you may choose to decline it. However, your changes will not take effect until you have rebooted. After the first reboot, a second reboot is required. If you have not rebooted a second time, when you bring up EZ Fibre and look at the adapters, the EZ Fibre main window indicates "UNKNOWN" where the adapter name would appear. The second reboot resolves this issue and the adapter name appears, completing the topology change. o EZ Fibre not seeing your adapter Make sure the correct driver is installed. If it is, and EZ Fibre is not seeing your adapter, try the command "drvconfig" before launching EZ Fibre. o Running or Installing EZ Fibre from a remote system If you need to run or install EZ Fibre from a remote system, the following is an example of how it can be done. 1) From the remote system type: # /usr/openwin/bin/xhost + 2) Login (telnet, rlogin, ssh, etc...) to the system where you want to run or install EZ Fibre. 3) Choose a shell and set up the DISPLAY environment variable. The DISPLAY variable is usually set to the remote system IP address (in this example 192.168.0.1) followed by :0.0. # csh # setenv DISPLAY 192.168.0.1:0.0 _____________________________________________________________________ Note: Before doing Step 4 you can check that the remote X Server is going to allow connections by trying to bring up an xterm. If you can bring up an xterm remotely you should be able to run EZ Fibre remotely. _____________________________________________________________________ 4) Now you are able to run or install EZ Fibre remotely. # /opt/jni/ezfibre/standalone/ezf or # /tmp/EZF_22/install.sh # /usr/openwin/bin/xterm =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 10.0 CONTACTING JNI o Electronic Support Technical information--including product literature, answers to frequently asked questions, information on software upgrades, and other topics--is available electronically through the following: JNI World Wide Web (WWW) site at www.jni.com o Technical and Product Support JNI provides technical support 24 hours a day, 365 days a year that is available by telephone at (858) 523-7222 or toll free at (877) 436-5642, or by email at support@jni.com o Sales and Ordering Information For sales and ordering information about JNI products, call JNI at (800) 452-9267 or (858) 523-7000 and ask for Sales. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=