Information furnished by Emulex is believed to be accurate and reliable. However, no responsibility is assumed by
Emulex for its use; or for any infringements of patents or other rights of third parties which may result from its use.
No license is granted by implication or otherwise under any paten t, copyrigh t or rela ted ri ghts of Emulex .
Emulex, the Emulex logo, AutoPilot Installer, AutoPilot Manager, BlockGuard, Connectivity Continuum,
Convergenomics, Emulex Connect, Emulex Secure, EZPilot, FibreSpy, HBAnyware, InSpeed, LightPulse,
MultiPulse, OneCommand, OneConnect, One Network. One Company., SBOD, SLI, and VEngine are trademarks of
Emulex. All other brand or product names referenced herein are trademarks or registered trademarks of their
respective companies or organizations.
Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not
limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex may make
improvements and changes to the product described in this manual at any time and without any notice. Em ulex
assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties that may
result. Periodic changes are made to information contained herein; although these changes will be incorporated into
new editions of this manual, Emulex disclaims any undertaking to give notice of such changes.
Emulex, 3333 Susan Street
Costa Mesa, CA 92626
OpenSolaris DHCHAP Notice.
Contains portions of Covered Software subject to the Common Development and Distribution License (CDDL)
Version 1.0. Such portions of Covered Software in Source Code form may be obtained from the web site
www.opensolaris.org, or by contacting online support from the web site www.emulex.com.
Derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm.
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.
VPorts and OneCommand Manager Application Situations........................... 268
The OneCommand Manager User ManualPage x
Introduction
The Emulex® OneCommandTM Manager application is a comprehensive management utility for Emulex
®
LightPulse
(UCNAs) that provides a powerful, centralized adapter management suite. Adapter management
includes discovery, reporting and management of local and remote adapters from a single console
anywhere in the Storage Area Network (SAN) and across operating system platforms. Remote
configuration capability can be provided by either Fibre Channel (FC) access via host systems on the
same FC SAN or by Transmission Control Protocol/Internet Protocol (TCP/IP) access from IP addresses
of remote machines. The OneCommand Manager application contains a graphica l user interface (GUI)
and a command line interface (CLI). This manual describes the OneComm and Mana ger applicatio n for
the following operating systems:
•Windows
•Linux
•VMware ESX Server
•Solaris
This OneCommand Manager installation includes options to install the OneCommand Vision Sensor
Application. The OneCommand Vision Sensor is designed to work with the Emulex OneCommand
Vision system, it is designed to collect critical I/O performance data while consuming the smallest
possible production server memory and CPU footprint.
The OneCommand Vision system is an intelligent application that enables proactive management of I/O
within a data center environment. OneCommand Vision gives IT administrators the ability to maximize
I/O resource utilization, identify bottlenecks, and enhance performance and availa bility by monitoring
and analyzing the I/O traffic within the infrastructure. OneCommand Vision collects, analyzes and
organizes critical I/O performance data; helping organizations establish performance baselines,
proactively monitor performance against those baselines, and lower time to resolutio n when prob lems
occur. For more information please visit http://www.emulex.com/vision/.
host bus adapters (HBAs) and OneConnect
TM
universal converged network adapters
New Features in this Release
•Supports Emulex multi-ASIC OneConnect adapters
•Supports Emulex 16 Gb/s host bus adapters
•Management host mode with push discovery of remote hosts
•Windows OneInstall to install all drivers and the OneCommand Manager application in a single
installation kit
•Installs the OneCommand Vision Sensor if desired.
Compatibility
See the Emulex website for specific information regarding supported operating systems and platforms.
The OneCommand Manager User ManualPage 1
Supported Features by Operating System
Not all OneCommand Manager application features are supported across all oper ating system s. The
following table lists the OneCommand Manager application features and their operating system support.
Table 1: Supported Features by Operating System Cross-Reference
Feature/TaskWindowsSolaris Linux
OneCommand Manager
application GUI
OneCommand Manager
application CLI
OneCommand Manager
application Web Launch
Interface utility
Discover local hosts, adapters,
targets and LUNs
Discover remote hosts,
adapters, targets and LUNs
Enable local discovery of
Emulex and OEM branded
Emulex adapters
Enable FC discovery of
Emulex and OEM branded
Emulex adapters
Change an adapter’s WWPN
or WWNN
Reset adapters
Set up persistent binding
Simultaneously set adapter
driver parameters to multiple
adapters
Set global driver parameters to
adapters
FC/FCoE Boot from SAN
iSCSI configuration
Update firmware and FC boot
code on a single adapter or
multiple adapters using batch
update
Enable or disable the x86
BootBIOS, EFI or OpenBoot,
PXE Boot
Run diagnostic tests on
adapters
Manage local adapters
Manage FC remote and
TCP/IP accessed adapters
Locate adapters using
beaconing
Mask and unmask LUNS
Perform authentication using
FC-SP DHCHAP
XXX X*
XXXX
XXX
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
X
XXX
XXX X**
XXXX
XXX
XXX X*
XXX X*
XXXX
XXX X*
XXX X*
XXXX
XX
XX***
VMware ESX
Server
The OneCommand Manager User ManualPage 2
Table 1: Supported Features by Operating System Cross-Reference (Continued)
Feature/TaskWindowsSolaris Linux
Create and delete virtual ports
Run in read-only mode
Configure boot from SAN
Modify an IP port number
View vital product data
View transceiver information
Create SAN element reports
Manage adapters using CIM
Enable or disable FIP
COMSTAR support
Adapter hot swapping/hot
* Supported only by hbacmd for the VMware release of the OneCommand Manager application. Remote
management clients can perform these functions on ESX Server adapters using the OneCommand Manager
application GUI.
** Temporary (not persistent) driver parameters are su pported on VMware ESX 3i Update 4 and versions of
VMware ESX 3.5 prior to Update 4.
***DHCHAP is not supported on RHEL6 and SLES11-SP1.
****Supported on OpenSolaris only.
^ vNIC is supported only on IBM virtual fabric adapters.
^^ Not supported on IA64 Windows 7 and x86/x64 Solaris 10, 11 systems
Note: The features described in this manual depend on the driver version installed on the
adapter. Not all features may be available to you.
Known Issues
See the product release notes for the latest information.
The OneCommand Manager User ManualPage 3
Installing and Uninstalling OneCommand Manager
Application Components
Installing the OneCommand Manager Application
In Windows
There are two ways to install the OneCommand Manager application in Windows:
•Attended installation using the GUI.
•Unattended installation using the command line.
Note: If you are running the OneCommand Vision application, you must stop the
OneCommand Vision sensor before installing the OneCommand Manager
application.
2. You can also set the following optional parameters:
•MHost - This option al switch allows a non-mana gement-ho st user to se lect a Ma nagemen t
Host with which to register. If this switch is not specified, the default value of 0 will be used
and the feature will be disabled. If the switch is specified, the value can be a host name or
an IP address which will be validated by the installer. An error message appears if /mmode
is set as Local Only or Management Host.
•excl - This op tional switch allows the non-man agemen t-host user to select whe ther it will
process requests exclusively from the Management Host specified by the MHost switch.
This option is only accepted if accompanied by a valid MHost value; otherwise an error
message appears. If this switch is not specified, the default value of 0 will be used. If the
switch is specified, the valid values are as follows:
0. Remotely managed by other hosts.
1. Remotely man aged by M anageme nt Host ONLY
•Mtcp - This option al switch allows you to ena ble or disable remo te manag ement and to
specify the TCP/IP port number over which management will occur. If this switch is not
specified, the default TCP/IP port number 2333 will be used.
If the management host option is selected, you must either select the default port number or
enter a valid TCP/IP port number on the command line. A value of 0 will not be accepted.
If one of the non-management host options is selected, the TCP/IP port number may be
entered on the command line.
The OneCommand Manager User ManualPage 7
In Solaris
The following must be installed for the utilities to function properly:
•The Solaris FC/FCoE inbox driver version 2.60 or later or the out of box driver version elxfc
4.00.xx.xx must be installed for FC/FCoE management.
•The NIC inbox driver version OCe1.20 or later or the out of box driver version 4.00 must be
installed for UCNA management.
Note: If Emulex OneConnect UCNAs are installed on the system, the NIC driver must be
installed and reporting all NIC ports. Otherwise, the OneCommand Manager
application cannot manage UCNAs.
To install the OneCommand Manager application in Solaris:
1. Copy the Solaris utility kit to a temporary directory on your system.
2. Untar the utility kit:
tar xvf elxocm-solaris-<version>.tar
3. Change to the newly created elxocm-solaris-<versio n> directory:
cd ./elxocm-solaris-<version>/
4. Execute the install script to begin installation. If the HBAnyware utility, OneCommand Manager
Core or OneCommand Manager Enterprise applications or the Solaris driver utilities are already
present on the system, the install script attempts to remove them first:
./install
5. When prompted, choose whether or not to install the OneCommand Vision Sensor:
Would you like to install the OneCommand Vision Sensor kits along with
this installation?
Enter y to install the kit.
Enter n not to install the kit. (default)
Enter the letter 'y' or 'n' y
6. When prompted, enter the type of management you want to use:
Enter the type of management you want to use:
1 Local Mode : HBA's on this Platform can be managed by OneCommand
clients on this Platform Only.
2 Managed Mode: HBA's on this Platform can be managed by local or
remote OneCommand clients.
3 Remote Mode : Same as '2' plus OneCommand clients on this Platform
can manage local and remote HBA's.
4 Management Host : Same as '1' plus OneCommand clients on this Platform
can manage remote HBA's.
If you select option 2, you are asked if you want to enable TCP/IP management from remote
hosts.
If you select option 3, you are asked if you want to enable TCP/IP management of/from remote
hosts. You are prompted to enter the TCP/IP port number to use. (Leaving the field blank
defaults to 23333.)
If you select options 2 or 3, you are prompted for the managment host address. (Leaving the
field blanks means none.)
You can enter an IP address or host name. If you enter a management host address, you will be
prompted to exclude management of this host from any other host.
The OneCommand Manager User ManualPage 8
If you select option 4, management of remote hosts is automatically selected and you are
prompted to enter the TCP/IP port number to use. (Leaving the field blank defaults to 23333.)
Note: Management hosts cannot be managed by remote hosts
7. If you answered 2, 3 or 4 in step 5, you must de cide if yo u want the One Command Manager
application to operate in read-only mode. Read-only mode preven ts users from performing
certain operations such as resetting adapters, updating an adapter's firmware and changing
adapter driver properties and bindings. It only affects the local OneCommand Manager
application interface. These operations can still be performed using remote management. Enter
<y> for yes to allow the user to perform these operations, enter <n> for no if read-only mode is
desired.
8. You are prompted about allowing users to change the management mode after installation.
Enter <y> for yes, or <n> for no.
In Linux
The following must be installed before you can install the OneCommand Manager application:
•The appropriate driver for your operating system:
•Linux drive r version 8.2.0.33 .3p or later (Fo r RHEL5 an d SLES10 op erating systems.)
•Linux drive r version 8.3.5.X or later (For RHEL 6 SLES 11 SP1 operating systems.)
Note: The RHEL 6 Enterprise kit requires the intallation of the libstdc++-5.so library. This
library is available through the compat-libstdc++-33 -3.2.3-68.<arch>.rpm or later . The
PPC and x86_64 builds require the 64bit version installed which is installed in
/usr/lib64.The i386 build requires the 32bit version installed which is installed in
/usr/lib.
•Previous versions of the Linux driver must be uninstalled. You must run the uninstall script that
shipped with the version of the Linux driver you want to remove.
To install the OneCommand Manager application in Linux:
1. Log on as ‘root’.
2. Download the utilities from the Emulex website or cop y them from th e installation CD.
3. Copy the installation and uninstallation scripts to a known location, for easy access by other
users.
4. Copy the OneCommand elxocm-<Platform>-<AppsRev>.tgz file to a directory on the install
machine.
5. Change to the directory to which you copied the tar file.
6. Untar the file.
•For RHEL 5 and RHEL 6 type:
tar zxvf elxocm-rhel5-rhel6-<apps_ver>-<rel>.tgz
•For SLES 10 and SLES 11 type:
tar zxvf elxocm-sles10-sles11-<apps_ver>-<rel>.tgz
7. Change to the elxocm directory created in step 6.
•For RHEL 5 and RHEL 6 type:
cd elxocm-rhel5-rhel6-<apps_ver>-<rel>
•For SLES 10 and SLES 11 type:
cd elxocm-sles10-sles11-<apps_ver>-<rel>
The OneCommand Manager User ManualPage 9
8. Run the install script. Type:
./install.sh
9. When promted, choose whether or not to install the OneComm and Vision Sensor:
Would you like to install the OneCommand Vision Sensor kits along with
this installation?
Enter y to install the kit.
Enter n not to install the kit. (default)
Enter the letter 'y' or 'n' y
10. When prompted, enter the type of management you want to use:
Enter the type of management you want to use:
1 Local Mode : HBA's on this Platform can be managed by OneCommand
clients on this Platform Only.
2 Managed Mode: HBA's on this Platform can be managed by local or
remote OneCommand clients.
3 Remote Mode : Same as '2' plus OneCommand clients on this Platform
can manage local and remote HBA's.
4 Management Host : Same as '1' plus OneCommand clients on this Platform
can manage remote HBA's.
If you select option 2, you are asked if you want to enable TCP/IP management from remote
hosts.
If you select option 3, you are asked if you want to enable TCP/IP management of/from remote
hosts. You are prompted to enter the TCP/IP port number to use. (Leaving the field blank
defaults to 23333.)
If you select options 2 or 3, you are prompted for the management host address. (Leaving the
field blanks means none.)
You can enter an IP address or host name. If you enter a management host address, you will be
prompted to exclude management of this host from any other host.
If you select option 4, management of remote hosts is automatically selected and you are
prompted to enter the TCP/IP port number to use. (Leaving the field blank defaults to 23333.)
Note: Management hosts cannot be managed by remote hosts
11. If you answered 2, 3 or 4 in step 5, you must decide if you want the OneComm and Man ager
application to operate in read-only mode. Read-only mode preven ts users from performing
certain operations such as resetting adapters, updating an adapter's firmware and changing
adapter driver properties and bindings. It only affects the local OneCommand Manager
application interface. These operations can still be performed using remote management. Enter
<y> for yes to allow the user to perform these operations, enter <n> for no if read-only mode is
desired.
12. You are prompted about allowing users to change the manage ment mod e after installation.
Enter <y> for yes, or <n> for no.
In VMware ESX Server
For the best real-time management of Emulex adapters in VMware ESX and ESXi environments, the
OneCommand Manager for VMware vCenter software plug-in (OCM for VMware) is h ighly
recommended. For more information and to down load go to
http://www.emulex.com/products/software-solutions/device-management/onecommand-manager-forvmware/overview.html.
The following must be installed before you can install the OneCommand Manager application:
The OneCommand Manager User ManualPage 10
•Emulex Driver for VMware ESX, ver sion 8.2 o r la ter is require d only if FC/FCoE functionality is
desired. Refer to the Emulex Driver for VMware ESX User Manual for specific information on
driver support in ESX Releases.
•The NIC driver is required only if FCoE/iSCSI/NIC functionality is desired.
•The iSCSI driver is required only if iSCSI functionality is desired. (ESX 4.1 or later)
To install the OneCommand Manager application agent in VMware ESX Server:
1. Log into the ESX Server COS.
2. Copy the elxocmcore-esx<NN>-<version>.<arch>.rpm file to a directory on the install machine,
where NN is 40 for ESX 4.0, 41 for an ESX 4.1 or 50 for an ESXi 5.0 system.
3. CD to the directory to which you copied the rpm file.
4. Install the rpm. Type:
rpm -Uvh elxocmcore-esx<NN>-<version>.<arch>.rpm
Where NN is 40 for ESX 4.0, 41 for an ESX 4.1 or 50 for an ESXi 5.0 system. The rpm contents
are installed in /usr/sbin/ocmanager. The OneCommand Manager application Command Line
Interface is also located in this directory.
Installing the OneCommand Manager Application Web Launch Interface
Prerequisites
In addition to the driver and OneCommand Manager application, the following prerequisites must be met
before you install the Web Launch feature:
Note: The OneCommand Manager application Web Launch Interface is not supported on
VMware ESX Server.
In Windows:
•Microsoft Internet Information Services (IIS) Server must be installed. See the Microsoft
website for information on downloads and installation.
•The Win dows Firewall fea ture m ay be enab led by de fault. If it is, you must ad d and enable
three exceptions: HTTP port, java.exe and rmiregistry.exe.
Note: Allowing programs and/or ports through the firewall may increase the security risks.
Use at your own discretion.
To enable the HTTP port:
1. Click Add Port... The Add a Port dialog box is displayed.
2. On the Add a Port dialog box, type HTTP as the Name and 80 as the Port Number.
3. Leave TCP enabled and click OK.
To enable the java.exe program:
1. Click Add Program... The Add a Program dialog box is displayed.
2. Click Browse...
3. Specify java.exe located in the OneCommand Manager JRE installation path. For
example: C:\Program Files\Emulex\util\JRE\bin\java.exe.
4. Click OK.
The OneCommand Manager User ManualPage 11
To enable the rmiregistry.exe program:
1. Click Add Program...The Add a Program dialog box is displayed.
2. Click Browse... and specify the rmiregistry.exe located in the OneCommand Manager
JRE installation path. For example:
4. Under Web Server (IIS), Click Internet Information Services (IIS) Manager.
5. In the right pane, find your server name under "Start Page" and click on it.
6. Double-click MIME Types listed under IIS group.
7. A MIME Types page appears. Under "Actions", click Add... A popup dialog box appears.
8. Add "jnlp" (without quotes) to the File name extension field.
9. Add "application/x-java-jnlp-file" (without quotes) to the MIME type field.
10. Click OK.
In Solaris and Linux:
•Apache Web server must be installed and running on the server tha t is hostin g the Web
Launch Service software.
•The Java Web Start application must be installed and running on the browser host.
The server on which you are installing the Web Launch Service package requires:
•An HTTP server configured to handle the JNLP MIME file type. The following MIME file type/
file extension must be added to your server configuration:
•The HTT P server must be ru nning.
The client on which you are running the browser requires:
•Java m ust be installed. The specific requir ements are:
•Sun 32 -bit Java 6.0 or later fo r Intel base d systems (x86 an d IA64)
•32-bit Java 6.0 or later for x86-64 systems
•32- bit Java 6.0 o r later for RHEL 5 and SLES 10 (ppc64)
Refer to the appropriate vendor documentation for detailed instructions about configuring MIME
types, configuring and starting the HTTP server and installing the JRE. See
/opt/ELXocm/README_WEBLAUNCH.txt (Solaris) or
/usr/sbin/ocmanager/README_WEBLAUNCH.txt (Linux) for more setup information.
To install the OneCommand Manager application Web Launch Interface:
In Windows (Windows Server 2003, Windows Server 2008 and Windows Server 2008 R2):
1. Click Programs>Emulex >OCManager WebLaunch Install. Web Launch installation begins.
The OneCommand Manager User ManualPage 12
In Solaris and Linux:
1. Log on as ‘root’.
2. Navigate to the OneCommand Mana ger directory.
•Solaris:
cd /opt/ELXocm
• Linux:
cd /usr/sbin/ocmanager
3. Run the install script. Type:
./wsinstall
4. When prompted, enter the web server's docume nt root dir ectory. For example:
•Solaris:
/var/apache/htdocs
•Linux:
/srv/www/htdocs
or
/var/www/html
5. Confirm that the IP address of the host is the IP address that the web server uses. Answer <y>
or <n> as appropriate. If you answer <n>, you are prompted for the IP address you want to use.
6. When asked if your web server is listening on the normal default HTTP port (80), answer <y> or
<n> as appropriate. If you answer <n>, you are prompted for the port you want to use.
Once you have entered the necessary information, you are notified when the installation of the
OneCommand Manager application Web Launch package is complete. The Web Launch configuration files are created and Web Launch Service automatically starts.
7. To verify the installation, locate another client, open a web browser window a nd enter the
following URL:
http://IP_ADDR:PORT_NUM/ocmanager.jnlp
where IP_ADDR is the IP address of the host on which you installed the OneCommand Manager
application Web Launch service, and PORT_NUM is the TCP port number of the listening host’s
web server. The standard OneCommand Manager application user interface appears.
Note: It is not necessary to enter a port number if the standard HTTP port was chosen
during configuration.
Installing the OneCommand Manager Application Command Line Interface
The OneCommand Manager application Command Line Interface (CLI) is a compreh ensive
management utility for Emulex host bus adapters (HBAs) and converged network adapters (C NAs) that
provides support for commonly used commands without requiring installation of the OneCommand
Manager application GUI. The OneCommand Manager ap plication CLI can be installed separately
without installing the OneCommand Manager application GUI. The OneCommand Manager CLI console
application, named hbacmd, can be installed on Windows, Solaris, Linux and versions of VMware ESX
Server that include a Console Operating System (COS). A single operation is performed by entering
’hbacmd’ followed by the command at the command line. For syntax information and details on using the
OneCommand Manager application CLI, see “Using the OneCo mm and Ma nager Application Command
Line Interface” on page 187.
Note: If you installed the OneCommand Manager application, the CLI is already installed.
The OneCommand Manager User ManualPage 13
In Windows
There are two ways to install the OneCommand Manager application CLI in Windows:
•Attended installation using the GUI.
•Unattended installation using the command line.
Attended Installation in Windows
To install the OneCommand Manager application CLI:
1. From the Emulex website, download the x64 or x86 OneCommand Manager Core Kit installation
file.
Note: For IA64 systems, use the x86 OneCommand Manager Core Kit installation file.
2. Navigate to the system directory where you download the file.
3. Double click the elxocmcore<version>.exe. The Emulex OCManager CLI wind ow appears.
Figure 4: OCManager CLI window
The OneCommand Manager User ManualPage 14
4. Click Next. The Installation options window appears.
5. Click Install. The Operation in Progress window appears. The Installation completed window
appears when the installation is finished.
6. Click Finish. You do not need to reboot the system.
Unattended Installation in Windows
To install the OneCommand Manager CLI application in Windows:
1. From the Emulex website, download the x64 or x86 OneCommand Manager Core Kit installation
file to your system.
2. At the command prompt, set the optional switch to /q or /q2. The kit is activated with this optional
switch. The /q switch displays some progress reports. The /q2 switch does not displa y prog ress
reports.
For example:
elxocmcore-windows-x64-5.01.00.10-4.exe /q2
In VMware ESX Server
To install the OneCommand Manager application CLI on a new system, install the specific rpm file for the
driver for your VMware version.
Prerequisites
•To manage FCoE adapters, load LPFC driver version 8.2, or later.
•To manage NIC or iSCSI adapters, load driver version 2.102.440.0, or later.
•To manage iSCSI adapters, load the iSCSI driver.
Note: The iSCSI driver is not supported for VMware ESX 4.0.
Procedures
To install the OneCommand Manager application CLI:
The OneCommand Manager User ManualPage 15
1. Log into the ESX Server Host COS.
2. Copy the elxocmcore-esxNN-<kit version>.<arch>.rpm file to a directory on the install machine.
3. Change to the directory to which you copied the rpm file .
Where NN is 40 for an ESX 4.0 system or 41 for an ESX 4.1 system. The rpm contents are
installed in /usr/sbin/ocmanager. The OneCommand Manager application CLI is also located in
this directory.
In a VMware ESX Server with an Existing HBAnyware CLI Kit Installed
To install the OneCommand Manager application CLI on a VMware system with an existing HBAnyware
CLI installed:
1. Install the rpm file by entering the following command all on one line at th e com and prom pt:
Where NN is 40 for ESX 4.0, 41 for an ESX 4.1 or 50 for an ESXi 5.0 system.
Uninstalling Older HBAnyware Kits on VMware
To uninstall an older HBAnyware Kit on VMware:
1. Log into the ESX Server COS.
2. Type: rpm -qa | grep elx and locate either of the following rpm files:
elxvmwarecorekit-<kit version>
Or
elxocmcore-esxNN-<kit version>
Where NN is 40 for ESX 4.0, 41 for an ESX 4.1 or 50 for an ESXi 5.0 system.
3. Type:
rpm -e elxvmwarecorekit-<kit version>
Or
rpm -e elxocmcore-esxNN-<kit version>
Where NN is 40 for ESX 4.0, 41 for an ESX 4.1 or 50 for an ESXi 5.0 system.
In Linux
Prerequisites
For existing systems install the following drivers before installing the OneCommand Manager application
CLI:
On LP21000 series adapters and OneConnect FCoE adapters:
•Linux driver version 8.2.0.33.3p or later (For RHEL5 and SLES10 operating systems.)
•Linux driver version 8.3.5.X (For RHEL6 and SLES 11 SP1 operating systems.)
Note: The RHEL 6 Enterprise kit requires the intallation of the libstdc++-5.so library. This
library is available through the compat-libstdc++-33 -3.2.3-68.<arch>.rpm or later . The
PPC and x86_64 builds require the 64bit version which is installed in
/usr/lib64.The i386 build requires the 32bit version which is installed in
/usr/lib.
The OneCommand Manager User ManualPage 16
On OneConnect iSCSI adapters:
•iSCSI driver
On OneConnect NIC adapters:
•NIC driver
Note: The NIC driver must also be installed if the adapter personality is iSCSI-NIC or
FCoE-NIC.
•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.
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.
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 dir ectory created in ste p 3.
cd elxocmcore-<supported_os>-<app_ver>-<rel>
5. Run the install.sh script.
./install.sh
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
In a Linux System with an Existing HBAnyware CLI Kit Installed
Note: The OneCommand Manager application core kit cannot be installed if a previous
version of HBAnyware is 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.
The OneCommand Manager User ManualPage 17
The install script executes an rpm upgrade (rpm -U *.rpm) to upgrade the installed version of the
core kit to the current version.
Note: There is no upgrade path from an HBAnyware 4.x or 3.x core kit to a OneCommand
Manager application 5.2.0.x core kit. You must uninstall previous versions of the
HBAnyware utility before installing a OneCommand Manager app lication core kit. For
information on uninstalling older versions of HBAnyware, see “Uninstalling Older
HBAnyware Kits on Linux” on page 18.
To perform a clean install:
1. Uninstall the existing OneCommand Manager application CLI using the uninstall script included
in the tar file or in /usr/sbin/ocmanager/scripts directory.
Note: If an HBAnyware CLI or enterprise kit is installed, follow the procedure for
“Uninstalling Older HBAnyware Kits on Linux” on page 18.
Note: Your configuration files are backed up by rpm with an .rpmsave extension.
2. Install the specific rpm file for your driver for Linux version. Fo r inform ation o n installing the rpm
file, see “In Linux” on page 16.
Uninstalling Older HBAnyware Kits on Linux
Uninstalling an older HBAnyware core kit:
1. Run the following command to remove the core kit.
rpm -e elxlinuxcorekit
Uninstalling an older HBAnyware enterprise kit:
1. Run the uninstall script located in /usr/sbin/hbanyware/scripts to remove the enterprise kit.
Or
Run the uninstall script located in the tar file to remove the enterprise kit.
If the HBAnyware Security Configurator is installed, it must be uninstalled before uninstalling the
HBAnyware utility. You must run the uninstall script that shipped with the version of HBAnyware
Security Configurator that you want to remove. Proceed to step 2. If the Security Configurator is
not installed, proceed to step 3.
2. If the HBAnyware Security Configurator is installed, follow these ste ps:
a. Log on as ‘root’.
b. Change to the directory to which you copied the tar file.
c.Extract the tar file using the tar -xvf command.
d. Change to the newly created directory.
e. Run the uninstall script with the ssc parameter specified. Type:
./uninstall ssc
3. Uninstall the HBAnyware utility and the Application Helper Module:
a. Log on as ‘root’.
b. Change to the directory to which you copied the tar file.
c.Extract the tar file using the tar -xvf command.
d. Change to the newly created directory.
e. Uninstall any previously installed versions. Type:
./uninstall
The OneCommand Manager User ManualPage 18
In Solaris
Prerequisites
•The Solaris FC/FCoE driver version 2.60 or later must be installed for FC/FCoE management.
•The NIC driver version 1.20 or later must be installed for UCNA management.
Note: If Emulex OneConnect UCNAs are installed on the system, the NIC driver must be
installed and reporting all NIC ports. Otherwise, the OneCommand Manager
application cannot manage UCNAs.
Procedures
To install the OneCommand Manager application CLI:
1. Copy the OneCommand Manager application core kit to a tempo rary directory on the system.
2. Untar the core kit. Type:
tar xvf elxocmcore-<kit version>.tar
3. Change to the newly created elxocmcore-<kit version> directory:
cd ./elxocmcore-<kit version>/
4. Run the install script and follow the instructions.
./install
If the HBAnyware utility, the OneCommand Manager application cor e kit, the One Command
Manager application enterprise kit, or the Solaris driver utilities are already present on the system, the install script attempts to first remove them.
Upgrading from the OneCommand Manager Application CLI to the FullFeatured OneCommand Manager Application Enterprise Kit
Note: An upgrade can be performed only if the version of the OneCommand Manager
application enterprise kit is the same or later than the OneCommand Manager
application CLI version. You cannot downgrade a OneCommand Manager application
CLI with a previous version of the OneCommand Manager application enterprise kit.
Note: When the OneCommand Vision Sensor software is installed on production servers
with Emulex adapters installed, the Sensor software may load and use some of the
software components included in the OneCommand Manager application or
HBAnyware utility software stacks. It is essential that the OneCommand Vision
Sensor software be stopped before performing any upgrades, or updates, to the
OneCommand Manager application or HBAnyware software stack components. For
information on stopping the Sensor, refer the OneCommand Vision user manual.
In Windows
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application kit:
1. From the desktop, run the elxocm-windows-<kit version>.ex e file that con tains the full
application kit.
Running this executable file removes the OneCommand Manager application CLI and installs a
full-featured version of the OneCommand Manager application that includes the CLI and the
GUI.
The OneCommand Manager User ManualPage 19
In Linux
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application kit:
1. Run the install.sh script of the OneCommand Manager application enterprise kit.
The install script executes an rpm upgrade (rpm -U *.rpm) to upgrade the installed core kit to an
enterprise kit.
In Solaris
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application kit:
1. Download the OneCommand Manager application enterprise kit to a temporary directory on your
system.
2. Untar the OneCommand Manager application enterprise kit tar file:
tar xvf elxocm-<kit version>.tar
3. Change to the newly created elxocm-<kit version> directory:
cd ./elxocm-<kit version>/
4. Run the install script and follow the instructions.
./install
In VMware ESX Server
The full-featured OneCommand Manager application kit is not supported for VMware ESX Server.
Uninstalling the OneCommand Manager Application
Note: Do not uninstall the OneCommand Manager application if you are running, or intend
to run, OneCommand Vision.
Note: Uninstalling the OneCommand Manager application also uninstalls the
OneCommand Vision application.
To uninstall the OneCommand Manager application and OneCommand Manager application Web
Launch Interface:
In Windows
1. (Windows 2003) Select Start>Control Panel>Add/Remove Programs.
or
(Windows 2008 & Windows 2008 R2) Select Start>Control Panel>Programs>Uninstall a Pro-
gram.
2. If present, select Emulex Common SAN Manage ment [vers ion] and click Remove or Uninstall. Click Yes. The Emulex Common SAN Management components are removed from
the system.
3. Select Emulex OCManager Enterprise [version] or Emu lex OC Manager CL I [version] an d
click Remove or Uninstall.
The OneCommand Manager User ManualPage 20
Loading...
+ 248 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.