User's Guide

The OneCommand Manager User Manual Page 17
On OneConnect iSCSI adapters:
• iSCSI driver
On OneConnect NIC adapters:
• NIC driver
• Use the latest or matching driver from the Emulex website.
For new systems, the specific driver rpm file for your Linux version must be installed.
Procedures
To install the OneCommand Manager application CLI:
1. Copy the applications kit tar file to a directory on the installation machine.
2. Change to the directory where you copied the tar file.
3. Untar the file.
tar zxvf elxocmcore-<supported_os>-<app_ver>-<rel>.tgz
4. Change (use cd command) to the core kit directory created in step 3.
cd elxocmcore-<supported_os>-<app_ver>-<rel>
5. Run the install.sh script.
./install.sh
In a Linux System with an Existing HBAnyware CLI Kit Installed
You have two options when installing the OneCommand Manager application CLI on a Linux system:
• Upgrade - preserve existing settings
• Clean install - overwrite existing settings
To upgrade:
1. You must install the current core kit as detailed in “In Linux” on page 16.
The rpm file handles the configuration file upgrade.
Note: The NIC driver must also be installed if the adapter personality is iSCSI-NIC or
FCoE-NIC.
Note: On RHEL 5.5, RHEL 5.6 and RHEL 6, the OneCommand Core rpm file requires the
“Libnl” library. This library is not installed by default, but can be obtained from the OS
distribution media.
• For i386 RHEL 5.5, RHEL 5.6 and RHEL 6, use the 32bit libnl library.
• For x86_64 RHEL 5.5, RHEL 5.6 and RHEL 6, use the 64bit libnl library.
• For ia64 RHEL 5.5, RHEL 5.6 and RHEL 6, use the 64bit libnl library.
• For PPC RHEL 5.5, RHEL 5.6 and RHEL 6, use the 32bit libnl library.
Note: The core kit consists of 2 rpm files for each supported architecture and each
supported version of Linux:
1. elxocmlibhbaapi-*.rpm
2. elxocmcore-*.rpm
Note: The OneCommand Manager application core kit cannot be installed if a previous
version of HBAnyware is installed.