OneCommand
™
Manager
Application
Version 5.0
User Manual
One Network.
One Company.
P004343-01A Rev. A Connect with Emulex.
Copyright © 2003- 200 9 Em ul ex. A l l ri gh ts reserved worldwide. No part o f t h is document may be reproduced by any
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 Con nect , Emulex Secure, EZPilot, FibreSpy, HBAnyware, InSpeed, LightPulse,
MultiPulse, OneCommand, OneC onn ect, O ne Net work . O ne Compan y., SBOD, SLI, and VEngine are trademarks of
Emulex. Al l other brand or product names referenced herein are trademarks or registered trademarks of their
respective companies or organizations.
Emulex provides this manual "as i s " wi thout any warranty of any ki nd , eit her 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 m a y
result. Periodic changes are made to information contained herein; although these changes will b e incor por ated 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 C overed Softw are in Sourc e Code form may be obtaine d 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.
The OneCommand Utility User Manual Page ii
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 Interfac e ... 6
Prerequisites...............................................................................................6
Procedures.................................................................................................. 7
Installing the OneCommand Manager Application Comman d Line In terface .....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 Ki t 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 Enterpr ise 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 Applicat ion 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 OneComman d Manage r Applic atio n
Web Launch Interface............................................................................... 17
Using the OneCommand Manager Application...................................................... 18
The OneCommand Manager Application Win dow Element Defi nitio ns ........... 18
The Menu Bar ...........................................................................................19
The Toolbar............................................................................................... 19
The Toolbar Buttons ................................................................................. 19
The Discovery-Tree .................................................................................. 20
The OneCommand Utility User Manual Page iii
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 Pro tocol ............................ 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 iv
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) Parameter s ......................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 Por ts .............................. 93
Configuring FCoE Initialization Protocol (FIP) for FCoE Ad apters................... 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 (One Connect Adapter s 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 v
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 (LP2100 0 Series
Adapters Only) .............................................................................................. 123
Updating CEE Firmware on Multiple Adapter s (LP210 00 Ser ies
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 Adapte rs Only) ......... 153
OneConnect iSCSI, FCoE and NIC-Only Loopback Test Combinations.. 154
Saving the Log File ................................................................................. 156
Using the OneCommand Manager Application Command- Line Inte rface ............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 vi
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 Manag er Appli catio n
Situations ...................................................................................................... 212
VPorts and OneCommand Manager Application Situations........................... 216
The OneCommand Utility User Manual Page vii
Introduction
The Emulex® OneCommandTM 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 dis covery, reporting and management of local and remote
adapters from a single console anywher e in the Storage Area Network (SAN) and acr oss pla tforms.
Remote configuration capability can be provided b y either Fib re Chan nel (F C) acces s v ia host sy stem s
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 applic ation for the followin g oper ating s ystems :
• 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 opera ting s ystem):
• Discover local and remote hosts, adapters, targets, virtual p orts, virtual machi nes and Logi cal
Unit Numbers (LUNs)
• Enable local and FC discovery of E mulex and O EM b randed Emulex adapters
• Change an adapter’s World Wide Port Name (WWPN) or World Wide Node Name (WW NN)
• Reset adapters
• Set up persistent binding on FC targets
• Set FC adapter driver parameters simultaneously to multip le adap ters usi ng Ba tch Upda te
• Set global driver parameters for FC adapters
• Update firmware and FC boot code (x86 BootBIOS, O penB oot or EF IBoot) on a s ingl e adapte r
or multiple adapters using Batch Upda te
• Enable or disable the adapter boot (x86 Boot BIOS, FC ode, EFIB oot or PXE Boot)
• Run diagnostic tests on adapters
• Manage local, FC remote and TCP/IP-acc ess ed ada pters
• Locate adapter ports using beaconing
• Mask and unmask FC LUNs
• Perform authentication using the Fibre Channel Sec urity P rotocol Di ffie-Hellman Cha llen ge
Handshake Authentication Protocol (FC-SP DHCHAP)
• Create and delete FC virtual ports (N_Port_ID vi rtualiz ation [NP IV] mus t be ena bled.)
• 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 1
• Manage adapters on VMware ESX servers b eing ma naged thr ough the Commo n Information
Model (CIM) interface
• Manage an adapter's CEE settings
• Enable or disable an adapter ’s Fibre Channel o ver Ether net (F CoE) Initia liz ation P ro tocol (FIP)
• Supports COMSTAR (COmmon Multiprotocol SCSI TARget) for Solaris 11(build 90 or later)
enabling the Emulex driver for Solaris (EM LXS ) to ma ke a ho st appe ar as a target to the S AN
• Display Virtual Port and Virtual Machine mapping informati on
• Manage Emulex Fibre Channel, iSCSI, FCoE and NIC-Onl y Converged Networ k A dapters
(CNAs)
• Discover iSCSI targets
• Login to iSCSI Targets from CNAs
• View iSCSI Target session information
• Logout from iSCSI targets
Supported Features by Operat ing S ystem
Not all OneCommand Manager application features are supp orted across all oper ating sys tems . 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
OneCommand Manager
application Graphical User
Interface (GUI)
OneCommand Manager
application Command Line
Interface (CLI)
OneCommand Manager
application Web Launch
Interface utility
Discover local hosts, adapters,
targets and LUNs
Discover remote h osts,
adapters, targets and LUNs
Enable local disco very of
Emulex and OEM branded
Emulex adapters
Enable FC discove ry of
Emulex and OEM branded
Emulex adapters
Change an adapte r’s WWPN
or WWNN
Reset adapters
Set up persistent bi ndi ng
Set adapter drive r para met ers
simultaneously to mult iple
adapters
Set global driver parameters to
adapters
Boot from SAN functionality
XXX X*
XXX X
XXX
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
XX
XXX
XXX X**
XXX X
VMware ESX
Server
The OneCommand Utility User Manual Page 2
Table 1: The OneCommand Manager application Features and Tasks Cross-Reference (Continued)
Feature/Task Windows Solaris SFS Linux
Update firmwar e and FC boot
code on a single adapter or
multiple adapte rs us ing bat ch
update
Enable or disable the x86
BootBIOS, EFI or Open Boot
Run diagnostic tests on
adapters
Manage local adapters
Manage FC remote and
TCP/IP accessed adapt er s
Locate adapters using
beaconing
Mask and unmask LUNS
Perform authent ica tion us ing
FC-SP DHCHAP
Create and delete virtua l ports
Run in read-only mode
Configure boot from SAN
Modify an IP port number
View vital product data
View transceiver information
Save SAN elemen t re po rts
Manage adapters using CIM
Enable or disable FIP
COMSTAR support
Adapter hot swapp ing /hot
plugging
XXX X*
XXX X*
XXX X
XXX X*
XXX X*
XXX X
XX
XXX
XXX
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
XXX X*
XXX
XXX X*
X
X
VMware ESX
Server
* 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 la test in forma tion.
The OneCommand Utility User Manual Page 3
Installing and Uninstalling OneCommand Manager
Application Components
Installing the OneCommand Manager Applicati on
In Windows
The AutoPilot Installer
installation. Refer to the Quick Installation Manual for mor e in forma tion. This manua l is avai labl e on the
Emulex Web site for your driver version.
In Solaris SFS
The following must be installed before you can ins tall the utili ties :
• The Solaris SFS driver vers ion 2.5 0 or later
• The Emulex Fibre Channel Adapter (FCA) uti lities; r efer to the FCA Util itie s User Manual for
instructions on unpacking and ins talling the FC A uti liti es.
To install the OneCommand Manager application in Solaris SFS:
1. Copy the So lar is u tility ki t to a tempo rary di re ctor y on y our sy stem .
2. Untar the utility k it:
tar xvf elxocm-solaris-<version>.tar
3. Chang e to the newl y create d elx ocm -solar is -<versi on> di rector y:
cd ./elxocm-solaris-<version>/
4. Ex ecute the install script to begin installation. If the HBAnyware uti lity, OneCommand Manager
Core or OneCommand Manager Enterprise appli cations or the Solar is SF S driv er utili ties are
already present on the system, the in stall scrip t attempts to remove the m fir st:
./install
5. Wh en 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 yo u ans wered <2> or <3> in step 5, you are asked if yo u want the OneCommand Manager
application to operate in read-only mode. Rea d-only m ode pr eve nts users from perfo rming
certain operations such as resetting adapters, up dating 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 mod e is d e sired.
7. You are prompted about allowing users to change the management mode after installatio n.
Enter <y> for yes, or <n> fo r no.
®
software streamlines the Emulex driver and OneCommand Manager application
The OneCommand Utility User Manual Page 4
In Linux
The following must be installed before you can ins tall the utili ties :
• The appropriate driver for your operating system:
• Linu x driv er vers ion 8.2.0.33.3p o r la ter (For RHE L5 and SLES 10 oper ating sy stems. )
• Linu x dr iver v ersion 8.2.8.x or la ter ( For S LES11 operating systems.)
• Previous versions of the Linux driv er mu st be un ins talled. You must run the uninstall script that
shipped with the version of the Linux driver y ou want to r emove.
To install the OneCommand Manager application in Linux:
1. Log o n 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 an d unins tallation s cripts to a kno wn loc ation, for eas y ac ces s by other
users.
4. Copy the OneComma nd elx ocm -< Pla tform>-<AppsRev>.tgz fi le to a d ire ctory on the ins tall
machine.
5. Chang e (use c d comm and) to the di rect ory to which y ou cop ied the tar file.
6. Untar the file.
• For RHE L 5 and S LES 10 type :
tar zxvf elxocm-rhel5-sles10-<apps_ver>-<rel>.tgz
• For S LES 11 type:
tar zxvf elxocm-sles11-<apps_ver>-<rel>.tgz
7. Chang e (use c d comm and) to the elxoc m dir ecto ry cr eated in step 6 .
• For RHE L 5 and S LES 10 type :
cd elxocm-rhel5-sles10-<apps_ver>-<rel>
• For S LES 11 type:
cd elxocm-sles11-<apps_ver>-<rel>
8. Unin stall any p rev iously ins talled ver sio ns. Type:
./uninstall.sh
9. Run the install s cript. 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 Ma nager
application to operate in read-only mode. Rea d-only m ode pr eve nts users from perfo rming
certain operations such as resetting adapters, up dating 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 mod e is d e sired.
The OneCommand Utility User Manual Page 5
12. You are prompted about allowing users to change the manag ement mo de after installation.
Enter <y> for yes, or <n> fo r no.
In VMware ESX Server
The following must be installed before you can ins tall the utili ties :
• Emulex Driver for VMware ESX, version 7.4 or l ater is requir ed on ly i f FC/FCoE functi onalit y is
desired. Refer to the Emulex Driver for VMware ESX User Manu al for spe cifi c inform ation on
driver support in ESX Releases.
• The NIC driver (be2net) is required onl y if FCoE /iSCS I/NIC functi onali ty is des ired.
• The iSCSI driver (be2iscsi) is req uired only if i SCSI fun ction ality is desi red .
To install the OneCommand Manager application Agent in VMware ESX Ser ver:
1. Log i nto the ESX S er ver Host CO S.
2. Copy the elxoc mcor e- esx<NN> -<ver si on>-< arch>.r pm fi le to a di rector y on the ins tall machin e,
where NN is 35 for ESX 3.5 or 40 for an ESX 4.0 system.
3. CD to the di rector y to whi ch you c opied th e rpm file.
4. Ins tall 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 E SX 4 . 0 system. T he rpm c ontents are
installed in /usr/sbin/hbanyware. The OneCommand Man ager applicati on Comman d 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 appl ica tion Web Lau nch Int erfa ce is no t su ppo rted on
VMware ESX Server.
In Windows:
• Mic rosoft Internet Infor mation Ser vices (IIS) S erver must b e ins talled. See the M icr osoft
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 applica tion doe s not run with pre-6.0
versions of the JRE. The JRE and instru ctio ns for ins talling it ar e avail able at
http://java.sun.com/downloads/index.html
• The Wi ndows F irewal l feature may be ena bled by default. If it is , you must a dd and ena ble
three exceptions: HTTP port, java.exe and rmir egis try.exe (both included with the JRE).
Note: Allowing programs and/or ports through the firewall may increase the security risks.
Use at your own discret ion .
To enable the HTTP port:
1. Click Add Port... The Add a Port dialog box is di spla ye d.
2. On the Add a Port dialog box, type HTTP as the Name and 80 as the Port Numbe r.
3. Leave the radio button on TCP and click OK.
The OneCommand Utility User Manual Page 6
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 exampl e:
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 dis play ed.
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 b e installed and running on the s erver th at is hosti ng the Web
Launch Service software.
• T he Java Web Start application must be installed and running on the br owser hos t.
The system on which you are installing the Web Launch Serv ic e package (the s erver) requir es :
• An HTTP server configured to handle the JNLP MIME file type. The following MIME file type/
file extension must be added to your serve r configur ati on:
MIME type: application/x-java-jnlp-file
File Extension: jnlp
• The HTTP ser ver mus t be running .
The system on which you are running the brows er (the c lien t) requir es :
• Jav a must be installed. The specific requirements are:
• Sun 3 2-bit Jav a 6.0 or late r for Intel b ased s ystems (x86 and IA 64)
• 32- bit Java 6.0 or later for x86-64 systems
• 32- bit Java 6.0 or l ater for RHEL 5 and S LES 1 0 (ppc64)
Refer to the appropriate vendor documentation for detailed instructions about configuring MIME
types, configuring and starting the HTTP ser ver and i nstalling 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 S erver 2008 and W ind ows Serv er 2008 R2) :
1. Cli ck Pro grams> Emulex >O CManag er WebLaunch Install. Web Launch installation begi ns.
In Solaris SFS and Linux:
1. Log o n as ‘ root’.
2. Nav igate to the HBAn ywar e direc tory.
• Solari s SFS:
cd /opt/HBAnyware
The OneCommand Utility User Manual Page 7
• Linu x:
cd /usr/sbin/hbanyware
3. Run the install s cript. Type:
./wsinstall
4. Wh en pr ompted, e nter the Web server's d ocum ent ro ot director y. For example:
• Solari s 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 >, y ou are pro mpted for the por t yo u want to us e.
Once you have entered the necessary infor mation, you ar e noti fied whe n the ins tallation of the
OneCommand Manager application Web Launch package is complete. The Web Launch configuration files are created and Web Launch Service au tomatic all y 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 ins talled the OneComm and Mana ger
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.
Note: It is not necessary to ente r a po rt numb er if th e stand ar d HTT P po rt wa s chos en
during configura ti on.
Installing the OneCommand Manager Application Command Line Interface
The OneCommandTM Manager application Command Line Interface (C LI) is a compr ehensiv e
management utility for Emulex host bus adapters ( HBA s) and conver ged n etwork adapte rs (CNAs) that
provides support for commonly used comm ands wi thout requir ing installation of the O neCom mand
Manager application Graphical User Interfa ce (GUI). T he OneComman d Manager application CLI is a
separate application with core driver kits that do not incl ude the OneCom mand Ma nager appli cation
GUI. The OneCommand Manager CLI console appli cation name is hbacmd and can be installed on
Windows, Solaris, Linux and versions of VM ware ESX Ser ver that in clud e a Cons ole O perating S ystem
(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.
The OneCommand Utility User Manual Page 8
Platforms that are supported with the OneCommand Manager appl ica tion CLI ar e detailed i n Table 2.
Table 2: OneCommand Manager Application Command Line Interface Supported Platforms
Driver Architecture Operating System
Storport Miniport Driver Intel x86, x64, and IA6 4
Note: Intel IA64 supported for Fi br e
Channel adapters only.
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 Enterpr i se Server
(SLES) 10-SP2 and later
LPFC 8.2.8.x Open Source
Driver for SUSE Linu x
Enterprise Server 11 GM
Solaris SFS 2.50 Drive r Intel x86, EM64T, AMD64 and Sun
Note: OneConnect adapters are not supported for IA64, PPC64, and Solaris platforms.
Intel x86, EM64T, AMD64, PPC64
and IA 64
Intel x86, EM64T, AMD64, PPC64
and IA 64
SPARC
Windows Server 2 003 Se rv ice P ack
2 or later
Windows Server 200 8
Windows Server 200 8 R2
RHEL 5.3 and lat er , an d SUSE Lin ux
Enterprise Server 10-SP2 and later
SUSE Linux Enterprise Server 11
GM
Solaris 10 and Solaris 11
In Windows
To install the OneCommand Manager application CLI, run the installation .exe file for a core Wi ndows
driver kit that does not include the OneComm and Mana ger appli catio n GUI:
• elxocmcore-windows-<kit versi on >.e xe
<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.
The OneCommand Utility User Manual Page 9
Prerequisites
• The LPFC driver version 7.4 or later mus t be loa ded.
Note: In-band management (FC based management) is not supported on VMware ESX 3.5
servers. Use out-of band mana gem ent (T CP/ IP bas ed ma nag eme nt) to rem otely
manage adapters on ESX 3.5 servers.
For VMware ESX 3.5 servers, the firewall on the ESX Server must be opened to manage systems remotely using T CP/ IP -bas ed man ag eme nt. 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 po rt is open, ru n th e fol lo wing comman d:
esxcfg-firewall -q
The TCP port number can be change d. If it is not cha nge d, the defaul t is 2333 3 .
Refer to the VMware Server Configuration Guide for more details on how to configure
the ESX firewall.
Procedures
To install the OneCommand Manager application CLI:
1. Log i nto the ESX S er ver Host CO S.
2. Copy the elxoc mcor e-esx NN-<ki t ver si o n>.< arch> .rpm fi le to a director y on the ins tall machi ne.
3. CD to the di rector y to whi ch you c opied th e rpm file.
4. Ins tall the rpm file. Type:
rpm -U elxocmcore-esxNN-<kit version>.<arch>.rpm
Where NN is 35 for an ESX 3.5 system. The rpm c ontents are installed i n /usr /sbin/hbanyware. The
OneCommand Manager application CLI is al so 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. Ins tall the rpm file by enter ing th e follo wing co mmand all o n one li ne:
# 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 i nto the ESX S er ver Host CO S.
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.
The OneCommand Utility User Manual Page 10
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 mu st be i nstalled befo re installing th e One Command Manager
application CLI:
On
LP21000 series adapters a nd OneConnec t FCoE adap ters:
• Linux driver version 8.2.0.33.3p or later (For RHE L5 and SLES 10 ope rating sy stem s.)
• Linux driver version 8.2.8.x (For SLE S11 operating systems.)
On OneConnect iSCSI adapters:
• be2iscsi driver ;
On OneConnect NIC adapters:
• be2net driver
• The be2net driver must also be installed if the adapter personal ity is i SCSI-NIC or FCoE-NIC.
Use the latest or matching driver from the Emule x Web site.
For new systems, the specific driver rpm file for you r Linux v ersio n must b e ins talled.
Note: On RHEL 5.3 and RHEL 5.4, the OneC omman d Co re rpm fil e re qui re s Lib nl . This
library is not installe d by def au lt, bu t can be ob taine d from th e OS distri bu tio n med ia .
• For i386 RHEL 5.3 and RHEL 5.4, use the 32bit libnl l ibrary.
• For x86_64 RHEL 5.3 and RHEL 5.4, use the 64bi t libnl lib rary.
• For ia64 RHEL 5.3 and RHEL 5.4, use the 64bit libnl l ibrary.
• For PPC RHEL 5.3 and RHEL 5.4, use the 32bit libnl l ibrary.
Procedures
To install the OneCommand Manager application CLI:
1. Copy the applic ations ki t tar file to a directory on the installatio n mac hine.
2. Chang e (use c d comm and) to the di rect ory to which y ou cop ied the tar file.
3. Untar the file.
tar zxvf elxocmcore-<supported_os>-<app_ver>-<rel>.tgz
4. Chang e (use c d comm and) to the core k it direct ory cr eated in ste p 3.
cd elxocmcore-<supported_os>-<app_ver>-<rel>
5. Run the install.s h sc ript.
./install.sh
Note: The core kit consists of 2 rpm files for eac h sup port ed ar ch itect ur e and eac h
supported version of Linux:
1. elxocmlibhbaa pi-*.rpm
2. elxocmcore-*.rpm
The OneCommand Utility User Manual Page 11
In a Linux System with an Existing HBAnyware CLI Kit InstalledI
Note: On RHEL 5.4 installations, the el xoc mli bhb aapi- *.r pm confli cts with th e Re d Hat 5.4
libhbaapi-devel rpm. Therefor e, the core kit install.sh scr i pt installs the
elxocmlibhbaapi onl y if t he Red H at lib hba ap i-dev el r pm is NO T in stalled.
Currently there is no conf li ct on SLES 10 and 11 platforms and the elxocmli bhbaa pi
and elxocmcore rpms are always installed.
Note: The OneCommand Manager appl ica tion co re kit can no t be installed if a pr evi ous
version of HBA nyware is installed.
You have two options when installing the OneCommand Manager applic ation CLI on a Lin ux s ys tem:
• Upgrade - preserve existing settin gs
• Clean install - overwrite existing settings
To upgrade:
1. You must install the current core kit as detailed in “In a New Linux Sy ste m” on page 11.
The rpm file handles the configuration file upgr ade.
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 HBA nyw are 4. x or 3. x core ki t to a OneComma nd
Manager applica tion 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 old er versions of H BAnyware, see “ Uninstalling Older
HBAnyware Kits on Linux” on page 12.
To perform a clean install:
1. Unin stall the ex isting O neComma nd Manag er ap plic ation CLI usi ng the uninstall sc ript inc lud ed
in the tar file or in /usr/sbin/hbanyware/scripts directory.
Note: If an HBAnyware CLI or ent erpr i se kit is instal le d, foll ow th e proce dur e for
“Uninstalling Older HB Anyw a re Kits on Li nux ” on page 12.
Note: Your configuration files are backed up by rpm w ith an .rpmsave extension.
2. Ins tall the specific rpm file for your driver for Linux versio n. For information on ins talling 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 followi ng command to rem ove the core ki t.
rpm -e elxlinuxcorekit
Uninstalling an older HBAnyware enterprise kit:
1. Run the unins tall script locate d in /us r/sbin/h banywa re/s cripts to rem ove the enterpri se kit.
Or
Run the uninstall script located in the tar file to remove the enterp rise k it.
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
The OneCommand Utility User Manual Page 12
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 HB Anyw are Secu rity Confi gurator i s installed, follow these steps:
a. Log on as ‘root’ .
b. Change to the dire ctory to which you copi ed the tar file .
c. Extract the tar file using the tar -xvf command.
d. Change to the newly created dir ectory.
e. Run the unins tall script with the ssc paramete r s pecified. Type:
./uninstall ssc
3. Unin stall the HBA nyware uti lity and the A ppli cation Helpe r Mo dule:
a. Log on as ‘root’ .
b. Change to the dire ctory to which you copi ed the tar file .
c. Extract the tar file using the tar -xvf command.
d. Change to the newly created dir ectory.
e. Uninstall any pr evious ly i nstalled v ersions. Type:
./uninstall
In Solaris SFS
Prerequisites
• The Solaris SFS 2.50 driver must be ins talled.
Procedures
To install the OneCommand Man ager applicati on CLI:
1. Copy the OneComma nd Manager application core kit to a temporar y d irector y on th e sy stem .
2. Untar the core k it. Type:
tar xvf elxocmcore-<kit version>.tar
3. Chang e to the newl y create d elxocm cor e-<ki t ver sio n> directory:
cd ./elxocmcore-<kit version>/
4. Run the install s cript and fo llow the ins tructions .
./install
If the HBAnyware utility, the OneCommand Manager application core kit, the OneCommand
Manager application enterprise kit, or the Sol aris S FS dri ver util itie s are alr eady present on the
system, the install script attempts to first remove them.
The OneCommand Utility User Manual Page 13
Upgrading from the OneComman d Man ager Appli catio n CLI to th e Ful lFeatured OneCommand Manage r Appl icati on En terpr ise K it
Note: An upgrade can be performed onl y if the ve rsi on of th e OneC omman d Man age r
application enterpr is e kit is the same or later th an the One C ommand Ma nag er
application CLI ve rsion . You cannot upgrade a OneCommand Mana ge r ap pli cat ion
CLI with a previous version of the OneCommand Manager application enterprise kit.
In Windows
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application enterprise kit:
1. From the des ktop, run the elxocm-windows-<kit version>.exe file that contains the full
application kit.
Running this executable file removes the OneCommand Manage r app lic ation CL I and ins talls a
full-featured version of the OneCommand Manager a pplic atio n that inc ludes the CLI a nd the
GUI.
In Linux
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application enterprise kit:
1. Run the install.s h scri pt of the OneComma nd Mana ger a pplic atio n enterpri se kit.
The install script executes an rpm upgrade (rpm -U *.rpm) to upgrade the installed core kit to an
enterprise kit.
In Solaris SFS
To upgrade from the OneCommand Manager application CLI to the full-featured OneCommand Manager
application enterprise kit:
1. Download the OneCommand Manager application enterprise kit to a temporary directory on your
system.
2. Untar the OneComma nd Manag er ap plication enterprise kit tar file:
tar xvf elxocm-<kit version>.tar
3. Chang e to the newl y create d elxocm -<kit v er sion > di rect ory:
cd ./elxocm-<kit version>/
4. Run the install s cript and fo llow the ins tructions .
./install
In VMware ESX Server
The full-featured OneCommand Manager application enterprise kit is not supported for VMware ESX
Server.
Uninstalling the OneCommand Manager Applica tion
To uninstall the OneCommand Manager application and OneCommand M anager appl ica tion Web
Launch Interface:
The OneCommand Utility User Manual Page 14
In Windows
1. Se lec t Start>Control Panel>Add/Remove Programs.
or
Select Start>Control Panel>Programs and Features>Uninstall a Program.
2. Se lec t E mulex elxo cm-windows-[ver sion] and clic k Remove or Uninstall. Click Yes. The
utilities are removed from the sy stem .
3. Se lec t Emulex Common SAN Management [version] and click Remove or Uninstall. Click
Yes. The Emulex Common SAN Ma nageme nt com ponents are removed fr om the s ystem.
4. Se lec t E m ul ex OCManage r [version] and c lic k Remove or Uninstall. The uninstallation is
complete.
In Solaris SFS
1. Log o n as ‘ root’.
2. Run the OneCo mmand M anager uni nstall sc ript:
/opt/HBAnyware/scripts/uninstall
In Linux
1. Log i n as ‘ro ot’.
2. c d to the elx ocm-< platform>-< versi on> i nstallatio n dir ecto ry.
3. Type:
./uninstall
In VMware
1. Log in as 'root'.
2. Type:
rpm -e elxocmcore-esxNN
Where NN is 35 for an ESX 3.5 system or 40 for an ESX 4.0 system.
Uninstalling the OneCommand Manager Application Web Launch Interface
Only
To uninstall the OneCommand Manager application Web Launch, but leave the OneCommand Manager
application installed:
In Windows:
The OneCommand Utility User Manual Page 15
1. Se lec t Start>Programs>Emulex>OCM anager WebLaunch Uninstall. The following screen
appears:
Figure 1: OneCommand Manager Application Web Launch, Uninstall screen
2. The O neComma nd Mana ger a pplic atio n Web Launch Interfac e is removed. Press any key to
continue.
In Solaris SFS and Linux:
1. Log o n as ‘ root’.
Note: If you installed the OneCommand Manager application Web Launch Interface, you
must uninstall it before uni nstal lin g th e OneCo mman d Man age r ap pl icati on.
2. Ex ecute the uni nstallation sc ript .
• Solari s SFS:
/opt/HBAnyware/wsuninstall
•Linux:
/usr/sbin/hbanyware/wsuninstall
This script stops the OneCommand Manager application Web Launch Interface service daemons (if they
are running) and removes all Web Launch related fil es fr om the h ost.
The OneCommand Utility User Manual Page 16
Starting the OneCommand Manager Application
To start the OneCommand Manager appl ic ation:
In Windows:
1. On the W indows deskt op, selec t Start>All Programs>Emulex>OCManager.
In Solaris SFS and Linux:
1. Log o n as ‘ root’.
2. Run the scr ip t to start the OneComman d Manag er ap plic ation .
• On Solaris SFS:
/opt/HBAnyware/ocmanager
• On Linux :
/usr/sbin/hbanyware/ocmanager
Starting the OneCommand Manager Application Web Launch Interfa ce
After the OneCommand Manager application Web Launch Interface software is ins talled and the Web
Launch server is initialized, you can launch the On eComman d Manag er ap plic ation dir ectly with y our
Web browser.
Note: Only the OneCommand Manager application GUI is exported to the requesting client.
All adapter discove ry and r emo te ma nag ement oper a tions ar e pe rfor me d by
resources running on th e remot e hos t th at serv ed up the GUI compon en t. There fo re ,
the SAN view displaye d by th e GUI is no t from t he cl ien t runn ing the GUI, bu t rat her
from the host from which this GUI was retrieved.
To launch the OneComma nd Mana ger applic atio n with y our Web browser:
1. O pen your Web browser. Linux and Solaris users must log on as ‘r oot’ .
2. En ter the URL of the oc manage r.jnlp file. Make sure that the URL specifies a rem ote serve r
which has the OneCommand Manager application Web Launch Interface software installed and
running.
http://IP_ADDR:PORT_NUM/ocmanager.jnlp
where IP_ADDR is the IP address of the host on which you installed the OneCommand Manager
Web Launch Service, and PORT_NUM is the TCP port number of the listening hosts' Web
server. If the port number is omitted, the default port 80 will be assumed. The standard
OneCommand Manager application user interfac e is d isp laye d.
Managing Files when Running the OneCommand Manager Application Web
Launch Interface
When running the OneCommand Manager appl ica tion Web Launch Interfa ce, all fil es (log fi les , driver
parameter files, firmware files, etc.) are located on the browser launch host, which is not necessarily the
same as the remote host that is specifie d in the Web launc h addres s.
The OneCommand Utility User Manual Page 17
Using the OneCommand Manager Application
Note: To properly view the OneCommand Manager application, ensure your system meets the
following display re qu ir ements:
For Windows systems, the di spl ay resol utio n must be set to 80 0 by 60 0 or bet ter.
For Linux and Solaris sys te ms, the di spl ay reso lut io n must be se t to 1024 by 768 or bett er.
The display must run in 256-color mode or higher. OneCommand Manag er application icons
use 256 colors. If the disp la y is set for 16 col or mode , OneC omma nd Ma nager app lica ti on
icons are not displayed.
The OneCommand Manager Appl icati on Window Elem ent D efinit ions
The OneCommand Manager application window c ontains five basi c compone nts: the menu bar, the
toolbar, the discovery-tree, the property tabs and the status bar.
Figure 2: OneCommand Manager application window
Note: The element you select in the discovery-tree determines whether a menu item or
toolbar icon is active . For ex amp le, if yo u sele ct the loca l host or oth er sy stem hos t,
the Reset Adapter it em on the Ada pt er menu is unav ail ab le. The Reset Ada pter
toolbar button is unava ila bl e as well .
Note: Screenshots in this manual are for illustrative purposes only. Your system information
can vary.
Note: The features displayed by your local OneCommand Manager application interface will
match those of the remote server. When accessing a remote server running an older
version of the OneCommand Manager application, features that are not supported by
the server’s ol der ver sio n of the OneC omm and Mana ger app li catio n ar e unavai la ble .
The OneCommand Utility User Manual Page 18
Note: In some instances, the type of information displayed and available functionality is
determined by the operati ng system in use.
The Menu Bar
The menu bar contains commands that enable you to perfor m a var iety of tasks such as ex iti ng the
OneCommand Manager application, resetting adapters and sorting items in the disc over y-tre e vi ew.
Many of the menu bar commands are also available from the toolb ar.
The Toolbar
The toolbar contains buttons that enable you to refresh the disc overy -tree, re set the sele cted ad apter
and choose how you want to view discovered SAN elem ents in the dis cover y-tree. M any o f the toolb ar
functions are also available from the menu b ar.
Figure 3: Toolbar
The toolbar is visible by default. Use the Toolbar item in the View menu to hide the toolbar. If the item is
checked, the toolbar is visible.
The Toolbar Buttons
The toolbar buttons perform the following tasks:
Discovery Refresh button
• Initiates a discovery refres h cycl e.
Reset button
• Resets the selected adapte r.
The View Buttons on the Toolbar
The View buttons on the toolbar enable you to view SAN elements from the host, fabric, virtual ports, or
by local or remote ad apt er per sp ective . B y def aul t, bot h lo cal and r emote adap te rs are disp layed in
Host view. The OneCommand Manager appl ica tion di spl ays el eme nts in asc end ing or der.
Host View button (default)
• Displays the host system.
Note: Y ou cannot change host names using the OneCommand Manager application; names
must be changed locally on th at system.
• Within each host system , displ ays th e in stalled ad apt er s.
• Displays adapter por ts and the por t numbe rs if ava il abl e.
• If multiple adapters ha ve t he sam e mod el nu mbe r, displays adapter s by th e WWN N.
• If targets are present, displays the WWPN. Multiple adapters can refer to the same target.
• If LUNs are present, displays the LUN number.
• COMSTAR ports are located on the same level in the discover y-tr e e as ini tiat or ports,
meaning that they branch out from adapters. Unlike initiator ports, however, targets do not
branch out from COMSTAR ports.
The OneCommand Utility User Manual Page 19
Fabric View button
• Displays the fabrics in th e SA N wi th t hei r fabr ic ID s.
• Displays the ports under each switc h.
• If targets are present, displ ays each WWP N. Mul ti ple adap te rs can re fe r to th e same
target.
• If LUNs are present, displays each LUN number.
• If the fabric ID is all zeros, no fabric is attached.
Virtual Ports View button
• Displays virtua l ports in the SAN.
Note: The Emulex emlxs driver for Solaris does not support COMSTAR running over virtual
ports, so the Virtu al Ports view only displays initiator ports.
Local HBAs Only button
• Displays only local adapters.
Help button
• Displays the OneCommand Manager application’s on-line help.
The Discovery-Tree
The discovery-tree (left pane) has icons that represent disco vered hos ts, adapters, por ts, virtual por ts,
fabrics, targets and LUNs.
Using the View menu, the OneCommand Manager application allows y ou to contro l the way iSCS I
initiator and target ports are identified in the discovery-tree. The "iSCSI Names" option displays all iSCSI
ports by their iSCSI Qualified Name (IQN). The "iSCSI A li as" option displays each port by its alias.
Figure 4: Discovery-tree
The OneCommand Utility User Manual Page 20
Discovery-Tree Icons
Discovery-tree icons represent the following:
The local host.
Other hosts connected to the sys te m.
A green adapter icon wi th blac k desc ri ptive text re prese nts an onl in e ada pter. Blue text
represents an adapter por t that ha d pr evious ly be en di scov er ed , but cur r ently is not bein g
seen by the discovery engine (service). The adapter is removed from the discovery-tree if it
still is not seen after the u ndiscovered adapter expiration time (default is 1800 seconds, or
30 minutes). If the adap te r is di sco ver ed agai n bef or e the expir at io n ti me, it r eve rts bac k to
normal black text. Se e “Co nf igu ri ng Dis cove ry, CIM Credentials an d TCP /IP Set ting s” on
page 31 for mor e infor ma tio n ab out dis cove ry sett in gs.
A gray adapter icon in di cat es al l ports for th at ad ap te r are no long er bei ng di scover ed .
A red icon indicates all ports for the adapter are offline (link down). Several situations could
cause the adapter to be offline or ina cces sib le:
• The adapter on a local host is not connected to the network, but is available for local
access.
• The adapter on a local host is malf uncti oni ng and in acc essi ble to the lo cal host and the
network.
• The adapter on a local host is busy pe rfor mi ng a local dow nl oad and is temp or aril y
inaccessible to the loc al ho st and th e ne twor k.
The port icon repre sen ts an ada pte r po rt. Newe r ad ap te rs al so di spla y the po rt numb er.
A port icon with a red X ind ica te s the port is dow n. If all dis c over ed po rts ar e do wn, th e
adapter icon c hanges to red.
Note: Multiport adapters ar e repr es ent ed in the dis c ove ry-t r ee wit h separat e por t i con s for
each port. Older multip ort ad apt er models ( fo r exampl e. LP8 000D C, LP 94 02DC or
LP9002DC) are represen te d by se parate ad ap ter ico ns.
The iSCSI icon represen ts an iS CSI PCI fu nct io n instance . iS CSI fu nction s can supp ort up
to sixteen logical ada pter s, w ith ea ch log ica l ad apt er app ea ri ng in the disco ver y- tre e as a
separate child node unde r the r esp ect ive i SCSI f unc ti on. The gre en iSCS I ico n repr es ents
an iSCSI PCI function on-line instance. A black iSCSI icon represents an iSCSI PCI function
port-disabled instance . A red iSC SI ic on r epre s ents an iSC SI P CI fu nct ion lin k down
instance.
The green FCoE icon represents an FCoE PCI function on-line instance. A black FCoE icon
represents an FCoE PCI fu nct ion por t-d isa ble d ins tance . A r ed FCo E ic on repr e sen ts an
FCoE PCI function link down instance.
The NIC icon represents a NIC-Only PCI function instance. A green icon indicates this
function instance is on-lin e, blac k ind ica te s it is disab le d, an d re d in dic ates a lin k dow n
instance.
The Virtual Port icon rep re sen ts a virt ua l port .
The COMSTAR icon represents COMSTAR target mode ports. (Solaris Only) COMSTAR
ports are unique in that a sing le po rt can be shown simul taneo usl y as bo th a ma nagea ble
adapter port and a regular target. When a COMSTAR port is seen as a target, it displays the
Targe t di scov ery -tr ee icon and Target dialog box information.
A COMSTAR icon with a red X indicates the port is down.
The OneCommand Utility User Manual Page 21
The Tar ge t icon re pr ese nts connec tio ns t o ind ivi dual st or age devices .
The LUN icon represents connections to individual disk LUNs.
The Media Exchang er icon represents conections to individual media exchangers. A media
exchanger is a jukebox-li ke de vice that is ca pable of sw appin g var io us media de vic e
instances (e.g. records or CDs) in and ou t.
The Tape LUN icon represents LUNs that are tape devices.
The Tar ge t Cont r oller LU N icon r epre s ents LUN s th at are storag e con tr ol le rs.
The Switch icon repre sen ts conne ction s to t he swit ch .
Expanding or Collapsing the Discovery-Tree View
You can also use the Expand/Collapse feature on the View menu to change the way di sco vered
elements are displayed. By selecting on e of the four levels the di sco ver y-tre e is expanded or coll apsed
to that level. You can choose Hosts/Fabrics (depending on the v iew), HBAs, Por ts and Targets.
The Property Tabs
The property tabs display configuration, statistical and status informa tion for network el ements. The set
of available tabs is context-sensitive, depending on the type of network element or adapter port currently
selected in the discovery-tree.
The Status Bar
The status bar is located near the bottom of the OneCommand Manager application window. The status
bar displays messages about certain OneCommand M anager appl ica tion func tions , su ch as “Di sco very
in progress”.
The status bar is visible by default. Use the Status Bar item in the View menu to hide the status bar.
When checked, the status bar is visible.
Changing Management and Rea d-Only Mod e
During installation, a management and a read-only mod e was s elec ted. If mod ific ation o f these s etting s
after installation was selected, you can choose three ty pes of h ost/ada pter m anagem ent:
• Strictly Local Management - This setting only allows management of adapters on this h ost.
Management of adapters on this host from other hos ts is not allowed.
• Local Management Plus - This setting only allows management of adapters on this host, but
management of adapters on this host from another hos t is poss ibl e.
• Full Management - This setting enables you to manag e adapter s o n this host an d other hosts
that allow it.
If Management Mode was enabled during installation, y ou ca n als o set read- onl y mod e.
• Read-only mode - This setting preve nts certain oper ations fro m being perfo rme d, such as
resetting adapters, updating the adapter or Converge d Enhan ced E thernet (CE E) fir mware
image and changing adapter driver properties and bindings. Dialog box buttons and menus that
pertain to these tasks are completely hidden or disab led.
The OneCommand Utility User Manual Page 22
To change management/r ead- only mode:
Note: You must restart the OneCommand Manager application to see the new management
mode.
In Windows
1. From the File menu, selec t Management Mode. The Management Mode dialog bo x app ears.
Figure 5: Management Mode dialog box
2. Choos e the m anageme nt type a nd read-o nly mode you want.
3. Cli ck OK .
In Solaris SFS
1. Run the followi ng script:
/opt/HBAnyware/set_operating_mode
2. Choos e the m anageme nt type a nd read-o nly mode you want.
In Linux
1. Stop the OneCommand Manager applic ation .
2. Run the followi ng script:
/usr/sbin/hbanyware/set_operating_mode
3. Choose the management type and read-only mode you want. Enter <y> for yes to allow the user
to perform these operations, enter <n> for no if re ad-o nly m ode is desir ed.
The OneCommand Utility User Manual Page 23
Printing Help Information
To print help inform ation:
1. Se lect th e help i nformation you want to print.
2. From the br owser menu sele ct File>P rint.
3. From the Pr int dialog box check Selection.
4. Cli ck OK .
The OneCommand Utility User Manual Page 24
Configuring Discovery
Automatic Fibre Channel Disco very
Adapters that have a physical FC connection to th e sam e SAN are discovered automatically when th e
OneCommand Manager application is launch ed. Ada pters that don't hav e a ph ysi cal FC connec tion to
the SAN where the OneCommand Manager application is l aunc hed c an be disc over ed by sending
management requests to the remote host using TCP/IP.
Note: The OneCommand Manager appl ica tion ca n onl y disc ove r and mana ge remo te
adapters on hosts running the One C omma nd Manag er applica ti on ’s remote
management server. Remote FC capabilities of the OneComma nd Manag er
application are sub jec t to fabri c zoni ng . H osts you wan t to disco ver and m anage
using the OneCommand Manager application must be in the same zone or
discovered and manage d th ro ug h TCP /IP ac cess .
Note: After adding an adapter to a running Windows system (commonly called a hot plug),
click Discovery Ref res h ( ) or restart the OneCommand Ma nag er app lic ati on to
display the new adapter por t in the disc ove ry-t re e. Ho t plu g is on ly su pport ed by the
OneCommand Manager appl ica tion on Win dows pl atfo rms .
Note: VMware ESX Server 3.5 do es not sup ppo r t in-b and mana gem ent or LP2 100 0 serie s
adapters.
Figure 6: Discovery Inf orm a ti on
Remote SAN Management Using TCP/ IP Ac cess Prot ocol
You can disc ov er adapter s on TC P/IP hosts and on h osts configure d to sup port the CIM inter fac e.
Remote SAN management over TCP/IP sends remote manag ement r equests using TCP/IP acc ess
protocol to remote hosts. TCP/IP access enables you to access adapters via their host IP-address or by
the name of the host on which they reside. Since ada pters can exi st on a h ost but n ot be a part of a FC
network, they do not appear during normal FC discove ry. Thus, TCP/IP access enlarges the number of
adapters that can be queried or modified.
The OneCommand Utility User Manual Page 25
Note: In Windows, if you are runn ing a fir ewal l you may nee d to add the One C omma nd
Manager applicati on remo te se rv er to the fi re w all ’s except ion list . T his remo te
server’s path is :
\Program Files\Emulex\Util\Common\rmserver.exe
On a 64-bit host the path is:
\Program Files (x86)\Emulex\Util\Common\rmserver.exe
The principle differences between FC and TCP/IP acc ess are:
• A TCP/IP host with or without an adapter installed does not need to conne ct to a fabric to
manage other hosts.
• A TCP/IP management host can manage all of the adapters in a remote host, not just the ones
connected to the same fabric. FC can only manage adapters connected to the same fabr ic.
• You can manage many more hosts since TCP/IP access is not constrained by the boundaries of
a fabric or zoning.
• True board status (e.g. link down) is available since the FC path is not necessar y to send a
status request to the remote host.
• Adapter security in a TCP/IP envir onmen t is m uch m ore i mpor tant since m any m ore h osts are
available for management and TCP/IP acc es s is not affected by fabr ics or z oning.
• Discovery of hosts in a TCP/IP environme nt is n ot automa tic like FC di sc overy. You must add
the hosts to be managed.
The Hosts File
The TCP/IP discovery portion of the OneCommand Manager application discovery server relies on a file
called the hosts file. This plain text file contains a list of h osts the util ity wi ll atte mpt to disco ver. The
discovery server does not attempt to disc over hos ts over TCP/IP through any other mec hanis ms (e.g.
ping sweeps, broadcasts, etc.).
The hosts file is automatically created or modifi ed when y ou perfor m any of the foll owing o perations :
• Adding a single host from the Add Remote Host window. If the host is discovered, the
OneCommand Manager application adds i ts IP address a nd name to the hos t file.
• Scanning a range or ranges of IP addresses for hosts that can be managed. This is performed in
the Add Remote Hosts window. For each discovered host, the OneCommand Manager
application adds the IP address and name to the hos t file .
• Removing a host from the host file using the Remove Remote Hosts window. For each removed
host, the OneCommand Manager application removes that IP add ress an d name fr om the h ost
file.
Manually Editing the Hosts File
You can open the ho sts file with any tex t edi tor, modify the contents and save the file. The nam e of the
host file is “hbahosts.lst”. Once the file is modified and sav ed, the upd ated fil e is u sed a fter the next
TCP/IP discovery cycle is comple te. If the discov ery s erver i s runni ng, it doe s not ne ed to be r estarted.
To manually edit the hos ts file:
1. Loc ate and o pen the ho sts file.
Windows: The file is located on the system drive in the directory "\Program Files\Emulex\Util" for
32-bit machines or "\Program Files (x8 6)\E mulex\Util " for 64-bit mac hines.
Solaris: The file is located in the directo ry "/opt/HBAny ware".
The OneCommand Utility User Manual Page 26
Linux: The file is located in the dir ector y " /usr /sb in/hban ywar e".
2. Ed it the fil e. G uidel ines for ed iting the file are a s follows:
• Eac h line of the fi le starts with an IP addres s. Fol lowin g the IP ad dress c an be a ny num ber
of tabs or spaces. This is followed by a “#” character, zero or more tabs or spaces and the
name of the host for that IP address. The host name is not requi red for di scover y. Its
purpose is to make the file more reada ble an d is u sed by the O neComm and Man ager
application to display the host name in the Remove Remote Hosts window when the host is
not discovered. However, the discovery server only needs the IP address to dis cover th e
host.
• Each li ne in the file c an be up to 1023 c haracter s, a lthough this is longer than is neede d for
a host IP address and host name. A line longer than this is trun cated, p oss ibly ca usi ng
discovery to not discover some of the h osts.
• Bl ank lines are ignor ed.
3. Sa ve the fi le.
Copying the File
A hosts file on one host can be copied and used on another host. This is us eful when there ar e multi ple
hosts on the same network running the OneCommand Manager appl ic ation. For exam ple, once the
remote hosts are added to the hosts file on one host, you can copy it to oth er ho sts so yo u do not ne ed
to create another hosts file.
Note: Due to the line terminator di fference s betw ee n Win dows and S olari s or Linu x hosts,
the files cannot be shared between Windows hosts and Solari s or Linux hosts.
The OneCommand Utility User Manual Page 27
Adding a Single Host
The OneCommand Manager application enables yo u to spe cify a si ngle TCP /IP hos t to manag e. You
can add a Resource Management Applicati on Progr ammi ng Interface (RMA PI) host o r CIM host us ing
the host name or IP address. If the host is succ essf ully di sc overed i t is ad ded to the h o sts file. If it has
not been discovered over FC already, the host and its adapter ports are added to the discovery-tree.
(Not available in read-only mode.)
Prerequisites
• The OneCommand Manager application mus t be ins talled on the r emote ho st.
Procedure
To add a single h ost:
1. From the Discovery menu, select TCP/IP>Add Host. The Add Remote TCP/IP Host dialog box
appears.
Figure 7: Add Remote TCP/IP Host dialog box
2. En ter the name or the IP a ddre ss of the hos t to be adde d.
Note: Entering the IP address to identify the host avoids possible name resoluti on issues.
3. Confi gure the dis cover y meth od:
• If you want to add the host using default discovery methods , che ck Add using default
credentials and click Add Host. You will receive a message indicating whether the new
host was successfully added.
• If you want to add the new hos t usin g spe cifi c CIM cred entials, c heck Add using spe-
cific CIM credentials and click Add Host. The Add Remote TCP/IP Host di alog b ox
appears with default CIM settings. CIM credentials are most often used when managing
VMware ESX 3i or VMware ES X 4i server s.
The OneCommand Utility User Manual Page 28
Figure 8: Add Remote TCP/IP Host dialog box with CIM Credentials
a. Edit the defaul t CIM se ttings if nec ess ary and c lic k Add Host. You will receive a
message indicating the new host was succes sfully a dded.
Adding a Range of Hosts
Find the TCP/IP-accessed manageable hosts by searching a range of IP addr es ses. The Add Range of
TCP/IP Hosts dialog box enables you to build the initial list of TCP/IP accessed manageable hosts. (Not
available in read-only mode.)
Note: The ranges of IP addresses ar e on ly scanne d ea ch ti me you ope n the Add Re mote
TCP/IP Hosts dialog box and click Start Discover y. The ranges are NOT
automatically scann ed by the disco ver y serve r du ri ng its dis cove ry cycle s.
The OneCommand Utility User Manual Page 29
Figure 9: Add Range of TCP/IP Hosts dialog box
Prerequisites
• The OneCommand Manager application must be installed on all remote hosts.
Procedure
To add a range of remote h osts:
1. From the Discovery menu, s elec t TCP/IP>Add Ra n g e of H o sts. The Add Range o f TCP /IP
Hosts dialog box appears.
2. En ter the complete s tart and end addr ess r ange and cli ck Add. The adde d addr ess ran ge
appears in the dialog box. Add any additional ranges y ou want to s earch.
The OneCommand Utility User Manual Page 30
3. Cli ck Start Discovery. If an address is remotely manageable, it is added to the list of addresses
that the discovery server will attempt to discover. The utility creates a host file if necess ar y, and
checks each address in the range to dete rmine if the host is available and remotely
manageable. The number of addresses (of managea ble hos ts) discover ed is peri odic ally
updated on the dialog box.
Note: The number of addresses does not correspond directly to the number of hosts added
to the discovery-tree.
For example, s ome of the addresses discovered may be for hosts that have already
been discovered over FC. How ever, new adapters can be dis cove red on tho se ho sts
that were not discovered over FC.
Also, a host can have more than one IP addr ess assigned to it. If multiple IP
addresses for a host are di scov er ed dur ing the sear ch , th e hos t will be add ed to the
discovery tree only once.
4. You can save the IP address ranges. Click Save Ranges to File to save the specified range(s)
to a file so that these address ranges appear the nex t time y ou us e the Add Range of T CP /IP
Hosts dialog box.
Removing Hosts
Removing hosts that are no longer discovered i mproves the operatio n of the di sco ver y serv er. For
example, you may want to remove a host when it is removed fr om the ne twork. (Not avail able i n readonly mode.)
To remove hosts:
1. From the Discovery menu, s elec t TCP/IP>R emove Host(s). The Rem ove Hos ts dialog b ox
shows a list of discovered hosts. Any host tha t is n ot cur re ntly d isc ov ered appear s i n red . Clic k
Show Undiscovered Hosts Only to display only currently undi sc over ed ho sts.
2. From the Remove Hosts dialog box, select the hosts you want to remove. You can select all the
displayed hosts by clickin g Select All.
3. Cli ck Remove to rem ove the selected hosts.
Configuring Discovery, CIM Credentials and TCP/IP Settings
Use the OneCommand Manager Applic ation Discove ry Settin gs di alog bo x to c onfigu re several
discovery server parameters. You can define when to start the discovery server, when to refresh FC and
TCP/IP accessed discoveries and when to r emove pr evi ousl y disc overed ada pters that are no l onger
being discovered. You can also define default CIM credentials such as the protocol, user name, port
number, password and name space. For TCP/IP management, you can specify an IP port number,
change an IP port number and enable a port for TCP/IP management.
The OneCommand Utility User Manual Page 31
Figure 10: OneCommand Manager Application Discovery Settings dialog box
To configure d iscove ry setti ngs:
1. From the Discovery menu, select Modify Settings. The Discovery Settings dialog box appears.
2. Defin e the dis cover y proper ties you want.
3. If TC P/IP M anagem ent is enabled, the En able T CP/IP Manag ement c heck box is s elec ted an d
the current port number is displayed in the Port Num ber field. If de sir ed, en ter a different port
number (between 1024 and 65535). Click Defaults to select the Enable TCP/IP Management
checkbox (if unchecked) and set the port number to 23333
.
If the port number or the Enable TCP/IP Management check box is chang ed, a se t of warning
messages may appear before changes are made. Cl ick Yes on the warning message to continue with the change.
Caution: The IP port number must be the sam e fo r al l hosts that are to be managed .
Setting an IP port number for one host to a different value than the other hosts
will make the host unabl e to manage ot he r ho sts over TCP /IP, as well as
make the host unmanageable over TCP/IP from other hosts.
4. If the IP port number is chang ed, the utility restarts the OneCommand Manag er ap plic ation
discovery server and management agent to use the new s etting s. If the s erver s cannot be
stopped and restarted, you are prompted to reboot the host for the new T CP/IP m anagem ent
settings to take effect.
5. If yo u want, edi t the CIM creden tials .
The OneCommand Utility User Manual Page 32
6. Cli ck OK to apply your changes. Click Defaults to return the discovery properties to their default
settings.
Configuring iSCSI Target Discovery
The iSCSI Target Di scover y tab allows you to confi gure iSCS I target disc overy related paramete rs.
Figure 11: iSCSI Target Discovery dialog box
To display th e iSCS I Target Discovery tab:
1. From the dis cover y-tree , sele ct the i SCSI p ort whose di sc over y settings you want to configure.
2. Se lec t the iSCS I Target Discovery tab.
Target Discovery Field Definitions
• Target Portals - The Target Portals table contains all target portals that are queried for targets.
Depending on the SAN setup, the contents of this table may be a subset of the av ail able target
portals, or it could contain the full set of target portals for all iSCSI targets.
• Targets - The Targets table contains all currently discovered targets. Targets in this table come
from one of three possible sources:
• The target was ma nuall y adde d.
• T he target was disc over ed v ia a target portal.
• The target was foun d thro ugh an iSNS s erver query.
The OneCommand Utility User Manual Page 33
Target Discover y bu ttons
• Add Portal - Click to add a target portal. See “Adding Target Portals” on page 34 for more
information.
• Remove Portal - Click to remove a portal. See “Removing a Target Portal” on page 35 for more
information.
• Target Login - Click to login to a selected target. See “Logging into Targets” on p age 36 for more
information.
• Target Session s - Clic k to view ac tiv e sessi ons fo r the selec ted target. See “Viewing Target
Sessions” on page 37 for more information.
• Manually Add Target - Click to manually add an iSCSI target. See “Add ing an i SCSI Target” on
page 36 for more i nform ation.
• Remove T arget - Click to manually remove an iSCSI target. See “Removing Targets” on page 37
for more information.
• Refresh Tar gets - Click to m anual ly for ce a complete rediscovery of the targets, querying all
configured iSNS servers and target portals.
Adding Target Portals
To add a target portal:
1. From the iSCSI Target Discovery dialog box, click Add Portal. The Add Target Portal dialog box
appears.
2. En ter the server IP ad dress an d TCP port number and c lick OK. After success fully addi ng a
target portal, that target portal's targets are discovered and appear in the target list.
Note: Whil e up to 12 8 ta rgets can be found on an iSCSI port, only a max imu m of 64 tar get s
can be discovered this w ay. Therefore, it is possi bl e tha t not al l th e targ et portal's
targets will appear in the target list. However, they can be added manually or
discovered through iS NS.
Specifying Portal Specific Login Options
Normally, the login options for the portal defaults to the options specified on the Initiator Login Options
tab. However, the Advanced Login Options dialog box allows you to modify the portal specific log in
options.
The OneCommand Utility User Manual Page 34
Figure 12: Advanced Login Options dialog box
To configure advanc ed l ogin op tions for a portal:
1. From the iSCSI Target Discovery dialog box, click Add Portal. The Add T arget Portal dialog box
appears.
2. En ter the require d infor mati on and c lick Advanced Login Opt ions. The A dvan ced L ogin
Options dialog box appears.
3. Specify the portal login parameters you want.
4. Cli ck OK .
Removing a Target Portal
To remove a target portal:
1. From the iS CSI Target Discovery dialog box, select the target portal you want to remove in the
Target Portals table.
2. Cli ck Remove Portal.
The OneCommand Utility User Manual Page 35
Logging into Targets
Only connected targets, that is targets that are successfully logged into, are dis play ed in the dis cover ytree. However, the Targets table in the iSCSI Target Discovery dialog box is composed of all discovered
targets regardless of their connection status. The connection status of each target is displayed i n the
'Status' column of the Targets table. Disconnected targets are targets that have not yet been logged into
by the initiator.
Figure 13: Target Login dialog box
To login to a target:
1. From the iS CSI Target Discovery dialog box, select the target from the Targets table.
2. Cli ck Target Login. The Target Login dialog box appears. T he dialog box dis play s the Target
Name and Target Alias of the target. When yo u log i nto a target and reboot th e sy stem, th e
OneConnect adapter automatically logs in to that target after the reboot is c ompl ete.
3. Confi gure Adv ance d Login Options i f you wa nt. See “Specifying Portal Specific Login Options”
on page 34 for more infor mati on.
4. Cli ck OK . If the target was suc cessfu lly logge d into, the target's status in the Targets table will
change to 'Connected'.
Note: If you are logging into a target more than once, or you ar e logging into the same
target from multiple iSCS I po rts, you mus t ha ve multi -pat hin g softwa re instal led to
properly present the target‘s LUN(s) to the operating system.
Adding an iSCSI Target
The iSCSI Target Di scover y di alog box en ables you to manual ly add and login i nto iS CSI targets.
To manually add an iS CSI target:
1. From the iSCSI Target Discovery dialog box, click Manually Add Target. The Add iSCSI Target
dialog box appears.
2. En ter the target iSCSI name, target IP add ress and TCP por t number.
3. Confi gure Adv ance d Login Options i f you wa nt. See “Specifying Portal Specific Login Options”
on page 34 for more infor mati on.
4. Cli ck OK . If the target was succes sfu lly added a nd logg ed into, th e target will appear as
‘Connnected’ in the Targets table.
The OneCommand Utility User Manual Page 36
Removing Targets
To remove a target:
1. Log o ut of all sessi ons for the target yo u want to r emove.
2. From the iS CSI Target Discovery dialog box, select the target you want to remove and clic k
Remove Target.
Note: In cases where the target still exists on the network, the removed target(s) may
reappear as targets are periodically refreshed on the host system. Removing a target
permanently remove s targets fr om th e OneCo mman d Man ager co nf igu rati on only
after the target portal is remov ed f rom the OneC omm and Mana ger con fi gur atio n or
the target portal or target have bee n ph ysic all y re move d from t he ne two rk.
Viewing Target Sessions
The Target Sessions dial og box enables y ou to v iew active ses sions for a c urrently con necte d target.
To view active sessi ons fo r a connected target:
1. From the iSCSI Target Discovery dialog box, select the target whose sessions you want to view
and click Target Sessions. The Target Sessions dialog box appears.
If there are multiple active sessions in pr ogress, use the Session pull-down menu to selec t the
session whose information you want to view. Click Close to close the dialog box.
Logging out of Target Sessions
The Target Sess ions dial og box enabl es you to log out of active sessions for a currently co nnecte d
target.
To logout of active se ssi ons for a connec ted target:
1. From the iS CSI Target Discovery dialog box, select the target whose sessions you wan t to log
out of and click Target Sessions. The Target Sessions dialog box appears.
2. From the Ses sion pul l- down men u, sel ect the ses sio n from which you want to logout.
3. Cli ck Close Session to log out of the session.
Note: If all sessions are logged out, the target is disconnected and removed from t he
discovery-tree.
The OneCommand Utility User Manual Page 37
Figure 14: Target Sessions dialog box
Target Sessions Field Definitions
• Initiator Name - The initiator named used to log into the ses sion.
• Status - The session status (logged in, login in progress, login failed, recover y, unknown).
• ISID - The initiator session identifie r (uniqu e for e ach s ess ion).
• ISID Qualifier - The first two bytes of the ISID (unique fo r each se ss ion) .
• TSIH - The target session identifier handle. A tag generated by an iSCS I target to identify an
iSCSI session with a specific iS CSI ini tiator.
• iSCSI Boot - “Yes” indicates a boot session. Logout is not possible from a boot session.
The OneCommand Utility User Manual Page 38
Session Negotiated Login Options Area
• InitialR2T - The initial request to transmit. When set to Yes, the initiator has to wait for the target
to solicit SCSI data before sending it. When set to No , it allows the i niti ator to send a burs t of
unsolicited FirstBurstLength bytes.
• Immediate Data - When set to Yes, it allows the initiator to append unsolicited data to a
command.
• MaxConnections - The maximum number of connections to targets that are allowed within a
single session.
• MaxOutstandingR2T - The maximum number of outstanding request to transmits (R2T s) per task
within a session, each up to MaxBurstLength bytes .
• FirstBurstLength - The maximum amount of unsolic ited data (in b ytes) the initi ator can s end to
the target during the execution of a single iSCSI comma nd.
• MaxBurstLength - The maximum amount of either unsol ic ited or so lic ited da ta the initiator may
send in a single burst. Any amount of data excee ding thi s value must be explicitly solici ted by
the target. This value should be set to multiple s of PAGESIZE.
• DefaultTime2Wait - The minimum time to wait, in seconds, before the initiator attempts to
reconnect or reassign a connection (or task) that has bee n dro pped after an unexpec ted
connection termination or reset. The initiator and target negotiate to d eterm ine thi s value.
• DefaultTime2Retain - The maximum time, in seconds, to reassign a conn ecti on after the initial
wait that is indicated in DefaultTime2Wait has elapsed. The initiator and target negotiate to
determine this value.
• ErrorRecoveryLevel - The operatio nal Erro rRec ove ryLevel for the s ess ion. 0 in dic ates recov er y
only by session restart. 1 indicates recovery by reissuing commands, data, or status. 2 indicates
connection failure recovery.
• DataPDUInOrder - The order of data protocol data units (PDUs) within a sequence.
• DataSequenceInOrder - The order between sequence s.
Session Statistics Area
• Session Direction - The direction of iS CSI s ess ion. Valid values are InboundSession and
OutboundSession.
• Cmd PDUs - The count of Command PDUs transferred on this sessio n.
• Response PDUs - The count of Response PDUs trans ferred on this s es sion.
• Xmt Data Octets - The count of data octets that were transmitted by the local iSCSI node on this
session.
• Recv Data Octets - The count of data octets that were received by the local iSCSI node on this
session.
• Digest Errors - The count of PDUs which were received on the session and contained header or
data digest errors.
• Connection Timeouts - The count of connections within this session which have been terminated
due to a timeout.
• Session Target Alias - The target alias for the se ssi on.
Connection Information Area
• iSCSI Connection ID - The iSCSI Connection ID ass igned to the c onnec tion.
• Status - The status of the connection. Val id values ar e con nected and unk nown.
• Source IP Address - The source IP address for the c onne ction .
• Source Port - The source TCP port number for th e conn ectio n.
The OneCommand Utility User Manual Page 39
• Destination IP Address - The destination IP a ddress fo r the connec tion .
• Destination Port - The destination TCP p ort nu mber for the conne ctio n.
• Redirected Destination - The redirected IP addre ss fo r the target.
• Redirected Destination Port - The redirected port numb er for the target.
Connection Negotiated Login Options
• Authentication Method - The authentication method used for connection. Valid values are None,
Mutual CHAP and one-way CHAP.
• MaxRecdDataSegmentLength - The maximum data segment length in bytes an initiator or target
can receive in an iSCSI PDU .
• Header Digest - When set to CRC32C, the integrity of an iSCSI PDU's header segments is
protected by a CRC32C checksum.
• Data Digest - When set to CRC32C, the integrity of an iSCSI PDU's data segments is protected
by a CRC32C checksum.
• TCPMSS - The maximum segment size for this conn ectio n. Th e driver us es thi s to determi ne
the size of the data PDU whenever it is required to transmit the entire PDU with a si ngle iSCSI
header.
Viewing Discovery Informatio n
The Discovery Information page contains a general summary of the dis co vered ele ments. The Host,
Fabric or Virtual Port icon, depending upon which view you select, is the root of the discovery-tree, but it
does not represent a specific network element. Expanding it rev eals all h osts, LUNs, targets, adapter
ports and virtual ports that are visible on the SAN.
To view the discov ery infor mation:
1. Cli ck the Hosts, Fabrics or Virt u a l Por t i con at th e root of the dis cov ery- tree. Disc ove red SAN
elements appear in the discovery-tree.
The OneCommand Utility User Manual Page 40
2. Se lec t an elem ent fro m the disco very- tree to lear n mor e abo ut it.
Figure 15: Discovery Information (Virtual Port view selected)
Discovery Information Field Definitions
• Number of Hosts - The total number of discovered host computers. This includes servers,
workstations, personal computers, multipro ces sor sy stem s and clu ster ed co mputer com p lexes.
• Number of Fabrics - The total number of discov ered fabri cs.
• Number of Adapters - The total number of discovere d adapters.
• Number of Adapter Ports - The number of discovered ad apter ports on this hos t that can be
managed by this host.
• Number of Target Por ts - The total number of unique discov ered targets on the SAN. In the
discovery-tree, the same target can appear under more than one a dapter.
• Number of Virtual Ports - The number of discovered virtual por ts on this h ost that c an be
managed by this host. (Only displ ayed if the Virtual Por ts element is sele cted in the di scover y tree.)
Viewing Host Information
There are two tabs that show host information: the Host Information tab and the Host Driver Parameters
tab. The Host Information tab is read-only. The Host Driver Parameters tab enables you to view and
define adapter driver settings for a specific hos t. See “T he Host Driv er Parameter s Tab” on page 78 for
more information about the Host Driver Parameters tab.
To view the Host Information and Host Driver Parameters tabs:
1. Do one of the foll owing:
The OneCommand Utility User Manual Page 41
•From View menu, click Group Adapters by Host Name.
• F rom the toolba r, click Group Adapters by Host Name.
2. Se lec t a host i n the di sco ver y-tre e.
3. Se lec t the Host Information tab or the Host Driver Param eters tab.
The Host Information tab displays information for the sel ected host i ncl uding th e numbe r of ada pters
installed in the selected host, the number of fabrics to whic h it is co nnecte d and s o on.
Figure 16: Host I nf orm a ti on tab
Host Information Field Definitions
• Number of Adapters - The number of adapter s in stalled in the host.
• Number of Adapter Ports - The number of discovered ad apter ports on this hos t that can be
managed by this host.
• Number of VPorts - The number of discovered virtual ports that can be managed by thi s host.
(Not supported on VMware ESX servers being managed through the CIM interface.)
• Number of Fabrics - The number of fabric s to wh ich th is h ost is attached. (No t supported on
VMware ESX servers being managed through th e CIM inter face.)
• Number of Virtual Machines - The number of virtual machines that can be seen by this host. (Not
supported on VMware ESX servers being ma naged thr ough the CIM inte rface.)
• Number of Target Por ts - The number of st orage dev ices se en by th e host.
• Remote Manager Server Version - The version of the OneCommand Manager application
server that is running on the host. If different versions of the OneCommand Manager application
are installed on different hosts in the SAN, those differences appear in this field.
• Operating System - The operating system and v er sio n installed o n the se lect ed host.
• Management IP Address - If the host is disc ove red with FC , the Manag ement IP Addr ess field
displays “Host discovered over Fibre Cha nnel” . If the host has bee n added with TCP/IP access,
the Management IP Address field displa ys the hos t's IP add ress, for example, 1 38.239.82 .131.
"Local Host" is displayed if you sele cted the host y ou ar e actually lau nchi ng fro m.
The OneCommand Utility User Manual Page 42
• CIM Provider Version - If the host is being managed using the CIM interface, the "CIM P rovider
Version" field will display the version of the Emulex CIM provider that is running on the remotely
managed system.
Note: The CIM Provider Version field only appears if the host is managed through the C IM
interface.
Viewing Adapter Information
The adapter information that is displayed depends upon the type o f adapter you s ele ct, Fibr e Channe l,
iSCSI or NIC-Only.
Viewing Fibre Channel Adapter Information
When you select a Fibre Channel adapter from the discovery-tree, the Adapter Information tab contains
general attributes associated with the s elected F ibre Chann el ada pter.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
To view Fibre Channel ada pter information :
1. Se lec t Host, Fabric or Virtual Ports vi ew.
2. Se lec t a Fibre Channel adapter in the d isc ov ery-tree.
Figure 17: Fibre Channel Adapter Information tab
Fibre Channel Adapter Information Field Definitions
• Model - The complete model name of the adap ter.
• Serial Number - The manufacturer's serial n umber for the sel ected adapter.
• Hardware Version - The board Joint Electron Devices Engineering Council identification (JEDEC
ID) ID version for the selected adapter.
• Device ID - The default device ID for the sele cted ad apter. (Not supported on VMware ESX
servers being managed through the CIM interface.)
• Adapter Temperatu re - If the adap ter's te mperature is n ot avai labl e, “Not Suppor ted” is
displayed. (Not supported on VMware ESX s ervers be ing managed through the CIM interface.)
If supported by the adapter, this field displays the adapter's temperature and one of the following
temperature-related status messages:
• Norm al: The ada pter’s temperature is within normal ope rational r ange.
The OneCommand Utility User Manual Page 43
• Ex ceeded oper ation al r ange - Crit ica l: The adapte r’s temperature is beyond normal
operational range. If the temperature continues to inc rease, the ad apter shuts down. You
must determine the cause of the temperature prob lem an d fix i t imme diatel y. Check for
system cooling issues. Common causes of system cooling issues include clogged air filters,
inoperable fans and air conditioning problems that ca use h igh amb ient ai r tempera tures.
• Ex ceeded oper ation al range - Adap ter stopped: T he tem per ature has r eached c ritical lim it,
forcing the adapter to shut down. Y ou must determine the cause of the temperature problem
and fix it before resuming operation. Check fo r s ystem co oling iss ues . Common c auses of
system cooling issues incl ude cl ogged a ir filter s, inoper able fa ns an d air cond itioni ng
problems that cause high ambient air temper atures.
After the system overheating issue is resolved and the adapter has cooled down, reboot the
system or, if the system supports hot swapping, cycle the power of the adapter slot.
Viewing iSCSI Adapter Information
When you select an iSCSI adapter from the discovery-tree, the Adapter Information tab contains general
attributes associated with the selected iSCS I adapter.
Note: No iSCSI i n fo rmat i on is p ro vid ed b y t he CI M pro v i de r o n any v e rsio n of VM wa re ESX.
To view general iSCSI adapte r inform ation:
1. Se lec t Host view.
2. Se lec t an iSCS I adapte r in the discov ery- tree.
Figure 18: iSCSI A dap te r In forma ti o n tab
iSCSI Adapter Information Field Definitions
• Model - The model of the selected adapter.
• Serial Number - The serial number of the selec ted ada pter.
• Active Firmware Version - The version of the firmware running on the selected adapter.
The OneCommand Utility User Manual Page 44
• Firmware State - The condition of the firmware.
• BIOS Version - The version of the BIOS in use.
• Boot Code Version - The version of the boot code in use.
Viewing NIC-Only Adapter Information
When you select a NIC-Only adapter from the discovery-tree, the adapter information is identical to that
displayed for iSCSI and FCoE adapters.
Note: No NIC information is displayed by any CIM provider on any version of VMware ESX.
To view general NIC-Only adap ter inform ation:
1. Se lec t Host view.
2. Se lec t a NIC-Only adapter in th e dis covery-tree.
Viewing Port Information
The Port Information tab contains detailed information associ ated with th e selected adapter por t. The
Port information that is displayed depends upon the type of ad apter you s elect, F ibre Channel , FCo E,
iSCSI or NIC-Only.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
Viewing Fibre Channel Port Information
When you select a Fibre Channel adapter from the d isc ove ry-tree, the P ort Info rmation tab contains
general attributes associated with the s elected F ibre Chann el ada pter.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
To view Fibre Channel Port i nformation:
1. Se lec t Host or Fabric view.
2. Se lec t a Fibre Channel port i n the di sco ver y-tre e.
The OneCommand Utility User Manual Page 45
3. Se lec t the Port Info rmatio n tab.
Figure 19: Fibre Ch ann el Po r t In fo rm a tio n tab
Port Information Field Definitions
Port Attributes Area Field Definitions
• Port WWN - The Port World Wide Name of the adapter.
• Node WWN - The Node World Wide Name of the selected adapter.
• Fabric Name or Host Name - The Fabric Na me field is dis play ed in Ho st vi ew. This is a 64-bit
worldwide unique identifier assigned to the fabr ic . The Host Name is displayed in Fabric view.
The host name is the name of the host containing the adap ter. (Not supported on VMware ESX
servers being managed through the CIM interface.)
• Boot Version - The version of boot code installed on the selected adapter port. If the boot code is
disabled, the field displays ”Disabled ”.
• Port FC ID - The Fibre Channel ID for the selected adapter port.
• Driver Version - The version of the driver installed for the adapter.
• Driver Name - The executable file image name fo r the driv er as it appears in the Emulex driver
download package.
• Firmware Version - The version of Emulex firmware currently active on th e adapter por t.
• Discovered Ports - The number of mapped and unmapped ports found during discovery by the
Emulex adapter driver. The mapped ports are targets and the unmapped ports are non-targets
such as switches or adapters.
• Port Type - The current operational mode of the selected adapter ’s port.
The OneCommand Utility User Manual Page 46
• OS Device Name - The platform-specific name by which the s elect ed ada pter is known to the
operating system. (Not supported on VM ware ESX servers being managed through the CIM
interface.)
• Symbolic Node Name - The FC name used to regis ter the dr iver with th e name s er ver.
• Supported Class of Service - A frame delivery scheme exhibiting a set of delivery characteristics
and attributes. There are three classes of s ervic e.
• Clas s 1 prov ides a dedicated c onne ction between a pair o f ports with confirmed del iv ery or
notification of non-delivery.
• Clas s 2 prov ides a frame swi tched ser vice with confi rme d deliver y or noti ficati on of non -
delivery.
• Class 3 provides a frame switched service similar to Class 2 but without notification of frame
delivery or non-delivery.
• Supported FC4 Types - A 256-bit (8-word) map of the FC-4 protocol types supported by the port
containing the selected adapter.
Port Status Area Field Definitions
• Link Status - The status of the link on the selected adapter port.
• Port Speed - The current port speed of the selected adapter port.
Loop Map Table Defin itions
• The loop map shows the different ports present in the loop, and is presen t only if the po rt
(adapter) is operating in loop mode. The simplest example would be to connect a JBOD directly
to an adapter. When this is done, the port type is a private loop, and the loop map has an entry
for the adapter, and one entry for each of the disks in the JBOD. (Not supported on VMware ESX
servers being managed through the CIM interface. Not supported for COMSTAR ports.)
Port Information Buttons
• Enable\Disable Port - Click to enable or disable the selected Fibre Channel port. See “Enabling
and Disabling Fibre Channel Ports” on page 104 for more information.
Viewing FCoE Port Information
When you select an FCoE adapter from the dis cover y-tree, th e Por t Information tab contains genera l
attributes associated with the selected FCoE adapter.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
To view FCoE Port infor matio n:
1. Se lec t Host or Fabric view.
2. Se lec t an FCo E port in the disc ov ery-tree.
The OneCommand Utility User Manual Page 47
3. Se lec t the Port Info rmatio n tab.
Figure 20: FCoE Por t In fo rm a tio n tab
Port Information Field Definitions
Port Attributes Area Field Definitions
• Port WWN - The Port World Wide Name of the adapter.
• Node WWN - The Node World Wide Name of the selected adapter.
• Fabric Name or Host Name - The Fabric Na me field is dis play ed in Ho st vi ew. This is a 64-bit
worldwide unique identifier assigned to the fabr ic . The Host Name is displayed in Fabric view.
The host name is the name of the host containing the adap ter. (Not supported on VMware ESX
servers being managed through the CIM interface.)
• Boot Version - The version of boot code installed on the selected adapter port. If the boot code is
disabled, the field displays ”Disabled ”.
• Port FC ID - The FCoE ID for the selected adapter port.
• PCI Function - The PCI funtion number assigned by the s ystem.
• Driver Version - The version of the driver installed for the adapter.
• Driver Name - The executable file image name fo r the driv er as it appears in the Emulex driver
download package.
• Firmware Version - The version of Emulex firmware currently active on th e adapter por t.
• Discovered Ports - The number of mapped and unmapped ports found during discovery by the
Emulex adapter driver. The mapped ports are targets and the unmapped ports are non-targets
such as switches or adapters.
• Port Type - The current operational mode of the selected adapter ’s port.
The OneCommand Utility User Manual Page 48
• OS Device Name - The platform-specific name by which the s elect ed ada pter is known to the
operating system. (Not supported on VM ware ESX servers being managed through the CIM
interface.)
• Symbolic Node Name - The FC name used to regis ter the dr iver with th e name s er ver.
• Supported Class of Service - A frame delivery scheme exhibiting a set of delivery characteristics
and attributes. There are three classes of s ervic e.
• Clas s 1 prov ides a dedicated c onne ction between a pair o f ports with confirmed del iv ery or
notification of non-delivery.
• Clas s 2 prov ides a frame swi tched ser vice with confi rme d deliver y or noti ficati on of non -
delivery.
• Class 3 provides a frame switched service similar to Class 2 but without notification of frame
delivery or non-delivery.
• Supported FC4 Types - A 256-bit (8-word) map of the FC-4 protocol types supported by the port
containing the selected adapter.
Port Status Area Field Definitions
• Link Status - The status of the link on the selected adapter port.
• Port Speed - The current port speed of the selected adapter port.
• Bandwidth Limit - The QoS bandwidth restriction on the port.
Viewing iSCSI Port Information
When you select an iSCSI adapter from the discov ery-tree, the iSCS I Port Info tab contains general
attributes associated with the selected iSCS I adapter. You can also change the iSCSI port’s TCP/IP
configuration and enable or disable the port. See “ Modifying TC P/IP iS CSI Por t Confi guration” on
page 100 and “Enabl ing an d Disa blin g Phy sical P or ts (OneConnect A dapters O nly )” on page 104 for
more information.
Note: No iSCSI port information is displayed by the CIM provider on any version of VMware
ESX.
To view iSCSI port inform ation:
1. Se lec t Host or Fabric view.
2. Se lec t an iSCS I port in the di sc ove ry-tree.
The OneCommand Utility User Manual Page 49
3. Se lec t the iSCSI Port Info tab.
Figure 21: iSCSI P ort Inf orm a ti on tab
Port Information Field Definitions
• Driver Name - The iSCSI driver file nam e.
• Driver Version - The iSCSI driver version.
• MAC Address - The iSCSI MAC address currentl y assig ned to the po rt.
• Perm MAC Address - The original facto ry-assi gned i SCSI MAC addr ess .
• Device ID - The PCI device ID assigned to the i SCSI fu nctio n.
• Vendor ID - The PCI vendor ID assigned to the iSCSI function.
• PCI Function - The PCI function number assig ned to the iSCSI fu nctio n.
• LDTO - (Link Down Time Out) The amount of time in seconds that the iSCSI driver delays
reporting a link down error to the operating system .
• Max MTU - Maximum transmission unit for iSCSI traffic.
• Default ETO - The default extended timeout.
• Max CDB Length - Maximum SCSI com mand de scrip tor block si ze.
• SubSys Device ID - The PCI subsystem ID assigned to the iSCSI function .
• SubSys Vendor ID - The PCI subsystem vendor ID assigned to the iSCSI function.
TCP/IP Configuration Area Field Definitions
• DHCP Enabled - The DHCP authentication status of the selected port.
• IP Address - The iSCSI initiator IP addr ess.
The OneCommand Utility User Manual Page 50
• Subnet Mask - The iSCSI initiator subnet mas k.
• Gateway Address - The iSCSI initiator g ateway a ddress.
• VLAN Enabled - The VLAN enabled state for the iSCSI inter face.
• VLAN ID - The VLAN identifier to use 0-4094 (only valid when VLAN is enabled). 0 indicates the
VLAN is disabled.
• VLAN Priority - The VLAN priority for the iSCSI interface .
Network Info Area Field Definitions
• Link Status - The status of the link on the selected adapter port.
• Max Port Speed - The maximum port speed of which the selected port is ca pable.
Port Information Buttons (Not availabl e in r ead-only mode.)
• Modify - Enables you to change TCP/IP settings for the selected port. Y ou can change the port’s
VLAN tag, priority, IP address and more. See “Modifying TCP/IP iSCS I Por t Configu ration” on
page 100 for mo re infor mation.
Viewing NIC Port Information
When you select a NIC port from the discovery-tree , the NIC Por t Info tab contains general a ttributes
associated with the selected NIC port.
Note: NIC ports do not exist only on NIC-On ly ad apt ers. A NIC port ca n als o exis t on an
iSCSI or FCoE adapter.
To view general NIC port informatio n:
1. Se lec t Host or Virt ual Por t s view.
2. Se lec t a NIC-Only adapter in th e dis covery-tree.
3. Se lec t the NIC Port Info tab .
Figure 22: NIC Port Info tab
The OneCommand Utility User Manual Page 51
NIC Port Info Field Definitions
• Driver Name - The NIC driver file name.
• Driver Version - The NIC driver version.
• MAC Address - The NIC MAC address currently assign ed to the po rt.
• Perm MAC Address - The original factory ass igne d NIC MAC add ress.
• Device ID - The PCI device ID assigned to the NIC fun ctio n.
• Subsys Device ID - The PCI subsystem ID assig ned to the NIC func tion .
• Vendor ID - The PCI vendor ID assigned to the NIC function.
• Subsys Vendor ID - The PCI subsystem vendor ID assigned to the NIC function.
• PCI Function - The PCI function number assigned to the NIC function.
• Max MTU - The maximum transmission u n it for iSCS I traffic.
• Current MTU - The current transmission u nit for iSCSI traffic.
• Interface Name - The interface assigned to this port by the ho st oper atin g sy stem.
• Link Status - The status of the link on the selected adapter port.
• Bandwidth Limit - The QoS bandwidth restriction on the port.
• PXE Boot Checkbox - (Preboot Execution Env ironment) Chec k the bo x to ena ble P XE b oot on
the selected port.
Note: PXE Boot is only available on ports with PCI function 0 or 1.
Viewing Physical Port Information
The Physical Port Info tab contains a general summarization of the PCI fun ctio ns und er tha t physic al
port and the current physical port status.
It also allows you to enable or disable the physic al po rt. Se e “Enabli ng and Di sabl ing P hysic al P orts
(OneConnect Adapters Only)” on page 104 for more information.
To view physical por t informatio n:
1. Se lec t Host view.
2. Se lec t an iSCS I, FCoE or NIC adapter por t in the d iscove ry-tr ee.
The OneCommand Utility User Manual Page 52
3. Se lec t the Physical P o rt Info tab.
Figure 23: Physical Por t In fo tab
Viewing Port Statistics
The Statistics tab provides cumulative totals for various error events and statistics on the port. Some
statistics are cleared when the adapter is reset. The Port Statistics information that is displayed depends
upon the type of adapter you select, Fibre Channe l, iS CSI or NIC-Only.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
Viewing Fibre Channel Port Statistics
When you select a Fibre Channel adapter fr om the d iscove ry-tr ee, the Po rt Statistics tab contains
statistics associated with the selected Fibre Chann el por t.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
To view Fibre Channel por t statistics:
1. Se lec t Host or Fabric view.
2. Se lec t a Fibre Channel adapter por t in the di scover y -tree.
The OneCommand Utility User Manual Page 53
3. Cli ck the Statistics tab.
Figure 24: Statistics tab
Port Statistics Field Definitions
• Tx Frames - FC frames transmitted by this adapte r port.
• Tx Words - FC words transmitted by this adapter port.
• Tx KB Count - FC kilobytes transm itted by this adapter port.
• Tx Sequences - FC sequences tra nsmitted by this adapter por t.
• LIP count - The number of loop initialization pr im itiv e (LIP) e vents that have occ urred fo r the
port. This field is not supported if the topology is not ar bitrated l oop. Loop initi ali zatio n cons ists
of the following:
• Temporarily suspending loop operations.
• Deter mini ng whether loo p capable ports are connec ted to the l oop.
• As sig ning A L_PA IDs.
• Pr oviding notification of configuration changes and l oop fai lures.
• Pl acin g loop p orts in the monitor ing state.
• Error Frames - The number of frames received with cyclic redundancy check (CRC) errors.
• Link Failures - The number of time s the link has fai led. A link failure is a possible cause of a
timeout.
• Loss of Signal - The number of times the s ignal was lost.
• Invalid Tx Words - The total number of invalid words transmitte d by thi s adapter port.
The OneCommand Utility User Manual Page 54
• Ex Count Orig - The number of FC exchanges origin ating on this port. (Not supported on
VMware ESX servers being managed through th e CIM inter face.)
• Active XRIs - The number of active excha nge r esourc e indi cators. (N ot su pported on V Mware
based ESX platforms using the CIM interface.)
• Received P_BSY - The number of FC po rt-busy li nk respo n se frames re ceived.
• Link Transitions - The number of times the SLI port sent a link atte ntion c ondi tion.
• Elastic Buf Overruns - The number of times the link i nter face h as had its elasti c buffer overrun.
• Rx Frames - The number of FC frames received by this adapter port.
• Rx Words - The number of FC words received by this adapter por t.
• Rx KB Count - The received kilobyte count b y this adap ter po rt.
• Rx Sequences - The number of FC sequences received by this adapter port. (N ot supported on
VMware ESX servers being managed through th e CIM inter face.)
• NOS count - The number of NOS events that have occur red on the s witc hed fabr ic. (Not
currently supported for the SCSIport Minipor t and Storport Miniport drivers, nor is i t supp orted
for arbitrated loop.)
• Dumped Frames - The number of frames that were los t due to a l ack of hos t buffers available .
(Not currently supported for the SCSIport Miniport driver, the Storport Miniport driver or the
driver for Solaris.)
• Loss of Sync - The number of times los s o f syn chr oniza tio n has o ccu rred.
• Prim Seq Prot Errs - The primitive sequenc e protoc ol er ror co unt. This counte r is inc re mented
whenever there is any type of protocol error.
• Invalid CRCs - The number of frames received that contain CRC failures.
• Ex Count Resp - The number of FC exchange respons es ma de by th is po rt. (Not sup porte d on
VMware ESX servers being managed through th e CIM inter face.)
• Active RPIs - The number of remote port indicator s. (Not s upported on V Mware ESX serve rs
being managed through the CIM interface.)
• Receive F_BSY - The number of FC p ort-bus y li nk re sp onse frames r ecei ved.
• Primitive Seq Timeouts - The number of times a primitive sequence event timed out. (Not
supported on VMware ESX servers being ma naged thr ough the CIM inte rface.)
• Arbitration Timeouts - The number of times the arbitration loop has timed out. Lar ge c ounts
could indicate a malfunction somewher e in the l oop or heav y us age of th e loop. (N ot suppor ted
on VMware ESX servers being managed th rough the CIM in terfac e.)
If you selected a COMSTAR port, the following information is also displayed:
• SCSI Write I/O Count - The number of SCSI write I/O requests received.
• SCSI Write KB Count - The total number of kilobytes written.
• Total SCSI I/O Count - The number of SCSI I/O reques ts received.
• No Receive Buffer Count - The number of SCSI I/O requests that were dropped.
• Queue Depth Overflow Count - The number of SCSI I/O requests receiv ed after a QFULL
condition.
• Dropped SCSI I/O Count - The number of dropped SCSI I/O operations .
• Aborted SCSI I/O Count - The number of aborted SCSI I/O oper ation s.
• Outstanding SCSI I/O Count - The number of SCSI I/O requests currently pending.
• SCSI Read I/O Count - The number of SCSI Read I/O requests received.
• SCSI Read KB Count - The total number of kilobytes read.
The OneCommand Utility User Manual Page 55
• SCSI Status Errors - The number of SCSI status errors sent to the initiator.
• SCSI Queue Full Errors - The number of QFULL error s sent to the i nitia tor.
• SCSI Sense Errors - The number of times se nse da ta was sent to the initiator.
• SCSI Residual Over - The number of residual o verru ns re turned to the i nitia tor.
• SCSI Residual Under - The number of residual underrun s returned to the i nitia tor.
Viewing iSCSI Statistics
When you select an iSCSI initiator from the di sc ove ry -tree, the iSCSI Statistics tab contains statistics
associated with the selected initiator.
Note: No iSCSI information is displayed when using the CIM provider for VMware ESX.
To view iSCSI port statistics:
1. Se lec t Host view.
2. Se lec t an iSCS I ini tiator node i n the dis co very- tree.
3. Cli ck the iSCS I Statistics tab.
Figure 25: iSCSI Statistics tab
iSCSI Statistics Field Definitions
• Node Roles - The node role for this iSCSI i nitia tor.
• Portal Count - The number of rows in the iscsiPortaltypeTable which are currently associated
with this iSCSI instance.
• Node Count - The number of rows in the iscsiNodetypeTable which are currently associated with
this iSCSI instance.
The OneCommand Utility User Manual Page 56
• Session Count -The number of rows in the iscsiSessiontypeTable which are currently associated
with this iSCSI instance.
• Session Failure Count - The number of times a s ess ion be longi ng to this por t has failed.
• Last Session Failure Type - The type of failure encountered in the last se ss ion fai lure.
• Last Session Remote Node Name - The iSCSI name of the remote node from the failed session.
• Session Digest Errors - The count of sessions whic h failed due to receipt o f a PDU c ontaining
header or data digest errors.
• Session Connection Timeout - The count of sessions which failed due to a sequence exceeding
a time limit.
• Session Format Errors - The count of sessions which failed due to receipt of an iSCSI PDU that
contained a format error.
• Login Failures - The number of times a log in from this ini tiator failed.
• Last Failure Time - The timestamp of the most recent failure of a login attempt from this initiator.
A value of 0 indicates that no failures h ave occurred.
• Last Target Failure Name - The UTF-8 string name of the target that most recently failed a login
request from this initiator.
• Last Target Failure Address - The In terne t Network Addr ess of the target that most r ec ently
failed.
• Login Accept Responses - The count of Log in Res pons e PDUs rec eiv ed by this i nitiator tha t
were accepted.
• Login Other Fail Responses - The count of Login Respons e PDUs r eceive d by thi s ini tiator with
any status code not counted by the other objects.
• Login Redirect Responses - The count of Login Res pons e PDUs rec eived by the ini tiator with
status class Redirection.
• Login Authentication Fail Response s - The count o f Login Re spons e PDUs with s tatus class
0x201 Authentication Failed recei ved by thi s init iator.
• Login Authentication Failures - The number of times the initiator has aborted a login because the
target could not be authenticated.
• Login Negotiation Failures - The number of times the initiator has aborted a login because
parameter negotiation with the target failed.
• Logout Normals - The count of Logout Command PDUs gener ated by this initi ator with r eason
code normal.
• Logout Others - The count of Logout Command PDUs generated by this initiator with any status
code other than normal.
• Port Row Status - This field allows entries to be dynamically added and removed from this table
via SNMP.
• Portal Role - The role of a portal. A portal can operate in either one of two roles as a target portal
and/or an initiator portal.
• Portal Protocol - The portal's transport protocol.
• Portal Tag - The portal’s aggregation tag when the por tal is use d as an initi ator.
The OneCommand Utility User Manual Page 57
Viewing Virtual Port Information (FC and FCoE Ada pters Only )
Use the Virtual Ports tab to view information about virtual ports and their assoc iated targets and LUNs.
To view virtual port in forma tion:
1. Do one of the foll owing:
•From the View menu, se lec t Group Adapters by Virtual Port.
• F rom the toolba r, click Group Adapters by Virtual Port.
Figure 26: Virtual Ports Information
Virtual Port Information Field Definitions
• Number of Hosts - The total number of hosts discovered in the SAN.
• Number of Fabrics - The total number of fabrics dis covere d in the SAN.
• Number of Adapters - The total number of adapters disc ov ered in the S AN.
• Number of Adapter Ports - The total number of adapter ports discovered in the SA N.
• Number of Target Por ts - The total number o f target ports discovered in the S AN.
• Number of Virtual Ports - The total number of virtual ports discovered in the SAN.
Viewing Fabric Information
The Discovery Information tab contains information about the selec ted fabr ic.
To view fabric dis cover y in formation:
1. Do one of the foll owing:
•From the View menu, se lec t Group Adapters by Fabric Address.
• F rom the toolba r, click Group Adapters by Fabric Address.
The OneCommand Utility User Manual Page 58
The Discovery Information tab shows information about the fabr ic.
Figure 27: Fabric D isco v e ry Inf orma ti on
Discovery Information Field Definitions
• Number of Hosts - The number of hosts discovered or seen by this h ost on th e sel ected fabri c.
• Number of Fabrics - The number fabric s id entifi ed dur ing di sc overy.
• Number of Adapters - The number of adapter s di sco vered by this host on the se lecte d fabr ic.
• Number of Adapter Ports - The number of discovered ad apter ports on this hos t that can be
managed by this host.
• Number of Target Por ts - The number of s torage dev ices se en by th is h ost on th e sel ected
fabric.
The OneCommand Utility User Manual Page 59
Viewing Transceiver Information
The Transceiver Data tab enables you to view transceiver information such as vendor na me, se rial
number, part number and so on. If the adapter does not support this feature the fields display N/A.
The Transceiver information that is displayed depends upon the type of ad apter you s elec t, Fibr e
Channel, iSCSI or NIC-Only.
Note: Not supported on systems using CIM pr ovi der v1 .2.1 on ESX 3i .
Viewing Fibre Channel Transceiver Information
When you select a Fibre Channel adapter from the d iscove ry-tr ee, the Transceiver Data tab contains
information associated with the selected Fibre Channel por t.
To view Fibre Channel tr ansceiv er informatio n:
1. Se lec t Host or Fabric view.
2. In the d iscove ry -tree, selec t the F ibre Channel port whose tr anscei ver infor mati on yo u want to
view.
3. Se lec t the Transceiver Data tab.
Figure 28: Fibre Channel Transceiver Data tab
Transceiver Information Field Definitions
Module Attributes Area
• Vendor - The name of the vendor.
The OneCommand Utility User Manual Page 60
• Identifier/Type - The identifier value that specifies the physical dev ic e desc ribed by the s erial
information.
• Ext. Identifier - Additional information ab out the transc eiv er.
• Connector - The external optical or electrical cable connector provided as the media interface .
• Wavelength - The nominal transmitter output wavelength at room temperature.
• OUI - The vendor’s Organizational ly Unique Id entifie r. It is also known as the IEEE Company
Identifier for the vendor.
• Date - The vendor ’s date code in the MM/DD/YY for mat.
• Serial Number - The serial number provi ded by the ve ndor.
• Part Number - The part number provided by the SFP v endor.
• Revision - The vendor revi sio n lev el.
Diagnostic Data Area
• Temperature - The i nternally meas ured modul e tempe rature.
• Supply Voltage - The internally measured supply voltage in the transceiv er.
• TX Bias Current - The internally measured T X bias c urrent.
• TX Output Power - The measured TX output power
• RX Input Power - The measured RX input power.
Viewing OneConnect Adapter Transceiver Information
When you select an OneConnect adapter p ort from the d iscove ry -tree, the Transceiver Data tab
contains information associated with the sel ected p ort.
To view iSCSI transcei ver informati on:
1. Se lec t Host or Fabric view.
Note: iSCSI and NIC-Only adapters do not appear in Fabric view.
2. In the d iscove ry -tree, selec t the por t whose transcei ver info rmation y ou want to view.
3. Se lec t the Transceiver Data tab.
The OneCommand Utility User Manual Page 61
Figure 29: iSCSI Transceiver Da ta tab
Transceiver Information Field Definitions
Module Attributes Area
• Vendor - The name of the vendor.
• Identifier/Type - The identifier value that specifies the physical dev ic e desc ribed by the s erial
information.
• Ext. Identifier - Additional information ab out the transc eiv er.
• Connector - The external optical or electrical cable connector provided as the media interface .
• Wavelength - The nominal transmitter output wavelength at room temperature.
• OUI - The vendor’s Organizational ly Unique Id entifie r. It is also known as the IEEE Company
Identifier for the vendor.
• Date - The vendor ’s date code in the MM/DD/YY for mat.
• Serial Number - The serial number provi ded by the ve ndor.
• Part Number - The part number provided by the SFP v endor.
• Revision - The vendor revi sio n lev el.
Diagnostic Data Area
• Temperature - The i nternally meas ured modul e tempe rature.
• Supply Voltage - The internally measured supply voltage in the transceiv er.
• TX Bias Current - The internally measured T X bias c urrent.
• TX Output Power - The measured TX output power.
The OneCommand Utility User Manual Page 62
• RX Input Power - The measured RX input power.
Viewing Vital Product Data (VPD)
The VPD tab displays vital product data (if available) for the sele cted FC or FCo E adap ter po rt such as
the product name, part number, serial number and so on.
Note: Not supported on systems using CIM pr ovi der v1 .2.1 on ESX 3i .
To view VPD information:
1. Se lec t Host or Fabric view.
2. In the d iscove ry tree, sele ct the po rt or FCo E function who se V PD informati on you want to v iew.
3. Se lec t the VP D ta b.
Figure 30: VPD tab
VPD Table Definitions
• Product Name - Product information about the sel ected a dapter por t.
• PN (Part Number) - The adapter's part number.
• SN (Serial Number) - The adapter's serial number.
•VO - Vendor unique data. “V” indicates a vendor-specific field. An adapter may have none, one
or more of these fields defined. Valid values for this field are “VO” (the letter “O”, not the number
zero) and “Vx” (where “x” is a number).
Note: Some adapters may show additional VPD information such as EC (EC level) and MN
(manufacturer ID).
Viewing Maintenance/Firmware Informat ion
Use the Maintenance or Firmware tabs to view firmware infor mation and upda te fir mware. For Fibr e
Channel adapters, you can also configure boot and ch ange W WPN a nd WW NN informatio n for th e
selected adapter port. (Not available in read- only mode.)
The OneCommand Utility User Manual Page 63
The maintenance/firmware information that is dis play ed dep ends u pon the type of adapter you select,
Fibre Channel, iSCSI or NIC-Only.
Note: Not all inf or m at io n i s di sp l ay e d o n s yst em s us i ng CIM provider v1.2.1 on ESX 3i. and
CIM provider v2.0 on ESX 4i.
Viewing Fibre Channel Maintenance Information
To view Fibre Channel firmwar e in forma tion:
1. Se lec t Host or Fabric view.
2. Se lec t a Fibre Channel adapter por t in the di scover y -tree.
3. Se lec t the Mainte nance tab.
Figure 31: Maintenance tab
Maintenance Tab Field Definitions
Firmware A re a
• Current Version - The Emulex firmware version number for this model of adapter.
• Initial Load - The firmware version stub r esp onsib le for ins talling SLI code into its proper slot.
(Not available on VMware ESX servers be ing ma naged thr ough th e CIM interfac e.)
• SLI-2 Name - The name of the SLI-2 firmware overlay. (Not available on VMware ESX servers
being managed through the CIM interface.)
• Kernel Version - The version of the firmware responsible for starting the driver. (Not available on
VMware ESX servers being managed through th e CIM inter face.)
The OneCommand Utility User Manual Page 64
• Operational Name - The name of the operational fir mware for the sel ected adapter. (Not
available on VMware ESX servers being managed throu gh the CIM i nterfa ce.)
• SLI-1 Name - The name of the SLI-1 firmware overlay. (Not available on VMware ESX servers
being managed through the CIM interface.)
• SLI-3 Name - The name of the SLI-3 firmware overlay. (Not available on VMware ESX servers
being managed through the CIM interface.)
• Adapter Boot Version - Displays one of the following:
• The sel ected adapter port's boot c ode v ersion if boot c ode is pr esent.
• “Disabl ed” if the boo t code is di sabl ed.
• “Not Pre sent” if boo t code i s no t loaded . If boot co de is not load ed, the En able A dapter
boot checkbox is not visible and you c annot c onfigure the s ele cted po rt to boo t from
SAN.
• Enable adapter boot checkbox - Check this box if you want the adapter to load and execute boot
code during system startup. Click Configure Boot to configure boot from SAN. See
“Configuring Boot from SAN” on page 134 for more information. (N ot ava ilabl e in read- onl y
mode.)
Note: Enabling adapter boot on ly cau ses the adap te r t o loa d the boo t cod e an d exe cut e it
during system startup. It does not mean that the adapter will boot from SAN. To boot
from SAN, the boot type must be enabled to boot from SAN. Do this in the Boot from
SAN configuratio n wind ow for eac h boo t ty pe. In addi ti on, th e BIOS must be
configured to boot from SAN.
WWN Management Area
Note: Not supported on COMSTAR and VMware ESX servers bein g man aged th ro ug h th e
CIM interface.
Current
• WWPN - The World Wide Port Name for the selected adapter port.
• WWNN - The World Wide Node Name for the selected adapter port.
Pending Changes
• WWPN - Works in conjunction with the Change WWN button. Dis play s th e World Wide Port
Name you assigned for the selected adapter por t, but the s ystem mus t be rebooted for the se
changes to take effect and appear under the “Current” listing. See “Configuring Boot from SAN”
on page 1 34 for more informatio n.
• WWNN - Works in conjunction with the Change WWN button. Disp lay s the World Wide Node
Name you assigned for the selected adapter por t, but the s ystem mus t be rebooted for the se
changes to take effect and appear under the “Current” listing. See “Configuring Boot from SAN”
on page 1 34 for more informatio n.
Maintenance Tab Buttons (Not a vai lable in read- only mode.)
• Update Firmware - Click to update firmware on the sele cted p ort. S ee “Updating A dapter
Firmware” on page 120 for more information.
• Configure Boot - Check Enable adapter boo t and click Config ur e B oo t to con figur e boot from
SAN. See “Configuring Boot from SAN” on page 134 for more information . (Not avail able on
VMware ESX servers being managed through th e CIM inter face.)
The OneCommand Utility User Manual Page 65
• Change WWN - Click to change the selected ada pter port's World Wide Node Name o r World
Wide Port Name. See “Changing World Wide Name Configuration (FC and F CoE P orts Only)”
on page 1 08 for more informatio n. (Not a vail able on VMware ESX s er vers bei ng man aged
through the CIM interface.)
Viewing FCoE Maintenance Information
To view FCoE firmware information:
1. Se lec t Host or Fabric view.
2. Se lec t an FCo E adap ter port in the dis cover y- tree.
3. Se lec t the Mainte nance tab.
Figure 32: FCoE Maintenance tab
Maintenance Tab Field Definitions
Firmware A re a
• Firmware Version on Flash - Specifies the firmware version stored on the adapter’s non-volatile
storage. When the system restarts, this version becom es the a ctiv e fir mware ve rs ion.
• Service Processor FW Version - Specifies the firmware version that is currently operatio nal on
the adapter.
• Active Firmware Version - The version of firmware running on the selected adapter.
• ULP FW Name - The firmware version running o n the (U pper Layer Protoc ol) proces sors wi thin
the ASIC.
The OneCommand Utility User Manual Page 66
WWN Management Area
Note: Not supported on COMSTAR and VMware ESX servers bein g man aged th ro ug h th e
CIM interface.
Current
• WWPN - The World Wide Port Name for the selected adapter port.
• WWNN - The World Wide Node Name for the selected adapter port.
Pending Changes
• WWPN - Works in conjunction with the Change WWN button. Dis play s th e World Wide Port
Name you assigned for the selected adapter por t, but the s ystem mus t be rebooted for the se
changes to take effect and appear under the “Current” listing. See “Configuring Boot from SAN”
on page 1 34 for more informatio n.
• WWNN - Works in conjunction with the Change WWN button. Disp lay s the World Wide Node
Name you assigned for the selected adapter por t, but the s ystem mus t be rebooted for the se
changes to take effect and appear under the “Current” listing. See “Configuring Boot from SAN”
on page 1 34 for more informatio n.
Maintenance Tab Buttons (Not a vai lable in read- only mode.)
• Configure Boot - Click Configure Boot to configure boot from SAN. See “Configuring Boot from
SAN” on page 134 for more information. (Not available on VMware ESX servers being managed
through the CIM interface.)
• Change WWN - Click to change the selected ada pter port's World Wide Node Name o r World
Wide Port Name. See “Changing World Wide Name Configuration (FC and F CoE P orts Only)”
on page 1 08 for more informatio n. (Not a vail able on VMware ESX s er vers bei ng man aged
through the CIM interface.)
Viewing OneConnect Adapter Firmware Information
Unlike Fibre Channel adapters, OneConnect adapter fir mwar e is maintained on a n adapter -spec ific
instead of port-specific basis.
To view iSCSI firmware information:
1. Se lec t Host view.
Note: iSCSI and NIC-Only adapters do not appe ar in Fa br ic view.
2. Se lec t a One Connec t adapter in the disc ov ery-tree.
The OneCommand Utility User Manual Page 67
3. Se lec t the Firmware tab.
Figure 33: iSCSI Firm ware Tab
Firmware Tab Field Definitions
• Active Firmware Version - The firmware version currently being used by the ad apter.
• Flash Firmware Version - The flash firmware version currently being used b y the ad apter.
• Boot Code Version - The boot code version currently being used by the adapter.
• BIOS Version - The version of the BIOS currently being used by the adapter.
Firmware Tab Buttons ( Not av aila ble i n read-on ly m ode.)
• Update Firmware - Click to update firmware on the sele cted a dapter. See “Updating Adapter
Firmware” on page 120 for more information.
Viewing Target Info rmati on
Target Information co ntains informatio n specific to the selected storage device . The type of i nfor mation
that is displayed depends on the type of adapte r you sel ect, F ibre Cha nnel or iS CSI.
The OneCommand Utility User Manual Page 68
Viewing Fibre Channel Target Information
When you select a target associated with a Fibre Channel adapter from the di sc overy- tree, the Target
Information tab displays information associated with that target.
To view Fibre Channel target information:
1. Se lec t Host, Fabric or Virt ual Port view.
2. In the d iscove ry -tree, selec t the F ibre Channel target whose infor mation y ou want to vie w. The
Target Information tab appear s.
Figure 34: Target Information tab
Target Information Field Definitions
Mapping Information Area
• FC ID - The FC ID for the target; assigned automatically in the firmware.
• SCSI Bus Number - The SCSI bus number to which th e target is mapped.
• SCSI Target Number - The target's ide ntifier on the SCSI bus.
• Node WWN - A unique 64-bit number, in hexadecimal, for the target (N_PORT or NL_PORT).
• Port WWN - A unique 64-bit number, in hexadecimal, for the fabric (F_PORT or Switched Fabric
Loop Port
[FL_PORT]).
• OS Device Name - The operating system dev ice name.
Note: See “Masking and Unmasking LUNs (Windows)” on page 129 for more information on
LUN Masking.
Viewing iSCSI Target Information
When you select a target associated with a iSCSI adapte r from the disc ove ry-tree, the Target
Information tab displays information associated with that target.
To view iSCSI target information:
1. Se lec t Host view.
The OneCommand Utility User Manual Page 69
2. In the d iscove ry -tree, s elect the iS CSI target whose infor matio n you wa nt to vi ew. The Target
Information tab appears.
Figure 35: iSCSI Target Information tab
Target Information Field Definitions
• Target iSCSI Name - The iSCS I name assi gned to the target.
• Target Alias - The iSCSI alias assigned to the target. This is assigned at the target portal, not by
the OneCommand Manager application.
• ETO - (Extended Timeout Value) The ETO for the target. The driver will ensure that I/Os are not
“timed out” until this time has expired (from the time the target stoppe d respond ing) . You can
change this value if you want.
Target Portal Information Area
• IP Address - The IP address through whic h the i nitia tor commun ica tes with the target.
• Port - The TCP port through which the initiator c ommuni cates with the target.
• Group Tag - The tag of the group for which s ub-grou ps must be refreshed.
Target Information Bu ttons
• Sessions - Click to view the currently acti ve s ession s for the target. See “Viewing Target
Sessions” on page 37 for more information.
• Apply - Click to save and apply your ETO changes.
The OneCommand Utility User Manual Page 70
Viewing LUN Information
The LUN Information tab contains information about the selected logical unit number (LUN). The type of
information that is displayed depends on the ty pe of adap ter you se lec t, Fibre Cha nnel o r iSCSI.
Note: LUNs that are associated with a man ag eab le COMSTAR port do not appear in the
discovery-tree and can no t be configu r ed using the OneComma nd Manag er
application or hbac md utili ti es. To view the LUNs using the OneCommand Manager
application, you must vie w th e COMS TAR port as a target.
Note: LUNs are discovered each ti me you clic k on th e “+ ” sym bol next to a tar get in the
discovery-tree. If an added LUN is not appearing below the target, click the “-” symbol
next to the target to coll apse th e LU N node s and the n cli ck the “+” to expand the
LUNs again. The new LUN shou ld be disp la yed.
Note: On Linux systems, to make LUNs that are newly add ed to a stor age ar ra y appear on
the host, the followi ng scr ip t mus t run fr o m the comman d she ll :
/usr/sbin/lpfc/lun_scan all
This is prevents you from hav ing to rebo ot . If th e host mach ine is re boo te d afte r t he
LUN is added to the target ar r ay, you do not need to run th e scr ipt .
Viewing Fibre Channel LUN Information
When you select a LUN associated with a Fibre Chann el adap ter from the d isc ove ry-tree, the LUN tab
displays information associa ted with tha t LUN.
To view the LUN informatio n:
1. Se lec t Host, Fabric or Vi rtual P ort view.
2. From the dis cover y-tree , sele ct a Fibr e Chan nel port.
The OneCommand Utility User Manual Page 71
3. Se lect th e LUN whos e informatio n you wa nt to view. The LUN Information tab appears.
Figure 36: Fibre C h annel LUN Informati on tab
The OneCommand Utility User Manual Page 72
Fibre Channel LUN Information Field Definitions
Vendor Product Information Area
• Vendor Name - The name of the vendor of the LUN.
• Product ID - The vendor-specific ID for the LUN.
• Revision - The vendor-specifi c revi sio n number for the LUN.
Mapping Information Area
• FCP LUN - The FC identifier used by the adapter to map to the SCSI O S LUN.
• SCSI OS LUN - The SCSI identifier used by the OS to map to the sp eci fic LUN.
• OS Device Name - The name assigned by the OS to the L UN.
LUN CapacityArea
Note: LUN capacity information is only pr ov ide d when the LUN is a mass-sto r age (di sk)
device. Other devices like tapes and scan ner s, etc. do no t di splay capaci ty.
• Capacity - The capacity of the LUN, in megabytes.
• Block Size - The length of a logical unit bl ock in bytes .
LUN Masking Area
• Current Mask Status - Possible states are masked or unmasked.
Viewing iSCSI LUN Information
When you select a LUN associated with an iSCSI ad apter from th e discov ery-tree, the LUN Information
tab displays information associated with that LUN.
To view the LUN informatio n:
1. Se lec t Host view.
2. From the dis covery- tree , sele ct the iSCSI L U N whose i nformation y ou want to view. The LUN
Information tab appears.
Figure 37: iSCSI LU N In fo rm at ion tab
The OneCommand Utility User Manual Page 73
iSCSI LUN Information Field Definitions
• Vendor Name - The name of the vendor of the LUN.
• Model Number - The vendor ’s model number for the LUN.
• LUN Name - The name of the LUN. (Available only on ESX platforms.)
• Serial Number - The vendor ’s serial number for the LUN.
• Capacity - The capacity of the LUN, in megabytes.
• Block Size - The length of a logical unit bl ock in bytes .
Viewing Fibre Channel Target Mapping (Windows and Solaris SFS)
The Target Mapping tab enables you to view current target mapping and to set up persistent binding.
Note: On Solaris SFS systems persistent binding is not supported.
Note: Target Ma ppi ng tab is not av ail able on COMS TAR ports.
To view target mapping:
1. Se lec t Host or Fabric view.
2. In the d iscove ry -tree, selec t the adapte r port whos e target mapping infor mati on yo u want to
view.
3. Se lec t the Target Mapping tab.
Figure 38: Target Mapping tab
The OneCommand Utility User Manual Page 74
Target Mapping Field Definitions
Current Settings Area
• Active Bind Type - WWPN, WWNN, or a destination identifier (D_ID).
• Automapping - The current state of SCSI device automap ping: enabled (default) or disabled.
• Auto-Persistent Binding - The current state of the Auto-Persistent binding service. (Not available
on VMware ESX servers being managed th rough the CIM in terfac e.)
Current Mappings Area
• This table lists current mapping information for the se lected adapter port.
Persistent Binding Configuration Area
• This table lists persistent binding information fo r the sele cted ad apter port. (Not av aila ble on
VMware ESX servers being managed through th e CIM inter face.)
Display Mode Radio Buttons
• Show WWPN, Show WWNN or Show D_ID options enable you to choose how to display
information in the Persistent Binding Configuration table.
Target Mapping Buttons
• Refresh - Click to refresh the Target Mapping tab.
• Change Settings - Click to enable or di sabl e automapping , choos e a bi nd typ e and ena ble or
disable LUN mapping and unmasking. (Not availa ble on V Mwar e ES X se rvers being managed
through the CIM interface.)
• Add Binding - Click to add a persi stent b indi ng.
• Bind New Target - Click to add a target that d oes no t appear in the Persis tent Bindin g table.
• Remove - Click to remove the selected bi nding.
• Remove All Bindings - Click to r emo ve al l per si stent bindings that are displayed.
Viewing Target Map ping ( Linux and VMwa re ES X)
Use this tab to view target mapping. The Target Mapping tab is read-only.
Note: Persistent binding is not supported by the Linux 2.6 kernel, the Emulex 8.2 version of the driver for Linux
or by VMware ESX Server.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i and
CIM provider v2.0 on ESX 4i.
To view target mapping:
1. Se lec t Host or Fabric view.
2. Select the adapter port in the discovery-tree whose target mapping information you want to view.
3. Se lec t the Target Mapping tab.
Target Mapping Field Definitions
Current Settings Area
• Active Bind Type - N/A
• Automapping - N/A
The OneCommand Utility User Manual Page 75
Current Mappings Area
• This table lists current mapping information for the se lected adapter.
Persistent Binding Configuration Area
•N/A
Display Mode Radio Buttons
•N/A
Target Mapping Buttons
•N/A
Viewing iSCSI and NIC PCI Registers
The PCI Registers tab contains PCI information about the selected NIC or iSCS I func tion. The ty pe of
information that is displayed depends on the type of func tion y ou selec t, Fibre Ch annel, i SCSI, or NIC only. See “Viewing the PCI Registers” on page 146 for Fibre Channel PCI register information .
Viewing iSCSI PCI Registers
The iSCSI PCI Registers tab displays base PCI regis ter s.
Figure 39: iSCSI P CI Re g isters tab
To view iSCSI PCI registers:
1. From the dis cover y-tree , sele ct the i SCSI function whose PCI information you want to view.
2. Se lec t the iSCSI PC I Registers tab.
The OneCommand Utility User Manual Page 76
Viewing NIC PCI Registers
The NIC PCI Registers tab displays base PCI registers.
Figure 40: iSCSI P CI Re g isters tab
To view NIC PCI registers:
1. From the dis cover y-tree , sele ct the NIC fun ction whose P CI informati on yo u want to vi ew.
2. Se lec t the NIC PCI Registers tab.
The OneCommand Utility User Manual Page 77
Managing Ada pter s
This section describes the various adapter management functions you can perform using OneCommand
Manager application.
Configuring the Fibre Channel or FC oE Ad apter Driv er
The OneCommand Manager application d isplays av ailab le driv er parameters along with thei r defaults
and maximum and minimum settings . A des cripti on of the s elec ted parameter is als o pro vided. T his
section contains information you should be aware of when wor king with dr iv er parameters. For a m ore
detailed description of specific driver parameters, refer to the appr opriate Em ulex driver User Manual.
(Not available in read-only mode.)
Note: This section only applies to FC and FcoE adapters. It does not apply to NIC-Only and
iSCSI adapters.
Note: In Solaris SFS and Linux, you can also specify par ameters when loading the driver
manually. (Not available in read-only mod e. ) Ref er to th e ap propr i ate drive r man ual
for instructions .
Activation Requirements
A parameter has one of the following activation requi rements:
• Dynamic - The change takes effect while the system is r unning.
• Reset - Requires an adapter reset from the utility before the c hange takes e ffect.
• Reboot - Requires reboot of the entire machine before the change takes effect. In this case, you
are prompted to perform a reboot when you exit the utili ty.
The Host Driver Parameters Tab
The Host Driver Parameters tab enables you to view and edit the adapter driv er parameter settings
contained in a specific host. The host driver parameters are global v alues and apply to all adapters in
that host unless they are overridden by parameters assigne d to a sp eci fic a dapter using the ada pter
Driver Parameters tab. For each parameter, the tab shows the current value, the range of acceptable
values, the default value, and whether the parameter is dynami c. A dynam ic parame ter allows the
change to take effect without resetting the adapter or rebooting the system.
For information on changing parameters for a single adap ter, see “Setting Driver Parameters” on
page 80. For infor mati on on c hanging parameters for the host, se e “S etting Driv er Para meter s for Al l
Adapters in a Host” on page 82.
Note: If there are no discovered FC or FCoE ada pt ers, the entir e Host Drive r P arame te rs
tab is grayed-out. This occurs because there are no adapters to which the host driver
parameters apply.
The OneCommand Utility User Manual Page 78
Figure 41: Host Driver Parameters tab
Host Driver Parameters Tab Field Definitions
• Installed Driver Type - The current driver installed on this host. If there is more than one dri ver
type installed, the Installed Driver Types menu shows a list of all driver types and driver versions
that are installed on the adapters in the host.
• Adapter Parameter table - A list of adapter driver parameters a nd their cu rr ent va lues.
Modify Adapter Parameter Area
• Adapter-specific information is d ispl aye d in thi s area. T his can in clude v alue, r ange, d efault,
activation requirements and description.
Driver Parameters Tab B uttons (Not av ail able in re ad-only mode.)
• Restore - If you changed driver parameters, but did n ot cl ick Apply and you want to re store the
parameters to their last saved values, click Restore.
• Defaults - Click to reset all driver parameter values to their d efault (out- of-box) values.
Note: Driver parameter values are not supported on hosts being managed through the CIM
interface.
• Apply - Click to apply any driver parameter changes. If y ou changed a dri ver parameter that is
not dynamic, you may need to reset the adapter por t or cr eate a new ramdi sk and reboot the
system.
The OneCommand Utility User Manual Page 79
Setting Driver Parameters
The Driver Parameters tab for adapters and hosts enable you to modify driver parameters for a specific
adapter or all adapters in a host.
For example, if you select a host in the discovery-tree, you can globally change the parameters for all
adapters in that host. If you select an adapter port in the discovery-tree, you can change the
lpfc_use_adisc , lpfc_log_verbose and the lpfc_nodev_tmo parameters for only that adapter.
For each parameter, the Driver Parameters tabs show the current value, the range of acceptable values,
the default value, and the activation requirement. You can also restore parameters to their default settings.
You can apply driver parameters for one a dapter to other adapters in the sys tem using the Dr iv er
Parameters tab, thereby simplifying multiple adapter co nfiguration . See “ Crea ting a B atch M ode Dr ive r
Parameters File” on page 84 for more information.
Note: The Linux 2.6 kernel only suppo rts set ti ng some of the driv er param ete rs for
individual adapter s. Some dr ive r paramet er s mus t be ap pl ied to al l ada pt ers
contained in the host. See the Emulex Driver for Linux User Manual for more detail.
Note: For all compatible Linux versions : If you change driver parameters using the
OneCommand Manager appl icati on or hbacmd util it ies and yo u want the se cha nges
to be permanent and persi st ac ross syst em rebo ots, you must cre ate a ne w ramd isk
image. The ramdisk image is use d when the kernel is initialized during system
startup, and loads the LPF C driv er wi th the up da te d dr ive r paramet er s.
To create a new ramdisk y ou c an use th e LPFC driver's l p fc-install s cr i pt . Re f er to the
“Creating a New Ramdisk” sect io n of the E mul ex Dri ver for Lin ux Us er Man ual for
instructions.
Note: For VMware ESX 3.5 and VMw are ES X 4.0: I f you chan ge driv er parame ters us ing
the OneCommand Manager ap pl ica ti on or hba cmd ut il ities and you want these
changes to be pe rmanent and persist across system reboots, you must create a new
ram disk image. The ram di sk imag e is us ed when the kernel is ini ti ali zed durin g
system startup and loads the LP FC drive r wit h the up dat ed driv er parame ter s.
Setting Driver Parameters for a Single Adapter
To change the driver parameters for a single adapter:
1. Se lec t Host or Fabric view.
2. In the d iscove ry -tree, selec t the adapte r port whos e parameters you wis h to ch ange.
3. Select the Driver Parameters tab. The parameter values for the selected adapter are displayed.
The OneCommand Utility User Manual Page 80
Figure 42: Driver Parameters tab - Adapter Selected
4. In the Driver Parameters tab, click the parameter that you want to change. A desc ri ption of th e
parameter appears on the right side of the tab.
5. En ter a n ew value in the Value field in the same hexadecimal or decimal for mat as the current
value or select a value from the drop-down menu. If you enter a value and the current value is in
hexadecimal format, it is prefaced by “0x” (for exampl e, 0x2d ). You can enter a new
hexadecimal value without the “0x”. For example, if you enter ff10, this value is interpreted and
displayed as “0xff10”.
6. If yo u want the c hange to be temporar y ( causing the parameter to rever t to its last p erma nent
setting when the system is rebooted), c heck the M ake ch ange temporary bo x. This option is
available only for dynamic parameters.
7. If yo u are making c hanges to multi ple parameters, and y ou want al l the c hanges to be
temporary, check the Make all changes temporary box. This setting overrides the setting of the
Make change temporary box. Only dynamic parameters can be made tempora ry.
8. Cli ck Apply.
Restoring All Parameters to Their Earlier Values
If you changed parameters, but did not click Apply and you want to restore the parameters to thei r last
saved values, click Restore.
Resetting All D efa ult Values
To reset all parameter value s to thei r default ( factory ) values , click Defaults.
The OneCommand Utility User Manual Page 81
Setting an Adapter Parameter Value to the Host Adapter Parameter Value
To set an adapter parameter value to the co rresp onding host paramete r value:
1. Se lec t Host or Fabric view.
2. In the d iscove ry -tree, selec t the adapte r port.
3. Se lec t the Driver P aramet ers ta b.
4. Cli ck Globals. All parameter values are no w the sam e as th e globa l, or host, value s.
5. To apply the global values, click Apply.
Saving Adapter Driver Parameters to a File
To save a desire d adapter parameter con figur ation c lick Save. To apply your configuration changes,
click Apply.
Note: OneCommand Manager application Web Launch Interface driver parameters files are
saved on the host that th e brow se r was la unc hed from no t th e hos t IP spe cif ied in
browser.
Each definition is saved in a comma -del imit ed file with the followin g form at:
<parameter-name>=<parameter-value>
The file is saved in the Emule x Repositor y d irector y.
In Windows: \Program Files\Emulex\Util\Em ulex Reposi tor y or
\Program Files (x64)\Emulex\Util\Em ulex Repos itor y for any IA64/x 64 sy ste ms
In Linux: /usr/sbin/hbanyware/RMRepository
In VMware ESX: /etc/cim/emulex/RMRepos itor y
In Solaris SFS: /opt/HBAnyware/RMRepository
The OneCommand Manager application can then use the Batc h Driver Par ameter Update functi on to
apply these saved settings to any or all compatible ada pters on the S AN.
Note: Host driver parameters and persistent binding settings cannot be saved.
Setting Driver Par ame ters for A ll Ada pte rs in a Host
To change the driver parameters for al l adapte rs ins talled in a host:
1. Do one of the foll owing:
•From the View menu, cl ic k Group Adapters by Host Name.
• F rom the toolba r, click Group Adapters by Host Name.
2. In the d iscovery-tree, click the host whose adapter driv er parameters you want to change.
3. Se lec t the Host Driver Parameters tab. If there are adapters with different driver types
installed, the Installed Driver Types menu shows a l is t of all d river types and dr iv er ver sions
that are installed. Select the driver whose parameters you want to change. T his menu does not
appear if all the adapters are using the same dri ver.
4. In the Host Driver Parameters tab, click the parameter that you want to change. A description of
the parameter appears on the right side of the tab.
The OneCommand Utility User Manual Page 82
Figure 43: Host Driver Parameters tab - Host Selected
5. En ter a n ew value in the Value field in decimal or hexadecimal format, depending on how the
current value is presented. If the value i s in hexadeci mal format, i t is pr efac ed by “0x ” (for
example -”0x2d”).
6. To make a change temporary (the parameter to revert to its last permanent setting when the
system is rebooted), check Make changes temporary. This option is available only for dynamic
parameters.
7. To make changes to multiple parameters, check Make all changes temporary. Only dynamic
parameters can be made temporary.
8. Cli ck Apply.
Changing Non-dynamic Parameter Values (Linux 8.2)
To change non-dynam ic param eter va lue s for Linux ve rsion 8.2:
1. Nav igate to the /usr /sb in/OneComma nd dir ec tory and r un the scr ipts to stop the One Command
Manager application processes. Type:
./stop_ocmanager
2. Stop all I/O to LPFC attached devices .
3. Unlo ad the LP FC d river. Type:
modprobe -r lpfc
4. Relo ad the dr iver. Type:
modprobe lpfc
The OneCommand Utility User Manual Page 83
5. If DHCHAP authenticati on is currently e mploy ed on th is machine, start up the Emul ex Fibre
Channel authentication service. Type:
/etc/init.d/fcauthd start
6. Start the elxhbamgr service (remote serv ice). Type:
./start_ocmanager
The OneCommand Manager application discovery service starts automatically when you launch
the application.
Note: If DHCHAP authentication is currently employed on Emulex adapters on this
machine, you must type "/etc/init.d/fcauthd start" to restart the
authentication daemon.
If the machine has the OneCommand Manager appl ic ation Web Launch Interfa ce installed, the
RMI services must be restarted. Type:
./start_weblaunch
Note: For changes to persist after a reboot, you must create a new ramdisk image. Refer to
the Emulex Driver for Lin ux User Manual for more infor mation.
Changing Non-dynamic Parameter Values (VMware ESX)
To change non-dynam ic param eter values:
1. Nav igate to the /usr /sb in/hban yware dir ecto ry and r un the s cripts to stop the OneCommand
Manager application processes. Type:
./stop_ocmanager
2. Stop all I/O to LPFC attached devices .
3. For V Mware ES X 3.5 r un the fo llowi ng com mand:
esxcfg-boot -b
For VMware ESX 4.0 run the following command:
esxcfg-boot --sched-rdbuild
4. Reboo t the sy stem .
Creating a Batch Mode Driver Parameters File
You can apply driver parameters for one a dapter to other adapters in the sys tem using the Dr iv er
Parameters tab. When you define parameters for an adapter, you create a .dpv file. The .dpv file
contains parameters for that adapter. After you create the .dpv file, the OneCommand Manager
application enables you to assign the .dpv file parameters to multipl e adapter s in the s ystem. ( Not
available in read-only mode.)
Note: Not supported for ES X 3.5 U2 systems.
To create the .dpv file:
1. Se lec t Host or Fabric view.
2. Se lec t the adapter por t whose parameters y ou want to app ly to o ther a dapters fr om the
discovery-tree.
3. Se lec t the Driver P aramet ers ta b.
4. Se t the dr iver parameters.
5. After yo u define the parameters for the s elec ted adap ter, click Apply.
The OneCommand Utility User Manual Page 84
6. Cli ck Save. The Save Driver Parameters dialog box appears. Y ou can save the file to a different
directory or change its name.
Figure 44: Save Driver Parameters dialog box
7. Use the two radio buttons to choose the type of parameters to save. You can save all
parameters or only those parameters whose current values differ from their corre spond ing
default values.
A list of the saved parameters and their current va lues show i n the Sa ved P arameter s box.
8. Cli ck Save .
Assigning Batch Mode Parameters
Note: Not supported on VMware ESX 3.5 version s prio r to Up date 4 an d VMw a re ES X 3i
Update 4.
To assign batch mode parameters to adap ters:
1. From the Batch m enu, s elect Update Driver Parameters. (You do not need to select any
discovery-tree elements at this time.)
2. Wh en the B atch Dr iver P arameter Update di alog bo x app ears, cl ick Browse.
3. The Driver Parameter File Selection dialog box appears. Select the file you want to use and click
OK. A dialog box appears notifying you that the OneCommand M anager appl ica tion i s
searching for compatible adapters.
Once compatible adapters are found, the Driver Parameter Fi le field of the Batc h Driver Parameter Update dialog box displays the sele cte d file's path. The “Suppor ted Mo dels ” text fiel d dis plays a list of all adapter models that are compatible with the selected file. The set of compatible
adapters appears in the dialog box’s discovery-tr ee.
The OneCommand Utility User Manual Page 85
Checkboxes next to the host and adapter entries are used to select or deselect an entry. Checking an adapter selects or removes that adapte r; check ing a host remov es o r s elec ts all elig ible
adapters for that host.
Figure 45: Bat c h Dri ver Par am ete rs Upd a te di alo g box for Wind ows
4. Mak e yo ur se lections and c lic k Sta r t Updat e . The OneCommand Manager Application Batch
Driver Parameter Update dialog box sho ws the c urrent s tatus of the update. W hen the update
completes, a final summary shows th e numbe r of ada pters that wer e su cc ess fully pr oces sed ,
and the number of adapters for which one or more parameter updates fail ed.
5. If yo u want, cl ic k Save Log File to save a repor t of the up date.
The OneCommand Utility User Manual Page 86
Configuring CEE (Converged En hanc ed Et herne t) Par amet ers
Configuring CEE/FCoE-Specific Parameters (LP21000 Series Adapters Only)
The CEE tab allows you to view and configure the CEE- spe cifi c parameters for the s ele cted po rt. The
CEE tab only appears if you select an LP21000 series adapter from the di sco ver y-tre e.
Note: LP21000 and LP21002 adapters ar e not supported for VMware ESX 3.5.
• When DCBX is present, the Current Values are received from the switch and can only be
changed by configuring the switch. Changing the Con figur ed Values save the values to the
adapter, but they will not be used.
• When DCBX is NOT present, the Current Values reflect the values being used by the adapter.
Changes to Configured Values take effect immediately and are copied to the Current Values
column.
To view and configure CEE /FCoE parameters for Fibr e Channel adapter s:
1. From the dis cover y-tree , sele ct a Fibr e Chan nel CEE adapte r (such as an LP21 000) .
2. Se lec t the CEE/FCoE tab.
3. Mak e any setti ng ch anges you wan t.
4. Cli ck Apply Changes.
Figure 46: CEE/FCoE tab, Configuration area
CEE/FCoE Tab Field Definitions
Converged Enhanced Ethernet Area Field Defini tions
• UIF Port Type - Select between Access and Trunk port types using the menu. The DCBX Sync
column indicates if the feature parameter exchange with the switch was successful. “Y es” means
it was successful. “No” means it was not s ucc essful. T he Cur rent Value column indicates the
current setting for the value.
• Pause Type - Select the Ethernet flow control type. Select between standard P AUSE flow control
and Per Priority based PAUSE flow control. Per Priority based flow control means the Eth erne t
network is seen as 8 virtual lanes (a.k.a. “ Priorities ”) of tr affic rather than one. Poss ibl e dr op
The OneCommand Utility User Manual Page 87
down values are Standard and Per Priority. The DCBX Sync column indicates if the featur e
parameter exchange with the switch was successful. “Yes” means it was successful. “No” means
it was not successful. The Current Value column indicates the current setting for the valu e.
• PFC Priority Map - A series of eight c hec kboxes tha t can on ly b e sel ected if the Pa use Type is
set to “Per Priority”. Selected values co rrespo nd to the fl ow contr ol p rio rities b eing us ed by the
board. The value of the FCoE Priority m ust always be in clud ed among the PFC Priority Map
values. Select a number of values fr om 1 to 8 . Poss ibl e va lues are 0 to 7.
Priority Area Field Definitions
• DCBX Sync - Indicates if the feature parameter exchange with the switch was successful. “Yes”
means it was successful. “No” means i t was not s ucc es sful.
• FCoE Priority - The available values for the FCoE Priority parameter. Possible drop down values
are 0 to 7.
CEE/FCoE Tab Buttons
• Update Firmware - Enables you to update CEE firmware on the selected adapter. See “Updating
CEE Firmware for a Single Adapter (LP21000 Ser ies Adap ters On ly) ” on page 123 for more
information.
• Defaults - Returns the dialog box parameters to their factory setti ngs.
• Apply Changes - Applies any changes made und er the Configur ed Value column. If DCBX is
present on the attached fabric switch, these changes a re s ave d in non -volatil e mem ory, but not
loaded. If DCBX is not present, changes made in the Configur ed Value column may or may not
take effect, depending on the switch's configuration. You are notified of any failures to save the
configured values to the CEE adapter's no n-volati le mem ory.
Configuring CEE Parameters for FCoE Adapter Ports
The CEE tab displays parameters for FCoE adapter ports.
To view the CEE parameters for FCoE adapter por ts:
1. From the dis cover y-tree , sele ct the FC oE adapter por t whose CEE pr operties you want to vi ew.
The OneCommand Utility User Manual Page 88
2. Se lec t the CEE ta b.
Figure 47: CEE tab for FCoE adapter ports
CEE Tab Field Definitions
• DCBX State - The current DCBX (Data Center discovery and Capability exchange protocol)
state (enabled or disabled).
• DCBX Mode - The DCBX mode can be either CEE or CIN.
Note: DCBX mode also configures FIP mode. If DCBX mode is CEE, FIP is enabled. If it is
CIN, FIP is disabled.
• LLDP Transmit State - DCBX uses Link Layer Discovery Protocol (LLDP) to exchange
parameters between two link peers. For the DCBX protocol to operate correc tly, both LLDP Rx
and Tx must be enabled. If either Rx or Tx is disabled, DCBX is di sab led.
• LLDP Receive State - DCBX uses LLDP to exchange parameters between two link peers. For
the DCBX protocol to operate correctly, both LLDP Rx and Tx must be enabled. If either Rx or Tx
is disabled, DCBX is disabled.
PFC Properties Area
• State - Enabled means that flow control in both directions (Tx and Rx) is enable d.
• Active Priority - Lists the priorities with PFC set to Enabled.
The OneCommand Utility User Manual Page 89
• Sync’d - If yes, the PFC priorities have been set by the peer. This parameter cannot be set.
• Error - The state of FCoE Error feature. The error feature in dic ates whe the r an error has
occurred during the configuration exchange with the peer. Error is also set to TRUE when the
Compatible method for the feature fails.
FCoE Properties Area
• State - The FCoE state. It can be Enabled or Disabled.
• Active Priorites - The current activ e prior ity a ssi gned for F CoE.
• Sync’d - If yes, the FCoE priority has been set b y the pe er. This parameter cannot be set.
• Error - The state of FCoE Error feature. The error feature in dic ated whether an er ror ha s
occurred during the configuration exchange with the pe er. Error is also set to YES when the
Compatible method for the feature fails.
Priority Group Properties Area
• State - The FCoE state. It can be Enabled or Disabled.
• Sync’d - If yes, the Priority Groups have been set by the peer. This parameter cannot be set.
• Error - The state of FCoE Error feature. The error feature in dic ated whether an er ror ha s
occurred during the configuration exchange with the pe er. Error is also set to YES when the
Compatible method for the feature fails.
Active Groups
• PG - The Priority Group number. It can be 0 to 7.
• Priorities - The priorities that are assign ed to eac h Prior ity Gr oup. It is r epresented in c omma
separated format.
• Bandwidth % - The percentage of available link bandwidth alloca ted to a partic ular Pr ior ity
Group.
CEE Tab Buttons
• Configure CEE - Click to configure CEE parame ters . See the inst ructions belo w.
To configure CEE for FCoE ada pter po rts:
Note: While there are eight CEE priority groups in which the CEE priorities can be
assigned, only two of tho se gr ou ps can be ass ign ed prior it ies and ba ndwi dths. The
FCoE priority is assig ned to on e pr io rity gr ou p an d th e oth er seve n (N I C) pr io ri ti es
must be assigned to one and only one ot he r prio r ity group . If you ar e co nfigu ri ng
priority groups on a DCB X enabl ed swi tch , in ord er to wor k pr ope rly w it h the ada pt er
port, you should only configure two prio rity groups in the same way.
1. From the dis cover y-tree , sele ct the FC oE adapter por t whose CEE proper ties you want to
configure.
2. Se lec t the CEE ta b.
3. Cli ck Configure CEE. The Configure CEE dialog box ap pear s.
The OneCommand Utility User Manual Page 90
4. Confi gure the setti ngs you wan t and cl ic k OK.
Figure 48: Configure CEE dialog box for FCoE adapter ports (DCBX enabled)
Configure CEE Dialog Box Field Definitions
DCBX Settings Area
• Enabled - DCBX can be enabled or disabled. W ith DCBX enab led, the c onfi gured val ues are
used only if the switch does not provid e them. With DCBX dis able d, the co nfigur ed v alues are
used.
• DCBX Mode - The DCBX mode can be set to CEE or CIN. Changes to the DCBX mode r equi re
a reboot of the host.
• Operating Version - Operating version of the DCBX protocol. The system adjusts as needed to
operate at the highest version supported by both link partner s. This setti ng ca nnot be c hange d.
• Maximum Version - The highest DCBX protocol version supported by the sy stem . Version
numbers start at zero. The DCBX protocol must be back war d com patible with al l previous
versions. This setting cannot be changed.
LLDP Settings Area
• Transmit Enabled - LLDP Transmit can be enabled or disabled.
The OneCommand Utility User Manual Page 91
• Transmit Port Description Enabled - Provides a description of the port in an alpha-numeric
format. The value equals the ifDescr object, if the LA N dev ice suppo rts RFC 2863.
• Transmit System Name Enabled - Provides the system's ass igned name in an alpha-numeric
format. The value equals the sysName objec t, if the LA N dev ice supports RFC 3418.
• Transmit System Description Enabled - Provides a description of the networ k entity i n an al phanumeric format. This includes system's name an d ver sions o f hard ware, op erating s yste m and
networking software supported by the device. The value equal s the s ysDesc r o bject, if the LA N
device supports RFC 3418.
• Transmit System Capabilities Enabled - Indicates the primary func tion(s) of the de vic e and
whether or not these functions are enabled on the devic e. The capab ilities are indic ated by two
octets. Bits 0 through 7 indicate Other, Repeater, Bridge, WLAN AP, Router, Telephone,
DOCSIS cable device and Station respectively. Bits 8 through 15 are reserved.
• Receive Enabled - LLDP Receive ca n be enab led or disable d .
PFC Priorities Area
• Active Priorities - The priorities that ar e marked a ctiv e for PF C.
• Enable - When checked, PF C is enable d .
• Configured Priorities - The priorities that are confi gured, but mi ght not y et be active.
FCoE Priority Area
• Active Priority - The active FCoE pr iority.
• Configured Priority - The configured FCoE p rio rity.
Priority Groups Area
Active Groups
• Group ID - The Priority Group ID.
• Priority Membership - The different priorities that are ass igned to the v arious P rio rity Gro ups.
This is the currently active configuration.
• Bandwidth - The bandwidths that are assigned to different Priority Groups. This is th e cur ren tly
active configuration.
Configured Groups
• Group ID - The Priority Group ID.
• Priority Membership - The configured pr ior ity member sh ip groupi ng.
• Bandwidth % - The configured value of bandwidth for the different Priority Groups.
Configure CEE Dialog Box Buttons
• Defaults - Click to return parameters to default FCoE CEE settings.
• Configuration Rules - Click to display the FCoE Priority window that lists the rules for configuring
FCoE priorities. You must observe the following rules when configuring CEE for FCoE adapter
ports:
1 One and only one priority is configured for the FCoE priority.
2. Only one PFC priority must be selected and it must match the FCoE priority.
3. The FCoE priority is assigned alone to any of the priority groups.
4. All other priorities must be assigned to one and only one other priority group.
5. Bandwidths of all the priority groups must add up to 100%.
• OK - Click to apply and save y our chang es.
The OneCommand Utility User Manual Page 92
• Cancel - Click to discard any chang es y ou made .
Configuring CEE Parameters for iSCSI Adapter Ports
The CEE tab displays parameters for iSCSI adapter ports.
To view the CEE parameters for FCoE adapter por ts:
1. From the dis cover y-tree , sele ct the i SCSI adapter por t whose CE E proper ties you wa nt to vi ew.
2. Se lec t the CEE ta b.
Figure 49: CEE tab for iSCSI adapter ports
CEE Tab Field Definitions
• DCBX State -The current DCBX (Data Center discovery and Capability exchange protocol) state
(enabled or disabled).
• DCBX Mode - The DCBX mode can be either CEE or CIN.
• LLDP Transmit State - DCBX uses Link Layer Discovery Protocol (LLDP) to exchange
parameters between two link peers. For the DCBX protocol to operate correc tly, both LLDP Rx
and Tx must be enabled. If either Rx or Tx is disabled, DCBX is di sab led.
The OneCommand Utility User Manual Page 93
Loading...