onecommand manager for vmware vcenter version 10 · p011049-01a rev. a connect • monitor •...

OneCommand Manager® for VMware vCenter

Version 10.4User Manual

P011049-01A Rev. A Connect • Monitor • Manage

2

Copyright © 2011-2015 Emulex. All rights reserved worldwide. No part of this 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 Connect, Emulex Secure, EZPilot, FibreSpy, HBAnyware, InSpeed, LightPulse, MultiPulse, OneCommand, OneConnect, One Network. One Company., SBOD, SLI, and VEngine are trademarks of Emulex. All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations.

Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex may make improvements and changes to the product described in this manual at any time and without any notice. Emulex assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties that may result. Periodic changes are made to information contained herein; although these changes will be incorporated into new editions of this manual, Emulex disclaims any undertaking to give notice of such changes.

Emulex, 3333 Susan StreetCosta Mesa, CA 92626

Note: References to OCe11100 series products also apply to OCe11100R series products.

OneCommand Manager for VMware vCenter Version 10.4 User Manual P011049-01A Rev. A

Table of Contents 3

Table of Contents

List of Figures .................................................................................... 13

List of Tables ..................................................................................... 17

1. Introduction ................................................................................... 18

Compatibility......................................................................................... 18

Abbreviations ........................................................................................ 21

2. Installing and Enabling OneCommand Manager for VMware vCenter .............. 25

Best Installation Practices ......................................................................... 25

Hardware Requirements ........................................................................... 25

Software Requirements ............................................................................ 25

Installing OneCommand Manager for VMware vCenter ...................................... 26

Verifying the OneCommand Manager for VMware vCenter Installation .................29

Activating and Enabling ESXi Management ..................................................... 30

Requirements.....................................................................................30

Lockdown Mode Feature ........................................................................30

Activating OneCommand Manager for VMware vCenter in the Web Client .............31

Enabling OneCommand Manager for VMware for vCSA.....................................31

Enabling OneCommand Manager for VMware vCenter Web Client .......................31

Enabling and Disabling OneCommand Manager for VMware vCenter with the Plug-in Manager...................................................................................... 32

Registering and Unregistering OneCommand Manager for VMware vCenter ............ 33

Uninstalling OneCommand Manager for VMware vCenter................................... 34

Reinstalling OneCommand Manager for VMware vCenter ................................... 34

3. Using OneCommand Manager for VMware vCenter.................................... 36

Accessing with VMware Web Client 6.0......................................................... 36

Accessing with VMware Web Client Versions 5.5 and 5.1................................... 36

Accessing the vSphere Console................................................................... 37

vSphere Console Views..........................................................................37

OneCommand Manager for VMware vCenter Window Elements ..........................38

4. Managing Clusters and Hosts ............................................................... 41

Managing Clusters ................................................................................... 41

Viewing Hosts in a Cluster......................................................................41Hosts within a Cluster, Field Definitions ......................................................... 42

Viewing Adapters in a Cluster..................................................................42


Table of Contents 4

Adapters within a Cluster, Field Definitions..................................................... 43

Viewing Physical Ports in a Cluster (Host-centric mode) ..................................43Physical Ports within a Cluster, Host-centric Field Definitions ............................... 44

Viewing Virtual Ports in a Cluster (Host-centric mode)....................................45Virtual Ports in a Cluster, Host-centric Field Definitions...................................... 45

Viewing Physical Port Information in a Cluster (Fabric- centric mode) .................46Fabric-centric Information Field Definitions..................................................... 47

Managing Hosts ...................................................................................... 48

Viewing Host Information for a Single Host..................................................48Host Information Field Definitions ................................................................ 48

Viewing Driver Parameters of All Adapters in a Host ......................................49Host Driver Parameters Tab Field Definitions ................................................... 50

Viewing Firmware Information for All Adapters in a Host ................................51Host Maintenance Tab Field Definitions.......................................................... 51

5. Managing Adapters and Ports .............................................................. 52

FC/FCoE Adapters ................................................................................... 52

Viewing FC and FCoE Port Information .......................................................52FC Adapter Information Field Definitions ........................................................ 52

Viewing FC Port Details and Changing Link State...........................................53FC Port Details Tab Field Definitions ............................................................. 53

Viewing FCoE Port Details ......................................................................55FCoE Port Details Field Definitions................................................................ 55

Viewing FC/FCoE Port Driver Parameters....................................................56FC/FCoE Driver Parameters Tab Field Definitions .............................................. 57

Viewing FC/FCoE Port Statistics ..............................................................58FC/FCoE Port Statistics Tab Field Definitions ................................................... 58

Viewing FC Port Transceiver Information ....................................................60Transceiver Information Field Definitions ....................................................... 60

Viewing FC/FCoE Port Vital Product Data (VPD) ............................................61VPD Table Definitions ............................................................................... 61

Viewing FC/FCoE Port Maintenance and Firmware Information..........................62Maintenance Tab Field Definitions ................................................................ 63

Viewing FC/FCoE Target Information.........................................................64Target Information Field Definitions.............................................................. 64

Viewing FC/FCoE LUN Information ............................................................64FC/FCoE LUN Information Field Definitions ..................................................... 65

Viewing PCI Registers for an FC Port .........................................................66

Viewing PCI Registers for an FCoE Port.......................................................67

Viewing Flash Contents for an FC Port .......................................................68

Viewing DCB Parameters for FCoE Adapter Ports ...........................................68


Table of Contents 5

DCB Tab Field Definitions........................................................................... 69

OneConnect Adapters .............................................................................. 70

Viewing OneConnect Adapter Information...................................................70Adapter Information Tab Field Definitions....................................................... 71

Viewing Licenses .................................................................................73

Viewing Physical Ports ..........................................................................73Physical Port Info Tab Field Definitions .......................................................... 73

Viewing Firmware Information.................................................................74Maintenance Tab Field Definitions ................................................................ 75

Viewing Physical Port DCB Parameters .......................................................75DCB Tab Field Definitions........................................................................... 76

Viewing PHY Data for OneConnect 10GBASE–T–Series Adapters ..........................77PHY Data Tab Field Definitions .................................................................... 77

Viewing Port Transceiver Information ........................................................78Transceiver Information Field Definitions ....................................................... 79

Viewing the Channel Management Tab for UFP (OCe11100–Series Adapters Only) ...............................................................................................80

Channel Mgmt Field Definitions for UFP.......................................................... 80

Viewing the Channel Management Tab for vNIC1 (OCe11100–Series Adapters Only) ...............................................................................................81

Channel Mgmt Field Definitions for vNIC1 ....................................................... 81

Installing Licenses ...............................................................................81

Changing Personalities ..........................................................................82

Enabling or Disabling a Physical Port .........................................................83

Changing a Physical Port’s Speed .............................................................83Change Port Speed Field Definitions.............................................................. 84

Configuring Physical Port DCB Parameters...................................................84Configure DCB Dialog Box Field Definitions...................................................... 85

Managing Port Channels Using Channel Management (OCe11100–Series Adapters Only) ...................................................................................88

Enabling and Disabling Channel Management ...............................................88

Configuring Channel Management.............................................................88Channel Mgmt Field Definitions ................................................................... 89

Disabling a Specific Channel ...................................................................90

Assigning an LPVID for a Specific Channel ...................................................90

Assigning Bandwidth for a Specific Channel .................................................90

OCe14100–Series Adapters ........................................................................ 91

Viewing Adapter Information ..................................................................91

Viewing Physical Port DCB Parameters .......................................................91DCB Tab Field Definitions........................................................................... 92


Table of Contents 6

Viewing Physical Data ...........................................................................93PHY Data Tab Field Definitions .................................................................... 93

Configuring OCe14000–Series Adapters.......................................................94OCe14100–Series Adapter Configuration Tab Field Definitions ............................... 95

Enabling or Disabling SR-IOV ...................................................................96

Configuring a Single Personality ...............................................................97

Setting Up a Custom Configuration ...........................................................98

Setting Up a Mixed Mode Configuration ......................................................99

Setting Up a Concurrent Mode Configuration.............................................. 100

Setting Up a UMC Configuration ............................................................. 101

Default UMC Settings .......................................................................... 102

Setting Up an IBM MultiChannel Configuration ............................................ 103

Setting Up a Multichannel vNIC Configuration ............................................ 104

Setting Up a MultiChannel SIMode Configuration ......................................... 105

Setting Up a Multichannel UFP Configuration ............................................. 106

Setting Dell NPar Bandwidth Settings....................................................... 107

Two-Port Adapters............................................................................. 107NParEP Mode Disabled ............................................................................ 107

NParEP Mode Enabled ............................................................................. 108

Four-Port Adapters ............................................................................ 109Dell NPar Enabled.................................................................................. 109

NParEP Mode Disabled ............................................................................ 110

NParEP Mode Enabled ............................................................................. 111

Setting Up HP Flex Configurations .......................................................... 112

Configuring DCB Parameters for FCoE/iSCSI Adapter Ports ............................. 114Configure DCB Dialog Box Field Definitions.................................................... 114

FCoE and iSCSI Configuration Rules ............................................................. 116

NIC Configuration Rules........................................................................... 116

6. Managing Protocols ........................................................................ 117

NIC.....................................................................................................117

Viewing NIC Port Information ................................................................ 117NIC Port Information Tab Field Definitions .................................................... 118

Viewing PCI Registers for a NIC Port ........................................................ 119

Viewing NIC Port Vital Product Data (VPD) ................................................ 120VPD Table Definitions ............................................................................. 121

Viewing Virtual Functions on a Host Operating System.................................. 121Port Information Field Definitions............................................................... 122

Network Boot ................................................................................... 122

Enabling and Disabling VEPA ................................................................. 122


Table of Contents 7

FC /FCoE Ports ......................................................................................123

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

Enabling an Optimized Access Storage (ExpressLane) LUN.............................. 123

Disabling ExpressLane LUNs .................................................................. 125

Configuring FIP ................................................................................. 125FIP Tab Field Descriptions ........................................................................ 126

Configuring DCB Parameters for FCoE Adapter Ports .................................... 127

Changing WWN Configuration for an FC Port .............................................. 127

Considerations When Changing WWN Configuration for an FC Port.................... 128

Resetting an FC/FCoE Port ................................................................... 130

Enabling and Disabling FC Ports ............................................................. 131

Setting Driver Parameters for an FC/FCoE Port........................................... 131

Saving Driver Parameters of an FC/FCoE Port to a File.................................. 132

iSCSI ...................................................................................................132

Viewing iSCSI Port Information .............................................................. 132iSCSI Port Info Tab Field Definitions ............................................................ 133

Viewing PCI Registers for an iSCSI Port..................................................... 134

Viewing and Changing iSCSI ISNS Server Information..................................... 135iSNS Tab Field Definitions ........................................................................ 135

Viewing iSCSI Initiator Statistics............................................................. 135iSCSI Statistics Tab Field Definitions............................................................ 136

Viewing iSCSI Initiator Login Options ....................................................... 137iSCSI Initiator Login Options Tab Field Definitions............................................ 138

Initiator Default Login Options Window Field Definitions ................................... 139

Viewing iSCSI Target Discovery Information ............................................... 140iSCSI Target Discovery Tab Field Definitions .................................................. 141

Viewing iSCSI Target Information ........................................................... 141iSCSI Target Information Tab Field Definitions................................................ 142

Viewing Target Session Information ........................................................ 142Target Sessions Window Field Definitions...................................................... 143

Viewing iSCSI LUN Information............................................................... 145iSCSI LUN Info Tab Field Definitions ............................................................ 145

Viewing iSCSI Port Vital Product Data (VPD)............................................... 146VPD Table Definitions ............................................................................. 146

Enabling iSCSI Boot ............................................................................ 147

Disabling the ISNS Server ..................................................................... 147

Changing the ISNS Server ..................................................................... 147

Configuring ISNS for iSCSI Target Discovery ............................................... 148

Configuring DCB Parameters for iSCSI Adapter Ports..................................... 148DCB Tab Field Definitions......................................................................... 148


Table of Contents 8

ETS Priority Group Properties Area ............................................................. 149

Configure DCB Dialog Box Field Definitions.................................................... 150

7. Updating Firmware ........................................................................ 153

Updating Firmware for an FC Adapter .........................................................153

Updating Firmware on FC Adapters in a Host ................................................154

Updating Firmware for OCe11100–Series and OCe14100–Series Adapters .............156

Performing a Batch Firmware Update in Cluster View .................................. 157

Updating Firmware on Multiple Adapters in Cluster View............................... 158

Jobs Window.................................................................................... 160Jobs Window Field Definitions ................................................................... 160

8. Exporting SAN Information in Cluster View........................................... 162

Export SAN Info Window Field Definitions ..................................................... 163

Capturing SAN Information in XML or CSV Format ........................................ 164

Considerations When Exporting SAN Information in a Cluster View.................... 164

9. Diagnostics................................................................................... 165

LightPulse FC Diagnostics.........................................................................165

Running Loopback Tests ...................................................................... 165

Running End to End (ECHO) Tests ........................................................... 166

Running D_Port Tests (LPe16000–Series FC Adapters).................................... 166

Running a Power-On Self-Test (POST) ...................................................... 170

Using Beaconing................................................................................ 170

Setting Up Diagnostic Test Options ......................................................... 170Setting Up a Test Failure Error Action.......................................................... 170

Setting Up Test Cycles ............................................................................ 170

Setting Up a Test Pattern......................................................................... 171

Test Status .......................................................................................... 171

Saving the Log File............................................................................. 171

Creating Port Diagnostic Dumps ............................................................. 172Diagnostic Dump Tab Field Definitions ......................................................... 172

Viewing Diagnostic Dump Files .............................................................. 173

OneConnect Diagnostics ..........................................................................175

Running Loopback Tests ...................................................................... 175

Using Beaconing................................................................................ 176

Running a TDR Test (10GBASE–T–Series Adapters Only).................................. 176

Setting Up Diagnostic Test Options ......................................................... 177Setting Up a Test Failure Error Action.......................................................... 177

Setting Up Test Cycles ............................................................................ 177

Setting Up a Test Pattern......................................................................... 177


Table of Contents 9

Test Status .......................................................................................... 177

Saving the Log File............................................................................. 177

Creating OneConnect Adapter Port Diagnostic Dumps ................................... 178Diagnostic Dump Tab Field Definitions ......................................................... 178

Viewing Diagnostic Dump Files .............................................................. 179

10. Generating and Installing Secured Certificates..................................... 181

Secure Sockets Layer (SSL) Certificate ........................................................181

Generating an SSL Certificate ............................................................... 181

Generating a Self-Signed Certificate ...........................................................182

Generating a Certificate Signing Request (CSR)..............................................183

Generating a CSR for a Server Using the Java Tool....................................... 183

Generating and Validating a CSR ............................................................ 183

Getting an SSL Certificate.................................................................... 184

Installing the SSL into the Web Server ..................................................... 184Installing the Certificates to the Keystore of OneCommand Manager for VMware vCenter.................................................................................... 184

Configuring the Tomcat Web Server ............................................................ 185

11. Troubleshooting .......................................................................... 187

Security ..............................................................................................187

Accepting the Blocked Content.............................................................. 187Internet Explorer................................................................................... 187

Chrome and Firefox ............................................................................... 187

Installing a Security Certificate ............................................................. 188

12. Using OneCommand Manager for VMware vCenter Command Line Interface......................................................................................... 192

elxvcpcmd Syntax Usage..........................................................................192

Help Commands ....................................................................................193

help (single command)........................................................................ 193Syntax................................................................................................ 193

Description.......................................................................................... 193

Parameters.......................................................................................... 193

help (group) .................................................................................... 193

CLI Command Reference Tables.................................................................194

Group Commands and CLI Command Descriptions...........................................202

General Group Commands.................................................................... 202setvccred............................................................................................ 202

reset ................................................................................................. 203

version............................................................................................... 203


Table of Contents 10

AdapterLicense Commands................................................................... 203installadapterlicense .............................................................................. 203

showlicenseadapterfeatures ..................................................................... 204

showlicenseadapterid ............................................................................. 204

Adapter Management Commands............................................................ 205getadapterportconfig ............................................................................. 205

setadapterportconfig.............................................................................. 205

Enabling/Disabling Multichannel ................................................................ 207

Attribute Commands .......................................................................... 208getpcidata .......................................................................................... 208

getportstatistics.................................................................................... 208

getvpd ............................................................................................... 209

getwwncap.......................................................................................... 209

hbaattributes ....................................................................................... 210

listhbas .............................................................................................. 210

pcidata .............................................................................................. 210

portattributes ...................................................................................... 211

serverattributes .................................................................................... 211

setphyportspeed ................................................................................... 212

setportenabled ..................................................................................... 212

Boot Command ................................................................................. 213enablebootcode .................................................................................... 213

Channel Management Commands ........................................................... 214cmgetparams ....................................................................................... 214

cmmode ............................................................................................. 215

cmsetbw............................................................................................. 215

umcsetlpvid......................................................................................... 216

Cluster Commands ............................................................................. 217exportsaninfo....................................................................................... 218

firmwareupdate .................................................................................... 218

listhbas .............................................................................................. 219

DCB Commands................................................................................. 219getdcbparams ...................................................................................... 219

getpginfo ............................................................................................ 220

setcnapgbw ......................................................................................... 220

setdcbparam........................................................................................ 221

setdcbpriority ...................................................................................... 222

Diagnostic Commands ......................................................................... 223D_Port ............................................................................................... 224

echotest ............................................................................................. 225

getbeacon........................................................................................... 225



getxcvrdata ......................................................................................... 226

loadlist............................................................................................... 226

loopbacktest ........................................................................................ 227

posttest.............................................................................................. 228

setbeacon ........................................................................................... 228

setcablenvp ......................................................................................... 229

tdrtest ............................................................................................... 229

Driver Parameter Commands ................................................................ 230driverconfig ......................................................................................... 230

getdriverparams.................................................................................... 230

getdriverparamsglobal ............................................................................ 231

saveconfig........................................................................................... 231

setdriverparam ..................................................................................... 232

setdriverparamdefaults ........................................................................... 233

Dump Commands............................................................................... 233deletedumpfiles.................................................................................... 233

dump................................................................................................. 234

getdumpdirectory.................................................................................. 234

getdumpfilenames ................................................................................. 235

getretentioncount ................................................................................. 235

setdumpdirectory .................................................................................. 236

setretentioncount.................................................................................. 236

FCoE Commands................................................................................ 237getfcfinfo ........................................................................................... 237

getfipparams ....................................................................................... 238

getlunlist ............................................................................................ 238

setfipparams........................................................................................ 238

targetmapping...................................................................................... 239

Firmware Commands .......................................................................... 239firmwareupdate .................................................................................... 240

iSCSI Commands................................................................................ 240clearisnsserver ..................................................................................... 240

getinitiatorproperties ............................................................................. 240

getiscsiluns.......................................................................................... 241

getiscsiportstats.................................................................................... 241

getsessioninfo ...................................................................................... 242

listprofiles........................................................................................... 242

listsessions .......................................................................................... 243

showisnsserver ..................................................................................... 243

showtarget .......................................................................................... 244

updateisnsserver ................................................................................... 244



Personality Commands ........................................................................ 245changepersonality ................................................................................. 245

showpersonalities .................................................................................. 246

SR-IOV Commands ............................................................................. 246listvfuncs ............................................................................................ 246

sriovenable.......................................................................................... 247

Target and LUN Commands................................................................... 248getexpresslanelunlist (LPe16000–Series and OCe15100– Series Only)...................... 248

getiscsiluns.......................................................................................... 248

getlunlist ............................................................................................ 248

listsessions .......................................................................................... 248

setexpresslanelunstate (LPe16000–Series and OCe15100– Series Only).................... 249

showtarget .......................................................................................... 250

targetmapping...................................................................................... 250

VEPA Commands ............................................................................... 250VEPAenable ......................................................................................... 250

Virtual Machines Commands ................................................................. 250listvms ............................................................................................... 250

listvports ............................................................................................ 251

WWWN Management Commands............................................................. 251changewwn ......................................................................................... 251

getwwncap.......................................................................................... 252

readwwn ............................................................................................ 252

restorewwn ......................................................................................... 252

Viewing Audit Logs Using the CLI Command ..................................................253


List of Figures 13

List of FiguresFigure 2-1 Installation options Window .............................................................26Figure 2-2 OCM for VMware vCenter configuration Window.....................................27Figure 2-3 OCM for VMware vCenter configuration Window with Port in use

Warning .....................................................................................28Figure 2-4 Register/Unregister Dialog Box .........................................................28Figure 2-5 vSphere Console, Getting Started Tab.................................................29Figure 2-6 Plug-in Manager Window .................................................................30Figure 2-7 vSphere Web Client Plug-In Management Page.......................................32Figure 2-8 Plug-in Manager with Selected Row ....................................................33Figure 2-9 Reinstallation Configuration Dialog Box ...............................................35Figure 3-1 Cluster View with Callouts...............................................................38Figure 3-2 Host View with Callouts ..................................................................39Figure 4-1 Hosts within a Cluster ....................................................................42Figure 4-2 Adapters within a Cluster................................................................43Figure 4-3 Physical Ports within a Cluster, Host-centric View ..................................44Figure 4-4 Close-Up of Physical Ports within a Cluster, Host-centric View ...................44Figure 4-5 Virtual Ports in a Cluster, Host-centric View .........................................45Figure 4-6 Information for a Physical Port in a Cluster, Fabric-Centric View.................46Figure 4-7 Close-up of Information for a Physical Port in a Cluster,

Fabric-Centric View.......................................................................47Figure 4-8 Information for a Single Host............................................................48Figure 4-9 Host Driver Parameters ..................................................................50Figure 4-10 Host Maintenance Tab....................................................................51Figure 5-1 FC Adapter Information Tab.............................................................52Figure 5-2 FC Port Details Tab .......................................................................53Figure 5-3 FCoE Port Details Tab ....................................................................55Figure 5-4 FC/FCoE Port Driver Parameters Tab ..................................................57Figure 5-5 FC/FCoE Port Statistics Tab .............................................................58Figure 5-6 FC Port Transceiver Tab .................................................................60Figure 5-7 Port VPD Tab...............................................................................61Figure 5-8 FC Port Maintenance Tab ................................................................62Figure 5-9 FCoE Port Maintenance Tab .............................................................62Figure 5-10 Target Information Tab ..................................................................64Figure 5-11 FC/FCoE LUN Information................................................................65Figure 5-12 FC Port PCI Registers Tab................................................................66Figure 5-13 FCoE Port PCI Registers Tab .............................................................67Figure 5-14 FC Port Flash Contents ...................................................................68Figure 5-15 DCB Tab (FCoE Adapter Port Selected) ................................................69Figure 5-16 OneConnect Adapter Information Tab ................................................71Figure 5-17 OCe11100–Series Adapter Physical Port Info Tab ....................................73


List of Figures 14

Figure 5-18 OCe11100-Series Adapter Maintenance Tab..........................................74Figure 5-19 FCoE Adapter Port, DCB Tab ............................................................75Figure 5-20 OneConnect Adapter PHY Data Tab ....................................................77Figure 5-21 OCe10100–Series Port Transceiver Tab ................................................79Figure 5-22 Channel Management Tab in UFP Mode................................................80Figure 5-23 Channel Management Tab in vNIC1 Mode .............................................81Figure 5-24 Install Feature Licenses Dialog Box.....................................................82Figure 5-25 Change Port Speed Dialog Box ..........................................................84Figure 5-26 DCB Configuration Dialog Box for FCoE and ISCSI Adapter Ports

(DCBX Enabled) ............................................................................85Figure 5-27 Channel Mgmt tab for the OCe11102 adapter ........................................89Figure 5-28 OCe14100-Series Adapter, DCB Tab (FCoE/iSCSI Adapter Port Selected) ........91Figure 5-29 OneConnect OCe14000-Series Adapter PHY Data Tab ...............................93Figure 5-30 OCe14100-series Adapter Configuration Tab (FCoE selected)......................95Figure 5-31 Current Configuration Details example................................................96Figure 5-32 OCe14100-series Adapter Configuration Tab, Custom Configuration .............98Figure 5-33 Mixed Mode Protocol Drop-Down Menu ................................................99Figure 5-34 Concurrent Storage Configuration View ............................................. 100Figure 5-35 Concurrent Storage Configuration Choices for the Third Function .............. 101Figure 5-36 UMC View (four ports) .................................................................. 101Figure 5-37 MultiChannel View (showing multichannel type drop-down menu) ............ 103Figure 5-38 MultiChannel vNIC View (Mixed Mode Storage)..................................... 104Figure 5-39 MultiChannel SIMode View ............................................................. 105Figure 5-40 MultiChannel UFP View (concurrent mode storage) ............................... 106Figure 5-41 Dell Two-Port NPar Configuration, NParEP Mode Disabled ....................... 107Figure 5-42 Dell Two-Port NPar Configuration, NParEP Mode Enabled........................ 108Figure 5-43 Adapter Configuration Tab with NPar Enabled ..................................... 109Figure 5-44 Dell Four Port NPar Configuration, NParEP Mode Disabled ....................... 110Figure 5-45 Dell Four Port NPar Configuration, NParEP Mode Enabled........................ 111Figure 5-46 HP Flex Adapter Configuration Tab, Flex selected ................................ 112Figure 5-47 HP Flex Adapter Configuration Tab, Single Personality selected................ 113Figure 5-48 DCB Configuration Dialog Box for FCoE and ISCSI Adapter Ports

(DCBX Enabled) .......................................................................... 114Figure 6-1 NIC Port Information Tab with SR-IOV Enabled on the Adapter ................. 118Figure 6-2 NIC Port Information Tab with SR-IOV Disabled on the Adapter ................. 118Figure 6-3 NIC Port PCI Registers Tab............................................................. 120Figure 6-4 NIC Port VPD Tab........................................................................ 120Figure 6-5 Virtual Functions Discovered on the Physical Function on the Host

OS.......................................................................................... 121Figure 6-6 Port Information tab for NIC Virtual Function ...................................... 121Figure 6-7 ExpressLane LUN Drop-Down Menu................................................... 124Figure 6-8 FC/FCoE LUN with ExpressLane Enabled ............................................ 125


List of Figures 15

Figure 6-9 FCoE Port FIP Tab ....................................................................... 126Figure 6-10 Configure DCB Dialog Box for FCoE Adapter Ports (DCBX Enabled) ............. 127Figure 6-11 Change WWN Configuration Dialog Box.............................................. 129Figure 6-12 Warning About Changing WWN........................................................ 130Figure 6-13 Reset Port Warning ..................................................................... 130Figure 6-14 iSCSI Port Info Tab ...................................................................... 133Figure 6-15 iSCSI Port, PCI Registers Tab .......................................................... 134Figure 6-16 iSCSI Port, iSNS Tab..................................................................... 135Figure 6-17 iSCSI Initiator, iSCSI Statistics Tab ................................................... 136Figure 6-18 iSCSI Initiator Logon Options Tab..................................................... 138Figure 6-19 iSCSI Initiator Default Login Options Window....................................... 138Figure 6-20 iSCSI Target Discovery Tab ............................................................ 141Figure 6-21 iSCSI Target Information Tab.......................................................... 141Figure 6-22 iSCSI Target Sessions Window ......................................................... 143Figure 6-23 iSCSI LUN Info Tab ...................................................................... 145Figure 6-24 iSCSI Port VPD Tab ...................................................................... 146Figure 6-25 iSCSI Port, Update iSNS Server Dialog Box .......................................... 147Figure 6-26 DCB Tab (iSCSI Adapter Port Selected) .............................................. 148Figure 6-27 Configure DCB Dialog Box for iSCSI Adapter Ports (DCBX Enabled).............. 150Figure 7-1 Firmware Download dialog box ...................................................... 153Figure 7-2 Empty Batch Firmware Download Dialog Box ....................................... 155Figure 7-3 Populated Batch Firmware Download Dialog Box .................................. 155Figure 7-4 Firmware Download Dialog Box ....................................................... 156Figure 7-5 Batch Firmware Update Information................................................. 158Figure 7-6 Batch Firmware Download Dialog Box, Host-Centric View........................ 159Figure 7-7 Batch Firmware Download Dialog Box, Fabric-Centric View ..................... 159Figure 7-8 Jobs Window ............................................................................. 160Figure 8-1 Export SAN Info.......................................................................... 162Figure 8-2 Export SAN Info Dialog Box ............................................................ 163Figure 8-3 Export SAN Info Jobs Window, Active Jobs List .................................... 163Figure 9-1 FC Adapter Diagnostics Tab ........................................................... 165Figure 9-2 Diagnostic Tests Warning .............................................................. 166Figure 9-3 FC Adapter Diagnostics Tab with D_Port Tests Option ............................ 167Figure 9-4 D_Port Tests Dialog Box ................................................................ 168Figure 9-5 D_Port Tests Dialog Box - Passed Results............................................ 169Figure 9-6 D_Port Tests Dialog Box - Failed Results ............................................ 169Figure 9-7 Diagnostic Test Log Entries ............................................................ 171Figure 9-8 FC Port Diagnostic Dump Tab ......................................................... 172Figure 9-9 Diagnostic Dump Files window ........................................................ 173Figure 9-10 Datastores View of vSphere Client ................................................... 174Figure 9-11 vSphere Datastore Browser ............................................................ 174Figure 9-12 OneConnect Adapter Diagnostics Tab................................................ 175


List of Figures 16

Figure 9-13 Diagnostic Tests Warning .............................................................. 176Figure 9-14 Port Diagnostic Dump Tab ............................................................. 178Figure 9-15 Diagnostic Dump Files window ........................................................ 179Figure 11-1 Blocked Content in Internet Explorer ................................................ 187Figure 11-2 Blocked Content in the Firefox or Chrome Browser ............................... 188Figure 11-3 Untrusted Certificate................................................................... 188Figure 11-4 Certificate Dialog Box .................................................................. 189Figure 11-5 Certificate Import Wizard ............................................................. 189



List of Tables 17

List of TablesTable 1-1 Support Provided by Emulex CIM Provider Versions .................................19

Table 11-1 Troubleshooting Issues and Resolutions ............................................. 190

Table 12-1 CLI Commands ........................................................................... 194

Table 12-2 Help Groups and Supported CLI Commands......................................... 196

1. IntroductionCompatibility

18

1. IntroductionEmulex® OneCommand Manager ®for VMware vCenter is a comprehensive management utility for Emulex adapters that provides a powerful, centralized adapter management suite for the VMware vCenter management console.

This comprehensive solution builds upon standard Emulex Common Interface Model (CIM) management providers and advanced functionality delivered with the Emulex OneCommand Manager application to present native configuration management, status monitoring, and online maintenance of Emulex adapters in VMware ESXi environments, using a graphical interface (GUI) or a command line interface (CLI).

Compatibility For supported versions of operating systems, platforms, and adapters, see the Emulex website.

OneCommand Manager for VMware vCenter can be hosted and registered on the following servers:

vCenter Server 6.0 vCenter Server 5.5 vCenter Server 5.1

OneCommand Manager for VMware vCenter is supported for the following Windows operating systems:

Windows Server 2008 SP2 (or later) – Standard, Enterprise and Datacenter editions (32 bit, x86) and (64 bit, x86_64)

Windows Server 2008 R2 – Standard, Enterprise and Datacenter editions (32 bit, x86) and (64 bit, x86_64)

Windows 7 -x64 Windows 8 -x64 Windows 8.1 -x64 Windows Server 2012

Refer to Table 1-1, Support Provided by Emulex CIM Provider Versions, on page 19 to determine the support provided by your Emulex CIM Provider.

Note: Illustrations in this manual are for illustrative purposes only. Your system information can vary.

OneCommand Manager for VMware vCenter supports Emulex LPe16202 adapters. If the adapter is in Fibre Channel (FC) mode, it functions as an FC adapter. If it is in Fibre Channel over Ethernet (FCoE) + network interface card (NIC) mode, it functions as a Converged Network Adapter (CNA).

OneCommand Manager for VMware vCenter supports Emulex OneConnect adapters, including OCe14101 and OCe14102 CNAs. The features available in OneCommand



19

Manager for VMware vCenter are determined by the Emulex CIM Provider version installed.

Table 1-1 lists the Emulex OneCommand Manager application support provided by the Emulex CIM Provider package and the individual FC and CNA providers in each package. The Emulex CIM Provider packages can be downloaded from the Emulex website.

Table 1-1 Support Provided by Emulex CIM Provider Versions

Emulex OneCommand Manager Application Features

ELX CIM Provider Package v10.4

OneCommand Manager for

VMware vCenter v 10.4CNA FC

Discover virtual ports connected to an FC or FCoE port

View virtual port information in a cluster (host-centric mode) N/A N/A

Discover hosts, adapters (FC, FCoE, NIC and iSCSI), targets, and logical unit numbers (LUNs) for selected ESXi hosts

Discover hosts and adapters (FC and FCoE) for selected ESXi fabrics

View firmware version

View boot code version

Update firmware and FC boot code on a single adapter

Update firmware and FC boot code on a per-fabric basis N/A N/A

Change World Wide Port Name (WWPN) or World Wide Name (WWN) for FC adapters

Locate FC and OneConnect adapters with beaconing

View Peripheral Component Interconnect Express (PCIe) registers

D_Port (also referred to as ClearLink) test, for LPe16000-series FC adapters only

N/A

PHY loopback test for OneConnect adapters

MAC loopback test for OneConnect adapters N/A

PCI loopback test for FC adapters N/A

Internal and External loopback test or FC adapters N/A

Echo test for FC adapters N/A

Power-on self-test (POST) test for FC adapters, except LPe16000-series FC adapters.

N/A

Time-domain reflectometer (TDR) tests for OneConnect 10GBASE-T-series adapters

N/A

Batch update firmware and FC boot code to multiple adapters N/A N/A

Enable/disable ports

Get driver parameters (global and port)



20

Set global driver parameters to adapters

Set port driver parameters to adapters

Target and LUN information

ExpressLane priority queueing for LPe16000-series and OCe15100-series adapters

Reset Port (FC and FCoE only)

View vital product data (VPD)

View physical data for OneConnect 10GBASE-T adapters N/A

iSCSI management N/A

Enable/disable FCoE Initialization Protocol (FIP) data N/A

DCB configuration for OneConnect adapters, and FCoE and iSCSI ports for LightPulse adapters

N/A

Display flash contents (wakeup parameters/flash load list) for the FC port of LightPulse adapters

N/A

Export storage area network (SAN) configuration information at cluster level and at host level

N/A N/A

Perform diagnostic dump at the adapter and port level

Personality (protocol) change and licensing N/A

iSCSI boot firmware table (iBFT) support for the CNA 16 Gb family of adapters that support the NIC or iSCSI protocol. PXE boot is supported on LPe16202 and OCe11000–series adapters.

N/A

Channel Management for OCe11100–series adapters N/A

Single root I/O virtualization (SR-IOV). N/A

Virtual Ethernet port aggregator (VEPA). N/A

Table 1-1 Support Provided by Emulex CIM Provider Versions (Continued)

Emulex OneCommand Manager Application Features

ELX CIM Provider Package v10.4

OneCommand Manager for

VMware vCenter v 10.4CNA FC


1. IntroductionAbbreviations

21

AbbreviationsAL_PA Arbitrated Loop Physical Address

ARI alternate routing-ID interpretation

ASIC application-specific integrated circuit

BIOS basic input/output system

BOFM Blade Open Firmware Management Protocol

BW bandwidth

CA certificate authority

CDB command descriptor block

CHAP Challenge Handshake Authentication Protocol

CIM Common Interface Model

CIN Cisco, Intel, Nuova (Data Center Bridging Exchange)

CLI command line interface

CLP Command Line Protocol

CNA Converged Network Adapter

CPU central processing unit

CRC cyclic redundancy check

CSR Certificate Signing Request

CSV comma-separated value

DAC direct-attach copper

DCB Data Center Bridging

DCBX Data Center Bridging Capabilities Exchange

DHCP Dynamic Host Control Protocol

DIF Data Integrity Field

DMA direct memory access

DNS Domain Name System or Domain Name Server

DOCSIS Data Over Cable Service Interface Specification

EC engineering change

ETO extended timeout

ETS Enhanced Transmission Selection

FC Fibre Channel

FCF Fibre Channel over Ethernet Forwarder

FCoE Fibre Channel over Ethernet

FCP Fibre Channel Protocol

FIP FCoE Initialization Protocol

FPMA fabric-provided MAC address



22

FW firmware

GUI graphical user interface

HBA host bus adapter

HTTP Hypertext Transfer Protocol

HTTPS Hypertext Transfer Protocol Secure

HW hardware

iBFT iSCSI boot firmware table

IEEE Institution of Electrical and Electronics Engineers

I/O input/output

IP internet protocol

IPL initial program load

IPv4 Internet Protocol version 4

IPv6 Internet Protocol version 6

iSCSI Internet Small Computer System Interface

ISID initiator session identifier

ISNS Internet Storage Name Service

JEDEC ID Joint Electron Device Engineering Council identification code

KB Kilobyte (1024 bytes)

LAN local area network

LDPC low-density parity check

LDTO link down timeout

LED light emitting diode

LIP Loop Initialization Primitive

LLDP Link Layer Discovery Protocol

LPVID logical port VLAN ID

LUN logical unit number

MAC Media Access Control

MB megabyte

Mb megabit

Mbps megabits per second

MDI Medium Dependent Interface

MN manufacturer ID

MSE mean squared error

MSS maximum segment size

MTU maximum transmission unit

N/A not applicable

NCSI Network Communication Services Interface



23

NIC network interface card

NOS network operating system

NPar NIC partitioning

NVP nominal velocity of propagation

NVRAM non-volatile random-access memory

OS operating system

OUI organizationally unique identifier

PCI Peripheral Component Interconnect (interface)

PCIe Peripheral Component Interconnect Express

PF physical function

PDU protocol data unit

PFC priority flow control

PGID priority group ID

PLL phase-locked loop

POST power-on self-test

PXE Preboot execution Environment

QoS quality of service

R2T request to transmit

RFC Request for Comments

RPI remote port indicator

Rx receive

SAN storage area network

SCSI Small Computer System Interface

SF standard function

SFCB Small Footprint CIM Broker

SFP small form-factor pluggable

SLI Service Level Interface

SNMP Simple Network Management Protocol

SNR signal-to-noise ratio

SR-IOV single root I/O virtualization

SSL secure sockets layer

TCP Transmission Control Protocol

TCP/IP TCP over Internet Protocol

TDR time-domain reflectometer

Tx transmit

UFP Universal Fabric Port

ULP Upper Layer Protocol



24

UMC Universal Multi-Channel

vCSA VMware for vCenter Server Appliance

VEPA virtual Ethernet port aggregator

VF virtual function

VLAN virtual local area network

VLAN_ID VLAN identifier

VM virtual machine

VPD vital product data

vPort virtual port

WLAN wireless LAN

WWN World Wide Name

WWNN World Wide Node Name

WWPN World Wide Port Name

XRI extensible resource indicator

XML Extensible Markup Language


2. Installing and Enabling OneCommand Manager for VMware vCenterBest Installation Practices

25

2. Installing and Enabling OneCommand Manager for VMware vCenter

This section describes installing, uninstalling, reinstalling, and enabling OneCommand Manager for VMware vCenter. This section also describes registering and unregistering OneCommand Manager for VMware vCenter.

Notes

OneCommand Manager for VMware vCenter provides real-time management as a plug-in through the VMware vSphere console and VMware Web Client.

The web client allows you to run OneCommand Manager for VMware vCenter from the vSphere Web client. System performance is directly influenced by the speed and efficiency of the underlying network infrastructure.

Best Installation Practices To avoid network latencies, ensure that all the managed ESXi hosts, the vCenter

Server, and the VI infrastructure client are in the same network. To avoid configuration conflicts, install the vCenter Server and the VI

infrastructure client on different hosts within the same network.

Hardware Requirements Physical or virtual (x86/x86_64) servers with a minimum RAM of 2 Gb/s and

250 Mbps of disk space

Software Requirements Adobe Flash Player 11.2 or later Driver and Firmware Requirements

Note: See the Emulex website for the latest compatible driver and firmware versions.

Emulex CIM Provider Package 10.0 or later Operating system – Windows Server 2008 (32 and 64 bit), Windows 7 (64 bit),

Windows 8 (64 bit), or Windows 2012 (64 bit) vCenter Server 5.1, 5.5, and 6.0 VMware ESXi 5.1, 5.5, and 6.0 environments vSphere Client 5.1, 5.5, and 6.0 vSphere Web Client to manage the VMware vCenter server instead of the

vSphere client


2. Installing and Enabling OneCommand Manager for VMware vCenterInstalling OneCommand Manager for VMware vCenter

26

Note: On the system where OneCommand Manager for VMware vCenter is installed, make sure the port numbers configured during the installation are open and dedicated to the OneCommand Manager for VMware vCenter server only. No other service should be listening on this port.

Installing OneCommand Manager for VMware vCenter

The Emulex CIM Provider must be installed on your ESXi host before installing OneCommand Manager for VMware vCenter. For more information on installing the CIM Provider, see the CIM Provider Package Installation Guide available on the Emulex website.

Note: As part of the OneCommand Manager for VMware vCenter installation, the OneCommand Manager for VMware vCenter Web Client components are installed and registered.

To install OneCommand Manager for VMware vCenter in Windows:

1. From the Emulex website, download the ELXOCM-VMware-vCenter-<version>-Setup.exe installation file to your system.

2. Navigate to the system directory to which you downloaded the file.3. Double-click ELXOCM-VMware-vCenter-<version>-Setup.exe. The OneCommand

Manager for VMware vCenter window appears.4. Click Next. The License agreement window appears.5. Read the agreement and select the I agree to these terms and conditions checkbox

and click Next. The Installation options window with the default Installation folder appears (Figure 2-1 on page 26).

Figure 2-1 Installation options Window



27

6. Ensure that the OCM for VMware vCenter checkbox is selected.7. Program files install by default to c:\Program Files\Emulex. To change this

location, click Browse and navigate to where you want the program files to reside.8. Click Install. The Operation in progress screen appears. When the process is

complete, the OCM for VMware vCenter configuration window appears (Figure 2-2 on page 27).

Figure 2-2 OCM for VMware vCenter configuration Window

Default port numbers for OneCommand Manager for VMware vCenter server are displayed.

Note: The Windows firewall setting must allow incoming connections on the HTTP and HTTPS ports that you configure here.



28

If the port numbers are already in use, a warning appears next to the port number (Figure 2-3 on page 28).

Figure 2-3 OCM for VMware vCenter configuration Window with Port in use Warning

9. Click Next. The Operation in progress screen appears. When the installation process is complete a message prompts you to launch the registration utility.

10. Click Yes. The Register/Unregister dialog box appears in a new browser window (Figure 2-4 on page 28).

Figure 2-4 Register/Unregister Dialog Box

11. Enter the following details of the vCenter Server: vCenter Server Name – The IP address of the vCenter Server. vCenter Server HTTPS Port – The HTTPS port number of the vCenter Server.

Note: The vCenter Server HTTPS port is by default 443. You can change this value if you have configured a different HTTPS port while installing the vCenter.

Username – The user name with required privileges. Password – The user password.



29

12. Click Register to register OneCommand Manager for VMware vCenter with a new vCenter Server.

Notes

You can unregister an existing OneCommand Manager for VMware vCenter by clicking Unregister.

If you change the host name of the machine hosting the vCenter server, you must re-install the vCenter server and re-register.

13. When the operation is successful, a message is displayed. Click OK.14. Close the browser window. The Installation completed window appears. 15. Click Finish. The OneCommand Manager for VMware vCenter Registration icon is

created on the desktop. You do not need to reboot the system.

Verifying the OneCommand Manager for VMware vCenter Installation

To verify OneCommand Manager for VMware vCenter installation:

1. Log in to the vCenter Server through the VMware vSphere console.2. Enter the IP address and credentials of the vCenter Server where OneCommand

Manager for VMware vCenter is registered. The vSphere console appears (Figure 2-5 on page 29).

Figure 2-5 vSphere Console, Getting Started Tab

3. In the vSphere console, select Plug-ins from the menu bar and select Manage Plug-ins. The Plug-in Manager window appears (Figure 2-6 on page 30).


2. Installing and Enabling OneCommand Manager for VMware vCenterActivating and Enabling ESXi Management

30

Figure 2-6 Plug-in Manager Window

4. In the Plug-in Manager window, note the status of OneCommand Manager for VMware vCenter (Emulex OneCommand). If the OneCommand Manager for VMware vCenter installation is complete, the status of Emulex OneCommand is enabled by default.

Activating and Enabling ESXi Management This section describes activating OneCommand Manager for VMware vCenter in the web client, enabling OneCommand Manager for VMware for vCenter Server Appliance (vCSA), and enabling OneCommand Manager for VMware vCenter in the web client.

Note: Refer to the vSphere manual on the VMware website for information on creating a user with required privileges and changing access permissions for a user in the Active Directory.

RequirementsOnly a user with these specific privileges can read and perform active management in OneCommand Manager for VMware vCenter:

“Extension.Register extension” to register OneCommand Manager for VMware vCenter using the registration utility

“Extension.Unregister extension” to unregister OneCommand Manager for VMware vCenter using the registration utility

“Host.CIM.CIM Interaction” to read and manage data through the OneCommand Manager for VMware vCenter

All other users, including the root user, of the ESXi host cannot perform any actions including reading data. If a user without the required privileges attempts to perform an action in OneCommand Manager for VMware vCenter, an error message is displayed.

Note: To configure user roles and assign privileges, refer to the VMware vCenter Server Manual on the VMware website.

Lockdown Mode FeatureRefer to the vSphere manual on the VMware website for information on enabling and disabling lockdown mode.


2. Installing and Enabling OneCommand Manager for VMware vCenterActivating and Enabling ESXi Management

31

If lockdown mode is enabled for an ESXi host, then only a user with the required privileges can access the ESXi host and manage adapters using OneCommand Manager for VMware vCenter. All other users including the root user will not have access to the ESXi host.

Activating OneCommand Manager for VMware vCenter in the Web Client

To activate OneCommand Manager for VMware vCenter, which allows it to be accessed from the Manage tab, you must modify the webclient.properties file on the server where the vSphere web client is installed.

1. Stop the vSphere web client service.2. Locate the webclient.properties file in the vSphere Web Client install directory,

typically %ProgramData%\VMware\vSphere Web Client, and add the following line:

scriptPlugin.enabled = true

3. Save and close the file.4. Restart the vSphere web client service.

Enabling OneCommand Manager for VMware for vCSAvCSA is a preconfigured Linux-based virtual machine that runs the vCenter Server and associated services. vCSA is an alternative for centralized management of VMware vSphere instead of Windows vCenter Server.

To enable OneCommand Manager for VMware vCenter on vCSA:

1. Edit webclient.properties file at: /var/lib/vmware/vsphere-client/webclient.properties

and add the statement:

scriptPlugin.enabled = true

2. Save the file.3. Restart the vSphere Web Client service on the web console.4. Log in to vCSA again.

The Manage tab for the OneCommand Manager for VMware vCenter is now displayed.

Enabling OneCommand Manager for VMware vCenter Web Client

OneCommand Manager for VMware vCenter can be enabled or disabled from the Plug-In Management section in the vSphere Web Client.

Note: You must have sufficient privileges to access the Plug-In Management section. Refer to the VMware documentation for information on configuring users and privileges.


2. Installing and Enabling OneCommand Manager for VMware vCenterEnabling and Disabling OneCommand Manager for VMware vCenter with the Plug-in Manager

32

To enable OneCommand Manager for VMware vCenter in the vSphere Web Client:

1. From the navigation panel on the left-side of the vSphere Web Client Home page, click Plugins > Manage Plug-ins. The Plug-in Manager page is displayed (Figure 2-7 on page 32).

Figure 2-7 vSphere Web Client Plug-In Management Page

2. In the Plug-In Manager page, select com.emulex.Emulex OneCommand and right-click under the Status column. A context menu opens.

3. Select Enable to enable OneCommand Manager for VMware vCenter or select Disable to disable OneCommand Manager for VMware vCenter.

Enabling and Disabling OneCommand Manager for VMware vCenter with the Plug-in Manager

If you enable OneCommand Manager for VMware vCenter, the OneCommand Manager for VMware vCenter functionality immediately appears on the vSphere console. If two or more plug-ins are registered, the Emulex OneCommand sub-tab (under the Classic Solutions tab) immediately appears on the vSphere console. If only one plug-in is registered, the OneCommand Manager for VMware vCenter functionality immediately appears on the Classic Solutions tab.

If you disable OneCommand Manager for VMware vCenter, the OneCommand Manager for VMware vCenter functionality immediately disappears. If two or more plug-ins are registered, the Emulex OneCommand sub-tab immediately disappears from the vSphere console. If only one plug-in is registered, the OneCommand Manager for VMware vCenter functionality immediately disappears from the Classic Solutions tab.

To change the status of OneCommand Manager for VMware vCenter:

1. Log in to the vCenter Server through the VMware vSphere console.2. Enter the IP address and credentials of the vCenter Server where OneCommand

Manager for VMware vCenter is registered. The vSphere console appears.3. In the vSphere console, select Plug-ins from the menu bar and select Manage

Plug-ins. The Plug-in Manager window appears.


2. Installing and Enabling OneCommand Manager for VMware vCenterRegistering and Unregistering OneCommand Manager for VMware vCenter

33

4. Click the Emulex OneCommand row. A context menu appears (Figure 2-8 on page 33).

Figure 2-8 Plug-in Manager with Selected Row

5. Select Enable or Disable.

Registering and Unregistering OneCommand Manager for VMware vCenter

OneCommand Manager for VMware vCenter can be registered with more than one vCenter Server. If you are using the vSphere Web Client, you must verify that the vSphere Web Client and the vCenter server are registered to the same vCenter Single Sign On server to ensure that the vSphere Web Client can access the vCenter server inventory.

To register or unregister OneCommand Manager for VMware vCenter with a new vCenter Server:

1. Double-click the OCM for VMware vCenter Registration icon on the desktop. This icon is created when OneCommand Manager for VMware vCenter is successfully installed. The register/unregister dialog box is displayed (Figure 2-4 on page 28).

2. Enter the following details of the vCenter Server: vCenter Server Name – The IP address of the vCenter Server. vCenter Server HTTPS Port – The HTTPS port number of the vCenter Server. The vCenter Server HTTPS port is by default 443. You can change this value if

you have configured a different HTTPS port while installing the vCenter. Username – The user name with required privileges. Password – The user password.

3. Do one of the following: Click Register to register OneCommand Manager for VMware vCenter with a

new vCenter Server.

-or-

Click Unregister to unregister an existing OneCommand Manager for VMware vCenter with a vCenter Server.


2. Installing and Enabling OneCommand Manager for VMware vCenterUninstalling OneCommand Manager for VMware vCenter

34

Notes

If you change the host name of the machine hosting the vCenter server, you must re-install the vCenter server and re-register.

If the vCenter server is already registered with another instance of OneCommand Manager for VMware server, it is replaced with this server instance.

4. When the operation is successful, a message is displayed. Click OK.5. Close the window.

Uninstalling OneCommand Manager for VMware vCenter

Before you uninstall OneCommand Manager for VMware vCenter, you must unregister it from the vCenter Server. For more information, refer to “Using OneCommand Manager for VMware vCenter” on page 36.

Caution: When you uninstall OneCommand Manager for VMware vCenter, ensure that you do not delete the default configuration and log files that are stored in the %TEMP%\Emulex\OCM for VMware directory. If these files are deleted, all historical information of active management performed from the host is permanently lost.

To uninstall OneCommand Manager for VMware vCenter in a Windows system:

1. Navigate to the system directory to which you downloaded the ELXOCM-VMware-vCenter-<version>-Setup.exe file.

2. Double-click the ELXOCM-VMware-vCenter-<version>-Setup.exe file. The OneCommand Manager for VMware vCenter window prompts you to reinstall/uninstall the application. Select Uninstall the application completely and click Next. A progress window is displayed.

The screen indicating the detection of OneCommand Manager for VMware vCenter appears.

3. Click OK. When uninstallation is complete, the Uninstallation Completed window is displayed.

4. Click Finish. You do not need to reboot the system.

Reinstalling OneCommand Manager for VMware vCenter

To reinstall OneCommand Manager for VMware vCenter in a Windows system:

1. Navigate to the system directory to which you downloaded the ELXOCM-VMware-vCenter-<version>-Setup.exe file.


2. Installing and Enabling OneCommand Manager for VMware vCenterReinstalling OneCommand Manager for VMware vCenter

35

2. Double-click ELXOCM-VMware-vCenter-<version>-Setup.exe. The OneCommand Manager for VMware vCenter window prompts you to reinstall/uninstall the application.

3. Select Re-install the application and click Next. A progress window is displayed. The OCM for VMware vCenter window appears.

4. Click Next. The License agreement screen appears.5. Read the agreement and select the I agree to these terms and conditions checkbox

and click Next. The Installation Options window with the previous installation folder location appears (see Figure 2-1 on page 26).

6. Ensure that the OCM for VMware vCenter checkbox is selected.7. To change the installation folder location, click Browse and navigate to where you

want the program files to reside.8. Click Install on the Installation Options window. The operation in progress

window appears. When the installation process is complete, the OneCommand Manager for VMware vCenter configuration window appears (Figure 2-9 on page 35).

Figure 2-9 Reinstallation Configuration Dialog Box

If OneCommand Manager for VMware vCenter was installed earlier with port numbers other than the defaults provided, those configured ports are shown. If the port numbers are already in use, a warning appears next to the port number.

Note: The Windows firewall setting must allow incoming connections on the HTTP and HTTPS ports that you configure here.

9. Follow the on-screen instructions and complete the installation with steps 9 to 14 of “Installing OneCommand Manager for VMware vCenter” beginning on page 26.


3. Using OneCommand Manager for VMware vCenterAccessing with VMware Web Client 6.0

36

3. Using OneCommand Manager for VMware vCenter

Note: To increase the size of the OneCommand Manager for VMware screen, the Recent Tasks panel on the right can be unpinned and collapsed.

OneCommand Manager for VMware vCenter is available at the host level and the cluster level in the vSphere inventory list.

Accessing with VMware Web Client 6.0After you are logged into the VMware Web Client, the OneCommand Manager for VMware vCenter version 6.0 is under the Manage tab for a particular host or cluster that you select in the vSphere client. When the Emulex OneCommand tab is loaded, the functionality and features available are the same as those for the OneCommand Manager for VMware vCenter available for vSphere console.

To launch the OneCommand Manager for VMware vCenter Web Client:

1. Log in to the vSphere Web Client. The vSphere Web Client home page is displayed.2. Navigate to an ESXi host or cluster in the Navigation pane.3. From the Host level view, select the host you want to display.

-or-

From the Cluster level view, select the cluster you want to display.

4. Go to the Manage tab to access the OneCommand Manager for VMware vCenter.

Accessing with VMware Web Client Versions 5.5 and 5.1

After you are logged into the vSphere client, the OneCommand Manager for VMware vCenter version 5.5 or version 5.1 is under the Classic Solutions tab for a particular host or cluster that you select in the vSphere client. When the Classic Solutions tab is loaded, the functionality and features available are the same as those for the OneCommand Manager for VMware vCenter available for vSphere console.

To launch the OneCommand Manager for VMware vCenter Web Client:

1. Log in to the vSphere Web Client. The vSphere Web Client home page is displayed.2. Navigate to an ESXi host or cluster in the Navigation pane.3. From the Host level view, select the host you want to display.

-or-

From the Cluster level view, select the cluster you want to display.

4. Go to the Classic solutions tab to access the OneCommand Manager for VMware vCenter.


3. Using OneCommand Manager for VMware vCenterAccessing the vSphere Console

37

Note: If OneCommand Manager for VMware vCenter is the only plug-in registered on the vCenter server, the tab title “Emulex OneCommand” does not appear under the Classic Solutions tab. OneCommand Manager for VMware vCenter directly loads under the Classic Solutions tab with no title. The “Emulex OneCommand” plug-in is shown as a sub tab only if two or more plug-ins are registered.

Accessing the vSphere ConsoleTo access the vSphere console:

1. Log in to the VMware vSphere Client.a. Double-click the VMware vSphere Client icon.b. Enter the credentials and click Login.c. Select a cluster or host in the vSphere console tree-view and if applicable, click

the Emulex OneCommand tab to perform active management on a cluster or a host.

Note: If OneCommand Manager for VMware vCenter is the only plug-in registered on the vCenter server, the tab title “Emulex OneCommand” does not appear under the Classic Solutions tab. OneCommand Manager for VMware vCenter directly loads under the Classic Solutions tab with no title. The “Emulex OneCommand” plug-in is shown as a sub tab only if two or more plug-ins are registered.

2. A Security Alert is displayed, click Yes. The vSphere console is displayed.

vSphere Console ViewsThe vSphere console supports two views, cluster view and host view.

The difference between the two views is the Emulex Device Management area; which may contain options or a tree-view.

In a cluster view, you can view fabric-centric, or host-centric information, about all the hosts in a cluster. Figure 3-1 on page 38 shows the Emulex Device Management options available in a host-centric cluster view. You can perform active management simultaneously on a fabric or a group of hosts belonging to a cluster.

In a host view, you can only view information about a single host. Figure 3-2 on page 39 shows the Emulex Device Management tree-view elements for a selected host. In the host view, in addition to selecting an element in the tree-view, you must also select a tab in the information pane to view the information for the element selected in the tree-view.

Notes

A host can be managed by only one vCenter Server at a time. The OneCommand Manager for VMware vCenter user interface is auto

refreshed every five minutes.



38

To access the cluster view:

Select a cluster in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab. The cluster view appears (Figure 3-1 on page 38).

To access the host view:

Select a host in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab. The host view appears (Figure 3-2 on page 39).

In both cluster and host views, the OneCommand Manager for VMware vCenter window consists of three major parts:

The Emulex Device Management area. The Information pane corresponding to the option or element selected in the

Emulex Device Management area. The About area shows version information about the Emulex OneCommand

Manager for VMware vCenter.

OneCommand Manager for VMware vCenter Window Elements

The OneCommand Manager for VMware vCenter window (Figure 3-1 on page 38 and Figure 3-2 on page 39) contains four basic components: the Emulex Device Management area, the information pane, the console buttons, and the filter options menu (if applicable).

Figure 3-1 Cluster View with Callouts



39

Figure 3-2 Host View with Callouts

Emulex Device Management Area

In a cluster view, the Emulex Device Management area contains links that determine what is displayed in the Information pane.

In a host view, the Emulex Device Management area is a discovery-tree with icons that represent discovered hosts, adapters, ports, virtual ports, fabrics, targets, and LUNs.

OneCommand Tabs

In a host view, The OneCommand tabs display configuration, statistical, and status information for network elements.

Information Pane

In a cluster view, the information pane shows information based upon what is selected in the Emulex Device Management area.

In a host view, the information pane shows information based upon the OneCommand tab that is selected.

Filter Options Menu

In a cluster view, selecting an item from the Filter Options menu will show information that is sorted and displayed based upon by the item selected.



40

Console buttons

Help – Click to load the complete indexed online help for OneCommand Manager for VMware vCenter. You can search for information for all OneCommand Manager for VMware vCenter tabs and functions.

Preferences – Click to access the User Preferences window. The User Preference window is available in host view only. In the User Preferences window, select the Event Logging checkbox to show up or down events for FC, FCoE and iSCSI ports logged into the vSphere console. NIC port events are not logged, as VMware already does this. FC, FCoE and iSCSI port events are limited to the active vCenter client. If the same user login is used from another vCenter client, the User Preference window does not show these events.

Refresh – Click to refresh cluster or host information. The User Preferences window logs only up and down events for the port. Other

events, such as temperature, are not posted.


4. Managing Clusters and HostsManaging Clusters

41

4. Managing Clusters and HostsThis section pertains to viewing cluster and host information.

Managing ClustersFrom within a cluster, you can view information about:

Hosts in a cluster Adapters belonging to hosts in a cluster Physical ports in host-centric mode Virtual ports in host-centric mode Physical ports in fabric-centric mode

Figure 3-1 on page 38 shows the main elements of the cluster view.

Viewing Hosts in a Cluster

Note: Hosts in a cluster with different provider versions support features as listed in Table 1-1, Support Provided by Emulex CIM Provider Versions, on page 19.

To view information about hosts in a cluster:

1. Select a cluster in the vSphere console tree-view. The Getting Started tab is selected by default.

2. If applicable, select the Emulex OneCommand tab, the Hosts information pane is displayed (Figure 4-1 on page 42).

To filter information for a host within a cluster field:

1. Use the Filter list to filter information. a. Search by any column title by selecting the title from the Filter list.b. To further narrow the search, enter a value in the field to the right of the Filter

list. You can also enter a wildcard for this field.c. Click Search.

2. Click Clear to clear the search criteria.3. Click Refresh to refresh the information. If a host is added to the currently selected

cluster, the host information is refreshed.



42

Figure 4-1 Hosts within a Cluster

Hosts within a Cluster, Field Definitions IP Address – The IP address of the host in the cluster. Operating System – The OS and version installed on the host. Drivers – The drivers and their versions installed on the host. CIM Provider Version – The version of the Emulex CIM Provider that is

running on the ESXi host. Adapters – The number of adapters installed in the host. Fabrics – The number of fabrics to which the host is connected. Ports – The number of discovered physical ports that can be managed by the

host. Lock Down Mode – Specifies if lockdown mode is enabled or disabled.

Viewing Adapters in a ClusterTo view information about adapters belonging to a host in a cluster:

1. Select a cluster in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab.

2. From the Emulex Device Management options, select Adapters. Adapters information is displayed (Figure 4-2 on page 43).

To filter adapter information within a cluster:

1. Use the Filter list to filter the adapter information. Choose any of the available adapter information fields from the list and enter a wildcard for the field and click Search.

2. Click Clear to clear the search criteria and the corresponding adapter information.



43

3. Click Refresh to refresh the information. If an adapter is added to any of the hosts, the adapter information is refreshed.

Figure 4-2 Adapters within a Cluster

Adapters within a Cluster, Field Definitions Adapter Model – The model of the adapter. Serial Number – The serial number of the adapter. Hardware Version – For FC adapters this field shows the JEDEC ID. For CNAs,

this field shows the board type and code version. Description – The type of adapter.

Viewing Physical Ports in a Cluster (Host-centric mode)To view information about a physical port that is in a cluster, in host-centric mode:

1. Select a cluster in the vSphere console tree-view.2. Select the Emulex OneCommand tab. Hosts information is displayed.3. From the Emulex Device Management options, select Ports. The host-centric

information pane is displayed (Figure 4-3 on page 44 and Figure 4-4 on page 44).

Note: Make sure the Group by Fabric checkbox is cleared.



44

Figure 4-3 Physical Ports within a Cluster, Host-centric View

Figure 4-4 Close-Up of Physical Ports within a Cluster, Host-centric View

Physical Ports within a Cluster, Host-centric Field Definitions Port WWN – The port World Wide Name. Link Status – The status of the link on the selected port. Fabric – This is a 64-bit worldwide unique identifier assigned to the fabric. Driver Name – The executable file image name for the driver as it appears in the

Emulex driver download package.



45

Driver Version – The version of the installed driver. Active FW Version – The active FW version. Flash FW Version – The FW version that will become active after the system is

rebooted.

Viewing Virtual Ports in a Cluster (Host-centric mode)To view information about a virtual port that is in a cluster, in host-centric mode:

1. Select a cluster in the vSphere console tree-view.2. If applicable, select the Emulex OneCommand tab. Port host information is

displayed.3. From the Emulex Device Management options, select vPorts. The virtual port

information is displayed (Figure 4-5 on page 45).

To filter virtual port information in a cluster:

1. Use the Filter list to filter the port information. 2. Choose any of the available host information fields from the list and enter a

wildcard for the field and click Search.3. Click Clear to clear the search criteria.

Figure 4-5 Virtual Ports in a Cluster, Host-centric View

Virtual Ports in a Cluster, Host-centric Field Definitions vPort WWN – The virtual port World Wide Name. vPort Node WWN – The virtual port node World Wide Name. vPort FCID – The virtual port FC ID. vPort Name – The virtual port name. Target Ports – The number of target ports. Virtual Machine – Virtual machine information.



46

Viewing Physical Port Information in a Cluster (Fabric- centric mode)

To view physical port information in a cluster, in fabric-centric mode:

1. Select a cluster in the vSphere console tree-view.2. Select the Emulex OneCommand tab, host information is displayed.3. From the Emulex Device Management options, select Ports. The host-centric

information pane is displayed.4. Select the Group by Fabric checkbox. Fabric information is displayed (Figure 4-6

and Figure 4-7 on page 47).

Figure 4-6 Information for a Physical Port in a Cluster, Fabric-Centric View

Note: iSCSI and NIC ports are not attached to any fabric, so they are listed under “No Fabric Attachment”.



47

Figure 4-7 Close-up of Information for a Physical Port in a Cluster, Fabric-Centric View

Fabric-centric Information Field Definitions Port WWN – The port World Wide Name. Host – The host IP address. Adapter – The adapter model. Link Status – The status of the link on the selected port. Driver Name – The executable file image name for the driver as it appears in the

Emulex driver download package. Driver Version – The version of the installed driver. Active FW Version – The active FW version. Flash FW Version – The FW version that will become active after the system is

rebooted.


4. Managing Clusters and HostsManaging Hosts

48

Managing HostsHost information includes:

Information for a single host Driver parameters for all adapters in a host Firmware information for all adapters in a host

Figure 3-2 on page 39 shows the main elements of the host view.

Viewing Host Information for a Single HostTo view host information for a single host:

1. Select a host in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab. The Host Information tab is selected by default and the information of the selected host appears (Figure 4-8 on page 48).

To filter the host information:

1. Use the Filter list to filter the fabric information. 2. Choose any of the available fabric information fields from the list and enter a

wildcard for the field and click Search.3. Click Clear to clear the search criteria.

Figure 4-8 Information for a Single Host

Host Information Field Definitions Host Name – The host identifier. Number of Adapters – The number of adapters installed in the host. Number of Fabrics – The number of fabrics to which the host is connected. Operating System – The OS and version installed on the selected host. Lock Down Mode – Indicates whether lockdown mode is enabled or disabled.



49

IP Address – The IP address of the host. Number of Ports – The number of discovered physical ports that can be

managed by this host. Number of Target Ports – The number of targets discovered across the ports. CIM Provider Version – The versions of the Emulex CIM Providers that are

running on the ESXi host.

Function Summary Area

NIC Functions – The number of NIC functions running on the discovered adapters on this host.

FC/FCoE

FC Functions – The number of FC functions running on the discovered adapters on this host.

FCoE Functions – The number of FCoE functions running on the discovered adapters on this host.

FC Targets – The number of FC targets discovered on the FC/FCoE functions on this host.

iSCSI

iSCSI Functions – The number of iSCSI functions running on the discovered adapters on this host.

iSCSI Targets –The number of iSCSI targets discovered on the iSCSI functions on this host.

Viewing Driver Parameters of All Adapters in a HostThe host Driver Parameters tab enables you to view and edit the adapter driver parameter settings for a specific host. The host driver parameters are global values and apply to all adapters in that host unless they are overridden by parameters assigned to a specific adapter using the port Driver Parameters tab. For each parameter, the information pane shows the current value, the range of acceptable values, the default value, and whether the parameter is dynamic. A dynamic parameter allows the change to take effect without resetting the adapter or rebooting the system. For information on changing parameters for the host, refer to “Setting Driver Parameters for an FC/FCoE Port” on page 131.

Note: If there are no discovered FC or FCoE adapters, the driver parameters table is empty. This occurs because there are no adapters to which the host driver parameters apply.

To view driver parameters for all adapters in a host:

1. Select a host in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab.

2. Select the Driver Parameters tab (Figure 4-9 on page 50).



50

Figure 4-9 Host Driver Parameters

Host Driver Parameters Tab Field Definitions Installed Driver Type – The current driver installed on this host. Driver Parameter table – A list of adapter driver parameters and their current

values.

Driver parameter specific information is displayed in this area. This includes value, range, default, activation requirements and description.

Parameter – The name of the driver parameter. Value – The value of the driver parameter. Temporary – Indicates if the value can be set temporarily at port level. Range – The range of acceptable values for the driver parameter. Default – The default value of the parameter. Activation Requirements – The steps required to activate the changed

value of the driver parameter. Description – The description of the driver parameter.

Host Driver Parameter Tab Buttons

Restore – Click if you changed parameters, but did not click Apply and you want to restore the parameters to their last saved values.

Defaults – Click to reset all parameter values to their default (factory) values. Apply – Click to apply the global values.



51

Viewing Firmware Information for All Adapters in a Host For updating firmware, see “Updating Firmware on FC Adapters in a Host” on page 154. The host Maintenance tab enables you to view and update firmware on multiple adapters in a specific host.

To view firmware for all adapters in a host:


2. Select the Maintenance tab (Figure 4-10 on page 51).

Figure 4-10 Host Maintenance Tab

Host Maintenance Tab Field Definitions Adapter – The model of the adapter. Port – The port WWN. Active FW Version – The current FW on the adapter. Flash FW Version – The flashed FW on the adapter. Shows n/a for FC ports.

Host Maintenance Tab Buttons

Update Firmware – Click to update firmware on the selected adapter.


5. Managing Adapters and PortsFC/FCoE Adapters

52

5. Managing Adapters and PortsThis section describes the various adapter and port management functions you can perform using OneCommand Manager for VMware vCenter.

FC/FCoE AdaptersThis section pertains to viewing FC/FCoE adapter and port information.

Viewing FC and FCoE Port InformationWhen you select an FC adapter from the Emulex Device Management tree-view, the Adapter Information pane contains general attributes associated with the selected FC adapter.

To view information for an FC adapter:


2. In the Emulex Device Management tree-view, select an FC adapter. The adapter Information tab is displayed (Figure 5-1 on page 52).

Figure 5-1 FC Adapter Information Tab

FC Adapter Information Field Definitions Model – The complete model name of the adapter. Manufacturer – The manufacturer of the adapter. Serial Number – The manufacturer's serial number for the selected adapter. HW Version – For LightPulse adapters, this field shows the JEDEC ID. Device ID – The default device ID for the selected adapter. Adapter Temperature

Normal – The adapter’s temperature is within normal operational range. Exceeded operational range – Critical: The adapter’s temperature is beyond

normal operational range. If the temperature continues to increase, the adapter shuts down. You must determine the cause of the temperature issue and fix it immediately. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperable fans and air conditioning issues that cause high ambient air temperatures.



53

Exceeded operational range – Adapter stopped. The temperature has reached critical limit, forcing the adapter to shut down. You must determine the cause of the temperature issue and fix it before resuming operation. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperable fans and air conditioning issues that cause high ambient air temperatures.

Not Supported - The adapter temperature is not available. 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 FC Port Details and Changing Link StateWhen you select an FC port from the Emulex Device Management tree-view, the Port Details tab contains general attributes associated with the selected FC adapter. A button in the Port Status area enables you to disable or enable the port. This button toggles between Disable and Enable, depending upon the current status of the physical port.

To view details for an FC port:


2. In the Emulex Device Management tree-view, select the FC port whose information you want to view.

3. The Port Details tab is displayed (Figure 5-2 on page 53).

Figure 5-2 FC Port Details Tab

FC Port Details Tab Field Definitions

Port Attributes Area

Port WWN – The port World Wide Name of the selected adapter. Node WWN – The node World Wide Name of the selected adapter.



54

Fabric Name – The Fabric Name is a 64-bit worldwide unique identifier assigned to the fabric.

Boot Version – The version of boot code installed on the selected adapter port. If the boot code is disabled, the field shows “Disabled”.

Port FCID – The FC ID of the selected adapter port. PCI Function – The PCI function number of the selected port. PCI Bus Number – The PCI bus number. Driver Version – The version of the driver installed for the adapter. Driver Name – The executable file image name for the driver as it appears in the

Emulex driver download package. Firmware Version – The version of Emulex firmware currently active on the

adapter port. 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. OS Device Name – The platform-specific name by which the selected adapter is

known to the operating system. Symbolic Node Name – The FC name used to register the driver with the name

server. Supported Class of Service – A frame delivery scheme exhibiting a set of

delivery characteristics and attributes. There are three classes of service. Class 1 provides a dedicated connection between a pair of ports with

confirmed delivery or notification of non-delivery. Class 2 provides a frame switched service with confirmed delivery or

notification 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

The Link Status field indicates the status of the link on the selected adapter port.

FC Port Details Tab Buttons

The Enable Port/Disable Port button toggles between Disable Port and Enable Port, depending upon the current status of the physical port.

Port Speed Area

The Port Speed field indicates the current port speed of the selected adapter port.



55

Viewing FCoE Port DetailsUse the Port Details tab to view general attributes associated with the selected FCoE port.

To view port details for an FCoE port:


2. In the Emulex Device Management tree-view, select the FCoE port whose details you want to view.

3. Select the Port Details tab (Figure 5-3 on page 55).

Figure 5-3 FCoE Port Details Tab

FCoE Port Details Field Definitions

Port Attributes Area

Port WWN – The port World Wide Name of the adapter. Node WWN – The node World Wide Name of the selected adapter. Fabric Name – The Fabric Name field is displayed in Host view. This is a 64-bit

worldwide unique identifier assigned to the fabric. The host name is the name of the host containing the adapter.

Boot Version – The version of boot code installed on the selected adapter port. If the boot code is disabled, the field shows “Disabled”.

Port FCID – The FCoE ID for the selected adapter port. PCI Function – The PCI function number assigned by the system. PCI Bus Number – The PCI bus number. Driver Version – The version of the driver installed for the adapter. Driver Name – The executable file image name for the driver as it appears in the

Emulex driver download package.



56

Firmware Version – The version of Emulex firmware currently active on the adapter port.

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. OS Device Name – The platform-specific name by which the selected adapter is

known to the operating system. Symbolic Node Name – The FC name used to register the driver with the name

server. Supported Class of Service – A frame delivery scheme exhibiting a set of

delivery characteristics and attributes. There are three classes of service. Class 1 provides a dedicated connection between a pair of ports with

confirmed delivery or notification of non-delivery. Class 2 provides a frame switched service with confirmed delivery or

notification 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

Link Status – The status of the link on the selected adapter port. LinkDown Reason - The reason for the Link Status on the selected port.

Port Speed Area

Port Speed – The current port speed of the selected adapter port. Bandwidth Limit – The QoS bandwidth restriction on the port.

Viewing FC/FCoE Port Driver ParametersThe Driver Parameter’s tab shows driver parameters for a port.

To view driver parameters for a port:


2. In the Emulex Device Management tree-view, select the port whose driver parameters you want to view.

3. Select the Driver Parameters tab (Figure 5-4 on page 57).



57

Figure 5-4 FC/FCoE Port Driver Parameters Tab

FC/FCoE Driver Parameters Tab Field Definitions Installed Driver Type – The current driver installed on this host. Port Parameter table – A list of port driver parameters and their current values.

Parameter – The driver parameter’s name. Value – The driver parameter’s value. Temporary – Indicates if the value is temporary. Range – The range of acceptable values for the driver parameter. Default – The driver parameter’s default value. Activation Requirements – The steps required to activate the changed value

of the driver parameter. Description – The driver parameter’s description.

FC/FCoE Driver Parameters Tab Buttons

Globals – Click to set a port parameter value to the corresponding host parameter value. All parameter values will be the same as the global, or host, values.

Restore – Click if you changed parameters, but did not click Apply and you want to restore the parameters to their last saved values.

Defaults – Click to reset all parameter values to their default (factory) values. Apply – Click to apply the global values. Export – Click to save a desired port parameter configuration.



58

Viewing FC/FCoE Port Statistics When you select an FC/FCoE port from the discovery-tree, the Port Statistics tab shows cumulative totals for error events and statistics on the port. Some statistics are cleared when the adapter is reset.

To view statistics for a port:


2. In the Emulex Device Management tree-view, select the port whose statistics you want to view.

3. Select the Statistics tab (Figure 5-5 on page 58).

Figure 5-5 FC/FCoE Port Statistics Tab

FC/FCoE Port Statistics Tab Field Definitions Tx Frames – The FC frames transmitted by this adapter port. Tx Words – The FC words transmitted by this adapter port. Tx KB Count – The FC kilobytes transmitted by this adapter port. Tx Sequences – The FC sequences transmitted by this adapter port. LIP count – The number of LIP events that have occurred for the port. This field

is supported only if the topology is arbitrated loop. Loop initialization consists of the following: Temporarily suspending loop operations. Determining whether loop capable ports are connected to the loop. Assigning AL_PA IDs. Providing notification of configuration changes and loop failures. Placing loop ports in the monitoring state.



59

Error Frames – The number of frames received with cyclic redundancy check (CRC) errors.

Link Failures – The number of times the link has failed. A link failure can cause a timeout.

Loss of Signal – The number of times the signal was lost. Invalid Tx Words – The total number of invalid words transmitted by this

adapter port. Ex Count Orig – The number of FC exchanges originating on this port. Active XRIs – The number of active exchange resource indicators. Received P_BSY – The number of FC port-busy link response frames received. Link Transitions – The number of times the SLI port sent a link attention

condition. Elastic Buf Overruns – The number of times the link interface has had its elastic

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 port. Rx KB Count – The received kilobyte count by this adapter port. Rx Sequences – The number of FC sequences received by this adapter port. NOS count – The number of NOS events that have occurred on the switched

fabric (not supported for an arbitrated loop). Dumped Frames – The number of frames that were lost due to a lack of host

buffers available. Loss of Sync – The number of times loss of synchronization has occurred. Prim Seq Prot Errs – The primitive sequence protocol error count. This counter

is incremented 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 responses made by this port. Active RPIs – The number of remote port indicators. Receive F_BSY – The number of FC port-busy link response frames received. Primitive Seq Timeouts – The number of times a primitive sequence event timed

out. Arbitration Timeouts – The number of times the arbitration loop has timed out.

Large counts could indicate a malfunction somewhere in the loop or heavy usage of the loop.



60

Viewing FC Port Transceiver InformationThe Transceiver Data tab shows transceiver information such as vendor name, serial number, and part number. If the adapter/transceiver does not support some or all of the transceiver data, the fields display N/A.

To view transceiver information for an FC port:


2. In the Emulex Device Management tree-view, select the FC port whose transceiver information you want to view.

3. Select the Transceiver Data tab (Figure 5-6 on page 60).

Figure 5-6 FC Port Transceiver Tab

Transceiver Information Field Definitions

Module Attributes Area

Vendor – The name of the vendor. Identifier/Type – A value that specifies the physical device described by the

serial information. Ext. Identifier – Additional information about the transceiver. 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 Organizationally Unique Identifier. It is also known as the

IEEE Company Identifier for the vendor. Date – The vendor’s date code in the MM/DD/YY format. Serial Number – The serial number provided by the vendor. Part Number – The part number provided by the SFP vendor.



61

Revision – The vendor revision level.

Diagnostic Data Area

Temperature – The internally measured module temperature. Supply Voltage – The internally measured supply voltage in the transceiver. Tx Bias Current – The internally measured Tx bias current. Tx Output Power – The measured Tx output power. Rx Input Power – The measured Rx input power.

Viewing FC/FCoE Port Vital Product Data (VPD)The VPD tab shows vital product data (if available) for the selected FC/FCoE port such as the product name, part number, serial number, and so on.

To view VPD information for a port:


2. In the Emulex Device Management tree-view, select the port whose VPD information you want to view.

3. Select the VPD tab (Figure 5-7 on page 61).

Figure 5-7 Port VPD Tab

VPD Table Definitions Part Number – The adapter's part number. Product Name – The product information about the selected adapter port. 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 and MN.



62

Viewing FC/FCoE Port Maintenance and Firmware Information

The Maintenance tab shows firmware information for an FC/FCoE port.

To view firmware information for a port:


2. In the Emulex Device Management tree-view, select the FC/FCoE port whose firmware information you want to view.

3. Select the Maintenance tab for the FC port (Figure 5-8 on page 62) or the FCoE port (Figure 5-9 on page 62).

Figure 5-8 FC Port Maintenance Tab

Figure 5-9 FCoE Port Maintenance Tab



63

Maintenance Tab Field Definitions

FC Port Firmware Area

Current Version – The Emulex firmware version number for this adapter. Initial Load – The firmware version stub responsible for installing SLI code into

its proper slot. SLI-2 Name – The name of the SLI-2 firmware overlay. Kernel Version – The version of the firmware responsible for starting the driver. Operational Name –The name of the operational firmware for the adapter. SLI-1 Name – The name of the SLI-1 firmware overlay. SLI-3 Name – The name of the SLI-3 firmware overlay.

FCoE Port Firmware Area

Firmware Version on Flash – The firmware version stored on the adapter’s non-volatile storage. When the system restarts, this version becomes the active firmware version.

Service Processor FW Version – The operational FW version on the adapter. Active Firmware Version – The FW version running on the selected adapter. ULP FW Name – The FW version running on the ULP processors within the

ASIC.

WWN Management Area (FC and FCoE)

Current

WWPN – The WWPN for the selected adapter port. WWNN – The WWNN for the selected adapter port.

Pending Changes

WWPN – If the WWPN has been changed, the new WWPN is displayed in this list until the system is rebooted. After rebooting, the new WWPN is displayed in the Current list.

WWNN – If the WWNN has been changed, the new WWNN is displayed in this list until the system is rebooted. After rebooting, the new WWNN is displayed in the Current list.

Maintenance Tab Buttons (FC and FCoE)

Change WWN – Click to change the selected adapter port's WWPN or WWNN. Refer to “Changing WWN Configuration for an FC Port” on page 127 for more information.

Reset – Click to reset the adapter port. Refer to “Viewing FC/FCoE Port Driver Parameters” on page 56 for more information.

Maintenance Tab Buttons (FC only)

Update Firmware – Click to update firmware on the selected port.



64

Viewing FC/FCoE Target InformationWhen you select a port target associated with an FC/FCoE adapter from the Emulex Device Management tree-view, the Target Information tab shows information associated with that target.

To view FC/FCoE target information:

1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab.

2. In the Emulex Device Management tree-view, select the FC/FCoE target port whose information you want to view. The Target Information tab appears.

Figure 5-10 Target Information Tab

Target Information Field Definitions FC ID – The FC ID for the target; assigned automatically in the firmware. SCSI Bus Number – The SCSI bus number to which the target is mapped. SCSI Target Number – The target's identifier 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 device name

Viewing FC/FCoE LUN InformationWhen you select a LUN associated with an FC/FCoE adapter from the Emulex Device Management tree-view, the LUN Info pane shows information associated with that LUN.

To view LUN information:


2. In the Emulex Device Management tree-view, select the FC/FCoE LUN whose information you want to view. The corresponding LUN Info pane is displayed (Figure 5-11 on page 65).



65

Figure 5-11 FC/FCoE LUN Information

FC/FCoE 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-specific revision number for the LUN.

Mapping Information Area

FCP LUN – The FC identifier used by the adapter to map to the OS LUN. SCSI OS LUN – The SCSI identifier used by the operating system to map to the

specific LUN. OS Device Name – The name assigned by the operating system to the LUN.

LUN Capacity Area

LUN capacity information is only provided when the LUN is a mass-storage (disk) device. Other devices such as tapes and scanners do not display capacity.

Capacity – The capacity of the LUN, in megabytes. Block Size – The length of a logical unit block in bytes.

LUN Masking Information Area

Current Mask Status - The current status is masked or unmasked.

The adapter information that is displayed depends upon the type of adapter you select; LightPulse (FC) or OneConnect.



66

Viewing PCI Registers for an FC PortThe PCI Registers tab shows PCI information, including PCIe details, about the selected FC port.

Note: The PCI fields may vary with the type of adapter installed.

To view PCI registers for an FC port:


2. In the Emulex Device Management tree-view, select the FC port whose PCI information you want to view.

3. Select the PCI Registers tab (Figure 5-12 on page 66).

Figure 5-12 FC Port PCI Registers Tab



67

Viewing PCI Registers for an FCoE PortThe PCI Registers tab shows PCI information about the selected FCoE port.

To view PCI registers for an FCoE port:


2. In the Emulex Device Management tree-view, select the FCoE port whose PCI information you want to view.


Figure 5-13 FCoE Port PCI Registers Tab



68

Viewing Flash Contents for an FC PortTo view the flash contents for an FC port:


2. In the Emulex Device Management tree-view, select the FC port whose Flash contents you want to view.

3. Select the Flash Contents tab. The Flash Contents information is displayed (Figure 5-14 on page 68).

Figure 5-14 FC Port Flash Contents

4. Select the Show Wakeup Images Only checkbox if you want to see only the flash contents with the wake-up images.

Viewing DCB Parameters for FCoE Adapter PortsTo view the DCB parameters for FCoE adapter ports:


2. In the Emulex Device Management tree-view, select the FCoE adapter port whose DCP properties you want to configure.

3. Select the DCB tab (Figure 5-15 on page 69).



69

Figure 5-15 DCB Tab (FCoE Adapter Port Selected)

DCB Tab Field Definitions DCBX State – The current DCBX state (enabled or disabled). LLDP Transmit 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.

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

Active Priorities – Lists the priorities with PFC that are set to Enabled. Sync'd – If set to Yes, the PFC priorities have been set by the peer. This

parameter cannot be set. Error – The error state. This capability indicates whether an error has occurred

during the configuration exchange with the peer. Error is also set to YES when the Compatible method for the capability fails.

Protocol Properties Area

State – The FCoE state. It can be enabled or disabled. Sync'd – If yes, the FCoE priority has been set by the peer. This parameter

cannot be set.


5. Managing Adapters and PortsOneConnect Adapters

70

Error – The FCoE error state. This capability indicates whether an error has occurred during the configuration exchange with the peer. Error is also set to YES when the Compatible method for the capability fails.

iSCSI Priority and FCoE Priority – Protocol properties, as applicable.

ETS Priority Group Properties Area

Note: Not shown when UMC is enabled on the adapter.

State – The FCoE or NIC-only 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 error state. This capability indicates whether an error has occurred

during the configuration exchange with the peer. Error is also set to YES when the Compatible method for the capability fails.

Active Groups

Group ID–The Priority Group number. It can be 0 to 7. Priority Membership – The priorities that are assigned to each Priority

Group. It is represented in comma separated format. Bandwidth% – The percentage of available link bandwidth allocated to a

particular Priority Group.

DCB Tab Buttons

Configure DCB – Click to configure DCB parameters. See the instructions that follow.

OneConnect AdaptersThis section pertains to viewing OneConnect adapter information, as well as installing licenses, configuring personalities, configuring parameters, and managing channels.

Viewing OneConnect Adapter InformationThe Adapter Information tab contains general attributes associated for the selected CNA. You can also use this tab to view and enable licenses. See “Viewing FC Port Details and Changing Link State” on page 53 for more information.

To view OneConnect adapter information:


2. In the Emulex Device Management tree-view, select a OneConnect adapter. The Adapter Information tab is displayed (Figure 5-16 on page 71).



71

Figure 5-16 OneConnect Adapter Information Tab

Adapter Information Tab Field Definitions Model – The model of the selected adapter. Manufacturer – The manufacturer of the adapter. Serial Number – The serial number of the selected adapter. Active Firmware Version – The firmware version running on the adapter. 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. HW Version – The HW version of the selected adapter. NCSI Version – The NCSI version. IPL File Name – The name of the IPL file currently loaded. PCI Express Link Speed – The PCI bus speed in which the adapter running. PCI Express Bus Width – The number of lanes for the slot in which the adapter

is running. Adapter Temperature – If the adapter's temperature is not available, “Not

Supported” is displayed. If supported by the adapter, this field shows the adapter's temperature and one of the following temperature-related status messages: Normal: The adapter’s temperature is within normal operational range. Warning: The adapter’s temperature is beyond normal operational range. If

the temperature continues to increase, the adapter shuts down. You must



72

determine the cause of the temperature issue and fix it immediately. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperable fans and air conditioning issues that cause high ambient air temperatures.

Exceeds operational range – Adapter stopped: The temperature has reached critical limit, forcing the adapter to shut down. You must determine the cause of the temperature issue and fix it before resuming operation. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperable fans and air conditioning issues that cause high ambient air temperatures.

After a system overheating issue is resolved and the adapter is cooled down, reboot the system or, if the system supports hot swapping, cycle the power of the adapter slot.

Personality Area

The Current field indicates the current personality in use by the adapter.

After Reboot Area

You can change the current personality of the adapter by clicking one of the following:

FCoE – Click to choose the FCoE personality. iSCSI – Click to choose the iSCSI personality. NIC Only – Click to choose the NIC only personality.

Channel Management Area (OCe11100–Series Adapters Only)

You can enable or disable channel management for an entire adapter and select the channel management mode from the Channel Management area.

Current Management Type – Shows the currently active channel management mode.

Management Type After Reboot – Changes the channel management mode when you select a channel management mode from the list. Select None from the list to disable channel management and click Apply.

License Features Area

Shows the available personalities. Shows the status of the available personalities.

Adapter Information Tab Buttons

Apply – Click to apply save any changes that you have made. After Reboot – Click to apply the selected personality. Management Type After Reboot – Click to apply the selected Management

Type After Reboot. Install Feature Licenses – Click to install licenses.



73

Viewing LicensesTo view available licenses for an OCe11100-series adapter:


2. In the Emulex Device Management tree-view, select an adapter whose licenses you want to view.

3. Select the Adapter Information tab (Figure 5-16 on page 71).

License information is displayed in the License Features area. The table shows the available licenses and whether they are licensed or not.

Note: An empty feature list means the adapter has no licensable capabilities.

Viewing Physical PortsThe Physical Port Info tab shows general information about the PCI functions under the selected physical port and the current physical port status.

To view physical port information:


2. In the Emulex Device Management tree-view, select the OCe11100-series adapter physical port for which you want to view information.

3. Select the Physical Port Info tab (Figure 5-17 on page 73).

Figure 5-17 OCe11100–Series Adapter Physical Port Info Tab

Physical Port Info Tab Field Definitions

PCI Function Summary Area

NIC – The number of NIC functions running on the adapter.



74

iSCSI – The number of iSCSI functions running on the adapter. FCoE – The number of FCoE functions running on the adapter.

Physical Port Status Area

Status: Down – Not operational Up – Operational n/a – Not available

Port Speed Area

Interface Type – The module type and speed. Configured Speed – The configured port mode (default, force or auto-negotiate)

and speed. DAC Cable Length – The DAC cable length in meters.

Viewing Firmware InformationUnlike LightPulse adapters, OCe11100-series adapter firmware is maintained on an adapter-specific basis instead of port-specific basis.

To view firmware information for an adapter:


2. In the Emulex Device Management tree-view, select the adapter for which you want to view firmware information.

3. Select the Maintenance tab. The Maintenance tab enables you to view and update firmware on an adapter in a specific host (Figure 5-18 on page 74).

Figure 5-18 OCe11100-Series Adapter Maintenance Tab



75

Maintenance Tab Field Definitions Active Firmware Version – The firmware version currently being used by the

adapter. Flash Firmware Version – The flash firmware version flashed on the adapter. BIOS Version – The version of the BIOS currently being used by the adapter. Boot Code Versions – The adapter's boot code versions currently being used by

the adapter.

Note: The Start-up Boot Code is the boot code that boots the adapter. It has no relation to the FC, or PXE boot code versions.

Maintenance Tab Button

The Update Firmware button updates firmware on the selected adapter. Refer to “Updating Firmware for OCe11100–Series and OCe14100–Series Adapters” on page 156 for more information.

Viewing Physical Port DCB ParametersThe DCB tab shows the DCB parameters for a physical port.

To view the DCB parameters for a physical port:


2. In the Emulex Device Management tree-view, select the physical port for which you want to view DCB parameters.


Figure 5-19 FCoE Adapter Port, DCB Tab



76

DCB Tab Field Definitions DCBX State – The current DCBX (Data Center discovery and Capability

exchange protocol) state (enabled or disabled). LLDP Transmit State – DCBX uses Link Layer Discovery Protocol (LLDP) to

exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP receive and transmit states must be enabled. If either the receive or transmit state is disabled, DCBX is disabled.

LLDP Receive State – DCBX uses LLDP to exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP receive and transmit states must be enabled. If either the receive or transmit states is disabled, DCBX is disabled.

PFC Properties Area

State – Enabled indicates that there is flow control in both directions (receive and transmit).

Active Priorities – Lists the number of priorities with PFC set to enabled. Sync’d – If Yes, the PFC priorities have been set by the peer. This parameter

cannot be set. Error – The FCoE error status. The error status indicates whether an error

occurred during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

Protocol Properties Area


Sync’d – If Yes, the PFC priorities have been set by the peer. This parameter cannot be set.

Error – The FCoE error status. The error status indicates whether an error occurred during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

iSCSI Priority (if applicable) –The configured iSCSI priority. FCoE Priority (if applicable) –The configured FCoE priority.

ETS Properties Area

State – The protocol state. It can be enabled or disabled. Sync’d – If Yes, the protocol priority has been set by the peer. This parameter

cannot be set. Error – The error status. The error status indicates whether an error occurred

during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

Active Groups Table Group ID – The Priority Group number. It can be 0 to 7.



77

Priority Membership – The priorities that are assigned to each Priority Group. It is represented in comma separated format.

Bandwidth% – The percentage of available link bandwidth allocated to a particular Priority Group.

DCB Tab Button

The Configure DCB button allows you to configure the DCB parameters.

Viewing PHY Data for OneConnect 10GBASE–T–Series Adapters

The PHY Data tab shows PHY data information for OneConnect 10GBASE-T–series adapters.

To view physical data information:


2. In the Emulex Device Management tree-view, select the physical port for which you want to view physical data information.

3. Select the PHY Data tab (Figure 5-20 on page 77).

Figure 5-20 OneConnect Adapter PHY Data Tab

PHY Data Tab Field Definitions

Operational Attributes Area

Temperature – The internally measured adapter temperature. Firmware – The version of Emulex firmware currently active on the adapter

port. Config ID – The CRC configuration details. Link Uptime – The time in seconds that the link has been up. Pair A/B/C/D

SNR Margin – The port’s average SNR margin for twisted pairs A, B, C & D.



78

Error Rates Area

LDPC Frame Errors – The number of LDPC frame errors. PHY CRC8 Errors – The number of physical CRC errors. Pair A/B/C/D MSE – The port’s average MSE relative to the transmitted code

words for twisted pairs A, B, C & D.

Counters Area

MDI PLL Events – The number of MDI PLL events. 10G EMI Events – The 10G EMI Event counter tracks the number of single-tone

interference detected by the CNA's MDI signals. This counter holds its value at MDI link down and self-clears at the next link up.

PHY Frames – Counts the number of physical frames transmitted and received since the MDI link has been established. This counter holds its value at MDI link down and self-clears at the next link up.

PHY Data Tab Button

Clear Counters – This button is inactive for the PHY Data tab for OCe11100-series adapter ports.

Viewing Port Transceiver InformationThe Transceiver Data tab enables you to view transceiver information such as vendor name, serial number, part number, and diagnostic data. If the adapter/transceiver does not support some or all of the transceiver data, the fields show N/A.

To view transceiver information:


2. In the Emulex Device Management tree-view, select the physical port whose transceiver information you want to view.



79

3. Select the Transceiver Data tab (Figure 5-21 on page 79).

Figure 5-21 OCe10100–Series Port Transceiver Tab

Transceiver Information Field Definitions

Module Attributes Area

Vendor – The name of the vendor. Identifier/Type – The identifier value that specifies the physical device

described by the serial information. Ext. Identifier – Additional information about the transceiver. 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 OUI. It is also referred to as the IEEE Company Identifier

for the vendor. Date – The vendor’s date code in the MM/DD/YY format. Serial Number – The serial number provided by the vendor. Part Number – The part number provided by the SFP vendor. Revision – The vendor revision level.

Diagnostic Data Area

Temperature – The internally measured module temperature. Supply Voltage – The internally measured supply voltage in the transceiver. Tx Bias Current – The internally measured Tx bias current. Tx Output Power – The measured Tx output power.



80

Rx Input Power – The measured Rx input power

Viewing the Channel Management Tab for UFP (OCe11100–Series Adapters Only)

For adapters that support UFP, the UFP properties are displayed in the Channel Management tab when UFP is enabled. The Port Channel Management tab for UFP is read-only with specific attributes listed in the table as shown in Figure 5-22.

Note: UFP is supported only on IBM virtual fabric adapters. For specific information as to whether it is supported on a specific adapter, see the release notes that are available on the IBM adapter pages on the Emulex website.

To view UFP channel management:

1. From the discovery-tree, select the UFP adapter port whose channel information you want to view.

2. Select the Channel Management tab (Figure 5-22 on page 80).

Figure 5-22 Channel Management Tab in UFP Mode

Channel Mgmt Field Definitions for UFP Channel Management Type – The channel management protocol type in use. Function Number – The function number assigned by the system to the channel. Type – The protocol type in use. MAC address – The MAC address assigned to the channel. Name – The name assigned to the UFP by an administrator during switch

configuration. Outer VLAN ID – The VLAN identifier used between the NIC port and the

switch. The switch maps this value into the VLAN ID used on the network. Min. Bandwidth – The minimum bandwidth at which the port is guaranteed to

run. Max. Bandwidth – The maximum bandwidth at which the port is guaranteed to

run.



81

Viewing the Channel Management Tab for vNIC1 (OCe11100–Series Adapters Only)

For adapters that support vNIC1, the vNIC properties are displayed in the Channel Management tab when vNIC is enabled. The Port Channel Management Tab for vNIC is read-only with the vNIC specific attributes listed in the table as shown in Figure 5-23.

Note: vNIC is only supported on certain virtual fabric adapters. For specific information as to whether it is supported on a specific adapter, see the release notes that are available on the Emulex website.

To view vNIC channel management:

1. From the discovery-tree, select the vNIC adapter port whose channel information you want to view.

2. Select the Channel Management tab (Figure 5-23 on page 81).

Figure 5-23 Channel Management Tab in vNIC1 Mode

Channel Mgmt Field Definitions for vNIC1 Channel Management Type – Channel management protocol type in use. Function # – Function number used to identify a specific channel. Type – Protocol personality of a specific channel. MAC address – MAC address assigned to a specific channel. Name – Name assigned to the vNIC by an administrator during switch

configuration. Outer VLAN ID – VLAN identifier used between the NIC port and the switch.

The switch maps this value into the VLAN ID used on the network. Min. BW – Minimum BW at which the port is guaranteed to run. Max. BW – Maximum BW at which the port is guaranteed to run.

Installing Licenses OneCommand Manager for VMware vCenter allows you to view available licenses and install licenses to enable capabilities such as FCoE or iSCSI personalities on OCe11100-series adapters.



82

Notes

When licenses or licensable features are not available for the adapter, license information is not displayed.

Licensing is not available for the LPe16202 adapter. Contact Emulex for the required license files.

To install licenses for an OCe11100-series adapter:


2. In the Emulex Device Management tree-view, select the adapter for which you want to install licenses.

3. Select the Adapter Information tab (Figure 5-16 on page 71).4. Click Install Feature Licenses. The Install Feature Licenses dialog box shows the

Adapter ID (Figure 5-24 on page 82).

Figure 5-24 Install Feature Licenses Dialog Box

5. Following the instructions you received with the Entitlement Code, go to the License website and enter the Adapter ID and Entitlement Code.

6. When the Adapter ID and Entitlement Code are successfully validated, download a License Key File containing one or more activation keys.

7. In the Install Feature Licenses dialog box, click Browse. The file selection dialog box appears. Select the file you want to use and click OK.

8. A dialog box appears confirming that you want to install the licenses. Click Yes. 9. A dialog box appears notifying you that the installation was successful or why it

failed. Click OK.

Changing Personalities OneCommand Manager for VMware vCenter allows you to change the personality running on an OCe11100-series adapter. There are three personalities: NIC-Only, FCoE, and iSCSI.

Note: OneCommand Manager for VMware vCenter does not support personality change for the LPe16202 adapter.



83

In some cases the adapters come pre-configured to support multiple personalities. In other cases an enablement license must be installed before the adapter can support multiple personalities. Refer to “Contact Emulex for the required license files.” on page 82 for more information.

To change the personality of an adapter:


2. In the Emulex Device Management tree-view, select an adapter whose personality you want to change.

3. Select the Adapter Information tab (Figure 5-16 on page 71). From the Personality area of the Adapter Information tab, select the personality type you want and click Apply.

Note: If the adapter does not support personalities, personality controls are not displayed. If the adapter does not support a particular personality type that control is disabled.

4. Reboot the host for the personality change to take effect.

Enabling or Disabling a Physical PortTo change the physical port status, on the Physical Port Info tab for the OCe11100–series adapter, click Enable Port/Disable Port. This button toggles between Disable Port and Enable Port, depending upon the current status of the physical port.

Changing a Physical Port’s SpeedThe Change Port Speed dialog box allows you to configure port mode, speed and DAC cable length.

To configure port speed for a physical port:


2. In the Emulex Device Management tree-view, select the physical port whose port speed you want to configure.

3. Select the Physical Port Info tab (Figure 5-17 on page 73).4. Click Set Speed. The Change Port Speed dialog box appears (Figure 5-25 on

page 84).5. As applicable, make mode, speed, and DAC cable length changes.6. Click OK.



84

Figure 5-25 Change Port Speed Dialog Box

Change Port Speed Field Definitions Mode

Default – Speed and DAC Cable Length fields are not active. Force Auto-Negotiate

Speed – This field is active if the mode is set to Force or Auto-Negotiate. If the mode is set to Force and depending upon the interface type, you can

set the speed to one of the following: 10 Mb/s 100 Mb/s 1 Gb/s 10 Gb/s

If the mode set to Auto-Negotiate, and depending upon the interface type, you can set the speed setting to a single or multiple speed value.

Single speed values 10 Mb/s 100 Mb/s 1 Gb/s 10 Gb/s

Multiple speed values combinations 10 Gb/s and 1 Gb/s 1 Gb/s and 100 Mb/s 1 Gb/s, 100 Mb/s and 10 Mb/s 100 Mb and 10 Mb/s

DAC Cable Length – This field is only required if the Force mode is selected and the speed is set to 10 Gb/s. Select from 1 to 10 meters. This field is not active in all other cases.

Configuring Physical Port DCB ParametersThe DCB Configuration dialog box allows you to configure physical port DCB parameters. While there are eight ETS Priority Groups in which the priorities can be



85

assigned, only two of those groups can be assigned priorities and bandwidths. The FCoE priority is assigned to one Priority Group and the other seven (NIC) priorities must be assigned to one and only one other Priority Group. If you are configuring Priority Groups on a DCBX enabled switch, in order to work properly with the adapter port, you must only configure two Priority Groups in the same way.

To configure DCB parameters for a physical port:


2. In the Emulex Device Management tree-view, select the physical port whose DCB properties you want to configure.

3. Select the DCB tab.4. Click Configure DCB. The DCB Configuration dialog box is displayed (Figure 5-26

on page 85).5. Configure the settings you want and click OK.

Figure 5-26 DCB Configuration Dialog Box for FCoE and ISCSI Adapter Ports (DCBX Enabled)

Configure DCB Dialog Box Field Definitions

DCBX Settings Area

Enabled – DCBX can be enabled or disabled. With DCBX enabled, the configured values are used only if the switch does not provide them. With DCBX disabled, the configured values are used.

DCBX Mode – The DCBX mode can be set to DCB or CIN. Changes to the DCBX mode require a reboot of the host.



86

Operating Version – The operating version of the DCBX protocol. The system adjusts as needed to operate at the highest version supported by both link partners. This setting cannot be changed.

Maximum Version – The highest DCBX protocol version supported by the system. Version numbers start at zero. The DCBX protocol must be backward compatible with all previous versions. This setting cannot be changed.

LLDP Settings Area

Transmit Enabled – LLDP Transmit can be enabled or disabled. Transmit Port Description Enabled – Provides a description of the port in an

alpha-numeric format. The value equals the ifDescr object, if the LAN device supports RFC 2863.

Transmit System Name Enabled – Provides the system's assigned name in an alpha-numeric format. The value equals the sysName object, if the LAN device supports RFC 3418.

Transmit System Description Enabled – Provides a description of the network entity in an alpha-numeric format. This includes system's name and versions of HW, OS, and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418.

Transmit System Capabilities Enabled – Indicates the primary function(s) of the device and whether these functions are enabled on the device. The capabilities are indicated 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 can be enabled or disabled.

PFC Priorities Area

You can configure PFC priorities on LPe16202 NIC ports and OCe11100–series NIC and iSCSI ports.

Active Priorities – The priorities that are marked active for PFC. Enable – This checkbox enables PFC priorities.

If you are configuring a NIC port, clear this checkbox. If you are configuring an iSCSI or FCoE port, select this checkbox.

Configured Priorities – If the Enable checkbox is selected, these are the priorities that are configured, but might not yet be active. You can select two PFC priority checkboxes. One of these selections must match the iSCSI priority. The other PFC priority is for Ethernet traffic. The PFC priority for Ethernet traffic must be assigned to a Priority Group which has no other priorities.

FCoE Priority Area (FCoE adapter ports only)

Active Priority – The active FCoE priority. Configured Priority – The configured FCoE priority.

iSCSI Priority Area (FCoE adapter ports only)

Active Priority – The active iSCSI priority.



87

Configured Priority – The configured iSCSI priority.

ETS Priority Groups Area

Active Groups

Max Configurable PGs – The maximum number of Priority Groups that can be configured.

Group ID – The Priority Group ID. Priority Membership – The different priorities assigned to the various

Priority Groups. This is the current active configuration. Bandwidth – The bandwidths that are assigned to different Priority Groups.

This is the current active configuration.

Configured Groups

Group ID – The Priority Group ID. Priority Membership – The configured priority membership grouping. Bandwidth% – The configured bandwidth value for the different Priority

Groups.

Configure DCB Dialog Box Buttons

Defaults – Click to return parameters to default DCB settings. Configuration Rules – Click to view a window that lists the rules for

configuring priorities. You must observe these rules when configuring Priority Groups for adapter ports. Configuration rules are displayed based on the type of adapter ports you are configuring.

OK – Click to apply and save your changes. Cancel – Click to discard any changes you made.

FCoE and iSCSI Configuration Rules

One and only one priority is configured for the priority. You can select a maximum of two PFC priorities and one of them must

match the priority. The PFC Priority Group to which the priority is assigned must contain no

other priorities. The additional PFC priority must be assigned to a Priority Group which has

no other priority. Bandwidths of all the Priority Groups must total 100%.

NIC Configuration Rules

One and only one priority is configured for the priority. The PFC priority must be assigned to a Priority Group which has no other

priorities. Bandwidths of all the Priority Groups must total 100%.



88

Managing Port Channels Using Channel Management (OCe11100–Series Adapters Only)

Channel management allows each supported OCe11100-series adapter’s physical port to be partitioned into a maximum of four isolated channels providing a converged conduit for network and storage traffic. Each channel has its own unique MAC address and provides traffic management capabilities such as enabling or disabling send and receive traffic, minimum and maximum transmit rates, and VLAN IDs for untagged packets.

Ports are managed using the Channel Management tab. The Channel Management tab is displayed when an adapter port is selected in the discovery-tree and Channel Management is enabled on the Adapter Information tab. See “Configuring Channel Management” on page 88.

The Channel Management tab for UMC or SIMode shows the function number, type of protocol, MAC address, and more for each channel. You can also configure and enable or disable channels, and assign LPVIDs.

Refer to the Emulex Universal Multi-Channel Reference Guide for more information about channel management.

Notes

You must reboot the host for channel management to activate. When the channel management mode in the Adapter Information tab is set to

None, the Channel Mgmt tab is not displayed. Channel management is not available for the LPe16202 adapters. Channel management and SR-IOV cannot be used together. If you set channel

management, then you must disable SR-IOV. If you set SR-IOV, then you must disable UMC.

Properties for all channels on a port can be viewed and modified at the time channel management is enabled on the Adapter Information tab; before the required reboot to activate channel management on the adapter.

SIMode or UMC mode is required to dynamically control CNA ports using channel management.

Enabling and Disabling Channel ManagementTo enable channel management, select a management type from the Management Type After Reboot list in the Channel Management area when in the Adapter Information view (Figure 5-16 on page 71).

To disable channel management, select None from the Management Type After Reboot list.

Configuring Channel Management When you select an OCe11102 adapter port with channel management enabled, the Channel Mgmt tab is available.



89

Note: The Channel Mgmt tab shows the settings for the configured channel management mode after reboot. This may not match the mode that is currently running on the adapter if you have changed the mode in the Adapter Information tab, but have not rebooted.

To manage the ports for an OCe11102 adapter:


2. In the Emulex Device Management tree-view, select the adapter port for which you want to manage channels.

3. Select the Channel Mgmt tab. The Channel Mgmt tab is displayed (Figure 5-27 on page 89).

Figure 5-27 Channel Mgmt tab for the OCe11102 adapter

4. Make appropriate changes to the LPVID, Min BW%, and Max BW% values in accordance with the guidelines that follow.

5. Click Apply. A reboot is not required.

Channel Mgmt Field Definitions Channel Management Type – Channel management protocol type in use. Funct# – Function number used to identify a specific channel. Type – Protocol personality of a specific channel. MAC Address – MAC address assigned to a specific channel. LPVID – Logical port VLAN ID. Minimum and maximum bandwidths (in percent) – Percentage of available

link bandwidth allocated to a particular function. Minimum bandwidth total – Sum of the minimum bandwidths which must

total 100% in order to apply any changes made in the Channel Mgmt tab.

Note: If you change any properties, you must click Apply Changes to save them. A reboot is not required for changes to take effect.



90

Disabling a Specific ChannelTo disable a channel, click the Minimum Bandwidth field for the specific channel and enter a ‘0’ value.

To enable a channel, click the Minimum Bandwidth field for the specific channel and enter a non-zero value.

For more information on setting bandwidths, see “Assigning Bandwidth for a Specific Channel” on page 90.

Assigning an LPVID for a Specific ChannelLPVID values range between 2 and 4094. Any “enabled” channel must be assigned an LPVID. LPVIDs must be unique across all channels on a port.

Note: LPVID does not apply to iSCSI and FCoE channel types. LPVID is set to zero for these protocols.

To assign an LPVID value:

1. Click the LPVID field for the channel you want to change. 2. Enter a valid LPVID value.3. Click Apply Changes.

Note: If you click Apply Changes and the LPVID values are not between 2 and 4094 or if they are not unique, an error message is displayed indicating the issue and that the changes were not saved.

Assigning Bandwidth for a Specific ChannelMinimum bandwidth values of the “enabled” channels can be set between 1% and 100%, but must all add up to exactly 100%. The total of these bandwidths is displayed and updated each time the minimum bandwidth field is changed. If the total is 100%, the background in the “Minimum bandwidth total:” is green. If not, the background is red to indicate changes must be made.

The maximum bandwidth of a channel must be greater than or equal to the minimum bandwidth for that channel.

To assign a bandwidth value:

1. Click the appropriate Bandwidth field for the channel you want to change. 2. Enter a valid bandwidth value.3. Click Apply Changes.

Note: If you click Apply Changes and the total minimum bandwidths do not add up to 100% or one of the maximum bandwidths is not valid, an error message is displayed indicating the issue and that the changes were not saved.


5. Managing Adapters and PortsOCe14100–Series Adapters

91

OCe14100–Series AdaptersThis section pertains to viewing and configuring OCe14000-series adapter and port information.

Viewing Adapter InformationThe Adapter Configuration tab contains current configuration information for the selected adapter.

To view configuration information:


2. In the Emulex Device Management tree-view, select an adapter. The Adapter Configuration tab is displayed (Figure 5-30 on page 95).

Viewing Physical Port DCB ParametersTo view the DCB parameters for a physical port:


2. In the Emulex Device Management tree-view, select the physical port for which you want to view DCB parameters.


Figure 5-28 OCe14100-Series Adapter, DCB Tab (FCoE/iSCSI Adapter Port Selected)



92

DCB Tab Field Definitions DCBX State – The current DCBX (Data Center discovery and Capability

exchange protocol) state (enabled or disabled). LLDP Transmit State – DCBX uses Link Layer Discovery Protocol (LLDP) to

exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP receive and transmit states must be enabled. If either the receive or transmit state is disabled, DCBX is disabled.

LLDP Receive State – DCBX uses LLDP to exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP receive and transmit states must be enabled. If either the receive or transmit states is disabled, DCBX is disabled.

PFC Properties Area


Active Priorities – Lists the number of priorities with PFC set to Enabled. Sync’d – If Yes, the PFC priorities have been set by the peer. This parameter

cannot be set. Error – The FCoE Error status. The error status indicates whether an error

occurred during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

FCoE and iSCSI Protocol Properties Area


Sync’d – If Yes, the PFC priorities have been set by the peer. This parameter cannot be set.

Error – The FCoE Error status. The error status indicates whether an error occurred during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

iSCSI Priority (if applicable) – The configured iSCSI priority. FCoE Priority (if applicable) – The configured FCoE priority.

ETS Properties Area

State – The protocol state. It can be Enabled or Disabled. Sync’d – If Yes, the protocol priority has been set by the peer. This parameter

cannot be set. Error – The error status. The error status indicates whether an error occurred

during the configuration exchange with the peer. Error is also set to Yes when the Compatible method fails.

Active Groups Table Group ID – The Priority Group number. It can be 0 to 7.



93

Priority Membership – The priorities that are assigned to each Priority Group. It is represented in comma separated format.

Bandwidth% – The percentage of available link bandwidth allocated to a particular Priority Group.

DCB Tab Button

The Configure DCB button allows you to configure the DCB parameters.

Viewing Physical DataThe PHY Data tab shows PHY data information for OneConnect 10GBASE-T–series adapters.

To view physical data information:


2. In the Emulex Device Management tree-view, select the physical port for which you want to view physical data information.

3. Select the PHY Data tab (Figure 5-29 on page 93).

Figure 5-29 OneConnect OCe14000-Series Adapter PHY Data Tab

PHY Data Tab Field Definitions

Operational Attributes Area

Temperature – The internally measured adapter temperature. Firmware – The version of Emulex firmware currently active on the adapter

port. Config ID – The CRC configuration details.



94

Link Uptime – The time in seconds that the link has been up. Pair A/B/C/D SNR Margin – The port’s average SNR margin for twisted pairs A, B, C & D.

Error Rates Area

LDPC Frame Errors – The number of LDPC frame errors. PHY CRC8 Errors – The number of physical CRC errors. Pair A/B/C/D MSE – The port’s average MSE relative to the transmitted code

words for twisted pairs A, B, C & D.

Counters Area

MDI PLL Events – The number of MDI PLL events. 10G EMI Events – The 10G EMI Event counter tracks the number of single-tone

interference detected by the CNA's MDI signals. This counter holds its value at MDI link down and self-clears at the next link up.

PHY Frames – Counts the number of physical frames transmitted and received since the MDI link has been established. This counter holds its value at MDI link down and self-clears at the next link up.

PHY Data Tab Button

Clear Counters – Click to clear the 10GBaseT counters for the port.

Configuring OCe14000–Series AdaptersWhen you select an OCe14000-series adapter from the discovery-tree, the Adapter Configuration tab is displayed. The type of information that appears depends on the what protocols and capabilities are available on the adapter. (The IPL defines the protocols and capabilities.)

For all adapters except NPar, there are three configuration modes available:

Single personality – Select a single protocol (along with NIC, or NIC-only) to run on all ports on the adapter.

Custom – Choose the protocols to run on each port independently. Custom configuration is available if the adapter is capable of mixed or concurrent mode storage.

Multichannel – View the channel properties and change the configurable properties (based on the multichannel type).

For NPar, the adapter is either running with NPar disabled (the adapter is running as a single NIC function on each port), or with NPar enabled, which can be similar to a multichannel configuration or a storage channel configuration.



95

Figure 5-30 OCe14100-series Adapter Configuration Tab (FCoE selected)

OCe14100–Series Adapter Configuration Tab Field Definitions Current Configuration – The protocol running on the adapter. Next Boot Configuration – Shows different checkboxes or radios buttons subject

to the protocol running on the adapter. Select a checkbox or radio button to change the tab's view and next boot configuration method.

The display in the lower area of the tab depends upon the selected view of the next boot configuration. For non-NPar configurations, depending upon configuration options available on the adapter, you can configure the adapter for a single personality (e.g. FCoE), multichannel, or a custom configuration (for mix and concurrent modes).

OCe14100–Series Adapter Configuration Tab Buttons

Apply - Saves the changes to the next boot configuration to the adapter. Restore - Resets any changes to the next boot configuration back to the currently

saved settings on the adapter. Factory Defaults – Returns the adapter to the factory default profile and settings

for that adapter. A reboot is required. Details – A pop up a window is displayed with more information about the

current configuration running on the adapter (Figure 5-31 on page 96).



96

Figure 5-31 Current Configuration Details example

Enabling or Disabling SR-IOV The Adapter Configuration tab (Figure 5-30 on page 95) allows you to enable or disable SR-IOV on an adapter. When SR–IOV is enabled, multiple VFs can be created on a NIC PF for an adapter port. These VF's are assigned by the ESXi host to the VMs. Each VM can be assigned one or more VFs by the guest OS running on the VM. To the guest OS, the VF is an independent NIC function with its own MAC address and is available for network I/O. The discovery-tree shows the VFs running on the discovered PFs. It also shows the selected VFs MAC Address, VLAN ID, Link Status, and Transmit Rate.

Note: You can enable or disable SR-IOV for operating systems that do not support SR-IOV. Enabling or disabling SR-IOV for operating systems that do not support SR-IOV may be applicable in some cases. Examples include:

You enable SR-IOV in PXE BIOS on a Windows Server 2008 system. In this case, you are unable to see that SR-IOV is enabled.

An adapter is configured to support SR-IOV in an operating system that supports SR-IOV and the adapter is moved to a system that doesn’t support SR-IOV.

The OneCommand Manager for VMware vCenter Command Line Interface is used in an offline environment, such as WinPE and CentOS.

To enable or disable SR-IOV:

1. Select Host view. 2. Select a NIC port function on an adapter in the discovery-tree.3. Select the Adapter Configuration tab.4. Select or clear the Enable SR-IOV checkbox (Figure 5-30 on page 95).5. Click Apply.



97

Notes

SR-IOV only runs on the first NIC on the port, even if there are additional NIC partitions on the port.

SR-IOV is only available on OCe14100–series adapters. SR-IOV is only available for NIC adapters. To use SR-IOV, you must enable SR-IOV in OneCommand Manager for

VMware vCenter and the system BIOS. See the Emulex Drivers for VMware ESXi User Manual for information on enabling SR-IOV in the system BIOS.

If you disable SR-IOV from the Adapter Configuration tab by clearing the Enable SR-IOV checkbox, the OS or port stops supporting SR-IOV after reboot.

SR-IOV must be enabled at the system BIOS level. SR-IOV is not supported with UMC channel management. If you are using

SR-IOV, then you must disable channel management. See “Managing Port Channels Using Channel Management (OCe11100–Series Adapters Only)” on page 88 for more information.

Configuring a Single PersonalityThe single personality runs the same protocol on all ports of the adapter.

When you configure a single personality for an adapter, all ports run the same number of functions and protocols on those functions.

SR-IOV can be enabled or disabled for all adapter types that support SR-IOV, except NPAR and multichannel configurations.

Note: SR-IOV can be enabled on NPAR adapters only when NPAR is disabled and all ports are configured to run NIC functions.

To configure a single personality:

1. From the discovery-tree, select the OCe14100-series adapter whose personality you want to configure.

2. Select the Adapter Configuration tab (Figure 5-30 on page 95).3. Check the Single personality (all ports) radio button.4. Select the personality you want to apply from the Personality drop-down menu.

If you choose a NIC configuration, there may be multiple NIC configurations available (for example; NIC or NIC- ETS Disabled). If the adapter supports multiple NIC configurations (profiles), you must select a NIC configuration from the NIC configuration list.

If you choose the NIC- ETS Disabled configuration, SR-IOV is automatically enabled on each NIC function and allows up to 63 virtual functions. If you choose the NIC configuration, to enable SR-IOV, you must check the Enable NIC SR-IOV checkbox.

5. Click Apply. A message appears notifying you of the profiles activation requirements. Not all selections require a reboot.



98

Setting Up a Custom ConfigurationThe Custom configuration view allows you to customize the protocols running on each port of an adapter. The Port Configuration table only shows the available ports (Figure 5-32 on page 98).


SR-IOV can be enabled on NPAR adapters only when NPAR is disabled and all ports are configured to run NIC functions.

Figure 5-32 OCe14100-series Adapter Configuration Tab, Custom Configuration

Notes

Custom configurations are only available if the adapter supports mixed or concurrent mode storage.

If you configure all ports the same, you essentially configure a single personality and the Adapter Configuration tab shows the Single Personality radio button automatically selected.

To set up a custom configuration:

1. From the discovery-tree, select the OCe14100-series adapter whose personality you want to configure.

2. Select the Adapter Configuration tab.3. check the Custom radio button.4. Select the personality you want to apply from the Protocol drop-down menu for

each port. If you choose a NIC configuration, there may be multiple NIC configurations

available (for example; NIC or NIC- ETS Disabled). If the adapter supports multiple NIC configurations (profiles), you must select a NIC configuration from the NIC configuration list.



99

If you choose the NIC- ETS Disabled configuration, SR-IOV is automatically enabled on each NIC function and allows up to 63 virtual functions. If you choose the NIC configuration, to enable SR-IOV, you must check the Enable NIC SR-IOV checkbox.

5. Click Apply. A message appears notifying you of the profiles activation requirements. Not all selections require a reboot.

Setting Up a Mixed Mode ConfigurationWhen mixed mode is available, you can configure up to two functions per port. The first function will be NIC. The second function can be a storage protocol or “None”. When you click on the second function's drop-down menu, the available storage protocols for the function are displayed (Figure 5-33 on page 99).



Figure 5-33 Mixed Mode Protocol Drop-Down Menu

You can select any of the available storage protocols or “None” to indicate that the second function will not be available on that port. After selecting the protocols to run on each port, click Apply to save the configuration.

Note: If you select the same protocol or “None” on all ports, you essentially configured a single personality. In this case, after clicking Apply, the tab switches to the single personality view showing the selected personality in the personality drop-down menu.

Note: If NIC protocol is selected for all functions, a drop-down menu appears with available NIC-Only profiles. One of the profiles must be selected.



100

Setting Up a Concurrent Mode ConfigurationWhen concurrent mode is available, you can configure up to three functions per port (Figure 5-34 on page 100).



Figure 5-34 Concurrent Storage Configuration View

The drop-down menu for selecting a storage protocol to run on the second and third functions is the same as the drop-down menu for mixed mode storage.

Concurrent Storage Configuration is subject to the following rules:

The first function must be NIC. If two storage functions are configured on a port, they must be different storage

protocols (for example, concurrent mode). When you select the storage protocol for the second function, the choices in the

drop-down menu for the third function are limited to the other storage protocol or “None” (Figure 5-35 on page 101).

Note: If you select the same protocol or “None” for all second functions on all ports and “None” for all third functions, you essentially configured a single personality. In this case, after clicking the Apply button, the tab switches to the single personality view and the selected personality is shown in the personality drop-down menu.



101

Figure 5-35 Concurrent Storage Configuration Choices for the Third Function

Setting Up a UMC ConfigurationWhen UMC is available and the UMC radio button is selected, the Adapter Configuration tab is similar to Figure 5-36 on page 101.

Figure 5-36 UMC View (four ports)



102

UMC protocol assignments are subject to the following rules:

The first channel can only be assigned NIC protocols. The first channel cannot be assigned None (disabled).

The second and third channels can be assigned the following: NIC None (disabled) Storage protocol (third channel only when concurrent mode storage is

available). If storage protocols are assigned to the second and third channels, they must be different storage protocols.

The fourth and higher channels (if available) can only be assigned NIC or None (disabled).

A channel's logical link is set to down by setting both the minimum and maximum bandwidths to 0.

The total minimum bandwidth for all enabled channels on a port must add up to 100, except when all the maximum bandwidths are 0 (for example, setting a logical link down on all channels).

The maximum bandwidth for each channel must be greater than or equal to the minimum bandwidth for that channel.

LPVIDs (range 2-4094) must be assigned to all NIC channels and must be unique across all NIC channels on a port. However, any or all of the LPVIDs on one port can be repeated on another port.

Default UMC SettingsMost hosts today do not support ARI, therefore the default UMC settings are designed to prevent enabling functions that require ARI (when possible). This prevents the possibility of enabling channels that are not seen on the PCI bus when the system boots. There is one case where functions requiring ARI are enabled when UMC is enabled. On a four port adapter, when UMC is disabled, if the third function on each port is already enabled when UMC is enabled, that function continues to be enabled. In this case, it is assumed that you previously enabled the third function because ARI was available.

When UMC is enabled, the channels are assigned default values based upon the following rules:

For each port:

All enabled functions (that is, functions not set to None) continue to be enabled, running the same protocol before UMC was enabled even if its function number is greater than seven (only possible on 4 four-port adapters).

Any channel with a function number less than eight is enabled with NIC. Any channel with a function number greater than seven is set to None

(disabled). The minimum bandwidths are assigned by dividing up 100% as evenly as

possible between the enabled channels. The maximum bandwidths for the enabled channels are set to 100.



103

Both the minimum and maximum bandwidth for the channels assigned None are set to 0.

The LPVIDs are set to 0. You must assign any NIC channel a valid LPVID.

Note: These rules create the default settings for the channels. You can update these rules before saving them.

Setting Up an IBM MultiChannel Configuration

Note: IBM multichannel currently only allows four channels per port even in one and two port configurations

For IBM multichannel configuration, there are three different multichannel types available: vNIC, SIMode, and UFP. When you check the MultiChannel radio button, the Adapter Configuration tab is displayed(Figure 5-37 on page 103).

Figure 5-37 MultiChannel View (showing multichannel type drop-down menu)

A MultiChannel Type drop-down menu is available to select the type of multichannel configuration on the adapter. The contents of the Channel Configuration table depend upon the selected multichannel type.



104

Setting Up a Multichannel vNIC ConfigurationWhen vNIC is selected on the adapter, the Adapter Configuration tab is displayed (Figure 5-38 on page 104).

Figure 5-38 MultiChannel vNIC View (Mixed Mode Storage)

The Channel Configuration table shows the channel properties for vNIC.

There are drop-down menus for each port's channels second and third channels. vNIC protocol assignments are subject to the following rules:

The first channel can only be assigned a NIC protocol. The first channel cannot be assigned None.

The second and third channels can be assigned the following: NIC None (disabled) Storage protocol (On the third channel only when concurrent mode storage

is available) The fourth and higher channels (if available) can only be assigned NIC or None

(disabled). LPVIDs (range 2-4094) must be assigned to all NIC channels and must be

unique across all NIC channels on a port. However, any or all of the LPVIDs on one port can be repeated on another port.



105

Setting Up a MultiChannel SIMode ConfigurationWhen MultiChannel SIMode is selected, the Adapter Configuration tab is displayed (Figure 5-39 on page 105). Other than the names, SIMode and UMC configuration is exactly the same. See “Configuring DCB Parameters for FCoE/iSCSI Adapter Ports” on page 114.

Figure 5-39 MultiChannel SIMode View



106

Setting Up a Multichannel UFP ConfigurationWhen UFP is selected, the Adapter Configuration tab shows the Channel Configuration table shows the channel properties for multichannel UFP (Figure 5-40 on page 106).

Figure 5-40 MultiChannel UFP View (concurrent mode storage)

There are drop-down menus for each port's channels second and third channels. Multichannel UFP channel protocol assignments are subject to the following rules:

The first channel can only be assigned NIC protocols. The first channel cannot be assigned None.

The second and third channels can be assigned the following: NIC None (disabled) Storage protocol (third channel only when concurrent mode storage is

available) Storage protocols can only be assigned to the second channel when

mix-mode storage is available. The third channel can be assigned a storage protocol when concurrent mode

storage is available under the following restrictions. Can only be assigned a storage protocol if the second channel is assigned

a storage protocol. The storage protocol must be different than the second channel's storage

protocol. The fourth and higher channels (if available) can be assigned the NIC protocol

or None (disabled).



107

Setting Dell NPar Bandwidth SettingsSimilar to UMC, a minimum and maximum bandwidth is assigned to each enabled (that is, not None) partition. The sum of the minimum bandwidths must add up to 100. The maximum bandwidth for each partition must be equal to or greater than the minimum bandwidth on that partition and no larger than 100. Unlike UMC, if the minimum and maximum bandwidths are set to 0, the logical link on the adapter is not brought down. A small of amount of data will trickle through the port for that partition when bandwidth is available. Bandwidth changes take effect immediately (no reboot required).

Two-Port AdaptersDell two-port adapters allow up to four or eight partitions per port, depending upon whether the NParEP Mode checkbox is checked or cleared.

NParEP Mode DisabledFor Dell NPar adapters, the Adapter Configuration tab is different than for the other adapters. There are two choices in the Next Boot Configuration: NPar Enabled and Enable NParEP Mode. When NPar is checked (enabled) and NParEP Mode is cleared (disabled), the adapter is basically a NIC-only adapter (Figure 5-41 on page 107).

If the NParEP Mode checkbox is cleared, only four partitions per port can be configured. FCoE, iSCSI or None can be configured on the second through fourth partitions, but only one FCoE and one iSCSI can be configured. None cannot be configured on the first partition.

Figure 5-41 Dell Two-Port NPar Configuration, NParEP Mode Disabled



108

NParEP Mode EnabledIf the NParEP Mode checkbox is selected (enabled), up to eight partitions per port can be configured (Figure 5-42 on page 108). FCoE or iSCSI can be configured on the second through fourth partitions, but only one FCoE and one iSCSI can be configured. Partitions higher than the fourth partition can only configured for NIC or None. None cannot be configured on the first partition.

Figure 5-42 Dell Two-Port NPar Configuration, NParEP Mode Enabled



109

Four-Port AdaptersDell four-port adapters allow up to two or four partitions per port, depending upon whether the NParEP Mode checkbox is checked or cleared.

Dell NPar EnabledWhen NPar is enabled on the Adapter Configuration tab (Figure 5-43 on page 109), you can switch between showing eight functions and showing sixteen functions for a given adapter.

Figure 5-43 Adapter Configuration Tab with NPar Enabled

If you know whether you are in an NParEP Mode configuration, you can display the appropriate number of functions for an adapter.

NPar protocol assignments are subject to the following rules:

The first channel can only be assigned NIC protocols. The first channel cannot be assigned None.

The second and third channels can be assigned the following: NIC None (disabled) Storage protocol (note: on 3rd channel only when concurrent mode storage

is available) The fourth and higher channels (if available) can only be assigned NIC or None

(disabled). The total of the minimum bandwidths of the enabled functions for each port

must add up to 100 percent. The maximum bandwidth for each function must be greater than, or equal to, the minimum bandwidth for that channel.

After changing the NPar configuration and applying the changes, except for bandwidth changes, a reboot is required to activate the new configuration.



110

SR-IOV must be disabled on the adapter BIOS when NPar is used. See “Updating Firmware” on page 153 for information on disabling SR-IOV on the adapter BIOS.

SR-IOV must be enabled on the system BIOS when NParEP is used. See the documentation that accompanied your Dell server for more information.

NParEP support is available only on Dell 13G or newer systems.

NParEP Mode DisabledWhen NPar is enabled and NParEP Mode is disabled on the Adapter Configuration tab (Figure 5-44 on page 110) only two partitions per port can be configured. FCoE, iSCSI or None can be configured on the second function, None cannot be configured on the first function.

Figure 5-44 Dell Four Port NPar Configuration, NParEP Mode Disabled



111

NParEP Mode EnabledIf the NParEP Mode checkbox is selected (enabled), up to four partitions per port can be configured (Figure 5-45 on page 111). FCoE or iSCSI can be configured on the second through fourth partitions, but only one FCoE and one iSCSI can be configured. None cannot be configured on the first partition.

Figure 5-45 Dell Four Port NPar Configuration, NParEP Mode Enabled



112

Setting Up HP Flex ConfigurationsIn the Next Boot Configuration area, the Flex or the FlexQbg radio button is available, depending upon the type of Flex adapter installed in your system. Selecting this radio button causes Flex to be configured during the next system boot.

Figure 5-46 HP Flex Adapter Configuration Tab, Flex selected

To configure an adapter for Flex or FlexObg:

1. Select the Flex or the FlexQbg radio button. The Flex or FlexQbg button title is displayed depending upon the type of Flex adapter installed in your system.

2. Click Apply. Once you click Apply, The Flex or FlexQbg radio button is inactive, or grayed out.

Flex will be configured during the next system boot.



113

Figure 5-47 HP Flex Adapter Configuration Tab, Single Personality selected



114

Configuring DCB Parameters for FCoE/iSCSI Adapter PortsTo configure DCB parameters for a physical port:


2. In the Emulex Device Management tree-view, select the physical port whose DCB properties you want to configure.

3. Select the DCB tab (Figure 5-28 on page 91).4. Click Configure DCB. The DCB Configuration dialog box appears (Figure 5-48 on

page 114). 5. Configure the settings you want and click OK.

Figure 5-48 DCB Configuration Dialog Box for FCoE and ISCSI Adapter Ports (DCBX Enabled)


DCBX Settings Area





115


LLDP Settings Area




Transmit System Description Enabled – Provides a description of the network entity in an alpha-numeric format. This includes system's name and versions of HW, OS, and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418.


Receive Enabled – LLDP Receive can be enabled or disabled.

PFC Priorities Area

You can configure PFC priorities on LPe16202 adapter NIC ports and OCe11100–series NIC and iSCSI ports.

Active Priorities – The priorities that are marked active for PFC. Enable – This checkbox enables PFC priorities.

If you are configuring a NIC port, clear this checkbox. If you are configuring an iSCSI or FCoE port, select this checkbox.

Configured Priorities – If the Enable checkbox is selected, these are the priorities that are configured, but might not yet be active. You can select two PFC priority checkboxes. One of these selections must match the iSCSI priority. The other PFC priority is for Ethernet traffic. The PFC priority for Ethernet traffic must be assigned to a Priority Group which has no other priorities.

FCoE Priority Area (FCoE adapter ports only)

Active Priority – The active FCoE priority. Configured Priority – The configured FCoE priority.

iSCSI Priority Area (FCoE adapter ports only)

Active Priority – The active iSCSI priority. Configured Priority – The configured iSCSI priority.



116


Active Groups

Max Configurable PGs – The maximum number of Priority Groups that can be configured.

Group ID – The Priority Group ID. Priority Membership – The different priorities assigned to the various Priority

Groups. This is the current active configuration. Bandwidth – The bandwidths that are assigned to different Priority Groups.


Configured Groups

Group ID – The Priority Group ID. Priority Membership – The configured priority membership grouping. Bandwidth% – The configured bandwidth value for the different Priority

Groups.


Defaults – Click to return parameters to default DCB settings. Configuration Rules – Click to view a window that lists the rules for configuring

priorities. You must observe these rules when configuring Priority Groups for adapter ports. Configuration rules are displayed based on the type of adapter ports you are configuring.

OK – Click to apply and save your changes. Cancel – Click to discard any changes you made.

FCoE and iSCSI Configuration Rules One and only one priority is configured for the priority. You can select a maximum of two PFC priorities and one of them must match

the priority. The PFC Priority Group to which the priority is assigned must contain no other

priorities. The additional PFC priority must be assigned to a Priority Group which has no

other priority. Bandwidths of all the Priority Groups must total 100%.

NIC Configuration Rules One and only one priority is configured for the priority. The PFC priority must be assigned to a Priority Group which has no other

priorities. Bandwidths of all the Priority Groups must total 100%.


6. Managing ProtocolsNIC

117

6. Managing ProtocolsThis section pertains to managing NIC, FC, FCoE, and iSCSI protocols.

NICThis section pertains to viewing NIC adapter and port information. This section also includes booting from the iSCSI SAN and enabling and disabling VEPA.

Viewing NIC Port InformationWhen you select a NIC port from the Emulex Device Management tree-view, the NIC Port Information tab shows general attributes associated with the selected NIC port. If the adapter supports vNIC, vNIC data is also displayed.

Notes

NIC ports not only exist on NIC-only adapters, but also exist on FCoE and iSCSI adapters.

vNIC is supported only on IBM virtual fabric adapters. For specific information as to whether it is supported on a specific adapter, refer to the release notes that are available on the IBM adapter pages on the Emulex website.

To view general NIC port information:


2. In the Emulex Device Management tree-view, select the NIC port for which you want to view information.

Note: In Virtual Ports view, NIC ports appear only on FCoE adapters. They do not appear on NIC-only adapters.

3. Select the Port Information tab (Figure 6-1 on page 118). If SR-IOV is enabled on the adapter, the Port Information is displayed similar to Figure 6-1 on page 118. If SR-IOV is disabled on the adapter, the Port information tab is displayed similar to



118

Figure 6-1 NIC Port Information Tab with SR-IOV Enabled on the Adapter

Figure 6-2 NIC Port Information Tab with SR-IOV Disabled on the Adapter

NIC Port Information Tab Field Definitions Driver Name – The NIC driver file name. Driver Version – The NIC driver version. MAC Address – The NIC MAC address currently assigned to the port. Perm MAC Address – The original factory assigned NIC MAC address. IP Address – The IP address for the NIC port. Subnet Mask – The subnet mask for the NIC port. Gateway Address – The gateway address for the NIC port. IP Address Origin – The origin of the IP address (DHCP or static). Link Status – The link status is always displayed as “n/a” (not available).



119

LinkDown Reason – The reason for the status of LinkDown on the selected port. Interface Name – The interface assigned to this port by the host OS. Port Speed – The current port speed of the NIC port. Device ID – The PCI device ID assigned to the NIC function. Subsys Device ID – The PCI subsystem ID assigned to the NIC function. Vendor ID – The PCI vendor ID assigned to the NIC function. Subsys Vendor ID – The PCI subsystem vendor ID assigned to the NIC function. IPv6 Address – The Internet Protocol Version 6 address, if applicable. PCI Function – The PCI function number assigned to the NIC function. PCI Bus Number – The PCI bus number to which the port is mapped. Current MTU – The current transmission unit for Ethernet traffic. Max MTU – The maximum transmission unit for Ethernet traffic. Min Bandwidth – The minimum SoftCap bandwidth assigned. Max Bandwidth – The maximum SoftCap bandwidth assigned. Enable VEPA checkbox - Select this checkbox to enable VEPA. For more

information on VEPA, see “Enabling and Disabling VEPA” on page 122.

Note: This checkbox does not appear if SR-IOV is disabled on the adapter.

Network Boot radio buttons - For more information network boot, see “Network Boot” on page 122. None- Select to disable the network boot functions. PXE - Select to boot from a network interface using a preboot execution

environment. iBFT – to boot from an iSCSI SAN using the iSCSI Boot Firmware Table

format. The iBFT boot option is only available for the CNA 16 Gb family of adapters that support the NIC or iSCSI protocol. PXE boot is supported on LPe16202, and OCe11000–series adapters.

Note: The Network Boot radio buttons do not appear if SR-IOV is enabled on the adapter.

Viewing PCI Registers for a NIC PortThe PCI Registers tab contains PCI information about the selected NIC function.

To view a NIC port’s PCI registers:


2. In the Emulex Device Management tree-view, select the NIC port for which you want to view PCI information.




120

Figure 6-3 NIC Port PCI Registers Tab

Viewing NIC Port Vital Product Data (VPD)The VPD tab shows vital product data (if available) for the selected NIC port such as the product name, part number, and serial number for example.

To view VPD information of an NIC port:


2. In the Emulex Device Management tree-view, select the NIC port for which you want to view VPD information.


Figure 6-4 NIC Port VPD Tab



121

VPD Table Definitions Product Name – The product information about a selected adapter port. Part Number – The adapter's part number. Serial Number – The adapter's serial number. VO – Vendor unique data. “V” indicates a vendor-specific field. An adapter can

have none, one, or more than one 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).


Viewing Virtual Functions on a Host Operating SystemOneCommand Manager for VMware vCenter can discover the VFs running on the discovered physical functions and show them in the discovery-tree (Figure 6-5 on page 121).

Figure 6-5 Virtual Functions Discovered on the Physical Function on the Host OS

Select the VF under the host OS in the discovery-tree to display the Port Information tab (Figure 6-6 on page 121).

Figure 6-6 Port Information tab for NIC Virtual Function



122

Port Information Field Definitions MAC Address – The NIC MAC address currently assigned to the port. VLAN-ID – The VLAN identifier used by the NIC port. Link Status – The status of the link on the selected port. Transmit Rate – The rate at which data is transmitted over the port in Mbs.

Network BootTo boot from the iSCSI SAN, the host must have an iSCSI boot capable network adapter that supports the iSCSI Boot Firmware Table (iBFT) format. The iBFT is a method of communicating parameters about the iSCSI boot device to an OS. To boot the host from the Network interface, use PXE.

NIC functions include iBFT boot configuration and PXE boot configuration which are displayed under the Network Boot section of the NIC Port Information tab. If the currently selected NIC port does not support network boot, the Network Boot section is not displayed.

Notes

The iBFT boot option is only available for the CNA 16 Gb family of adapters that support the NIC or iSCSI protocol. PXE boot is supported on LPe16202, and OCe11000–series adapters.

Network boot options are only available on ports with a PCI function of 0 or 1. Network boot is supported by CIM Provider 3.6.12 and above.

To select a network boot configuration on the selected port, click the desired option from the Network Boot section:

iBFT – to boot from an iSCSI SAN using the iSCSI Boot Firmware Table format. PXE – to boot from a network interface using a preboot execution environment. None – to disable the network boot functions.

Enabling and Disabling VEPA VEPA allows the network traffic at the VFs to bypass the hypervisor's virtual switch, and allow the PFs to transmit the traffic to the external switch. This relieves the CPU of the switching burden, and puts the traffic on the physical network, where you can monitor it using familiar techniques.

To enable VEPA, check Enable VEPA (Figure 6-1 on page 118). To disable VEPA, clear the Enable VEPA checkbox.

Notes

SR-IOV must be enabled to enable VEPA. For more information on SR-IOV, see “Enabling or Disabling SR-IOV” on page 96.

VEPA is only available on the OCe14100–series adapters. VEPA is only available for NIC ports.


6. Managing ProtocolsFC /FCoE Ports

123

FC /FCoE PortsThis section pertains to managing FC/FCoE adapter and port information.

Setting Driver Parameters for All Adapters in a Host To change the driver parameters for all adapters in a host:

1. From the vSphere console tree-view, select the host whose adapter driver parameters you want to change and if applicable, select the Emulex OneCommand tab.

2. Select the host Driver Parameters tab (Figure 4-9 on page 50). If there are adapters with different driver types installed, the Installed Driver Types menu shows a list of all driver types and driver versions that are installed. Select the driver whose parameters you want to change. This menu does not appear if all the adapters are using the same driver.

3. In the driver parameter table, click the Value field of a parameter that you want to change. The range for the value is displayed. Enter a value in decimal or hexadecimal format, depending on how the current value is presented. If the value is in hexadecimal format, it is prefixed by “0x” (for example -”0x2d”).

4. Parameters that can be changed temporarily can only be changed from the corresponding port. Such parameters are represented with a check-box next to it.

5. Click Apply.

Enabling an Optimized Access Storage (ExpressLane) LUN

Notes

Enabling an ExpressLane LUN is supported only for the LPe16000 and OCe15100 families of adapters.

Express Lane is supported only on ESXi5.5 and ESXi 6.0 versions. An ExpressLane LUN must be enabled in the driver before it can be used by the

OneCommand Manager for VMware vCenter. Additionally, the priority value to mark each of the ExpressLane frames must be specified to the FC/FCoE driver through new driver parameters.

ExpressLane is not supported for LUNs attached to virtual ports.

If your system contains flash and rotational storage I/O on the same initiator port, the improved performance of the flash storage can be hindered by the slower rotational storage I/O performance. Because both are sharing the same queue, rotational storage I/O requests queued up in front of flash storage I/O requests can prevent the performance gains of flash storage I/O (that is, head of line blocking).

To prevent this, you can create a separate priority queue in the driver to process the requests ahead of the normal queue. Additionally, the I/O frames placed on this queue can be marked with a priority so that the switch and target also prioritizes the flash I/O requests. By indicating to the FC/FCOE driver, which LUNs receive this special priority queuing (for example, ExpressLane LUNs), performance on these LUNs can be



124

greatly improved. Even if only FC flash storage is available on your system, there can be LUNs that you want to run I/O with a higher priority than other LUNs.

To enable an ExpressLane LUN:


2. In the Emulex Device Management tree-view, expand the FC/FCoE adapter port.3. Expand the FC/FCoE target.4. Right-click the LUN on which you want to enable ExpressLane. 5. Select Enable ExpressLane LUN from the drop-down menu (Figure 6-7 on

page 124).

Figure 6-7 ExpressLane LUN Drop-Down Menu

The LUN icon changes to (Figure 6-8 on page 125).

Note: The ExpressLane state of a LUN is enabled at the driver (active) level and the configured level (persists across reboots).



125

Figure 6-8 FC/FCoE LUN with ExpressLane Enabled

Disabling ExpressLane LUNsYou can disable a specific ExpressLane LUN or disable all ExpressLane LUNS for a port.

To disable a specific ExpressLane LUN:

1. In the Emulex Device Management tree-view, expand the FC/FCoE adapter port.2. Expand the FC/FCoE target.3. Right-click the LUN for which you want to disable ExpressLane. 4. Select Disable ExpressLane LUN from the drop-down menu.

To disable all ExpressLane LUNs for a port:

1. In the Emulex Device Management tree-view, expand the FC/FCoE adapter port.2. Expand the FC/FCoE target.3. Right-click any LUN with ExpressLane enabled. 4. Select Disable All ExpressLane LUNs on this target from the drop-down menu.

Configuring FIPThe FIP tab allows you to view configure FIP for an FCoE adapter port.

To configure FIP:


2. In the Emulex Device Management tree-view, select the FCoE adapter port whose FIP properties you want to configure.

3. Select the FIP tab (Figure 6-9 on page 126).4. Set the parameters you want and click Apply Changes.



126

Figure 6-9 FCoE Port FIP Tab

FIP Tab Field Descriptions

DCB Settings Area

DCB settings are only applicable when the DCBX Mode in the DCB tab is set to DCB.

Note: If the “DCB (FIP) Settings” area has “Active” in its title, this indicates that DCB (FIP) is the current DCBX mode (DCBX mode is set from the DCB tab). If CIN (Non-FIP) is the current DCBX mode, “Active” is in the “CIN (Non-FIP) Settings” area.

Primary Fabric Name – Indicates the FC fabric's WWN to which to connect. If the Primary Fabric Name is wild (all 0xFFs), then connection to any fabric name is allowed.

Primary Switch Name – Indicates the FC switch's WWN to which to connect. If the Primary Switch Name is wild (all 0xFFs) then connection to any switch name is allowed.

VLAN ID – Determines the VLAN where the adapter FCoE services are available. It can have a value from 0 to 4095 and supports wild card values if the Any VLAN ID is valid checkbox is selected.

Any VLAN ID is valid checkbox – When checked, the VLAN ID field of the FCoE forwarder can be any valid value.

CIN Settings Area

FC Map – Enter the bit value that completes the FPMA. VLAN ID – Determines the VLAN where the adapter FCoE services are

available. It can have a value from 0 to 4095.

FIP Tab Buttons

Apply Changes – Click to set new FIP parameters.



127

Configuring DCB Parameters for FCoE Adapter PortsTo configure DCB for FCoE adapter ports:


2. In the Emulex Device Management tree-view, select the FCoE adapter port whose properties you want to configure.

3. Select the DCB tab (Figure 6-10 on page 127).4. Click Configure DCB. The Configure DCB dialog box appears.5. Configure the settings you want and click OK.

Figure 6-10 Configure DCB Dialog Box for FCoE Adapter Ports (DCBX Enabled)

Note: An error message is displayed if you try to configure more priority groups than the adapter supports. The “Max Configurable PGs” field in the ETS Priority Groups area shows the number of priority groups supported by the adapter.

Changing WWN Configuration for an FC PortThe Maintenance tab enables you to change the WWPN and the WWNN of a selected adapter port. For example, you might want to use an installed adapter as a standby if another installed adapter fails. By changing the standby adapter's WWPN or WWNN, it can assume the identity and configuration (such as driver parameters and persistent binding settings) of the failed adapter.



128

There are three options for referencing WWNs:

Factory default WWN – The WWN as shipped from the factory. Non-volatile WWN – The values that are saved in the non-volatile adapter’s

flash memory that survive a reboot and/or power outage. Volatile WWN – A temporary value that is saved in the volatile memory on the

flash. If volatile WWNs are set, they are used instead of the non-volatile WWNs. Volatile WWN changes require a warm system reboot to take effect. Volatile WWN changes are lost on systems that power cycle the adapters during the reboot.

Caution: Changing volatile WWNs result in taking the selected adapter offline. Ensure that this adapter is not controlling a boot device and all I/O activity on this adapter has stopped before proceeding. Emulex assumes no responsibility for the consequences of making volatile WWN changes on a boot adapter.

Considerations When Changing WWN Configuration for an FC Port

To avoid address conflicts, do not assign a WWNN or WWPN with OneCommand Manager for VMware vCenter if you also use another address management tool.

The WWPN and WWNN in the Pending Changes list can show “n/a” instead of “none”. This happens when the remote host is busy processing some critical task and WWN Management cannot obtain the current state of WWN management.

In an environment where preboot management exists, a WWPN or WWNN modified by OneCommand Manager for VMware vCenter can be overridden by preboot management such as IBM BOFM and industry standard CLP.

For example:

In an environment with CLP/BOFM, OneCommand Manager for VMware vCenter modifies the WWNN or WWPN. OneCommand Manager for VMware vCenter requires a reboot to complete the change. After a reboot, the CLP string is sent during the system boot and rewrites the WWNN or WWPN, or EFIBoot finds the BOFM protocol and uses the default WWNN or WWPN per the BOFM's command.

In an environment without CLP/BOFM, OneCommand Manager for VMware vCenter modifies the WWNN or WWPN. OneCommand Manager for VMware vCenter requires a reboot to complete the change. The system boots and the OneCommand Manager for VMware vCenter-modified WWNN or WWPN is used.

On a system where OneCommand Manager for VMware vCenter is installed, make sure the port numbers configured during the installation are open and dedicated to the OneCommand Manager for VMware vCenter server only. No other service should be listening on this port.



129

To change a port's WWPN or WWNN:


2. In the Emulex Device Management tree-view, select the FC port for which you want to change the WWN information.

3. Select the Maintenance tab (Figure 5-9 on page 62).4. Click Change WWN. The Change WWN Configuration dialog box is displayed

(Figure 6-11 on page 129).

Figure 6-11 Change WWN Configuration Dialog Box

5. Do one of the following: Enter a new WWPN or WWNN. Click Get Factory Default WWNs to load the settings that were assigned when

the adapter was manufactured. These values can then be modified and saved as volatile or non-volatile WWNs.

Click Get Non-Volatile WWNs to load the current non-volatile WWN. These values can be modified and saved to volatile or non-volatile memory. You can edit the data returned from the button.

6. Check Write changes to volatile memory for temporary use to save the New WWPN and New WWNN settings as volatile WWNs. If cleared, the New WWPN and New WWNN settings are saved as non-volatile WWNs.

Note: If the adapter or firmware does not support volatile WWNs, the “Write changes to volatile memory for temporary use” checkbox is disabled. This type of change is supported locally and via TCP/IP connections. This checkbox is disabled for remote in-band adapters regardless of adapter models and firmware version.



130

7. Click OK. The following warning is displayed (Figure 6-12 on page 130).

Figure 6-12 Warning About Changing WWN

8. Click Yes. The New WWPN and new WWNN values are saved. The new WWPN and WWNN appear in the Pending Changes list in the WWN Management area of the Maintenance tab.

9. Reboot the system for the changes to take effect (the new WWPN and WWNN appear in the Pending Changes list of the Maintenance tab until the system is rebooted). After rebooting, the changes are applied and appear in the Current section of the Maintenance tab.

Note: After changing the WWN of an adapter, you must reboot the system before trying to access the adapter on that system.

Resetting an FC/FCoE Port

Caution: Do not reset an adapter port while copying or writing files. This could result in data loss or corruption.

Notes

While resetting a port on OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host.

For FCoE ports, a reset is only necessary to activate changed driver parameters or FIP settings. It does not actually perform an adapter level reset of the port.

When changing WWN configuration on OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host.

To reset an FC port:


2. In the Emulex Device Management tree-view, select the FC port you want to reset.3. Select the Maintenance tab (Figure 5-9 on page 62).4. Click Reset. The following warning is displayed (Figure 6-13 on page 130).

Figure 6-13 Reset Port Warning

5. Click Yes. The adapter port resets. The reset can require several seconds to complete. While the adapter port is resetting, the message “Operation is in progress” is displayed. When the reset is finished, the message “Reset Port Completed” is displayed.



131

Enabling and Disabling FC PortsUsing the Port Information tab you can enable or disable FC ports. When you disable an FC port, you disable all functions for the port. Disabled ports appear in the discovery-tree as with an “x” over the port icon.

Note: Ensure there is no I/O traffic on the port before disabling it and never disable a boot port.

To enable or disable an FC port:


2. In the Emulex Device Management tree-view, select the FC port for that you want to enable or disable.

3. Select the Port Details tab (Figure 5-2 on page 53).4. Click Enable Port or Disable Port.

Setting Driver Parameters for an FC/FCoE PortTo change the driver parameters for a port using the Value field:


2. In the Emulex Device Management tree-view, select the port for which you want to change the driver parameters.

3. Select the Driver Parameters tab (Figure 5-4 on page 57).4. In the driver parameter table, click the Value field of a parameter that you want to

change. The range for the value is displayed. Enter a value in decimal or hexadecimal format, depending on how the current value is presented. If the value is in hexadecimal format, it is prefaced by “0x” (for example -”0x2d”). You can enter a hexadecimal value without the “0x”. For example, if you enter ff10, this value is interpreted and displayed as “0xff10”.

5. If you want the change to be temporary (causing the parameter to revert to its last permanent setting when the system is rebooted), check the Temporary box. This option is available only for dynamic parameters.

6. If you are making changes to multiple parameters, and you want all the changes 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 temporary.

7. Click Apply.


6. Managing ProtocolsiSCSI

132

Saving Driver Parameters of an FC/FCoE Port to a FileTo change the driver parameters for a port:


2. In the Emulex Device Management tree-view, select the FC port for which you want to change the driver parameters.

3. Select the Driver Parameters tab (Figure 5-4 on page 57).4. Click Export to create and save a desired port parameter configuration. Each

definition is saved in a comma-delimited file with the following format:<parameter-name>=<parameter-value>

5. Click Apply to apply your configuration changes.

iSCSI This section pertains to viewing iSCSI information and managing iSCSI ports.

Viewing iSCSI Port InformationWhen you select an iSCSI port from the Emulex Device Management tree-view, the iSCSI Port Information tab shows general attributes associated with the selected iSCSI port.

To view general iSCSI port information:


2. In the Emulex Device Management tree-view, select the iSCSI port for which you want to view information.

3. Select the Port Information tab (Figure 6-14 on page 133).



133

Figure 6-14 iSCSI Port Info Tab

iSCSI Port Info Tab Field Definitions Driver Name – The iSCSI driver file name. Driver Version – The iSCSI driver version. MAC Address – The iSCSI MAC address currently assigned to the port. Perm MAC Address – The original factory assigned iSCSI MAC address. Device ID – The PCI device ID assigned to the iSCSI function. Vendor ID – The PCI vendor ID assigned to the iSCSI function. PCI Function – The PCI function number assigned to the iSCSI function. LDTO – The amount of time in seconds that the iSCSI driver delays reporting a

link down error to the OS. Max MTU – The maximum transmission unit for Ethernet traffic. Default ETO – The default extended timeout. Max CDB Length – The maximum SCSI command descriptor block size. Subsystem Device ID – The PCI subsystem ID assigned to the iSCSI function. Subsys Vendor ID – The PCI subsystem vendor ID assigned to the iSCSI

function. PCI Bus Number – The PCI bus number to which the port is mapped.

TCP/IP Info Area

DHCP Enabled – The DHCP authentication status of the selected port.



134

IP Address – The IP address for the NIC port. Subnet Mask – The subnet mask for the NIC port. Gateway Address – The gateway address for the NIC port. VLAN Enabled – The VLAN enabled state for the iSCSI interface. VLAN ID – The VLAN identifier to use, from 0 to 4094 (only valid when VLAN

is enabled). A value of 0 indicates the VLAN is disabled. VLAN Priority – The VLAN priority for the iSCSI interface.

Network Info Area

Link Status – The status of the link on the selected port. LinkDown Reason - The reason for the status of LinkDown on the selected port. Port Speed – The current port speed of the iSCSI port. Min Bandwidth – The minimum SoftCap bandwidth assigned. Max Bandwidth – The maximum SoftCap bandwidth assigned.

Viewing PCI Registers for an iSCSI PortThe PCI Registers tab contains PCI information about the selected iSCSI port.

To view PCI registers for an iSCSI port:


2. In the Emulex Device Management tree-view, select the iSCSI port for which you want to view PCI information.


Figure 6-15 iSCSI Port, PCI Registers Tab



135

Viewing and Changing iSCSI ISNS Server InformationIf the server has been set up as an ISNS, the iSNS tab shows the IP address and TCP Port for the selected iSCSI port.

To view ISNS server information:


2. In the Emulex Device Management tree-view, select the iSCSI port for which you want to view ISNS information.

3. Select the iSNS tab (Figure 6-16 on page 135).

Figure 6-16 iSCSI Port, iSNS Tab

iSNS Tab Field Definitions

iSNS Server Area

IP Address - The IP address of the ISNS server. TCP Port - The TCP port number for the connection to the ISNS server.

Viewing iSCSI Initiator StatisticsThe iSCSI Statistics tab shows information for the selected iSCSI port.

To view iSCSI initiator statistics:


2. In the Emulex Device Management tree-view, select the iSCSI initiator for which you want to view Statistic information.

3. Click the iSCSI Statistics tab (Figure 6-17 on page 136).



136

Figure 6-17 iSCSI Initiator, iSCSI Statistics Tab

iSCSI Statistics Tab Field Definitions Node Roles – The node role for this iSCSI initiator. Portal Count – The number of rows in the iscsiPortaltypeTable that are

currently associated with this iSCSI instance. Node Count – The number of rows in the iscsiNodetypeTable that are currently

associated with this iSCSI instance. Session Count – The number of rows in the iscsiSessiontypeTable that are

currently associated with this iSCSI instance. Session Failure Count – The number of times a session belonging to this port

has failed. Last Session Failure Type – The type of failure encountered in the last session

failure. Last Session Remote Node – The iSCSI name of the remote node from the failed

session. Session Digest Errors – The count of PDUs that were received on the session and

contained header or data digest errors. Session Connection Timeout – The count of connections within this session that

have been terminated due to a timeout. Session Format Errors – The count of sessions that failed due to receipt of an

iSCSI PDU that contained a format error. Login Failures – The number of times a login from this initiator 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 have occurred. Last Failure Type – A description of the last failure.



137

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 Internet Network Address of the target that most recently failed.

Login Accept Responses – The count of Login Response PDUs received by this initiator that were accepted.

Login Other Fail Responses – The count of Login Response PDUs received by this initiator with any status code not counted by the other objects.

Login Redirect Responses – The count of Login Response PDUs received by the initiator with status class of Redirection.

Login Authentication Fail Responses – The count of Login Response PDUs with status class 0x201 Authentication Failed received by this initiator.

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 generated by this initiator with a normal reason code.

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 as a target portal and/or an initiator portal.

Viewing iSCSI Initiator Login OptionsThe iSCSI Initiator Login Options tab shows the set of login options used by the initiator when logging into a target.

To view iSCSI initiator login information:


2. In the Emulex Device Management tree-view, select the iSCSI initiator for which you want to view initiator login information.

3. Click the iSCSI Initiator Login Options tab (Figure 6-18 on page 138).



138

Figure 6-18 iSCSI Initiator Logon Options Tab

To view iSCSI initiator default login options:


2. In the Emulex Device Management tree-view, select the iSCSI initiator for which you want to view Initiator Login information.

3. Click the iSCSI Initiator Login Options tab (Figure 6-18 on page 138).4. Click View Default Login. The Initiator Default Login Options window is

displayed (Figure 6-19 on page 138).

Figure 6-19 iSCSI Initiator Default Login Options Window

iSCSI Initiator Login Options Tab Field Definitions

iSCSI Names Area

Initiator iSCSI Name – The iSCSI qualifier name of the initiator. Initiator Alias – An optional non-unique string used to identify the initiator.



139

Initiator Login Options Area

Immediate Data – If set to Yes, the initiator can append unsolicited data to an iSCSI command.

Header Digest – If set to CRC32C, the integrity of an iSCSI PDU's header segments are protected by a CRC32C checksum. If set to None, the PDU’s header segments are not protected.

Data Digest – If set to CRC32C, the integrity of an iSCSI PDU's data segment is protected by a CRC32C checksum. If set to None, the PDU’s data segments are not protected.

Authentication Area

Authentication Method One-Way CHAP requires only that the authenticator (iSCSI target)

authenticate the iSCSI initiator. Mutual CHAP requires that both the iSCSI target and iSCSI initiator

authenticate each other. None indicates that no authentication is performed.

Target CHAP Name – The iSCSI login name sent by the initiator to the target for authentication. This name is required for both One-Way CHAP and Mutual CHAP authentication. The target CHAP name is also known as the username.

Target Secret – The iSCSI login secret sent by the initiator to the target for authentication. A target secret is required for both One-Way CHAP and Mutual CHAP authentication.

Initiator CHAP Name – The iSCSI login name sent by the target to the initiator for authentication. The initiator CHAP name is only required for Mutual CHAP authentication. The initiator CHAP name is also known as the username.

Initiator Secret – The iSCSI login secret sent by the target to the initiator for authentication. The initiator secret is only required for Mutual CHAP authentication.

iSCSI Initiator Login Options Tab Buttons

View Default Login Options – Click to show the Initiator Default Login Options window.

Initiator Default Login Options Window Field Definitions 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 initiator to send a burst of unsolicited FirstBurstLength bytes.

ImmediateData – If set to Yes, allows the initiator to append unsolicited data to a command.

MaxOutstandingR2T – The maximum number of outstanding request to transmit's (R2T's) per task within a session, each up to MaxBurstLength bytes.

FirstBurstLength – The maximum amount of unsolicited data (in bytes) the initiator can send to the target during the execution of a single iSCSI command.



140

MaxBurstLength – The maximum amount of either unsolicited or solicited data the initiator may send in a single burst. Any amount of data exceeding this value must be explicitly solicited by the target.

DefaultTimeToWait – The minimum time to wait, in seconds, before the initiator attempts to reconnect or reassign a connection (or task) that has been dropped after an unexpected connection termination or reset. The initiator and target negotiate to determine this value.

DefaultTimeTo Retain – The maximum time, in seconds, to reassign a connection after the initial wait that is indicated in DefaultTime2Wait has elapsed. The initiator and target negotiate to determine this value.

HeaderDigest – The valid values for this property are CRC32C or None. If set to CRC32C and the initiator is configured accordingly, the integrity of an iSCSI PDU's header segments is protected by a CRC32C checksum.

DataDigest – The valid values for this property are CRC32C or None. If set to CRC32C and the initiator is configured accordingly, the integrity of an iSCSI PDU's data segment is protected by a CRC32C checksum.

MaxConnections – The maximum number of connections to targets that are allowed within a single session.

DataPPDUInOrder – The order of data PDUs within a sequence. DataSequenceInOrder – The order between sequences. MaxRecDataSegmentLength – The maximum data segment length in bytes an

initiator or target can receive in an iSCSI PDU. ErrorRecoveryLevel – The operational ErrorRecoveryLevel for the session. 0

indicates recovery only by session restart. 1 indicates recovery by reissuing commands, data, or status. 2 indicates connection failure recovery.

Initiator Default Login Options Window Buttons

Close – Click to close the window.

Viewing iSCSI Target Discovery InformationThe iSCSI Target Discovery tab shows all currently discovered targets. Targets on this tab come from one of three sources:

The target was added manually. The target was discovered via a target portal. The target was found through an ISNS server query.

To view iSCSI target discovery information:


2. In the Emulex Device Management tree-view, select the iSCSI initiator for which you want to view target discovery information.

3. Click the iSCSI Target Discovery tab (Figure 6-20 on page 141).



141

Figure 6-20 iSCSI Target Discovery Tab

iSCSI Target Discovery Tab Field Definitions iSCSI Name – The iSCSI name assigned to the target. Alias – The iSCSI alias assigned to the target. This is assigned at the target

portal, not by OneCommand Manager for VMware vCenter. Status – The status column indicates if the target is connected or disconnected.

Viewing iSCSI Target InformationThe iSCSI Target Information tab shows information about the target. You can also view information about a target session.

To view iSCSI target discovery information:


2. In the Emulex Device Management tree-view, select the iSCSI target for which you want to view target discovery information. The iSCSI Target Information tab is displayed (Figure 6-21 on page 141).

Figure 6-21 iSCSI Target Information Tab



142

iSCSI Target Information Tab Field Definitions Target iSCSI Name – The iSCSI name assigned to the target. Target Alias – The iSCSI alias assigned to the target. This is assigned at the

target portal, not by OneCommand Manager for VMware vCenter. ETO – The extended timeout for the target. The driver ensures that I/Os are not

“timed out” until this time has expired (from the time that the target stopped responding).

iSCSI Target Information Tab Buttons

The Sessions button opens the Target Sessions window.

Viewing Target Session InformationThere may be multiple active sessions for a connected target.

To view iSCSI target session information:


2. In the Emulex Device Management tree-view, select the iSCSI target for which you want to view target discovery information. The iSCSI Target Information tab is displayed (Figure 6-21 on page 141).

3. Click Sessions (Figure 6-22 on page 143). You can toggle between sessions by using the drop-down menu in the upper left corner of the window.



143

Figure 6-22 iSCSI Target Sessions Window

Target Sessions Window Field Definitions Initiator Name – The initiator named used to log into the session. ISID – The initiator session identifier (unique for each session). iSCSI Boot – If set to Yes, indicates a boot session. Logout is not possible from a

boot session. Status – The session status (logged in, login in progress, login failed, recovery,

or unknown). ISID Qualifier – The first two bytes of the ISID (unique for each session). TSIH – The target session identifier handle. A tag generated by an iSCSI target

to identify an iSCSI session with a specific iSCSI initiator.

Session Negotiated Login Options Area

InitialR2T – The initial request to transmit. If set to “Yes”, the initiator has to wait for the target to solicit SCSI data before sending it. If set to “No”, it allows the initiator to send a burst of unsolicited FirstBurstLength bytes.

Immediate Data – If 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.



144

MaxOutstandingR2T – The maximum number of outstanding request to transmits (R2Ts) per task within a session, each up to MaxBurstLength bytes.

FirstBurstLength – The maximum amount of unsolicited data (in bytes) the initiator can send to the target during the execution of a single iSCSI command.

MaxBurstLength – The maximum amount of either unsolicited or solicited data the initiator can send in a single burst. Any amount of data exceeding this value must be explicitly solicited by the target.

DefaultTimeToWait – The minimum time to wait, in seconds, before the initiator attempts to reconnect or reassign a connection (or task) that has been dropped after an unexpected connection termination or reset. The initiator and target negotiate to determine this value.

DefaultTimeToRetain – The maximum time, in seconds, to reassign a connection after the initial wait that is indicated in DefaultTimeToWait has elapsed. The initiator and target negotiate to determine this value.

ErrorRecoveryLevel – The operational ErrorRecoveryLevel for the session. 0 - recovery only by session restart. 1 - recovery by reissuing commands, data, or status. 2 - connection failure recovery.

DataPDUInOrder – The order of PDUs within a sequence. DataSequenceInOrder – The order between sequences.

Session Statistics Area

Session Direction – The direction of the iSCSI session. Valid values are InboundSession and OutboundSession.

Cmd PDUs – The count of Command PDUs transferred on this session. Response PDUs – The count of Response PDUs transferred on this session. 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 session.

Connection Information Area

iSCSI Connection ID – The iSCSI Connection ID assigned to the connection. Status – The status of the connection. Valid values are connected and unknown. Source IP Address – The source IP address for the connection. Source Port – The source TCP port number for the connection. Destination IP Address – The destination IP address for the connection.



145

Destination Port – The destination TCP port number for the connection. Redirected Destination – The redirected IP address for the target. Redirected Destination Port – The redirected port number for the target.

Connection Negotiated Login Properties Area

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 connection. The driver uses this to determine the size of the data PDU whenever it is required to transmit the entire PDU with a single iSCSI header.

Viewing iSCSI LUN InformationThe iSCSI LUN Info tab shows basic vendor, product and LUN masking information.

To view iSCSI LUN information:


2. In the Emulex Device Management tree-view, select the LUN for which you want to view information. The LUN Info tab is displayed (Figure 6-23 on page 145).

Figure 6-23 iSCSI LUN Info Tab

iSCSI LUN Info Tab Field Definitions

Vendor/Product Information Area

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.



146

Serial Number – The vendor’s serial number for the LUN.

LUN Capacity Area

Capacity – The un-formatted size of the LUN, in megabytes. Block Size – The length of a logical unit block in bytes.

LUN Masking Information Area

The Current Mask Status field indicates possible LUN mask states as masked or unmasked.

Viewing iSCSI Port Vital Product Data (VPD)The VPD tab shows vital product data (if available) for the selected iSCSI port such as the product name, part number, serial number and so on.

To view VPD information of an iSCSI port:


2. In the Emulex Device Management tree-view, select the iSCSI port for which you want to view VPD information.


Figure 6-24 iSCSI Port VPD Tab

VPD Table Definitions Product Name – The product information about a selected adapter port. Part Number – The adapter's part number. Serial Number – The adapter's serial number.



147

VO – Vendor unique data. “V” indicates a vendor-specific field. An adapter can 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).


Enabling iSCSI BootTo enable iSCSI boot:


2. In the Emulex Device Management tree-view, select the iSCSI port for which you want to view information.

3. Select the Port Info tab (Figure 6-14 on page 133).4. To enable iSCSI boot, check Enable iSCSI Boot. To disable iSCSI boot, clear Enable

iSCSI Boot.

Disabling the ISNS ServerTo disable the ISNS server, click Clear iSNS on the iSNS tab (Figure 6-16 on page 135).

Changing the ISNS ServerTo change the ISNS server:

1. On the iSNS tab, click Add/Update iSNS. The Update iSNS Server dialog box is displayed (Figure 6-25 on page 147).

Figure 6-25 iSCSI Port, Update iSNS Server Dialog Box

2. Enter the new server address and Port ID.3. Click OK to commit the new ISNS server. The new ISNS information is displayed

on the iSNS tab (Figure 6-16 on page 135). The new or updated ISNS server is also queried for iSCSI targets. Any discovered targets are added to the iSCSI Target Discovery tab.



148

Configuring ISNS for iSCSI Target DiscoveryAn ISNS maintains a database of storage network elements that can be queried by other hosts within the SAN. iSCSI storage devices in particular can register targets with the ISNS for efficient discovery by iSCSI clients. Use the iSCSI SNS tab to configure the ISNS server or to discover the server. For more information about the iSCSI iSNS tab, refer to “Changing the ISNS Server” on page 147.

Configuring DCB Parameters for iSCSI Adapter PortsThe DCB tab shows parameters for iSCSI adapter ports.


2. In the Emulex Device Management tree-view, select the iSCSI adapter port whose FIP properties you want to configure.


Figure 6-26 DCB Tab (iSCSI Adapter Port Selected)

DCB Tab Field Definitions DCBX State – The current DCBX state (enabled or disabled). LLDP Transmit 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.

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

Note: PFC is not supported on all the iSCSI adapter ports.



149

State – If Enabled, there is flow control in both directions (Tx and Rx). If Disabled, flow control is currently disabled. The priority value, if shown, is not applicable. This can be caused by: The switch port PFC is set to On instead of Auto The switch port is using port flow control instead of PFC PFC is disabled at the adapter or the switch

Active Priorities – Lists the priorities with PFC set to Enabled. Sync'd – If Yes, the PFC priorities have been set by the peer. This parameter


during the configuration exchange with the peer. Error is also set to YES when the compatible method for the capability fails.

iSCSI Properties Area

State – The iSCSI state. It can be enabled or disabled. Active Priority – The current active priority assigned for FCoE. Sync'd – If yes, the FCoE priority has been set by the peer. This parameter

cannot be set. Error – The iSCSI error state. This capability indicates whether an error has

occurred during the configuration exchange with the peer.

ETS Priority Group Properties Area

Note: Not shown when UMC is enabled on the adapter.

State – The current Priority Group state. It can be enabled or disabled. Sync'd – If yes, the Priority Groups have been set by the peer. This parameter


during the configuration exchange with the peer.

Active Groups Table

PG –The Priority Group number. It can be 0 to 7. Priorities – The priorities that are assigned to each Priority Group. It is

represented in comma separated format. Bandwidth (%) – The percentage of available link BW allocated to a particular

Priority Group.

DCB Tab Buttons

Configure DCB – Click to configure DCB parameters. See the instructions that follow.

To configure DCB for iSCSI adapter ports:




150

2. In the Emulex Device Management tree-view, select the iSCSI adapter port whose DCB settings you want to configure.

3. Select the DCB tab.4. Click Configure DCB. The Configure DCB dialog box appears (Figure 6-27 on

page 150).5. Configure the settings you want and click OK.

Figure 6-27 Configure DCB Dialog Box for iSCSI Adapter Ports (DCBX Enabled)

Note: An error message is displayed if you try to configure more priority groups than the adapter supports. The “Max Configurable PGs” field shows the number of priority groups supported by the adapter.


DCBX Settings Area





151


LLDP Settings Area




Receive Enabled – LLDP Receive can be enabled or disabled. Transmit System Description Enabled – Provides a description of the network

entity in an alpha-numeric format. This includes system's name and versions of HW, OS and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418.


PFC Priorities Area

Active Priorities – The priorities that are marked active for PFC. Enable – When checked, PFC is enabled. Configured Priorities –The priorities that are configured, but might not yet be

active. A maximum of two PFC priority checkboxes can be selected, out of which one of these selections must match the iSCSI priority. The additional PFC priority is for Ethernet traffic. The PFC priority for Ethernet traffic must be assigned to a Priority Group which has no other priorities.

iSCSI Priority Area

Active Priority – The active iSCSI priority. Configured Priority – The configured iSCSI priority.


Note: Not available when UMC is enabled on the adapter.

Active Groups Group ID – The Priority Group ID. Priority Membership – The different priorities assigned to the various

Priority Groups. This is the current active configuration. Bandwidth – The bandwidths that are assigned to different Priority Groups.




152

Configured Groups Group ID – The Priority Group ID. Priority Membership – The configured priority membership grouping. Bandwidth% – The configured bandwidth value for the different Priority

Groups.


Defaults – Click to return parameters to default DCB settings. Configuration Rules – Click to view a window that lists the rules for configuring

priorities. You must observe these rules when configuring Priority Groups for adapter ports.

Configuration Rules – Click to display the iSCSI Priority window that lists the rules for configuring iSCSI priorities.

You must observe the following rules when configuring priority groups for iSCSI adapter ports:

1. Only one priority can be configured as the iSCSI priority.2. A maximum of two PFC priorities can be selected and one of them must

match the iSCSI priority.

Note: Not all adapters support two PFC priorities. Adapters that do not support two PFC priorities display an error message if you try to configure more than one PFC priority.

3. The priority group to which the iSCSI priority is assigned must contain no other priorities.

4. The additional PFC priority must be assigned to a priority group which has no other priorities.

5. Bandwidths of all the priority groups must add up to 100%. OK – Click to apply and save your changes. Cancel – Click to discard any changes you made.


7. Updating FirmwareUpdating Firmware for an FC Adapter

153

7. Updating FirmwareOneCommand Manager for VMware vCenter enables you to update firmware for a single adapter or simultaneously for multiple adapters.

Notes

If you start a firmware update and log out from the vSphere console before the firmware update is completed, all pending jobs fail.

The firmware update progresses in the background until all the jobs are completed. During this period you can still browse through the other tabs.

The submitted firmware update job can be tracked in the VMware tasks window.

Multiple firmware update jobs can be submitted for different adapters and ports on the same or different ESXi hosts simultaneously to OneCommand Manager for VMware. However, only a single job is processed on a given ESXi host. The remaining jobs on that host will be queued and processed sequentially.

Updating Firmware for an FC AdapterTo update firmware for an FC port:

1. Select a host in the vSphere console tree-view and if applicable, select the Emulex OneCommand tab (Figure 2-5 on page 29).

2. In the Emulex Device Management tree-view, select the adapter for which you want to update firmware.

3. Select the Maintenance tab and click Update Firmware. If a warning screen appears, click Yes. The Firmware Download dialog box is displayed (Figure 7-1 on page 153).

Figure 7-1 Firmware Download dialog box


7. Updating FirmwareUpdating Firmware on FC Adapters in a Host

154

4. Click Browse and navigate to the unzipped, extracted image file you want to download.

5. On the browse window, select the file and click OK. The Firmware Download dialog box appears.

6. Click Start Update. A message prompting you to confirm the firmware update appears.

7. Click Yes. When the update begins, the Jobs window is displayed (Figure 7-8 on page 160). A status message in the Active Job list shows the progress of the download. The ports on which the firmware is being downloaded have the status “Job is in progress”, the others have “Waiting in queue to start”. When download is completed, the entry moves to the Completed Jobs window. The status message field in the Completed Jobs window shows the status of the completed job.

Notes

If you start a firmware update and log out from the vSphere console before the firmware update is completed, all pending jobs fail.


Updating Firmware on FC Adapters in a Host On the system where OneCommand Manager for VMware vCenter is installed, make sure the port numbers configured during the installation are open and dedicated to the OneCommand Manager for VMware vCenter server only. No other service should be listening on this port.

Before you can perform a batch update, the firmware file must be downloaded from the Emulex website and extracted to a directory on your local drive.

To update firmware for compatible adapters:

1. On the Batch Firmware Update Information pane, click Update Firmware (Figure 7-1 on page 150).

Note: You do not need to select a particular tree element for this operation.


7. Updating FirmwareUpdating Firmware on FC Adapters in a Host

155

The Batch Firmware Download dialog box is displayed (Figure 7-2 on page 155).

Figure 7-2 Empty Batch Firmware Download Dialog Box

2. Click Browse. The Firmware File Selection dialog box appears. Select the file you want to use and click OK. A status message appears indicating that OneCommand Manager for VMware vCenter is searching for compatible adapters.

After compatible adapters are found, the Firmware File field of the Batch Firmware Download dialog box shows the selected image file name. The Supported Models field shows a list of all adapter models that are compatible with the selected image file. The set of compatible adapters shows in the dialog box’s tree-view (Figure 7-3 on page 155).

Figure 7-3 Populated Batch Firmware Download Dialog Box

The tree-view shows all adapters and their corresponding hosts for which the selected firmware file is compatible. Use the checkboxes next to the host and adapter entries to select or deselect an entry. Checking an adapter selects or removes that adapter; checking a host removes or selects all eligible adapters for that host.

To view the compatible adapters in a fabric-centric mode, select the Group by Fabric checkbox.


7. Updating FirmwareUpdating Firmware for OCe11100–Series and OCe14100–Series Adapters

156

For adapters where each individual port can have new firmware installed, you can select the ports on the adapter to which you want to download firmware.

3. Make your selections and click Start Download. A message prompting you to confirm the firmware update appears, click Yes.

When the update begins, a status message in the Active Job window shows the progress as either “Job is in progress” or “Waiting in queue to start” (. The ports on which the firmware is being downloaded have the status “Job is in progress” the others have “Waiting in queue to start”. You can select the checkbox to cancel the jobs with status “Waiting in queue to start”. When download is completed, the entry moves to the Completed Jobs window. The status message field in the Completed Jobs window shows the status of the completed job.

Notes

If you start firmware update and log out from the vSphere console before the firmware update is completed, all pending jobs fail.


Updating Firmware for OCe11100–Series and OCe14100–Series Adapters

For OCe11100-series and OCe14100-series adapters, you update the firmware for the entire adapter and not for individual ports.

To update firmware for an adapter:


2. In the Emulex Device Management tree-view, select the adapter for which you want to update firmware information.

3. Select the Maintenance tab (Figure 5-18 on page 74) and click Update Firmware. If a warning message appears, click Yes. The Firmware Download dialog box is displayed (Figure 7-4 on page 156).

Figure 7-4 Firmware Download Dialog Box



157

4. Click Browse and navigate to the unzipped, extracted image file you want to download.

5. On the browse window, select the file and click OK.6. Click Start Update.

When the update begins, the Jobs window is displayed (Figure 7-8 on page 160). A status message in the Active Job list shows the progress of the download. The ports on which the firmware is being downloaded have the status “Job is in progress”, the other ports display the “Waiting in queue to start” status.

When the download has completed, the entry moves to the Completed Jobs window. The status message field in the Completed Jobs window shows the status of the completed job.

You can monitor jobs submitted through the OneCommand Manager for VMware vCenter Command Line Interface. If you start a firmware update and log out from the vSphere console before the firmware update is completed, all pending jobs fail. The firmware update progresses in the background until all the jobs are completed. During this period, you can still browse through the other tabs. The firmware update job submitted can also be tracked in the VMware tasks window.

7. Open Firmware Summary and the updated firmware information for the selected adapter is displayed.

Performing a Batch Firmware Update in Cluster View Before you can perform a batch update, you must download the firmware file from the Emulex website and extract it into a directory on your local drive.

Note: On the system where OneCommand Manager for VMware vCenter is installed, make sure the port numbers configured during the installation are open and dedicated to the OneCommand Manager for VMware vCenter server only. No other service should be listening on this port.

To perform a batch firmware update on a single adapter:


2. From the Emulex Device Management options, select Batch Firmware Update (Figure 7-5 on page 158).



158

Figure 7-5 Batch Firmware Update Information

3. Click Update Firmware to install firmware on multiple adapters in a single step. Batch firmware loading is restricted to a single firmware file and to all accessible adapters for which that file is compatible.

Updating Firmware on Multiple Adapters in Cluster ViewTo update firmware for multiple adapters:

1. On the Batch Firmware Update Information pane, click Update Firmware (Figure 7-5 on page 158). A Batch Firmware Download dialog box appears with blank fields.

Note: You do not need to select a particular tree element for this operation.

2. Click Browse and a search dialog box appears. On the search dialog box, select the file you want to use and click OK. A status message appears indicating that OneCommand Manager for VMware vCenter is searching for compatible adapters. After compatible adapters are found, the following is displayed in the Batch Firmware Download dialog box (Figure 7-6 on page 159): The Firmware File field shows the selected image file name. The Supported Models field shows a list of all adapter models that are

compatible with the selected image file. The set of compatible adapters appears in the dialog box’s tree-view.

3. To view the compatible adapters in host-centric mode, make sure the Group by Fabric checkbox is cleared.



159

Figure 7-6 Batch Firmware Download Dialog Box, Host-Centric View

4. To view the compatible adapters in a fabric-centric mode, select the Group by Fabric checkbox (Figure 7-7 on page 159).

Figure 7-7 Batch Firmware Download Dialog Box, Fabric-Centric View

The tree-view shows all adapters and their corresponding hosts or fabrics for which the selected firmware file is compatible. Use the checkboxes next to the entries to select or deselect a host, fabric, adapter or port (if the adapters where the individual port can have new firmware downloaded).

Note: iSCSI and NIC ports are not attached to any fabric, they are not listed in the Batch Firmware Download dialog box.

5. Make your selections and click Start Download. A message prompting you to confirm the firmware update appears, click Yes.



160

Jobs WindowWhen the download begins, the Jobs window is displayed. A status message in the Active Job list shows the progress of the firmware download. The ports on which the firmware is being downloaded have the status “Job is in progress”, the other ports have “Waiting in queue to start”.

When the download is completed, the entry moves to the Completed Jobs window. The status message field in the Completed Jobs window shows the status of the completed job (Figure 7-2 on page 155).

Figure 7-8 Jobs Window

Jobs Window Field Definitions

Active Jobs Column Definitions

User – The user who triggered the firmware update. Host – The IP address of the host to which the adapter/port belongs. Adapter – The model of the adapter selected for the firmware update request. Port – The Port WWN for an FC adapter. This field is blank for a CNA. Start Time – The time the job is submitted. Status Message – The status of the job. This field also indicates if a reboot is

required to activate the firmware.

Completed Jobs Column Definitions

User – The user who triggered the firmware update. Host – The IP address of the host to which the adapter/port belongs. Adapter – The model of the adapter. Port – The port WWN for an FC adapter. This field is blank for a CNA.



161

Start Time – The time the job is submitted. End Time – The time the job is completed. Status Message – The status of the job.

Jobs Window Buttons

Update Firmware – Click to update firmware on a different adapter in the same cluster.

Cancel Updates – Click to cancel the jobs with “Waiting in queue to start” status.


8. Exporting SAN Information in Cluster ViewUpdating Firmware for OCe11100–Series and OCe14100–Series Adapters

162

8. Exporting SAN Information in Cluster ViewExporting SAN information (creating a SAN report) progresses in the background until all the jobs are completed. During this period you can still browse through the other tabs.

Note: Creating a SAN report can take several minutes for a large SAN.

To export SAN information:


2. From the Emulex Device Management tree, select Export San Info. Export SAN Information is displayed (Figure 8-1 on page 162).

3. Click Export San Info. The Export SAN Info dialog box is displayed (Figure 8-2 on page 163).

4. Select host or hosts to export. Optionally, select the Select/Deselect All checkbox to select all hosts. Clear the Select/Deselect All checkbox to clear all host checkboxes.

5. Click Export.

The Export SAN Info Jobs window is displayed. The status is displayed in the Active Jobs list (Figure 8-3 on page 163).

When the export job is completed, the entry is displayed in the Completed Jobs list with a “Successfully completed” status.

Figure 8-1 Export SAN Info



163

Figure 8-2 Export SAN Info Dialog Box

Figure 8-3 Export SAN Info Jobs Window, Active Jobs List

Export SAN Info Window Field Definitions

Active Jobs Column Definitions

User – The user who triggered the firmware update. Start Time – The time the job is submitted. Status Message – The status of the job.

Completed Jobs Column Definitions

User – The user who triggered the firmware update. Start Time – The time the job is submitted.



164

End Time – The time the job is completed. Status Message – The status of the job. Download – Click XML or CSV to download the file with SAN information in

the specified format.

Jobs Window Buttons

Export SAN Info – Click to update firmware on a different adapter in the same cluster.

Capturing SAN Information in XML or CSV Format1. Click the row that represents the information you want to capture.2. Scroll to the right until the Download column appears.3. In the Download column, click XML or CSV to capture the information.

Considerations When Exporting SAN Information in a Cluster View

At any time only ten completed jobs are available to be exported. If more than ten jobs are completed, the first completed jobs are not available for download.

If you click Export SAN Info and log out from the vSphere console before the export is completed, all pending jobs fail.


9. DiagnosticsLightPulse FC Diagnostics

165

9. DiagnosticsThis section describes diagnostics for LightPulse FC and OneConnect adapters.

LightPulse FC DiagnosticsWhen running port diagnostic tests using OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host.

Running Loopback TestsThere are three loopback tests that you can run for the FC adapter port:

PCI Loopback – A firmware controlled diagnostic test in which a random data pattern is routed through the PCI Bus without being sent to an adapter link port. The returned data is subsequently validated for integrity.

Internal Loopback – A diagnostic test in which a random data pattern is sent down to an adapter link port, then is immediately returned without actually going out on the port. The returned data is subsequently validated for integrity.

External Loopback – A diagnostic test in which a random data pattern is sent down to an adapter link port. The data goes out of the port and immediately returns via a loopback connector. The returned data is subsequently validated for integrity.

To run loopback tests:

1. From the Emulex Device Management tree-view, select the FC adapter physical port on which you want to run the loopback test.

2. Select the Diagnostics tab (Figure 9-1 on page 165). In the Loopback Test area of the dialog box, choose the type of loopback test you want to run and define the loopback test parameters.

Figure 9-1 FC Adapter Diagnostics Tab



166

Note: You must insert a loopback plug in the selected adapter before running an External Loopback test. Also, you must ensure that the NIC function of the port goes to a link up state.

3. Click Start Test. The following warning is displayed (Figure 9-2 on page 166).

Figure 9-2 Diagnostic Tests Warning

4. Click Yes. A progress bar shows that the test is running.5. Periodic test feedback, consisting of the current loopback test/cycle plus the

completion status of each type of test, is displayed in the Test Status section of the dialog box. Click Show Test Logs to view and save the log file.

Running End to End (ECHO) TestsRun echo tests using the End-to-End (ECHO) Test section of the Diagnostics tab. The end-to-end test enables you send an ECHO command/response sequence between an adapter port and a target port.

To run end-to-end echo tests:

1. From the Emulex Device Management tree-view, select the FC adapter physical port on which you want to initiate the End-to-End (ECHO) test.

2. Select the Diagnostics tab (Figure 9-1 on page 165). In the End-to-End (Echo) Test area, select Echo Test.

3. Enter the WWPN for the target. The Diagnostic Test warning appears (Figure 9-13 on page 176).

4. Click Yes. A result screen appears and the test results appear in the Test Log. 5. Click Clear to erase the contents of the log display or click Save to File to save the

log file.

Note: The ECHO test button is enabled only if its port has targets connected.

Running D_Port Tests (LPe16000–Series FC Adapters)D_Port is a diagnostic mode supported by Brocade switches only for the LPe16000 family of FC adapters with D_Port support.

Note: D_Port is also referred to as ClearLink.

D_Port tests detect physical cabling issues that can result in increased error rates and intermittent behavior. When activated, D_Port tests include:

Local electrical loopback



167

Loopback to the remote optics Loopback from the remote port to the local optics A full device loopback test with data integrity checks An estimate of cable length (to validate that a proper buffering scheme is in

place)

These tests allow a level of fault isolation to distinguish faults due to marginal cable, optics modules, and connector or optics seating.

To run D_Port tests:

1. From the Emulex Device Management tree-view, select the FC adapter physical port for which you want to run the D_Port tests.

2. Select the Diagnostics tab and in the Standard Tests area, click Launch (Figure 9-3 on page 167).

Figure 9-3 FC Adapter Diagnostics Tab with D_Port Tests Option

3. The D_Port Tests dialog box is displayed (Figure 9-4 on page 168), click Start Test.



168

Figure 9-4 D_Port Tests Dialog Box

The D_Port tests are launched. If all tests pass, a dialog box similar to Figure 9-5 on page 169 is displayed. If all tests do not pass, the Failed result in shown in the Test Phase Results. See Figure 9-6 on page 169 for an example.

Click Save Results to File to save the test results to a text file. You can view this text file in any text editor.

Notes

To stop tests, click Stop Test. The D_Port tests can take an extended period of time to complete. If the Overall Test Result is FAILED, you must re-run the tests successfully or

reset the HBA port to bring the link back up. If an older version of an SFP is used in an adapter's port, which does not fully

support all D_Port tests, some of the test phase results report skipped. If an older SFP version is detected by the OneCommand Manager for VMware vCenter, a message is displayed under the results box indicating that the SFP version does not fully support all D_Port tests.

If a test phase fails, the D_Port diagnostics are automatically stopped. In this case, some of the phases may not be reported in the results. However, the failed phase will be reported.



169

Figure 9-5 D_Port Tests Dialog Box - Passed Results

Figure 9-6 D_Port Tests Dialog Box - Failed Results



170

Running a Power-On Self-Test (POST)The POST is a firmware test normally performed on an adapter after a reset or restart. The POST does not require any configuration to run.

To run the POST:

1. From the Emulex Device Management tree-view, select the FC adapter physical port on which you want to run the POST.

2. Select the Diagnostics tab (Figure 9-1 on page 165) and in the Standard Tests area, click Start Test. A progress window appears, showing the progress of the POST test.

3. After the test is completed, the Test Completion Status window appears. Click OK. A POST window is displayed with the POST information.

Using BeaconingBeaconing enables you to force a specific adapter’s LEDs to blink in a particular sequence. The blinking pattern acts as a beacon, making it easier to locate a specific adapter among racks of other adapters.

When you enable beaconing for CNAs, the two LEDs blink rapidly in unison until you disable beaconing.

Note: Beaconing is disabled if the selected adapter does not support beaconing.

To enable or disable beaconing:

1. From the Emulex Device Management tree-view, select the adapter port whose LEDs you want to set.

2. Select the Diagnostics tab (Figure 9-1 on page 165) and click Beacon On or Beacon Off.

Setting Up Diagnostic Test OptionsSetting up test options include error actions, test cycle counts, and test patterns.

Setting Up a Test Failure Error ActionThere are two error action options in the event of a test failure:

Stop Test – Does not log the error and aborts the test. No further tests are run. Ignore – Logs the error and proceeds with the next test cycle.

Setting Up Test CyclesSpecify one of the following test cycles:

Select an established cycle count by clicking on the corresponding radio button. Enter a custom cycle count in the blank field in the Test Cycles area. Set the test to run until you manually click Stop Test, by selecting the Infinite

radio button.



171

Setting Up a Test PatternEnter a custom test pattern to be used in tests that transfer data. The test pattern can be up to eight hexadecimal bytes.

Test StatusThe Test Status area shows how many completed cycles of each test ran, as well as the number of errors.

Saving the Log FileYou can save the test log to a log file for later viewing or printing. When data is written to a saved file, the data is appended at the end of the file. Each entry has a two-line header with the adapter identifier and the date and time of the test. The data accumulates to form a chronological history of the diagnostics performed on the adapter.

The default location is the OneCommand Manager for VMware vCenter install directory on your local drive.

In the VMware Server: There is no default directory for ESXi.

After writing an entry into the log, you are prompted to clear the display. Figure 9-7 on page 171 shows the Diagnostic Test log entries that will be saved to the log file.

Figure 9-7 Diagnostic Test Log Entries

To save the log file:

1. After running a test from the Diagnostic tab, click Show Test Logs. The Diagnostic Test Logs dialog box appears. The default name of a saved file is DiagTest.log.

2. Browse to the desired directory, change the log file name if you want and click Save to File.



172

Creating Port Diagnostic DumpsDiagnostic dump enables you to create and manage a diagnostic dump for a selected FC port. Dump files contain information, such as firmware version and driver version for example, that is particularly useful when troubleshooting an adapter.

To start a diagnostic dump:


2. In the Emulex Device Management tree-view, select the FC port.3. Select the Diagnostic Dump tab (Figure 9-8 on page 172). Diagnostic Dump

information is displayed.

Figure 9-8 FC Port Diagnostic Dump Tab

4. Enter a name in the Dump File Directory field in the Dump Details area to set the dump file directory. A prefix of /vmfs/volumes is added to the location, if it is not specified.

5. To specify up to 20 files to retain using the Dump Files Retention counter, enter the number of files and click Update.

6. Click Start Dump to initiate a diagnostic dump on the selected FC port. Click Delete Existing Dump Files to remove existing dump files for the selected FC port.

Caution: Disruption of service can occur if a diagnostic dump is run during I/O activity.

Diagnostic Dump Tab Field Definitions Serial Number – The port WWN. Dump File Directory – The location where the dump files are created. Dump File Retention – The number of dump files per FC port to retain on the

host.



173

Diagnostic Dump Tab Buttons

Modify Dump Directory – Click to modify the dump file directory. Update – Click to change the dump file retention count. Delete Existing Files – Click to remove existing dump files from the selected FC

port. Start Dump – Click to initiate a diagnostic dump on the selected FC port. Show Dump Files – Click to view the diagnostic dump files generated through

the diagnostic dump feature.

Viewing Diagnostic Dump FilesDiagnostic dump file names can be viewed using the OneCommand Manager for VMware vCenter. The dump files are stored on the host’s data store and the vSphere client can be used to download dump files by browsing the host data store.

To view the FC port diagnostic dump:

1. On the Diagnostic Dump tab, click Show Dump Files. The Diagnostic Dump Files window opens showing the diagnostic dump files currently on your system (Figure 9-9 on page 173). These files are available in the dump directory configured from the Diagnostic Dumps tab. You can extract these files using the vSphere client.

Figure 9-9 Diagnostic Dump Files window

2. Extract the dump files by using the vSphere client to download the dump files by browsing the data store.a. Click the Configuration tab in the vSphere client. The Datastores view is

displayed (Figure 9-10 on page 174).b. Right-click the datastore where the dump file is located, and select Browse

Datastore... from the context menu. A Datastore Browser window opens (Figure 9-11 on page 174).



174

c. In the Datastore Browser, right-click the dump file that you want to review and select Download... from the context menu. A Browse for Folder window opens.

d. Select the desired location for the dump files in the Browse for Folder window and press OK. The file is down loaded to the location you select.

You can view the dump file in any text editor.

Figure 9-10 Datastores View of vSphere Client

Figure 9-11 vSphere Datastore Browser


9. DiagnosticsOneConnect Diagnostics

175

OneConnect DiagnosticsWhen running port diagnostic tests using OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host.

Running Loopback TestsRun the following loopback tests:

PHY Loopback – The PHY loopback test connects the transmit output of the physical layer to the receive input of the physical layer. The data is transmitted, received, and checked for data miscompute errors.

MAC Loopback – The MAC loopback test connects the transmit output of the MAC controller to the receive input of the MAC controller (bypassing the PHY).

To run loopback tests:

1. From the Emulex Device Management tree-view, select the physical port on which you want to run the loopback test.

2. Select the Diagnostics tab (Figure 9-12 on page 175). In the Loopback Test area of the dialog box, choose the type of loopback test you want to run and define the loopback test parameters.

Figure 9-12 OneConnect Adapter Diagnostics Tab

You must insert a loopback plug in the selected adapter before running an External Loopback test. Also, you must ensure that the NIC function of the port goes to a link up state.

3. Click Start Test. The following warning is displayed (Figure 9-13 on page 176).



176

Figure 9-13 Diagnostic Tests Warning

4. Click Yes. A progress bar shows that the test is running.

Periodic test feedback, consisting of the current loopback test/cycle plus the completion status of each type of test, is displayed in the Test Status section of the dialog box. Click Show Test Logs to view and save the log file.

Using BeaconingBeaconing can force an adapter’s LEDs to blink in a particular sequence. The blinking pattern acts as a beacon, making it easier to locate a specific adapter among racks of other adapters.

When you enable beaconing for OneConnect adapters, the two LEDs blink rapidly in unison until you disable beaconing.

Note: Beaconing is disabled if the selected adapter does not support beaconing.

To enable or disable beaconing:

1. From the Emulex Device Management tree-view, select the adapter port whose LEDs you want to set.

2. Select the Diagnostics tab (Figure 9-12 on page 175) and click Beacon On or Beacon Off.

Running a TDR Test (10GBASE–T–Series Adapters Only)To run a TDR test:

1. From the Emulex Device Management tree-view, select the adapter port on which you want to run a TDR test.

2. Select the Diagnostics tab (Figure 9-12 on page 175).3. In the TDR area, enter an NVP value. This value compares the cable speed of

reflection versus the speed of light.4. Click Start TDR Test.



177

Setting Up Diagnostic Test OptionsSetting up test options include error actions, test cycle counts, and test patterns.

Setting Up a Test Failure Error ActionThere are two error action options in the event of a test failure:

Stop Test – Does not log the error and aborts the test. No further tests are run. Ignore – Logs the error and proceeds with the next test cycle.

Setting Up Test CyclesSpecify one of the following test cycles:

Select an established cycle count by clicking on the corresponding radio button. Enter a custom cycle count in the blank field in the Test Cycles area. Set the test to run until you manually click Stop Test, by selecting the Infinite

radio button.

Setting Up a Test PatternEnter a custom test pattern to be used in tests that transfer data. The test pattern can be up to eight hexadecimal bytes.

Test StatusThe Test Status area shows how many completed cycles of each test ran, as well as the number of errors. Periodic test feedback, consisting of the current loopback test/cycle plus the completion status of each type of test, is displayed in the Test Status area. Click Show Test Logs to view and save the log file.

Saving the Log FileSave the test log to a log file for later viewing or printing. When data is written to a saved file, the data is appended at the end of the file. Each entry has a two-line header that contains the identifier of the adapter being tested and the date and time of the test. Over time, the data accumulates to form a chronological history of the diagnostics performed on the adapter.

The default location is the OneCommand Manager for VMware vCenter install directory on your local drive.

In the VMware Server: There is no default directory for ESXi.

After writing an entry into the log, you are prompted to clear the display. Figure 9-7 on page 171 shows the Diagnostic Test log entries that will be saved to the log file.

To save the log file:

1. After running a test from the Diagnostic tab (Figure 9-12 on page 175), click Show Test Logs. The Diagnostic Test Logs dialog box appears. The default name of a saved file is DiagTest.log.



178

2. Browse to the desired directory, change the log file name if you want and click Save to File.

Creating OneConnect Adapter Port Diagnostic DumpsDiagnostic dump enables you to create and manage a diagnostic dump for a selected OneConnect adapter port. Dump files contain information, such as firmware version and driver version for example, that is particularly useful when troubleshooting an adapter.

To start a diagnostic dump:


2. In the Emulex Device Management tree-view, select the port.3. Select the Diagnostic Dump tab (Figure 9-14 on page 178).

Figure 9-14 Port Diagnostic Dump Tab

4. Enter a name in the Dump File Directory field in the Dump Details area to set the dump file directory. A prefix of /vmfs/volumes is added to the location, if it is not specified.

5. To specify up to 20 files to retain using the Dump Files Retention counter, enter the number of files and click Update.

6. Click Start Dump to initiate a diagnostic dump on the selected FC port. Click Delete Existing Dump Files to remove existing dump files for the selected OneConnect port.

Caution: Disruption of service can occur if a diagnostic dump is run during I/O activity.

Diagnostic Dump Tab Field Definitions Serial Number – The port WWN. Dump File Directory – The location where the dump files are created. Dump File Retention – The number of dump files per port to retain on the host.



179

Diagnostic Dump Tab Buttons

Modify Dump Directory – Click to modify the dump file directory. Update – Click to change the dump file retention count. Delete Existing Files – Click to remove existing dump files from the selected

OneConnect port. Start Dump – Click to initiate a diagnostic dump on the selected port. Show Dump Files – Click to view the diagnostic dump files generated through

the diagnostic dump feature.

Viewing Diagnostic Dump FilesDiagnostic dump file names can be viewed using the OneCommand Manager for VMware vCenter. The dump files are stored on the host’s data store and the vSphere client can be used to download dump files by browsing the host data store.

To view the FC port diagnostic dump in the OneCommand Manager for VMware vCenter:

1. On the Diagnostic Dump Tab (Figure 9-14 on page 178), click Show Dump Files. The Diagnostic Dump Files window is displayed, showing the diagnostic dump files currently on your system (Figure 9-15 on page 179). These files are available in the dump directory configured from the Diagnostic Dumps tab. You can extract these files using the vSphere client.

Figure 9-15 Diagnostic Dump Files window

2. Extract the dump files by using the vSphere client to download the dump files by browsing the data store.a. Click the Configuration tab in the vSphere client. The Datastores view is

displayed (Figure 9-10 on page 174).



180

b. Right-click the datastore where your dump file is located, and select Browse Datastore... from the context menu. A Datastore Browser window opens (Figure 9-11 on page 174).

c. In the Datastore Browser, right-click the dump file that you want to review and select Download from the context menu. A Browse for Folder window opens.

d. Select the desired location for the dump files in the Browse for Folder window and press OK. The file is down loaded to the location you select.

You can view the dump file in any text editor.


10. Generating and Installing Secured CertificatesSecure Sockets Layer (SSL) Certificate

181

10. Generating and Installing Secured Certificates

OCMNG is a web application, based on a client-server model, running on the Apache Tomcat Web Server. Data is exchanged between the client (browser) and the server (on a remote machine) which requires a secure user login to manage Emulex adapters on different and multiple hosts.

Secure Sockets Layer (SSL) CertificateAn SSL certificate establishes an encrypted connection between the web server and the web browser on a remote machine. This connection allows private information to be transmitted without eavesdropping, data tampering, or message forgery.

An SSL certificate provides security through encryption and authentication. Encryption is ensured by accessing the remote server using the HTTPS protocol and an SSL certificate.

Note: If OneCommand Manager for VMware vCenter is running, the server must be configured to support HTTPS protocol access and provide a self-signed certificate.

The OneCommand Manager for VMware vCenter server is authenticated to the browser by a Public Key in the self-signed certificate.

Generating an SSL CertificateTo allow secured communication between the client and server, perform these steps:

1. Generate a self-signed certificate with a keystore for each server providing the server's domain name and company details. See “Generating a Self-Signed Certificate” on page 182 for instructions. For more information, see the X.509 attributes list on the International Telecommunications Union website.

2. Use this certificate to create a request to the customer's trusted certificate authority (CA). The request certificate is referred as a Certificate Signing Request (CSR). The CA issues a new SSL certificate.“Generating a CSR for a Server Using the Java Tool” on page 183 for instructions.

3. Import the new SSL certificate to the application server and install the SSL certificate on the client's browser. See “Installing the Certificates to the Keystore of OneCommand Manager for VMware vCenter” on page 184 for instructions.

4. Configure the server to use the keystore file. “Configuring the Tomcat Web Server” on page 185 for instructions.

5. Access the server's content through the browser using 'HTTPS' protocol.

The browsers understand the certificate and the browsers allow access to and from the remote server.


10. Generating and Installing Secured CertificatesGenerating a Self-Signed Certificate

182

Generating a Self-Signed CertificateA self-signed certificate is a certificate that is signed by itself (the server hosting OneCommand Manager for VMware vCenter) rather than a trusted CA. This self-signed certificate includes a public or private key that is distributed by the SSL to verify the identity of the server.

A self-signed certificate can also be used as an alternative to SSL certificates if the server is not running in a public domain.

If a self-signed certificate is used in place of an SSL, a warning is shown in the browser before accessing the server content.

For Java-based applications, a self-signed certificate can be generated using the tools provided by Java. This creates a keystore file which must be installed on the web-server. This keystore includes a private key specific to the server used for generating a CSR and authenticating the server.

As the OneCommand Manager for VMware vCenter server is developed using Java, it leverages the keytool tool provided by Java to generate the self-signed certificates at no cost.

Note: The self-signed certificate for the OneCommand Manager for VMware vCenter server is generated and installed on its server as part of the OneCommand Manager for VMware server installation on a Windows machine. This self-signed certificate is generated with Emulex organization details using RSA algorithm and private key of size 2048 bits.

To generate a self-signed certificate:

1. In the OCM for VMware installation directory, go to ApacheTomcat\conf.>>cd /d "C:\Program Files\Emulex\OCM for VMware\ApacheTomcat\conf"

2. Run the following command:>> ..\..\JRE\bin\keytool.exe -genkey -alias <new-alias> -keyalg RSA -keystore emulex.vcplugin.jks -keysize 2048

Note: You can change alias, keysize, and keystore name.

Example

Enter keystore password: (Enter "emulex" if using the same keystore name)Re-enter new password:

What is your first and last name?

[Unknown]: pluginserver.ad.emulex.com (Give the complete domain name of the server [FQDN])What is the name of your organizational unit?

[Unknown]: ocm

What is the name of your organization?

[Unknown]: elx

What is the name of your City or Locality?

[Unknown]: bg

What is the name of your State or Province?

[Unknown]: ka


10. Generating and Installing Secured CertificatesGenerating a Certificate Signing Request (CSR)

183

What is the two-letter country code for this unit?

[Unknown]: in

Is CN=pluginserver.ad.emulex.com, OU=ocm, O=elx, L=bg, ST=ka, C=in correct?

[no]: yes

Enter key password for <elxocm>:

(RETURN if same as keystore password)

Generating a Certificate Signing Request (CSR)A CSR is a block of encrypted text that is generated on the server on which the certificate will be used. A CSR contains information to be included in the SSL certificate such as the organization name, common name (domain name), locality, country, and other X.509 attributes. It also contains the public key that will be included in the certificate. The CA uses the CSR to create a new SSL certificate.

Generating a CSR for a Server Using the Java ToolTo generate a CSR for a server, use the Java tool available in the jre/bin folder. The syntax using the Java tool is:

keytool -certreq -keyalg <algorithm> -alias <alias-name> -file <csr-name> -keystore <keystore-name>

Example

keytool -certreq -keyalg RSA -alias selfsigned -file elxocmreq.csr -keystore emulex.vcplugin.jks

Generating and Validating a CSRTo generate a CSR:

1. Generate a self-signed certificate (See “Generating a Self-Signed Certificate” on page 182 for instructions).

2. Generate a CSR using the following syntax:>>..\..\JRE\bin\keytool -certreq -v -alias <new-alias> -file elxocmreq.csr -keypass elxocm -keystore emulex.vcplugin.jks

Enter the keystore password: (Enter "emulex" if using the default keystore name)Certification request stored in file <elxocmreq.csr>

To validate a CSR for its completeness:

You can validate the generated CSR for its completeness before submitting (with the help of the CA). Copy the CSR content at the below link for validation.

http://www.sslshopper.com/csr-decoder.html

Note: The CSR must begin and end with the tags:

"-----BEGIN NEW CERTIFICATE REQUEST-----" and "-----END NEW CERTIFICATE REQUEST-----".



184

Example

-----BEGIN NEW CERTIFICATE REQUEST-----

MIIC2TCCAcECAQAwZDELMAkGA1UEBhMCaW4xCzAJBgNVBAgTAmthMQswCQYDVQQHEwJiZzEMMAoG

A1UEChMDZWx4MQwwCgYDVQQLEwNvY20xHzAdBgNVBAMTFmJnc3N5ZWQxLmFkLmVtdWxleC5jb20w

ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCDhovljXhfjNPM/5eBsX4280AIl3YARn0p

R6Z7eOqs1r5Qh07kT58M6T8fER+NpIN7WhOOF/TbsFsS0gmfYwJQqttvtq1dtxUGpvFe9lywbP+l

kY+w6GOyPTG2qnXgILtX5ArZbC2UBbz+J8WJ3SjPHXiSY35EZWnyZZmIN8v1vOe9e21f8vwRkn/4

fdfFrpoQa3H+GcAJMRSBRTd5H6mXQv6HaA5Z0BbsABisFx4scqSuM/HJKLP6GcSHR61bzHfiO/NH

4qU/s6I2LC5DvGs1hIW3PPbmb1rxBiEFpjPtWhfzPxPMKSU8uey+lE0UIPMS0FMTxo63oYnMeiSX

X5mxAgMBAAGgMDAuBgkqhkiG9w0BCQ4xITAfMB0GA1UdDgQWBBSvpKLBF3lY03Jin9kI4ym94bJi

zjANBgkqhkiG9w0BAQsFAAOCAQEAfs94wzEUlDAMq0jITi6fiD7YxK2KFWJgMBfjxZIGex2zxlHL

mOS14BGSWk5dvSMwqDBC14l4C79rUOlTUwwWs9zFqMHynndQ2Ze2vuJNTWUlnFyFb37/rEvbFufB

QVvFXgycaKRgUpWo2x5sekRJRAPxXI/vLWOFRLLrzcVykgZ/sg3QrO4ezlKFc49put0vKpvI1dY9

l9BN2REuWrlmq5y3L8nx8mKX9dRmP6CKzHBaVrvY+nVju+Vf/ikfTtQIDEXAIW2Q7AObpcOaudnf

Nsaey+u27vGy77gAv7092xBHsDyOrD7COy/83b194igmVBVY4dt0496oXkOHCA0txA==

-----END NEW CERTIFICATE REQUEST----

Getting an SSL CertificateThe CSR can be submitted to the trusted CA (as chosen by the user). The CA will validate the CSR and issue a new SSL Certificate.

Installing the SSL into the Web ServerOn receiving the SSL certificate from the CA, the customer must install the SSL certificate on the server to accept the secure connections.

Note: The CSR must be generated on the same machine that the server is running. The SSL certificate must also be installed on this same server.

Installing the Certificates to the Keystore of OneCommand Manager for VMware vCenterThe Root Certificate file, the Intermediate Certificate file, and the Primary Certificate file must all be installed in the keystore.

To install the certificates to the keystore of OneCommand Manager for VMware vCenter:



185

1. Download the SSL certificate file from the CA. Save the SSL certificate file to the same directory as the keystore (self-signed certificate) that was created for the CSR.

Note: The certificate will only work with the same keystore that was initially created the CSR. The certificate must be installed to your keystore in the correct order.

2. Install the Root Certificate file.

Every time you install a certificate to the keystore you must enter the keystore password that you chose when you generated it. Enter the following command to install the Root certificate file:

keytool -import -trustcacerts -alias root -file RootCertFileName.crt -keystore keystore.key

If the following message is displayed:

Certificate already exists in system-wide CA keystore under alias <...> Do you still want to add it to your own keystore?

Select Yes.

If successful, the following message is displayed:

Certificate was added to keystore.

3. Install the Intermediate Certificate file.

If the CA provided an intermediate certificate file, you must install it here using the following command:

keytool -import -trustcacerts -alias intermediate -file IntermediateCertFileName.crt -keystore keystore.key


Certificate was added to keystore.

4. Install the Primary Certificate file.

Use following command to install the Primary Certificate file (for your domain name):

keytool -import -trustcacerts -alias tomcat -file PrimaryCertFileName.crt -keystore keystore.key


Certificate reply was installed in keystore.

All the certificates are now installed to the keystore file. You must configure your server to use the keystore file.

Configuring the Tomcat Web Server

Note: These configuration changes are not required if the default keystorename and password are used. If they are different, you must change the configuration as needed.



186

1. Copy the keystore file (or Self-signed Certificate) to a directory (preferably, the conf folder) of the Tomcat Web Server.

2. Open the file ${CATALINA_HOME}/conf/server.xml in a text editor.3. Uncomment the SSL Connector Configuration.4. Make sure the keystorePass matches the password for the keystore and the

keystoreFile contains the path and filename of the keystore.

Your connector should be displayed similar to the following:

<Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true">

<Factory className="org.apache.catalina.net.SSLServerSocketFactory" clientAuth="false" protocol="TLS" keystoreFile="./conf/emulex.vcplugin.jks" keystorePass="emulex"/>

5. Save the changes to server.xml.6. Restart the Tomcat Web Server.

If you launch the OneCommand Manager for VMware vCenter URL in the browser, the application should be launched without any security warnings.

Note: Use the hostname with the domain name that you used to generate the CSR.


11. TroubleshootingSecurity

187

11. TroubleshootingThis section includes information about certificate or insecure-content warnings that may be displayed on the machine. This section also includes a table with unexpected circumstances and some proposed solutions.

SecurityThe vSphere Web Client server and the OneCommand Manager for VMware vCenter can be installed on different machines. As a result, certificate or insecure-content warnings could occur. There are two ways to remedy the issue:

Accept the blocked content – temporary solution Install a security certificate– permanent solution

Accepting the Blocked ContentThe procedure for accepting blocked content depends on the type of browser you are using. This is not a permanent solution and you must repeat this procedure every time you load the web client. If you want a permanent solution, you must install the correct security certificate. See “Installing a Security Certificate” on page 188.

Internet ExplorerAccept the blocked content (Figure 11-1 on page 187).

Figure 11-1 Blocked Content in Internet Explorer

Chrome and Firefox1. Load the plug-in URL in a separate tab or window.

The plug-in URL format is:

https://<plugin-server>:<https-port>/elxvcplugin

For example:

https://pluginserverhostFQDN:443/elxvcplugin

Note: You can extract the plug-in server, IP address, host name, and port number from the browser warning message.

2. Confirm or accept the certificate warning (Figure 11-2 on page 188).



188

3. Refresh the vSphere web client tab or window.

Figure 11-2 Blocked Content in the Firefox or Chrome Browser

Installing a Security CertificateA permanent solution to the security warnings is to install the correct security certificate.

To install a security certificate:

1. Open Internet Explorer in Administrative Mode.2. Load the plug-in url and accept the certificate warning.

The plug-in url must have the following format:

https://<plugin-server>:<https-port>/elxvcplugin

The page loads with a certificate error.

3. Click on the Certificate Error. A list appears showing the untrusted certificate (Figure 11-3 on page 188).

Figure 11-3 Untrusted Certificate

4. Click View certificates in the Certificate Error list. The Certificate dialog box is displayed (Figure 11-4 on page 189).



189

Figure 11-4 Certificate Dialog Box

5. Click Install Certificate.... The Certificate Import Wizard is displayed (Figure 11-5 on page 189).

Figure 11-5 Certificate Import Wizard

6. Follow the wizard instructions and install the certificate to the Trusted Root Certification Authorities location.



190

There are several circumstances in which your system may operate in an unexpected manner. Table 11-1, Troubleshooting Issues and Resolutions explains some of these circumstances and offers one or more solutions for each issue.

Table 11-1 Troubleshooting Issues and Resolutions

Issue Resolution

The Emulex OneCommand tab is not visible in the vSphere console.

In the vSphere console select the Plug-in menu and choose Manage Plug-ins. In the Plug-in Manager window, check the status of the Emulex OneCommand Manager for VMware vCenter (Emulex OneCommand). The status must be “Enabled”. If it is not, enable it.

On the machine where OneCommand Manager for VMware vCenter is installed, make sure the port numbers configured during the installation are open and dedicated to the plug-in server only. No other service should be listening on this port.

When you select the Emulex OneCommand tab in the vSphere console, a message appears indicating that the Adobe Flash player is required.

Ensure the version of Adobe Flash player installed is 11.2 or later. If you have not installed the Adobe Flash player, you can download it from the Adobe website.

When you select the Emulex OneCommand tab in the vSphere console, the Emulex Device Management tree-view does not display any elements.

Ensure that you have the required privileges to view information in the vSphere console.

There is slow response from OneCommand Manager for VMware vCenter.

Ensure that the following are on the same network:• ESXi servers managed by the OneCommand Manager VMware

for vCenter server• Systems hosting the OneCommand Manager for VMware

vCenter server• OneCommand Manager for VMware vCenter

Firmware update fails on a LightPulse or a OneConnect adapter, or installing licenses fails on a OneConnect adapter.

On the ESXi host, check the firewall settings and ensure that the HTTP/HTTPS ports are open. Use the following command to disable the firewall: esxcli network firewall unload

Firmware update fails with the error message “Error reading resource”.

Check the following:• Make sure that you can ping the hostname, on which the

OneCommand Manager for VMware vCenter is installed, from the ESXi host. If you cannot ping the hostname, either reinstall providing the reachable IP/hostname (with domain) or add the host name to the DNS.

• Check the memory space in the ESXi host and clean up the old logs.

When you make any changes to the ESXi host, such as plugging cables, unplugging cables, or storage references, OneCommand Manager for VMware vCenter does not reflect the change immediately.

Click Refresh in the GUI. If the change is not reflected, restart ‘sfcb’ on the ESXi host using the command:

/etc/init.d/sfcbd-watchdog restart

Click Refresh again in the GUI.



191

On a Windows 7 x64 OS, executing the CLI commands using the executables results in unnecessary error traces.

The C disk is highly protected; even the administrator account has limited privileges. For example, the contents in the directory “C:\Program Files\” have no write and full control privileges.

To remedy the problem:• Assign your account write and full control privileges to

“C:\Program Files \”.

-or-• Install OneCommand Manager for VMware vCenter on another

disk, for example, D.

When OneCommand Manager for VMware vCenter loads within the vSphere console, it shows a Security warning.

See “Security” on page 187.

When the VMware Web Client is launched, it requires OneCommand Manager for VMware vCenter to load in another browser tab and accept the Emulex Certificate.

See “Security” on page 187.

Table 11-1 Troubleshooting Issues and Resolutions (Continued)

Issue Resolution


12. Using OneCommand Manager for VMware vCenter Command Line Interfaceelxvcpcmd Syntax Usage

192

12. Using OneCommand Manager for VMware vCenter Command Line Interface

The CLI client component of OneCommand Manager for VMware vCenter is installed as part of OneCommand Manager for VMware vCenter installation.

elxvcpcmd Syntax Usage OneCommand Manager for VMware vCenter CLI runs only in TCP/IP mode. OneCommand Manager for VMware vCenter CLI can manage Emulex adapters

in systems with VMware ESXi 5.1, 5.5 and 6.0 environments. CLI Client commands are supported for Windows only. All commands must start with elxvcpcmd.exe. The elxvcpcmd.exe is available

in the OneCommand Manager for VMware vCenter installation directory (which is by default C:\Program Files\Emulex). This component is intended for use in scripted operations within batch files. Each time you run this script from the command line, a single operation is performed.

Most operations retrieve information about an entity on the SAN and show that information on the console.

Most of the CLI client commands require one or more additional parameters that specify the nature of the command

The requested operation must contain at least three characters, or as many as needed to distinguish it from any other operation.

The parameters must be specified in the order indicated in the syntax. Parameters that are not required and can be omitted are in square brackets [ ]. To run a command at the cluster level, use:

elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> c=<clustername> <ocm_cmd> [<ocm_cmd_arg>...]

To run a command at the host level, use:elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> h=<esx_host> <ocm_cmd> [<ocm_cmd_arg>...]

For FC and FCoE ports, the WWPN of the adapter must be specified.

Note: When a WWPN is specified, individual fields are separated by colons (:).

For example, run the following command to display the port attributes for the adapter with the specified WWPN:

elxvcpcmd.exe v=10.120.121.122 u=Administrator p=password h=10.120.121.123 portattributes 10:00:00:00:C9:39:6C:9D

For NIC ports, the MAC address must be specified.

Note: When a MAC address is specified, the fields are separated by a dash (-).

For example, run the following command to show the port attributes for the CNA port with the specified MAC address:

OCM for VMware vCenter Version 10.4 User Manual P011049-01A Rev. A

12. Using OneCommand Manager for VMware vCenter Command Line InterfaceHelp Commands

193

elxvcpcmd.exe v=10.120.121.122 u=Administrator p=password h=10.120.121.123 portattributes 00-11-22-33-44-55

For help purposes only, commands are grouped together.

Help CommandsHelp commands include help for a single command or a group of commands.

help (single command)

Syntax elxvcpcmd.exe [CmdName] help

Description This command shows the help for a specific command.

Parameters

help (group)

Syntax elxvcpcmd.exe help

Description

This command shows the help for a group. These help groups are categorized based on the functionality of the commands. Table 12-2 on page 196 shows all supported groups, definitions and supported commands. You can specify the group name in the help command to find the commands supported for a group.

Example Commandelxvcpcmd.exe attributes help

Parameters

None.

CmdName Any CLI command.


12. Using OneCommand Manager for VMware vCenter Command Line InterfaceCLI Command Reference Tables

194

CLI Command Reference TablesTable 12-1 on page 194 lists CLI commands in alphabetical order, with the corresponding page number for details.

Table 12-2 on page 196 lists the CLI commands within a help group. These help groups are categorized based on the functionality of the commands.

Table 12-1 CLI Commands

Command Page

clearisnsserver 240

cmgetparams 214

changepersonality 245

changewwn 251

cmmode 215

cmsetbw 215

D_Port (Clearlink) 224

deletedumpfiles 233

driverconfig 230

dump 234

echotest 225

enablebootcode 213

exportsaninfo 218

firmwareupdate 218

getadapterportconfig 205

getbeacon 225

getdcbparams 219

getdriverparams 230

getdriverparamsglobal 231

getdumpdirectory 234

getdumpfilenames 235

getexpresslanelunlist 248

getfcfinfo 237

getfipparams 238

getinitiatorproperties 240

getiscsiluns 241

getiscsiportstats 241



195

getlunlist 238

getpcidata 208

getpginfo 220

getportstatistics 208

getretentioncount 235

getsessioninfo 242

getvpd 209

getwwncap 209

getxcvrdata 226

hbaattributes 210

installadapterlicense 203

listhbas 210

listprofiles 242

listsessions 243

listvfuncs 246

listvms 250

listvports 251

loadlist 226

loopbacktest 227

pcidata 210

portattributes 211

posttest 228

readwwn 252

reset 203

restorewwn 252

saveconfig 231

serverattributes 211

setadapterportconfig 205

setbeacon 228

setcableenvp 229

setcnapgbw 220

setdcbpriority 222

setdriverparam 232

Table 12-1 CLI Commands (Continued)

Command Page



196

setdriverparamdefaults 233

setdumpdirectory 236

setexpresslanelunstate 249

setfipparams 238

setphyportspeed 212

setportenabled 212

setretentioncount 236

setvcred 202

showisnsserver 243

showlicenseadapterfeatures 204

showlicenseadapterid 204

showpersonalities 246

showtarget 244

sriovenable 247

targetmapping 250

tdrtest 229

umcsetlpvid 216

updateisnsserver 244

VEPAenable 250

version 203

Table 12-1 CLI Commands (Continued)

Command Page

Table 12-2 Help Groups and Supported CLI Commands

Help Group Supported CLI Commands Command Descriptions

General group - General commands that can be run on the OneCommand manager application for VMware servers.

setvccred

reset*

version

setvcred - An optional command that saves vCenter credentials and executes subsequent commands without specifying vCenter credentials.

reset - Resets the adapter.*

version - Shows the version of the installed CLI.



197

AdapterLicense group - Commands to install and read personality licenses for an Emulex adapter.

installadapterlicense

showlicenseadapterfeatures

showlicenseadapterid

installadapterlicense - Installs the license keys from a license file to enable specific features on the adapter.

showlicenseadapterfeatures - Shows the licenses available for the adapter to which the specified port belongs.

showlicenseadapterid - Shows the license ID of the adapter to which a specified port belongs.

Adapter Management group (OCe14000 Adapters only) - Commands to retrieve and set adapter port configuration.

getadapterportconfig

setadapterportconfig

getadapterportconfig - Lists the active and configured adapter port configurations.

setadapterportconfig - Configures the function protocol assignments for all ports on an adapter.

Attributes group - Commands to read and manage information about an adapter

getpcidata*

getportstatistics

getvpd

getwwncap*

hbaattributes

listhbas

pcidata*

portattributes

serverattributes

setphyportspeed

setportenabled

getpcidata - Lists PCI register details for FC, FCoE, NIC, and iSCSI ports.*

getportstatistics - Lists statistics for an FC or FCoE port. If the optional parameter, clear, is set, this command clears the 10GBaseT counters.

getvpd - This command shows the VPD details for the specified port on the adapter.

getwwncap - Shows the WWN capabilities of the specified port.*

hbaattributes - At the host level, shows adapter attributes for a port on the adapter.

listhbas - For a cluster or a host, shows a list of manageable Emulex adapters.

pcidata - Lists PCI attributes for a port on the adapter.*

portattributes - Shows a list of all port attributes for the port on the adapter.

portstatistics -

serverattributes - Lists basic information about the host.

setphyportspeed - For OCe11102 adapters, sets the port speed.

setportenabled - Enables or disables the port status for an FC, FCoE, NIC, or iSCSI port on a host.

Boot Group -Commands to enable an ESXi host to manage the boot environment.

enablebootcode enablebootcode - Enables or disables the booBIOS state on a given port.





198

Channel Management group -Commands to enable and manage an ESXi host to handle Channel Management.

cmgetparams

cmmode

cmsetbw

umcsetlpvid*

cmgetparams - Lists channel management information for the adapter.

cmmode- Enables or disables channel management on the adapter.

cmsetbw - Sets bandwidth for channels on the physical port.

umcsetlpvid - Sets the logical port VLAND IDs for each channel on a physical port.*

Cluster group - Commands that can be run on a cluster.

exportsaninfo

firmwareupdate

listhbas

exportsaninfo - Exports SAN information related to Emulex adapters in all the hosts in a cluster.

firmwareupdate -Updates the firmware on the Emulex adapters found in a VMware cluster or the ESXi host.

listhbas - Lists manageable Emulex adapters.

DCB group - Commands to enable an ESXi host to read and manage data center bridging parameters for an Emulex adapter.

getdcbparams

getpginfo

setcnapgbw

setdcbparam

setdcbpriority

getdcbparams - extracts the DCB parameters associated with a given FCoE, NIC, or iSCSI port.

getpginfo - Lists the priorities and bandwidth percentages for all the priority groups for the port.

setcnapgbw - Sets the bandwidth percentage of a priority group on a port.

setdcbparam - Configures DCB and LLDP settings on a CNA.

setdcbpriority - Sets the priorities for a priority group.

Diagnostic group - Commands to run diagnostic tests for an Emulex adapter or port.

D_Port (Also known as ClearLink)

echotest

getbeacon*

loadlist

loopbacktest

posttest

setbeacon

setcablenvp

tdrtest

D_Port - Runs D_Port diagnostics.

echotest - Runs an echo test on a port.

getbeacon - Shows the current beacon state for a port on an adapter.*

loadlist - Lists the flash memory load list data for an FC port.

loopbacktest - Runs a loopback test on a port.

posttest - Runs a power-on self-test on a specified FC port.

setbeacon - Turns the beacon state on or off for a port on an adapter

setcablenvp - On an OCe11100 T 10GBASE-T-series adapter, sets the NVP (required for the TDRTest command) for the cable that connects to the physical port associated with the WWPN or MAC.

tdrtest - On an OCe11100 T 10GBASE-T-series adapter, runs a test to verify the integrity of the link.





199

DriverParameters group - Commands to enable an ESXi host to read and manage driver parameters for the host and an Emulex adapter.

driverconfig

getdumpdirectory

getdriverparamsglobal

saveconfig

setdriverparam

setdriverparamdefaults

driverconfig - Sets all driver parameters to the values in the .dpv file on an ESXi host.

getdumpdirectory - Lists driver parameters for a port.

getdriverparamsglobal - Lists global driver parameters for a port.

saveconfig - Saves an FC or FCoE adapter’s driver parameters to a file.

setdriverparam - Sets a driver parameter for a port and designates the scope of the change.

setdriverparamdefaults - Restores all driver parameters to the default value, at the port or global level (temporarily or permanently).

Dump group - Commands to manage dump files for a selected adapter. A dump files is useful when troubleshooting.

deletedumpfiles

dump

getdumpdirectory

getdumpfilenames

getretentioncount

setdumpdirectory

setretentioncount

deletedumpfiles - Deletes all diagnostic dump files for a port.

dump - Performs a core dump on a local port of an OCe11102 adapter.

getdumpdirectory - Shows a dump file directory for a port in the host.

getdumpfilenames - Lists all dump filenames for a port.

getretentioncount - Shows the maximum number of diagnostic dump files to keep for a port.

setdumpdirectory - Sets the dump directory for all adapters in the server.

setretentioncount - Specifies the maximum number of diagnostic dump files for the adapter.

FCoE group - Commands to enable an ESXi host to read and manage FCoE functions for an Emulex adapter.

getfcfinfo

getfipparams

getlunlist*

setfipparams

targetmapping

getfcfinfo -Lists Fibre Channel Forwarding information for an adapter in FCoE mode.

getfipparams - Lists FIP parameters for a CNA adapter in FCoE mode.

getlunlist - Lists the LUNs attached to the FC and FCoE target of the specified port.*

setfipparams - Sets FIP parameters for a CNA adapter in FCoE mode.

targetmapping - Lists the targets attached to the FC and FCoE of the specified port.*

Firmware group - A command for an ESXi host to update the firmware for an Emulex adapter or port.

firmwareupdate firmwareupdate - Updates the firmware on Emulex adapters in a VMware cluster or ESXi host.





200

iSCSI group - Commands to enable an ESXi host to read and manage iSCSI functions for an Emulex adapter.

clearisnsserver

getinitiatorproperties

getiscsiluns*

getiscsiportstats

listprofiles

listsessions*

showisnsserver

showtarget*

VEPAenable

clearisnsserver - Clears the configured ISNS server and disables ISNS target discovery.

getinitiatorproperties - Lists all the initiator login options for the specified port.

getiscsiluns - Lists the LUNs attached to the iSCSI target of an iSCSI port.*

getiscsiportstats - Lists the port statistics for an iSCSI port.

listprofiles - Lists available profile IDs and their descriptions for an adapter, including the currently active and configured profile IDs.

listsessions -Lists all the sessions on a specified target.*

showisnsserver - Shows the currently configured Internet Storage name Server.

showtarget - Lists the iSCSI target details of the adapter to which the iSCSI port belongs.*

VEPAenable - Updates the Internet Storage name Server.

Personality group - Commands to enable an ESXi host to read and change personalities for an Emulex adapter

Note: Not supported for the OCe14000–series adapters. Use the setadapterportconfig command for these adapters.

changepersonality

showpersonalities

changepersonality -Changes the valid personality of the adapter to which the specified port belongs.

showpersonalities - Lists the personalities of the adapter to which the specified port belongs.

SR-IOV group - Commands that allow multiple VFs to be created on a NIC PF for an adapter port.

Note: SR-IOV is not supported with UMC channel management.

listvfuncs

sriovenable

listvfuncs - Lists all of the virtual functions discovered.

sriovenable - Enables or disables SR-IOV support for an adapter’s physical port.





201

TargetAndLuns group - Commands to enable an ESXi host to read targets and LUNS attached to the port on an Emulex adapter.

getexpresslanelunlist*

getiscsiluns

getlunlist

listsessions*

setexpresslanelunstate*

showtarget

targetmapping

getexpresslanelunlist - On LPe16000-series and OCe15100–series adapters,lists the LUNs that support ExpressLane and their respective ExpressLane status.*

getiscsilunsgetiscsiluns - Lists the LUNs attached to the iSCSI target of an iSCSI port.

getlunlist - Lists the LUNs attached to the FC and FCoE target of the specified port.

listsessions -Lists all the sessions on a specified iSCSI target.*

setexpresslanelunstate - Enables or disables ExpressLane on a LUN.*

showtarget - Lists the iSCSI target details of the adapter to which the iSCSI port belongs.

targetmapping - Lists the targets attached to the FC and FCoE of the specified port.

VEPA group - A command that enables or disables the VEPA state on an OCe14000-series NIC port.

Note: VEPA commands require that SR-IOV is enabled

VEPAenable VEPAenable - Enables or disabled Virtual Ethernet Port Aggregator (VEPA) on an OCe14000-series NIC port.

Virtual Machines group - Commands to enable an ESXi host to find Virtual Machines and their attached ports.

listvms

listvports

listvms- Lists all virtual machines and their information for all manageable ports.

listvports - Lists all virtual ports on the specified physical port.

WWWNManagement group - Commands to enable ESXi host to read and manage the WWN details for the port on an Emulex adapter.

changewwn

getwwncap

readwwn

restorewwn

changewwn - Changes the WWN of the port.

getwwncap - Lists the WWN capabilities of the port.

readwwn - Lists the WWN details of the port and category.

restorewwn - Restores the WWN value of the port.




12. Using OneCommand Manager for VMware vCenter Command Line InterfaceGroup Commands and CLI Command Descriptions

202

Group Commands and CLI Command DescriptionsThis section provides syntax and descriptions for group and CLI commands.

General Group CommandsThe general group commands save vCenter credentials, reset the adapter, and show the version of the installed CLI.

setvccred

Syntaxelxvcpcmd.exe setvccred v=<vCenter IP/Name> u=<username> p=<password>

Description

While executing a set of CLI commands, you must enter vCenter credentials repeatedly. By executing the “setvccred” command first, you can save these credentials including vCenter server name/IP, username and password to a file in an encrypted format and execute subsequent commands without use of vCenter credentials.

Using this command is optional. You can continue to execute the commands providing all credentials.

Note: This command does not apply to ports or adapters.

Parameters

Examples

Execute setvccred first:

elxvcpcmd.exe setvccred v=12.345.678.901 u=username p=password

Subsequent commands can be:

New format:

elxvcpcmd.exe h=12.345.678.123 listhbas

-or-

Old Format:

elxvcpcmd.exe v=12.345.678.901 u=username p=password h=12.345.678.123 listhbas

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.



203

resetThis command resets the adapter. An adapter reset can require several seconds to complete, especially for remote devices. When the reset is completed, the system command prompt is displayed.

Notes

Supported only for FC and FCoE ports. Not supported for NIC and iSCSI ports. For FCoE ports, this command only resets the driver to update changed driver

parameters that require a driver reset. It does not cause a HW reset of the adapter port.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> reset <WWPN>

Parameters

versionThis command shows the version of the CLI installed.

Syntaxelxvcpcmd.exe version

Parameters

None.

AdapterLicense CommandsThe Adapter License commands install license keys, and show license information.

installadapterlicenseThis command installs the license keys from a license file to enable specific features on the adapter. You must specify either the WWPN or the MAC address.

Note: The InstallAdapterLicense command applies to CNAs only.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password>

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.



204

h=<esx_host> installadapterlicense <WWPN | MAC> [Licence File Path]

Parameters

showlicenseadapterfeaturesThis command shows the licenses available for the adapter to which the specified port belongs.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> showlicenseadapterfeatures <WWPN | MAC>

Parameters

showlicenseadapteridThis command shows the license ID of the adapter to which the specified port belongs.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> showlicenseadapterid <WWPN | MAC>

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.Licence File Path The local file path of the license file to be installed.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.




205

Adapter Management CommandsThe Adapter Management commands show adapter port configurations, set adapter port configurations, and enable or disable MultiChannel.

Note: Adapter Management Commands support only OCe14000-series adapters.

getadapterportconfig After rebooting, the command shows the active and configured adapter port configurations including the total number of ports, the maximum number of FCoE and iSCSI functions that can be defined, and if the adapter allows mixed mode storage and concurrent mode storage, and SR-IOV state. The number of functions per port depends upon the current setup of the adapter (for example, mixed or concurrent storage mode, multichannel, NPar). Depending upon the presence of NParEP on a host, this command may show more functions per port than are actually running on the host.

Note: For multichannel and NPar configurations, this command only shows the port protocol assignments. For the entire multichannel configuration use the cmgetparams command.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc username> p=<vc password> h=<esx host> GetAdapterPortConfig <MAC|WWPN>

Parameters

setadapterportconfigThe setadapterportconfig command configures the function protocol assignments for all ports on an adapter. Additionally use this command to restore the adapter to its factory default profile and settings. The number of ports and function protocol assignments specified in this command depends upon the available ports, storage mode (mixed or concurrent) and multichannel/NPar state. Depending upon the presence of NParEP on a host, this command may allow the configuration of more functions per port than is available on the PCI bus. This means a lesser number of functions per port than are configured by this command may be noticed after rebooting the host. The SR-IOV state can be enabled or disabled using the optional sriov parameter.

MAC The MAC address of the NIC port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FCoE port.MAC The MAC address of the NIC or iSCSI port.



206

Syntaxelxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.203.195 SetAdapterPortConfig <MAC|WWPN> defaults

or

hbacmd SetAdapterPortConfig <MAC|WWPN> p0=P0Config [p1=P1Config] [p2=P2Config][p3=P3Config] [pid=ProfileID] [mctype=Type] [NParEpMode=state][sriov=SriovState]

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC MAC address of any iSCSI or NIC function on the adapter.WWPN World Wide Port Name of any FCoE function on the adapter.p0=fcnCfg 1st port's function(s)p1=fcnCfg 2nd port's function(s) (required for 2 and 4 port adapters)p2=fcnCfg 3rd port's function(s) (required for 4 port adapters)p3=fcnCfg 4th port's function(s) (required for 4 port adapters)fcnCf f0[,f1[,...fM]] where

f0: 1st function protocol on port (must be NIC)f1: 2nd function protocol on port (optional)fM: Mth function protocol on port (optional)

The number of functions (that is, the value of M) per port are model and multichannel type specific.

pid Optionally specifies the profile ID to use for the personality. This parameter is required for NIC only.

Type Optional multichannel type specification (specify none to disable multichannel). This parameter is required to specify multichannel. If not specified, no change to the configured multichannel type is made.

State NParEP Mode state. This parameter can only be specified when mctype=NPar.

Valid states are:

0 = Disabled1 = Enabled

SriovState SR-IOV state

Valid states are:

0 = Disabled1 = Enabled)



207

Syntax Rules for the setadapterportconfig Command

No spaces are allowed between around the = or commas in when specifying a port (e.g. p0 = nic, iscsi would cause an error).

The only choice for the f0 parameter is NIC. Choices for the f1–fm parameters are None, iSCSI or FCoE (or NIC for multichannel configurations).

This command fails if you specify two storage protocols on a port and the concurrent storage mode is not available.

This command fails if you specify three storage functions on a port. This command fails if you specify two of the same storage functions on a port. The number of functions (f) you can specify depend upon the adapter model

and the configuration type (for example, non-multi–channel, multichannel, NPar, etc.). If you specify an incorrect number of functions, the command fails.

You can only specify NIC as the f0 parameter if no other f parameters are specified. Also you cannot specify NIC with multichannel configurations.

The pid=profile_id option is required for NIC only configurations. It you specify an incorrect number of functions, the command fails.

If the mctype parameter is specified, it must be an available multichannel type (see CMGetParams command for available types) or set to None to disable multichannel. If the mctype parameter is not specified, the currently configured multichannel type (including None) remains unchanged.

If one or more functions are set to None and they are the last functions on a port, they do not need to be specified (for example, p0=nic,iscsinone can be shortened to p0=nic,iscsi).

You can only specify NParEPMode with the mctype-NPar parameter or when the current configured MC type is NPar.

When you disable NPar (for example mctype=none), the NParEP Mode is automatically disabled.You must reboot to activate a new port configuration.

SR-IOV can be enabled or disabled only when the mctype is a non-multichannel type such as a single personality, NPAR, or Custom.

Example Commands

Mixed Mode

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 setadapterportconfig 00-00-c9-12-34-56 p0=nic,iscsi p1=nic,fcoe p2=nic,fcoe p3=nic

Concurrent Mode with Two Ports

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 setadapterportconfig 00-00-c9-12-34-56 p0=nic,iscsi,fcoe p1=nic,fcoe

Enabling/Disabling MultichannelUse the Type parameter to enable and disable multichannel. When enabling multichannel, the additional function protocols must be specified for the extra channels that are not available when multichannel is disabled.



208

Examples for Enabling and Disabling Multichannel

To enable multichannel:

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 setadapterportconfig 00-00-c9-12-34-56 p0=nic,iscsi,nic,nic p1=nic,fcoe,nic,nic p2=nic,fcoe,nic,nic p3=nic,iscsi,nic,nic mctype=umc

To disable multichannel:

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 setadapterportconfig 00-00-c9-12-34-56 p0=nic,iscsi p1= nic,fcoe p2=nic,fcoe p3=nic,iscsi mctype=none

Attribute CommandsThe Attribute commands show port information, adapter attributes, pcidata, and server attributes. These commands also enable a port on a host and set physical port speed.

getpcidataThis command shows PCI register details for FC, FCoE, NIC and iSCSI ports.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getpcidata <WWPN | MAC>

Parameters

getportstatisticsThis command extracts the statistics for a designated FC or FCoE port. The optional clear parameter, clears the 10GBaseT counters for an OCe14000-series port.

Note: If the clear parameter is specified for other than an OCe14000-series adapter, an error message is displayed.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getportstatistics <WWPN> [clear]




209

Parameters

getvpdThis command shows the VPD details for the specified port on the adapter.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getvpd <WWPN | MAC>

Parameters

getwwncap

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getwwncap <WWPN>

Description

This command shows the WWN capabilities of the specified port.

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.clear An optional parameter that clears the counters for a 10GBaseT port.





210

hbaattributesThis command shows a list of all adapter attributes for the specified port on the adapter. This command is supported only at the host level.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> hbaattributes <WWPN | MAC>

Parameters

listhbasThis command shows a list of the manageable Emulex adapters found by remote discovery. For NIC ports, instead of the port WWN, the MAC address is displayed.The node WWN and fabric WWN are not displayed.

Syntax

For a cluster:

elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <c=clustername> listhbas

For a host:

elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> listhbas

Parameters

pcidataThis command shows the PCI attributes for the port specified on the adapter.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP>


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.c The cluster name in the vSphere console.h The IP address of the ESXi host with Emulex adapters.



211

pcidata <WWPN | MAC>

Parameters

portattributesThis command shows a list of all port attributes for the port on the adapter.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> PortAttributes <WWPN | MAC>

Parameters

serverattributesThis command is used to retrieve basic information about the host such as the OS version and CIM provider version.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> serverattributes


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port. If the port supports VEPA, the

output contains the line “VEPA State: <enabled | disabled>.



212

Parameters

setphyportspeedThis command sets the port speed on OCe11102 adapters.

Syntax

elxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> SetPhyPortSpeed <WWPN | MAC> <Mode> [Speed [Length]]

Parameters

Example

The following command configures the port to a forced speed of 1 Gb/sec with a cable length of 4 meters.

elxvcpcmd.exe v=11.190.705.200 u=username p=password h=11.190.206.300 setphyportspeed 2 1Gb 4

setportenabledThis command is used to enable or disable an FC, FCoE, NIC or iSCSI port on a host.

Notes

Ensure that all I/O traffic on the port is stopped before disabling the port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FCoE port.MAC The MAC address of the CNA port.Mode Mode number:

0 = Default1 = Auto-Negotiate2 = Force

Note: When Mode = 0, the Speed and Length arguments are ignored. When Mode = 1, the Length arguments is ignored.

Speed Speed string that is required for Mode = 1 or 2 (s=10Gb/1Gb/100Mb).Length DAC cable length in meters (0-10, required for 10Gb SFP Plus

interface type).



213

When the setportenabled command disables an FC port, the adapter must be reset to activate the new setting. Only CNAs do not require a reset when the adapter port is enabled or disabled.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setportenabled <WWPN | MAC> <Flag>

Parameters

Boot CommandThe enablebootcode command enables or disables the bootBIOS state on a port.

enablebootcodeThis command enables or disables the bootBIOS state on a given port by enabling or disabling the boot code on the FC adapter, the PXE BIOS or the iBFT for 16GB ports of the NIC on the CNA.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> enablebootcode <WWPN | MAC> [Flag][NetworkBootMethod]

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.Flag 0 = Disabled

1 = Enabled

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex

adapters.MAC The MAC address of the CNA port.Flag 0 – disable BootBIOS state.

1 – enable BootBIOS state.



214

Channel Management CommandsThe Channel Management commands show channel management information, enable or disable channel management on an adapter, set a channel’s minimum and maximum bandwidth, and set the Logical Port VLAN ID for each channel.

cmgetparamsThis command shows the following information for the adapter:

The active (booted) mode (NPar or disabled) for the adapter The channel management state of the adapter The configured state of the adapter The configured channel management mode, that is N/A if disabled The available channel management modes The port's channels and their channel properties

The protocol type (because the channels are based on all physical ports, some adapters show only two or three channels instead of four because that is all the physical port allows)

The MAC address The LPVID The Minimum and maximum BW

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> cmgetparams <WWPN | MAC>

Parameters

Examples

All NIC

elxvcpcmd.exe v=10.20.30.40 u=username p=password h=10.11.12.13 cmgetparams 00-00-c9-12-34-56

NetworkBootMethod Network boot method to be used by the NIC.

iBFT PXE

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN WWPN of an FCoE function on the physical port.MAC MAC address of any NIC function on the physical adapter port.



215

Multichannel enabled, UMC, Mixed Mode

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 cmgetparams 00-00-c9-12-34-56


NPar enabled - 4 functions/port


cmmodeThis command enables or disables channel management on an adapter.

Note: A system reboot is required for the change to take effect.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> cmmode <WWPN | MAC Address> <None | Type>

Parameters

Example

This command shows that the channel management on an adapter containing a NIC function with a MAC address of [00-00-c9-ad-ad-aa] is disabled.

elxvcpcmd.exe v=10.20.30.40 u=username p=password h=10.11.12.13 CMMode 00-00-c9-bb-cc-aa None

cmsetbwThis command sets the minimum and maximum BW for up to N channels each on the physical port (where N is number of channels enabled on the adapter). The total of the minimum BWs must add up to 100%. The total of the maximum BWs must be greater than or equal to the minimum BWs and have a maximum of 100%. When only three channels are available, specifying Min3,Max3 causes an error. When only two channels are available, specifying Min2,Max2 and Min3,Max3 causes an error.

When in channel management mode, you can disable a channel’s logical link by setting the minimum BW and the maximum BW to 0. If a channel’s protocol is set to None, the

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN WWPN of an FCoE function on the physical port.MAC MAC address of any NIC function on the physical adapter port.None|Type Specify None to disable channel management or specify a channel

management type to enable channel management.



216

minimum and maximum BW must be 0. Setting the minimum BW to a value greater than 0 enables the channel if it was previously disabled.

Notes

This command is not available for 1 Gb ports. For OCe14000–series adapters (with NPar disabled), the total minimum

bandwidth must add up to 0 or 100%. If the adapter is enabled for NPar, the total minimum bandwidth must add up to 100%.

The maximum bandwidth of a channel must be greater than or equal to the minimum bandwidth for that channel up to a maximum of 100.

This command fails if the current channel management mode is vNIC1 or UFP, or None.

When channel management is enabled, a system reboot is not required for the change take effect.

Syntax>elxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> cmsetbw <WWPN | MAC> <Min0,Max0> <Min1,Max1>...[MinN,MaxN]

Parameters

Exampleelxvcpcmd.exe v=10.20.30.40 u=username p=password h=10.11.12.13CMSetBW 00-00-c9-bb-cc-aa 25,50 50,75 0,0 25,100

umcsetlpvidThis command sets the Logical Port VLAN IDs (LPVID) for each channel on a physical port. LPVID values are in the range of 2-4094. When only three channels are available, specifying LPVID3 causes an error. When only two channels are available, specifying LPVID2 and LPVID3 causes an error.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of an FCoE function on the physical port.MAC The MAC address of a NIC function on the physical adapter

port.

Bandwidth Value Note: The number of channels and the maximum value of N are adapter model specific.

Min0,Max0 The minimum and maximum bandwidths for channel 0.Min1,Max1 The minimum and maximum bandwidths for channel 1.MinN,MaxN The minimum and maximum bandwidths for channel 2.



217

Notes

LPVID values are in the range of 2-4094. This is the only command available to set LPVID values. Every NIC channel on a physical port must have a unique LPVID. This command is not available FCoE and iSCSI channels because they are

storage channels. LPVIDs for FCoE and iSCSI channels must be set to ‘0’. This command is not available for 1 Gb ports. If UMC is disabled when this command is executed, a warning message is

displayed stating that UMC is disabled and must be enabled for any changes to take effect.

A system reboot is not required for the change take effect. LPVID properties are only associated with UMC. The umcsetlpvid command

fails if the current channel management mode is not UMC. SR-IOV is not supported with UMC channel management.

Syntax

elxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host>umcsetLPVID <WWPN | MAC> <LPVID0> <LPVID1> [LPVIDN]

Parameters

Exampleelxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 umcsetlpvid 00-00-c9-12-34-56 1001 1002 1003 1004

Cluster CommandsCluster commands export SAN information, update firmware and list adapters.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC MAC address of any NIC function on the physical adapter port.LPVID State

LPVID0 LPVID for channel 0 LPVID1 LPVID for channel 1LPVIDN LPVID for channel N

Note: The number of channels and the maximum value of N are adapter model specific.



218

exportsaninfoThis command exports all SAN information related to Emulex adapters in all the hosts in a cluster. This command is supported only at the cluster level.

Note: Emulex recommends that you redirect this output to a file with a proper extension, .xml for XML-formatted files and .csv for CSV-formatted files. Due to the amount of information that must be obtained and reported, this command can take a long time on large SAN configurations.

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <c=clustername> exportsaninfo [format]

Note: [format] is optional. If the format parameter is specified as csv, the adapter information is shown in CSV format. If the format parameter is specified as xml, the adapter information is shown in XML format. Leaving the format parameter blank shows the data in XML format.

Parameters

firmwareupdateThis command updates the firmware on the Emulex adapters found in the specified VMware cluster or the ESXi host.

Procedure

1. Run the firmwareupdate command. A list of adapter serial numbers (for CNAs) or port WWNs (for FC adapters) are displayed, applicable to the firmware file specified.

2. Select the adapter or port option to use for the update. List, Range, All or Choice options are displayed.

The firmware update process begins and returns the result for each adapter or port.

3. If you press <Ctrl> + <C> and the firmware update process has started on any adapter or port, the update continues. But if the firmware update process is queued, the update is cancelled.

Note: The optional argument [all|WWNs|MACs] updates the firmware without any user prompt. Either all or a combination of WWNs and MACs can be given as an option.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.c The cluster name.Format csv – The output information in CSV format.

xml – The output information in XML format (default).



219

You can view the status of submitted firmware jobs on the OneCommand Manager VMware for vCenter, Maintenance tab of the cluster or host.

Syntax

For a cluster:

elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> c=<clustername> firmwareupdate [all|WWNs|MACs] <filelocation>

For a host:

elxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> h=<ESXhostIP> firmwareupdate [all|WWNs|MACs] <filelocation>

Parameters

listhbasSee “listhbas” on page 210.

DCB CommandsDCB commands show DCB parameter information, show priority and bandwidth percentages for all priority groups, configure the DCB and LLDP settings on an adapter, and set bandwidth percentage of a priority group on a port.

getdcbparamsThis command extracts the DCB parameters associated with a given FCoE, NIC or iSCSI port.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getdcbparams <WWPN | MAC>

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.c The cluster name in the vSphere console.h The IP address of the ESXi host with Emulex adapters.all|WWNs|MACs (optional)

The all optional argument updates all compatible adapters or ports without any user prompt. The WWNs or MACs optional argument updates the port WWNs or MACs belonging to a specified cluster or host without any user prompt.

file_location The firmware file path on the local disk.

v The vCenter server IP address.u The user name for the vCenter server.



220

getpginfoThis command shows the priorities and bandwidth percentages for all the priority groups for the port. Additionally, this command shows the number of priority groups supported by an adapter.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getpginfo <WWPN>

Parameters

setcnapgbwThis command sets the BW percentage of a priority group on a given FCoE, NIC or iSCSI port according to the following rules:

BW0 to BW7 must add up to 100%. BW can be assigned to a priority group that has priorities.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setcnapgbw <WWPN | MAC> <BW0>...<BW7>

Parameters

p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FC or FCoE port.MAC The MAC address of the NIC or iSCSI port.


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.BW0 to BW7 The BW for priority group 0 to 7.



221

Example

This command sets the bandwidth of PGID0 to 50 PGID1 to 50 and the rest to 0%.

elxvcpcmd.exe setcnapgbw 10:00:00:00:c9:3c:f7:88 50 50 0 0 0 0 0 0

setdcbparamThis command configures the DCB and LLDP settings on a CNA.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setdcbparam <WWPN | MAC> <Param> <Value>

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.

Param and Value Parameters

DCB Parameters and Values (1 = Enabled and 0= Disabled)DCBXState The current DCBX (Data Center discovery and Capability exchange

protocol) state.PFCEnable If set to 1, there is flow control in both directions (Tx and Rx).FCoEPriority You must specify a single priority (0-7). [only for FCoE adapters]iSCSIPriority You must specify a single priority (0-7). [only for iSCSI adapters]PFCPriorities Specify PFCPriorities as a single priority or as a list of comma

separated values (up to 7 values ranging from 0-7).Default Setting the SetDCBParam arguments to default sets all CNA DCB

parameters (including priority groups) to their default values.

Link Layer Discovery Protocol (LLDP) Parameters and ValuesTxState Transmit State – 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.

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

TxPortDesc Transmit Port Description – Provides a description of the port in an alpha-numeric format. The value equals the ifDescr object, if the LAN device supports RFC 2863.



222

Example Commandelxvcpcmd v=12.345.678.901 u=username p=password h=12.345.678.123 setdcbparam 00-00-c9-3c-f7-88 fcoepriority 3

setdcbpriority

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setdcbpriority <WWN | MAC> <PFC Priorities> <Priorities of PGID0> < Priorities of PGID1>...<Priorities of PGID7>

Description

This command sets the priorities for a priority group. The values must be set according to the following rules:

The priorities range from 0 to 7. The PGIDs range from 0 to 7. A priority can exist in only one priority group. All priorities must appear once in any of the eight (PG0-PG7) priority groups. Each set of priorities for a group must be separated by a space. Specify multiple priorities for the same group by a comma-separated list. To specify none, use - for the argument. The same priority values cannot be specified to different groups. All priorities (0 to 7) must be assigned to a PGID. Not all PGIDs must be assigned a priority. Not all adapters support two PFC priorities and eight priority groups. For

adapters, if you exceed the PFC priorities or priority groups an error message appears.

TxSysDesc Transmit System Description – Provides a description of the network entity in an alpha-numeric format. This includes the system's name and versions of HW, OS, and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418.

TxSysName Provides the system's assigned name in an alpha-numeric format. The value equals the sysName object, if the LAN device supports RFC 3418.

TxSysCap Transmit System Capabilities - Indicates the primary function(s) of the device and whether or not these functions are enabled on the device. The capabilities are indicated 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. Where multiple values are possible, specify them with a comma-separated list.



223

FCoE Adapter Specific Rules:

Minimum of one and a maximum of two PFC priorities can be configured. One of the PFC priorities must match FCoE priority. The additional PFC priority must be assigned to a priority group that has no

other priorities. The FCoE priority must be assigned to a priority group that has no other

priorities.

iSCSI Adapter Specific Rules:

Minimum of one and a maximum of two PFC priorities can be configured. One of the PFC priorities must match iSCSI priority. The additional PFC priority must be assigned to a priority group that has no

other priorities. The iSCSI priority must be assigned to a priority group that has no other

priorities.

NIC Adapter Specific Rules:

Only one PFC priority can be configured. The PFC priority must be assigned to a priority group that has no other

priorities.

Parameters

Example Commandelxvcpcmd v=12.345.678.901 u=username p=password h=12.345.678.123 setdcbpriority 10:00:00:00:c9:3c:f7:88 3 0,1,2,4,5,6,7 3 0 0 0 0 0 0

Diagnostic CommandsThe Diagnostic commands run diagnostics including POST, loopback, and TDR tests. Diagnostic commands also show and set beacon status, set the nominal velocity of propagation (N-V-P), required for the TDR test (OCe11100 T 10GBASE-T–series adapters only), and run the D_Port diagnostic (LPe16000-series FC adapters only).

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.PFCPriorities PFC priority that is a comma separated list of up to 7 values ranging

from 0-7.Priorities of PGID

Priority group membership that is a comma separated list of priorities ranging in value for 0-7.



224

D_Port

elxvcpcmd.exe v=10.192.000.000 u=root p=password d_Port WWPN

Description

The D_Port diagnostic is also known as ClearLink. The D_Port diagnostic tests are run from the OneCommand Manager for VMware vCenter CLI by specifying the D_Port command. D_Port is a diagnostic mode supported by Brocade switches only for the LPe16000-series FC adapters with D_Port support.

D_Port tests detect physical cabling issues that can result in increased error rates and intermittent behavior. When activated, D_Port tests include:

Local electrical loopback Loopback to the remote optics Loopback from the remote port to the local optics A full device loopback test with data integrity checks An estimate of cable length (to validate that a proper buffering scheme is in

place)

These tests allow a level of fault isolation to distinguish faults due to marginal cable, optics modules, and connector or optics seating.

Parameters

Considerations for running DPort

It is not possible to detect if the switch can run D_Port tests before running the tests. Therefore, a test failure occurs if the D_Port command is run with a switch that does not support D_Port.

To terminate tests while they are running, type <CTL> + <C>. In this case no results are given.

If the overall test result is FAILED, you must re-run the tests successfully or reset the HBA port to bring the link back up. A message is displayed instructing you to perform one of these actions if the overall test result is FAILED.

If a test phase fails, the D_Port tests are automatically stopped. In this case, some of the phases may not be reported in the results. However, the failed phase will be reported.

More than one error can be reported. In this case, multiple lines are displayed for the test phase showing each error.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.WWPN The WWPN of the FC function of the adapter on which to run tests.



225

echotest

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> echo <WWN | MAC> <Destination WWPN> <Count> <StopOnError> [Pattern]

Description

This command runs a loopback test on a given FC, FCoE, NIC or iSCSI port.

Parameters

Exampleelxvcpcmd.exe v=10.20.30.40 u=user p=password h=1.2.3.4 echo 10:00:00:c9:12:34:56 10:00:00:c9:ab:cd:ee 100 1 1a2b3c4d5e

getbeacon

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getbeacon <WWPN | MAC>

Description

This command shows the current beacon state, ON or OFF.

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.Destination WWPN WWPN of the destination (echoing) adapter.Count The number of times to run the test (0 = run test infinitely,

Range = 1...99,999).StopOnError Checks if the test must be halted on error.

0 = No halt1 = Halt

Pattern (optional)

One to eight hexadecimal bytes to use for loopback data (for example: 1a2b3c4d).




226

getxcvrdata

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getxcvrdata <WWN | MAC>

Description

This command shows transceiver data such as vendor name and serial number.

Parameters

loadlist

Note: Loadlist is not supported for CNAs.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> loadlist <WWPN>

Description

This command shows the flash parameters for a given FC port.

p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FC or FCoE port.MAC The MAC address of the NIC or iSCSI port.




227

Parameters

loopbacktest

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> loopbacktest <WWPN | MAC> <Type> <Count> <StopOnError> [Pattern]

Description

This command is used to run a loopback test on a given FC, FCoE, NIC or iSCSI port.

Parameters


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.Type The type of loopback test to run:

0 = PCI LoopBack Test1 = Internal LoopBack Test2 = External LoopBack Test (requires loopback plug)3 = Host to DDR DMA (OneConnect adapters) Loopback Test4 = PHY Loopback Test5 = MAC Loopback Test

Note: Loopback tests 0 and 1 are not supported for CNAs. Loopback tests 3, 4, and 5 are only supported for CNAs.

Count The number of times to run the test (0 = run test infinitely, Range = 1...99,999)

StopOnError Checks if the test must be halted on error.

0 = No halt1 = Halt

Pattern (optional)

1 to 8 hexadecimal bytes to use for loopback data (for example: 1a2b3c4d)



228

Example Commandelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password>

h=<esx_host> loopbacktest 00-00-c9-93-2f-9f 4 120 0

posttest

Note: The posttest command does not apply to the LPe16000–series of adapters.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> posttest <WWPN | MAC>

Description

This command runs the POST on a specified FC port.

Parameters

setbeacon

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setbeacon <WWN | MAC> <BeaconState>

Description

This command turns the beacon on or off.

Parameters


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC MAC address of the NIC or iSCSI port.BeaconState New state of the beacon:

0 = Off1 = On



229

setcablenvp

Note: This command supports only OCe11100 T 10GBASE-T–series adapters.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setcablenvp <WWN | MAC> <NPV>

Description

This command sets the nominal velocity of propagation (N-V-P), required for the TDR test, for the cable that connects to the physical port associated with the WWPN or MAC.

Parameters

tdrtest

Note: This command only supports OneConnect adapters that use coax copper cables such as the 10GBASE-T adapter (OCe11102-xT).

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> tdrtest <WWPN | MAC>

Description

The TDR test attempts to determine if any cable faults are compromising the integrity of the link. The test requires that the cable be free of disturbances¡ -–'down' and quiet. It is best if the cable is not terminated; however, if it is terminated then the link partner must not be active during the test.

For each twisted pair cable (labeled A, B, C, or D):

If a fault cannot be detected, the test output displays “OK” and an estimated cable length (in meters), if possible. If the length cannot be determined, the estimated length is displayed as “invalid”.

If one of two faults (a short or an open connection) is detected, the test output shows the fault type (“Shorted” or “Open”) and the distance to the fault (in meters).

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.NVP A percentage value between 1 and 100 (Consult your cable

documentation to obtain the proper NVP value).



230

This command runs a TDR test on a 10GBASE-T adapter.

Parameters

Driver Parameter CommandsThe Driver Parameter commands show, set, and save driver parameter values. You can also change the parameters back to factory default values.

driverconfig

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> driverconfig <WWPN> <FileName> <Flag>

Description

This command sets all driver parameters to the values in the .dpv file on a particular ESXi host. The .dpv file’s driver type must match the driver type of the host platform FC/FCoE adapter.

Parameters

getdriverparams

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getdriverparams <WWPN | MAC>


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.FileName The name of the .dpv file (stored in the Emulex Repository directory)Flag G = Makes change global (all adapters on this host)

N = Makes change non-global (adapter-specific)



231

Description

This command shows the driver parameters of the specified port.

Parameters

getdriverparamsglobal

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getdriverparamsglobal <WWPN | MAC>

Description

This command shows the global driver parameters of the specified port.

Parameters

saveconfig

Note: Driver parameters that are set temporarily and globally (using the G and T flags) must be read using the getdriverparamsel xvcpcmd command to view the current value of the parameter. The getdriverparamsglobal elxvcpcmd command returns only permanently set driver parameter values. Additionally, if temporary, global values have been set for one or more driver parameters, the saveconfig elxvcpcmd command must be run with the N flag (using the N flag is analogous to the elxvcpcmd command getdriverparams) to force the driver parameter values for the specified adapter to be saved. Inaccurate values may be saved if the G flag is used for this command.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> saveconfig <WWN> <FileName> <Flag>

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FC/FCoE port.MAC The MAC address of the NIC or iSCSI port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FC/FCoE port.MAC The MAC address of the NIC or iSCSI port.



232

Description

This command saves the specified FC/FCoE adapter’s driver parameters to a file on an ESXi host. The resulting file contains a list of driver parameter definitions in ASCII file format with definitions delimited by a comma. Each definition is of the form:

<parameter-name>=<parameter-value>.

The command saves either the values of the global set, or those specific to the adapter in the Emulex Repository directory.

Parameters

setdriverparam

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> setdriverparam <WWPN | MAC> <Flag1> <Flag2> <Param> <Value>

Description

This command sets the driver parameter at the port or global level, either permanently or temporarily for the specified port.

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.FileName The name of the local .dpv file.Flag Valid types are:

G = Make change global (all adapters on this host) N = Make change non-global (adapter-specific)

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.Flag1 L = Local (all adapters on this host)

G = Global (all adapters on this host)Flag2 P = Permanent (persists across re-boot)

T = Temporary.



233

setdriverparamdefaults

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> setdriverparamdefaults <WWPN | MAC> <Flag1> <Flag2>

Description

This command restores the driver parameter to the default value at the port or global level, either permanently or temporarily for the specified port.

Parameters

Dump CommandsThe Dump commands initiate a core dump on a local port, show the dump file for the port on the host, shows the diagnostic dump file retention count set on a port, and specify the maximum number of diagnostic dump files for the adapter.

deletedumpfiles

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> deletedumpfiles <WWN | MAC>

Description

This command deletes all diagnostic dump files for a given port.

Parameters

Param The name of the driver parameter.Value The value of the driver parameter.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.Flag1 L = Local (all adapters on this host)

G = Global (all adapters on this host)Flag2 P = Permanent (persists across re-boot)

T = Temporary.

v The vCenter server IP address.



234

dump

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> dump <WWPN | MAC> core [Options]

Description

This command performs a core dump on a local port for an OCe11102 adapter. The dump file is placed in the dump directory with the following filename format:

<Hostname>_<Adapter serial number>_<datetimestamp>.core

If the command is successful, the following message is displayed:

Dump Successful.

Note: Since this command is dumping memory, it can take time while generating large files.

Parameters

getdumpdirectory

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getdumpdirectory <WWN | MAC>

Description

This command shows the dump file directory for the FCoE, NIC or iSCSI port in the host.

u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the CNA port.Options Additional options are available under the direction of Emulex Technical

Support.



235

Note: The dump directory applies to all adapters in the server. There is not a separate dump directory for each adapter.

Parameters

getdumpfilenames

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getdumpfilenames <WWPN | MAC>

Description

This command shows a list of all the dump filenames for a given port.

Parameters

getretentioncount

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getretentioncount <WWN | MAC>

Description

This command shows the diagnostic dump file retention count set on a port.

Note: The retention count applies to all adapters in the server.

Parameters






236

setdumpdirectory

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setdumpdirectory <WWN | MAC> <DumpDirectory>

Description

Use the setdumpdirectory command to set the dump directory for a given FC/FCoE, NIC or iSCSI port. To use the SetDumpDirectory command, you must have a directory mapped under /vmfs/volumes/ where the files will be placed.

Note: The dump directory applies to all adapters in the server. There is no separate dump directory for each adapter.

Parameters

Example Commandelxvcpcmd v=12.345.678.901 u=username p=password h=12.345.678.123 setdumpdirectory 10:00:00:00:c9:61:f2:64 vcenter-datastore

This example shows the dump directory set to /vmfs/volumes/vcenter-datastore.

setretentioncount

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setretentioncount <WWN | MAC> < RetentionCount >

p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.DumpDirectory The directory under /vmfs/volumes that you created to store the

dump files.



237

Description

This command specifies the maximum number of diagnostic dump files for the adapter. When the count reaches the limit, the next dump operation deletes the oldest file.

Note: The retention count applies to all adapters in the server.

Parameters

FCoE CommandsThe FCoE commands show the FCF information of an adapter, show the FIP parameters of the adapter, and shows the LUNs attached to the target of the specified port. The FCoE commands also set the FIP parameters of the adapter in FCoE mode and show the targets attached to the FC and FCoE of the specified port.

getfcfinfo

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password>h=<esx_host> getfcfinfo <WWPN>

Description

This command shows the FCF information of an adapter in FCoE mode.

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC or iSCSI port.RetentionCount The number of dump files to retain.




238

getfipparams

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getfipparams <WWPN>

Description

This command shows the FIP parameters of the CNA in FCoE mode.

Parameters

getlunlist

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getlunlist <WWPN> <TargetWWN>

Description

This command shows the LUNs attached to the FC and FCoE target of the specified FC/FCoE port.

Parameters

setfipparams

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> setfipparams <WWPN> <Param> <Value>

Description

This command sets the FIP parameters of the adapter in FCoE mode.


v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.Target WWPN The WWPN of the iSCSI target.



239

Parameters

Example Commandelxvcpcmd v=12.345.678.901 u=username p=password h=12.345.678.123 setfipparams 10:00:00:00:c9:5b:3a:6d fcmap 0x0efc99

targetmapping

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> targetmapping <WWPN>

Description

This command shows the targets attached to the FC and FCoE of the specified port.

Parameters

Firmware CommandsThe firmwareupdate command updates firmware on the Emulex adapters found in the specified VMware cluster or the ESXi host.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.Param FIP parameter name (pfabric, pswitch, vlanid, fcmap, and cinvlanid).Value FIP parameter value and the valid range for the FIP parameter.

pfabric – 8 byte fabric name (format XX:XX:XX:XX:XX:XX:XX:XX)pswitch – 8 byte switch name (format XX:XX:XX:XX:XX:XX:XX:XX)vlanid – 2 byte VLAN_ID [0-4095] OR 'any' for any valid VLAN_IDfcmap – 3-byte FC_map, 0x0EFCxxcinvlanid – 2-byte VLAN_ID [0-4095]




240

firmwareupdateSee “firmwareupdate” on page 218.

iSCSI CommandsiSCSI commands show initiator login options for a port, show LUNs attached to the target of the port, show statistics for a port, show session information, show available profile IDs, show all sessions for a target, show the configured Internet Storage Name, and shows iSCSI target details of the adapter to which the port belongs. The iSCSI commands also update the configured iSNS server.

clearisnsserver

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> clearisnsserver <MAC>

Description

This command clears the configured ISNS server and disables ISNS target discovery for a given port. If there is no ISNS server currently configured, this command does nothing.

Parameters

getinitiatorproperties

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getinitiatorproperties <MAC>

Description

This command shows all the initiator login options for the specified port. These properties are set as the target portal’s login properties to be used when discovering the targets on the target portal. The discovered targets inherit these properties.

v The IP address of the vCenter server managing the ESXi host.u The user name of the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.



241

Parameters

getiscsiluns

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getiscsiluns <MAC> <Target>

Description

This command shows the LUNs attached to the iSCSI target of the specified iSCSI port.

Parameters

getiscsiportstats

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getiscsiportstats <MAC>

Description

This command shows all the port statistics for a specified port.

Parameters

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.Target The name of the iSCSI target.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.



242

getsessioninfo

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> getsessioninfo <MAC> <Target> <TSIH | <ISID_Qual Target_IP>>

Description

This command lists all session information for a specified session. You must specify the iSCSI target name <Target>. You must also specify the TSIH <TSIH> of the session, or the session's ISID Qualifier <ISID_Qual> and the target's IP address <Target_IP>. These parameters tell the command to gather the information from the specified target and session. You can find the TSIH and ISID qualifier by running the ListSessions command.

Parameters

Note: You must specify either the TSIH value or the ISID qualifier. If ISID qualifier is specified you must also specify the Target’s ID address.

listprofiles

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhost> ListProfiles <WWPN | MAC address>

Description

This command shows a list of the available profile IDs and their descriptions for an adapter. This command also shows currently active and configured profile IDs. The ID descriptions shown with the command are useful when you determine the appropriate profile ID to specify for a ChangePersonality command. Examples of ID descriptions include the following:

ISCSI initiator, no DIF, FCOE initiator + Target, with DIF NIC - ETS Disabled

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.Target The target’s iSCSI name enclosed in quotes (string length:11-255).TSIH The TSIH value of the session (value: 1-65535).ISID_Qual The ISID qualifier of the session (value: 0-65535).Target_IP The Target's IP address.



243

Mixed Storage, 25% ISCSI initiator only, 75% FCOE, no DIF

Parameters

Example

elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 listprofiles 00-00-c9-12-34-56

listsessions

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> listsessions <MAC> <Target>

Description

This command lists all the sessions on a specified target. The iSCSI target name <Target> instructs the command to gather the information from the listed iSCSI target name.

Parameters

showisnsserver

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> showisnsserver < MAC>

Description

This command shows the currently configured Internet Storage Name Server. This command also indicates whether or not ISNS discovery is enabled.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of an FCoE function on the physical port.MAC address The MAC address of any NIC function on the physical adapter port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.Target The iSCSI target name.



244

Parameters

showtarget

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> showtarget <MAC>

Description

This command shows the iSCSI target details of the adapter to which the specified iSCSI port belongs.

Parameters

updateisnsserver

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> updateisnsserver <MAC> <Server IP> <Port>

Description

This command updates the configured ISNS server. This command requires the server IP <Server_IP> and port number <Port> of the ISNS server be available to respond to the ISNS requests.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.



245

Parameters

Personality CommandsPersonality commands shows the personalities of the adapter to which the specified port belongs and change the valid personality of the adapter to which the specified port belongs.

changepersonality

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> changepersonality <WWPN | MAC> <type> [FCoE\iSCSI\NIC]

Description

This command changes the valid personality of the adapter to which the specified port belongs.

Note: The listprofiles command (see page 242) shows the currently active and configured profile IDs. The descriptions of these IDs are useful for determining the appropriate profile ID to specify for the “changepersonality” command.

Note: This command is not supported for the OCe14000–series adapters. Use the setadapterportconfig command for these adapters.

Parameters

Exampleelxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.203.195 changepersonality 00-00-c9-12-34-56 nic 21

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of the iSCSI port.Server_IP The IP address of the ISNS server to configure.Port The port number of the ISNS server to configure (value: 1024-65535).

h The IP address of the ESXi host with Emulex adapter.WWPN The port’s WWPN of any FCoE function on the adapter.MAC The MAC address of the NIC or iSCSI port.[FCoE\iSCSI\NIC] The changed personality that is activated upon a system reboot.pid A profile ID to use for NIC.



246

showpersonalities

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> showpersonalities <WWPN | MAC>

Description

This command shows the personalities of the adapter to which the specified port belongs.

Notes

If the active and/or configured configurations are not single personality, the active and/or configured personality indicators are not shown.

The personalities shown depend upon the availability of the personality, that is controlled by the profiles that are exposed by an adapter's IPL.

This command is not supported for the OCe14000–series adapters. Use the setadapterportconfig command for these adapters.

Parameters

Exampleelxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.000 showpersonalities 00-00-c9-12-34-56

Adapter Personalities:

NIC

iSCSI

FCoE (active) (configured

SR-IOV CommandsSR-IOV commands show a list of all the discovered virtual functions and also enables or disables SR-IOV support for an adapter's physical port.

listvfuncs

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password>




247

h=<esx_host> listvfuncs <MAC>

Description

This command shows a list of all the virtual functions discovered.

Parameters

sriovenable

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> sriovenable <MAC> <0 | 1>

Description

This command enables or disables SR-IOV support for an adapter's physical port.

Parameters

Note: SR-IOV is not supported with UMC channel management.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC MAC address of any NIC function on the physical adapter port

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC Address of any NIC function on the physical

adapter port.SR-IOV Enable state 0 = disable SR-IOV

1 = enable SR-IOV



248

Target and LUN CommandsTarget and LUN commands show the LUNs that support ExpressLane and their status (LPe16000-series and OCe15100-series only), show LUNs attached to the target of the port

getexpresslanelunlist (LPe16000–Series and OCe15100– Series Only)

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> getexpresslanelunlist <WWPN> <Target WWPN> <Option>

Description

This command shows the LUNs that support ExpressLane and their respective ExpressLane status.

Note: Only LUNs that support ExpressLane are shown by this command. LUNS without ExpressLane support are not shown.

Parameters

Exampleelxvcpcmd.exe v=10.192.000.000 u=user p=password h=10.192.87.198 getexpresslanelunlist 10:00:00:00:00:87:01:98 20:22:d4:ae:52:6e:6f:08 0

getiscsilunsSee “getiscsiluns” on page 248

getlunlistSee “getlunlist” on page 238.

listsessionsSee “listsessions” on page 243.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of the FC/FCoE function connected to the target.Target WWPN The WWPN of the FC/FCoE target.Option Valid options:

0: Get information from the driver1: Get information from configuration



249

setexpresslanelunstate (LPe16000–Series and OCe15100– Series Only)

Syntaxsetexpresslanelunstate <WWPN> <Target WWPN> <Lun> <State> <Option>

Description

This command enables and disables ExpressLane on a particular LUN.

Note: A masked LUN cannot be enabled for ExpressLane.

Parameters

Example Commands

The following command enables ExpressLane for LUN 2 on specified target, in the driver and configuration.

elxvcpcmd.exe v=10.192.000.000 u=user p=password h=10.192.87.198 setexpresslanelunstate 10:00:00:00:00:87:01:98 20:22:d4:ae:52:6e:6f:08 2 1 2

The following command enables ExpressLane for LUN 2 on a specified target, in the driver only. After a reboot, a LUN is not an ExpressLane LUN.

elxvcpcmd.exe v=10.192.000.000 u=user p=password h=10.192.87.198 setoaslunstate 10:00:00:00:00:87:01:98 20:22:d4:ae:52:6e:6f:08 2 1 0

The following command disables ExpressLane for LUN 2 on a specified target, in the driver and configuration.


The following command disables ExpressLane for LUN 2 on a specified target, in the driver only. Assuming this is configured to be an ExpressLane LUN, after a reboot LUN 2 is an ExpressLane LUN again.


wwpn The WWPN of the FC/FCoE function connected to the target.Targetwwpn The WWPN of the target.LUN LUN number to enable/disable ExpressLane.State 0 = Disable ExpressLane

1 = Enable ExpressLaneOption Valid ExpressLane options:

0 = Set ExpressLane LUN state in driver (active)1 = Set ExpressLaneLUN state in configuration (persist across reboots)2 = Set ExpressLane LUN state in both (driver and configuration)



250

showtargetSee “showtarget” on page 244.

targetmappingSee “targetmapping” on page 239.

VEPA Commands

VEPAenableVEPA is only supported on OCe14000-series NIC ports. For all other adapter types and port types this feature is undefined, and this command returns the following error message: “Hardware Does Not Support”.

SR-IOV must be enabled on the NIC port for VEPA to be enabled.

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_pwd> h=<esx_host> VEPAenable <MAC Address> <0|1>

Description

This command enables or disables VEPA. takes two parameters:

Parameters

Virtual Machines Commands

listvms

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> listvms <WWPN>

Description

This command lists all virtual machines and their information for all manageable ports.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.MAC The MAC address of any NIC on the relevant physical port.(0/1) Specifies whether to enable or disable VEPA: 0 is disabled and 1 is

enabled.



251

If you specify the host with the “h=<esx_host>” option or just give the physical WWPN, only the virtual machines for that host are shown. If you specify the physical port and the virtual port, only the virtual machine for the specified virtual port returns.

The virtual machine name is only displayed if the virtual port is associated with a virtual machine on VMware ESXi 5.0 and 5.1. If you are running this command on any other server that has virtual ports, you will not see the virtual machine name.

Parameters

listvports

Syntaxelxvcpcmd.exe v=<vcenter_server> u=<vc_username> p=<vc_password> h=<esx_host> listvports <WWNP>

Description

This command lists virtual ports on the specified physical port. Leaving the physical WWPN parameter blank lists all virtual ports on all manageable hosts that support virtual ports.

Parameters

WWWN Management Commands

changewwn

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> changewwn <WWPN> <New WWPN> <New WWNN> <ReadType>

Description

This command changes the WWN of the specified port.





252

Parameters

getwwncapSee “getwwncap” on page 209.

readwwn

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP>

showpersonalities <WWPN | MAC> [ReadType]

Description

This command shows the WWN details of the specified port and category.

Parameters

restorewwn

Syntaxelxvcpcmd.exe v=<vcenter server> u=<vc_username> p=<vc_pwd> <h=ESXhostIP> restorewwn <WWPN> <RestoreType>

Description

This command restores the WWN value of the specified port.

h The IP address of the ESXi host with Emulex adapters.WWPN The port’s WWPN.ReadType 0 = Volatile, 1 = Non-volatile.

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.MAC The MAC address of the NIC port.ReadType Valid types are:

0 = Volatile

1 = Non-volatile

2 = Factory default

3 = Current

4 = Configured


12. Using OneCommand Manager for VMware vCenter Command Line InterfaceViewing Audit Logs Using the CLI Command

253

Parameters

Viewing Audit Logs Using the CLI CommandNote: All active management actions performed are saved to a log file specific to the

action. The maximum size of a log file is 2 MB. If the size of the log file exceeds this limit, old log entries are deleted for the particular event.

Syntaxelxvcpaudit.exe <event name>

Note: If an event name is not specified, all events are displayed.

Description

You can use the elxvcpaudit.exe script to log all the historical active management performed through the vSphere console on the Emulex adapters. To see the usage information, run the script with no parameters specified. All supported events are displayed.

Parameter

List of Supported Event Names

v The vCenter server IP address.u The user name for the vCenter server.p The user password for the vCenter server.h The IP address of the ESXi host with Emulex adapters.WWPN The WWPN of a port on the ESXi host with Emulex adapters.RestoreType Valid types are:

0 = Restore Default WWNs 1 = Restore NVRAM WWNs

event name The command name describing the appropriate active management action performed.

installadapterlicense Licenses installed on the CNA.changepersonality Personality changes on the CNA.loopbacktest Diagnostic tests on the CNA.setdriverparam Driver parameters changes on a LightPulse or OneConnect

adapter, at both port and global levels.setdcbparam DCB parameter changes on the CNA.setbeacon Beacon setting changes on the CNA.setfipparam FIP parameter changes on the CNA.download Firmware download activities.


12. Using OneCommand Manager for VMware vCenter Command Line InterfaceViewing Audit Logs Using the CLI Command

254

ExampleAudit log for : changewwn

--------------------

User Name : Administrator

Date and Time : 2011-06-16T19:25:12Z

Operation : ChangeWWNJobInfo

Host Name : 10.192.203.179

Adapter Id : BT11161224

Port Id : 10:00:00:00:C9:BB:1E:77

Message : Successfully changed WWN

New State

New WWPN = 10:00:00:00:C9:BB:1E:78

New WWNN = 20:00:00:00:C9:BB:1E:78

Volatile = false

Old State

Old WWPN = 10:00:00:00:C9:BB:1E:77

Old WWNN = 20:00:00:00:C9:BB:1E:77

reset Port reset activities.changewwn WWN change activities.


onecommand manager for vmware vcenter version 10 · p011049-01a rev. a connect • monitor •...

Documents