Filter
Top Products
Solaris SFS Driver User Manual Page 7
You do not need to reboot your system to run a utility program, but you must either enter the program’s
full path name, or add the package's bin directory (/opt/EMLXemlxu/bin) to your environment’s search
path. To use the man pages provided by the package, you must also add the package's man directory
(opt/EMLXemlxu/man) to your environment's man path.
For further information on installing and removing packages, consult the Solaris system administration
documentation and the pkgadd(1M) and pkgrm(1M) manual pages.
Installing the HBAnyware Utility, Web Launch and Security Configurator
Known Issues
• Starting with the HBAnyware utility version 3.2, Emulex provides support for LightPulse adapters
that are reprogrammed with WWPNs outside the typical Emulex range, such as Hewlett-
Packard’s upcoming Virtual Connect for Fibre Channel on the BladeSystem c-Class platform. In
such environments, the HBAnyware utility version 3.2, must be deployed across all servers on
the SAN, as well as any other management console used for out-of-band management, so that
all adapters appear in the Discovery Tree.
Installing the HBAnyware Utility
Prerequisites
• The FCA Utilities must be installed prior to installing the HBAnyware utility.
• Java Runtime Environment:
Version 5 of the Java Runtime Environment (JRE) must be installed. The HBAnyware utility will
not run under earlier versions of the JRE.
The JRE and instructions for installation can be found at
http://java.sun.com/downloads/index.html.
Procedure
To install the HBAnyware utility from the tar file:
1. Untar the EmlxApps tar file:
tar xvf EmlxApps-300b12-Solaris.tar
2. Run the unpack script to obtain the correct package version. Type:
./unpack_apps
3. Unzip the HBAnyware package file. Type:
gunzip HBAnyware-<version>-<platform>.tar.gz
4. Untar the HBAnyware package file. Type:
tar -xvf HBAnyware-<version>-<platform>.tar
5. Run the pkgadd utility. Type:
pkgadd -d .
Caution: The utilities require the java runtime binaries and libraries, so their path must be
included at the beginning of the PATH environment variable to avoid conflicts with
possible earlier versions of java that may still be installed on the system. For
example, if the java runtime binaries are in /usr/java/bin, then include this path in
the PATH environment variable.
For example: (bash> export PATH="/usr/java/bin:$PATH")