Emulex OneCommand Manager Command Line Interface User Manual (P006980-01A Version 5.2, August 2011)

OneCommand Manager Command Line Interface User Manual Page 6
The install script executes an rpm upgrade (rpm -U *.rpm) to upgrade the installed version of the
core kit to the current version.
Performing a Clean Install
Follow these steps:
1. Uninstall the existing OneCommand Manager CLI using the uninstall script included in the tar
file or in /usr/sbin/ocmanager/scripts directory.
2. Install the specific rpm file for your driver for Linux version. For information on installing the rpm
file, see installing the OneCommand Manager CLI “In Linux” on page 4.
In Solaris
Prerequisites
• The Solaris 2.60 driver must be installed.
• The Solaris OCE 1.20 NIC driver must be installed (required only for OneConnect CNA
management).
Procedures
To install the OneCommand Manager CLI:
1. Copy the OneCommand Manager core kit to a temporary directory on the system.
2. Untar the core kit. Type:
tar xvf elxocmcore-solaris-<kit version>.tar
3. Change to the newly created elxocmcore-solaris-<kit version> directory:
cd ./elxocmcore-solaris-<kit version>/
4. Run the install script and follow the instructions.
./install
If any of the following are already present on the system, the install script attempts to remove
them first:
• HBAnyware utility
• OneCommand Manager core kit
• OneCommand Manager application enterprise kit
• Solaris driver utilities
Note: There is no upgrade path from an HBAnyware 4.x or 3.x core kit to a
OneCommand Manager 5.1 or later core kit. You must un-install previous versions of
the HBAnyware utility before installing a OneCommand Manager core kit. For
information on uninstalling older versions of HBAnyware, see “Uninstalling Older
HBAnyware Kits in Linux” on page 8.
Note: If an HBAnyware CLI or enterprise kit is installed, follow the procedure for
“Uninstalling Older HBAnyware Kits in Linux” on page 8.
Note: Your configuration files are backed up by rpm with an .rpmsave extension.