Emulex ProLiant BL620c G7 User manual

OneCommand

™

Manager

Application

Version 5.0

User Manual

One Network.

One Company.

P004343-01A Rev. A Connect with Emulex.

The OneCommand Utility User Manual Page ii

means or translated to any electronic medium without the prior written consent of Emulex.

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 patent, copyright or related rights 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. Emulex

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.

The OneCommand Utility User Manual Page iii

Introduction..............................................................................................................1

Supported Features by Operating System.........................................................2

Known Issues....................................................................................................3

Installing and Uninstalling OneCommand Manager

Application Components..........................................................................................4

Installing the OneCommand Manager Application.............................................4

In Windows .................................................................................................4

In Solaris SFS.............................................................................................4

In Linux .......................................................................................................5

In VMware ESX Server ...............................................................................6

Installing the OneCommand Manager Application Web Launch Interface ...6

Prerequisites...............................................................................................6

Procedures..................................................................................................7

Installing the OneCommand Manager Application Command Line Interface.....8

In Windows .................................................................................................9

In a New VMware ESX Server ....................................................................9

Prerequisites.......................................................................................10

Procedures .........................................................................................10

In a VMware ESX Server with an Existing HBAnyware CLI Kit Installed...10

Uninstalling Older HBAnyware Kits on VMware..................................10

In a New Linux System ............................................................................. 11

Prerequisites....................................................................................... 11

Procedures ......................................................................................... 11

In a Linux System with an Existing HBAnyware CLI Kit InstalledI .............12

Uninstalling Older HBAnyware Kits on Linux.......................................12

In Solaris SFS...........................................................................................13

Prerequisites.......................................................................................13

Procedures .........................................................................................13

Upgrading from the OneCommand Manager Application CLI to the Full-Featured

OneCommand Manager Application Enterprise Kit .........................................14

In Windows ...............................................................................................14

In Linux .....................................................................................................14

In Solaris SFS...........................................................................................14

In VMware ESX Server .............................................................................14

Uninstalling the OneCommand Manager Application ..................................14

In Windows ..............................................................................................15

In Solaris SFS...........................................................................................15

In Linux .....................................................................................................15

In VMware.................................................................................................15

Uninstalling the OneCommand Manager Application Web Launch

Interface Only..................................................................................................15

Starting the OneCommand Manager Application...................................................17

Starting the OneCommand Manager Application Web Launch Interface......... 17

Managing Files when Running the OneCommand Manager Application

Web Launch Interface...............................................................................17

Using the OneCommand Manager Application...................................................... 18

The OneCommand Manager Application Window Element Definitions ...........18

The Menu Bar ...........................................................................................19

The Toolbar...............................................................................................19

The Toolbar Buttons .................................................................................19

The Discovery-Tree ..................................................................................20

The OneCommand Utility User Manual Page iv

Discovery-Tree Icons .........................................................................21

Expanding or Collapsing the Discovery-Tree View ......................22

The Property Tabs ....................................................................................22

The Status Bar .........................................................................................22

Changing Management and Read-Only Mode ...........................................22

In Windows.........................................................................................23

In Solaris SFS.....................................................................................23

In Linux...............................................................................................23

Printing Help Information.................................................................................24

Configuring Discovery ...........................................................................................25

Automatic Fibre Channel Discovery ...............................................................25

Remote SAN Management Using TCP/IP Access Protocol ............................ 25

The Hosts File ................................................................................................26

Manually Editing the Hosts File.................................................................26

Copying the File .......................................................................................27

Adding a Single Host.......................................................................................28

Adding a Range of Hosts ................................................................................29

Removing Hosts..............................................................................................31

Configuring Discovery, CIM Credentials and TCP/IP Settings ........................31

Configuring iSCSI Target Discovery ................................................................33

Adding Target Portals................................................................................34

Specifying Portal Specific Login Options.............................................34

Removing a Target Portal..........................................................................35

Logging into Targets..................................................................................36

Adding an iSCSI Target.............................................................................36

Removing Targets.....................................................................................37

Viewing Target Sessions...........................................................................37

Logging out of Target Sessions................................................................. 37

Viewing Discovery Information ..............................................................................40

Viewing Host Information.................................................................................41

Viewing Adapter Information ...........................................................................43

Viewing Fibre Channel Adapter Information..............................................43

Viewing iSCSI Adapter Information........................................................... 44

Viewing NIC-Only Adapter Information......................................................45

Viewing Port Information ................................................................................. 45

Viewing Fibre Channel Port Information....................................................45

Viewing FCoE Port Information.................................................................47

Viewing iSCSI Port Information.................................................................49

Viewing NIC Port Information....................................................................51

Viewing Physical Port Information...................................................................52

Viewing Port Statistics ....................................................................................53

Viewing Fibre Channel Port Statistics........................................................53

Viewing iSCSI Statistics ............................................................................56

Viewing Virtual Port Information (FC and FCoE Adapters Only) ................58

Viewing Fabric Information..............................................................................58

Viewing Transceiver Information ...............................................................60

Viewing Fibre Channel Transceiver Information........................................ 60

Viewing OneConnect Adapter Transceiver Information.............................61

Viewing Vital Product Data (VPD) ...................................................................63

Viewing Maintenance/Firmware Information....................................................63

Viewing Fibre Channel Maintenance Information......................................64

Viewing FCoE Maintenance Information ...................................................66

The OneCommand Utility User Manual Page v

Viewing OneConnect Adapter Firmware Information.................................67

Viewing Target Information .............................................................................68

Viewing Fibre Channel Target Information ................................................69

Viewing iSCSI Target Information..............................................................69

Viewing LUN Information ................................................................................71

Viewing Fibre Channel LUN Information ...................................................71

Viewing iSCSI LUN Information ................................................................73

Viewing Fibre Channel Target Mapping (Windows and Solaris SFS)...............74

Viewing Target Mapping (Linux and VMware ESX) .........................................75

Viewing iSCSI and NIC PCI Registers............................................................. 76

Viewing iSCSI PCI Registers ....................................................................76

Viewing NIC PCI Registers .......................................................................77

Managing Adapters ...............................................................................................78

Configuring the Fibre Channel or FCoE Adapter Driver................................... 78

The Host Driver Parameters Tab .............................................................. 78

Setting Driver Parameters ........................................................................80

Setting Driver Parameters for a Single Adapter ..................................80

Restoring All Parameters to Their Earlier Values................................81

Resetting All Default Values ...............................................................81

Setting an Adapter Parameter Value to the Host Adapter

Parameter Value ................................................................................82

Saving Adapter Driver Parameters to a File .......................................82

Setting Driver Parameters for All Adapters in a Host .........................82

Changing Non-dynamic Parameter Values (Linux 8.2) .......................83

Changing Non-dynamic Parameter Values (VMware ESX) ................84

Creating a Batch Mode Driver Parameters File.........................................84

Assigning Batch Mode Parameters ....................................................85

Configuring CEE (Converged Enhanced Ethernet) Parameters ......................87

Configuring CEE/FCoE-Specific Parameters (LP21000 Series

Adapters Only)..........................................................................................87

Configuring CEE Parameters for FCoE Adapter Ports ..............................88

Configuring CEE Parameters for iSCSI Adapter Ports..............................93

Configuring FCoE Initialization Protocol (FIP) for FCoE Adapters...................96

Managing Ports .....................................................................................................99

Changing Adapter Port Names (FC Ports Only).............................................. 99

Resetting Adapter Ports ..................................................................................99

Modifying TCP/IP iSCSI Port Configuration...................................................100

Advanced TCP/IP Configuration .............................................................102

Configuring iSNS for iSCSI Target Discovery................................................ 103

Enabling and Disabling Fibre Channel Ports................................................. 104

Enabling and Disabling Physical Ports (OneConnect Adapters Only)............ 104

Configuring iSCSI Port Initiator Login............................................................105

Changing World Wide Name Configuration (FC and FCoE Ports Only)......... 108

Creating and Deleting Virtual Ports (FC and FCoE Ports Only)......................111

Creating Virtual Ports...............................................................................111

Deleting Virtual Ports ............................................................................. 113

Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and

Solaris SFS) ........................................................................................................ 115

Linux Considerations..................................................................................... 116

Enabling Authentication................................................................................. 116

The DHCHAP Tab ......................................................................................... 117

The OneCommand Utility User Manual Page vi

Changing Authentication Configuration................................................... 118

Changing Your Password.................................................................. 118

Viewing the Error and Event Log ...................................................... 119

Updating Adapter Firmware.................................................................................120

Updating Firmware for a Single Adapter........................................................ 120

Updating Firmware for Multiple Adapters ......................................................121

Updating CEE Firmware for a Single Adapter (LP21000 Series

Adapters Only) .............................................................................................. 123

Updating CEE Firmware on Multiple Adapters (LP21000 Series

Adapters Only) ............................................................................................. 126

Mapping and Masking (FC and FCoE Ports Only)...............................................128

Automapping SCSI Devices (Windows) ........................................................ 128

Mapping and Masking Defaults (Windows) .............................................129

Masking and Unmasking LUNs (Windows) .............................................129

Using Automapping and Persistent Binding (Windows)................................. 131

Changing Automapping Settings............................................................. 131

Adding a Persistent Binding....................................................................132

Binding a Target that Does Not Appear in the Persistent Binding Table ..133

Adding New Targets Using sd.conf (Solaris 8, 9 and 10) ........................ 134

Configuring Boot from SAN .................................................................................134

Boot Types ....................................................................................................135

Boot Device Parameters ...............................................................................135

Configuring Advanced Settings (Boot from SAN) .......................................... 139

Exporting SAN Information ..................................................................................143

Diagnostics .........................................................................................................144

Fibre Channel Diagnostics ............................................................................144

Viewing Flash Contents, PCI Registers and Wakeup Information ..........145

Viewing Flash Contents ..........................................................................145

Viewing Overlay Details .........................................................................146

Viewing the PCI Registers ......................................................................146

Running a Quick Test .............................................................................146

Running a Power On Self Test (POST) ...................................................147

Using Beaconing ....................................................................................147

Creating Diagnostic Dumps ....................................................................147

Running Advanced Diagnostic Tests....................................................... 148

Running Loopback Tests.........................................................................149

Loopback Test Combinations ..................................................................149

Running End-to-End (ECHO) Tests.........................................................151

Saving the Log File ................................................................................. 152

iSCSI, FCoE and NIC-Only Diagnostics (OneConnect Adapters Only) .........153

OneConnect iSCSI, FCoE and NIC-Only Loopback Test Combinations..154

Saving the Log File ................................................................................. 156

Using the OneCommand Manager Application Command-Line Interface............157

Using the CLI Client ......................................................................................160

Syntax Rules...........................................................................................160

The CLI Client Command Reference............................................................. 160

Parameters Not Supported by CIM Interface........................................... 162

Read-Only Mode..................................................................................... 166

Help Commands .....................................................................................166

The OneCommand Utility User Manual Page vii

Attributes Commands..............................................................................167

Authentication Commands......................................................................168

Boot Commands .....................................................................................170

CEE Commands .....................................................................................171

FCoE Commands....................................................................................175

Diagnostic Commands ............................................................................ 176

Driver Parameter Commands.................................................................. 179

Dump Commands ...................................................................................182

LUN Masking Commands .......................................................................183

Miscellaneous Commands ......................................................................184

Persistent Binding Commands................................................................ 188

TCP/IP Management Host File Commands............................................. 190

VPort Commands.................................................................................... 190

WWN Management Commands.............................................................. 192

iSCSI Commands....................................................................................193

ASCII Strings that May Be Returned ............................................................. 207

Troubleshooting...................................................................................................210

General Situations.........................................................................................210

Emulex Driver for Linux and OneCommand Manager Application

Situations ......................................................................................................212

VPorts and OneCommand Manager Application Situations........................... 216

The OneCommand Utility User Manual Page 1

Introduction

The Emulex

®

OneCommand

TM

Manager application is a comprehensive management utility for Emulex

host bus adapters (HBAs) and converged network adapters (CNAs) that provides a powerful, centralized

adapter management suite, including discovery, reporting and management of local and remote

adapters from a single console anywhere in the Storage Area Network (SAN) and across 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 both graphical user interface (GUI) and a command

line interface (CLI).

This manual describes the OneCommand Manager application for the following operating systems:

• Windows

• Solaris SAN Foundation Software (SFS) (‘emlxs’ is the module name for the Emulex driver for

Solaris SFS)

• Linux

• VMware ESX Server

Use the OneCommand Manager application to do any of the following (refer to Table 1 to determine if a

specific feature or task is supported by your operating system):

• Discover local and remote hosts, adapters, targets, virtual ports, virtual machines and Logical

Unit Numbers (LUNs)

• Enable local and FC discovery of Emulex and OEM branded Emulex adapters

• Change an adapter’s World Wide Port Name (WWPN) or World Wide Node Name (WWNN)

• Reset adapters

• Set up persistent binding on FC targets

• Set FC adapter driver parameters simultaneously to multiple adapters using Batch Update

• Set global driver parameters for FC adapters

• Update firmware and FC boot code (x86 BootBIOS, OpenBoot or EFIBoot) on a single adapter

or multiple adapters using Batch Update

• Enable or disable the adapter boot (x86 BootBIOS, FCode, EFIBoot or PXEBoot)

• Run diagnostic tests on adapters

• Manage local, FC remote and TCP/IP-accessed adapters

• Locate adapter ports using beaconing

• Mask and unmask FC LUNs

• Perform authentication using the Fibre Channel Security Protocol Diffie-Hellman Challenge

Handshake Authentication Protocol (FC-SP DHCHAP)

• Create and delete FC virtual ports (N_Port_ID virtualization [NPIV] must be enabled.)

• Run in read-only mode

• Configure FC boot from SAN

• Modify an IP port number of the remote management agent

• View vital product data (VPD) for the selected FC adapter port

• View transceiver information for the selected adapter port

• Save reports about discovered SAN elements

The OneCommand Utility User Manual Page 2

• Manage adapters on VMware ESX servers being managed through the Common Information

Model (CIM) interface

• Manage an adapter's CEE settings

• Enable or disable an adapter’s Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP)

• Supports COMSTAR (COmmon Multiprotocol SCSI TARget) for Solaris 11(build 90 or later)

enabling the Emulex driver for Solaris (EMLXS) to make a host appear as a target to the SAN

• Display Virtual Port and Virtual Machine mapping information

• Manage Emulex Fibre Channel, iSCSI, FCoE and NIC-Only Converged Network Adapters

(CNAs)

• Discover iSCSI targets

• Login to iSCSI Targets from CNAs

• View iSCSI Target session information

• Logout from iSCSI targets

Supported Features by Operating System

Not all OneCommand Manager application features are supported across all operating systems. The

following table lists the OneCommand Manager application features and their operating system support.

Table 1: The OneCommand Manager application Features and Tasks Cross-Reference

Feature/Task Windows Solaris SFS Linux

VMware ESX

Server

OneCommand Manager

application Graphical User

Interface (GUI)

XXX X*

OneCommand Manager

application Command Line

Interface (CLI)

XXX X

OneCommand Manager

application Web Launch

Interface utility

XXX

Discover local hosts, adapters,

targets and LUNs

XXX X*

Discover remote hosts,

adapters, targets and LUNs

XXX X*

Enable local discovery of

Emulex and OEM branded

Emulex adapters

XXX X*

Enable FC discovery of

Emulex and OEM branded

Emulex adapters

XXX X*

Change an adapter’s WWPN

or WWNN

XXX X*

Reset adapters

XXX X*

Set up persistent binding

XX

Set adapter driver parameters

simultaneously to multiple

adapters

XXX

Set global driver parameters to

adapters

XXX X**

Boot from SAN functionality

XXX X

The OneCommand Utility User Manual Page 3

* 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 supported on VMware ESX 3i Update 4 and versions of

VMware ESX 3.5 prior to Update 4.

Known Issues

See the product release notes for the latest information.

Update firmware and FC boot

code on a single adapter or

multiple adapters using batch

update

XXX X*

Enable or disable the x86

BootBIOS, EFI or OpenBoot

XXX X*

Run diagnostic tests on

adapters

XXX X

Manage local adapters

XXX X*

Manage FC remote and

TCP/IP accessed adapters

XXX X*

Locate adapters using

beaconing

XXX X

Mask and unmask LUNS

XX

Perform authentication using

FC-SP DHCHAP

XXX

Create and delete virtual ports

XXX

Run in read-only mode

XXX X*

Configure boot from SAN

XXX X*

Modify an IP port number

XXX X*

View vital product data

XXX X*

View transceiver information

XXX X*

Save SAN element reports

XXX X*

Manage adapters using CIM

XXX

Enable or disable FIP

XXX X*

COMSTAR support

X

Adapter hot swapping/hot

plugging

X

Table 1: The OneCommand Manager application Features and Tasks Cross-Reference (Continued)

Feature/Task Windows Solaris SFS Linux

VMware ESX

Server

The OneCommand Utility User Manual Page 4

Installing and Uninstalling OneCommand Manager

Application Components

Installing the OneCommand Manager Application

In Windows

The AutoPilot Installer

®

software streamlines the Emulex driver and OneCommand Manager application

installation. Refer to the Quick Installation Manual for more information. This manual is available on the

Emulex Web site for your driver version.

In Solaris SFS

The following must be installed before you can install the utilities:

• The Solaris SFS driver version 2.50 or later

• The Emulex Fibre Channel Adapter (FCA) utilities; refer to the FCA Utilities User Manual for

instructions on unpacking and installing the FCA utilities.

To install the OneCommand Manager application in Solaris SFS:

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-<version> 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 SFS driver utilities are

already present on the system, the install script attempts to remove them first:

./install

5. When prompted, 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.

6. If you answered <2> or <3> in step 5, you are asked if you want the OneCommand Manager

application to operate in read-only mode. Read-only mode prevents 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

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.

7. You are prompted about allowing users to change the management mode after installation.

Enter <y> for yes, or <n> for no.

The OneCommand Utility User Manual Page 5

In Linux

The following must be installed before you can install the utilities:

• The appropriate driver for your operating system:

• Linux driver version 8.2.0.33.3p or later (For RHEL5 and SLES10 operating systems.)

• Linux driver version 8.2.8.x or later (For SLES11 operating systems.)

• 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 Web site or copy them to the system from the 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 (use cd command) to the directory to which you copied the tar file.

6. Untar the file.

• For RHEL 5 and SLES 10 type:

tar zxvf elxocm-rhel5-sles10-<apps_ver>-<rel>.tgz

• For SLES 11 type:

tar zxvf elxocm-sles11-<apps_ver>-<rel>.tgz

7. Change (use cd command) to the elxocm directory created in step 6.

• For RHEL 5 and SLES 10 type:

cd elxocm-rhel5-sles10-<apps_ver>-<rel>

• For SLES 11 type:

cd elxocm-sles11-<apps_ver>-<rel>

8. Uninstall any previously installed versions. Type:

./uninstall.sh

9. Run the install script. Type:

./install.sh

10. 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.

11. If you answered <2> or <3> in step 10, you are asked if you want the OneCommand Manager

application to operate in read-only mode. Read-only mode prevents 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

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.

The OneCommand Utility User Manual Page 6

12. You are prompted about allowing users to change the management mode after installation.

Enter <y> for yes, or <n> for no.

In VMware ESX Server

The following must be installed before you can install the utilities:

• Emulex Driver for VMware ESX, version 7.4 or later is required 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 (be2net) is required only if FCoE/iSCSI/NIC functionality is desired.

• The iSCSI driver (be2iscsi) is required only if iSCSI functionality is desired.

To install the OneCommand Manager application Agent in VMware ESX Server:

1. Log into the ESX Server Host COS.

2. Copy the elxocmcore-esx<NN>-<version>-<arch>.rpm file to a directory on the install machine,

where NN is 35 for ESX 3.5 or 40 for an ESX 4.0 system.

3. CD to the directory to which you copied the rpm file.

4. Install the rpm. Type:

rpm -ivh elxocmcore-esx<NN>-<version>-<arch>.rpm

Where NN is 35 for an ESX 3.5 system or 40 for an ESX 4.0 system. The rpm contents are

installed in /usr/sbin/hbanyware. The OneCommand Manager application Command Line Inter-

face 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:

In Windows:

• Microsoft Internet Information Services (IIS) Server must be installed. See the Microsoft

Web site for information on downloads and installation.

• You must install a separate Java Runtime Environment (JRE) 6.0 on hosts that will be used

as Web Launch clients. The OneCommand Manager application does not run with pre-6.0

versions of the JRE. The JRE and instructions for installing it are available at

http://java.sun.com/downloads/index.html

• The Windows Firewall feature may be enabled by default. If it is, you must add and enable

three exceptions: HTTP port, java.exe and rmiregistry.exe (both included with the JRE).

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 the radio button on TCP and click OK.

Note: The OneCommand Manager application Web Launch Interface is not supported on

VMware ESX Server.

Note: Allowing programs and/or ports through the firewall may increase the security risks.

Use at your own discretion.

The OneCommand Utility User Manual Page 7

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 bin directory of the JRE installation path. For example:

C:\Program Files\Java\jre1.6.0_06\bin\java.exe.

4. Click OK.

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 bin directory of the JRE

installation path. For example:

C:\Program Files\Java\jre1.6.0_06\bin\rmiregistry.exe.

3. Click OK.

4. Click OK to apply the new firewall settings.

In Solaris SFS and Linux:

• Apache Web server must be installed and running on the server that is hosting the Web

Launch Service software.

• The Java Web Start application must be installed and running on the browser host.

The system on which you are installing the Web Launch Service package (the server) 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:

MIME type: application/x-java-jnlp-file

File Extension: jnlp

• The HTTP server must be running.

The system on which you are running the browser (the client) requires:

• Java must be installed. The specific requirements are:

• Sun 32-bit Java 6.0 or later for Intel based systems (x86 and IA64)

• 32-bit Java 6.0 or later for x86-64 systems

• 32-bit Java 6.0 or 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/HBAnyware/README_WEBLAUNCH.txt (Solaris) or

/usr/sbin/hbanyware/README_WEBLAUNCH.txt (Linux) for more setup information.

Procedures

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.

In Solaris SFS and Linux:

1. Log on as ‘root’.

2. Navigate to the HBAnyware directory.

• Solaris SFS:

cd /opt/HBAnyware

The OneCommand Utility User Manual Page 8

• Linux:

cd /usr/sbin/hbanyware

3. Run the install script. Type:

./wsinstall

4. When prompted, enter the Web server's document root directory. For example:

• Solaris SFS:

/var/apache/htdocs

•Linux:

/srv/www/htdocs

or

/var/www/html

5. You are provided with the IP address of the host and asked if that 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. You are 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 config-

uration files are created and Web Launch Service automatically starts.

7. To verify the installation, locate another client, open a Web browser window and enter this URL

according to this format:

http://IP_ADDR:PORT_NUM/ocmanager.jnlp

where IP_ADDR is the IP address of 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 is displayed.

Installing the OneCommand Manager Application Command Line Interface

The OneCommand

TM

Manager application Command Line Interface (CLI) is a comprehensive

management utility for Emulex host bus adapters (HBAs) and converged network adapters (CNAs) that

provides support for commonly used commands without requiring installation of the OneCommand

Manager application Graphical User Interface (GUI). The OneCommand Manager application CLI is a

separate application with core driver kits that do not include the OneCommand Manager application

GUI. The OneCommand Manager CLI console application name is hbacmd and 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 CLI Client” on page 160.

Note: It is not necessary to enter a port number if the standard HTTP port was chosen

during configuration.

The OneCommand Utility User Manual Page 9

Platforms that are supported with the OneCommand Manager application CLI are detailed in Table 2.

In Windows

To install the OneCommand Manager application CLI, run the installation .exe file for a core Windows

driver kit that does not include the OneCommand Manager application GUI:

• elxocmcore-windows-<kit version>.exe

<kit version> represents the complete version. For example: elxocmcore-windows-5.0.2.14-1.exe

In a New 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.

Table 2: OneCommand Manager Application Command Line Interface Supported Platforms

Driver Architecture Operating System

Storport Miniport Driver Intel x86, x64, and IA64

Note: Intel IA64 supported for Fibre

Channel adapters only.

Windows Server 2003 Service Pack

2 or later

Windows Server 2008

Windows Server 2008 R2

LPFC 7.4.x Driver Intel x86, EM64T and AMD64 VMware ESX Server 3.5

LPFC 8.2.0.33.3p Open

Source Driver for Red Hat

(RHEL) 5.3 and later, SUSE

Linux Enterprise Server

(SLES) 10-SP2 and later

Intel x86, EM64T, AMD64, PPC64

and IA 64

RHEL 5.3 and later, and SUSE Linux

Enterprise Server 10-SP2 and later

LPFC 8.2.8.x Open Source

Driver for SUSE Linux

Enterprise Server 11 GM

Intel x86, EM64T, AMD64, PPC64

and IA 64

SUSE Linux Enterprise Server 11

GM

Solaris SFS 2.50 Driver Intel x86, EM64T, AMD64 and Sun

SPARC

Solaris 10 and Solaris 11

Note: OneConnect adapters are not supported for IA64, PPC64, and Solaris platforms.

The OneCommand Utility User Manual Page 10

Prerequisites

• The LPFC driver version 7.4 or later must be loaded.

Procedures

To install the OneCommand Manager application CLI:

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. CD to the directory to which you copied the rpm file.

4. Install the rpm file. Type:

rpm -U elxocmcore-esxNN-<kit version>.<arch>.rpm

Where NN is 35 for an ESX 3.5 system. The rpm contents are installed in /usr/sbin/hbanyware. 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:

# rpm -U elxocmcore-esxNN-<kit version>.<arch>.rpm

Where NN is 35 for an ESX 3.5 system.

Uninstalling Older HBAnyware Kits on VMware

To uninstall an older HBAnyware Kit on VMware:

1. Log into the ESX Server Host 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 35 for an ESX 3.5 system.

Note: In-band management (FC based management) is not supported on VMware ESX 3.5

servers. Use out-of band management (TCP/IP based management) to remotely

manage adapters on ESX 3.5 servers.

For VMware ESX 3.5 servers, the firewall on the ESX Server must be opened to man-

age systems remotely using TCP/IP-based management. To enable TCP port

#23333, run the following commands:

esxcfg-firewall --openPort 23333,tcp,in,OneCommand

esxcfg-firewall --openPort 23333,tcp,out,OneCommand

To verify that the correct port is open, run the following command:

esxcfg-firewall -q

The TCP port number can be changed. If it is not changed, the default is 23333.

Refer to the VMware Server Configuration Guide for more details on how to configure

the ESX firewall.

The OneCommand Utility User Manual Page 11

3. Type:

rpm -e elxvmwarecorekit-<kit version>

Or

rpm -e elxocmcore-esxNN-<kit version>

Where NN is 35 for an ESX 3.5 system.

In a New Linux System

Prerequisites

For existing systems the following must be installed 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.2.8.x (For SLES11 operating systems.)

On OneConnect iSCSI adapters:

• be2iscsi driver ;

On OneConnect NIC adapters:

• be2net driver

• The be2net driver must also be installed if the adapter personality is iSCSI-NIC or FCoE-NIC.

Use the latest or matching driver from the Emulex Web site.

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 (use cd command) to the directory to which 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

Note: On RHEL 5.3 and RHEL 5.4, the OneCommand Core rpm file requires Libnl. This

library is not installed by default, but can be obtained from the OS distribution media.

• For i386 RHEL 5.3 and RHEL 5.4, use the 32bit libnl library.

• For x86_64 RHEL 5.3 and RHEL 5.4, use the 64bit libnl library.

• For ia64 RHEL 5.3 and RHEL 5.4, use the 64bit libnl library.

• For PPC RHEL 5.3 and RHEL 5.4, 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

The OneCommand Utility User Manual Page 12

In a Linux System with an Existing HBAnyware CLI Kit InstalledI

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 a New Linux System” on page 11.

The rpm file handles the configuration file upgrade.

The install script executes an rpm upgrade (rpm -U *.rpm) to upgrade the installed version of the

core kit to the current version.

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/hbanyware/scripts directory.

2. Install the specific rpm file for your driver for Linux version. For information on installing the rpm

file, see “In a New Linux System” on page 11.

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

Note: On RHEL 5.4 installations, the elxocmlibhbaapi-*.rpm conflicts with the Red Hat 5.4

libhbaapi-devel rpm. Therefore, the core kit install.sh script installs the

elxocmlibhbaapi only if the Red Hat libhbaapi-devel rpm is NOT installed.

Currently there is no conflict on SLES 10 and 11 platforms and the elxocmlibhbaapi

and elxocmcore rpms are always installed.

Note: The OneCommand Manager application core kit cannot be installed if a previous

version of HBAnyware is installed.

Note: There is no upgrade path from an HBAnyware 4.x or 3.x core kit to a OneCommand

Manager application 5.0 core kit. You must uninstall previous versions of the

HBAnyware utility before installing a OneCommand Manager application core kit. For

information on uninstalling older versions of HBAnyware, see “Uninstalling Older

HBAnyware Kits on Linux” on page 12.

Note: If an HBAnyware CLI or enterprise kit is installed, follow the procedure for

“Uninstalling Older HBAnyware Kits on Linux” on page 12.

Note: Your configuration files are backed up by rpm with an .rpmsave extension.

The OneCommand Utility User Manual Page 13

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 steps:

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

In Solaris SFS

Prerequisites

• The Solaris SFS 2.50 driver must be installed.

Procedures

To install the OneCommand Manager application CLI:

1. Copy the OneCommand Manager application core kit to a temporary 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 core kit, the OneCommand

Manager application enterprise kit, or the Solaris SFS driver utilities are already present on the

system, the install script attempts to first remove them.

Page is loading ...

Emulex ProLiant BL620c G7, OneCommand Manager 5.0 User manual

Related papers

Other documents