Manual

ManualsBrandsDell ManualsComputer HardwareEmulex Family of Adapters

P010433-01A Rev. A Emulex Connects™ Servers, Storage and People

Documentation for

Emulex

OneConnect™ and

LightPulse

Adapters

Summary of content (1815 pages)

PAGE 1
Documentation for ® OneConnect™ and Emulex ® LightPulse Adapters P010433-01A Rev.
PAGE 2
EMULEX CONFIDENTIAL. Copyright © 2013–2014 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.
PAGE 3
Table of Contents Table of Contents List of Figures .................................................................................... 24 List of Tables ..................................................................................... 47 OneCommand™ Manager Application ............................ 56 Version 10.2 User Manual .......................................... 56 1. Introduction ................................................................................... 58 Compatibility ..............
PAGE 4
Table of Contents 6. Viewing Discovery Information .......................................................... 104 7. Managing Hosts ............................................................................. 105 Viewing Host Grouping Information ............................................................106 Grouping Hosts......................................................................................108 Searching for Hosts in the Discovery-Tree ....................................................
PAGE 5
Table of Contents OneCommand™ Manager Command Line Interface Version 10.2 User Manual .........................................291 1. Introduction ................................................................................. 293 Overview .............................................................................................293 Abbreviations .......................................................................................293 OneCommand Manager Secure Management ..............................
PAGE 6
Table of Contents Dump Commands ...................................................................................365 FCoE Commands ....................................................................................370 iSCSI Commands ....................................................................................372 LUN Masking Commands ..........................................................................394 LUN ExpressLane Commands ...............................................................
PAGE 7
Table of Contents Extracting the Offline Adapter Standalone Management Utility (Linux and Windows PE).........................................................................................464 Offline Adapter Management Utility Installation for FreeBSD.............................465 Firmware and Boot Code .........................................................................466 3. Adapter Management Utility Command Line Interface ............................. 467 Auto-Discovery (/auto) ..............
PAGE 8
Table of Contents World Wide Name Commands....................................................................498 Boot Code Commands .............................................................................500 Configuration Commands .........................................................................503 Viewing Personality Information (personalityInfo) ..........................................504 Changing Personality Information (changePersonality) ....................................
PAGE 9
Table of Contents Emulex Drivers Version 10.2 for Windows Quick Installation Manual .................................................544 1. Introduction ................................................................................. 546 Compatibility ........................................................................................546 Operating System Requirements ................................................................546 2. Driver Installation Options ....................................
PAGE 10
Table of Contents Troubleshooting the iSCSI Driver................................................................690 Appendix A. Error and Event Log Information........................................... 693 FC/FCoE Error and Event Logs ...................................................................693 NIC Error and Event Logs .........................................................................704 iSCSI Error and Event Log.........................................................................
PAGE 11
Table of Contents OneCommand™ NIC Teaming and VLAN Manager Version 2.8 User Manual ..........................................743 1. Overview..................................................................................... 745 Restrictions..........................................................................................746 Supported Operating Systems ...................................................................746 Terminology ................................................................
PAGE 12
Table of Contents Appendix A. Load Balancing Use Cases.................................................... 807 Perceived Port Load ...............................................................................807 Destination MAC ....................................................................................807 Destination IP .......................................................................................808 Appendix B. NIC Teaming Driver Event Log .............................................
PAGE 13
Table of Contents Appendix C. OneConnect 10 GbE Adapter Port Speed Specifications .............. 973 Port Speed Negotiation on Non-Mezzanine Cards ...........................................973 Port Speed on Mezzanine Cards.................................................................973 Appendix D. Updating Ethernet Firmware ............................................... 974 Appendix E. Ethtool -S Option Statistics .................................................. 975 Appendix F.
PAGE 14
Table of Contents iSCSI Driver Configuration ...................................................................... 1028 4. Troubleshooting ........................................................................... 1035 Troubleshooting the FC/FCoE Driver ......................................................... 1035 Troubleshooting the NIC Driver ............................................................... 1132 Troubleshooting the iSCSI Driver...........................................................
PAGE 15
Table of Contents OneCommand Manager™ for VMware vCenter Version 10.2 User Manual ................................................. 1158 1. Introduction ................................................................................ 1160 Abbreviations ..................................................................................... 1164 2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components ...................................................................................
PAGE 16
Table of Contents Updating Firmware on Adapters in a Host .................................................. 1297 Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters ........................................ 1304 8. Exporting SAN Information in Cluster View .......................................... 1306 9. Diagnostics.................................................................................. 1309 LightPulse FC HBA Diagnostic Tests ...................................
PAGE 17
Table of Contents Boot Version 10.2 for the Fibre Channel Protocol User Manual ........................................................ 1398 1. Introduction ................................................................................ 1400 Abbreviations ..................................................................................... 1400 Emulex Boot Code Files ......................................................................... 1403 2. Boot from SAN ...........................................
PAGE 18
Table of Contents Add Boot Devices ................................................................................. 1476 Delete Boot Devices ............................................................................. 1478 Change Boot Device Order ..................................................................... 1480 Configure Adapter Parameters ................................................................ 1482 Configure Boot Parameters..............................................................
PAGE 19
Table of Contents Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual ........................................... 1509 1. Introduction ................................................................................ 1511 Overview ........................................................................................... 1511 Abbreviations ..................................................................................... 1512 2.
PAGE 20
Table of Contents 6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures................ 1578 Navigating the FCoE BIOS Utility .............................................................. 1578 Starting the FCoE BIOS Utility ................................................................. 1578 Enabling an Adapter to Boot from SAN....................................................... 1579 Scanning for Target Devices ...................................................................
PAGE 21
Table of Contents Erasing Ports and Controller Configuration ................................................. 1660 12. Configuring UEFI for iSCSI.............................................................. 1663 Overview ........................................................................................... 1663 Navigating the Emulex iSCSI Configuration Utility......................................... 1663 Starting the Emulex iSCSI Configuration Utility ............................................
PAGE 22
Table of Contents Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot..................................................... 1721 Linux and Citrix PXE Server Remote Installation Procedure ............................ 1721 Appendix C. Examples for Configuring and Booting UEFI NIC ....................... 1729 UEFI NIC Server Configuration Script for SLES11 SPx ..................................... 1729 UEFI NIC Server Configuration Script for RHEL 6.x.................
PAGE 23
Table of Contents Adapter Installation Manual .................................... 1805 1. Introduction ................................................................................ 1807 Adapter Identification........................................................................... 1807 2. Installation.................................................................................. 1809 Preparing the Adapter for Installation .......................................................
PAGE 24
List of Figures List of Figures OneCommand™ Manager Application Version 10.2 User Manual Figure 2-1 Figure 2-2 Management Mode Dialog Box.................................................. 62 OneCommand Manager application Web Launch Uninstallation Screen.............................................................................. 73 Figure 4-1 OneCommand Manager Application Window ................................. 78 Figure 4-2 Toolbar .....................................................................
PAGE 25
List of Figures Figure 8-7 Figure 8-8 Figure 8-9 Figure 8-10 Figure 8-11 Figure 8-12 Figure 8-13 Figure 8-14 Figure 8-15 Figure 8-16 Figure 8-17 Figure 8-18 Figure 8-19 Figure 8-20 Figure 8-21 Figure 8-22 Figure 8-23 Figure 8-24 Figure 8-25 Figure 8-26 Figure 8-27 Figure 8-28 Figure 8-29 Figure 8-30 Figure 8-31 Figure 8-32 Figure 8-33 Figure 8-34 Figure 8-35 Figure 8-36 Figure 8-37 Figure 8-38 Figure 8-39 Figure 8-40 FC Transceiver Data Tab .......................................................
PAGE 26
List of Figures Figure 8-41 iSCSI PCI Registers Tab ......................................................... 173 Figure 8-42 DCB Tab for iSCSI Adapter Ports (OneConnect Adapter Selected)....... 174 Figure 8-43 Configure DCB Dialog Box for iSCSI Adapter Ports (DCBX enabled) .......................................................................... 176 Figure 8-44 iSCSI Initiator Login Options Tab.............................................. 179 Figure 8-45 Initiator Default Login Options Window ..........
PAGE 27
List of Figures Figure 8-72 Figure 8-73 Figure 8-74 Figure 8-75 Figure 8-76 Figure 8-77 Figure 8-78 Single Personality View (FCoE selected)..................................... 217 Custom View ..................................................................... 219 Mixed Mode Protocol pull-down menu ....................................... 220 Concurrent Storage Configuration View ..................................... 221 Concurrent Storage Configuration Choices for the Third Function ......
PAGE 28
List of Figures Figure 13-2 Overlay Detail Window ......................................................... 266 Figure 13-3 Quick Test Warning ............................................................. 266 Figure 13-4 Diagnostics Tab for LPe16000 series adapters (D Port Tests... button depicted) ................................................................ 268 Figure 13-5 D_Port Tests window ........................................................... 269 Figure 13-6 Diagnostic Dump Dialog Box .......
PAGE 29
List of Figures Emulex® Drivers Version 10.2 for Windows User Manual Figure 2-1 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure Figure Figure Figure AutoPilot Installer Warning (Software-First Installation) ................. 569 Partial View of Windows Device Manager ................................... 608 NIC Advanced Properties in Windows Server 2008 .............
PAGE 30
List of Figures OneCommand™ NIC Teaming and VLAN Manager Version 2.8 User Manual Figure 3-1 OneCommand NIC Teaming and VLAN Manager Element Definitions........................................................................ 754 Figure 3-2 The Discovery-Tree ............................................................. 756 Figure 3-3 General Tab Information for a Host Computer ............................. 757 Figure 3-4 General tab Information for an Emulex Adapter ...........................
PAGE 31
List of Figures OneCommand Manager™ for VMware vCenter Version 10.2 User Manual Figure 2-1 Figure 2-2 Figure 2-3 1169 1170 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 2-9 Figure 3-1 Installation Options Window................................................. OCM for VMware vCenter Configuration Window......................... OCM for VMware vCenter Configuration Window with Port in Use Warning....................................................................
PAGE 32
List of Figures Figure 6-10 Figure 6-11 Figure 6-12 Figure 6-13 Figure 6-14 Figure 6-15 Figure 6-16 Figure 6-17 Figure 6-18 FC/FCoE LUN Information Tab .............................................. Enable ExpressLane LUN Pull Down Menu ................................. FC/FCoE LUN with ExpressLane Enabled .................................. FC Port PCI Registers Tab .................................................... FC Port Flash Contents .......................................................
PAGE 33
List of Figures Figure 6-43 Figure 6-44 Figure 6-45 Figure 6-46 Figure 6-47 Figure 6-48 Figure 6-49 Figure 6-50 Figure 6-51 Figure 6-52 Figure 6-53 Figure 6-54 Figure 7-1 Figure 7-2 OneConnect OCe11102 Adapter Information Tab ........................ Install Feature Licenses Dialog Box......................................... Channel Mgmt tab for the OCe11102 adapter ............................ Channel Management Tab in vNIC1 Mode ................................. Channel Management Tab in UFP Mode.....
PAGE 34
List of Figures Figure 7-4 Figure 7-5 Figure 7-6 Figure 7-7 Figure 7-8 Figure 7-9 Figure 7-10 Figure 7-11 Figure 8-1 Figure 8-2 Figure 8-3 Figure 9-1 Figure 9-2 Figure 9-3 Figure 9-4 Figure 9-5 Figure 9-6 Figure 9-7 Figure 9-8 Figure 9-9 Figure 9-10 Figure 9-11 Figure 9-12 Figure 9-13 Figure 9-14 Figure 9-15 Figure 9-16 Figure 10-1 Figure 10-2 Figure 10-3 Batch Firmware Update Jobs Window ..................................... Empty Batch Firmware Download Dialog Box .............................
PAGE 35
List of Figures Figure 12-4 Certificate Dialog Box ........................................................ 1395 Figure 12-5 Certificate Import Wizard ................................................... 1395 Boot Version 10.
PAGE 36
List of Figures Figure 6-8 Figure 6-9 Figure 6-10 Figure 6-11 Figure 6-12 Figure 6-13 Figure 6-14 Figure 6-15 Figure 6-16 Figure 6-17 Figure 6-18 Figure 6-19 Figure 6-20 Figure 6-21 Figure 6-22 Figure 6-23 Figure 6-24 Figure 6-25 Figure 6-26 Figure 6-27 Figure 6-28 Figure 6-29 Figure 6-30 Figure 6-31 Figure 6-32 Figure 6-33 Figure 6-34 Figure 6-35 Figure 6-36 Figure 6-37 BIOS Enabled Screen .......................................................... Adapter Configuration Menu...............................
PAGE 37
List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 6-43 6-44 6-45 6-46 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22 7-23 7-24 8-1 8-2 Figure 8-3 Figure 8-4 Figure 8-5 Figure 8-6 Figure 8-7 Batch Mode Update path Screen............................................
PAGE 38
List of Figures Figure 8-8 Figure 8-9 Figure 8-10 Figure 8-11 Figure Figure Figure Figure Figure Figure 8-12 8-13 8-14 8-15 8-16 8-17 Internal Loopback Test Progress Screen ................................... Internal Loopback Test Data Pattern Results Screen .................... Running Adapter Diagnostic Tests In Progress Screen ................... Select Diagnostic Tests – Adapter Diagnostic Tests Passed Screen...........................................................................
PAGE 39
List of Figures Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 2-9 Figure 2-10 Figure 2-11 Figure 2-12 Figure 2-13 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 PXE Boot Process ..............................................................
PAGE 40
List of Figures Figure 3-18 Figure 6-1 Figure 6-2 Figure 6-3 Figure 6-4 Figure 6-5 Figure 6-6 Figure 6-7 Figure 6-8 Figure 6-9 Figure 6-10 Figure 6-11 Figure 6-12 Figure 6-13 Figure 6-14 Figure 6-15 Figure 6-16 Figure 6-17 Figure 6-18 Figure 6-19 Figure 6-20 Figure 6-21 Figure 6-22 Figure 8-1 Figure 8-2 Figure 8-3 Figure 8-4 Figure 8-5 Figure 9-1 Figure 9-2 IBM Virtual Fabric Mode MultiChannel Configuration Screen ........... Emulex Adapter Listing.......................................................
PAGE 41
List of Figures Figure 9-7 Controller Properties Screen with MPIO Port Pop-up Menu............. Figure 9-8 Network Configuration Screen .............................................. Figure 9-9 Network Configuration Screen with IP Version Pop-up Menu........... Figure 9-10 Configure VLAN ID/Priority Screen ......................................... Figure 9-11 Configure IPv4 Address Screen .............................................. Figure 9-12 DHCP IP Address Dialog Box .................................
PAGE 42
List of Figures Figure 11-12Configure SRIOV Screen ...................................................... Figure 11-13Configure NIC Mode Pop-up Menu .......................................... Figure 11-14Controller Configuration Screen ............................................ Figure 11-15Multichannel Configuration for Function 0 Screen ....................... Figure 11-16Configure Bandwidth Screen ................................................ Figure 11-17Configure LPVID Screen ......................
PAGE 43
List of Figures Figure 12-15Add/Ping iSCSI Target Screen ............................................... Figure 12-16Boot Target Option on the Edit/Ping Target Screen..................... Figure 12-17Authentication Method Option on the Edit/Ping Target Screen ....... Figure 12-18Edit/Ping Target Screen...................................................... Figure 12-19Successful Target Ping ....................................................... Figure 12-20Advanced iSCSI Target Information Screen..........
PAGE 44
List of Figures Figure Figure Figure Figure B-1 B-2 B-3 B-4 Figure B-5 Figure B-6 Figure C-1 Figure C-2 Figure C-3 Figure C-4 Network Installation and Diskless Environment Window ................ Configure Network Installations Window .................................. Network Installation Dialog Window ....................................... Network Installation and Diskless Environment Window with IP Address ......................................................................... Edit Dialog Box ....
PAGE 45
List of Figures Figure C-29 Figure C-30 Figure C-31 Figure C-32 Figure D-1 Figure D-2 Figure E-1 Figure F-1 Figure F-2 Figure F-3 Figure F-4 Figure F-5 Figure F-6 Figure F-7 Figure F-8 Figure F-9 Figure F-10 Figure F-11 Figure F-12 Figure F-13 Figure F-14 Figure F-15 Figure F-16 Figure G-1 Figure G-2 Figure G-3 Figure G-4 Figure G-5 Figure H-1 Figure H-2 Network Device List .......................................................... Automatic Configuration via DHCP Dialog Box............................
PAGE 46
List of Figures Figure H-8 Figure H-9 Boot Configuration Screen ................................................... 1797 Port Configuration Screen ................................................... 1799 Adapter Installation Manual Figure 1-1 Figure 1-2 Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Two Port Adapter ............................................................. Single Port Adapter ...........................................................
PAGE 47
List of Tables List of Tables OneCommand™ Manager Application Version 10.2 User Manual Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 14-1 Table 14-2 Secure Management User Privileges........................................... 84 Active Commands: machines on same domain .............................. 84 Active Commands: machines on different domain.......................... 84 Passive Commands: machines on any domain ............................... 85 General Situations ....................................
PAGE 48
List of Tables Offline and Online Adapter Management Utilities Version 10.2 User Manual Table 4-1 Table 5-1 Table 6-1 Supported Commands for the Offline Adapter Management Utility ............................................................................. 488 Elxflash Status Messages ....................................................... 514 LPCfg Error Codes ............................................................... 516 OneCapture™ Version 10.
PAGE 49
List of Tables Emulex® Drivers Version 10.2 for Windows User Manual Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 3-8 Table 3-9 Table 3-10 Table 3-11 Table 3-12 Table 3-13 Table 3-14 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table A-1 Table A-2 Table A-3 Table A-4 Table A-5 Table A-6 Table A-7 Table A-8 Table A-9 Table A-10 Table A-11 Table A-12 Storport Miniport Driver Parameters .........................................
PAGE 50
List of Tables Table A-13 NIC Event Log Entries........................................................... 705 Table A-14 iSCSI Error Log Entries on Windows Server 2008 ........................... 710 Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 ....................................................... 713 Table B-1 Data String Parameters for Option 43........................................
PAGE 51
List of Tables Emulex® Drivers Version 10.2 for Linux User Manual Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table A-1 Table A-2 Table A-3 Table B-1 Table C-1 Table E-1 Table E-2 Table F-1 Table F-2 Table F-3 Table F-4 Static FC and FCoE Driver Parameters ....................................... 823 Dynamic FC and FCoE Driver Parameters.................................... 826 Ethernet Driver Configuration Parameters ....
PAGE 52
List of Tables Emulex® Drivers Version 10.2 for VMware ESXi User Manual Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 3-8 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table 4-7 Table 4-8 Table 4-9 Table 4-10 Table 4-11 FC and FCoE Driver Parameters............................................. ESXi 5.5 Ethernet Driver Parameters....................................... User-configurable NIC Driver Parameters .................................
PAGE 53
List of Tables OneCommand Manager™ for VMware vCenter Version 10.2 User Manual Table 1-1 Table 10-1 Table 11-1 Table 12-1 Support Provided by Emulex CIM Provider Versions ..................... Troubleshooting Issues and Resolutions ................................... Group and Supported Commands ........................................... Troubleshooting Issues and Resolutions ................................... 1161 1328 1332 1396 Boot Version 10.
PAGE 54
List of Tables Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual Table 2-1 Table 2-2 Table 3-1 Advanced Mode Capabilities (by Operating System)..................... 1524 PXE Boot Parameter Default Values ........................................ 1533 PXE Boot Parameter Default Values ........................................ 1556 Table 6-1 Valid AL_PA Values.....................................................................
PAGE 55
List of Tables Adapter Installation Manual Table 2-1 FC Adapter LED Activity ..................................................... 1815 Documentation for Emulex OneConnect and LightPulse Adapters P010433-01A Rev.
PAGE 56
OneCommand™ Manager Application Version 10.2 User Manual P010066-01A Rev.
PAGE 57
Copyright © 2003-2014 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.
PAGE 58
1. Introduction Compatibility 1. Introduction The Emulex® OneCommandTM Manager application is a comprehensive management utility for Emulex host bus adapters (HBAs), universal converged network adapters (UCNAs), and converged fabric adapters (CFAs) that provides a powerful, centralized adapter management suite. Adapter management includes discovery, reporting and management of local and remote adapters from a single console anywhere in the Storage Area Network (SAN) and across operating system platforms.
PAGE 59
1.
PAGE 60
1.
PAGE 61
1. Introduction Abbreviations VF virtual function VM virtual machine vNIC virtual network interface card VPD vital product data VPort virtual port WWN world wide name WWNN world wide node name WWPN world wide port name VM virtual machine XML Extensible Markup Language OneCommand™ Manager Application P010066-01A Rev.
PAGE 62
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application 2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application Note: If the OneCommand Vision application was previously installed on the system, you will be prompted to remove it before installing the OneCommand Manager application.
PAGE 63
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application modes. See “Using OneCommand Manager Secure Management” on page 83 or “Changing Management and Read-Only Mode” on page 85 for more information. Choose the management type you want and click OK. 6. Check or uncheck the Enable TCP/IP Management checkbox to enable or disable remote management over TCP/IP. You can also change the TCP/IP port used (23333 is the IANA registered port for Emulex).
PAGE 64
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application The following are the possible achange values: 0 – Do not allow Management Mode to change 1 – Allow Management Mode to change You can also set the following optional parameters:    MHost – This optional switch allows a non-management-host user to select a Management Host with which to register.
PAGE 65
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application /usr/lib64. The i386 build requires the 32-bit version, which is installed in /usr/lib.  Previous versions of the Linux driver must be uninstalled. You must run the uninstall script that shipped with the version of the Linux driver you want to remove. Attended Installation in Linux To install the OneCommand Manager application, or upgrade an existing installation, in Linux: 1.
PAGE 66
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application 9. When prompted, enter the type of management you want to use: Enter the type of management you want to use: 1 Local Mode : HBA's on this Platform can be managed by OneCommand clients on this Platform Only. 2 Managed Mode: HBA's on this Platform can be managed by local or remote OneCommand clients.
PAGE 67
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application “OneCommand Manager Secure Management Configuration Requirements” on page 85 for configuration instructions. To view the options for unattended installation, type ./install -h or ./install --help Upgrading an Installation in Linux The OneCommand Manager application supports the following upgrade paths:   You can upgrade from an earlier Core Kit to a later Enterprise Kit.
PAGE 68
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application 5. When prompted, choose whether or not to enable Secure Management for OneCommand: Do you want to enable Secure Management feature for OneCommand? (s/u) Enter 's' to select secure management. (LDAP/NIS OCM group configuration required) Enter 'u' to run without secure management (default). Enter the letter 's' or 'u'. If you enter ‘s’, proceed to step 7.
PAGE 69
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application yes to allow users to perform these operations, enter for no if read-only mode is desired. 8. You are prompted whether to allow users to change the management mode after installation. Enter for yes, or for no.
PAGE 70
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application Web Launch Interface Installing the OneCommand Manager Application Web Launch Interface Note: The OneCommand Manager application Web Launch Interface is not supported on VMware ESXi Server. Note: OneCommand Manager Secure Management mode is not supported for OneCommand Manager application Web Launch clients.
PAGE 71
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application Web Launch Interface To add the MIME type: 1. 2. 3. 4. 5. 6. 7. Launch Server Manager. Expand Roles. Under Roles, expand Web Server (IIS). Under Web Server (IIS), Click Internet Information Services (IIS) Manager. In the right pane, find your server name under “Start Page” and click on it. Double-click MIME Types listed under IIS group. A MIME Types page appears.
PAGE 72
2. Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application Web Launch Interface Note: Citrix XenServer does not support the Web Launch Interface. 1. Log on as ‘root’. 2. Navigate to the OneCommand Manager directory.  Solaris: cd /opt/ELXocm  Linux: cd /usr/sbin/ocmanager 3. Run the install script. Type: ./wsinstall 4. When prompted, enter the web server's document root directory.
PAGE 73
2. Installing and Uninstalling OneCommand Manager Application Components Uninstalling the OneCommand Manager Application Uninstalling the OneCommand Manager Application To uninstall the OneCommand Manager application and OneCommand Manager application Web Launch Interface:  In Windows  1. Select Start>Control Panel>Programs>Uninstall a Program. 2. If present, select Emulex Common SAN Management [version] and click Remove or Uninstall. Click Yes.
PAGE 74
2. Installing and Uninstalling OneCommand Manager Application Components Uninstalling the OneCommand Manager Application Web Launch Interface Only  2. The OneCommand Manager application Web Launch Interface is removed. Press any key to continue. In Linux and Solaris 1. Log on as ‘root’. 2. Execute the uninstallation script.
PAGE 75
3. Starting and Stopping the OneCommand Manager Application In Windows 3. Starting and Stopping the OneCommand Manager Application In Windows To start the OneCommand Manager application, from the Windows desktop, select Start>All Programs>Emulex>OCManager. If Secure Management is enabled, you are prompted for your user name and password. See “Using OneCommand Manager Secure Management” on page 83 for more information.
PAGE 76
3. Starting and Stopping the OneCommand Manager Application Starting the OneCommand Manager Application Web Launch Interface may be using the same port number causing a conflict between the MILI and the other application. In this case, you can change the TCP/IP port number to run both OCM and the other application on the same host. The MILI TCP/IP port is changed by creating a file called "mili.conf".
PAGE 77
3. Starting and Stopping the OneCommand Manager Application Starting the OneCommand Manager Application Web Launch Interface Managing Files when Running the OneCommand Manager Application Web Launch Interface When running the OneCommand Manager application Web Launch Interface, all OneCommand Manager application files, such as log files, configuration files, and driver parameter files are located on the Web Launch server.
PAGE 78
4. Using the OneCommand Manager Application The OneCommand Manager Application Window Element Definitions 4. Using the OneCommand Manager Application Note: To properly view the OneCommand Manager application, ensure your system meets the following display requirements:   For Windows, Linux and Solaris systems, the display resolution must be set to 1024 x 768 or higher. For Windows systems, use the default font size. The display must run in 256-color mode or higher.
PAGE 79
4. Using the OneCommand Manager Application The OneCommand Manager Application Window Element Definitions     The element you select in the discovery-tree determines whether a menu item or toolbar icon is active. For example, if you select the local host or other system host, the Reset Adapter item on the Adapter menu is unavailable. The Reset Adapter toolbar button is unavailable as well. Screenshots in this manual are for illustrative purposes only. Your system information can vary.
PAGE 80
4. Using the OneCommand Manager Application The OneCommand Manager Application Window Element Definitions Note: You cannot change host names using the OneCommand Manager application; names must be changed locally on that system. • • • • • • Displays the installed adapters within each host system. Displays adapter ports and the port numbers if available. Displays adapters by the WWNN if multiple adapters have the same model number. Displays the WWPN if targets are present.
PAGE 81
4. Using the OneCommand Manager Application The OneCommand Manager Application Window Element Definitions Discovery-Tree The discovery-tree (left pane) has icons that represent discovered hosts, adapters, ports, virtual ports, fabrics, targets and LUNs. Using the View menu, the OneCommand Manager application allows you to control the way iSCSI initiator and target ports are identified in the discovery-tree. The “iSCSI Names” option displays all iSCSI ports by their iSCSI Qualified Name (IQN).
PAGE 82
4. Using the OneCommand Manager Application The OneCommand Manager Application Window Element Definitions The iSCSI icon represents an iSCSI PCI function instance. iSCSI functions can support up to sixteen logical adapters, with each logical adapter appearing in the discovery-tree as a separate child node under the respective iSCSI function. A green iSCSI icon represents an iSCSI PCI function on-line instance. A black iSCSI icon represents an iSCSI PCI function port-disabled instance.
PAGE 83
4. Using the OneCommand Manager Application Using OneCommand Manager Secure Management Expanding or Collapsing the Discovery-Tree View You can use the Expand/Collapse capability on the View menu to change the way discovered elements are displayed. By selecting one of the four levels, the discovery-tree is expanded or collapsed to that level. You can choose Hosts/Fabrics (depending on the view), adapters, ports, PCI functions, and targets.
PAGE 84
4. Using the OneCommand Manager Application Using OneCommand Manager Secure Management for each user. The following table defines the OneCommand Manager application user groups and each group's management capabilities. Table 4-1 Secure Management User Privileges OneCommand Manager Capability Group Name ocmadmin Allows full active management of local and remote adapters. ocmlocaladmin Permits full active management of local adapters only. ocmuser Permits read-only access of local and remote adapters.
PAGE 85
4. Using the OneCommand Manager Application Changing Management and Read-Only Mode Table 4-4 Passive Commands: machines on any domain Remote Server (Secure) Remote Server (Not Secure) Client (Secure) Allowed Allowed Client (Not Secure) Allowed Allowed * To inform you of an unsecured server that you may want to secure. ** Allowed if the username and password are the same on both domains.
PAGE 86
4. Using the OneCommand Manager Application Changing Management and Read-Only Mode    Full Management – This setting enables you to manage adapters on this host and other hosts that allow it. Management Host – This setting allows this host to manage other hosts, but prevents it from being managed by other hosts. Enable TCP/IP Management (of/from remote host) – This setting enables you to manage remote hosts or to manage this host remotely.
PAGE 87
4. Using the OneCommand Manager Application Changing Management and Read-Only Mode Note: After making changes, you must restart the OneCommand Manager application to see the new management mode settings.  In Windows 1. From the File menu, select Management Mode. The Management Mode dialog box appears. Figure 4-4 Management Mode Dialog Box  2. Choose the management type and read-only mode you want. 3. Click OK. In Solaris 1. Run the following script: /opt/ELXocm/set_operating_mode  2.
PAGE 88
5. Configuring Discovery Discovery Using the TCP/IP Access Protocol 5. Configuring Discovery Discovery Using the TCP/IP Access Protocol You can discover adapters on IPv4 and IPv6 TCP/IP hosts and on hosts configured to support the CIM interface that have the OneCommand Manager application installed. Remote SAN management over TCP/IP sends remote management requests using TCP/IP access protocol to remote hosts.
PAGE 89
5. Configuring Discovery Discovery Using the TCP/IP Access Protocol      You can manage many more hosts since TCP/IP access is not constrained by the boundaries of a fabric or zoning. True board status (such as link down) is available since the FC path is not necessary to send a status request to the remote host. Adapter security in a TCP/IP environment is much more important since many more hosts are available for management, and TCP/IP access is not affected by fabrics or zoning.
PAGE 90
5. Configuring Discovery Discovery Using the TCP/IP Access Protocol 2. Edit the file. Guidelines for editing the file are as follows:  Each line of the file starts with an IPv4 or IPv6 address. Following the IP address can be any number of tabs or spaces. This is followed by a “#” character, zero or more tabs or spaces and the name of the host for that IP address. The host name is not required for discovery.
PAGE 91
5. Configuring Discovery Discovery Using the TCP/IP Access Protocol To add a single host: 1. From the Discovery menu, select TCP/IP>Add Host. The Add Remote TCP/IP Host dialog box appears. Figure 5-2 Add Remote TCP/IP Host Dialog Box 2. Enter the name or the IPv4 or IPv6 address of the host to be added. Note: Entering the IP address to identify the host avoids possible name resolution issues.
PAGE 92
5. Configuring Discovery Discovery Using the TCP/IP Access Protocol Adding a Range of Hosts (IPv4 Only) You can find the TCP/IP-accessed manageable hosts by searching a range of IPv4 addresses. The Add Range of TCP/IP Hosts dialog box enables you to build the initial list of TCP/IP accessed manageable hosts. (Not available in strictly local or local plus management modes.
PAGE 93
5. Configuring Discovery Configuring Discovery and CIM Credentials 2. Enter the complete start and end address range (IPv4 only) and click Add. The added address range appears in the dialog box. Add any additional ranges you want to search. 3. Click Start Discovery. If an address is remotely manageable, it is added to the list of addresses that the discovery server attempts to discover.
PAGE 94
5. Configuring Discovery Configuring Discovery and CIM Credentials adapters of all these hosts are displayed by the OneCommand Manager application as a single host entry. Figure 5-5 Discovery Settings Dialog Box To configure discovery settings: 1. From the Discovery menu, select Modify Settings. The Discovery Settings dialog box appears. 2. Define the discovery properties you want. 3.
PAGE 95
5. Configuring Discovery Configuring iSCSI Target Discovery Output similar to the following will be returned. emulex-cim-provider 10.0.514.6-01 Emulex VMwareAccepted 2013-06-10 4. Choose the refresh rate settings you want to apply. 5. Click OK to apply your changes. Click Defaults to return the discovery properties to their default settings. Configuring iSCSI Target Discovery The iSCSI Target Discovery tab allows you to configure iSCSI target discovery related parameters.
PAGE 96
5. Configuring Discovery Configuring iSCSI Target Discovery    The target was manually added. The target was discovered via a target portal. The target was found through an iSNS server query. Target Discovery Buttons        Add Portal – Click to add a target portal. See “Adding Target Portals” on page 96 for more information. Remove Portal – Click to remove a portal. See “Removing a Target Portal” on page 96 for more information. Target Login – Click to log into a selected target.
PAGE 97
5. Configuring Discovery Configuring iSCSI Target Discovery Configuring iSNS for iSCSI Target Discovery An iSNS maintains a database of storage network elements that can be queried for iSCSI targets by other hosts within the SAN. iSCSI storage devices in particular can register targets with the iSNS for efficient discovery by iSCSI clients such as the OneCommand Manager application. Use the iSCSI iSNS tab to configure the iSNS server or to discover the server using DHCP.
PAGE 98
5. Configuring Discovery Configuring iSCSI Target Discovery 3. Click OK. The server is pinged and the new server appears in the iSNS Server list. Note: If the server cannot be pinged, a popup message appears indicating this and you must choose whether or not to add the address. The new iSNS server is also queried for iSCSI targets and any discovered targets are added to the Target's table on the main Target Discovery tab. To remove a server: 1.
PAGE 99
5. Configuring Discovery Configuring iSCSI Target Discovery the Initiator Login Options tab does not change the discovered targets login options. Figure 5-9 Target Login Dialog Box To log into a target: 1. From the iSCSI Target Discovery tab, select the target from the Targets table. 2. Click Target Login. The Target Login dialog box appears. The dialog box displays the Target Name and Target Alias of the target.
PAGE 100
5. Configuring Discovery Configuring iSCSI Target Discovery Manually Adding an iSCSI Target The iSCSI Target Discovery tab enables you to manually add and log into iSCSI targets. To manually add an iSCSI target: 1. From the iSCSI Target Discovery tab, click Manually Add Target. The Add iSCSI Target dialog box appears. 2. Enter the target iSCSI name, target IP address and TCP port number. 3. Specify the Target Login Options and Authentication type you want to use. 4.
PAGE 101
5. Configuring Discovery Configuring iSCSI Target Discovery Logging out of Target Sessions The Target Sessions dialog box enables you to log out of active sessions for a currently connected target. To log out of active sessions for a connected target: 1. From the iSCSI Target Discovery tab, select the target whose sessions you want to log out of and click Target Sessions. The Target Sessions dialog box appears. 2. From the Session pull-down menu, select the session from which you want to log out. 3.
PAGE 102
5. Configuring Discovery Configuring iSCSI Target Discovery   TSIH – The target session identifier handle. A tag generated by an iSCSI target to identify an iSCSI session with a specific iSCSI initiator. (Not available when running the open-iSCSI driver.) iSCSI Boot – When checked, the target is enabled for boot. However, it does not necessarily mean that the target is the current boot device. Check this box to enable boot from this target. Uncheck it to disable boot from this target.
PAGE 103
5. Configuring Discovery Configuring iSCSI Target Discovery      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 that were received on the session and contained header or data digest errors. Connection Timeouts – The count of connections within this session that have been terminated due to a timeout.
PAGE 104
6. Viewing Discovery Information Configuring iSCSI Target Discovery 6. Viewing Discovery Information The Discovery Information page contains a general summary of the discovered elements. The Host, Fabric or Virtual Port icon, depending upon which view you select, is the root of the discovery-tree, but it does not represent a specific network element. Expanding it reveals all hosts, LUNs, targets, adapter ports, and virtual ports that are visible on the SAN. To view discovery information: 1.
PAGE 105
7. Managing Hosts Configuring iSCSI Target Discovery 7. Managing Hosts There are two tabs that show host information: the Host Information tab and the Host Driver Parameters tab. The Host Information tab is read-only. The Host Driver Parameters tab enables you to view and define adapter driver settings for a specific host. See “The Host Driver Parameters Tab” on page 150 for more information about the Host Driver Parameters tab. To view the Host Information and Host Driver Parameters tabs: 1.
PAGE 106
7. Managing Hosts Viewing Host Grouping Information     host's IP address, for example, 138.239.82.131. "Local Host" is displayed if you selected the host from which you are actually launching. Remote Manager Server Version – The version of the OneCommand Manager application server that is running on the host. If different versions of the OneCommand Manager application are installed on different hosts in the SAN, those differences appear in this field.
PAGE 107
7. Managing Hosts Viewing Host Grouping Information To view host grouping information, from the discovery-tree, select the host group whose information you want to view. Figure 7-2 Host Group Information Tab Host Group Information Field Definitions     Group Name – The name of the selected group. Number Hosts – The total number of hosts assigned to the group. Number of Adapters – The total number of discovered adapters in the group. Number of Physical Ports – The total number of ports in the group.
PAGE 108
7. Managing Hosts Grouping Hosts Grouping Hosts The OneCommand Manager application enables you to assign related hosts to host groups. Typically, hosts within the same host group share some common function, or they may simply reside within the same organizational unit within an enterprise such as a “Payroll” group or a “Shipping/Receiving” group. You can display the hosts in the discovery-tree in either a group centric format or in the host-based flat format.
PAGE 109
7. Managing Hosts Grouping Hosts Managing Host Groups Use the Host Group Management dialog box to create and delete host groups, add and remove hosts, and restore host groups. Note: Managing host groups is not supported on VMware. Figure 7-3 Host Group Management Dialog Box Host Group Management Field Definitions     Available Hosts – The list of hosts that can be added to a host group. You can select a host and right-click to see its group assignments.
PAGE 110
7. Managing Hosts Grouping Hosts    Restore All Groups – Returns all groups to their original state. OK – Saves the current configuration changes and closes the dialog box. Cancel – Discards changes and closes the dialog box. Host Group Management Icons  Indicates the host is currently assigned to a single host group.  Indicates the host is currently assigned to multiple host groups. Creating a Host Group To create a new host group: 1. From the View menu, select Manage Groups.
PAGE 111
7. Managing Hosts Grouping Hosts Adding a Host to a Host Group To add a host to a group: 1. From the View menu, select Manage Groups. The Host Group Management dialog box appears. 2. From the Groups list, select the group to which you want to add the host. 3. From the Available Hosts list, select the host you want to add (or select multiple hosts by using Ctrl-Click or Shift-Click), and click the Right Arrow.
PAGE 112
7. Managing Hosts Searching for Hosts in the Discovery-Tree    Windows: InstallationDriveLetter:\Program Files\Emulex\Util\Config\hostgroups Linux: /usr/sbin/ocmanager/config/hostgroups Solaris: /opt/ELXocm/config/hostgroups The host group configuration files are completely interchangeable between different operating systems. For example, the host group configuration files created on a Solaris hosts can be copied directly to a Linux or Windows host, with no conversion required.
PAGE 113
8. Managing Adapters and Ports Using CIM (Windows only) 8. Managing Adapters and Ports This section describes the various adapter and port management functions you can perform using the OneCommand Manager application. Using CIM (Windows only) VMware on the Visor-based ESXi platforms uses CIM as the only standard management mechanism for device management.
PAGE 114
8. Managing Adapters and Ports FC/FCoE 2. Select an FC adapter in the discovery-tree. Figure 8-1 FC Adapter Information Tab FC Adapter Information Field Definitions      Model – The complete model name of the adapter. Serial Number – The manufacturer's serial number for the adapter. Hardware Version – Displays the JEDEC ID. Device ID – The default device ID for the selected adapter. (Not supported on VMware ESXi servers being managed through the CIM interface.
PAGE 115
8. Managing Adapters and Ports FC/FCoE 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 Information When you select an FC port from the discovery-tree, the Port Information tab contains general attributes associated with the selected FC adapter. To view FC Port information: 1. Select Host or Fabric view. 2. Select a FC port in the discovery-tree. 3.
PAGE 116
8. Managing Adapters and Ports FC/FCoE FC Port Information Field Definitions Port Attributes Area Field Definitions                 Port WWN – The Port World Wide Name of the adapter. Node WWN – The Node World Wide Name of the adapter. Fabric Name or Host 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 displayed in Fabric view. The host name is the name of the host containing the adapter.
PAGE 117
8. Managing Adapters and Ports FC/FCoE  Port Speed – The current port speed of the selected adapter port. Loop Map Table Definitions  The loop map shows the different ports present in the loop, and is present only if the port (adapter) is operating in loop mode. The simplest example would be to connect a JBOD directly to an adapter. When this is done, the port type is a private loop, and the loop map has an entry for the adapter, and one entry for each of the disks in the JBOD.
PAGE 118
8. Managing Adapters and Ports FC/FCoE 3. Select the Port Information tab. Figure 8-3 FCoE Port Information Tab FCoE Port Information Field Definitions Port Attributes Area Field Definitions           Port WWN – The Port World Wide Name of the adapter. Node WWN – The Node World Wide Name of the adapter. Fabric Name or Host 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 displayed in Fabric view.
PAGE 119
8. Managing Adapters and Ports FC/FCoE    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. Enable PFC Throttle checkbox – PFC throttle is enabled by default to prevent the loss of FCoE packets. Uncheck the box to disable PFC throttle.
PAGE 120
8. Managing Adapters and Ports FC/FCoE 3. Select the Statistics tab. Figure 8-4 Statistics Tab Port Statistics Field Definitions          Tx Frames – FC frames transmitted by this adapter port. Tx Words – FC words transmitted by this adapter port. Tx KB Count – FC kilobytes transmitted by this adapter port. Tx Sequences – FC sequences transmitted by this adapter port. LIP count – The number of loop initialization primitive (LIP) events that have occurred for the port.
PAGE 121
8. Managing Adapters and Ports FC/FCoE                    Ex Count Orig – The number of FC exchanges originating on this port. (Not supported on VMware ESXi servers being managed through the CIM interface.) Active XRIs – The number of active exchange resource indicators. (Not supported on VMware based ESXi platforms using the CIM interface.) Received P_BSY – The number of FC port-busy link response frames received.
PAGE 122
8. Managing Adapters and Ports FC/FCoE             No Receive Buffer Count – The number of SCSI I/O requests that were dropped. Queue Depth Overflow Count – The number of SCSI I/O requests received after a QFULL condition. Dropped SCSI I/O Count – The number of dropped SCSI I/O operations. Aborted SCSI I/O Count – The number of aborted SCSI I/O operations. Outstanding SCSI I/O Count – The number of SCSI I/O requests currently pending.
PAGE 123
8. Managing Adapters and Ports FC/FCoE Virtual Port Information Field Definitions      Number of Hosts – The total number of hosts discovered in the SAN. Number of Fabrics – The total number of fabrics discovered in the SAN. Number of Adapters – The total number of adapters discovered in the SAN. Number of Physical Ports – The total number of physical ports discovered in the SAN. Number of Virtual Ports – The total number of virtual ports discovered in the SAN.
PAGE 124
8. Managing Adapters and Ports FC/FCoE and so on. If the adapter/transceiver does not support some or all of the transceiver data, the fields display N/A. To view FC transceiver information: 1. Select Host or Fabric view. 2. In the discovery-tree, select the FC port whose transceiver information you want to view. 3. Select the Transceiver Data tab. Figure 8-7 FC Transceiver Data Tab Transceiver Data Field Definitions Module Attributes Area         Vendor – The name of the vendor.
PAGE 125
8. Managing Adapters and Ports FC/FCoE   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 transmitted bias current. TX Output Power – The measured transmitted output power. RX Input Power – The measured received input power.
PAGE 126
8. Managing Adapters and Ports FC/FCoE Note: Some adapters may show additional VPD information such as EC (EC level), MN (manufacturer ID) and XY data. Data in the YX field is a vendor-specific hexadecimal dump. Viewing FC Maintenance Information Use the Maintenance tab to view firmware information and update adapter firmware. You can also configure boot from SAN and change WWPN and WWNN information for the selected adapter port. (Not available in read-only mode.) To view FC firmware information: 1.
PAGE 127
8. Managing Adapters and Ports FC/FCoE     SLI-1 Name – The name of the SLI-1 firmware overlay. SLI-3 Name – The name of the SLI-3 firmware overlay. Adapter Boot Version – Displays one of the following:  The selected adapter port's boot code version if boot code is present.  “Disabled” if the boot code is disabled.  “Not Present” if boot code is not loaded. If boot code is not loaded, the Enable Adapter boot checkbox is not visible and you cannot configure the selected port to boot from SAN.
PAGE 128
8. Managing Adapters and Ports FC/FCoE Maintenance Tab Buttons (Not available in read-only mode.)    Download Firmware – Click to update firmware on the selected port. See “Updating Adapter Firmware” on page 249 for more information. Configure Boot – Check Enable adapter boot and click Configure Boot to configure boot from SAN. See “Configuring Boot from an FC SAN” on page 254 for more information. (Not available on VMware ESXi servers being managed through the CIM interface.
PAGE 129
8. Managing Adapters and Ports FC/FCoE Maintenance Tab Field Definitions 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 firmware version that is currently operational on the adapter. Active Firmware Version – The version of firmware running on the selected adapter.
PAGE 130
8. Managing Adapters and Ports FC/FCoE 2. In the discovery-tree, select the FC/FCoE target whose information you want to view. The Target Information tab appears. Figure 8-11 Target Information Tab Target Information Field Definitions Mapping Information Area       FC ID – The FC ID for the target; assigned automatically in the firmware. SCSI Bus Number – The SCSI bus number to which the target is mapped. SCSI Target Number – The target's identifier on the SCSI bus.
PAGE 131
8. Managing Adapters and Ports FC/FCoE To view the LUN information: 1. Select Host, Fabric or Virtual Port view. 2. From the discovery-tree, select an FC/FCoE port. 3. Select the LUN whose information you want to view. The LUN Information tab appears. Figure 8-12 FC/FCoE LUN Information Tab 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.
PAGE 132
8. Managing Adapters and Ports FC/FCoE Mapping Information Area    FCP LUN – The FC identifier used by the adapter to map to the SCSI 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 Note: LUN capacity information is only provided when the LUN is a mass-storage (disk) device. Other devices like tapes and scanners, etc. do not display capacity.
PAGE 133
8. Managing Adapters and Ports FC/FCoE 3. Select the Target Mapping tab. Figure 8-13 Target Mapping Tab Target Mapping Field Definitions Current Settings Area   Active Bind Type – WWPN, WWNN, or a destination identifier (D_ID). Automapping – The current state of SCSI device automapping: enabled (default) or disabled. Current Mappings Area  This table lists current mapping information for the selected adapter port.
PAGE 134
8. Managing Adapters and Ports FC/FCoE      Change Settings – Click to enable or disable automapping, choose a bind type and enable or disable LUN mapping and unmasking. (Not available on VMware ESXi servers being managed through the CIM interface.) Add Binding – Click to add a persistent binding. Bind New Target – Click to add a target that does not appear in the Persistent Binding table. Remove – Click to remove the selected binding.
PAGE 135
8. Managing Adapters and Ports FC/FCoE and SCSI ID can change when the system is rebooted. With persistent binding applied to one of these targets, the WWPN, SCSI Bus and SCSI ID remain the same when the system is rebooted. (Not available in read-only mode.) The driver refers to the binding information at during system boot. When you create a persistent binding, the OneCommand Manager application tries to make that binding dynamic.
PAGE 136
8. Managing Adapters and Ports FC/FCoE 3. Select the Target Mapping tab. All targets are displayed. Figure 8-14 Target Mapping Tab 4. Target mappings are displayed by WWPN, WWNN, or D_ID. “PB”, indicates mapping from persistent binding, while “Auto”, indicates an automapped target. In the Display Mode section, choose the display mode you want to use. 5. If you want click Change Settings. The Mapped Target Settings dialog box appears. You can enable or disable auto-mapping and change the active bind type.
PAGE 137
8. Managing Adapters and Ports FC/FCoE 4. Click Add Binding. The Add Persistent Binding dialog box is displayed. Figure 8-15 Add Persistent Binding Dialog Box 5. Select the bind type that you want to use (WWPN, WWNN or D_ID). 6. Select the Bus ID and target ID that you want to bind, and click OK. Note: Automapped targets have entries only in the second column of the Targets Table. Persistently bound targets have entries in the second and third columns.
PAGE 138
8. Managing Adapters and Ports FC/FCoE 5. Click the type of binding you want to use, and type the WWPN, WWNN, or D_ID you want to bind to the target. 6. Select the Bus ID and Target ID that you want to bind, and click OK. Note: A target does not appear on the target list if automapping is disabled and the target is not already persistently bound. Masking and Unmasking LUNs (Windows) LUN masking refers to whether or not a LUN is visible to the operating system.
PAGE 139
8. Managing Adapters and Ports FC/FCoE  Normally, for a specific LUN, the states reported in the 'On Reboot' and 'Current' column are identical. However, there can be times where these do not match. For example, the hbacmd utility can be used to change only the 'Current' mask state for a LUN and not touch the 'On Reboot' mask state contained in the configuration file. Current – The 'Current' column displays the live mask state currently in use by the driver.
PAGE 140
8. Managing Adapters and Ports FC/FCoE Note: Masked LUNs cannot be ExpressLane enabled because they are not presented to the host. Conversely, ExpressLane LUNs cannot be masked. Figure 8-18 Enabling an ExpressLane LUN To enable an ExpressLane LUN: 1. Select Host, Fabric or Virtual Port view. 2. From the discovery-tree, select an LPe15000 or LPe16000 series adapter. 3. Select the LUN on which you want to enable ExpressLane. The LUN Information tab appears. 4.
PAGE 141
8. Managing Adapters and Ports FC/FCoE fails. By changing the standby adapter's WWPN or WWNN it can assume the identity and configuration (for example, driver parameters, persistent binding settings, and so on) of the failed adapter. There are three options for referencing WWNs:    Factory Default WWN – As shipped from the factory. This value canot be changed. Non-Volatile WWN – Values that are saved in non-volatile adapter’s flash memory that survives a reboot and/or power outage.
PAGE 142
8. Managing Adapters and Ports FC/FCoE To change a port's WWPN or WWNN: 1. Do one of the following:  From the View menu, click Group Adapters by Host Name. From the toolbar, click Group Adapters by Host Name.  From the Host Grouping menu, select Group Adapter by Fabric Names. 2. In the discovery-tree, select the port whose information you want to change. 3. Select the Maintenance tab.  Figure 8-19 Maintenance Tab 4. Click Change WWN.
PAGE 143
8. Managing Adapters and Ports FC/FCoE 5. Click Yes. The Change World Wide Name Configuration dialog box appears. Figure 8-21 Change World Wide Name Configuration Dialog Box 6. Do one of the following:  Enter a new WWPN and/or WWNN.  Click Get Factory Default WWNs to load the settings that were assigned when the adapter was manufactured to the New WWPN and WWNN settings. These values can then be modified if desired and saved as Volatile or Non-Volatile WWNs.
PAGE 144
8. Managing Adapters and Ports FC/FCoE 9. Reboot the system for the changes to take effect. After rebooting, the changes are applied and appear in the Current section of the Maintenance dialog box. Creating and Deleting FC/FCoE Virtual Ports Creating Virtual Ports The OneCommand Manager application can automatically generate the WWPN for the virtual port based on the WWPN for the physical port or you can manually type the WWPN. You cannot generate virtual ports on 1 Gb/s and 2 Gb/s adapters.
PAGE 145
8. Managing Adapters and Ports FC/FCoE 2. From the discovery-tree, select the adapter port on which you want to create a virtual port. The Virtual Ports tab appears. Figure 8-22 Virtual Ports Tab 3. Do one of the following:  Check Auto-generate world wide port name. The OneCommand Manager application creates the unique WWPN for the new virtual port based on the WWPN of the physical port. This option allows you to automatically create up to 255 unique virtual ports for each physical port.
PAGE 146
8. Managing Adapters and Ports FC/FCoE Note: Ensure that a manually entered WWPN is unique to your particular SAN. Failure to do so could result in a non-functioning SAN and data loss. 4. Enter an optional name for the virtual port if you want. You can give the new virtual port any name you want up to 99 characters in length. This name is used as part of the Symbolic Node Name for the VPort. 5. Click Create Virtual Port. A dialog box appears notifying you that the virtual port was created.
PAGE 147
8. Managing Adapters and Ports FC/FCoE 2. From the discovery-tree, select the virtual port you want to delete. The Virtual Ports tab appears. Figure 8-23 Virtual Port Tab 3. Click Remove Virtual Port. The Delete Virtual Port Warning dialog box appears. Figure 8-24 Delete Virtual Port Warning Note: The link on the physical port must be up to delete a virtual port. The Remove Virtual Port button on the Virtual Port tab is disabled if the link is down. 4.
PAGE 148
8. Managing Adapters and Ports FC/FCoE Changing FC Adapter Port Names The OneCommand Manager application enables you to change FC adapter port names. (Not available in read-only mode.) For example, you may want to identify a particular adapter port with the function it supports, such as a tape drive, scanner, or some other device. Use any characters you want for names, and names can be up to 255 characters in length. You can also revert to the adapter's default name.
PAGE 149
8. Managing Adapters and Ports FC/FCoE  From the Port menu, click Reset Port.  From the toolbar, click Reset. The following warning appears: Figure 8-25 Reset Warning 3. Click Yes. The adapter port resets. The reset can require several seconds to complete. While the adapter port is resetting, the status bar shows “Reset in progress.” When the reset is finished, the status bar shows “Reset Completed”.
PAGE 150
8. Managing Adapters and Ports FC/FCoE The Host Driver Parameters Tab The Host Driver Parameters tab enables you to view and edit the adapter driver parameter settings contained in 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 adapter Driver Parameters tab.
PAGE 151
8. Managing Adapters and Ports FC/FCoE  Adapter-specific information is displayed in this area. This can include value, range, default, activation requirements and description. Driver Parameters Tab Buttons (Not available in read-only mode.)    Restore – If you changed driver parameters, but did not click Apply and you want to restore the parameters to their last saved values, click Restore. Defaults – Click to reset all driver parameter values to their default (out-of-box) values.
PAGE 152
8. Managing Adapters and Ports FC/FCoE Figure 8-27 Driver Parameters Tab – Adapter Selected 4. In the Driver Parameters tab, click the parameter that you want to change. A description of the parameter appears on the right side of the tab. 5. Enter a new value in the Value field in the same hexadecimal or decimal format as the current value or select a value from the drop-down menu. If you enter a value and the current value is in hexadecimal format, it is prefaced by “0x” (for example, 0x2d).
PAGE 153
8. Managing Adapters and Ports FC/FCoE Setting an Adapter Parameter Value to the Host Adapter Parameter Value To set an adapter parameter value to the corresponding host parameter value: 1. 2. 3. 4. 5. Select Host or Fabric view. In the discovery-tree, select the adapter port. Select the Driver Parameters tab. Click Globals. All parameter values are now the same as the global, or host, values. To apply the global values, click Apply.
PAGE 154
8. Managing Adapters and Ports FC/FCoE Setting Driver Parameters for All Adapters in a Host To change the driver parameters for all adapters installed in a host: 1. Do one of the following:  From the View menu, click Group Adapters by Host Name. From the toolbar, click Group Adapters by Host Name. 2. In the discovery-tree, click the host whose adapter driver parameters you want to change. 3. Select the Host Driver Parameters tab.
PAGE 155
8. Managing Adapters and Ports FC/FCoE Changing Non-dynamic Parameter Values (Linux 8.2) To change non-dynamic parameter values for Linux version 8.2: 1. Navigate to the /usr/sbin/ocmanager directory and run the scripts to stop the OneCommand Manager application processes. Type: ./stop_ocmanager 2. Stop all I/O to LPFC attached devices. 3. Unload the LPFC driver. Type: modprobe -r lpfc 4. Reload the driver. Type: modprobe lpfc 5.
PAGE 156
8. Managing Adapters and Ports FC/FCoE 6. Click Save. The Save Driver Parameters dialog box appears. You can save the file to a different directory or change its name. Figure 8-29 Save Driver Parameters Dialog Box 7. Use the two radio buttons to choose the type of parameters to save. You can save all parameters or only those parameters whose current values differ from their corresponding default values. A list of the saved parameters and their current values show in the Saved Parameters box. 8.
PAGE 157
8. Managing Adapters and Ports FC/FCoE Checkboxes next to the host and adapter entries are used 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. Figure 8-30 Batch Driver Parameters Update Dialog Box 4. Make your selections and click Start Updates. The OneCommand Manager application Batch Driver Parameter Update dialog box shows the current status of the update.
PAGE 158
8. Managing Adapters and Ports FC/FCoE 3. Set the parameters you want and click Apply Changes. Figure 8-31 FIP Tab for FCoE Adapters FIP Dialog Box Field Descriptions     Primary Fabric Name – Indicates the FC Fabric's WWN to which to connect. If the Primary Fabric Name is wild, i.e. 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, i.e.
PAGE 159
8. Managing Adapters and Ports FC/FCoE 2. Select the DCB tab. Figure 8-32 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.
PAGE 160
8. Managing Adapters and Ports FC/FCoE FCoE Properties Area (FCoE ports only)     State – The FCoE 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 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.
PAGE 161
8. Managing Adapters and Ports FC/FCoE Figure 8-33 Configure DCB Dialog Box for FCoE 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. Operating Version – Operating version of the DCBX protocol.
PAGE 162
8. Managing Adapters and Ports FC/FCoE   Transmit System Capabilities Enabled – 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. Receive Enabled – LLDP Receive can be enabled or disabled.
PAGE 163
8. Managing Adapters and Ports iSCSI 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 FCoE 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%.
PAGE 164
8. Managing Adapters and Ports iSCSI 3. Select the iSCSI Port Information tab. Figure 8-34 iSCSI Port Information Tab iSCSI Port Information 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.
PAGE 165
8. Managing Adapters and Ports iSCSI To view iSCSI network information: 1. Select Host or Fabric view. 2. Select an iSCSI port in the discovery-tree. 3. Select the iSCSI Network Information tab. Figure 8-35 iSCSI Network Information Tab iSCSI Network Information Tab Field Definitions Connection Info Area     Link Status – The status of the link on the selected adapter port. Port Speed – The port speed at which the selected port is running. Min. Bandwidth – The minimum bandwidth (i.e.
PAGE 166
8. Managing Adapters and Ports iSCSI   VLAN ID – The VLAN identifier to use 0-4094 (only valid when VLAN is enabled). 0 indicates the VLAN is disabled. VLAN Priority – The VLAN priority for the iSCSI interface. IPV6 Address (OCe14000-Series Adapters only)      Automatic assignment – When enabled, the unique routable addresses are assigned in conjunction with the router (similar for DHCP assignment).
PAGE 167
8. Managing Adapters and Ports iSCSI Advanced TCP/IP Configuration The Advanced TCP/IP Configuration dialog box enables you to add and remove Route and Address Resolution Procotol (ARP) table entries (applicable to IPv4 only) for the selected iSCSI port. Figure 8-36 Advanced TCP/IP Configuration Dialog Box To add table entries: 1. From the discovery-tree, select the iSCSI port whose configuration you want to modify. 2. Select the Network Information tab. 3. Click Advanced.
PAGE 168
8. Managing Adapters and Ports iSCSI 3. Select the VPD tab. Figure 8-37 iSCSI VPD Tab VPD Table Definitions     Product Name – Product information about the selected adapter port. PN (Part Number) – The adapter's part number. SN (Serial Number) – The adapter's serial number. VO – Vendor unique data. “V” indicates a vendor-specific field. An adapter may have none, one or more of these fields defined.
PAGE 169
8. Managing Adapters and Ports iSCSI 3. Click the iSCSI Statistics tab. Figure 8-38 iSCSI Statistics Tab iSCSI Statistics Field Definitions            Node Roles – The node role for this iSCSI initiator. Portal Count – The number of rows in the iscsiPortaltypeTable which are currently associated with this iSCSI instance. Node Count – The number of rows in the iscsiNodetypeTable which are currently associated with this iSCSI instance.
PAGE 170
8. Managing Adapters and Ports iSCSI                 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. Last Target Failure Name – The UTF-8 string name of the target that most recently failed a login request from this initiator.
PAGE 171
8. Managing Adapters and Ports iSCSI 2. In the discovery-tree, select the iSCSI target whose information you want to view. The Target Information tab appears. Figure 8-39 iSCSI Target Information Tab Target Information 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 the OneCommand Manager application. ETO – (Extended Timeout Value) The ETO for the target.
PAGE 172
8. Managing Adapters and Ports iSCSI Viewing iSCSI LUN Information When you select a LUN associated with an iSCSI adapter from the discovery-tree, the LUN Information tab displays information associated with that LUN. Note: The Refresh LUNs button only refreshes the LUN list for the currently selected target. To view the LUN information: 1. Select Host view. 2. From the discovery-tree, select the iSCSI LUN whose information you want to view. The LUN Information tab appears.
PAGE 173
8. Managing Adapters and Ports iSCSI Viewing iSCSI PCI Registers The iSCSI PCI Registers tab displays base PCI registers. See “Viewing the PCI Registers” on page 266 for FC PCI register information. Figure 8-41 iSCSI PCI Registers Tab To view iSCSI PCI registers: 1. From the discovery-tree, select the iSCSI function whose PCI information you want to view. 2. Select the iSCSI PCI Registers tab.
PAGE 174
8. Managing Adapters and Ports iSCSI 2. Select the DCB tab. Figure 8-42 DCB Tab for iSCSI Adapter Ports (OneConnect Adapter 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.
PAGE 175
8. Managing Adapters and Ports iSCSI PFC Properties Area Note: PFC is not supported on all the iSCSI adapter ports.     State – Enabled means that flow control in both directions (Tx and Rx) is enabled. State – Enabled means that flow control in both directions (Tx and Rx) is enabled. Disabled means that priority-flow control is currently disabled. The priority value, if Shown, is not applicable.
PAGE 176
8. Managing Adapters and Ports iSCSI  Configure DCB – Click to configure DCB parameters. See the following instructions. To configure DCB for iSCSI adapter ports: 1. From the discovery-tree, select the iSCSI adapter port whose DCB properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4. Configure the settings you want and click OK. Note: An error message is displayed if you try to configure more priority groups than the adapter supports.
PAGE 177
8. Managing Adapters and Ports iSCSI       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.
PAGE 178
8. Managing Adapters and Ports iSCSI     Group ID – The Priority Group ID. Priority Membership – The configured priority membership grouping. Bandwidth % – The configured value of bandwidth for the different Priority Groups. Max Configurable PGs – The maximum number of Priority Groups that can be configured. Configure DCB Dialog Box Buttons   Defaults – Click to return parameters to default iSCSI DCB settings.
PAGE 179
8. Managing Adapters and Ports iSCSI controlled using several drop down boxes. You can also configure the initiator authentication method and view the factory default login options. Figure 8-44 iSCSI Initiator Login Options Tab 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. OneCommand™ Manager Application P010066-01A Rev.
PAGE 180
8. Managing Adapters and Ports iSCSI Initiator Login Options Area    ImmediateData – Defines whether the initiator may append unsolicited data to a SCSI command. Possible values are “Yes” and “No”. HeaderDigest – When set to “CRC32C”, and the initiator is configured accordingly, the integrity of an iSCSI PDU's header segments are protected by a CRC32C checksum. Possible values are “CRC32C” and “None”.
PAGE 181
8. Managing Adapters and Ports iSCSI 3. Click Apply Changes. Note: Any changes to the iSCSI initiator name and alias apply to all ports on the adapter (i.e. all iSCSI ports share the iSCSI initiator name and alias). Note: On Windows platforms running the Microsoft iSCSI initiator, the initiator iSCSI name is the Microsoft iSCSI iqn. If you change it, the change remains in effect until the system is rebooted. After reboot, the Microsoft iqn is used again as the iSCSI initiator name.
PAGE 182
8. Managing Adapters and Ports NIC       DataSequenceInOrder – The order between sequences. 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.
PAGE 183
8. Managing Adapters and Ports NIC 3. Select the Port Information tab. Figure 8-46 NIC Port Information Tab NIC Port Information 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. IPv4 Address – The IPv4 address for the NIC port. Subnet Mask – The subnet mask for the NIC port.
PAGE 184
8. Managing Adapters and Ports NIC          PCI Function – The PCI function number assigned to the NIC function. PCI Bus Number – The PCI BUS number assigned to the NIC function. Max MTU – The maximum transmission unit for iSCSI traffic. Current MTU – The current transmission unit for iSCSI traffic. Port Speed – The current port speed of the selected port. Bandwidth Limit – The QoS bandwidth restriction on the port. (Non vNIC adapters only) VEPA Mode – Not Supported.
PAGE 185
8. Managing Adapters and Ports NIC 3. Select the VPD tab. Figure 8-47 NIC VPD Tab VPD Table Definitions     Product Name – Product information about the selected adapter port. PN (Part Number) – The adapter's part number. SN (Serial Number) – The adapter's serial number. VO – Vendor unique data. “V” indicates a vendor-specific field. An adapter may have none, one or more of these fields defined.
PAGE 186
8. Managing Adapters and Ports NIC Configuring DCB Parameters for NIC Only Adapter Ports The DCB tab displays parameters for NIC-only adapter ports. To view the DCB parameters for NIC-only adapter ports: 1. From the discovery-tree, select the NIC adapter port whose DCB properties you want to view. 2. Select the DCB tab. Figure 8-48 DCB Tab for NIC Adapter Ports (NIC Adapter Selected) DCB Tab Field Definitions    DCBX State – The current DCBX state (enabled or disabled).
PAGE 187
8. Managing Adapters and Ports NIC PFC Properties Area     State – Enabled means that flow control in both directions (Tx and Rx) is enabled. State – Enabled means that flow control in both directions (Tx and Rx) is enabled. Disabled means that priority-flow control is currently disabled. The priority value, if Shown, is not applicable.
PAGE 188
8. Managing Adapters and Ports NIC  Configure DCB – Click to configure DCB parameters. See the instructions below. To configure DCB for NIC adapter ports: 1. From the discovery-tree, select the NIC adapter port whose DCB properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4. Configure the settings you want and click OK. Note: An error message is displayed if you try to configure more priority groups than the adapter supports.
PAGE 189
8. Managing Adapters and Ports NIC 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.
PAGE 190
8. Managing Adapters and Ports NIC  Max Configurable PGs – The maximum number of Priority Groups that can be configured. Configure DCB Dialog Box Buttons   Defaults – Click to return to the factory settings. Configuration Rules – Click to display the NIC Priority window that lists the rules for configuring NIC priorities. You must observe the following rules when configuring priority groups for NIC-Only adapter ports:   1. Only one PFC priority can be configured. 2.
PAGE 191
8. Managing Adapters and Ports NIC 5. Reboot to change the SR-IOV state. Figure 8-50 Port Information Dialog Box with NIC VF selected Enabling and Disabling VEPA on NIC SR-IOV Ports The VEPA checkbox is displayed when SR-IOV is currently enabled on the NIC function. Check/uncheck the Enable VEPA checkbox under the Enable SR-IOV checkbox to enable/disable VEPA for the virtual functions on the NIC port. Note: VEPA is only available on OCe14000 series adapters. Note: SR-IOV is not supported with UMC.
PAGE 192
8. Managing Adapters and Ports NIC Figure 8-51 Port Information Dialog Box with NIC VF selected (OCe14102 adapter selected) Guest Operating System Discovery and Management from the Base Host Operating System When the OneCommand Manager application is installed on a guest operating system, the guest operating system and VF are discovered by the OneCommand Manager application running on the host operating system. The guest operating system host appears as a remote host in the discovery-tree.
PAGE 193
8. Managing Adapters and Ports NIC Select the VF in under the Base operating system host in the discovery-tree to display the Port Information tab. Some of the information displayed in the tab is obtained from the OneCommand Manager remote management agent running on the guest operating system.
PAGE 194
8. Managing Adapters and Ports NIC Running the OneCommand Manager Application on a Guest Operating System When the OneCommand Manager application is installed and executes on a VM’s guest operating system, it runs in a local-only/read-only mode. Therefore, only the guest host containing the adapter and NIC port is displayed in the discovery-tree.
PAGE 195
8. Managing Adapters and Ports OneConnect Adapters OneConnect Adapters Viewing OneConnect Adapter Information When you select a OneConnect adapter from the discovery-tree, the Adapter Information tab contains general attributes associated with the selected OneConnect adapter. You can also use this tab to change an adapter’s personality, enable or disable UMC, and to view and enable licenses.
PAGE 196
8. Managing Adapters and Ports OneConnect Adapters       HW Version – The hardware version of the selected adapter. NCSI Version – The Network Controller Sideband Interface version. IPL File Name – The name of the IPL (Initial Program Load) file currently loaded. PCI Express Link Speed – The speed of the PCI bus in which the adapter running. PCI Express Bus Width – The number of lanes for the slot in which the adapter is running.
PAGE 197
8. Managing Adapters and Ports OneConnect Adapters License Features Area Note: Not available on OneConnect OCe11101-EM/EX, OCe11102-EM/EX or OCe14000-series adapters.   Show License Features button – Click to show available licenses. See “Showing and Installing Licenses for OneConnect OCe10102 and OCe11102 Adapters” on page 204 for more information. Install License Features button – Click to install licenses.
PAGE 198
8. Managing Adapters and Ports OneConnect Adapters Configuring UMC Channel Management (OCe11102 adapters only) Note: IBM refers to UMC as SIMode. Using the Channel Management tab, each physical port can 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 and provisioning capabilities such as minimum and maximum transmit rates and LPVIDs (for untagged packets).
PAGE 199
8. Managing Adapters and Ports OneConnect Adapters 3. Assign an LPVID to all NIC channels. LPVID values can be specified between 2 and 4094 and must be unique across all channels on a port. However, LPVIDs do not need to be unique across the adapter's ports. You can assign the same LPVIDs on each port on the adapter. 4. Set the Minimum Bandwidth and Maximum Bandwidth values for each channel. Setting a channel's minimum and maximum bandwidth values to 0 disables the channel.
PAGE 200
8. Managing Adapters and Ports OneConnect Adapters Note: vNIC 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. Figure 8-57 Channel Management Tab for vNIC1 (IBM only) 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.
PAGE 201
8. Managing Adapters and Ports OneConnect Adapters Viewing the Channel Management Tab for UFP (IBM only) For IBM 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. 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.
PAGE 202
8. Managing Adapters and Ports OneConnect Adapters   Minimum BW (%) – The minimum percentage of the port's bandwidth at which the channel is guaranteed to run. Maximum BW (%) – The maximum percentage of the port's bandwidth that can be used by the channel. Viewing ASIC Information When you select a OneConnect multi-ASIC adapter from the discovery-tree, the ASIC Information tab contains general attributes associated with the selected ASIC. You can also use this tab to view and enable licenses.
PAGE 203
8. Managing Adapters and Ports OneConnect Adapters    PCI Express Link Speed – The speed of the PCI bus 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.
PAGE 204
8. Managing Adapters and Ports OneConnect Adapters Viewing OneConnect Multi-ASIC Adapter Information When you select a OneConnect multi-ASIC adapter from the discovery-tree, the Adapter Information tab contains general attributes associated with the selected dual ASIC four-port OneConnect adapter. To view general OneConnect multi-ASIC adapter information: 1. Select Host view. 2. Select a OneConnect multi-ASIC adapter in the discovery-tree.
PAGE 205
8. Managing Adapters and Ports OneConnect Adapters Figure 8-61 OneConnect OCe10102 and OCe11102 Adapter Information Tab Showing Licenses To view the available licenses for OCe10102 or OCe11102 adapters: 1. From the discovery-tree, select the OCe10102 or OCe11102 adapter whose licenses you want to view. The Adapter Information tab is displayed. 2. On the Adapter Information tab click Show License Features. The License Features window appears.
PAGE 206
8. Managing Adapters and Ports OneConnect Adapters Figure 8-62 Licensed Features Window Installing Licenses To install licenses for OCe10102 or OCe11102 adapters: 1. From the discovery-tree, select the OCe10102 or OCe11102 adapter whose licenses you want to install. The Adapter Information tab is displayed. 2. From the Adapter Information tab, click Install Feature Licenses. The Install Feature Licenses dialog box appears displaying the AdapterID. Figure 8-63 Install Feature Licenses Dialog Box 3.
PAGE 207
8. Managing Adapters and Ports OneConnect Adapters 4. When the AdapterID and Entitlement Code are successfully validated, download a License Key File containing one or more activation keys. 5. Using the Install Feature Licenses dialog box, enter the name of the License Key File (or click Browse to use a file browser to find the file) and click OK. 6. A dialog box appears confirming that you want to install the licenses. Click OK. 7.
PAGE 208
8. Managing Adapters and Ports OneConnect Adapters Figure 8-64 OneConnect OCe10102 and OCe11102 Adapter Information Tab To change the personality of OCe10102 and OCe11102 adapters: 1. From the discovery-tree, select the OCe10102 or OCe11102 adapter whose personality you want to change. The Adapter Information tab is displayed. 2. From the Personality area of the Adapter Information tab, select the personality type you want and click Apply.
PAGE 209
8. Managing Adapters and Ports OneConnect Adapters 3. Select the Firmware tab. Figure 8-65 OneConnect Firmware Tab Firmware Tab Field Definitions    Active Firmware Version – The firmware version currently being used by the adapter. Flash Firmware Version – The flash firmware version currently being used by the adapter. BIOS Version – The version of the BIOS currently being used by the adapter.
PAGE 210
8. Managing Adapters and Ports OneConnect Adapters Firmware Tab Buttons (Not available in read-only mode.)   Download Firmware – Click to update firmware on the selected adapter. See “Updating Adapter Firmware” on page 249 for more information. Diagnostic Dump – Click to create a diagnostic dump for the selected adapter. See “Creating Diagnostic Dumps” on page 282 for more information.
PAGE 211
8. Managing Adapters and Ports OneConnect Adapters Note: Enabling and disabling OneConnect physical ports is not supported via the CIM interface. Note: You cannot disable a port if PXE Boot is enabled or if any of the iSCSI target sessions are boot sessions. To enable or disable a physical port: 1. In the discovery-tree, select the physical port you want to enable or disable. 2. Select the Physical Port Info tab. 3. Click Enable Port or Disable Port.
PAGE 212
8. Managing Adapters and Ports OneConnect Adapters For 10GB SFP+, the length is the actual DAC cable length and 0 indicates an optical cable. For the QSFP+ module type, a length of 0 indicates an optical cable and any non-zero length indicates a DAC cable (i.e. the length does need to be the actual DAC cable length). 5. Click OK. Note: For an embedded mezzanine adapter linked to an embedded switch on the internal port, the DAC Cable Length value is ignored.
PAGE 213
8. Managing Adapters and Ports OneConnect Adapters PHY Data Field Definitions Operational Attributes Area   Temperature – The temperature of the selected port. Pair A/B/C/D Signal-to-Noise (SNR) Margin – Displays the CNA's MDI interface average SNR margin for twisted pairs A, B, C & D. Error Rates Area   Low Density Parity Check (LDPC) Frame Errors – The LDPC counter tracks the number of LDPC frames received by CNA's MDI interface that can not be corrected.
PAGE 214
8. Managing Adapters and Ports OneConnect Adapters 3. Select the Transceiver Data tab. Figure 8-69 OneConnect Transceiver Data Tab Transceiver Data 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.
PAGE 215
8. Managing Adapters and Ports OCe14000-Series Adapters   TX Output Power – The measured TX output power. RX Input Power – The measured RX input power. OCe14000-Series Adapters Configuring OCe14000-Series Adapters When 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.
PAGE 216
8. Managing Adapters and Ports OCe14000-Series Adapters Figure 8-70 OCe14000-series Adapter Configuration Tab (FCoE selected) OCe14000-series Adapter Configuration Tab Field Definitions    Current Configuration – The protocol running on the adapter. Next Boot Configuration – Displays 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.
PAGE 217
8. Managing Adapters and Ports OCe14000-Series Adapters  Details – Displays a pop-up window with more information about the current configuration running on the adapter. Figure 8-71 Current Configuration Details example Configuring Single Personalities The Single personality view allows you to select the same protocol to run on all ports of the adapter.
PAGE 218
8. Managing Adapters and Ports OCe14000-Series Adapters To configure a single personality: 1. From the discovery-tree, select the OCe14000-series adapter whose personality you want to configure. 2. From the Adapter Configuration tab, check the Single personality (all ports) radio button. 3. Select the personality you want to apply from the Personality pull-down menu. If you choose the NIC + RoCE configuration, the NIC + RoCE configuration list displays descriptions of the available RoCE profiles.
PAGE 219
8. Managing Adapters and Ports OCe14000-Series Adapters When the Custom radio button is selected, the Adapter Configuration tab looks like the following: Figure 8-73 Custom View Note: Custom configurations are only available if the adapter supports mixed or concurrent mode storage. Note: If you configure all ports the same, you essentially configured a single personality. To set up a custom configuration: 1.
PAGE 220
8. Managing Adapters and Ports OCe14000-Series Adapters When you click on the second function's pull-down menu, the available storage protocols for the function are displayed. Figure 8-74 Mixed Mode Protocol pull-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.
PAGE 221
8. Managing Adapters and Ports OCe14000-Series Adapters Concurrent Mode When concurrent mode is available, up to three functions per port are configurable. Figure 8-75 Concurrent Storage Configuration View When configuring storage, the first function must be set to NIC. The pull-down menu for selecting a storage protocol to run on the second and third functions is the same as the pull-down menu for mixed mode storage.
PAGE 222
8. Managing Adapters and Ports OCe14000-Series Adapters 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 pull-down menu. Configuring RoCE in a Custom View In Custom view, NIC + RoCE can be configured on the first function of a port. After checking Configure NIC + RoCE, only the first function of each port is available and you can select NIC + RoCE or just NIC to run on each port.
PAGE 223
8.
PAGE 224
8. Managing Adapters and Ports OCe14000-Series Adapters   If storage protocols are assigned to the 2nd and 3rd channels, they must be different storage protocols. The 4th and higher channels on a port (if available) can only be assigned NIC or None. Bandwidth and LPVID assignments are subject to the following rules:      A channel's logical link can be set to down by setting both the minimum and maximum bandwidths to 0.
PAGE 225
8. Managing Adapters and Ports OCe14000-Series Adapters 7. The LPVIDs will be set to 0. You must assign a valid LPVID to the NIC channel. Note: These rules create the default settings for the channels. You can change these settings before saving them. IBM MultiChannel Configuration View For IBM multichannel configuration, there are three different multichannel types available: vNIC, SIMode, and UFP.
PAGE 226
8. Managing Adapters and Ports OCe14000-Series Adapters vNIC Configuration When vNIC is selected on the adapter, the Adapter Configuration tab looks like the following: Figure 8-80 MultiChannel vNIC View (mix mode storage) The Channel Configuration table shows the channel properties for vNIC. Additionally, the protocol can be configured on the second and third channels including NIC . The NIC channels can be assigned an LPVID (or inner VLAN ID). It can be assigned any value from 0-4094.
PAGE 227
8. Managing Adapters and Ports OCe14000-Series Adapters  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. SIMode Configuration When SIMode is selected, the Adapter Configuration tab looks like the following: Figure 8-81 MultiChannel SIMode View SIMode and UMC configuration are exactly the same. See “UMC Configuration View” on page 223 for more information.
PAGE 228
8. Managing Adapters and Ports OCe14000-Series Adapters UFP Configuration When UFP is selected, the Adapter Configuration tab looks like the following: Figure 8-82 MultiChannel UFP View (concurrent mode storage) The Channel Configuration table shows the channel properties for UFP. Additionally, the protocol can be configured on the second and third channels including NIC . UFP Configuration Rules There are drop-down menus for each port's 2nd and 3rd channels.
PAGE 229
8. Managing Adapters and Ports OCe14000-Series Adapters For Dell NPar adapters the Adapter Configuration tab is different than for the other adapters. There are no choices in the Next Boot Configuration for single personality, multichannel, or custom configurations. Instead there is a single checkbox to enable or disable NPar and an NPar Configuration table to configure NPar partition protocol and bandwidth assignments.
PAGE 230
8. Managing Adapters and Ports OCe14000-Series Adapters When NPar is disabled (NPAR Enabled checkbox is unchecked), only a single partition per port is available. This partition can be configured to run NIC or NIC + RoCE. Figure 8-83 Adapter Configuration Tab for NPar Adapters (NPar disabled) Configuring RoCE on NPar Adapters You can configure NIC + RoCE on NPar adapters when NPar is disabled. See Figure 8-83 above. Use the Protocol pull-down menu for each port to select NIC or NIC + RoCE.
PAGE 231
8. Managing Adapters and Ports OCe14000-Series Adapters  SR-IOV is not supported with RoCE configurations. When NPar is enabled, the Adapter Configuration tab looks like the following: Figure 8-84 Adapter Configuration Tab with NPar Enabled (NParEP Mode Disabled) For adapters that support sixteen functions, on two port adapters you can configure up to eight partitions per port. Four port adapters allow up to four partitions per port. The “None” setting can be configured on any but the 1st partition.
PAGE 232
8. Managing Adapters and Ports OCe14000-Series Adapters Figure 8-85 Adapter Configuration Tab with NPar and NParEP Mode Enabled (2 port configuration) When NParEP Mode is enabled on two port adapters, up to eight partitions per port can be configured. Figure 8-86 Adapter Configuration Tab with NPar and NParEP Mode Enabled (4 port configuration) Four port adapters allow up four partitions per port to be configured when NParEP Mode is enabled.
PAGE 233
8. Managing Adapters and Ports OCe14000-Series Adapters Note: These rules apply when NParEP mode is enabled or disabled.        The first partition on a port is always NIC. Up to sixteen partitions can be configured on NPar adapters when NParEP Mode is enabled. When NPar is enabled, RoCE cannot be configured on any partition. A storage protocol can be assigned to any of the second through fourth partitions. Any partitions above the fourth partition can only be assigned NIC or None.
PAGE 234
8. Managing Adapters and Ports OCe14000-Series Adapters Configuring DCB Parameters for FCoE/iSCSI Adapter Ports The DCB tab displays parameters for FCoE/iSCSI adapter ports. Note: For adapter ports running only FCoE or only iSCSI, refer to “Configuring DCB Parameters for FCoE Adapter Ports” on page 158 and to “Configuring DCB Parameters for iSCSI Adapter Ports” on page 173. To view the DCB parameters for FCoE/iSCSI adapter ports: 1.
PAGE 235
8. Managing Adapters and Ports OCe14000-Series Adapters PFC Properties Area     State – Enabled means that flow control in both directions (Tx and Rx) is enabled. State – Enabled means that flow control in both directions (Tx and Rx) is enabled. Disabled means that priority-flow control is currently disabled. The priority value, if Shown, is not applicable.
PAGE 236
8. Managing Adapters and Ports OCe14000-Series Adapters  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 below. To configure DCB for FCoE adapter ports: 1. From the discovery-tree, select the adapter port whose DCB properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4.
PAGE 237
8. Managing Adapters and Ports OCe14000-Series Adapters    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. Operating Version – 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.
PAGE 238
8. Managing Adapters and Ports OCe14000-Series Adapters Note: Not shown when multichannel, including NPar, is enabled on the adapter.   Active Groups  Group ID – The Priority Group ID.  Priority Membership – The different priorities that are assigned to the various Priority Groups. This is the currently active configuration.  Bandwidth – The bandwidths that are assigned to different Priority Groups. This is the currently active configuration. Configured Groups  Group ID – The Priority Group ID.
PAGE 239
8. Managing Adapters and Ports OCe14000-Series Adapters Configuring DCB Parameters for RoCE Adapter Ports The DCB tab displays parameters for RoCE adapter ports. Note: RoCE configurations are not supported with SR-IOV. To view the DCB parameters for RoCE adapter ports: 1. From the discovery-tree, select the RoCE adapter port whose DCB properties you want to view. 2. Select the DCB tab.
PAGE 240
8. Managing Adapters and Ports OCe14000-Series Adapters PFC Properties Area     State – Enabled means that flow control in both directions (Tx and Rx) is enabled. State – Enabled means that flow control in both directions (Tx and Rx) is enabled. Disabled means that priority-flow control is currently disabled. The priority value, if Shown, is not applicable.
PAGE 241
8. Managing Adapters and Ports OCe14000-Series Adapters  Configure DCB – Click to configure DCB parameters. See the instructions below. To configure DCB for NIC adapter ports: 1. From the discovery-tree, select the NIC adapter port whose DCB properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4. Configure the settings you want and click OK.
PAGE 242
8. Managing Adapters and Ports OCe14000-Series Adapters  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.
PAGE 243
8. Managing Adapters and Ports OCe14000-Series Adapters   Priority Membership – The configured priority membership grouping. Bandwidth % – The configured value of bandwidth for the different Priority Groups. Note: PG15 has no bandwidth setting.  Max Configurable PGs – The maximum number of Priority Groups that can be configured. Bandwidths of all the priority groups must add up to 100%. Configure DCB Dialog Box Buttons   Defaults – Click to return to the factory settings.
PAGE 244
9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) Linux Considerations 9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) Use the DHCHAP tab to view and configure FC-SP DHCHAP (Diffie-Hellmann Challenge Handshake Authentication Protocol). You can authenticate an adapter to a switch. Note: The following notes apply when using FC-SP DHCHAP authentication:        DHCHAP is available only for FC ports, not FCoE ports.
PAGE 245
9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) Enabling Authentication lpfc_enable_auth Module Parameter Use the lpfc_enable_auth module parameter to enable or disable authentication support. This module parameter can be set when loading the driver to enable or disable authentication on all Emulex adapters in the system, or it can be set dynamically after the driver is loaded to enable or disable authentication for each port (physical and virtual).
PAGE 246
9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) DHCHAP Tab DHCHAP Tab The DHCHAP tab enables you to configure authentication. Figure 9-1 DHCHAP Tab DHCHAP Tab Field Definitions   Source – The WWPN of the adapter port. Destination – The fabric (switch). Configuration Area   Mode – The mode of operation. There are three modes: Enabled, Passive and Disabled.  Enabled – The adapter initiates authentication after issuing an FLOGI to the switch.
PAGE 247
9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) DHCHAP Tab      authentication failure is assumed (no authentication is performed). The time value ranges from 20 to 999 seconds. Bi-Directional – If enabled, the adapter driver supports authentication initiated by either the switch or the adapter. If disabled, the driver supports adapter initiated authentication only. Re-authenticate – If enabled, the driver can periodically initiate authentication.
PAGE 248
9. Using FC-SP DHCHAP Authentication (Windows, Linux 8.2 and Solaris) DHCHAP Tab Changing Your Password To change your password: 1. From the discovery-tree, select the adapter whose password you wish to change. 2. Select the DHCHAP tab and click Set Password. The Password dialog box is displayed. 3. Choose Set Local Password or Set Remote Password.  Local password is used by the adapter driver when the adapter initiates authentication to the switch (typical use).
PAGE 249
10. Updating Adapter Firmware Updating Firmware for a Single Adapter 10. Updating Adapter Firmware The OneCommand Manager application enables you to update firmware for a single adapter or simultaneously for multiple adapters. Updating Firmware for a Single Adapter Using the Maintenance or Firmware tab, you can update firmware on local and remote adapters. The firmware file must be downloaded from the Emulex website and extracted to a local drive before you can perform this procedure.
PAGE 250
10. Updating Adapter Firmware Updating Firmware for a Single Adapter 3. Select the Maintenance or Firmware tab and click Download Firmware. If the warning screen appears, click Yes. The Firmware Download dialog box appears. Figure 10-1 Firmware Download Dialog Box 4. Using the Firmware Download dialog box, navigate to the unzipped, extracted image file you want to download.
PAGE 251
10. Updating Adapter Firmware Updating Firmware for Multiple Adapters Updating Firmware for Multiple Adapters Use batch mode 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. (Not available in read-only mode).
PAGE 252
10. Updating Adapter Firmware Updating Firmware for Multiple Adapters Figure 10-2 Batch Firmware Download Dialog Box, Selecting Adapters to Update 4. Make your selections and click Start Download. When downloading begins, the tree-view displays the progress. As firmware for a selected adapter is being downloaded, it appears orange in the tree-view. Once successful downloading is complete, the entry changes to green. If the download fails, the entry changes to red.
PAGE 253
10. Updating Adapter Firmware Updating Firmware for Multiple Adapters Figure 10-3 Batch Firmware Download Dialog Box, Download Complete 5. When downloading is finished, you can click Save Log File to save copy of the activity log. OneCommand™ Manager Application P010066-01A Rev.
PAGE 254
11. Configuring Boot from an FC SAN Boot Types 11. Configuring Boot from an FC SAN You can use the OneCommand Manager application to configure a system to boot from an attached FC/FCoE LUN. Boot from SAN allows servers on a storage network to boot their operating systems directly from a SAN storage device, typically identified by its WWPN and a LUN located on the device.
PAGE 255
11. Configuring Boot from an FC SAN Boot Device Parameters       For OpenBoot, you must also provide a Target ID parameter. The OneCommand Manager application runs on a running operating system, so you must boot the host to configure boot from SAN with the OneCommand Manager application. You must work from a running host that supports the OneCommand Manager application. Often, this host has booted from a direct-attached drive.
PAGE 256
11. Configuring Boot from an FC SAN Boot Device Parameters Note: For OneConnect adapters, boot is always enabled and cannot be disabled. Figure 11-1 Boot from SAN Configuration Dialog Box The Boot from SAN Configuration dialog box varies for each boot type. Figure 11-1 depicts the boot from SAN configuration for the x86 type boot. 4. Verify the adapter address and boot version to make sure you configure the correct adapter and that it has the boot code version you want. 5.
PAGE 257
11. Configuring Boot from an FC SAN Boot Device Parameters Auto (default)  1 Gb/s (if available)  2 Gb/s (if available)  4 Gb/s (if available)  8 Gb/s (if available)  16 Gb/s (if available) 7. If you want, click Advanced Settings to configure autoscan, spinup delay and so on. See “Configuring Advanced Settings (Boot from SAN)” on page 259 for more information. 8. For x86 and EFIBoot, select one or more boot devices. For OpenBoot, select only one boot device. 9.
PAGE 258
11. Configuring Boot from an FC SAN Boot Device Parameters Figure 11-2 Select Boot Device Window (for x86 or EFIBoot) 10. On the Boot from SAN Configuration dialog box, click Apply to save your changes, but leave the dialog box open or click OK to apply the changes and close the dialog box. Note: Click Close to close the Boot from SAN Configuration dialog box without saving your changes. A message appears to discard your changes. 11. Reboot the system for your changes to take effect.
PAGE 259
11. Configuring Boot from an FC SAN Configuring Advanced Settings (Boot from SAN) Configuring Advanced Settings (Boot from SAN) The OneCommand Manager application provides advanced settings for each boot type. From the Boot from SAN Configuration dialog box, click Advanced Settings. A boot type-specific dialog box allows you to enable options such as spinup delay and autoscan. If you do not use advanced settings, the default values are used.
PAGE 260
11. Configuring Boot from an FC SAN Configuring Advanced Settings (Boot from SAN)   If a boot device is present, the BIOS boots from it immediately. If a boot device is not ready, the BIOS waits for the spinup delay and, for up to three additional minutes, continues the boot scanning algorithm to find another multi-boot device. Note: The default topology is auto topology with loop first. Change this topology setting, if necessary, before configuring boot devices.
PAGE 261
11. Configuring Boot from an FC SAN Configuring Advanced Settings (Boot from SAN) EFIBoot Advanced Adapter Settings Dialog Box Use the EFIBoot Advanced Adapter Settings dialog box to configure the advanced settings for the selected EFIBoot adapter. Figure 11-4 EFIBoot Advanced Adapter Settings Dialog Box EFIBoot Advanced Adapter Settings Field Definitions      Device Path – Makes the Fibre driver appear as a SCSI driver.
PAGE 262
11. Configuring Boot from an FC SAN Configuring Advanced Settings (Boot from SAN) 100 ms  200 ms Default AL_PA number – The range is 0x 00-EF. The default is 0x00. This option changes the AL_PA (Arbitrated Loop Physical Address) of the selected adapter. (Not available for OneConnect adapters.)   OpenBoot Advanced Adapter Settings Dialog Box Use this dialog box to configure the Advanced Adapter Settings for the selected OpenBoot adapter.
PAGE 263
12. Exporting SAN Information Creating a SAN Report 12. Exporting SAN Information Creating a SAN Report The OneCommand Manager application enables you to create reports about discovered SAN elements. Reports are generated in .xml and .csv format and include all the SAN information that is displayed through the various OneCommand Manager application tabs. Note: Creating a SAN report can take several minutes for a large SAN. To create a SAN report: 1. From the File menu, select Export SAN Info. 2.
PAGE 264
13. Diagnostics LightPulse FC HBA Diagnostics 13. Diagnostics Note: Diagnostics are not supported on COMSTAR ports. LightPulse FC HBA Diagnostics This section describes the diagnostics available for LightPulse FC adapters. For OneConnect adapter diagnostics, see “OneConnect Diagnostics” on page 276. Use the Diagnostics tab to:     View flash load list, PCI registers and wakeup parameter information. Run these tests on Emulex adapters installed in the system: (Not available in read-only mode.
PAGE 265
13. Diagnostics LightPulse FC HBA Diagnostics Viewing Flash Contents, PCI Registers, and Wakeup Information The Diagnostics tab shows PCI register dump information and flash memory contents. The information is read-only and is depicted below. Figure 13-1 PCI Registers and Flash Contents of the Diagnostics Tab Viewing Flash Contents If you check the Show Wakeup Image Only checkbox, the flash overlays that are not loaded when the system is booted no longer display. This checkbox defaults to unchecked.
PAGE 266
13. Diagnostics LightPulse FC HBA Diagnostics Viewing Overlay Details If you double-click on a flash overlay, another window appears with details about that overlay. Figure 13-2 Overlay Detail Window To see the details of a different flash overlay image, you can either close the details window and double-click on another overlay name, or choose a different overlay name from the Flash overlay menu. Viewing the PCI Registers The PCI Registers appear directly on the Diagnostics tab.
PAGE 267
13. Diagnostics LightPulse FC HBA Diagnostics Running a Power On Self Test (POST) Note: Not supported on LPe15000 or LPe16000 series adapters. 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. (Not available in read-only mode.) To run the POST: 1. From the discovery-tree, select the adapter port on which you want to run the POST. 2. Select the Diagnostics tab and click Power-on Self Test (POST).
PAGE 268
13. Diagnostics LightPulse FC HBA Diagnostics      provides the ability to diagnose marginal cable conditions (e.g. dust in the optics) that result in higher error rates. D_Port should not be enabled on the switch port. D_Port tests run with the physical connection in an offline diagnostic state, so normal I/O cannot be sent through the physical port while the test is in progress. While the port is in D_Port mode, the link will appear down on that port; similar to an unplugged cable.
PAGE 269
13. Diagnostics LightPulse FC HBA Diagnostics 3. Click Start Tests. Figure 13-5 D_Port Tests window D_Port Window Descriptions D Port Window Field Definitions      Overall Test Result – Displays PASSED or FAILED depending upon the outcome of all the test phases. Frame Size – The size of the frames used in each test phase. Frame Count – The number of frames generated during each test phase. Roundtrip Link Latency – Estimated cable length calculated by switch during the execution of all tests.
PAGE 270
13. Diagnostics LightPulse FC HBA Diagnostics  Close - Click to close the window (disabled while tests are running). Note: If the SFP does not support running D_Port diagnostics, clicking the Start Tests button causes an error message to be displayed indicating this and the tests will not be executed. Note: If the adapter firmware does not support running D_Port diagnostics, clicking the Start Tests button causes an error message to be displayed indicating this and the tests will not be executed.
PAGE 271
13. Diagnostics LightPulse FC HBA Diagnostics Note: For VMware systems you must set a dump directory before initiating a dump. The dump directory must be a “Storage” partition (a datastore) under the directory /vmfs/volumes. 4. Click OK. Dump files are created. Where these files are created depends upon your operating system:  Windows – %ProgramFiles%Util\Dump\  Solaris – /opt/ELXocm/Dump  Linux – /var/log/emulex/ocmanager/Dump  VMware – a dump directory you created under /vmfs/volumes.
PAGE 272
13. Diagnostics LightPulse FC HBA Diagnostics To run advanced diagnostics tests, click Advanced Diagnostic Tests on the Diagnostics tab to view the Diagnostic Test Setup dialog box. You can run four types of tests:     PCI Loopback Internal Loopback External Loopback End-to-End (ECHO) Note: You cannot run the External Loopback test and ECHO test concurrently. If you select External Loopback the ECHO test section is disabled and vice versa.
PAGE 273
13. Diagnostics LightPulse FC HBA Diagnostics   Internal Loopback Test – 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 Test – A diagnostic test in which a random data pattern is sent down to an adapter link port. The data goes out the port and immediately returns via a loopback connector.
PAGE 274
13. Diagnostics LightPulse FC HBA Diagnostics 3. Click Start. The following warning appears: Figure 13-9 Run Diagnostic Tests Warning 4. Click OK. If you choose to run an External Loopback test the following window appears. Figure 13-10 Advanced Diagnostic Tests Warning Window for External Loopback 5. Click OK. The progress bar indicates that the test is running.
PAGE 275
13. Diagnostics LightPulse FC HBA Diagnostics and click Select. All relevant information for the selected port is automatically added to the Target Identifier section of the Diagnostics dialog box. Figure 13-11 Select Echo Test Target Window 3. Define the other parameters you want to use and click Start Test. The following warning window appears: Figure 13-12 Advanced Diagnostic Tests Warning Window 4. Click OK. A result screen appears and the test results appear in the Test Log.
PAGE 276
13. Diagnostics OneConnect Diagnostics After writing an entry into the log, you are prompted to clear the display. The default name of the saved file is DiagTest.log. An example of a saved log file appears below: Figure 13-13 Example of a DiagTest.log Window To save the log file: 1. After running a test from the Diagnostic Test Setup dialog box, click Save to File. The Select Diagnostic Log file Name dialog box appears. The default name of a saved file is DiagTest.log. 2.
PAGE 277
13. Diagnostics OneConnect Diagnostics All functions are supported locally and remotely on hosts managed with TCP/IP access. Test results and the status of running tests are time stamped and appear in the Test Status area. Figure 13-14 Diagnostics Tab (10GBASE-T adapter selected) OneConnect Loopback Test Combinations Run the following loopback test combinations using the appropriate checkboxes:   DMA Loopback Test – (For OCe10102-FM and OCe11102-FM adapters only.
PAGE 278
13. Diagnostics OneConnect Diagnostics FCoE End to End Echo Test The end-to-end test enables you send an ECHO command/response sequence between an adapter port and a target port. (Not available on ESXi systems.) Note: Not all remote devices respond to an echo command. You cannot run the ECHO test and the External Loopback test concurrently. If you select the ECHO Test the External Loopback test is disabled. Error Action Enables you to define what is to be done in the event of a test failure.
PAGE 279
13. Diagnostics OneConnect Diagnostics 3. Click Start. The following warning appears: Figure 13-15 Run Diagnostic Tests Warning 4. Click OK. If you choose to run an External Loopback test the following window appears: Figure 13-16 Advanced Diagnostic Tests Warning Window for External Loopback 5. Click OK. The progress bar indicates that the test is running.
PAGE 280
13. Diagnostics OneConnect Diagnostics Note: On OCe11102 series adapters beaconing can only be done on one port at a time. If you enable beaconing on a port, you cannot enable beaconing on another port until you disable beaconing on the previous port. Running TDR Tests (10GBASE-T Adapters Only) The TDR test is a cable diagnostic that can tell you the length of the cable, whether or not the cable has any defects (open/short), and the distance to the defect; if one exists.
PAGE 281
13. Diagnostics OneConnect Diagnostics After writing an entry into the log, you are prompted to clear the display. The default name of the saved file is DiagTest.log. An example of a saved log file appears below: Figure 13-17 Example of a DiagTest.log Window To save the log file: 1. After running a test from the Diagnostic tab, click Save Test Log. The Diagnostic Test Log dialog box appears. The default name of a saved file is DiagTest.log. 2.
PAGE 282
13. Diagnostics OneConnect Diagnostics Creating Diagnostic Dumps The diagnostic dump capability enables you to create a “dump” file for a selected adapter. Dump files contain various information such as firmware version, driver version and so on, that is particularly useful when troubleshooting an adapter. You can also retrieve dump files from remote hosts. (Not available in read-only mode.) To start a diagnostic dump: 1.
PAGE 283
13. Diagnostics OneConnect Diagnostics .dmp  .txt 5. To obtain remote host dump files and copy them to your local system, click Get Dump Files. The Diagnostic Dump File Transfer dialog box appears.  Note: The Get Dump Files button is disabled when a local adapter port is selected. Figure 13-19 Diagnostic Dump File Transfer Dialog Box 6. Select the files you want to copy (multiple selections are available) and click Start Copy.
PAGE 284
14. Troubleshooting General Situations 14. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation.
PAGE 285
14. Troubleshooting General Situations Table 14-1 General Situations (Continued) Situation Resolution In the OneCommand Manager application Ensure the Emulex NIC driver is loaded and that the operating discovery-tree, multiple UCNA FCoE or iSCSI system sees ALL NIC ports. They do not need to be plumbed or ports are grouped under a single physical port. configured; just visible to the operating system. An operating error occurs when attempting to Reboot the system. run the OneCommand Manager application.
PAGE 286
14. Troubleshooting Emulex Driver for Linux and OneCommand Manager Application Situations Emulex Driver for Linux and OneCommand Manager Application Situations Table 14-2 Emulex Driver for Linux and OneCommand Manager Application Situations Situation Resolution NIC Link fails to come up. For Emulex UCNAs and CFAs in NIC mode, you may need to properly configure the network interface using system administration utilities.
PAGE 287
14. Troubleshooting Emulex Driver for Linux and OneCommand Manager Application Situations Table 14-2 Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution LPFC driver fails to recognize an adapter and logs “unknown IOCB” messages in the system log during driver load. The adapter is running outdated firmware. Update adapter firmware to minimum supported revision listed in the driver installation guide (or newer).
PAGE 288
14. Troubleshooting Emulex Driver for Linux and OneCommand Manager Application Situations Table 14-2 Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution The OneCommand Manager application software package does not install. An error message states that: “inserv Service Elxlpfc has to be enabled for service ElxDiscSrvinserv: exiting now/sbin/ inserv failed exit code 1.” Reinstall the driver with the lpfc-install script.
PAGE 289
14. Troubleshooting Emulex Driver for Linux and OneCommand Manager Application Situations Table 14-2 Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution Cannot see new LUNs. Try the following: 1) Click the Refresh LUNs button in the toolbar. 2) Exit the OneCommand Manager application and restart the OneCommand Manager application. If new LUNs are visible, you are finished.
PAGE 290
14. Troubleshooting Emulex Driver for Solaris and OneCommand Manager Application Situations Emulex Driver for Solaris and OneCommand Manager Application Situations Table 14-3 Emulex Driver for Solaris and OneCommand Manager Application Situations Situation Resolution NIC link fails to come up. For Emulex UCNAs and CFAs in NIC mode, you may need to properly configure the network interface using system administration utilities.
PAGE 291
OneCommand™ Manager Command Line Interface Version 10.2 User Manual P010067-01A Rev.
PAGE 292
Copyright © 2007–2014 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.
PAGE 293
1. Introduction Overview 1. Introduction Overview The OneCommand™ Manager Command Line Interface (CLI) utility is a comprehensive management utility for Emulex host bus adapters (HBAs), universal converged network adapters (UCNAs, also called OneConnect adapters), and converged fabric adapters (CFAs). The CLI provides support for commonly used commands without requiring installation of the OneCommand Manager graphical user interface (GUI). The OneCommand Manager CLI console application name is HbaCmd.
PAGE 294
1.
PAGE 295
1.
PAGE 296
1. Introduction OneCommand Manager Secure Management OneCommand Manager Secure Management Overview OneCommand Manager Secure Management gives system administrators the ability to further enhance the active management security of their networks. Using Secure Management, administrators can define each user's privileges for managing both local and remote adapters. When running in Secure Management mode, users must log in with their user name and password to run the OneCommand Manager application.
PAGE 297
1. Introduction OneCommand Manager Secure Management Remote management operations between two machines is allowed or denied depending on the OneCommand Manager secure management status of the machines, and the domains to which the machines belong. The following tables list the behavior (assuming appropriate user credentials are used).
PAGE 298
1. Introduction OneCommand Manager Secure Management by typing “getent group” from the shell command line. If the four OneCommand Manager group names are listed with their member users, the machine is ready to use OneCommand Manager secure management. Secure Management Installation The enabling or disabling of the Secure Management feature is specified at OneCommand Manager installation time. This can be done either interactively or by using dedicated install switches on Windows, Linux, and Solaris.
PAGE 299
1. Introduction OneCommand Manager Secure Management Using OneCommand Manager with Secure Management Enabled To run the OneCommand Manager CLI application when Secure Management is enabled, you must include your user name and password each time you type a command. For example: Secure Management disabled: hbacmd Secure Management enabled: hbacmd User names and passwords are used to authenticate the commands.
PAGE 300
2. Installing and Uninstalling the CLI Linux 2. Installing and Uninstalling the CLI This chapter details prerequisites and procedures for installing and uninstalling the OneCommand Manager CLI in the following operating systems: Linux, Solaris, VMware ESXi, and Windows. It also describes the Secure Management capability and the procedure for starting and stopping daemon processes.
PAGE 301
2. Installing and Uninstalling the CLI Linux libhbaapi Library The inbox libhbaapi library is required on RHEL 5, RHEL 6, and SLES 11.     For i386 RHEL 5 and RHEL 6, use the 32bit libhbaapi RPM. For x86_64 RHEL 5 and RHEL 6, use the 64bit libhbaapi RPM. For PPC RHEL 5 use the 32bit libhbaapi RPM. For PPC RHEL 6 use the 64bit libhbaapi RPM. For existing systems, before installing the OneCommand Manager CLI, download the appropriate Linux driver from the Emulex website, and install it.
PAGE 302
2. Installing and Uninstalling the CLI Linux 6. When prompted, choose whether or not to enable Secure Management for OneCommand: Do you want to enable Secure Management feature for OneCommand? (s/u) Enter 's' to select secure management. (LDAP/NIS OCM group configuration required) Enter 'u' to run without secure management (default). Enter the letter 's' or 'u'.
PAGE 303
2. Installing and Uninstalling the CLI Linux Performing a Clean Install (Removing Existing Settings) 1. Uninstall the existing OneCommand Manager CLI using the uninstall script included in the tar file or in /usr/sbin/ocmanager/scripts directory. Your configuration files are backed up by rpm with an “.rpmsave” extension. Note: If an HBAnyware CLI or enterprise kit is installed, follow the procedure for “Uninstalling Older HBAnyware Kits in Linux” on page 303. 2.
PAGE 304
2. Installing and Uninstalling the CLI Solaris e. Run the uninstall script with the ssc parameter specified. Type ./uninstall ssc 3. Uninstall the HBAnyware utility and the Application Helper module: a. Log on as “root”. b. Change to the directory containing the tar file. c. Extract the tar file using the tar -xvf command. d. Change to the newly created directory. e. Uninstall any previously installed versions. Type .
PAGE 305
2. Installing and Uninstalling the CLI VMware ESXi If any of the following are already present on the system, the install script attempts to remove them first: HBAnyware utility  OneCommand Manager core kit  OneCommand Manager application enterprise kit  Solaris driver utilities 5. When prompted, choose whether or not to enable Secure Management for OneCommand:  Do you want to enable Secure Management feature for OneCommand? (s/u) Enter 's' to select secure management.
PAGE 306
2. Installing and Uninstalling the CLI Windows The Emulex CIM Provider is available as an offline bundle in ESXi platforms. VMware recommends using the offline bundle to update software on VMware platforms. For more information about the ESXi Patch Management activities, see the VMware website. To install the Emulex CIM Provider in a VMware ESXi hypervisor environment, use the esxli command line utility and perform the following steps: 1. Copy the CIM provider zip file to /var/log/vmware. 2.
PAGE 307
2. Installing and Uninstalling the CLI Windows 2. Use the following syntax for the installation executable file: elxocmcore-windows--.exe
PAGE 308
2. Installing and Uninstalling the CLI Windows   excl – This optional switch allows the non-management-host user to select whether the OneCommand Manager application will process requests exclusively from the Management Host specified by the MHost switch. This option is only accepted if accompanied by a valid MHost value; otherwise an error message appears. If this switch is not specified, the default value of 0 will be used.
PAGE 309
2. Installing and Uninstalling the CLI Starting and Stopping Daemon Processes Starting and Stopping Daemon Processes Linux and Solaris On Linux and Solaris machines, you can stop and start the OneCommand Manager daemon processes using the “stop_ocmanager” and “start_ocmanager” scripts respectively.
PAGE 310
3. Updating to the OneCommand Manager Application Enterprise Kit Linux 3. Updating to the OneCommand Manager Application Enterprise Kit Note: The full-featured OneCommand Manager application enterprise kit is not supported on Citrix XenServer 5.6 SP2, Citrix XenServer 6.0, or VMware ESXi server. This chapter details procedures for updating the OneCommand Manager CLI to the OneCommand Manager application enterprise kit in Linux, Solaris, and Windows operating systems.
PAGE 311
3. Updating to the OneCommand Manager Application Enterprise Kit Windows Windows To update from the OneCommand Manager CLI to the full-featured OneCommand Manager application enterprise kit in Windows: 1. From the desktop, run the “elxocm-windows--.exe” file that contains the full application kit. Running this executable file removes the OneCommand Manager CLI and installs a full-featured version of the OneCommand Manager application that includes the CLI and the GUI.
PAGE 312
4. CLI Client Command Usage Overview 4. CLI Client Command Usage Overview The CLI Client component of the OneCommand Manager application provides access to the capabilities of the Remote Management library or the CIM interface from a console command prompt to get the management information. The CLI Client is intended for use in scripted operations from within shell scripts or batch files. The CLI Client is a console application named HbaCmd.
PAGE 313
4. CLI Client Command Usage HbaCmd Syntax Usage HbaCmd Syntax Usage The following syntax rules and usage apply to the HbaCmd application:     Parameters denoted within angle brackets < > are required. Parameters denoted within square brackets [ ] are optional. For Linux and Solaris, (which are case-sensitive), program names must be in lowercase letters, therefore, the command line must begin with “hbacmd” (rather than “HbaCmd”).
PAGE 314
4. CLI Client Command Usage Secure Management CLI Interface Also, for some implementations, it is possible to have multiple NIC ports with the same current MAC addresses, but with unique permanent MAC addresses. Therefore, to ensure that the OneCommand Manager can access the correct port, only the permanent MAC address is supported. Note that both the permanent MAC address and the current MAC address are displayed by using the ListHBAs command. See “ListHBAs” on page 403.
PAGE 315
4. CLI Client Command Usage CIM Interface CIM Interface Note: In Linux and Solaris, you cannot use HbaCmd as a CIM client. Device Management Using the CIM Interface VMware on the hypervisor-based ESXi platforms use the CIM as the only standard management mechanism for device management. For VMware ESXi hosts, you can manage adapters using the OneCommand Manager application on Windows, but you must install and use the appropriate Emulex CIM Provider.
PAGE 316
4. CLI Client Command Usage CIM Interface  Add the host IP address with CIM credentials using the AddHost command. For example: hbacmd [u=userid] [p=password] [n=namespace] AddHost Default CIM Credentials If you specify the command with the CIM method “m=cim” without specifying the CIM credentials (userid, password, or namespace), the default value for the missing CIM credential is obtained in the following order: 1. The information entered using the addhost command is looked up. 2.
PAGE 317
4. CLI Client Command Usage CIM Interface Mfg: Emulex Corporation Serial No.: BG73539764 Port Number: n/a Mode: Initiator Discovery: cim C:\Program Files\Emulex\Util\OCManager>hbacmd h=10.192.113.
PAGE 318
4. CLI Client Command Usage Commands Supported in Target-Mode Ports CLI Client Commands Supported in CIM Interface For a list of HbaCmd commands supported through the CIM interface see Table 5-1, CLI Client Command Reference, on page 322.
PAGE 319
4. CLI Client Command Usage Unsupported Commands per Operating System Unsupported Commands per Operating System For a list of all the supported commands, see Table 5-1, CLI Client Command Reference, on page 322.
PAGE 320
4.
PAGE 321
4. CLI Client Command Usage Unsupported Commands per Operating System               ListVFunctions ListVMs ListVPorts PersistentBinding RemoveAllPersistentBinding RemovePersistentBinding RescanLuns SetAuthConfig SetBindingSupport SetCimCred SetLunMask SetPersistentBinding SetPassword VportTargets Windows Windows does not support the following CLI commands:   SetDumpDirectory ListVMs OneCommand Manager Command Line Interface Version 10.2 User Manual P010067-01A Rev.
PAGE 322
5. CLI Client Command Descriptions 5. CLI Client Command Descriptions A check mark () designates a supported command for a particular operating system and CIM interface. N/A indicates “not applicable”.
PAGE 323
5.
PAGE 324
5.
PAGE 325
5.
PAGE 326
5.
PAGE 327
5. CLI Client Command Descriptions Help Help The Help command displays command information for the HbaCmd application. Without using its optional parameters, the Help command lists all the commands in their respective groups. Using the optional parameter, GroupName, it lists the commands in a group. Using the optional parameter, CmdName, it shows the details for a specific command.
PAGE 328
5.
PAGE 329
5.
PAGE 330
5. CLI Client Command Descriptions Adapter License Management Commands 2. For protocol priorites (fcoepriority, iscsipriority, rocepriority), the valid range is 0 to 7. Only one priority can be specified for each invocation of this this command and must be for a protocol running on the port. If more than one protocol priority can be set, they should be unique values. 3.
PAGE 331
5. CLI Client Command Descriptions Adapter License Management Commands Examples For non-VMware ESXi hosts: hbacmd InstallAdapterLicense 00-12-34-56-78-9A K:\lf1324.lic For VMware ESXi hosts: hbacmd h= m=cim u=root p= n= InstallAdapterLicense 00-12-34-56-78-9A K:\lf1324.lic ShowAdapterLicenseFeatures This command displays the list of licensed and licensable features, as well as, features that are already licensed.
PAGE 332
5. CLI Client Command Descriptions Attributes Commands Parameters WWPN The WWPN of an FCoE port. MAC The MAC address of a NIC or iSCSI port. Examples For non-VMware ESXi hosts: hbacmd ShowLicenseAdapterID 00-12-34-56-78-9A For VMware ESXi hosts: hbacmd h= m=cim u=root p= n= ShowLicenseAdapterID 00-12-34-56-78-9A Attributes Commands HbaAttributes This command shows a list of all adapter attributes for all ports on the adapter.
PAGE 333
5. CLI Client Command Descriptions Attributes Commands Parameters h The IP address of the host. WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. PortStatistics This command shows all port statistics for the adapter. The type of information listed may vary according to the adapter model. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax PortStatistics Parameters WWPN The WWPN of an FC or FCoE port.
PAGE 334
5. CLI Client Command Descriptions Attributes Commands to a range of values for auto-negotiation with the switch, for example 10Gb/1Gb/100Mb. There are three values that can be configured - port speed mode, speed value(s), and the DAC cable length. The configurable port speeds are based upon the port module type and the mode defined by port speed Mode parameter. For the “Default” port speed Mode, the speed setting is not required.
PAGE 335
5. CLI Client Command Descriptions Attributes Commands Length The length of the direct attach copper (DAC) cable in meters. Valid values are 0–10. A length value of 0 indicates an optical cable. A Length value is required when using a 10Gb SFP and QSFP transceiver interface type.
PAGE 336
5. CLI Client Command Descriptions Authentication Commands Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. PortEnabled The port-enabled state: 0 = Disabled 1 = Enabled Authentication Commands These commands are used to configure a DHCHAP connection between an FC port and a switch port. Note: Authentication commands are supported on FC adapter ports only. These commands are not available on OneConnect or LPe16000 family adapters.
PAGE 337
5. CLI Client Command Descriptions Authentication Commands Parameters WWPN1 The WWPN of an FC port. WWPN2 Use “ff:ff:ff:ff:ff:ff:ff:ff” for a switch or use the WWPN for a target. PasswordType 1 = ASCII 2 = Hex (binary) 3 = Password not yet defined The current password value. Password GetAuthConfig This command retrieves the authentication configuration for the adapter. Supported By Linux, Solaris, and Windows Syntax hbacmd GetAuthConfig Parameters WWPN1 The WWPN of an FC port.
PAGE 338
5. CLI Client Command Descriptions Authentication Commands InitiateAuth This command initiates the authentication configuration on the adapter. Supported By Linux, Solaris, and Windows Syntax InitiateAuth Parameters WWPN1 The WWPN of an FC port. WWPN2 Use “ff:ff:ff:ff:ff:ff:ff:ff” for a switch or use the WWPN for a target. SetAuthConfig This command sets the authentication configuration for the adapter.
PAGE 339
5.
PAGE 340
5. CLI Client Command Descriptions Boot Commands Boot Commands EnableBootCode This command is used to perform either of the following:   Enable or disable network boot for NIC ports. If network boot is being enabled, it is necessary to select the specific network boot type. The supported network boot types are PXE and iBFT. Note that iBFT is not supported on all NIC adapter types. Enable/disable the boot code for an FC adapter port.
PAGE 341
5. CLI Client Command Descriptions Boot Commands GetBootParams This command shows the FC boot parameters. If any arguments are missing or invalid, a suitable error is reported. If all arguments are correct, the data is displayed in tabular form. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetBootParams Parameters WWPN The WWPN of an FC port. Type X86, OpenBoot, or UEFI. SetBootParam This command changes the FC boot parameters.
PAGE 342
5. CLI Client Command Descriptions Channel Management Commands Channel Management Commands These commands enable and disable channel management and set channel properties for UCNAs. Channel management is not supported on LPe16202 adapters. Each port on each adapter’s physical port can 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.
PAGE 343
5. CLI Client Command Descriptions Channel Management Commands Parameters MAC MAC address of any NIC or iSCSI function on an adapter port. WWPN WWPN of an FCoE function on an adapter port.
PAGE 344
5.
PAGE 345
5. CLI Client Command Descriptions Channel Management Commands CMMode This command enables or disables channel management mode on OCe10100- and OCe11100-series adapters. For UMC configurations, the UMCEnable command can still be used to enable UMC only. This command also sets the channel management type at the adapter level. A system reboot is required for the change take effect.
PAGE 346
5. CLI Client Command Descriptions Channel Management Commands The number of channels, the number of channels that need to be specified, and the number of bandwidth combinations that need to be specified depend upon the adapter model. See “CMGetParams” on page 342 to determine how many bandwidths need to be specified for a port by looking at the number of functions indicated in the “Func #” column of the output.
PAGE 347
5. CLI Client Command Descriptions Channel Management Commands Configured mode: UMC Available modes: UMC Func# Type MAC Address LPVID Min BW Max BW ----- ----- ----------------- ----- ------ ------ 0 NIC 00-00-c9-12-34-56 2 25 50 2 iSCSI 00-00-c9-12-34-57 n/a 50 100 4 NIC 00-00-c9-12-34-58 3 0 0 6 NIC 00-00-c9-12-34-59 4 25 50 CMSetLPVID This command sets the LPVID values for the UMC and SIMode NIC channels.
PAGE 348
5. CLI Client Command Descriptions DCB Commands  If channel management is disabled when this command is executed, an error message is displayed. Examples 4 NIC Channels >>hbacmd CMSetLPVID 00-00-c9-12-34-56 1001 1002 1003 1004 8 Channels, Storage on 2nd channel >hbacmd CMSetLPVID 00-00-c9-55-43-21 1001 0 1002 1003 1004 1005 1006 1007 DCB Commands This command shows the DCB and LLDP parameters for iSCSI, FCoE, and NIC adapter ports.
PAGE 349
5. CLI Client Command Descriptions DCB Commands GetPGInfo This command shows the ETS priority group bandwidth percentages for the port of a OneConnect adapter. Additionally, this command displays the number of priority groups supported by an adapter. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetPGInfo Parameters WWPN The WWPN address of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. Example hbacmd h=10.192.203.
PAGE 350
5. CLI Client Command Descriptions DCB Commands SetDCBParam This command configures the DCB and LLDP settings on a OneConnect adapter port. Use the GetDCBParams command to obtain valid parameter names for use in this command. Notes:    You cannot set DCBX mode. If you attempt to specify a “dcbxmode” parameter, an error message is displayed. RoCE is only available on the OCe140000-series of adapters. RoCE is only available on Windows operating systems.
PAGE 351
5. CLI Client Command Descriptions DCB Commands RoCEPriority This parameter is applicable for ports running RoCE only. A single priority must be specified. The range of valid values is 0-7. Note: Only one priority can be specified for each invocation of this command and must be for a protocol running on the port. If more than one protocol priority can be set, they should be unique values. PFCPriority A list of comma-separated values where multiple PFC priorities are supported.
PAGE 352
5. CLI Client Command Descriptions DCB Commands Example hbacmd h=10.190.103.165 m=cim u=root p=Host001 n=root/emulex SetDCBParam 00-00-c9-3c-f7-88 fcoepriority 3 SetDCBPriority This command sets the PFC priorities and the ETS priority groups priorities. The values must be set according to the following rules:    The priorities range from 0 to 7. A priority (0-7) must exist in only one priority group. All priorities must appear once in any of the eight (PG0-PG7) priority groups or if available, PG15.
PAGE 353
5. CLI Client Command Descriptions Diagnostic Commands Parameters WWPN The WWPN of an FCoE function on a port. MAC The MAC address of a function on a port. PFC The PFC priority that is a comma-separated list of up to eight values, ranging from 0–7. PG0-PG7 Priority group membership that is a comma-separated list of priorities ranging from 0–7. Each set of priorities for a group must be separated by a space. All priorities (0–7) must be assigned to some PGID.
PAGE 354
5. CLI Client Command Descriptions Diagnostic Commands  When using D_Port in a boot from SAN configuration, the configuration must have redundant paths to the boot LUN and only one of the redundant adapter ports should be set to D_Port. Supported By Linux, VMware ESXi, and Windows Syntax DPortTest Parameters The WWPN of the FC function on the adapter.
PAGE 355
5. CLI Client Command Descriptions Diagnostic Commands Test Failures >hbacmd DPortTest 10:00:00:00:c9:d1:a2:d0 Running D_Port Tests. Please wait. Polling for results.................................
PAGE 356
5. CLI Client Command Descriptions Diagnostic Commands EchoTest This command runs the echo test on FC adapters. Notes   This command is only supported on FC and FCoE ports. The EchoTest command fails if the target WWPN does not support the ECHO ELS command. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax EchoTest Parameters WWPN Source The WWPN of the originating adapter.
PAGE 357
5. CLI Client Command Descriptions Diagnostic Commands GetXcvrData This command shows transceiver data for a port on an adapter. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetXcvrData [Type] Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. Type The type of SFP data to display:   1 = Formatted data 2 = Raw data Example C:\Program Files\emulex\Util\OCManager>hbacmd h=10.192.203.
PAGE 358
5. CLI Client Command Descriptions Diagnostic Commands LoopBackTest This command runs one of the loopback tests available on the adapter port specified by the WWPN or MAC address. Notes:   PHY diagnostics are not supported on mezzanine cards and blade network daughter cards because they do not contain PHYs. The external loopback test is not supported for OCe11102-xT adapters.
PAGE 359
5. CLI Client Command Descriptions Diagnostic Commands LoopMap Note: Supported for FC ports only. This command shows the arbitrated loop map data. Supported By Linux, Solaris, and Windows Syntax LoopMap Parameters WWPN The WWPN of the FC port. PciData This command shows the PCI configuration data (if available). The PCI registers displayed are specific to the function referenced in the OneCommand Manager CLI.
PAGE 360
5.
PAGE 361
5. CLI Client Command Descriptions Diagnostic Commands SetCableNVP Note: This command supports only OCe11100-series adapters and LPe16202 adapters. This command sets the NVP, required for the TDRTest command, for the cable that connects to the physical port associated with the WWPN or MAC. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax SetCableNVP Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port.
PAGE 362
5. CLI Client Command Descriptions Driver Parameter Commands Example hbacmd TDRTest The example output: Pair A: OK. Cable Length Estimation: 50m. Pair B: OK. Cable Length Estimation: invalid. Pair C: Open. Distance to Fault: 38m. Pair D: Shorted. Distance to Fault: 36m. Wakeup Note: Not supported for OneConnect and LPe16200-series adapters. This command shows the firmware's wakeup parameters for the adapter.
PAGE 363
5. CLI Client Command Descriptions Driver Parameter Commands DriverConfig This command sets all driver parameters to the values in the .dpv file type. The .dpv file’s driver type must match the driver type of the host platform adapter. Supported By Linux, VMware ESXi, and Windows Syntax DriverConfig Parameters WWPN The WWPN of an FC or FCoE port. FileName The name of the .dpv file, which is stored in the Emulex Repository directory.
PAGE 364
5. CLI Client Command Descriptions Driver Parameter Commands SaveConfig This command saves the specified adapter’s driver parameters to a file. The resulting file contains a list of driver parameter definitions in ASCII file format with definitions delimited by a comma. Each definition has the following syntax: = The command saves either the values of the global set, or those specific to the adapter in the Emulex Repository directory.
PAGE 365
5. CLI Client Command Descriptions Dump Commands Example To enable dynamic target mode: hbacmd SetDriverParam 10:00:00:00:c9:ff:ff:ff L P enable-dtm 1 To disable dynamic target mode, set the flag to 0. SetDriverParamDefaults This command changes all values to the default for the adapter(s). Supported By Linux, VMware ESXi, and Windows Syntax SetDriverParamDefaults Parameters WWPN The WWPN of an FC or FCoE port. Flag1 L = Make change local for this adapter only.
PAGE 366
5. CLI Client Command Descriptions Dump Commands DeleteDumpFiles This command deletes all diagnostic dump files for the adapter. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax DeleteDumpFiles Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. Dump This command creates a diagnostic dump file in the HbaCmd dump file directory. Note: In some cases, a core dump can be performed on an inoperative OneConnect adapter.
PAGE 367
5. CLI Client Command Descriptions Dump Commands GetDumpDirectory This command shows the dump file directory for the adapters in the host. Notes   The dump directory can be set on VMware ESXi hosts only. The dump directory applies to all adapters in the server. There is not a separate dump directory for each adapter. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetDumpDirectory Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of the NIC or iSCSI port.
PAGE 368
5. CLI Client Command Descriptions Dump Commands Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. filename The name of the dump file to be copied from the remote host. Example hbacmd h=10.192.193.154 m=cim u=root p=Swamiji001 n=root/emulex GetDumpFile BG-HBANYWARE-15_10000000c97d1314_20100120-032820421.dmp GetDumpFileNames This command gets the names of the files in the remote host’s dump directory.
PAGE 369
5. CLI Client Command Descriptions Dump Commands SetDumpDirectory This command sets the dump directory for the VMware ESXi hosts only. Supported By VMware ESXi To use the SetDumpDirectory command, you must have a directory (which must be a “Storage” partition) mapped under /vmfs/volumes where the files will be dumped. This directory points to the internal hard disk or an external storage area and can also be mapped using the vSphere Client utility from VMware.
PAGE 370
5. CLI Client Command Descriptions FCoE Commands Syntax SetRetentionCount Parameters WWPN The WWPN of an FC or FCoE port. MAC The MAC address of a NIC or iSCSI port. Value The number of dump files to retain. Example hbacmd h=10.192.193.154 m=cim u=root p=Swamiji001 n=root/emulex SetRetentionCount 00-00-c9-93-2f-9f 6 FCoE Commands Note: These commands are supported only on OneConnect and LPe16202 FCoE ports.
PAGE 371
5. CLI Client Command Descriptions FCoE Commands Parameters WWPN The WWPN of an FCoE port. Example hbacmd GetFIPParams 10:00:00:00:c9:5b:3a:6d SetFIPParam This command sets the FIP parameters of the adapter in FCoE mode. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax SetFIPParam Parameters WWPN The WWPN of an FCoE port.
PAGE 372
5. CLI Client Command Descriptions iSCSI Commands iSCSI Commands The commands in this section support the iSCSI interface in the OCM CLI. Note: iSCSI commands are supported only on OneConnect iSCSI ports. Note: Only OCe14000-series adapters support IPv6 addresses. The MAC address of the iSCSI port must be passed to each command as the first argument. Some commands require values to be set in a format similar to: “option_name=value”.
PAGE 373
5. CLI Client Command Descriptions iSCSI Commands Parameters MAC_Address The MAC address of the iSCSI port. Dest_MAC_Address The destination MAC address to add to the ARP table. Dest_IP_Address The destination IP address to add to the ARP table. AddiSNSServer This command adds a new iSNS server to the existing set of iSNS servers. It accepts either an IPv4 or IPv6 server addresses. Note: For OCe11000-series and OCe11100-series adapters, only one iSNS server can be configured.
PAGE 374
5. CLI Client Command Descriptions iSCSI Commands AddTarget This command adds a target to the list of targets seen by the initiator and logs into the target once it has been successfully created. This command requires that you specify a valid IPv4 or IPv6 target IP , port number , and iSCSI name . If you do not specify the remaining options, these options are set to their default values.
PAGE 375
5. CLI Client Command Descriptions iSCSI Commands This optional parameter specifies whether the added target is a boot device: Boot 0 = Added target is not a boot device 1 = Added target is a boot device This optional parameter specifies whether to log in to the target after it has been added: Login 0 = Do not log in to the target 1 = Specify log in to the target If the Login parameter is omitted, the default is 1.
PAGE 376
5. CLI Client Command Descriptions iSCSI Commands Syntax AddTargetPortal [ImmediateData=<0|1>] [HeaderDigest=<0|1>] [DataDigest=<0|1>] [Auth=<0|1|2> "TgtCHAPName" "TgtSecret" "InitCHAPName" "InitSecret"] Parameters MAC_Address The MAC address of an iSCSI port. Target_IP IP address of the target portal. You can specify an IPv4 or IPv6 IP address. Port Port number of the target portal (value: 1024-65535).
PAGE 377
5. CLI Client Command Descriptions iSCSI Commands DelARPTableEntry This command removes an ARP table entry. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax DelARPTableEntry Parameters MAC_Address The MAC address of an iSCSI port. Dest_MAC_Address The destination MAC address to remove from the ARP table. Dest_IP_Address The destination IP address to remove from the ARP table.
PAGE 378
5. CLI Client Command Descriptions iSCSI Commands Parameters MAC_Address MAC address of an iSCSI port. Dest_IP_Address Destination IP address to delete from the route table. Subnet_Mask Subnet Mask to delete from the route table. Gateway Gateway to delete from the route table. DiscoveriSNSServer This command discovers an iSNS server address through DHCP. If the DHCP server returns an iSNS server address, it replaces the configured iSNS server and can be viewed using the ShowiSNSServer command.
PAGE 379
5. CLI Client Command Descriptions iSCSI Commands Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetInitiatorProperties Parameters MAC_Address The MAC address of an iSCSI port. GetiSCSILuns This command shows all the LUNs and their information for a specified target. The command gathers the information from the iSCSI target indicated by the parameter.
PAGE 380
5. CLI Client Command Descriptions iSCSI Commands GetNetworkConfiguration This command lists a port’s TCP/IP information for IPv4 and IPv6 protocols. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetNetworkConfiguration Parameters MAC_Address The MAC address of an iSCSI port. Example TCP/IP Configuration for 00-00-c9-ad-ad-b1: VLAN Enabled: No VLAN ID: 0 Priority: 0 IPv4 Configuration: DHCP Enabled: Yes IP Address: 10.192.81.204 Subnet Mask: 255.255.248.
PAGE 381
5. CLI Client Command Descriptions iSCSI Commands Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetSessionInfo > Parameters The MAC address of an iSCSI port. MAC_Address iscsi_target_name Target’s iSCSI name enclosed in quotes (string length: 11–255). TSIH TSIH value of the session (value: 1–65535). ISID_Qual ISID qualifier of the session (value: 0–65535). Target_IP The Target's IP address.
PAGE 382
5. CLI Client Command Descriptions iSCSI Commands Added target iqn.2006-01.com.openfiler:target122-000.on.port.00-00-c9-2f-45-1b Added target iqn.2006-01.com.openfiler:target122-001.on.port.00-00-c9-2f-45-1b iSCSIPing This command issues ICMP echo requests to a target. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax iSCSIPing Parameters MAC_Address The MAC address of an iSCSI port. IP_Address IP address of target to send ICMP echo request.
PAGE 383
5. CLI Client Command Descriptions iSCSI Commands Parameters MAC_Address The MAC address of an iSCSI port. iscsi_target_name Target’s iSCSI name enclosed in quotes. The string length is 11–255. RemoveTargetPortal This command removes the SendTarget Portal containing the IPv4 or IPv6 target IP and the port from the list of portals for the specified initiator.
PAGE 384
5. CLI Client Command Descriptions iSCSI Commands TSIH TSIH value of the session. The possible values are 1–65535. ISID_Qual Target_IP ISID qualifier of the session. The possible values are 0–65535. You can specify an IPv4 or IPv6 Target IP address that the target is using depending on the adapter type. 0|1 Specifies the state of the BootProperty for the target: 0 = Disabled 1 = Enabled SetInitiatorProperties This command sets the initiator properties for the specified port.
PAGE 385
5. CLI Client Command Descriptions iSCSI Commands Parameters MAC_Address The MAC address of an iSCSI port. Initiator_Name Initiator iSCSI name enclosed in quotes (string length: 1–224). Initiator_Alias Initiator iSCSI alias enclosed in quotes (string length: 0–32).
PAGE 386
5. CLI Client Command Descriptions iSCSI Commands Syntax SetNetworkConfiguration VLAN_Enabled=<0|1>[VLAN_ID=<0-4094> Priority=<0-7>]DHCP=<0|1> [ [IPv4_Gateway]] [AA=<0|1> [ [RA1=IPv6_Address RA2=IPv6_Address] [GW6=IPv6_Address]]] Parameters MAC_Address The MAC address of an iSCSI port. VLAN_ENABLED 0 = Disabled 1 = Enabled VLAN_ID VLAN ID of the interface. The possible values are 0–4095. Note: This value is specified only when VLAN is enabled.
PAGE 387
5. CLI Client Command Descriptions iSCSI Commands Notes    VLAN_ID and Priority are required only if VLAN_ENABLED is enabled; otherwise, these values should be omitted. IPv4_Address and Subnet are required only if DHCP is disabled; otherwise these values should be omitted. At a minimum, the DHCP or AA parameter must be specified and, if required, their associated parameters as well. If either the DHCP or AA parameter is not specified an error results.
PAGE 388
5. CLI Client Command Descriptions iSCSI Commands DataDigest 0 = None (default) 1 = CRC32C Auth 0 = None (default) 1 = One-Way CHAP 2 = Mutual CHAP TgtCHAPNam Target CHAP name enclosed in quotes (string length: 1–256). TgtSecret Target Secret enclosed in quotes (string length: 12–16). InitCHAPName Initiator CHAP name enclosed in quotes (string length: 1–256). InitSecret Initiator Secret enclosed in quotes (string length: 12–16). SetTargetProperties This command sets the ETO value of a target.
PAGE 389
5. CLI Client Command Descriptions iSCSI Commands  If you set the authentication method to “One-Way CHAP” (=1), you must also specify the “Target CHAP Name” and “Target Secret.” For example: hbacmd SetTPLoginProperties 00-11-22-33-44-55 10.192.1.1 5050 Auth=1 "TgtChapName" "TargetSecret1"  If you set the authentication method to “Mutual CHAP” (=2), you must specify all four values. For example: hbacmd SetTPLoginProperties 00-11-22-33-44-55 10.192.1.
PAGE 390
5. CLI Client Command Descriptions iSCSI Commands Syntax ShowARPTable Parameters MAC_Address The MAC address of an iSCSI port. ShowiSNSServer This command shows the currently configured Internet Storage Name Server. It shows up to four iSNS servers if you are using the OCe14000 family of adapters and includes IPv6 addresses, as well as, IPv4 addresses. This command also indicates whether or not iSNS discovery is enabled.
PAGE 391
5. CLI Client Command Descriptions iSCSI Commands ShowTarget This command shows the properties for a specified target. If you do not specify the iSCSI target name , all targets and their associated properties return. If you specify in place of the , all targets are refreshed before returning the information. If you do not provide a or value, only the targets from the last refresh are displayed.
PAGE 392
5. CLI Client Command Descriptions iSCSI Commands TargetLogin This command logs in to a target. The iSCSI target name is the only mandatory option. The and information are optional and if they are not provided a default target portal is used. If you do not specify the remaining options, these options are set to their default values. When you set the authentication method to a value other than 0, you must set additional parameters.
PAGE 393
5. CLI Client Command Descriptions iSCSI Commands TgtCHAPName The Target CHAP name enclosed in quotes (string length: 1–255 characters). Note: The Target CHAP name is required it you set Auth to 1 or 2. TgtSecret The Target Secret enclosed in quotes (string length: 12–16 characters). Note: The Target CHAP name is required it you set Auth to 1 or 2. InitCHAPName The Initiator CHAP name enclosed in quotes (string length: 1–255 characters). Note: The Target CHAP name is required it you set Auth to 2.
PAGE 394
5. CLI Client Command Descriptions LUN Masking Commands UpdateiSNSServer This command updates a configured iSNS server and accepts IPv4 or IPv6 iSNS server addresses. This command requires the server IP and port number of the iSNS server to be available to respond to the iSNS requests. If a single iSNS server is configured, this command replaces the single iSNS server IP address with a new IP address. If no iSNS server is configured, this command adds a new iSNS server.
PAGE 395
5. CLI Client Command Descriptions LUN Masking Commands Parameters HBA WWPN The WWPN of an FC or FCoE port on the adapter. Target WWPN The WWPN of the target. Option 0 = Get information from the driver 1 = Get information from the configuration GetLunUnMaskByHBA This command queries for the presence of any unmasked LUNs by adapter. Supported By Solaris and Windows Syntax GetLunUnMaskByHBA
PAGE 396
5. CLI Client Command Descriptions LUN ExpressLane Commands Syntax RescanLuns Parameters HBA WWPN The WWPN of an FC or FCoE port on the adapter. Target WWPN The WWPN of the target. SetLunMask This command masks the specified LUNs. Supported By Solaris and Windows Syntax SetLunMask
PAGE 397
5. CLI Client Command Descriptions LUN ExpressLane Commands Notes: For Linux and VMware operating systems, only ExpressLane-enabled LUNs are shown by this command. LUNS without ExpressLane-enabled support are not shown. ExpressLane LUNs are supported on 16 GB FC ports only.   Syntax GetExpressLaneLunList [vport=]
PAGE 398
5. CLI Client Command Descriptions Miscellaneous Commands Parameters WWPN The WWPN of the FC/FCoE function connected to the target or physical WWPN if virtual ports are selected. vPORT WWPN The WWPN of an optional vPort allowing you to set the state of a vPort LUN. Target WWPN The WWPN of the target LUNs. LUN The LUN number on which to set the ExpressLane status. Note: Obtain the LUN number from the output of the GetExpressLaneLunList command under the “OS LUN” column.
PAGE 399
5. CLI Client Command Descriptions Miscellaneous Commands Parameters host_address The IP address (using the IPv4 or IPv6 format) or the host name. IP_Address The IP address of the host. CnaClearEventLog Note: Supported for OneConnect and LPe16202 adapters only. This command clears the event log specified by the WWPN or MAC address. Supported By Linux, VMware ESXi, and Windows Syntax CnaClearEventLog Parameters WWPN The WWPN of an FCoE port. MAC The MAC address of a NIC or iSCSI port.
PAGE 400
5. CLI Client Command Descriptions Miscellaneous Commands Download Loads the firmware image to the port specified by the WWPN or MAC address. Notes   For 16-Gb HBA firmware downloads, the OneCommand Manager application only accepts “.grp” files. For OneConnect and 16-Gb HBAs, while the WWPN or MAC address is used to identify the adapter, the updated firmware applies to all ports on that adapter.
PAGE 401
5. CLI Client Command Descriptions Miscellaneous Commands Parameters format An optional parameter that specifies the format of the adapter information:   csv xml Note: Leaving the format blank shows the data in xml format (default). FecEnable This command enables or disables FEC on LPe16000-series FC adapters. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax FecEnable WWPN <0|1> Parameters WWPN The WWPN of the FC port.
PAGE 402
5. CLI Client Command Descriptions Miscellaneous Commands Syntax GetElxSecInfo Parameters None GetQoSInfo This command shows the QoS information for a specified NIC port if multichannel support is enabled. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetQoSInfo Parameters MAC The MAC address of a NIC port. Example hbacmd GetQoSInfo 00-00-c9-93-20f-d6 GetVPD This command shows the port’s VPD.
PAGE 403
5. CLI Client Command Descriptions Miscellaneous Commands ListHBAs This command shows a list of the manageable Emulex adapters found by local and remote out-of-band (TCP/IP) discovery. For a NIC-only or iSCSI adapter, the MAC address is displayed rather than the port WWN. The node WWN and fabric WWN are not displayed. The type of information listed may vary according to the adapter model.
PAGE 404
5. CLI Client Command Descriptions Miscellaneous Commands Parameters host_address The host to remove. IP_Address The IP address of the host to remove. Reset This 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 for FC and FCoE ports only.
PAGE 405
5. CLI Client Command Descriptions Miscellaneous Commands Parameters username Login User ID of the VMware ESXi. password The login password of the VMware ESXi. namespace The namespace where the Emulex provider is registered in the SFCB CIMOM of VMware ESXi, specifically “root/emulex”. portnum The port number of the SFCB CIMOM listening to, that is, 5988 (HTTP) or 5989 (HTTPS). SetPfcThrottle This command returns the PFC throttle state as enabled or disabled.
PAGE 406
5. CLI Client Command Descriptions Miscellaneous Commands Supported By Linux, Solaris, VMware ESXi, and Windows Syntax SRIOVEnable <0|1> Parameters MAC The MAC address of a NIC port. 0|1 0 = Disables SR-IOV 1 = Enables SR-IOV Example The following command enables SR-IOV on NIC physical function with MAC address 00-00-c9-12-34-56: hbacmd SRIOVEnable 00-00-c9-12-34-56 1 TargetMapping This command shows a list of mapped targets and the LUNs for the port.
PAGE 407
5. CLI Client Command Descriptions Persistent Binding Commands Parameters MAC The MAC Address of any NIC on the physical port. 0|1 The VEPA state: 0 = Disabled 1 = Enabled Version This command shows the current version of the OneCommand Manager CLI Client. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax For the RM interface: hbacmd Version Note: The “h=” option (for specifying an optional IP address or host name) after “hbacmd” is not available for the Version command.
PAGE 408
5. CLI Client Command Descriptions Persistent Binding Commands In a remote environment, you can perform persistent bindings operations from a host running any operating system (including Linux or VMware ESXi), but only to a remote host that is running Windows or Solaris. For a binding to take effect immediately (that is, SetPersistentBinding parameter: Scope = I or B), the and parameters must match the SCSI bus and SCSI target to which the FC target is already automapped.
PAGE 409
5. CLI Client Command Descriptions Persistent Binding Commands BindingSupport This command shows the binding support for the adapter. Supported By Solaris and Windows Syntax BindingSupport Parameters WWPN The WWPN of an FC or FCoE port. Source C = Configuration support L = Live support PersistentBinding This command specifies which set of persistent binding information (configuration or live state) is requested.
PAGE 410
5. CLI Client Command Descriptions Persistent Binding Commands RemovePersistentBinding This command removes persistent binding between an FC target and a SCSI bus and target. The binding to be removed can be to a target WWPN, target WWNN, or target D_ID. Supported By Solaris and Windows Syntax RemovePersistentBinding Parameters WWPN The WWPN of an FC or FCoE port.
PAGE 411
5. CLI Client Command Descriptions Persistent Binding Commands BindFlag The type of binding support for the adapter: D = Binding by D_ID (not available for Windows driver) P = Binding by WWPN N = Binding by WWNN (not available for Windows driver) A = Binding by automap (not available for Windows driver) DA = Binding by D_ID and automap PA = Binding by WWPN and automap NA = Binding by WWNN and automap SetPersistentBinding This command sets a persistent binding between an FC target and a SCSI bus target.
PAGE 412
5. CLI Client Command Descriptions Personality Change Commands Personality Change Commands The OneCommand Manager application enables you to change the personality or protocol running on OneConnect adapters. When you change the personality of the adapter and reboot the host, the adapter starts running the new personality. The personalities that the OneConnect adapters currently run are NIC-only, NIC + FCoE, NIC + iSCSI, and NIC + RoCE for OCe14000-series adapters.
PAGE 413
5. CLI Client Command Descriptions Personality Change Commands Supported By Linux, Solaris, VMware ESXi, and Windows Syntax ChangePersonality [Profile_ID] Parameters WWPN The WWPN of an FCoE port. MAC The MAC address of a NIC, NIC/RoCE, or iSCSI port. type The personality type to which the adapter is being changed. The available values are shown when using the “ShowPersonalities” command. See “ShowPersonalities” on page 414.
PAGE 414
5. CLI Client Command Descriptions Personality Change Commands ShowPersonalities This command displays the list of single personalities available on an adapter. The personality type is displayed as either NIC, NIC + RoCE, iSCSI, or FCoE. Notes    If the active configurations are not single personality, the active personality indicators are not displayed. The available personalities are adapter dependent. RoCE is only available on Windows operating systems.
PAGE 415
5. CLI Client Command Descriptions Profile Management Commands Profile Management Commands GetAdapterPortConfig This command displays the active and reboot adapter port configurations of an OCe14000-series adapter. This includes the total number of ports, the maximum number of FCoE and iSCSI functions that can be defined, and whether mixed mode and concurrent mode storage are supported by the adapter.
PAGE 416
5.
PAGE 417
5. CLI Client Command Descriptions Profile Management Commands Reboot Configuration Profile ID : 23 MCType : None Port Assignments: Port 1 (p0): NIC,FCoE,None Port 2 (p1): NIC,FCoE,None Note: (pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI).
PAGE 418
5.
PAGE 419
5. CLI Client Command Descriptions Profile Management Commands Syntax ListProfiles Parameters MAC MAC address of any NIC, NIC+RoCE or iSCSI function on the adapter. WWPN WWPN of any FC/FCoE function on the adapter Example Note: Different adapter models will have a different set of profiles.
PAGE 420
5. CLI Client Command Descriptions Profile Management Commands 10.2 and later. If these conditions are not met, although you may configure all sixteen functions, only eight functions will be present and discovered by the OneCommand Manager application after a reboot. Notes:       RoCE is only available on Windows operating systems. SR-IOV is not supported with RoCE configurations. SR-IOV must be disabled on the adapter BIOS when NPar is used.
PAGE 421
5. CLI Client Command Descriptions Profile Management Commands :: f0[,f1[,...fM]] where: fcnCfg f0 1st function protocol on port (must be NIC or NIC+RoCE). f1 2nd function protocol on port (optional). fm Mth function protocol on port (optional). The number of functions per port, the value of “M”, are model and multichannel type specific. ProfileID This parameter is required when specifying a NIC only or NIC+RoCE personality. Otherwise this parameter must be omitted.
PAGE 422
5. CLI Client Command Descriptions Profile Management Commands          The number of functions (f) specified depends upon the adapter model and configuration type, for example, non-multichannel, multichannel, RoCE, and NPar. If an incorrect number of functions are specified, an error is generated. The pid=ProfileID option is required for NIC+RoCE configurations. If it specified and the profile does not work with the specified port functions, an error is generated.
PAGE 423
5. CLI Client Command Descriptions Profile Management Commands Profile ID : 37 MCType : None Port Assignments: Port 0: NIC,iSCSI Port 1: NIC,FCoE Port 2: NIC,iSCSI Port 3: NIC,FCOE Reboot Configuration Profile ID : 37 MCType : None Port Assignments: Port 0 (P0): NIC,iSCSI Port 1 (P1): NIC,FCoE Port 2 (P2): NIC,FCoE Port 3 (P3): NIC,None Note: (pN)labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE 1=NIC,iSCSI).
PAGE 424
5. CLI Client Command Descriptions Profile Management Commands MCType : None Port Assignments: Port 1 (p0): NIC,iSCSI,FCoE Port 2 (p1): NIC,FCoE,None Note: (pN)labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE 1=NIC,iSCSI).
PAGE 425
5. CLI Client Command Descriptions Profile Management Commands Multichannel Configurations Note: ARI must be available to support sixteen functions on an adapter. OCe14000-series adapters automatically support ARI. However, the system’s motherboard must support ARI, it must be enabled in the system BIOS, and the operating system must support ARI.
PAGE 426
5. CLI Client Command Descriptions Profile Management Commands      RoCE cannot be specified for any multichannel configurations. This command fails under the following conditions:  Two storage protocols are specified for f1 and f2 and concurrent storage mode is not available.  Three storage protocols are specified on a port.  The f2 and f3 storage protocols are the same. For mixed mode, f2 through fm must be NIC or “None”. For concurrent mode, f3 must be NIC or “None”.
PAGE 427
5. CLI Client Command Descriptions Profile Management Commands Profile ID : 37 MC Type : UMC Port Assignments: Port 0 (p0): NIC,iSCSI,NIC,NIC Port 1 (p1): NIC,FCoE,NIC,NIC Port 2 (p2): NIC,FCoE,NIC,NIC Port 3 (p3): NIC,iSCSI,NIC,NIC Note:(pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI).
PAGE 428
5. CLI Client Command Descriptions Profile Management Commands Note:(pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI). Setting Multichannel Bandwidths See “CMSetBW” on page 345 for more information. Dell NPar Configurations Note: ARI must be available to support sixteen functions on an adapter. OCe14000-series adapters automatically support ARI.
PAGE 429
5.
PAGE 430
5. CLI Client Command Descriptions Profile Management Commands Port Assignments: Port 1: NIC,iSCSI,FCoE,NIC Port 2: NIC,iSCSI,FCoE,NIC Reboot Configuration Profile ID : 37 MC Type : NPAR NParEP Mode : Enabled Port Assignments: Port 1 (p0): NIC,iSCSI,NIC,NIC,NIC,NIC,NIC,NIC Port 2 (p1): NIC,iSCSI,FCoE,NIC,NIC,NONE,NONE,NONE Note:(pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI).
PAGE 431
5.
PAGE 432
5. CLI Client Command Descriptions Profile Management Commands Setting NPar Function Protocols When NPar is enabled, the protocols for additional functions on each port can be specified depending upon the board model, the number of ports available on the adapter, and the NParEP Mode setting, otherwise they will be set to “None”; meaning there is no protocol running on the function. The SetAdapterPortConfig command configures the protocols running on each function.
PAGE 433
5. CLI Client Command Descriptions Profile Management Commands Port 3: NIC,NIC Port 4: NIC,NIC Reboot Configuration Profile ID : 37 MC Type : NPAR NParEP Mode : Disabled Port Assignments: Port 1 (p0): NIC,iSCSI Port 2 (p1): NIC,FCoE Port 3 (p2): NIC,FCoE Port 4 (p3): NIC,iSCSI Note: (pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI).
PAGE 434
5. CLI Client Command Descriptions Profile Management Commands NParEP Mode : Disabled Port Assignments: Port 1 (p0): NIC,iSCSI,NIC,FCoE Port 2 (p1): NIC,FCoE,iSCSI,NIC Note: (pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI).
PAGE 435
5. CLI Client Command Descriptions Profile Management Commands Note: (pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI). Setting NPar Bandwidths After enabling NPar with the SetAdapterPortConfig command, default bandwidths are set for each partition that is enabled. Use the CMSetBW command to configure new bandwidths if the default bandwidths are not acceptable. See “CMSetBW” on page 345 for more information.
PAGE 436
5.
PAGE 437
5.
PAGE 438
5.
PAGE 439
5. CLI Client Command Descriptions UMC Commands Profile ID : 16 MC Type : None Port Assignments: Port 1: NIC Port 2: NIC Reboot Configuration Profile ID : 21 MC Type : None Port Assignments: Port 1 (p0): NIC+RoCE Port 2 (p1): NIC Note: (pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI). UMC Commands The adapter’s physical ports provide a converged conduit for network and storage traffic. Each channel has its own unique MAC address.
PAGE 440
5. CLI Client Command Descriptions UMC Commands UmcEnable This command enables or disables UMC on OCe10100- and OCe11100-series adapters at the adapter level. A system reboot is required to make the change take effect. Notes    The UmcEnable command will enable UMC channel management only, but it will disable any channel management type in effect when it is used. The CMMode command can also be used to enable UMC or other channel management modes.
PAGE 441
5. CLI Client Command Descriptions UMC Commands Supported By Linux, Solaris, VMware ESXi, and Windows Syntax UmcGetParams Parameters WWPN WWPN of an FCoE function on the physical port. MAC Address MAC address of any NIC function on the adapter port.
PAGE 442
5. CLI Client Command Descriptions UMC Commands UmcSetBW Note: This command has been replaced by the CMSetBW command and is provided for backward compatibility for OCe11100-series adapters only. This command sets the minimum and maximum bandwidths for each channel (up to four) on the physical port. This command can also be used to disable the link on a channel by setting the minimum and maximum bandwidths of that channel to 0. The total of the minimum bandwidths must add up to 100.
PAGE 443
5. CLI Client Command Descriptions UMC Commands UmcSetLPVID Note: This command has been replaced by the CMSetLPVID command and is provided for backward compatibility for OCe11100-series adapters only. This command sets the LPVID values for the UMC and SIMode NIC channels. Use the UmcGetParams command to determine the number of LPVIDs required. See “UmcGetParams” on page 440 for more information.
PAGE 444
5. CLI Client Command Descriptions VPort Commands VPort Commands Note: Supported by FC and FCoE adapter ports only. This command creates a virtual port with an automatically-generated WWPN or a user-specified virtual WWPN on the specified physical port. If you specify “auto”, the virtual WWPN is generated automatically. Otherwise, you must specify the virtual WWPN for this parameter. If creation is successful, the WWPN is displayed as part of the output from the command.
PAGE 445
5. CLI Client Command Descriptions VPort Commands ListVFunctions This command lists the virtual functions on a specified NIC port (that is, physical function). Supported By Linux, Solaris, VMware ESX, and Windows Syntax ListVFunctions Parameters The MAC address of a NIC port. MAC Example hbacmd ListVFunctions 00-00-c9-12-34-56 The example output: Virtual Functions for 00-00-c9-12-34-56: MAC Address : 00-00-c9-12-34-ab VLADID : 10 Transmit Rate : 100 Mbit/sec.
PAGE 446
5. CLI Client Command Descriptions VPort Commands Supported By Linux Syntax ListVMs Parameters physical WWPN The WWPN of an FC or FCoE port. virtual WWPN The WWPN of the virtual port. ListVPorts 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.
PAGE 447
5. CLI Client Command Descriptions WWN Management Commands WWN Management Commands Notes   Supported for FC/FCoE adapter ports only. WWN management validates WWNs carefully to avoid WWPN duplication; WWNN duplication is acceptable however. Therefore, you may see error and warning messages if a name duplication is detected. It is strongly recommended that the activation requirement be fulfilled after each WWN change or restore.
PAGE 448
5. CLI Client Command Descriptions WWN Management Commands Parameters WWPN The WWPN of an FC or FCoE port. New WWPN The WWPN of the FC or FCoE port. New WWNN The WWNN of an FC or FCoE port. Type 0 = Volatile 1 = Non-Volatile GetWWNCap This command shows if volatile change is supported for the WWPN. Supported By Linux, Solaris, VMware ESXi, and Windows Syntax GetWWNCap Parameters WWPN The WWPN of an FC or FCoE port. ReadWWN This command reads different types of WWNs.
PAGE 449
5. CLI Client Command Descriptions WWN Management Commands RestoreWWN This command changes the WWNs to the factory default or non-volatile values. The change is non-volatile. Notes    A reboot is required to activate the new setting. For VMware ESXi: After changing the WWN of an adapter, you must reboot the ESXi system before trying to access the adapter on that system. For information on rebooting the ESXi system, see the VMware documentation.
PAGE 450
Appendix A. OneCommand Manager Error Messages Appendix A. OneCommand Manager Error Messages Table A-1 contains a list of some of the error messages that may be encountered during an OCM session. Table A-1 OneCommand Manager Error Messages Error Message Command(s) Error: Read-only management mode Active management commands is currently set on this host. The that change a property on an requested command is not permitted adapter or host. in this mode.
PAGE 451
Appendix A. OneCommand Manager Error Messages Table A-1 OneCommand Manager Error Messages (Continued) Error Message Command(s) Description ERROR: <181>: Authentication: Insufficient credentials All The specified username and password are valid and the user is a member of an OneCommand Manager group, however the OneCommand Manager group does not have sufficient privileges to execute the specified command. See “OneCommand Manager Secure Management” on page 296 for more information.
PAGE 452
Offline and Online Adapter Management Utilities Version 10.2 User Manual P010071-01A Rev.
PAGE 453
Copyright © 2003-2014 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.
PAGE 454
1. Introduction Offline Adapter Management Utility 1. Introduction This document explains how to use the adapter management utility kits for Linux and Windows pre-boot environments (offline management), as well as, the FreeBSD operating system. You can also use adapter management utility kits for production environments referred to as the online adapter management utility.
PAGE 455
1. Introduction Online Adapter Management Utility Online Adapter Management Utility The Online Adapter Management Utility uses a command line interface allowing you to build scripts for automated and unattended firmware and boot code download solutions for Emulex LightPulse® Fibre Channel (FC) host bus adapters (HBAs), LightPulse® FC and Fibre Channel over Ethernet/network interface card (FCoE/NIC) Converged Fabric Adapters (CFAs), and OneConnectTM UCNAs that are in production systems.
PAGE 456
1. Introduction Command Syntax  Uses the flash file on supported UCNAs. Note: This functionality is available for Elxflash Offline and Elxflash Standalone only.         Changes the base directory where fwmatrix.txt is located. Provides online help. Changes the base directory where the firmware and boot code directories are located. Displays an image file's version. Appends the output of the Adapter Management Utility to a log file.
PAGE 457
1. Introduction Supported Platforms Linux operating systems, Emulex recommends using linlpcfg (all lowercase) for the Offline Adapter Management Utility commands (for example, ./linlpcfg listhba). The Offline Adapter Management Utility commands require both:   One space between the command name and the first argument. One space between additional arguments. Note: Do not put a space before or after the equal sign within an argument.
PAGE 458
1. Introduction Abbreviations NIC network interface card (or controller) PCI peripheral controller interface PCI_ID PCI device identification number POST power-on self-test ROM read-only memory SAN storage area network UCNA Universal Converged Network Adapter VPD vital product data WWN world wide name WWNN world wide node name WWPN world wide port name Offline and Online Adapter Management Utilities Version 10.2 User Manual P010071-01A Rev.
PAGE 459
2. Installation Platform Prerequisites 2. Installation Platform Prerequisites Linux The Linux platform requires additional software, such as libraries, to run the different versions of the Offline/Online utility. This section provides the prerequisites. Note: The Linux driver must be installed on the system for the Elxflash applications to work properly.
PAGE 460
2. Installation Installing the Offline Adapter Management Utility for Linux CentOS 6.1 and later     Inbox NIC driver ethtool libsysfs pcutils-libs Windows There are no prerequisites for Windows. FreeBSD The FreeBSD platform requires additional software, such as libraries, to run the different versions of the Offline utility. These prerequisites are listed below and provided by the operating system.     libstdc++ libm libc libgcc Note: BASH is required to run the install and uninstall scripts.
PAGE 461
2. Installation Extracting the Online Adapter Management Utility for Linux Uninstalling The Offline Adapter Management utility for Linux uses an uninstall script to uninstall the utility. The uninstall script executes specific actions depending on the switches that are used.   ./uninstall.sh – Uninstalls ElxflashOffline and Elxlinlpcfg ./uninstall.
PAGE 462
2. Installation Installing the Offline Adapter Management Utility for Linux (NIC Only) Installing the Offline Adapter Management Utility for Linux (NIC Only) The install script determines the correct architecture and distribution, and upgrades the existing ElxflashOffline and Elxlinlpcfg files. If there are no existing ElxflashOffline or Elxlinlpcfg files, the install script installs the packaged ElxflashOffline and Elxlinlpcfg files.
PAGE 463
2. Installation Extracting the Online Adapter Management Utility for Windows   OneConnect iSCSI and NIC drivers winLpCfg/Elxflash Offline Note: The setupElxAll-.exe file is compatible only with WinPE. It does not function with any version of Windows Server. Updating On an existing Windows PE Offline Adapter Management utility installation, run Offline-WinPE---.exe. The installer uninstalls the existing version and then installs the updated version.
PAGE 464
2. Installation Extracting the Driver Files from the Offline Adapter Management Utility for Windows Extracting the Driver Files from the Offline Adapter Management Utility for Windows To extract the driver files from the offline adapter management utility files, you can use the installer or the command line. When extracting these files, all files, both x64 and x86, are extracted to :\My Documents\Emulex\Drivers. This location is hard-coded and cannot be changed.
PAGE 465
2. Installation Offline Adapter Management Utility Installation for FreeBSD In Windows, for example, three directories should be visible in the kit's root directory after you extract the standalone utility. The top level “boot” directory and “firmware” directory are the default directories in which elxflash looks for firmware and boot code images. Ensure that firmware and boot code are located in these directories. # dir 07/05/2012 07:02 PM
. 07/05/2012 07:02 PM ..
PAGE 466
2. Installation Firmware and Boot Code Uninstalling To uninstall the Offline Adapter Management utility for FreeBSD: Run the uninstall script located in the root directory of the installation kit. For example: # cd elxflashOffline--- # ./uninstall.sh Firmware and Boot Code Firmware images are available on the Emulex support site at: http://www.emulex.com. All firmware image files are expected to be in the sub-directory named "firmware".
PAGE 467
3. Adapter Management Utility Command Line Interface Auto-Discovery (/auto) 3. Adapter Management Utility Command Line Interface There are two supported modes for each Adapter Management Utility (Elxflash) switch. The first mode relies on the fwmatrix.txt file. It is your responsibility to update the firmware and boot code directories with the appropriate firmware and boot code images. Note: Ensure that there are no spaces in the in the fwmatrix.txt model name to avoid a firmware update failure.
PAGE 468
3. Adapter Management Utility Command Line Interface Downgrade (/downgrade or /g)   Using the firmware subdirectory, the Adapter Management Utility automatically discovers the best matching firmware for each installed and supported adapter. If multiple versions of firmware or boot code are found for an adapter, the Adapter Management Utility uses the most recent version when performing the firmware download.
PAGE 469
3.
PAGE 470
3. Adapter Management Utility Command Line Interface Force Boot Code (/fb)  For each installed and supported adapter, forces a download of firmware and boot code using the versions specified in the fwmatrix.txt file.
PAGE 471
3. Adapter Management Utility Command Line Interface Force Firmware (/ff)  If multiple versions of boot code are found for an adapter, the Adapter Management Utility uses the most recent version when performing the boot code download. ./elxflash /fb – Forces a boot code download using the fwmatrix.txt file.  For each installed and supported adapter, forces a download of boot code using the boot code version specified in the fwmatrix.txt file.
PAGE 472
3.
PAGE 473
3. Adapter Management Utility Command Line Interface Help (/h or /?)   If multiple versions of firmware and boot code are found for an adapter, Elxflash uses the most recent versions when performing the firmware and boot code downloads. The flash executable file is used to download firmware to supported UCNAs. Example usage: ./elxflash /f /fo – Forces a firmware and boot code download using the fwmatrix.txt file, and downloads the firmware to supported UCNAs using the flash executable file.
PAGE 474
3. Adapter Management Utility Command Line Interface Image Version Display (/iv) Note: This switch was “/i” in previous versions of the online/offline utility. Image Version Display (/iv) Usage: /iv= The image version display switch displays the firmware image file’s version number. Example usage: ./elxflash /iv=firmware/A11460.grp 1.1.46.0 Note: The image version display switch requires a path to the firmware image file in order to decode image file's version.
PAGE 475
3. Adapter Management Utility Command Line Interface Process FC HBAs Only (/fc)   If the update versions are higher than the currently installed versions on the adapter, the Adapter Management Utility provides a download preview for each adapter that can be updated. If multiple update versions of firmware or boot code are found for an adapter, the Adapter Management Utility provides a download preview using the most recent versions. .
PAGE 476
3. Adapter Management Utility Command Line Interface Process UCNAs and CFAs (/ucna) Notes:   /fc is not available on ElxflashOffline_NIC_only. This switch supports LPe16202 CFAs in FC mode. Process UCNAs and CFAs (/ucna) Usage: /ucna The Process UCNA and CFAs switch causes elxflash to act only on UNCAs or CFAs. Example usage: ./elxflash /q /ucna - Only UCNAs are displayed for a query. ./elxflash /auto /up /ucna - Apply auto update only to UCNAs.
PAGE 477
3. Adapter Management Utility Command Line Interface Ramdrive (/ramdrive) - (Windows Offline Adapter Management Utility only) For example: C:\elxflashStandalone-windows-10.0.567.22-1\win>elxflash.bat /q HBA=LPe16002, Port Type=FC, WWN=10:00:00:00:C9:D1:6A:52, PCI ID=E200, VID=10DF, SSID=E206, SVID=10DF, Firmware=1.1.48.0, Boot Code=KT803A10, Boot Enabled=1 HBA=LPe16002, Port Type=FC, WWN=10:00:00:00:C9:D1:6A:53, PCI ID=E200, VID=10DF, SSID=E206, SVID=10DF, Firmware=1.1.48.
PAGE 478
3. Adapter Management Utility Command Line Interface Rewrite (/rewrite or /e)     The fwmatrix.txt file is ignored. You must place the desired rewrite versions of firmware or boot code in their respective directories. If the rewrite versions are more recent than or the same as the versions installed on the adapter, then the rewrite versions are downloaded to the adapter.
PAGE 479
3. Adapter Management Utility Command Line Interface Silent (/s) where is Success or Error, and = 0 for completion with no errors or a non-zero error code for any error. Notes:   FCoE, iSCSI, and NIC-only adapters require a system reboot to activate new firmware. If the preview switch is also used, the Status = field displays “Preview.” Silent (/s) Usage: /s The silent switch prevents all output from being displayed. Example usage: .
PAGE 480
3. Adapter Management Utility Command Line Interface Update (/update)    /query or /q /rewrite or /e /update For example, “./elxflash /sysfs /auto /f” discovers UCNA NIC functions using SysFS and discovers legacy FC functions using LpCfg. It forces a firmware download on UCNA adapters using ethtool or SysFS and forces a firmware and boot code download on legacy FC adapters using LpCfg. Notes:    Only UCNA NIC functions are displayed. Displaying iSCSI and FCoE functions is not supported.
PAGE 481
3. Adapter Management Utility Command Line Interface Verbose (/v) Note: The most recent boot code version is downloaded regardless of the installed boot code. This allows upgrading from one type of boot code to another type. ./elxflash /update – Upgrades the firmware or boot code using the fwmatrix.txt file.   For each installed and supported adapter, the current firmware and boot code versions are compared with the versions specified in fwmatrix.txt. If the update versions in fwmatrix.
PAGE 482
3.
PAGE 483
3. Adapter Management Utility Command Line Interface XML Output (/xml) Note: The vpd command does not display any information if used without the switches listed above. If you attempt to use the /vpd command without the switches listed above, an error message is displayed. If the VPD command is used in conjunction with the fwmatrix.txt file, the model name in the fwmatrix.txt file must match the VPD model name reported by Elxflash.
PAGE 484
4. Offline Adapter Management Utility Command Line Interface Running the Offline Adapter Management Utility from the Command Prompt 4. Offline Adapter Management Utility Command Line Interface The Offline Adapter Management Utility allows you to configure Emulex adapters before you install or boot a server operating system.
PAGE 485
4. Offline Adapter Management Utility Command Line Interface Running the Standalone Adapter Management Utility  For example, starting an Offline Adapter Management Utility with script1.txt in the c:\test directory: oslpcfg @C:\test\script1.txt Note: To redirect screen output to a file, add at the end of each command. For example: oslpcfg listboot n=1 >result.out Note: For more information on script files, see “Creating Script Files” on page 507 and “Script File Commands” on page 508.
PAGE 486
4. Offline Adapter Management Utility Command Line Interface Running the Standalone Adapter Management Utility The elxflash.bat script is used to configure the environment, run elxflash, and revert any changes before exiting. This script installs the MILI service if it is not installed. The winlpcfg.bat script is used to configure the environment, run winlpcfg, and revert any changes before exiting. This script installs the MILI service if it is not installed.
PAGE 487
4. Offline Adapter Management Utility Command Line Interface Running the Standalone Adapter Management Utility The following files and directories should be present:      i386\ x86_64\ ppc64\ elxflash.sh linlpcfg.sh The elxflash.sh script is used to configure the environment, run elxflash, and revert any changes before exiting. This script installs the MILI daemon if it is not installed. The linlpcfg.sh script is used to configure the environment, run linlpcfg, and revert any changes before exiting.
PAGE 488
4. Offline Adapter Management Utility Command Line Interface Supported Commands Supported Commands Table 4-1 lists all Offline Adapter Management Utility commands that are supported or not supported on Emulex adapters on various platforms.  indicates commands are supported on both winlpcfg and linlpcfg. L indicates commands are supported only on linlpcfg. FCoE only indicates commands are supported only by FCoE adapters.
PAGE 489
4.
PAGE 490
4.
PAGE 491
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information For example, either: oslpcfg help download or oslpcfg ? download returns a response similar to the following: download or download Resetting an Adapter (reset) This command resets a specific adapter or all adapters in the system.
PAGE 492
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information For example:   Emulex conventional model name (using /c switch) – LPe16002 VPD model name– LPe1104-M6-D Viewing the Offline Adapter Management Utility Version Information (version) This command shows the Offline Adapter Management Utility version information. To view this information, type oslpcfg version Viewing VPD This command shows the VPD of the adapter specified by its number.
PAGE 493
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information V1 :Emulex LightPulse LPe16002-M6-D 2-Port 16Gb Fibre Channel Adapter V2 :LPe16002-M6-D Command completed, NO Error Viewing Boot Device Information (readbootdevice) This command shows the WWN, the LUN (in decimal format), and the topology in use for the currently selected boot device.
PAGE 494
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information PCI Bus Number : 3 PCI Dev Number : 0 PCI Fun Number : 2 BER : 0 Port Number : 0 ControllerStatus : Alive Manufacturer : Emulex Corporation ModelNumber : OCe11102-FM Description : Emulex OneConnect OCe11102-FM 2-port PCIe 10GbE CNA Capabilities Initiator : TCP offload, Raw Ethernet, Virtual Machines, iSCSI ActiveFirmwareVersion : 10.0.657.0 FirmwareVersionOnFlash : 10.0.654.14 BIOSVersion : 10.
PAGE 495
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information HBA 6: iSCSI MAC:00.00.C9.D5.6A.4F BE:0 Functional FW: 10.0.657.0 devID:712 Port:1 Bus:3 Dev:0 Func:3 OCe11102-FM HBA 7: NIC MAC:00.00.C9.D5.6A.4A BE:0 Functional FW: 10.0.657.0 devID:710 Port:0 Bus:3 Dev:0 Func:0 OCe11102-FM HBA 8: NIC MAC:00.00.C9.D5.6A.4E BE:0 Functional FW: 10.0.657.0 devID:710 Port:1 Bus:3 Dev:0 Func:1 OCe11102-FM HBA 9: NIC MAC:00.00.C9.F1.8D.EE BE:1 Functional FW: 4.2.324.
PAGE 496
4. Offline Adapter Management Utility Command Line Interface Viewing Adapter Information Viewing the MAC Address (listmac) This command shows the MAC address of a NIC UCNA port. To view the MAC address of a NIC UCNA port, type oslpcfg listmac n= Sample response: adapter 2: NIC Permanent MAC 00-00-c9-5b-3a-f4 MAC 00-00c9-5b3ac2 Viewing Firmware Program Revisions (listrev) This command shows the firmware versions in the adapter’s flash memory, specified by their numbers.
PAGE 497
4. Offline Adapter Management Utility Command Line Interface Firmware and Boot Code Download Commands Note: If you are using an FCoE adapter, the readconfig command only supports reading configuration region 8 and 32.
PAGE 498
4. Offline Adapter Management Utility Command Line Interface World Wide Name Commands To access the flash device on the adapter directly, type (all on one line) oslpcfg directdownload a= i= s= where s=1 saves the existing VPD. The following example accesses the flash device on an LPe12000 HBA: oslpcfg directdownload a=lpe12000 i=C:\image\ud100a8.
PAGE 499
4. Offline Adapter Management Utility Command Line Interface World Wide Name Commands The offline utility prompts you to enter new data:     WWPN word 0 WWPN word 1 WWNN word 0 WWNN word 1 The following example writes the WWPN and WWNN for adapter #1. oslpcfg writewwn n=1 Enter or Scan value for WWPN word 0 now Enter a value.
PAGE 500
4. Offline Adapter Management Utility Command Line Interface Boot Code Commands If this occurs, install firmware that supports the volatile WWN. To restore the non-volatile WWN, type oslpcfg restorenvwwn n= The following example restores the non-volatile WWN on adapter #2. oslpcfg restorenvwwn n=2 Restoring the IEEE address (restoredefwwn) This command reads the IEEE address (assigned by the manufacturer) and writes it to the non-volatile WWPN and WWNN.
PAGE 501
4. Offline Adapter Management Utility Command Line Interface Boot Code Commands oslpcfg enableboot n= i= The following example enables BootBIOS on adapter #6: oslpcfg enableboot n=6 i=1 To disable BootBIOS, type oslpcfg disableboot n= The following example disables BootBIOS on adapter #6: oslpcfg disableboot n=6 Selecting a Boot Device (setbootdevice) This command sets the boot device specified by its WWN, LUN, and desired topology.
PAGE 502
4. Offline Adapter Management Utility Command Line Interface Boot Code Commands Read All Alternative Boot Devices (readaltboot) This command shows the WWN and LUN numbers in decimal format of all possible alternate boot devices. You can have up to seven alternate boot devices.
PAGE 503
4. Offline Adapter Management Utility Command Line Interface Configuration Commands Configuration Commands Updating Configuration Regions (config) There are two forms of configuration:   Configure all adapters of a given adapter name at once Configure a single adapter by its number Valid region numbers range from 0 to 32.
PAGE 504
4. Offline Adapter Management Utility Command Line Interface Viewing Personality Information (personalityInfo) Viewing Personality Information (personalityInfo) Note: The personalityInfo command applies to OneConnect adapters only. This command displays the current personality and the available personalities. To view personality information, type oslpcfg personalityInfo n= where adapter index is obtained from the listHBA command.
PAGE 505
4. Offline Adapter Management Utility Command Line Interface Running Tests Running Tests Note: Since the extloopback, intloopback, and pciloopback commands do not support testing on all installed adapters, the o=3 option applies to running linlpcfg with the script command. The o=3 option instructs lpcfg to ignore errors and continue script execution. Running the External Loopback Test (extloopback) Note: Extloopback is not supported LPe16000 series FC adapters.
PAGE 506
4. Offline Adapter Management Utility Command Line Interface Running Tests Running the Internal Loopback Test (intloopback) This command runs the internal loopback test. You can run the test on a specific adapter in the system. Specify the number of times you want the test to repeat, and direct the test response if an error occurs.
PAGE 507
4. Offline Adapter Management Utility Command Line Interface Using Script Files To run the PCI loopback test, type (all on one line) oslpcfg pciloopback n= r= o=
PAGE 508
4. Offline Adapter Management Utility Command Line Interface Using Script Files Script File Commands The following is a sample script file. Each command follows the syntax covered above. The comment lines begin with a semicolon (;): version screendisplay o=0 ;download a=lpe11000 i=c:\temp\zd272a2.
PAGE 509
4. Offline Adapter Management Utility Command Line Interface Using Script Files In the following script file example, messages from the version and listhba commands are output to the log file and to the screen. After the screendisplay command is set to 0, all successive commands (download, listboot, and enableboot) result messages are output only to the log file, not to the screen. version listhba screendisplay o=0 download a=lpe11000 i=c:\temp\zd272a2.
PAGE 510
4. Offline Adapter Management Utility Command Line Interface Using Script Files Note: If the scriptvwwnn command has been used previously, the adapter continues to use that WWPN until you change the WWPN with the restorenvwwn command.
PAGE 511
4. Offline Adapter Management Utility Command Line Interface Using Script Files Updating Volatile WWPN (scriptvwwpn) This command reads the WWPN words 0 and 1 from the command line to update the volatile WWPN. When next discovered, the adapter uses this new WWPN. It does not use the original IEEE address assigned by manufacturing (located in Configuration Region 16 or 32) nor does it use the value entered by the writewwn or scriptwwpn commands.
PAGE 512
4. Offline Adapter Management Utility Command Line Interface Using Script Files Sample log file: >>>>>>>> Test Script starts on Tue Jul 31 14:52:36 2007>>>>>>>> listhba adapter 1: C96C146D Functional FW: WS2.70A5 LPe1150-F4 adapter 2: C94B0718 Functional FW: ZS2.
PAGE 513
4. Offline Adapter Management Utility Command Line Interface Using Script Files **Start tests on Adapter 1 EXTLB: Error - Link is not UP Encounter Error, stop all tests >>>>>>> Test Script stops on Tue Jul 31 14:53:45 2007 Offline and Online Adapter Management Utilities Version 10.2 User Manual P010071-01A Rev.
PAGE 514
5. Offline and Online Adapter Management Utility Status Messages Using Script Files 5. Offline and Online Adapter Management Utility Status Messages The Offline Adapter Management Utility takes a less stringent approach to reporting status messages when used with auto-discovery. An error message is returned only when the Offline Adapter Management Utility reports a failure during a download or if the firmware and boot directories cannot be located.
PAGE 515
5. Offline and Online Adapter Management Utility Status Messages Using Script Files Table 5-1 Elxflash Status Messages (Continued) Message Number Message Title Message Details 9 ERROR_UNSUPPORTED_OS Used by the Exlflash Standalone execution scripts. Returned when the scripts are run on an unsupported operating system. 10 ERROR_UNSUPPORTED_ARCH Used by the Exlflash Standalone execution scripts and returned when the scripts are run on an unsupported architecture.
PAGE 516
6. Offline LPCfg Error Codes Using Script Files 6. Offline LPCfg Error Codes The following table lists the offline LPCfg error codes.
PAGE 517
6.
PAGE 518
6.
PAGE 519
7. Troubleshooting Unsupported Driver 7. Troubleshooting The force firmware (/ff), force boot (/fb), and force firmware and boot code (/f) switches take precedence over the /downgrade, /update, and /rewrite switches. If /ff, /fb, or /f are used, the /downgrade, /update, and /rewrite switches are ignored. The following examples illustrate this behavior: 1. ./elxflash /ff /update a. /update is ignored. b. Performs a force firmware operation on all installed and supported adapters. 2. .
PAGE 520
OneCapture™ Version 10.2 User Manual P010073-01A Rev.
PAGE 521
Copyright © 2013-2014 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.
PAGE 522
1. Introduction Abbreviations 1. Introduction OneCapture™ is an Emulex® device driver utility that gathers system, adapter, device driver, and applications information. You can use this information to examine the functionality of the drivers. Data collected by OneCapture is compressed into a single file which can be sent to Emulex Technical Support for analysis when debugging systems or for diagnostic purposes. OneCapture is fully supported on OCe11000-series adapters.
PAGE 523
2. Running OneCapture Running OneCapture on Windows 2. Running OneCapture You can run OneCapture on any of the following operating systems:       Windows Linux Citrix FreeBSD Solaris VMware ESXi OneCapture is installed as a single .exe or .sh file. Download the appropriate OneCapture file to each of the machines from which you want to collect data. You can run OneCapture from any directory or folder on your computer.     For Windows systems download the OneCapture.exe file.
PAGE 524
2. Running OneCapture Running OneCapture on Linux, Citrix, FreeBSD, and Solaris Basic – The default selection. Select Basic if you do not need to use another type of capture.  Safe – Use Safe if you are capturing data on a Boot from SAN system.  Full – Includes all available captures, but requires a system and adapter reboot. Use only if needed.  Custom – Automatically selected when you do a custom pick of components to capture in the checkbox list. 4. Click Capture.
PAGE 525
2. Running OneCapture Running OneCapture on VMware ESXi 3. Change the script to executable mode, for example, Chmod 777 OneCapture. The progress of the script is displayed. For example: Running Emulex OneCapture Solaris, version Emulex Corporation Report Utility Started at Friday, February 1, 2013 12:50:42 PM CST Initializing report environment for host:solaris Collecting System Information... [-] 1% uname -a 4.
PAGE 526
2. Running OneCapture Running OneCapture on VMware ESXi  execution. Refer to the Emulex CIM Provider Package Installation Guide, available on the Emulex website, for instructions. You must enable SSH access on the ESXi system. To enable SSH on the ESXi system: 1. Press F2 on the ESXi main screen. 2. Go to Troubleshooting Options. 3. Choose Enable SSH. Note: Ensure that the user name and password do not include these special characters: !@#$%^&*()_+{|:"<>?. These special characters are not supported.
PAGE 527
2. Running OneCapture Running OneCapture on VMware ESXi To enable the ESXi shell: 1. Press F2 on the ESXi main screen. 2. Go to Troubleshooting Options. 3. Choose Enable ESXi shell. You may also run the "OneCapture_ESX.sh" by SSH to the ESXi host.  To run OneCapture: 1. Copy the script file "OneCapture_ESX.sh" onto the system through SSH (Secure Shell) or use any other method. 2. Run the shell script for corresponding systems, for example: ./OneCapture_ESX.sh 3.
PAGE 528
2. Running OneCapture Silent Mode Execution Silent Mode Execution To run OneCapture with the GUI in Windows and ESXi in silent mode, without user input, use the following command line parameters. For Windows and ESXi systems: Usage example: OneCapture.exe /silent /type=basic /dir=”C:\Capture\BE3” /outputfilename "output.zip" Available parameters: /force Forces a capture without showing any prompts.
PAGE 529
2. Running OneCapture Silent Mode Execution OneCapture_ESX.exe /silent /type=basic /dir="C:\Capture\BE3" /connect [ip address] /username [username] /password [password] /skip_cim Available parameters: /connect [ip address] Sets the remote VMware host IP address to which to connect. /username [username] Sets the remote VMware host username to which to connect. /password [password] Sets the remote VMware host password to which to connect.
PAGE 530
3. Collected Data Silent Mode Execution 3. Collected Data OneCapture by default collects live firmware core dumps. For dead dumps, Emulex adapters are taken offline during OneCapture execution. You must reboot to bring the adapters online. To skip collect FW dumps:   For Linux and Solaris systems, use "--bootfromsan'' to skip live dumps.
PAGE 531
3. Collected Data Windows Systems Windows Systems The following information is available for Windows systems.
PAGE 532
3. Collected Data Windows Systems Table 3-1 Windows information collected (Continued) Type Information TinyLog PowerShell RoCE Information SEstats RoCE information NetStat RoCE information ElxTrace Trace messages MILI MILI log MILI service status Hbacmd MILIReport OneCommand Manager Application Information Hbacmd version Hbacmd ListHBAs Hbacmd ListHBAs (local) Hbacmd HbaAttribute (local) Hbacmd PortAttribute (local) Cnaboardmgmt.log RM.
PAGE 533
3. Collected Data Linux Systems Table 3-1 Windows information collected (Continued) Type Information AutoPilot Configuration Data FC FCoE iSCSI NIC MPIO Information mpclaim -s mpclaim -e mpclaim -v Linux Systems The following information is available from Linux systems.
PAGE 534
3.
PAGE 535
3. Collected Data Linux Systems Table 3-2 Linux information collected (Continued) Type Information Parameter Current multipath topology multipath -ll iSCSI module information modinfo be2iscsi Partition tables File system mount Disk UUID Disk space available File system table /etc/fstab SCSI information Mount information FC Specific Information modinfo SCSI device info SCSI class information FCoE Specific Information lpcs driver information SCSI class information /sys/class/scsi/..
PAGE 536
3. Collected Data Linux Systems Table 3-2 Linux information collected (Continued) Type Information Parameter List of executable files with elx prefix name List of executable files with mili prefix name rm.log cnaboardmgnt.log utils-install.log mili2d.log Installer.log HBACMD listhbas milirpt version hbaattr (local HBA only) Kernel Log dmesg kernel log Kernel Configuration Compile time kernel configuration /proc/config.
PAGE 537
3. Collected Data Solaris Systems Solaris Systems The following information is available from Solaris systems.
PAGE 538
3.
PAGE 539
3. Collected Data FreeBSD Systems Table 3-3 Solaris information collected (Continued) Type Information Parameter dump /CrashDump/ Crash Dump FreeBSD Systems The following information is available from FreeBSD systems. Table 3-4 FreeBSD information collected Type Information Parameter Kernel information uname -a Kernel release uname -r Network interfaces ifconfig -a Hardware model sysctl -a | egrep -I hw.model Clockrate sysctl -a | egrep hw.clockrate CPU Count sysctl -a | egrep hw.
PAGE 540
3.
PAGE 541
3. Collected Data VMware Systems Table 3-5 VMware information collected (Continued) Type Information CIM Configuration Crash Fault File system Hardware Hung VM Installer Integrity checks Logs Network Performance snapshot Storage System Testing Userworld Virtual Host profiles SCSI /proc/lpfc820 dump (ESXi 5.0 and 5.1 systems only) Debug pages from lpfc device driver HBA Dump Core dump HBACMD (ESXi 5.0 and 5.
PAGE 542
3. Collected Data VMware Systems Table 3-5 VMware information collected (Continued) Type Information Log config /tmp/*.log /tmp/ucna.txt /etc/cim/emulex/*.log /etc/cim/emulex/*.dmp /etc/cim/emulex/*.conf VM_KV_PAGE vm_kv_page -v lpfc-kv-pages.txt vm_kv_page -q all -p all lpfc-kv-pages.txt OneCapture™ User Manual P010073-01A Rev.
PAGE 543
4. Troubleshooting VMware Systems 4. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation. Note: If no operating system is specified, then the issue is applicable to all operating systems. Table 4-1 OneCapture troubleshooting Situation Resolution UCNA information was not captured.
PAGE 544
Emulex Drivers Version 10.2 for Windows Quick Installation Manual P010078-01A Rev.
PAGE 545
Copyright © 2003-2014 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.
PAGE 546
1. Introduction Compatibility 1. Introduction Compatibility For a complete list of adapters that are compatible with these drivers, see the driver's Downloads page on the Emulex website. For compatible firmware versions, see the Downloads page for the specific adapter. Operating System Requirements One of the following operating systems must be installed on an x64 server: Note: The Microsoft patch KB2846340 must be installed on your system in order for the NIC installation to be successful.
PAGE 547
2. Driver Installation Options OneInstall Installer 2. Driver Installation Options There are two ways that you can install the Windows drivers:   OneInstall Installer contains all the Emulex Windows drivers (Emulex Storport Miniport and NDIS Miniport drivers) and the OneCommand Manager application in a single download package.
PAGE 548
2. Driver Installation Options Driver Kit Installer Notes:   The Enterprise kit for the OneCommand Manager application does not operate locally on Windows Server Core. You must install the OneCommand Manager Core Kit (command-line interface only) to the Windows Server Core. The OneInstall Installer does not allow you to perform pre-installation tasks, unattended installations, or text-only installations. For these tasks, use the AutoPilot Installer kits.
PAGE 549
2. Driver Installation Options AutoPilot Installer 4. Select one or both of the following options:  Perform Installation of Software - copies the driver kit for your operating system to your computer.  Unpack All Drivers - extracts all drivers to the current user’s documents folder. Select this option to perform boot from SAN installations. The Operation in progress page shows the kit file loading progress. When the kit files are loaded, the Installation completed page opens. 5.
PAGE 550
2. Driver Installation Options AutoPilot Installer     Utility Only installation. If the drivers in the driver kit share the same version with those already installed on the system, you can reinstall or update the previously installed utility without reinstalling the drivers. Text-Only installation. Text-based installation mode is used automatically when AutoPilot Installer is run on a Server Core system. Network installation.
PAGE 551
2. Driver Installation Options AutoPilot Installer 2. Click Next to proceed to the Installation Options page. For each installation option, the default installation location for that option is displayed. Browse to a different location, if desired. 3. Click Install to continue the installation. The Progress dialog box is displayed. After all tasks complete, a Finish page is displayed. The Start AutoPilot Installer box is automatically selected. 4. Click Finish. AutoPilot Installer is run automatically.
PAGE 552
2. Driver Installation Options Hardware-First Installation or Driver Update Hardware-First Installation or Driver Update The driver kit installer must be downloaded from the Emulex website and installed. Notes:   Updating the NIC protocol driver may temporarily disrupt operation of any NIC teams configured on the system. To update the Emulex protocol drivers, begin this procedure at step 2. To perform a hardware-first installation: 1. Install a new Emulex adapter and power-on the system.
PAGE 553
2. Driver Installation Options Hardware-First Installation or Driver Update Software-First Installation The driver kit must be downloaded from the Emulex website and loaded. Either the full or core driver package may be installed; only one can be installed on a system. To perform a software-first installation: 1. Run AutoPilot Installer using any of the options listed in “Running a Software Installation Interactively” on page 550.
PAGE 554
3. Installation Failure Hardware-First Installation or Driver Update 3. Installation Failure If the installation fails, the Diagnostics window shows that the adapter failed. If the adapter fails: 1. Select the adapter to view the reason why the adapter failed. The reason and suggested corrective action are displayed. 2. Perform the suggested corrective action and run AutoPilot Installer again. Note: AutoPilot Installer can be run again from the Start menu (Programs>Emulex>AutoPilot Installer) or APInstall.
PAGE 555
Emulex® Drivers Version 10.2 for Windows User Manual P010077-01A Rev.
PAGE 556
Copyright © 2003-2014 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.
PAGE 557
1. Introduction Driver Information 1. Introduction Driver Information This product supports the Emulex® OneConnect™ family of universal converged network adapters (UCNAs) and the Emulex LightPulse® family of host bus adapters (HBAs) and converged fabric adapters (CFAs).
PAGE 558
1. Introduction Abbreviations Operating System Requirements One of the following operating systems must be installed on an x64 server:  Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2: x64 versions, Enterprise and Server Core installation Note: The Microsoft patch KB2846340 must be installed on your system in order for the NIC installation to be successful. If the patch is not installed on your system, the installation stops and asks you to install it.
PAGE 559
1.
PAGE 560
1.
PAGE 561
1.
PAGE 562
1.
PAGE 563
2. Installation Driver Installation Options 2. Installation Driver Installation Options There are two ways that you can install the Windows drivers:   OneInstall Installer contains all the Emulex Windows drivers (Emulex Storport Miniport and NDIS Miniport drivers) and the OneCommand Manager application in a single download package.
PAGE 564
2. Installation Driver Installation Options   ElxPlus driver (supports the OneCommand Manager application, persistent binding, and LUN mapping and masking) OneCommand Manager application for Emulex adapters Note: The Enterprise kit for the OneCommand Manager application does not operate locally on Windows Server Core. You must install the OneCommand Manager Core Kit (command-line interface only) to the Windows Server Core.
PAGE 565
2. Installation AutoPilot Installer   Perform Installation of Software - copies the driver kit for your operating system to your computer. Unpack All Drivers - extracts all drivers to the current user’s documents folder. Select this option to perform boot from SAN installations. The Operation in progress page shows the kit file loading progress. When the kit files are loaded, the Installation completed page opens. 5.
PAGE 566
2. Installation AutoPilot Installer    Text-only installation – Text-based installation mode is used automatically when AutoPilot Installer is run on a Server Core system. Network installation – You can place the driver kit installers on a shared network drive and install them across your LAN. Network-based installation is often used in conjunction with unattended installation and scripting. This allows you to configure and install the same driver version on all the hosts in a SAN.
PAGE 567
2. Installation AutoPilot Installer Option 1: Automatically Run the AutoPilot Installer Use this option unless you have specific configuration needs. 1. Double-click the driver kit or run it from a command line. See appendix D., “AutoPilot Installer Command Line and Configuration File Parameters,” on page 726 for information on the command line options. The command line parameter APargs allows you to specify arguments that are automatically passed to the AutoPilot Installer command.
PAGE 568
2. Installation AutoPilot Installer Note: The location of APInstaller.exe may differ on your system, depending on your system's Program Files location. You may also specify a different location when you install the driver package. Hardware-First Installation or Driver Update The driver kit must be downloaded from the Emulex website and loaded. Notes:   Updating the NIC protocol driver may temporarily disrupt operation of any NIC teams configured on the system.
PAGE 569
2. Installation Text-Only Driver Installation Software-First Installation The driver kit must be downloaded from the Emulex website and loaded. Either the full or core driver package may be installed; only one can be installed on a system. To perform a software-first installation: 1. Run AutoPilot Installer using one of the two options listed in “Running a Software Installation Interactively” on page 566.
PAGE 570
2.
PAGE 571
2. Installation Manually Installing or Updating the Emulex Protocol Drivers Uncomment the line that sets “SilentInstallEnable” to “True”. There are other settings in the same section of the configuration file related to unattended installations that you may also want to edit. See “Software Configuration Parameters” on page 728 for more information. After editing the file, you can run the AutoPilot Installer from the Start menu, a command prompt, or a script.
PAGE 572
2. Installation Manually Installing or Updating the Emulex Protocol Drivers 6. Select Show All Devices and click Next. 7. Click Have Disk... and direct the Device Wizard to the location of elxplus.inf. If you have installed the driver installer kit in the default folder and C:\ is your Windows system drive, the path is: C:\Program Files\Emulex\AutoPilot Installer\Drivers\Storport\x64\HBA 8. Click OK. 9. Select Emulex PLUS. Click Next and click Next again to install the driver. 10. Click Finish.
PAGE 573
2. Installation Manually Installing or Updating the Emulex Protocol Drivers 4. Open the SCSI and RAID Controllers item. 5. Double-click the desired Emulex adapter. Note: The driver affects only the selected adapter. If there are other adapters in the system, you must repeat this process for each adapter. All dual-channel adapter models are displayed in Device Manager as two adapters, and each adapter must be updated. 6. Select the Driver tab. 7. Click Update Driver. The Update Driver wizard starts. 8.
PAGE 574
2. Installation Manually Installing or Updating the Emulex Protocol Drivers Note: The driver affects only the selected adapter. If there are other adapters in the system, you must repeat this process for each adapter. All dual-channel adapter models are displayed in Device Manager as two adapters; therefore, you must update each adapter. 9. Select Install from a list or specific location (Advanced) and click Next. 10. Select Don't search. I will choose the driver to install and click Next. 11.
PAGE 575
2. Installation Removing Emulex Driver Kits and Drivers 12. When the device driver finishes installing, click Close. The driver installation is completed. The driver should start automatically. Windows Server 2012 1. Select Server Manager>Dashboard>Tools>Computer Management>Device Manager. Note: Server Manager is set to open by default when booting Windows Server 2012. If it does not open automatically, you can open it with the Server Manager icon at the bottom left of the screen. 2. 3. 4. 5. 6.
PAGE 576
2. Installation Removing Emulex Driver Kits and Drivers 2. Select one of the following in the program list and click the Uninstall icon in the tool bar above the program list. If you have User Access Control enabled, click Continue when asked for permission.  Emulex FC kit-2.xx.xxx  Emulex/FCoE kit-2.xx.xxx  Emulex/NIC 4.xx.xxx  Emulex/iSCSI kit-4.xx.xxx 3. Click Yes when prompted to remove the kit. After the kit is removed from the system, click OK.
PAGE 577
2. Installation Removing Emulex Driver Kits and Drivers 2. Navigate to Emulex\AutoPilot Installer. 3. Run the following batch files:  Uninstall_fc_kit.bat  Uninstall_cna_kit.bat  Uninstall_nic_kit.bat  Uninstall_iscsi_kit.bat The driver files are removed from the system. On all platforms, the reports folder in the “Emulex\AutoPilot Installer” folder is not removed, so you can still view installation history and the drivers that have been installed on the system.
PAGE 578
2. Installation Removing Emulex Driver Kits and Drivers Older Versions of the Emulex Storport Miniport Driver To uninstall or update an earlier version of the Storport Miniport driver (prior to version 1.20), you must remove the registry settings for the adjunct driver prior to manually installing a new driver. To remove the adjunct driver registry settings: 1. Browse to the Storport Miniport driver version 1.20 (or later) driver kit that you downloaded and extracted. 2. Double-click on the deladjct.
PAGE 579
3. Configuration FC/FCoE Driver Configuration 3. Configuration Note: For information on configuring profile management, see the OneCommand Manager Application User Manual or the OneCommand Manager Command Line Interface User Manual. FC/FCoE Driver Configuration The Emulex Storport Miniport driver has many options that you can modify to provide different behavior. You can set Storport Miniport driver parameters using the OneCommand Manager application.
PAGE 580
3. Configuration FC/FCoE Driver Configuration Most parameters default to a setting that optimizes adapter performance. Table 3-1 Storport Miniport Driver Parameters Parameter Definitions AutoMap=n AutoMap controls the way targets are assigned SCSI IDs. Discovered targets are assigned persistent SCSI IDs according to the selected binding method. Persistent bindings do not take effect with the driver in stand-alone mode. Activation Requirement Adapter/Protocol Reboot 0 = automap is disabled.
PAGE 581
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Activation Requirement Parameter Definitions ConfigScale ConfigScale sets the memory footprint profile in Reboot accord with the anticipated use case on a per port basis. While the default value is 4, a value of 1 is considered to be the typical use case. The ConfigScale parameter supersedes the ExtTransferSize parameter for OneConnect adapters.
PAGE 582
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Parameter Definitions DriverTraceMask The DriverTraceMask parameter is only available on operating systems that support extended system event logging. Activation Requirement Adapter/Protocol Dynamic If set to 0 = the parameter is disabled. If set to 1 = error events logging is enabled. If set to 4 = warning events logging is enabled. If set to 8 = informational events logging is enabled.
PAGE 583
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Parameter Definitions ExtTransferSize ExtTransferSize is an initialization-time parameter that affects the maximum SGL that the driver can handle, which determines the maximum I/O size that a port will support. Activation Requirement Adapter/Protocol LightPulse adapters only including LPe15000 and LPe16000 HBAs. If set to 0 = the maximum default transfer size is 512KB for all controller models.
PAGE 584
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Parameter Definitions LinkSpeed=n LinkSpeed has significance only if the adapter supports speeds other than one Gb/s. Activation Requirement Adapter/Protocol Reset FC Only Value: Auto-select, 1 Gb/s, 2 Gb/s, 4 Gb/s, 8 Gb/s Default = Auto-select Notes: • Setting this option incorrectly can cause the adapter to fail to initialize.
PAGE 585
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Activation Requirement Parameter Definitions NodeTimeout=n The node timer starts when a node (that is, a Dynamic discovered target or adapter) becomes unavailable. If the node fails to become available before the NodeTimeout interval expires, the operating system is notified so that any associated devices (if the node is a target) can be removed.
PAGE 586
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Parameter Definitions ScanDown=n If set to 0 = lowest AL_PA = lowest physical disk (ascending AL_PA order). Activation Requirement Adapter/Protocol Reboot FC Only Reboot LightPulse Only Reset FC Only If set to 1 = highest AL_PA = lowest physical disk (ascending SEL_ID order). Value: 0–1 Default = 1 Note: This option applies to private loop only in DID mode.
PAGE 587
3. Configuration FC/FCoE Driver Configuration Table 3-1 Storport Miniport Driver Parameters (Continued) Activation Requirement Parameter Definitions TraceBufSiz=n TraceBufSiz sets the size in bytes for the internal Reboot driver trace buffer. The internal driver trace buffer acts as an internal log of the driver's activity. Adapter/Protocol Value: 250,000–2,000,000 or 0x3D090–0x1E8480 (hex).
PAGE 588
3. Configuration FC/FCoE Driver Configuration Note: A system restart is required to make changes to CoalesceMsCnt and CoalesceRspCnt. Performance Testing There are three driver parameters that need to be considered (and perhaps changed from the default) for better performance testing: QueueDepth, CoalesceMsCnt, and CoalesceRspCnt.
PAGE 589
3. Configuration NIC Driver Configuration NIC Driver Configuration Notes:   TOE is supported and enabled by default. TOE is not supported on LPe16202 CFAs and OCe14000-series adapters. Configuring NIC Driver Options The Windows Server NIC driver supports configurable driver options through the Advanced Property page in Windows Device Manager. For information on how to configure the options through the Advanced Property page, see “Modifying Advanced Properties” on page 607.
PAGE 590
3. Configuration NIC Driver Configuration As a result, the driver can only report a feature's current capabilities (accurate for the present configuration), if the feature is currently enabled. However, standard PowerShell commands will report whatever is present in the registry, when the feature is not enabled. This can conflict with what the driver actually supports in the current configuration.
PAGE 591
3. Configuration NIC Driver Configuration     ARI must be available on the system to support up to sixteen functions on an adapter. If these conditions are not met, although you may configure all sixteen functions, only eight functions will be present and discovered by the OneCommand Manager application after a reboot. Only OCe14000-series adapters support ARI. The system hardware, such as the motherboard and BIOS, must support ARI.  ARI must be enabled in the system BIOS.
PAGE 592
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options Option Name Acceptable Values Supported Operating Systems Class of Service (802.
PAGE 593
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems Enhanced Transmission Selection Disabled (default) Windows Server 2008 Enabled Definition If ETS is enabled, the driver filters Windows Server 2008 R2 transmit packets based on the 802.1p priority tag into multiple Windows Server 2012 separate transmit rings.
PAGE 594
3.
PAGE 595
3.
PAGE 596
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems NetworkDirect 0—Disabled Windows Server 2012 R2 1—Enabled (default) Definition The Network Direct feature enables an offloaded RDMA interface for SMB 3.0 network attached storage traffic using Microsoft's SMB Direct protocol.
PAGE 597
3.
PAGE 598
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Preferred NUMA Node Not present or a value from 0–65535. Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Optional. No default setting is Windows Server 2012 set.
PAGE 599
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Receive Side Scaling Disabled Enabled (default) Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Support for multiple RSS queues if enabled. RSS scales receive processing over multiple CPUs in parallel.
PAGE 600
3.
PAGE 601
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems RSS Profile Closest processor (default) Windows Server 2012 The RSS Profile setting determines the RSS load balancing profile implemented by Microsoft for this network adapter.
PAGE 602
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values SR-IOV Disabled (default) Enabled Supported Operating Systems Note: For OCe11102, LPe16202, and OCe14000-series only. Windows Server 2012 Windows Server 2012 R2 Definition SR-IOV enables the adapter to allocate virtual PCI functions for each virtual machine in Hyper-V.
PAGE 603
3.
PAGE 604
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems TCP Connection Offload (IPv4) Enabled Windows Server 2008 Disabled (default) Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Note: TCP Connection Offload is not supported on 16Gb UCNAs.
PAGE 605
3.
PAGE 606
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems UDP Checksum Offload (IPv6) Disabled Windows Server 2008 RX and TX Enabled (default) Windows Server 2008 R2 RX Enabled Windows Server 2012 TX Enabled Windows Server 2012 R2 Enabled (default) Note: For OCe11102, LPe16202, and OCe14000 only.
PAGE 607
3. Configuration NIC Driver Configuration Table 3-3 Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 NIC Driver Options (Continued) Option Name Acceptable Values Supported Operating Systems VLAN Identifier (802.
PAGE 608
3. Configuration NIC Driver Configuration The Windows Device Manager is displayed. Figure 3-1 Partial View of Windows Device Manager 2. Right-click the network adapter for which you wish to modify advanced properties. 3. Click Properties, and click the Advanced tab (Figure 3-2 on page 609). 4. From the list of properties, click the property (parameter) you want to modify, then select the new value of the property by selecting from the Value list. 5. Click OK.
PAGE 609
3. Configuration NIC Driver Configuration Note: Modifying properties causes the network driver to reload and some TCP connections may be temporarily dropped. Figure 3-2 NIC Advanced Properties in Windows Server 2008 Statistics Property Page Use the Statistics Properties tab to view the performance of the device and network.
PAGE 610
3. Configuration NIC Driver Configuration 4. From the list of properties, select the property (parameter) you want to view. Figure 3-3 NIC Statistics Properties in Windows Server 2008 Table 3-4 NIC Driver Properties Statistics Statistic Name Description Transmit Throughput The data rate for this adapter on the network, including all packet headers. It is expressed in terms of bits/sec, where 1 byte = 8 bits. This is computed as the average over approximately 3 seconds.
PAGE 611
3. Configuration NIC Driver Configuration Table 3-4 NIC Driver Properties Statistics (Continued) Statistic Name Description RSS Receive Packets The number of receive packets that were suitable for RSS. Transmit Flow Control Pause Requests The number of times the network adapter sent a PAUSE frame to request that the peer stop sending data temporarily. This indicates a potential bottleneck in the system. Typically, this bottleneck is the result of the DMA of packets from the adapter to host memory.
PAGE 612
3. Configuration NIC Driver Configuration Table 3-4 NIC Driver Properties Statistics (Continued) Statistic Name Description Receive Drops No Memory (DMA Limited) The number of packets dropped as a result of insufficient buffers posted by the driver. This is generally the result of the CPU core used for any receive queue reaching 100%. The system may lack sufficient CPU cycles to post receive buffers at the necessary rate.
PAGE 613
3. Configuration NIC Driver Configuration Table 3-4 NIC Driver Properties Statistics (Continued) Statistic Name Description CRC Errors The number of packets dropped as the result of CRC errors on the layer 2 Ethernet packet. In products that expose multiple PCIe functions per Ethernet port, this statistic is only incremented for the lowest PCI function per port since the packet cannot be further classified because of the error.
PAGE 614
3. Configuration NIC Driver Configuration Options: -a str[,str] Selects all adapters with any of the given strings in the connection or device name. If omitted, occfg prompts for an adapter from a list. -s name=v,[name=v] Sets the parameter's value and reloads the devices. -g name[,name] Gets parameter value. -r Skips reloading the driver when setting a parameter. -f Force reloading the driver. -- Force disabling the driver. -+ Force enabling the driver. -l List available adapters and exit.
PAGE 615
3. Configuration NIC Driver Configuration Selecting an Adapter In batch mode, the “-a” parameter should be followed by a substring that is contained within the adapter name. The name is a combination of the device manager name (for example, Emulex OneConnect OCe11102) and the network connection name (for example, Local Area Connection). The later may be modified by using the Windows Network Connections applet (ncpa.cpl).
PAGE 616
3. Configuration NIC Driver Configuration To modify a parameter without a driver reload, use “-r”. This is useful to modify several parameters in sequence, then force a reload of the driver at the end. To force a driver reload use the “-f” parameter.
PAGE 617
3. Configuration NIC Driver Configuration Displaying All Parameters To display the current value of all parameters, use either “-p” or “-q” command line options. This shows the registry value or driver value of the parameter, or both when using “-pq” together. For example: occfg.exe -a "SLOT 5 Port 1" -pq OneConnect Network Config (10.2.164.0) Copyright 2011 Emulex Emulex OneConnect OCe14102-UX-D 2-port PCIe 10GbE CNA (SLOT 5 Port 1) Display all properties. [Registry] Class of Service (802.
PAGE 618
3.
PAGE 619
3.
PAGE 620
3. Configuration NIC Driver Configuration 3. The program provides a list of available registry parameters to modify or query. Type either the number of the corresponding option or a substring in the parameter name. The substring must uniquely identify the parameter or occfg will display all potential options. 4. To apply the parameters, select the menu item to exit and reload the drivers.
PAGE 621
3. Configuration NIC Driver Configuration Notes:       The operating system comes with an Emulex inbox driver. Emulex recommends that you use the Emulex out-of-box driver. For a list of supported drivers and adapters, see the latest Windows Drivers release notes, which are available for download from the Emulex website. SR-IOV is not supported with RoCE configurations. SR-IOV is not supported with UMC.
PAGE 622
3. Configuration NIC Driver Configuration Advanced mode = Enable  Universal Multichannel (UMC) = Disable 3. Save the settings and enable SR-IOV for each PCI function. The server reboots after this modification.  SR-IOV Server Validation Use the following Microsoft PowerShell commands to determine if your server is capable of SR-IOV.     Get-VmHost Get-NetAdapterSriov Get-VmNetworkAdapter Get-VmSwitch See Microsoft documentation for more information.
PAGE 623
3. Configuration NIC Driver Configuration 8. Reboot the system. 9. If the system does not boot, press and select Previous Known Good, or use the system restore function while booting from an operating system install disc or recovery disc. 10. If the system boots but does not work properly, restore from a previous restore point, or import the saved .reg file and reboot. Verifying the Driver Version To verify the Emulex device driver meets the minimum requirements: 1.
PAGE 624
3. Configuration NIC Driver Configuration 3. Open the Network Adapters item, find the Emulex device and right-click. Select Properties from the context-menu. The Properties dialog box opens showing the Driver page. The Driver page contains the driver version number. Figure 3-5 Emulex NIC Driver Properties Page 4. Click Driver Details. A window opens displaying the driver name. Enabling SR-IOV in the Emulex Device To enable SR-IOV in the Emulex device: 1.
PAGE 625
3. Configuration NIC Driver Configuration Figure 3-6 Emulex NIC Advanced Properties Page 5. Select SR-IOV from the list and select Enabled from the Value list. Note: You must configure Hyper-V to create an SR-IOV enabled virtual machine. See Microsoft Hyper-V documentation for more information. Hyper-V The Hyper-V role must be added using the Server Manager.
PAGE 626
3. Configuration NIC Driver Configuration Once the Emulex driver is loaded, the Emulex SR-IOV virtual function is used for all unicast receive and transmit traffic. The emulated NIC handles multicast and broadcast traffic. If SR-IOV is disabled, the Emulex adapter is removed from the virtual machine, and all traffic automatically uses the emulated NIC. This technology allows Live Migration of Virtual Machines when using SR-IOV.
PAGE 627
3. Configuration NIC Driver Configuration Figure 3-7 Emulex NIC Statistics Properties page Verifying SR-IOV from the Host Hyper-V Server 1. From the Device Manager, open the Network Adapters item, click the Microsoft Hyper-V Network adapter and right-click. Select Properties from the context-menu. The Hyper-V Network adapter Properties dialog box opens showing the Driver page. 2. Select the Statistics tab. 3. From the Statistics tab, locate the “Virtual Functions Allocated” item.
PAGE 628
3. Configuration NIC Driver Configuration Configuring NVGRE for the OCe14000-series Adapters Network virtualization using NVGRE is a network virtualization method that uses encapsulation and tunneling to create large numbers of VLANs for subnets that can extend across dispersed data centers and layer 2 (the data link layer) and layer 3 (the network layer). The purpose is to enable multi-tenant and load-balanced networks that can be shared across on-premises and cloud environments.
PAGE 629
3. Configuration NIC Driver Configuration 7. Expose a NIC interface into the VM for each of the vSwitches:  Make sure “Enable virtual machine queue” is selected under Network Adapter -> Hardware Acceleration of the VMs.  Record the MAC addresses located under the Network Adapter -> Advanced Features. These will be used in the add/remove policy scripts. 8.
PAGE 630
3. Configuration NIC Driver Configuration Remove-NetVirtualizationLookupRecord; New-NetVirtualizationLookupRecord -VirtualSubnetID "6001" -CustomerAddress "10.0.0.5" -ProviderAddress "192.x.x.x" -MACAddress "080800000005" -Rule "TranslationMethodEncap" New-NetVirtualizationLookupRecord -VirtualSubnetID "6001" -CustomerAddress "10.0.0.7" -ProviderAddress "192.x.x.
PAGE 631
3. Configuration NIC Driver Configuration # --------------------------------------------------------------------------------# Blue1 Host1 5001 10.0.0.5 192.x.x.x 06-06-00-00-00-05 10.0.0.1 # Blue2 Host2 5001 10.0.0.7 192.x.x.x 06-06-00-00-00-07 10.0.0.1 # # [Customer Routes] # DestPrefix NextHopGW Note # ----------------------------------------------------------------------------------# 10.0.1.0/24 0.0.0.
PAGE 632
3. Configuration NIC Driver Configuration # Host2 example-host2 192.x.x.x {Blue2:5001, Red2:6001} # [2-1] Host1 # # (a) Configure Provider Address and Route: # Get the interface, assign the PA and the default route Get-NetVirtualizationProviderAddress | where {$_.ProviderAddress -eq "192.x.x.x"} | Remove-NetVirtualizationProviderAddress; # (b) Set VirtualSubnetID on the VM network port Get-VMNetworkAdapter "Blue1" | where {$_.
PAGE 633
3. Configuration NIC Driver Configuration MS_NETWNV.sys should only be bound to WNVNIC (physical NIC). If ms_netwnv is bound to a vswitch or Hyper-V adapter, unbind it from the host server. For example: Disable-netadapterbinding vEthernet* -ComponentID ms_netwnv Verify that all of the IP Addresses and MAC Addresses used in the add and remove policy scripts match the VM IP’s/MACs using ipconfig /all. Create firewall rules to allow ICMP (ping) packets: 1.
PAGE 634
3. Configuration NIC Driver Configuration 2. Change the VM IP Address. For example: change 10.0.0.5 on one host and 10.0.0.7 on the other. Without NVGRE, you would not be able to use the same IP address as the other VM. Ensure that you see the WNVNIC interface using the PowerShell command get-netadapter.  If you are unable to see the NVGRE Ethernet connection, make sure that the Hyper-V’s control panel/network connections property and advanced property windows are all closed.
PAGE 635
3. Configuration NIC Driver Configuration  OneCommand Manager CLI. See the OneCommand™ Manager Command Line Interface Manual for information about enabling the RoCE profile using OneCommand Manager CLI. Confirming That the RoCE Profile Is Enabled Confirm that the RoCE profile is enabled by using one of the following methods:  In the Advanced tab of the Network Property page, ensure that NetworkDirect is enabled. See Figure 3-8.
PAGE 636
3. Configuration NIC Driver Configuration  Get-NetOffloadGlobal Figure 3-10 Get-NetOffloadGlobal - RoCE-Enabled If the profile is correct and NetworkDirect is enabled, you should see active NetworkDirect listeners on IP addresses (port 445) assigned to the NICs using “netstat -xan”. Using SMB Direct with NetworkDirect Because RoCE is supported in Windows using SMB Direct with NetworkDirect, it is important that SMB Direct and NetworkDirect be configured correctly.
PAGE 637
3. Configuration NIC Driver Configuration Mapping the RoCE-Enabled Client to the Server-Side Storage Using an available network share with the proper permissions configured, open an SMB share from the Windows Run command or from the command prompt, by typing: "net use [devicename:*] [\\computername\sharename] By default this creates two RDMA connections per SMB Direct-enabled network interface on a particular server. Each SMB Direct connection maps to an RDMA queue pair.
PAGE 638
3.
PAGE 639
3. Configuration NIC Driver Configuration Figure 3-15 Multichannel Constraint SMB Direct Resource Usage Active Connections Active connections describe the connections that a client makes to a server. Passive connections describe the connections that a server allows the client to complete. The maximum number of active connections per port for an adapter are required when setting the “ConnectionCountPerRdmaNetworkInterface” parameter.
PAGE 640
3. Configuration NIC Driver Configuration Table 3-5 shows the maximum number of SMB Direct active (client mode) connections that can be initiated on Windows Server 2012 and Windows Server 2012 R2 using the OCe14000-series adapters.
PAGE 641
3. Configuration NIC Driver Configuration For Windows Server 2012 and Windows Server 2012 R2, all existing RDMA connections between the particular client-server pair, on which the failure occurred, are torn down and recreated. After a certain number of unsuccessful retries, SMB traffic falls back to TCP/IP.
PAGE 642
3. Configuration NIC Driver Configuration L2 Flow Control While running a port in generic pause mode because of congestion, RoCE latencies can be adversely affected. Under these conditions, it is advisable to configure RoCE to use PFC. PFC mode ensures that RoCE traffic latencies are unaffected in presence of congestion as a result of NIC traffic. However, PFC mode is not required. For switches and adapters that do not support PFC, RoCE can continue to work without PFC mode.
PAGE 643
3. Configuration NIC Driver Configuration  An OCe14000-series adapter configures RoCE traffic for priority 5.  Manually enable priority 5 on the switch under a different priority group other than FCoE/iSCSI/NIC priority group. Note: If you do not enable priority 5 on the switch side, the OCe14000 adapter continues to be configured for PFC mode priority 5. This configuration may result in packet losses, unrecoverable errors, or infinite retries for RoCE traffic.
PAGE 644
3. Configuration NIC Driver Configuration Refer to the Emulex Universal Multichannel Reference Guide for additional information on multichannel. NPar Configuration (Dell Only) Notes:     NPar is available only on OCe14000-series adapters. When NPar is enabled, RoCE cannot be configured on any function. Each partition should have standard NIC properties for stateless offload. SR-IOV must be disabled on the adapter BIOS when NPar is used.
PAGE 645
3. Configuration NIC Driver Configuration The following items are supported on a per-partition basis:    Statistics LSO, LRO, RSS, TSO, and MTU Support for NetQueues NPar Considerations          NPar can use virtual adapters using VLAN tagging per partition. NPar can use RSS queuing support per partition. DCBX is supported while in NPar mode. If iSCSI or FCoE functions are not enabled, they are available as NIC functions. Only one iSCSI function is allowed per physical port.
PAGE 646
3. Configuration NIC Driver Configuration Note: NParEP is only available when NPar mode is activated on OCe14000-series adapters. See “Using NParEP” on page 649.     Reset the adapter to the factory default settings using the Factory Default button. Use the Port tab to view the available ports on the adapter. Configure a protocol to run on each partition on the ports. Configure the minimum and maximum bandwidth for each partition on the ports.
PAGE 647
3. Configuration NIC Driver Configuration   you select Disabled, only the first PCI functions on each port are powered-on and present. None of the PCI function parameters can be changed. If you select NPar, NPar is enabled and the PCI function parameters can be modified (see “Enabling NPar Using the Multichannel Property Page” on page 645). Factory Default — restores the adapter to its factory default settings. A system reboot is required for the changes to take an effect.
PAGE 648
3. Configuration NIC Driver Configuration Multichannel Property Page with NPar Enabled Figure 3-20 The Multichannel Property Page with NPar Enabled and NParEP Disabled When NPar is enabled on the Multichannel property page, all PCI functions present on a port are listed on each Port tab. Each row corresponds to a single PCI function and contains all PCI function parameters. The following PCI function parameters are available:     The Enabled column contains check boxes for each PCI function.
PAGE 649
3. Configuration NIC Driver Configuration    The BW[%] column lists the maximum bandwidth that a PCI function can use as a percentage of the total port bandwidth. The Name column provides a friendly device name if possible. Otherwise, it is a device name or a generic operating system device class name. NParEP — enables NParEP. See “Using NParEP” on page 649 for more information. Criteria for Making PCI Function Modifications      The first PCI function on each port cannot be disabled.
PAGE 650
3. Configuration NIC Driver Configuration Figure 3-21 The Multichannel Property Page with NPar Enabled and NParEP Enabled Multichannel Property Page with NPar and NParEP Enabled To enable NParEP, select the NParEP checkbox. When NParEP is enabled, the PCI functions in Table 3-8 or Table 3-9 become visible. PCI Function Presentation Using NParEP Note: When using host tools that allow you to configure partitions, you can select an option of "None" for a PCI function.
PAGE 651
3.
PAGE 652
3. Configuration NIC Driver Configuration Network Driver Performance Tuning Optimizing Server Hardware and BIOS Configuration Adapter performance can be improved by selecting a more efficient PCIe packet payload size. If the system BIOS allows selection of a larger PCIe packet size, selecting at least a 512-byte PCIe packet payload size provides the best efficiency for PCIe data transfers. This may be an option in the server's system BIOS.
PAGE 653
3. Configuration NIC Driver Configuration Table 3-10 Windows Server Performance Tuning Situations (Continued) Situation Answer/Solution There is a small server struggling to keep up with larger servers on the network. Disable RSS, enable TCP offload, enable jumbo packets, and increase the interrupt moderation to allow fewer interrupts per second. There is a general purpose server such as Use TCP offload, and enable RSS. Active Directory server, DHCP server, or a DNS server.
PAGE 654
3. Configuration NIC Driver Configuration Ethernet frame header or the trailing CRC. The standard MTU is 1500 bytes, corresponding to a 1514-byte packet size plus a 4-byte trailing CRC. Historically, any 1514-byte frame is a standard packet, while any frame larger than 1514 bytes is called a jumbo packet. Windows Server attempts to standardize the terminology across vendors so the jumbo packet parameter refers to the byte size of the packet. The Windows Server driver supports several jumbo packet values.
PAGE 655
3. Configuration NIC Driver Configuration Receive and transmit flow control are on by default. Flow control is not available if using FCoE on a converged network adapter. In this situation, priority pause is negotiated with the network switch and used only for the FCoE protocol packets. The NIC function can also use priority pause if supported by the switch. This requires tagging packets in the operating system with the correct priority value, and enabling ETS in the driver properties.
PAGE 656
3. Configuration NIC Driver Configuration To improve network and CPU performance for heavy network loads under these conditions, you may have to make an appropriate NUMA CPU selection. For example, in Windows Server 2012 R2, you can use the Task Manager to adjust the “Set Affinity” property to bind the application to a specific NUMA node for maximum network performance and CPU efficiency. Checksum Offloading and Large Send Offloading (LSO) The adapter supports IP, TCP, and UDP checksum offloading.
PAGE 657
3. Configuration NIC Driver Configuration RSS may help performance. If the same four-processor server uses RSS, there are four parallel executing DPCs, one on each processor. The total CPU usage that is available for networking processing is increased from 25 percent to 100 percent. Some server machines and some network traffic profiles do not benefit from RSS.
PAGE 658
3. Configuration NIC Driver Configuration     TCP timers, including delayed ACK, push, retransmit and keep alive, are implemented in hardware. This reduces host CPU usage. Retransmits are handled entirely in hardware. Packetizing data, including segmenting, checksums, and CRC, is supported. The network driver should use send and receive buffers that are larger than 1 MB for maximum efficiency. The driver provides efficient parallel processing of multiple connections TCP on multiple CPU systems.
PAGE 659
3. Configuration NIC Driver Configuration netsh interface tcp add chimneyapplication state=disabled application= netsh interface tcp add chimneyport state=disabled remoteport=23 localport=* Note: The netsh commands require the Windows firewall to be running. If the firewall is disabled, all applications and ports added with the netsh commands may fail to connect.
PAGE 660
3. Configuration NIC Driver Configuration Enabling certain Windows networking features, such as network bridging, VPN, and routing, may cause the operating system to enable IP NAT services and the IPSEC policy agent. These services, if enabled, disallow connections from being offloaded to the adapter.
PAGE 661
3. Configuration NIC Driver Configuration Some applications run slower with interrupt coalescing enabled, such as applications that depend on the completion of the current network transfer before they post additional work. If an application sends and receives one network message before posting the next message, it is considered latency bound.
PAGE 662
3. Configuration iSCSI Driver Configuration   Unbind unused network protocols in the Network Connections property page. Disable any firewall services, IPSEC, or NAT. iSCSI Driver Configuration Table 3-12 lists the user-configurable iSCSI driver options available on Windows Server. It includes a description of the parameters, their default values, and their configuration limits.
PAGE 663
3. Configuration iSCSI Driver Configuration Table 3-12 iSCSI Driver Options (Continued) Parameter Default Value Minimum Value Maximum Value Description im_policy 2 0 4 The Interrupt Moderation policy parameter controls the rate of interrupts for the UCNA. For more information, see “Interrupt Moderation Policy Settings” on page 664. large_io 64 64 512 Maximum transfer size in a single I/O request, in KB.
PAGE 664
3. Configuration iSCSI Driver Configuration Interrupt Moderation Policy Settings The Interrupt Moderation policy settings control the rate of interrupts for UCNA hardware. By default, the driver implements an interrupt moderation scheme that is based on the I/O load and the interrupt rate. The default setting for im_policy tries to vary the interrupt rate between 3500 to 10000 interrupts per second. In addition, the iSCSI driver allows other configuration settings, as shown in Table 3-13.
PAGE 665
3. Configuration iSCSI Driver Configuration The Microsoft iSCSI Initiator Service sets its own initiator name. Once you have installed it, you must replace this with your chosen initiator name. To do this: 1. In the Microsoft iSCSI Initiator Service, under the general tab, click Change. 2. Type your initiator name and click OK. Logging into a Target Using the Microsoft Software Initiator If you install the Software Initiator, you must select the UCNA initiator when logging into the target. To do this: 1.
PAGE 666
3. Configuration iSCSI Driver Configuration 6. Enable MPIO. a. Select Start>Administrative Tools>Server Manager. b. In the Server Manager tree, click Features. c. In the Features area, click Add Features. d. In the Add Features wizard on the Select Features page, select the Multipath I/O check box and click Next. e. On the Confirm Installation Selections page, click Install. f. When the installation is completed, click Close on the Installation Results page. g.
PAGE 667
3. Configuration iSCSI Driver Configuration Maximum Transmission Unit (MTU) for iSCSI Connections Because the Emulex OneConnect UCNA is a multi-function adapter, the MTU settings for iSCSI functions are different than the ones for NIC functions. For iSCSI, there is no explicit way to configure MTU from the OneCommand Manager application. Instead, this value is auto-negotiated by the firmware.
PAGE 668
3. Configuration iSCSI Driver Configuration Configuring LDTO and ETO on the Windows Server LDTO and ETO values are configured using the Advanced tab of the Device Manager Property page. Table 3-14 lists the default values of LDTO and ETO on the Windows Server and the limits within which they can be configured. Note: If the ETO is set to a number between 0 and 19, the driver assumes the value to 20 seconds internally. You will not see any modification to the registry.
PAGE 669
4. Troubleshooting General Troubleshooting 4. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section contains reference tables on event codes and error messages and provides information regarding unusual situations. General Troubleshooting Table 4-1 General Troubleshooting Issue Answer/Solution The operating system fails to install or Verify that the operating system is supported by the driver.
PAGE 670
4. Troubleshooting Troubleshooting the FC/FCoE Driver Event Trace Messages ELS Log Messages (0100–0130) lpfc_mes0100: FLOGI failure – ulpStatus: x%x, ulpWord[4]:x%x Description An ELS FLOGI command that was sent to the fabric failed. Severity Error Log LOG_ELS verbose Action Check the fabric connection. lpfc_mes0101: FLOGI completes successfully – NPortId: x%x, RaTov: x%x, EdTov: x%x Description An ELS FLOGI command that was sent to the fabric succeeded.
PAGE 671
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0104: ADISC completes to NPortId x%x Description The adapter performed an ADISC into the remote NPort. Severity Information Log LOG_ELS verbose Action No action needed, informational. lpfc_mes0105: LOGO completes to NPortId: x%x Description The adapter performed a LOGO into a remote NPort. Severity Information Log LOG_ELS verbose Action No action needed, informational.
PAGE 672
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0115: Unknown ELS command: x%x, received from NPortId: x%x\n Description Received an unsupported ELS command from a remote NPORT. Severity Error Log LOG_ELS verbose Action Check remote NPORT for potential issue. See Also lpfc_mes0112 lpfc_mes0128: Accepted ELS command: OpCode: x%x Description Accepted an ELS command from a remote NPORT. Severity Information Log LOG_ELS verbose Action No action needed, informational.
PAGE 673
4. Troubleshooting Troubleshooting the FC/FCoE Driver Discovery Log Messages (0202–0262) lpfc_mes0202: Start Discovery: Link Down Timeout: x%x, initial PLOGICount:%d Description Device discovery/rediscovery after FLOGI, FAN or RSCN has started. TMO is the current value of the soft link time. It is used for link discovery against the LinkDownTime set in parameters. DISC CNT is number of nodes being discovered for link discovery. RSCN CNT is number of nodes being discovered for RSCN discovery.
PAGE 674
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0225: Device Discovery completes Description This indicates successful completion of device (re)discovery after a link up. Severity Information Log LOG_DISCOVERY verbose Action No action needed, informational. lpfc_mes0229: Assign SCSIId x%x to WWN word 0: x%x, WWN word 1: x%x, NPortId x%x Description The driver assigned a SCSI ID to a discovered mapped FCP target.
PAGE 675
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0236: Issuing command to name server” type: x%x Description The driver is issuing a nameserver request to the fabric. Also recorded if a GID_FT is sent. Severity Information Log LOG_DISCOVERY verbose Action No action needed, informational. See Also lpfc_mes0239 or lpfc_mes0240 lpfc_mes0238: NameServer response DID count:%d Description Received a response from fabric name server with N DIDs.
PAGE 676
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0256: Start node timer on NPortId: x%x, timeout value:%d Description Starting timer for disconnected target with NPort ID and timeout value. Severity Information Log LOG_ELS verbose Action No action needed, informational. lpfc_mes0260: Stop node timer on NPortId: x%x, SCSIId: x%x Description Discontinuing timer for reconnected target with NPort ID and SCSI ID.
PAGE 677
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0326: Reset HBA – HostStatus: x%x Description The adapter has been reset. Severity Information Log LOG_MBOX verbose Action No action needed, informational. INIT Log Messages (0400–0463) lpfc_mes0400: Initializing discovery module: OptionFlags: x%x Description Driver discovery process is being initialized with internal flags as shown. Severity Information Log LOG_ELS verbose Action No action needed, informational.
PAGE 678
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0436: Adapter not ready: hostStatus: x%x Description The adapter failed during powerup diagnostics after it was reset. Severity Error Log LOG_INIT verbose Action This error could indicate a hardware or firmware issue. If issues persist report these errors to Technical Support. lpfc_mes0442: Adapter failed to init, CONFIG_PORT, mbxStatus x%x Description Adapter initialization failed when issuing CONFIG_PORT mailbox command.
PAGE 679
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0458: Bring Adapter online Description The FC driver has received a request to bring the adapter online. This may occur when running HBAnyware. Severity Warning Log LOG_INIT verbose Action None required. lpfc_mes0460: Bring Adapter offline Description The FC driver has received a request to bring the adapter offline. This may occur when running HBAnyware. Severity Warning Log LOG_INIT verbose Action None required.
PAGE 680
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0703: Issue LUN reset to PathId: x%x, TargetId: x%x, Lun: x%x, Did: x%x Description Storport is requesting a reset of the indicated LUN. Severity Warning Log LOG_INIT verbose Action Review system configuration. Possible side-effect of cluster operations. lpfc_mes0713: Issued Target Reset to PathId:%d, TargetId:%d, Did: x%x Description Storport detected that it needs to abort all I/O to a specific target.
PAGE 681
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0729: FCP command error: ulpStatus: x%x, ulpWord[4]: x%x, XRI: x%x, ulpWord[7]: x%x Description The specified device failed an I/O FCP command. Severity Warning Log LOG_FCP verbose Action Check the state of the target in question. Remarks lpfc_mes0730 is also recorded if it is a FCP Rsp error. lpfc_mes0730: FCP response error: Flags: x%x, SCSI status: x%x, Residual:%d Description The FCP command failed with a response error.
PAGE 682
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes0747: Target reset complete: PathId: x%x, TargetId: x%x, Did: x%x Description A target reset operation has completed. Severity Warning Log LOG_FCP verbose Action Review system configuration. Possible side-effect of cluster operations. Remark See also Message 0713. lpfc_mes0748: Lun reset complete: PathId: x%x, TargetId: x%x, Lun: x%x Description A LUN reset operation has completed.
PAGE 683
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes1303: Link Up event: tag: x%x, link speed:%dG, topology (0 = Pt2Pt, 1 = AL):%d Description A link up event was received. It is also possible for multiple link events to be received together. Severity Error Log LOG_LINK_EVENT verbose Action If numerous link events are occurring, check physical connections to the FC network. Remarks lpfc_mes1304 is recorded if Map Entries > 0 and the corresponding mode and SEVERITY level is set.
PAGE 684
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes1401: Invalid tag: ContextIndex: x%x, ulpCommand: x%x Description Firmware has generated an invalid response. Severity Error Log LOG_LINK_EVENT verbose Action Review hardware configuration. Contact Emulex Technical Support. NPIV Messages (1800–1899) lpfc_mes1800: NPIV FDISC failure VPI: x%x Error x%x Reason x%x Description Virtual Port fails on a FDISC to the switch with the error and reason listed.
PAGE 685
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes1804: Removing Virtual Port: x%x VPI:x%x Description Removing Virtual Port ID. Severity Information Log LOG_NPIV verbose Action No action needed, informational. ELS Messages (1900–1999) lpfc_mes1900: x%x sends ELS_AUTH_CMD x%x with TID x%x Description An ELS_AUTH_CMD is sent. Severity Information Log LOG_FCSP verbose Action No action needed, informational.
PAGE 686
4. Troubleshooting Troubleshooting the FC/FCoE Driver lpfc_mes1905: Authentication policy change for local x%08x x%08x remote x%08x%08x Description Authentication policy has been changed. Severity Information Log LOG_FCSP verbose Action No action needed, informational. Emulex Drivers for Windows User Manual P010077-01A Rev.
PAGE 687
4. Troubleshooting Troubleshooting the NIC Drivers Troubleshooting the NIC Drivers The following table provides troubleshooting information for the NIC drivers. Table 4-3 Troubleshooting the NIC Drivers Issue Answer/Solution Performance is not as expected. The adapter may be installed in the wrong type of PCIe slot. Verify that the adapter has been properly installed. If TOE is enabled and performance is not as high as expected, the operating system may not offload TOE connections.
PAGE 688
4. Troubleshooting Troubleshooting the NIC Drivers Table 4-3 Troubleshooting the NIC Drivers (Continued) Issue Answer/Solution When running Windows Server 2008, Apply the 979614 hotfix as described on the Microsoft website.
PAGE 689
4. Troubleshooting Troubleshooting the NIC Drivers TCP Offload Failure The following table lists common reasons why TCP offloads do not occur and their suggested fixes. Table 4-4 Troubleshooting TCP Offload Failures Reasons for No TCP Offload Solutions Chimney offload is disabled on the system.
PAGE 690
4. Troubleshooting Troubleshooting the iSCSI Driver Troubleshooting the iSCSI Driver Troubleshooting the Cisco Nexus Switch Configuration Note: The LACP cannot be used on the an iSCSI port. Table 4-5 Cisco Nexus Switch Situations for iSCSI Issue Solution The system is showing an excessive number of Ensure that the LACP is not used on the I/O timeouts as a result of the switch routing iSCSI port. frames to the incorrect port.
PAGE 691
4. Troubleshooting Troubleshooting the iSCSI Driver Table 4-6 Troubleshooting the iSCSI Driver (Continued) Issue Answer/Solution The following POST error message appears: In the iSCSI BIOS, the Emulex iSCSI initiator name may be different if more than one OneConnect UCNAs are in the system. This message appears if the iSCSI initiator name is different on Initiator iSCSI Name mismatch, Please use iSCSISelect to set a single multiple controllers.
PAGE 692
4. Troubleshooting Troubleshooting the iSCSI Driver Table 4-6 Troubleshooting the iSCSI Driver (Continued) Issue Answer/Solution A login to new target fails after Microsoft iSCSI Initiator Service is installed. When Microsoft iSCSI software is installed, the service chooses a default IQN name for the UCNA. The Microsoft iSCSI service issues the request to the iSCSI driver via the WMI interface to set this new IQN name.
PAGE 693
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Viewing the FC/FCoE Error Log The system event log is a standard feature of Windows Server software. All events logged by the Emulex Storport Miniport will be Event ID 11 with source “elxfc/elxcna”. To view the error LOG: 1. Open the Event Viewer window by doing one of the following:  Click Start>Programs>Administrative Tools>Event Viewer.
PAGE 694
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Severity Scheme When the Event Viewer is launched, there are three branches: Application, Security and System. All ELXFC/ELXCNA error log entries are found under the System branch, and all ELXFC/ELXCNA error log entries have the Event Viewer severity level of “error”.    A severe error code indicates that the driver, firmware or adapter is behaving abnormally and your intervention is required to correct the issue.
PAGE 695
Appendix A.
PAGE 696
Appendix A.
PAGE 697
Appendix A.
PAGE 698
Appendix A.
PAGE 699
Appendix A.
PAGE 700
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Viewing the FC/FCoE Event Log Event Log Interpretation   All events logged by Emulex Storport Miniport are in Event ID 11 with source “elxfc/elxcna”.
PAGE 701
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs FC-CT Reject Reason Codes Codes that indicate the reason a CT command was rejected. Table A-7 FC-CT Reject Reason Codes Explanation Code Invalid command code 0x01 Invalid version level 0x02 Logical busy 0x05 Protocol error 0x07 ELS Command Codes FC protocol codes that describe what particular Extended Link Services command was sent.
PAGE 702
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Local Reject Status Codes Codes supplied by the Emulex adapter firmware which indicate why a command was failed by the adapter.
PAGE 703
Appendix A. Error and Event Log Information FC/FCoE Error and Event Logs Additional Notes on Selected Error Codes These are error codes which may be seen more frequently than others or which indicate conditions that you might be able to solve by investigation and correction of issues in the SAN configuration. Note: The nomenclature of “0x” is used as the prefix for the byte code fields because those byte codes are actually hex values.
PAGE 704
Appendix A. Error and Event Log Information NIC Error and Event Logs NIC Error and Event Logs Viewing the NIC Error Log For Windows Server operating systems, the network driver generates error codes in the system event log. These error codes can be viewed by using the Event Viewer application. To view the error codes: 1. 2. 3. 4. 5. 6. Click the Start tab on the bottom of the screen. Click Run. Type eventvwr and click OK. Click Windows Log. Click System.
PAGE 705
Appendix A. Error and Event Log Information NIC Error and Event Logs NIC Event Log Windows Device Manager generates error log codes if any errors occur during the installation of the NIC driver. Each log contains a Message Id, Severity and Symbolic Link. The Message Id is unique and tracks the error message (if not displayed). Table A-13 shows the list of error codes, the severity of the error, the message displayed, the meaning of the error and recommended resolutions.
PAGE 706
Appendix A. Error and Event Log Information NIC Error and Event Logs Table A-13 NIC Event Log Entries (Continued) Message ID Hexadecimal/ Decimal Severity Message Recommended Resolution 0x00031/49 Warning RSS is limited to 4 queues. Enable Advanced Mode in the PXE BIOS to use up to 16 queues. This may require a firmware update. Enable Advanced Mode in the PXE Select BIOS utility during boot to use up to 16 queues. This may require a firmware update.
PAGE 707
Appendix A. Error and Event Log Information NIC Error and Event Logs Table A-13 NIC Event Log Entries (Continued) Message ID Hexadecimal/ Decimal Severity Message Recommended Resolution 0x0025/37 Warning The device firmware does not support TCP offload functionality. The firmware and the driver are not compatible versions. See the Downloads section of the Emulex website for compatible firmware and drivers. 0x0024/36 Error The device firmware does not support network functionality.
PAGE 708
Appendix A. Error and Event Log Information NIC Error and Event Logs Table A-13 NIC Event Log Entries (Continued) Message ID Hexadecimal/ Decimal Severity Message Recommended Resolution 0x0014/20 Error Failed to read registry configuration. The registry is corrupted. Reinstall the driver and/or operating system. 0x0013/19 Error Resource conflict. The operating system failed to allocate resources for the device. Check low memory conditions and operating system hardware resource conflicts.
PAGE 709
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-13 NIC Event Log Entries (Continued) Message ID Hexadecimal/ Decimal Severity Message Recommended Resolution 0x0003/3 Error Unsupported medium. This is an internal NDIS error. Check the operating system installation. 0x0002/2 Error The network driver initialization failed. This may be a firmware driver mismatch or corrupt installation. Check the firmware version, reinstall the firmware and try again.
PAGE 710
Appendix A. Error and Event Log Information iSCSI Error and Event Log Figure A-2 iSCSI Error Because the UCNAs are dual PCI-function adapters, the \Device\RaidPort value changes depending on the device that observed the error. iSCSI Error Log on Windows Server 2008 The following is a brief description of the error log codes generated by the iSCSI driver for Windows Server 2008. It includes the error code, the message displayed, and the meaning of the message with the recommended resolution.
PAGE 711
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-14 iSCSI Error Log Entries on Windows Server 2008 (Continued) Message ID Message Description/Recommended Resolution 0x33900002 The iSCSI driver failed an I/O request because it failed to retrieve a scatter gather list from the Storport driver. This failure occurred due to a failed memory allocation in the operating system. Check low memory conditions.
PAGE 712
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-14 iSCSI Error Log Entries on Windows Server 2008 (Continued) Message ID Message 0x138d0101 The iSCSI driver detected an error This may indicate a target is in error or may offloading the iSCSI connection. The point to transient network connectivity issues. operation will be retried again. It may also indicate a firmware error.
PAGE 713
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-14 iSCSI Error Log Entries on Windows Server 2008 (Continued) Message ID Message Description/Recommended Resolution 0x11840002 The iSCSI driver encountered a mismatched version of the firmware running on the board. This error may be followed by error codes 0x31840001 or 0x31880001 indicating that the iSCSI driver failed to load.
PAGE 714
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x04 Error Firmware version does not match with driver version. The driver version that is running on the system does not match the version of the firmware on the UCNA. Install a driver that is compatible with the firmware.
PAGE 715
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x0e Warning iSCSI error was detected on session A, ExpCmdSn B, MaxCmdSn C. The iSCSI driver received an invalid iSCSI Command Sequence Number update from the target.
PAGE 716
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x12 Error Unrecoverable error detected. UE Low: A UE High: B FW Line: C. An unrecoverable error was detected by the iSCSI driver.
PAGE 717
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x1b Warning A configuration parameter is out of range. The iSCSI driver failed to load a configuration value specified in the registry because the value was out of range.
PAGE 718
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x24 Error Device is not supported on Windows 7 Operating System, failing driver load. The iSCSI adapter family is not supported on the Windows 7 client operating systems.
PAGE 719
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message 0x34 Warning Connection was invalidated This condition is detected by the OneConnect internally due to a bad opcode firmware. If this message is unexpected, please in the PDU header. check the iSCSI configuration.
PAGE 720
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message 0x3f Warning Command was invalidated This condition is detected by the OneConnect internally; a received PDU had firmware. If this message is unexpected, please an invalid StatusSN. check your iSCSI configuration.
PAGE 721
Appendix A. Error and Event Log Information iSCSI Error and Event Log Table A-15 iSCSI Error Log Entries on Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 (Continued) Message ID Severity Message Recommended Resolution 0x4d Warning Connection was invalidated internally; the command and data were not on the same connection. This condition is detected by the OneConnect firmware.
PAGE 722
Appendix B. Configuring iSCSI through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations Appendix B. Configuring iSCSI through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations If you are using the DHCP server to obtain an IP address for the UCNA, Emulex recommends that you set up a reservation. A reservation assigns a specific IP address based on the MAC address of the UCNA.
PAGE 723
Appendix B. Configuring iSCSI through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations Description of Mandatory and Optional Parameters Table B-1 describes the parameters used in the data string for option 43. Table B-1 Data String Parameters for Option 43 Parameter Description Field Type A valid IPv4 address in dotted decimal notation Mandatory A decimal number ranging from 1 to 65535 (inclusive). The default TCP port is 3260.
PAGE 724
Appendix B. Configuring iSCSI through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations The following is an example of default TCP port and mutual-CHAP settings: iscsi:"192.168.0.2"::"000000000000000E":"iqn.2009-4.com:1234567890" ::"E":"D":"M"         Target IP address: 192.168.0.2 Target TCP port: Use default from RFC 3720 (3260) Target boot LUN: 0x0E Target iqn name: iqn.2009-04.com:1234567890 Initiator name: Not specified.
PAGE 725
Appendix C. Port Speed Specifications Negotiating Speed on a Mezzanine Card Appendix C. Port Speed Specifications A UCNA can support only one Ethernet port speed at a time, and the preference is always for 10 Gb/s. The type of module used (copper or optical) does not make a difference. As soon as a 10-Gb module is plugged into one of the ports, the UCNA switches to a 10-Gb speed no matter what speed the other port is running, or even if I/O is running on that port.
PAGE 726
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AParg Driver Kit Parameter and Appending to the APInstall.exe File Appendix D. AutoPilot Installer Command Line and Configuration File Parameters The AutoPilot Installer can initiate an installation from a command prompt or script. AutoPilot Installer can be run manually from the command line or a script, or it can be run automatically by the driver kit.
PAGE 727
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Installer Syntax You can specify a non-default directory for the driver kit by specifying an 'installation folder' on the command line. For example: elxdrv-fc-fcoe.exe install:"C:\Emulex" This option can be used in conjunction with the “APArgs” directive.
PAGE 728
Appendix D.
PAGE 729
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Installer Syntax Note: ForceDriverUpdate applies to unattended installations only; in interactive installations this parameter is ignored. Instead you are asked if the driver should be updated.
PAGE 730
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Installer Syntax ReportLocation (Setting Up an Installation Report Title and Location) The automatically generated file name for this report is "report_mm-dd-yy.txt" where ‘mm’ is the month number, ‘dd’ is the day, and ‘yy’ indicates the year. You can change only the installation report folder; the file name is auto-generated.
PAGE 731
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Configuration File AutoPilot Configuration File The AutoPilot configuration file is organized into sections, grouped according to related commands. There are six main sections.       [AUTOPILOT.ID] – Configuration Identification [AUTOPILOT.CONFIG] – Software Configuration [STORPORT.CONFIGURATION] – Configuration Prompts/Vendor-Specific Questions [STORPORT.QFES] – QFE Checks [STORPORT.
PAGE 732
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Configuration File Software Configuration [AUTOPILOT.CONFIG] This section can contain settings that control and configure AutoPilot Installer and the OneCommand Manager application operation. This section can appear only once in the AutoPilot configuration file. See “Software Configuration Parameters” on page 728 for information about settings that may be specified in this section.
PAGE 733
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Configuration File Example of [STORPORT.CONFIGURATION] section: [STORPORT.CONFIGURATION] ;The first section contains the driver parameters common to all configurations, no matter what answers are given. DriverParameter="EmulexOption=0;" [QUESTIONS] question = "What is your link speed?", "Note: select 'Auto-detect' if you are unsure about the answer.
PAGE 734
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Configuration File path and file name This string identifies the file to be checked and its location relative to the Windows home folder. In most cases, the file to check is the Microsoft Storport driver, for example, “\system32\drivers\storport.sys”. This string is also used in dialogs and log file messages.
PAGE 735
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Installer Exit Codes AutoPilot Installer Exit Codes AutoPilot Installer sets an exit code to indicate whether an installation was successful or an error occurred. These exit codes allow AutoPilot Installer to be used in scripts with error handling.
PAGE 736
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters AutoPilot Installer Installation Reports Table D-1 Unattended Installation Error Codes (Continued) Error Code Hex Description 2399142032 0x8F000090 APInstaller encountered an error while parsing the command line (Report file contains details). AutoPilot Installer Installation Reports During each installation, AutoPilot Installer produces a report describing events that occurred during the installation.
PAGE 737
Appendix D. AutoPilot Installer Command Line and Configuration File Parameters Command Script Example goto server1ok :none if not errorlevel 1248 goto noreport echo No Emulex adapter found. goto server1ok :noreport if not errorlevel 110 goto nocfg echo Could not open installation report file. goto server1ok :nocfg if not errorlevel 87 goto badcfg echo Invalid configuration file parameters. goto server1ok :badcfg if not errorlevel 2 goto server1ok echo No appropriate driver found.
PAGE 738
Appendix E. RoCE Switch Support Overview Appendix E. RoCE Switch Support Overview Some switches do not support DCBX, and most DCBX-enabled switches do not fully support RoCE as a protocol. As of today, none of the known switch vendors (Arista, Brocade, Cisco, and Juniper) allow configuring priority for RoCE specific traffic. Additionally, most of the known switch vendors do not support APP TLV of 0x8915 for RoCE ETS bandwidth and PFC configuration.
PAGE 739
Appendix E. RoCE Switch Support DCBX-Enabled Switch Connection PFC Mode 6. Configure a valid VLAN with an ID other than 0 or 1. 7. Ensure that Jumbo Frames is enabled, or at minimum set the MTU >= 4200. 8. Specify each switch port service policy rather than using the system QoS. Notes: • • Some switches have jumbo frame size support disabled on the port and global level by default. Some switches show the priority for FCoE on the switch itself. Use a policy with zero bandwidth for the FCoE priority.
PAGE 740
Appendix E.
PAGE 741
Appendix E.
PAGE 742
Appendix E. RoCE Switch Support DCBX-Enabled Switch Connection PFC Mode Verifying Switch Configuration in OneCommand Manager Note: You do not need to configure the OCe14000-series adapter in the OneCommand Manager utility to enable RoCE with Priority Flow Control (PFC). You can use the OneCommand Manager GUI application or the OneCommand Manager CLI application to verify the switch configuration.
PAGE 743
OneCommand™ NIC Teaming and VLAN Manager Version 2.8 User Manual P009415-01A Rev.
PAGE 744
Copyright © 2003-2013 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.
PAGE 745
1. Overview 1. Overview The Emulex® OneCommand™ Network Interface Card (NIC) Teaming and Virtual Local Area Network (VLAN) Manager allows you to group multiple NICs as a single virtual device and provides the ability to team two or more NIC/vNIC ports. It also enables you to add one or more VLANs over a team or over a NIC/vNIC.
PAGE 746
1. Overview Restrictions Link Aggregation Control Protocol (LACP) – Also known as dynamic link aggregation. For more information, see “IEEE 802.3ad and LACP Team Types” on page 749.  IEEE 802.3ad static – For more information, see “IEEE 802.3ad and LACP Team Types” on page 749.
PAGE 747
1. Overview Terminology Terminology      Team – A group of available adapters working together and presented as a single adapter to applications. VLAN – A Virtual LAN allows computers or virtual machines (hypervisor guests) to act as if they are connected by a private, directly connected network. You can assign VLANs to teams or individual adapters. VLAN Bound adapter – A single adapter to which you assigned VLANs. This adapter cannot be part of a team. These are also called VLAN adapters.
PAGE 748
1. Overview Receive-Side Scaling Transmit load balancing is achieved by creating a hashing table using the hashing algorithm based on load distribution type. When the virtual teaming adapter selects a physical adapter (or port) to carry all the frames to the destination, the unique MAC address of the physical adapter is included in the frame, and not the team MAC address. This is required to comply with the IEEE 802.3 standard.
PAGE 749
1. Overview Receive-Side Scaling For Hyper-V virtual machines that use the Failover, LACP and 802.3ad team types, both the primary and secondary adapters do not have RSS support. The OCe11102 UCNA does not have this limitation and is fully supported. IEEE 802.3ad and LACP Team Types IEEE 802.3ad and Switch-Controlled Teaming (LACP) are similar to link aggregation static mode except that it uses the LACP to negotiate the ports that make up the team.
PAGE 750
2. Installing, Updating, and Uninstalling Installing the Driver and the NIC Teaming and VLAN Manager 2. Installing, Updating, and Uninstalling There are two ways to install the OneCommand NIC Teaming driver, and the NIC Teaming and VLAN Manager:   Attended installation using the GUI Unattended installation using the command line Installing the Driver and the NIC Teaming and VLAN Manager Prerequisites See Table 2-1 for Microsoft.NET Framework version requirements for your supported operating system.
PAGE 751
2. Installing, Updating, and Uninstalling Attended Installation Attended Installation Procedure To perform an attended installation: 1. From the Emulex website, download the elxdrvr-nic-teaming-.exe to your system. The installer is an executable file that self-extracts and copies the following software onto your system:  NIC Teaming driver  NIC Teaming and VLAN Manager  NIC Teaming and VLAN Manager utilities 2.
PAGE 752
2. Installing, Updating, and Uninstalling Updating the Driver and the NIC Teaming and VLAN Manager Exit Codes The Installer's Setup program returns an exit code that indicates the result of its actions. This result code is useful if you run Setup in unattended installation in a batch file, where it can be tested through the %ERRORLEVEL% variable (Windows NT4 and later only), or by using an IF ERRORLEVEL statement. An exit code of zero indicates success. A non-zero exit code indicates a failure.
PAGE 753
2. Installing, Updating, and Uninstalling Uninstalling the Driver and the NIC Teaming and VLAN Manager Uninstalling the Driver and the NIC Teaming and VLAN Manager WARNING: Use the Emulex-provided kit to uninstall the driver. Do not use a previous version of the driver utilities to uninstall the OneCommand NIC Teaming driver and NIC Teaming and VLAN Manager. Do not use Device Manager to uninstall the OneCommand NIC Teaming driver and NIC Teaming and VLAN Manager.
PAGE 754
3. Using the OneCommand NIC Teaming and VLAN Manager Starting the OneCommand NIC Teaming and VLAN Manager 3. Using the OneCommand NIC Teaming and VLAN Manager Starting the OneCommand NIC Teaming and VLAN Manager To start the OneCommand NIC Teaming and VLAN Manager, click OneCommand NIC Teaming and VLAN Manager from your Windows Start menu.
PAGE 755
3. Using the OneCommand NIC Teaming and VLAN Manager OneCommand NIC Teaming and VLAN Manager Element Definitions Menu Bar File Exit – Exits the application.  Tools Backup Current Configuration – Saves the current teaming configuration on the system. Use the Save As browser dialog box to specify a location for backing up the configuration and click Save. Restore Saved Configuration – Restores from a saved configuration. Use the browse dialog box to select a saved configuration and click Open.
PAGE 756
3. Using the OneCommand NIC Teaming and VLAN Manager OneCommand NIC Teaming and VLAN Manager Element Definitions Help button  Displays OneCommand NIC Teaming and VLAN Manager online help. Discovery-Tree The discovery-tree (left pane) has icons that represent the host machine, teams, and adapters.
PAGE 757
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information Viewing General Information Information is displayed in two ways on a General tab.   If you have a team group, adapter group, or VLAN group selected in the discovery-tree, a General tab shows a listing of that item. If you double-click on an item in the General tab’s listing, the General Information for that item is displayed in its General tab.
PAGE 758
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information Configuration Management Area     Last Restored File: The file that was used to restore the configuration last. Last Restored Date: The date and time when the last restoration was done. Last Backed-up File: The file to which the configuration was backed up last. Last Backup Date: The date and time when the last backup was made. Configuration Management buttons   Backup – Click to back up a configuration in a .
PAGE 759
3.
PAGE 760
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information 2. Select a team in the discovery-tree. The General tab for the team is displayed. Figure 3-6 General Tab Information for a Team General Tab for a Team - Field Definitions Team Properties Area       Team Type – The team type For a failover team, this area shows the Automatic Failback field. This field shows whether automatic failback is enabled. For a non-failover team (LACP, 802.
PAGE 761
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information  Native VLAN – Shows whether native VLAN is enabled. Connection Properties Area      Link Status – This field shows whether the team is functional. A link up status indicates that at least one team member is functional. A link down status indicates that no team members are functional. Link Speed – The current link speed of the team.
PAGE 762
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information 2. Select a VLAN in the discovery-tree. The General tab for the VLAN is displayed. This tab is read-only.
PAGE 763
3. Using the OneCommand NIC Teaming and VLAN Manager Viewing General Information 2. Select an adapter listed under “VLAN Adapters” in the discovery-tree. The General tab for the VLAN adapter is displayed.
PAGE 764
3. Using the OneCommand NIC Teaming and VLAN Manager Creating, Configuring, and Removing Teams  MAC Address – The NIC MAC address currently assigned to the selected adapter port Creating, Configuring, and Removing Teams A team of adapters functions as a single virtual network interface and appears the same as non-teamed adapters to other network devices. A protocol address such as an IP address is usually assigned to the physical adapter.
PAGE 765
3. Using the OneCommand NIC Teaming and VLAN Manager Creating, Configuring, and Removing Teams  It is possible for the IPv6 configuration information to be retained when a team or VLAN is deleted. If a new team or VLAN is created, it is possible this IPv6 configuration information, such as static IPv6 address, may be used with the new team or VLAN. If this behavior is observed, use the network properties dialog for the team or VLAN to correct the configuration.
PAGE 766
3. Using the OneCommand NIC Teaming and VLAN Manager Creating, Configuring, and Removing Teams GUID is be used in event log messages instead of the adapter's Friendly Name. Exceeding these limits has no other known consequences. 4. Choose a team type. Valid options:  Failover – A type of switch-independent teaming. If Failover is selected, the Automatic Failback Enabled check box is available.
PAGE 767
3. Using the OneCommand NIC Teaming and VLAN Manager Creating, Configuring, and Removing Teams   The primary adapter is labeled “Marked as Primary” and is at the top of the list in the Team Members area. If this is the adapter that you want to be primary, click Create Team. To change the primary adapter, select the adapter in the Team Members area and click Set Primary. The new primary adapter will display at the top of the adapter list and be marked as primary. Click Create Team.
PAGE 768
3. Using the OneCommand NIC Teaming and VLAN Manager Creating, Configuring, and Removing Teams  deletion from the team. If this button is not active, the secondary adapter cannot be removed. The primary adapter is labeled “primary”. To choose a different primary adapter, select the adapter in the Team Members area and click Set Primary. The new primary adapter will be marked as “primary” and the previous primary adapter will be marked as “non-primary”. The Modify Team button is available. 5.
PAGE 769
3. Using the OneCommand NIC Teaming and VLAN Manager Changing the General Settings Changing the General Settings The default global reactivation delay is the amount of seconds that an adapter must wait to carry traffic before it is allowed to rejoin its team. The reactivation delay defaults to 30 seconds and prevents jittering while the adapter stabilizes. If you change the default global reactivation delay value using the General Settings dialog box, all new teams that you create will use the new value.
PAGE 770
3. Using the OneCommand NIC Teaming and VLAN Manager Replacing a Team Adapter Replacing a Team Adapter Note: Adapters that have been disabled in either Network Connections or device Manager cannot be managed by the OneCommand NIC Teaming and VLAN Manager and may not be visible to the OneCommand NIC Teaming and VLAN Manager. Make sure that any affected adapters are enabled before making any NIC Teaming configuration changes. Note: You should not disable an adapter port that is part of an 802.
PAGE 771
3. Using the OneCommand NIC Teaming and VLAN Manager Saving a Configuration To replace a secondary adapter with one of a different model: 1. 2. 3. 4. Turn off the machine. Replace the adapter. Turn on the machine. Remove the old adapter from the team. Note: If removing the old adapter from the team will result in only one adapter, add the new adapter first, then remove the old adapter. 5. Add the new adapter to the team. Saving a Configuration To save a configuration in a text file format: 1.
PAGE 772
3. Using the OneCommand NIC Teaming and VLAN Manager Saving a Configuration configuration is saved, a confirmation message is displayed. This message shows the path and file name of the saved configuration. Click OK on this message to close it. OneCommand NIC Teaming and VLAN Manager User Manual P009415-01A Rev.
PAGE 773
3. Using the OneCommand NIC Teaming and VLAN Manager Restoring a Configuration Restoring a Configuration Restores from a saved configuration. Use the browse dialog box to select a saved configuration and click Open. A Confirmation Restoration message warns you that the current teaming configuration will be erased. Click Yes on the message to proceed. To restore a configuration from a saved configuration 1. Access the Confirm Restoration dialog box one of these ways:  From the toolbar, click Restore.
PAGE 774
3. Using the OneCommand NIC Teaming and VLAN Manager Configuring a VLAN        If you use static IP addresses (non-DHCP), you must assign IP addresses to any native VLANs and VLANs that you create. VLANs that have been disabled in either Network Connections or device Manager cannot be managed by the OneCommand NIC Teaming and VLAN Manager and may not be visible to the OneCommand NIC Teaming and VLAN Manager.
PAGE 775
3. Using the OneCommand NIC Teaming and VLAN Manager Configuring a VLAN 3. Select the VLANs tab. The VLANs tab is displayed. Figure 3-14 VLANs Tab 4. Enter a Starting VLAN ID. Valid tag values are from 1—4094. 5. Enter the number of VLANs to create. 6. Click Add VLAN to add the VLAN to the team. You can create up to 48 VLANs for a team. The Configured VLANs area shows the list of VLANs configured for the team. The VLAN Name shows the VLAN Name in the format VLAN_. 7. Click Apply.
PAGE 776
3. Using the OneCommand NIC Teaming and VLAN Manager Configuring a VLAN Configuring a VLAN Adapter To configure a VLAN adapter: 1. From the Start menu click All Programs>Emulex>OneCommand Teaming and VLAN Manager to start the application. The General tab is displayed. 2. Select an Emulex adapter from the available adapter list in the discovery-tree. 3. Select the Create VLAN Adapter tab. The Create VLAN Adapter tab is displayed. Figure 3-15 Create VLAN Adapter Tab 4. Enter a starting VLAN ID.
PAGE 777
3. Using the OneCommand NIC Teaming and VLAN Manager Configuring a VLAN Native VLANs Once a VLAN has been placed over a team or an adapter, you can still access a team or adapter directly, without going through a VLAN, if you desire. This means that the VLAN tag is 0 and this is the native VLAN. The native VLAN is disabled by default when you create the first VLAN on a team. However, you can specify whether or not to enable or disable the native VLAN.
PAGE 778
3. Using the OneCommand NIC Teaming and VLAN Manager Configuring a VLAN 6. On the Modify VLAN ID dialog box, click OK. The changes that you have specified appear in the Pending Changes list. 7. Click Apply. 8. Click Yes. The VLAN list is automatically updated with the changes. Removing a VLAN during VLAN Configuration To remove a VLAN (for a team or VLAN adapter, selected in the discovery-tree) during VLAN configuration: 1. Click the VLANs tab. 2.
PAGE 779
4. Using Teamed Adapters in Hyper-V Deleting Hyper-V Teams 4. Using Teamed Adapters in Hyper-V Exporting a team to a virtual machine allows for isolation of virtual machine traffic and allows the virtual machine to be moved to other machines without having to modify the virtual machine. Note: The use of VLANs is not supported under Hyper-V. In Hyper-V environments only NIC Teaming's Native VLAN should be used.
PAGE 780
5. OneCommand NIC Teaming Manager Command Line Interface Introduction 5. OneCommand NIC Teaming Manager Command Line Interface Introduction The OneCommand™ NIC Teaming Manager Command Line Interface (OCTeamCmd) is a companion to the OneCommand NIC Teaming and VLAN Manager. Use the OCTeamCmd in scripted operations from within shell scripts or batch files. Each time you run this application from the command line, a single operation is performed. The first parameter of this command is the requested operation.
PAGE 781
5. OneCommand NIC Teaming Manager Command Line Interface Syntax Rules Network Connection Names Windows assigns each adapter, team and VLAN a Network Connection Name. In most versions of Windows the name defaults to the form of “Local Area Connection N”. To view the Network Connection Name from the desktop: 1. Select: All Programs>My Network Places. 2. Right-click the adapter and click Properties. The Network Connection Name is labeled by the operating system in a format similar to Local Area Connection #N.
PAGE 782
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value 0x00000000 Description 0 No errors. 0x8F000001 -1895825407 2399141889 The OneCommand NIC Teaming and VLAN Manager is running. The OneCommand NIC Teaming and VLAN Manager and the OCTeamCmd utility cannot run at the same time.
PAGE 783
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value Description 0x8F000013 -1895825389 2399141907 No teams exist on the system. 0x8F000014 -1895825388 2399141908 There is an invalid number of command arguments. 0x8F000015 -1895825387 2399141909 Required data is not found on the command line.
PAGE 784
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value Description 0x8F00002B -1895825365 The primary adapter is not an Emulex adapter. 2399141931 A non-Emulex adapter was set as the primary adapter. 0x8F00002C -1895825364 2399141932 The adapter's link is not enabled by the calling function.
PAGE 785
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value 0x8F00003D -1895825347 2399141949 The number of teams configured is already at the maximum allowed. 0x8F00003E -1895825346 2399141950 The number of VLANs configured is already at the maximum allowed.
PAGE 786
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value 0x8F000050 -1895825328 2399141968 A timeout occurred while waiting for Windows to complete the creation of a VLAN. The creation may have happened, but it did not happen within 5 minutes.
PAGE 787
5. OneCommand NIC Teaming Manager Command Line Interface Error Codes Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value 0x8F000065 -1895825307 2399141989 The adapter is not bound to team or the adapter is not a bound adapter. 0x8F000066 -1895825306 2399141990 The adapter is not a member of a team or the adapter is not a member of the team and it set as the primary member.
PAGE 788
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Table 5-1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes (Continued) Hexadecimal Error Code Signed Unsigned Decimal Value Decimal Value 0x8F00007A -1895825286 2399142010 Device Manager reports that the team is disabled or cannot be found. 0x8F00007B -1895825285 2399142011 The driver failed to start. 0x8F00007C -1895825286 2399142012 Unable to obtain a handle to NDIS.
PAGE 789
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters command An optional parameter that specifies the name of the CLI command. Use this argument to show help for a specific command. Description The OCTeamCmd.exe help command without any parameters or with the command line options of “help”, “/h” or “/?” lists the utility’s version and all OCTeamCmd commands. Example of Help With No Optional Command c:\Program Files\Emulex\NIC Teaming>OcTeamCmd.
PAGE 790
5.
PAGE 791
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Backing Up the NIC Teaming Configuration Syntax OCTeamCmd.exe backup Parameters filename The name of the backup file that is created. Description This command stores a backup of the current NIC teaming configuration in the specified file. If the specified file exists, the command returns an error. You can include a directory path in addition to the filename.
PAGE 792
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Restoring the NIC Teaming Configuration Syntax OCTeamCmd.exe restore Parameters filename The NIC Teaming and VLAN configuration is restored from this file that was created using the backup option. Description This command replaces current NIC teaming configuration with the configuration found in the specified backup file.
PAGE 793
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Showing NIC Teaming and VLAN Configurations Syntax OCTeamCmd.exe show Parameters None. Description This command shows a summary of the overall NIC teaming and VLAN configurations. Note: Network adapters are considered “bound” when they are part of the network team or VLAN adapter. Adapters that are not part of your network team or not part of a VLAN adapter are considered “unbound”.
PAGE 794
5.
PAGE 795
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Link Speed: 10.0 Gbps TOE: disabled Members: Emulex OneConnect OCe11102-N-X, NIC/TOE - Ethernet 3 (Primary) MTU: 1500 Emulex OneConnect OCe11102-N-X, NIC/TOE #2 - Ethernet 4 (Secondary) MTU: 1500 VLANs: VLAN_Native IPV4: 172.20.205.101 IPV6: fe80::ada4:acb8:46d8:f4e8%71 IPV6: c900:172:20:204:ada4:acb8:46d8:f4e8 Packet Sent: 318 Packets Received: 18219 Showing VLAN Adapters Syntax OCTeamCmd.
PAGE 796
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference IPV4: 172.30.101.179 IPV6: fe80::4c32:804c:90c6:2754 IPV6: c900:172:30:101:4c32:804c:90c6:2754 Packet Sent: 237 Packets Received: 42 Showing Free Adapters Syntax OCTeamCmd.exe show freeadapters Parameters None. Description This command shows a listing of adapters that are not assigned to a team and do not have any assigned VLANs. Adapters are identified using their name, network manager (network connection name) and alias.
PAGE 797
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters team-id Team name. adapter-id Adapter alias assigned by OCTeamCMD. network-connection-name This name is not stored by OCTeamCMD. This name is maintained by Windows. vlan-id An optional parameter that specifies the number used as the VLAN tag. Description This command shows details about a team or an adapter.
PAGE 798
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Used VLAN IDs: 101, 102, 103 Available VLAN IDs: VLAN_Native, 1-100, 104-4094 Showing the Global Reactivation Delay Default Syntax show reactdelay Parameters None. Description This command shows the global default reactivation delay that is used when creating teams. The default delay value is 30 seconds and is shown in milliseconds. Example c:\Program Files\Emulex\NIC Teaming>OcTeamCmd.
PAGE 799
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters auto-failback-setting fbenabled or fbdisabled hash Hash algorithm Description This command creates a team. The team-name is the name for the team that is to be created. The name cannot exceed 79 characters and must be unique. The adapters listed as part of the team must not be part of another team and must not have VLANs assigned to them.
PAGE 800
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Example c:\Program Files\Emulex\NIC Teaming>OcTeamCmd.exe create team failover :fbenabled myteam nic5 nic6 Successfully created team: myteam WARNING: The MTU sizes of some of the team member adapters are not matching. As a result, the team will use the least MTU. Also, TOE will be disabled. Deleting a Team Caution: Removing a team may take several minutes.
PAGE 801
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters team-id Team from which an adapter is to be added. adapter-id Adapter to be added. Description This command adds a specified adapter from the specified team. The adapter can only be added if the team currently has less than the maximum number of adapters for that team type. For more information about adding an adapter, see “Replacing a Team Adapter” on page 770.
PAGE 802
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters team-id Team from which an adapter is to be removed. adapter-id Adapter to be removed. Description This command removes the specified adapter from the specified team. The adapter can only be removed if the team will be left with the minimum number of adapters for that team type. Example c:\Program Files\Emulex\NIC Teaming>octeamcmd.
PAGE 803
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Parameters team-id If a VLAN is to be assigned to a team, this is the team name. adapter-id If a VLAN is to be assigned to an adapter, this is the adapter alias. vlan-id The number to be used as the VLAN tag. Valid values range from 1 to 64. number An optional parameter that specifies the total number of VLANs to be assigned. Valid values range from 1 to 4.
PAGE 804
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Modifying a VLAN ID Syntax # OcTeamCmd.exe modify vlan Successful condition Successfully modified the VLAN ID from to Error Conditions VLAN ID is already assigned to . Invalid VLAN value specified. Example # OCTeamcmd.exe modify vlan LACPTeam 333 444 Deleting a VLAN Note: Do not remove a team or VLAN while they are carrying traffic.
PAGE 805
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference sequentially follow the VLAN ID of the first VLAN. If any of these VLANs do not exist, then no VLANs specified in the command are deleted. Single VLANs may also be deleted by specifying their VLAN ID without the optional number of VLANs to delete. Example Delete from team c:\Program Files\Emulex\NIC Teaming>OcTeamCmd.
PAGE 806
5. OneCommand NIC Teaming Manager Command Line Interface The Command Reference Default reactivation delay of 45 seconds is successfully set c:\Program Files\Emulex\NIC Teaming> Setting the Reactivation Delay of an Existing Team Syntax set reactdelay Parameters delay value Delay value in seconds. Valid values range from 1 to 200. team-id The name of the team that will use the global reactivation delay value.
PAGE 807
Appendix A. Load Balancing Use Cases Perceived Port Load Appendix A. Load Balancing Use Cases Perceived Port Load This method automatically distributes TCP/IP traffic across team member channels by examining traffic load history patterns. When to Use Favorable types of traffic patterns for this balancing method include web traffic (HTTP, HTTPS) and e-mail traffic (SMTP, POP3).
PAGE 808
Appendix A. Load Balancing Use Cases Destination IP When Not to Use If the client, laptop or desktop systems are located on different IP subnets and IP routing is required to reach them (from the server), this method is typically not a good fit. When the Ethernet frames sent from the server system's NIC team to the IP router (often a single gateway) all have the same constant destination MAC address (that of the IP router), this method does not distribute traffic well.
PAGE 809
Appendix B. NIC Teaming Driver Event Log Appendix B. NIC Teaming Driver Event Log The event log is a standard feature of Windows Server software. 1. Click Start>Run. The Run dialog box is displayed. In the Run dialog box, type: eventvwr 2. 3. 4. 5. Click OK. Click Windows Log. Click System. Click the EMLX error under System Events to show the event details. Table 5-3 shows event log entry detail.
PAGE 810
Emulex® Drivers Version 10.2 for Linux User Manual P010081-01A Rev.
PAGE 811
Copyright © 2003-2014 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.
PAGE 812
1. Introduction Overview 1. Introduction Overview This Emulex® Drivers Version 10.2 for Linux manual provides installation, updating, uninstalling, configuring, and troubleshooting procedures for several types of Emulex-supported drivers for Linux. This manual is applicable to several versions of Linux drivers, operating systems, firmware, and adapters.   For supported firmware versions and their latest release, see the “Downloads” page on the Emulex website for the specific adapter.
PAGE 813
1.
PAGE 814
1.
PAGE 815
1.
PAGE 816
2. Installing and Uninstalling General Installation Requirements 2. Installing and Uninstalling Emulex releases Linux binary RPMs that are digitally signed using the GNU Privacy Guard (GPG) standard. This will allow certification of the contents of the RPMs and verification that the contents have not been modified since they were created by Emulex. The RPMs have been digitally signed by Emulex with a GPG private key that is only held by Emulex.
PAGE 817
2. Installing and Uninstalling Binary RPM FC and FCoE Driver Kit To install the binary RPM FC and FCoE driver: 1. Download the appropriate driver kit from the Emulex website. 2. Log in as “root” to a terminal, and unpack the tarball: tar xzf elx-lpfc-dd--.tar.gz 3. Change to the directory that is extracted: cd elx-lpfc-dd--/ 4. Run the elx_lpfc_install.sh script without options to install the driver kit: .
PAGE 818
2. Installing and Uninstalling Ethernet Driver Kit Ethernet Driver Kit The Ethernet driver kit includes the driver that supports the NIC protocol. The Ethernet driver kit contains the following:  A zipped tar file that includes the driver binary RPMs for a specific driver version, and for all of the supported Linux distribution kernels. Note: Use only officially-released Linux distribution kernels.
PAGE 819
2. Installing and Uninstalling Ethernet Driver Kit Uninstalling the Ethernet Driver Kit Note: You must run the uninstall script that shipped with the version of the driver kit you want to remove. To uninstall the Ethernet driver: 1. Log in as “root”. 2. If possible, exit all applications that use Ethernet-attached drives, then unmount the drives. If you cannot exit all applications that use Ethernet-attached drives, the uninstall works properly, but you must reboot after the uninstallation is complete. 3.
PAGE 820
2. Installing and Uninstalling iSCSI Driver Kit iSCSI Driver Kit Previously, Emulex provided a proprietary iSCSI driver as the out-of-box driver for all Linux operating systems. The Open-iSCSI driver was available inbox only. For RHEL 6.4 and SLES 11 SP2 and later drivers, Emulex is transitioning the Open-iSCSI driver to be the out-of-box driver. For RHEL 5.x, the out-of-box driver will continue to be the proprietary driver. The iSCSI driver kit includes the driver that supports the iSCSI protocol.
PAGE 821
2. Installing and Uninstalling Booting from a Non-Zero LUN Attached to an Emulex LPFC Adapter  For SAN boot with a SLES operating system, kernel parameter withiscsi=1 should be passed during installation. Since this driver is based on Open-iSCSI, attempting to perform a SAN-boot without these dependencies will fail. To install the iSCSI driver: 1. Download the appropriate driver kit from the Emulex website. 2.
PAGE 822
2. Installing and Uninstalling OneCommand Manager Application OneCommand Manager Application The OneCommand Manager application is a powerful and centralized adapter management suite. It provides discovery, reporting, and management of local and remote adapters from a single console anywhere in the SAN and across platforms. Both a GUI and CLI are provided.
PAGE 823
3. Configuration FC and FCoE Driver Configuration 3. Configuration FC and FCoE Driver Configuration FC and FCoE Driver Parameters Note: The FC and FCoE driver parameters determine some aspects of the driver’s behavior. There are two main types, static and dynamic. Changes to the static parameters require a driver reload for the change to take effect. Changes to most dynamic parameters take effect immediately; some do not take effect until there is a link-down/link-up sequence.
PAGE 824
3. Configuration FC and FCoE Driver Configuration Table 3-1 Static FC and FCoE Driver Parameters (Continued) Parameter sysfs Visible Description lpfc_enable_hba_heartbeat When enabled, the heartbeat logic in the FC and FCoE driver is able to detect whether the adapter is functional. If the heartbeat logic detects the adapter is not functional, the driver will shut down the adapter. The enabled value is 1 (default). Yes The disabled value is 0.
PAGE 825
3. Configuration FC and FCoE Driver Configuration Table 3-1 Static FC and FCoE Driver Parameters (Continued) sysfs Visible Parameter Description lpfc_max_luns Specifies the highest available LUN ID that is valid, per target. For example, a value of 19 means that LUN IDs from 0 to 19 are valid for the target. The SCSI layer scans each target until it reaches this specified LUN ID. Yes The minimum value is 0. The maximum value is 65535. The default value is 255.
PAGE 826
3. Configuration FC and FCoE Driver Configuration Table 3-1 Static FC and FCoE Driver Parameters (Continued) sysfs Visible Parameter Description lpfc_use_msi When enabled, determines whether the driver uses MSI or MSI-X. • 0 = MSI disabled; INTx mode is used (default for the FC RHEL5.x driver). • 1 = MSI; allows a maximum of 32 interrupts. • 2 = MSI-X; allows a maximum of 2048 interrupts (default for FC RHEL6.x/SLES11-SPx drivers).
PAGE 827
3. Configuration FC and FCoE Driver Configuration Table 3-2 Dynamic FC and FCoE Driver Parameters (Continued) Parameter Description lpfc_fcp_io_sched For LPe16000 and LPe15000 series adapters using RHEL6.x/SLES11-SPx drivers, determines which algorithm to use when scheduling an FCoE I/O to an I/O channel. For more information, see “LPFC Driver Performance Tuning” on page 865. The default value is 0, configuration by round-robin scheduling. A value of 1 sets configuration to CPU scheduling.
PAGE 828
3. Configuration FC and FCoE Driver Configuration Table 3-2 Dynamic FC and FCoE Driver Parameters (Continued) Parameter Description lpfc_topology For FC adapters, this parameter sets the link topology. The possible values are: • 0x0 = loop first; if loop fails, then point-to-point (default) • 0x2 = point-to-point only • 0x4 = loop only • 0x6 = point-to-point first; if point-to-point fails, then loop Note: For FCoE adapters, this parameter is not applicable and has no effect.
PAGE 829
3. Configuration FC and FCoE Driver Configuration Persistent Configuration with modprobe.conf or lpfc.conf For the FC RHEL5.x driver, to make the FC and FCoE driver parameters persist across module loads and reboots, modify the /etc/modprobe.conf file. The FC and FCoE driver parameters are specified in /etc/modprobe.conf via the “options” command. For example, the following command sets the verbose flag: options lpfc lpfc_log_verbose=0xffffffff For FC RHEL6.
PAGE 830
3. Configuration FC and FCoE Driver Configuration driver parameters.
PAGE 831
3. Configuration FC and FCoE Driver Configuration To create a new initial ramdisk image for inbox FC and FCoE drivers and installed binary RPM FC driver kits:  For RHEL 5.x distributions, type mkinitrd -f /boot/initrd-.img  For RHEL 6.x distributions, type dracut -f /boot/initramfs-.
PAGE 832
3. Configuration FC and FCoE Driver Configuration Configuring the System to Boot Using Persistent Names For SLES 11 SPx Note: SLES 11 SPx is configured by default with udev to provide persistent names for hard disks, including FC-attached disks. To use a persistent name for a boot device with SLES 11 SPx: 1. In /boot/grub/menu.lst, find the kernel line for the default boot. For example: kernel /boot/vmlinuz root=/dev/sda2 vga=0x314 2.
PAGE 833
3. Configuration FC and FCoE Driver Configuration information elements to build the unique ID. The following are examples of each scenario. FC Tape Device Examples The following examples use the scsi_id command to retrieve and generate a unique SCSI identifier: scsi_id [options] For these examples, the following [options] are used:   Treats the device as white listed. It is needed on the command line or in the scsi_id.config file for the scsi_id command to generate any output.
PAGE 834
3.
PAGE 835
3. Configuration FC and FCoE Driver Configuration Create a new file named /etc/udev/rules.d/45-local.rules and put the appropriate rule in it. Then run “udevtrigger” to reload the udev rules, and the output of the rules will follow: udevtrigger ls -al /dev/fc* lrwxrwxrwx 1 root root 3 Apr 7 15:03 fc_lun_st0 -> st0 lrwxrwxrwx 1 root root 3 Apr 7 15:03 fc_lun_st1 -> st1 Persistent Naming References See the following references for more information on persistent naming:   http://www.reactivated.
PAGE 836
3. Configuration Ethernet Driver Configuration Ethernet Driver Configuration Ethernet Driver Configuration Parameters The Ethernet driver supports the user-configurable parameters described in Table 3-3. Table 3-3 Ethernet Driver Configuration Parameters Parameter Description num_vfs In systems supporting SR-IOV, when IOV is enabled, this parameter indicates the number of VFs to be enabled per PF. For configuring SR-IOV, see “SR-IOV Configuration” on page 838.
PAGE 837
3. Configuration Ethernet Driver Configuration Support for Ethtool set/get-channels The Ethtool get-channels command is available in kernel versions of RHEL 6.4, SLES 11.2, and 3.0.x and higher.
PAGE 838
3. Configuration Ethernet Driver Configuration SR-IOV Configuration Introduction This section contains requirements and instructions to use SR-IOV with the following host operating systems:      Red Hat Enterprise Linux 6.3 - 64-bit KVM Red Hat Enterprise Linux 6.4 - 64-bit KVM Red Hat Enterprise Linux 6.
PAGE 839
3. Configuration Ethernet Driver Configuration Setting Up SR-IOV Note: Currently, SR-IOV is supported only in non-multichannel setups. Prerequisites To set up SR-IOV on your system, you need the following:  A server/blade with an SR-IOV-capable motherboard BIOS. Note: Configuration mechanisms for parameters such as MAC address, VLAN and QoS for VF are supported in RHEL 6 and above, and SLES 11 and above distributions.
PAGE 840
3.
PAGE 841
3. Configuration Ethernet Driver Configuration Notes:   On 4-port OCx11104 adapters, VFs can be configured only for ports 0 and 1, not for ports 2 or 3. VFs are supported for network functions only; they are not supported for storage functions. Table 3-5 Total VF Counts that are Supported for Various Adapter Configurations Adapter Configuration Number PF of Ports Count 2 VF Count per ASIC Comments OCe11102 2-port 10Gb NIC, stand-alone adapter 2 60 Per port VF count is 30.
PAGE 842
3. Configuration Ethernet Driver Configuration Detach desired VFs: # virsh nodedev-dettach pci_0000_16_04_0 Device pci_0000_16_04_0 detached <-- VF LOM Port 0 (Function 0) # virsh nodedev-dettach pci_0000_16_08_0 Device pci_0000_16_08_0 detached <-- VF LOM Port 1 (Function 1) Example 2 (using only one VF per physical port): SLES 11.x Xen: - View Emulex PCI devices with the lspci command: # lspci | grep Emulex 16:00.
PAGE 843
3. Configuration Ethernet Driver Configuration Edge Virtual Bridging The OCe14000-series chip supports both VEB and tagless VEPA modes. VEB mode is enabled by default in the chip. Switching to VEB/VEPA mode can be done using the Emulex OneConnectTM Manager utility.
PAGE 844
3. Configuration Ethernet Driver Configuration MAC Address Configuration The OneConnect adapter or LightPulse CFA in FCoE+NIC mode is shipped with factory-configured MAC addresses for the network interfaces corresponding to the PFs. The driver generates random MAC addresses for the network interfaces corresponding to the VFs based on the factory-configured MAC address. Other MAC addresses can be assigned for the interfaces corresponding to the VF using IP utility commands in the hypervisor.
PAGE 845
3. Configuration Ethernet Driver Configuration Note: Transparent VLAN tagging does not occur on any VLAN packets that are sent with VLAN configuration mode in the guest operating system on the VF. Transmission Rate Configuration Configure the transmission rate limit (TX-RATE) on a VF interface from the hypervisor using the following IP command syntax: # ip link set eth vf rate where:    eth is the interface corresponding to the physical function.
PAGE 846
3. Configuration Ethernet Driver Configuration vf 0 MAC 00:00:c9:9d:90:80, tx rate 10000 (Mbps) vf 1 MAC 00:00:c9:9d:90:81, tx rate 10000 (Mbps) ARI Considerations for OCe14000-Series Adapters Alternative routing-ID interpretation (ARI) is supported on the OCe14000-series adapters. The maximum number of functions allowed on an adapter is controlled by the adapter's IPL file and the system’s support for ARI.
PAGE 847
3. Configuration Ethernet Driver Configuration NIC Partitioning (NPar) Configuration (Dell Only) Notes:    NPar support is only available on OCe14000-series adapters running in 10 Gb mode. NPar is only supported on Dell 13G or newer systems. SR-IOV must be disabled on the adapter BIOS when NPar is used. See the following documentation for information on disabling SR-IOV on the adapter BIOS:  To configure SR-IOV using the adapter BIOS, see the Boot for NIC, iSCSI, FCoE, and RoCE Protocols User Manual.
PAGE 848
3. Configuration Ethernet Driver Configuration The following items are supported on a per-partition basis:     Per-partition statistics LSO, LRO, RSS, and TSO needed per partition MTU per partition Support for NetQueues Using NParEP Notes:     NParEP is available only on OCe14000-series adapters. On a four-port adapter, ARI functionality must be enabled in the PCIe subsystem on a particular system to support NParEP on all four ports.
PAGE 849
3. Configuration iSCSI Driver Configuration iSCSI Driver Configuration Open-iSCSI Support Open-iSCSI is a high-performance, transport independent, multi-platform implementation of Request for Comments (RFC) 3720. The inbox Open-iSCSI driver is supported. However, for distributions of Linux versions RHEL 5.x and for versions earlier than RHEL 6.3 and SLES 11 SP2, the inbox driver does not support ISNS or iSCSI boot due to limitations in Open-iSCSI distribution tools.
PAGE 850
3. Configuration iSCSI Driver Configuration iscsiadm -m host --print=4 Example output: Host Number: 8 State: running Transport: be2iscsi Initiatorname: IPaddress: HWaddress: 00:00:c9:f2:73:8d Netdev: Host Number: 9 State: running Transport: be2iscsi Initiatorname: IPaddress: HWaddress: 00:00:c9:f2:73:91 Netdev: 4. Display the information for all Ethernet interfaces. ifconfig -a Example output: eth0 Link encap:Ethernet HWaddr 00:25:B3:DF:8D:AC inet addr:10.
PAGE 851
3. Configuration iSCSI Driver Configuration BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.
PAGE 852
3. Configuration iSCSI Driver Configuration be2iscsi.00:00:c9:f2:73:91 be2iscsi,00:00:c9:f2:73:91,,, "This is the interface for which IP was set using iSCSI Select" be2iscsi.00:00:c9:f2:73:8d be2iscsi,00:00:c9:f2:73:8d,,, bnx2i.00:00:00:00:00:00 bnx2i,00:00:00:00:00:00,,, 8. Discover the targets using the Ethernet interface for which the IP was set. iscsiadm -m discovery -t st -p 192.168.65.196:3260 -I be2iscsi.
PAGE 853
3. Configuration iSCSI Driver Configuration Login to [iface: be2iscsi.00:00:c9:f2:73:91, 192.168.65.196,3260] successful. Login to [iface: be2iscsi.00:00:c9:f2:73:91, 192.168.65.196,3260] successful. Login to [iface: be2iscsi.00:00:c9:f2:73:91, 192.168.65.196,3260] successful. Login to [iface: be2iscsi.00:00:c9:f2:73:91, 192.168.65.196,3260] successful. target: iqn.tgt6, portal: target: iqn.tgt4, portal: target: iqn.tgt2, portal: target: iqn.tgt5, portal: 10.
PAGE 854
3. Configuration iSCSI Driver Configuration SLES 11 SP1, RHEL 5.8, and Later Versions Discovering and Adding iSCSI Targets The following steps are used to discover and add a target using the Ethernet adapter for SLES 11 SP1, RHEL 5.8, and later versions. 1. For the iSCSI function, set the IP address using the iSCSI Select utility.  The initiator IP is set to 192.168.65.99. This IP is set for the iSCSI function, but it does not get set for the Ethernet interface.  The target portal IP is 192.168.65.196.
PAGE 855
3. Configuration iSCSI Driver Configuration In this command, is the IP address and port number and is the name of the iface created in step 1. 6. Add the iSCSI driver MAC address: iscsiadm -m iface -I --op=update -n iface.hwaddress -v In this command, is the name of the iface created in step 1. 7. Set the initiator’s IP address: iscsiadm -m iface -I -o update -n iface.
PAGE 856
3. Configuration iSCSI Driver Configuration Perform the following steps to discover targets using iSNS through the NIC interface: 1. Ensure that a ping to the iSNS server IP from the initiator machine is successful through the NIC interface. 2. Run the discovery command: iscsiadm -m discoverydb -t isns -p -I default --discover -P 1 For example: iscsiadm -m discoverydb -t isns -p 10.192.204.116 -I default --discover -P1 Example output: Target: iqn.tgt:TGT1 Portal: 192.168.65.
PAGE 857
3. Configuration Virtual Port (VPort) Configuration Virtual Port (VPort) Configuration VPort Configuration Prerequisites Before configuring VPorts, consider the following points:  Ensure you are using the latest recommended firmware for VPort functionality. Check the Emulex website for the latest firmware. Note: Before performing a firmware update, driver installation is required. See “Installing and Uninstalling” on page 816.
PAGE 858
3. Configuration Virtual Port (VPort) Configuration simultaneously. If you are running a loop topology and you create a VPort, the VPort’s link state will be offline. Deleting VPorts Using the rmvport.sh Script Note: You must un-map, un-mount, and flush I/Os to VPort-connected devices before deleting the VPort. You can use the rmvport script to delete VPorts. To see the usage information, run the script with no parameters specified. The rmvport.sh script uses the following syntax: ./rmvport.
PAGE 859
3. Configuration Virtual Port (VPort) Configuration /sys/class/fc_host/hostY/ Creating a new VPort also creates a new sysfs directory in the bus and devices tree: ls /sys/bus/pci/drivers/lpfc/0000:07:00.0/host8/ fc_host:host8 host10 power scsi_host:host8 uevent ls /sys/bus/pci/drivers/lpfc/0000:07:00.0/host8/host10 fc_host:host10 power scsi_host:host10 uevent In this example, host 8 is the physical port, and host 10 is a VPort that was created on host 8. For FC RHEL6.
PAGE 860
3. Configuration Virtual Port (VPort) Configuration VPort sysfs Entries Note: VPort sysfs entries in Table 3-7 are only present if the driver was loaded with lpfc_enable_npiv enabled. Table 3-7 VPort sysfs Entries VPort sysfs Entries Type lpfc_peer_ port_login Read/ Write Range /Input Location and Description 0=Off(default) /sys/class/scsi_host/hostX/lpfc_peer_port_login 1=On This entry sets the port’s behavior when discovering targets in the SAN.
PAGE 861
3. Configuration Virtual Port (VPort) Configuration Table 3-7 VPort sysfs Entries (Continued) VPort sysfs Entries node_name Type Readonly Range /Input 16-byte hexadecimal value Location and Description For the FC RHEL5.x driver: /sys/class/fc_host/hostX/node_name For FC RHEL6.x/SLES11-SPx drivers /sys/class/fc_host/hostX/node_name/sys/class/fc _vports/vport-X:0-Z/node_name These entries display the physical or VPort's node name.
PAGE 862
3. Configuration Virtual Port (VPort) Configuration Table 3-7 VPort sysfs Entries (Continued) VPort sysfs Entries vport_delete Type Range /Input Location and Description Write- WWPN; WWNN /sys/class/fc_host/hostX/vport_delete only This entry deletes a VPort on the physical port that hostX is located on. The VPort matching the WWPN and WWNN is immediately deleted. This entry returns a “0” if the VPort deletion was successful. A non-zero value indicates that the VPort was not deleted.
PAGE 863
3. Configuration Virtual Port (VPort) Configuration /sys/devices/pci00:03/00:03:06.1/host5/vport-5:0-0/host6/rport-6:0-2: power target6:0:0 uevent In this example:    There is a new entry in the fc_vports directory for the VPort (vport-5:0-0). The vport-5:0-0 entry indicates that the VPort was created from host5 and it is the first (0) VPort to be created on that fc_host. The new host for the VPort is host6, and it will appear in the usual directories. There is also a new directory in the bus tree.
PAGE 864
3. Configuration DHCHAP Authentication and Configuration DHCHAP Authentication and Configuration Note: This section is applicable to the FC RHEL5.x driver only. To activate FC-SP/Authentication between the adapter host port and fabric F_Port using DHCHAP, modify the DHCHAP-associated driver properties in the driver configuration file. The LPFC driver for Linux version RHEL5.x supports MD5 and SHA-1 hash functions and supports the following DH groups: Null, 1024, 1280, 1536, and 2048.
PAGE 865
3. Configuration LPFC Driver Performance Tuning   restart - The restart command stops the fcauthd daemon and then restarts it. condrestart - The conditional restart command checks the status of the fcauthd daemon. If it is running, it issues a stop and then a start command. If the fcauthd daemon is not running, nothing happens. lpfc_enable_auth Module Parameter Use the lpfc_enable_auth module parameter to enable or disable authentication support.
PAGE 866
3. Configuration LPFC Driver Performance Tuning supporting parallel I/O paths, and each I/O path is capable of posting and completing FCP commands independent of the other. OneConnect and LPe16000 and LPe15000 series adapters that are running in MSI-X interrupt mode can use more than one I/O path. Each I/O channel is composed of a unique MSI-X vector- EQ/CQ/WQ tuple. This parameter will override the value of the lpfc_fcp_eq_channel and the lpfc_fcp_wq_count parameters.
PAGE 867
3. Configuration LPFC Driver Performance Tuning By default, the module parameter is configured for 50,000 interrupts per second per adapter port. lpfc_vector_map.sh The lpfc_vector_map.sh script uses kernel sysfs entry points to map a specific I/O channel (MSI-X vector-EQ/CQ/WQ tuple) to a specific CPU. The script should be run immediately after the driver is loaded. This script resides in /usr/sbin/lpfc. The recommended way to run this script is by adding the following line to /etc/modprobe.d/lpfc.
PAGE 868
3. Configuration Network Performance Tuning Network Performance Tuning Memory Bandwidth Considerations The availability of higher memory bandwidth leads to better network performance. The following sections describe how memory bandwidth can be increased. Enabling Optimal Bandwidth Options Most computers offer multiple distinct memory channels, or memory interleaves, which may not be enabled by default.
PAGE 869
3. Configuration Network Performance Tuning echo 64000000 > /proc/sys/net/core/rmem_max echo 32000000 > /proc/sys/net/core/wmem_default echo 32000000 > /proc/sys/net/core/wmem_max These settings assume ideal conditions such as low latency, zero (or close-to-zero) packet loss in the network, enough free memory, and 10 Gb/s path-to-peer system. These tcp_rmem and tcp_wmem values are also the default values in recent RHEL 5 distributions.
PAGE 870
3. Configuration Network Performance Tuning If the PCIe bus does not provide 10 Gb/s of throughput due to chipset limitations or the bus width, the adapter cannot maintain 10 Gb/s of incoming receive data. It starts dropping packets quickly. In this situation, it may be beneficial to enable receive flow control in the adapter, and enable flow control in the attached switch for all devices. This helps to slow down the transmitters.
PAGE 871
3. Configuration Network Performance Tuning ethtool –K eth gro off LRO can be disabled using the –C option with the ethtool command: ethtool -C eth rx-frames 1 where eth is the name of the Ethernet device you are working on (for example, eth0). Maximum Transmission Unit (MTU) The Ethernet driver supports MTUs between 256 bytes and 9000 bytes. The default MTU is set to 1500.
PAGE 872
3. Configuration Network Performance Tuning For receive interrupts, disable AIC (since it is enabled by default) and set the interrupt delay duration using ethtool. For example, to disable AIC and set the constant RX interrupt delay to 8 microseconds, run ethtool -C eth adaptive-rx off rx-usec 8 where eth is the number of the Ethernet interface you are working on. If your application requires low or predictive latency, Emulex recommends that you turn off AIC and set rx-usecs to 0.
PAGE 873
3. Configuration Network Performance Tuning Transmit/Receive Queue Statistics, on page 976. Turning off auditing and SELinux can improve CPU utilization, and in some cases increase throughput. You can disable auditing by appending audit=0 in the boot command line. You can turn off SELinux by specifying selinux=0 in the boot command line. For example, the following command boots the Linux kernel with the SELinux and auditing options disabled: kernel /boot/vmlinux-2.6.
PAGE 874
4. Troubleshooting Situations and their Resolutions 4. Troubleshooting Situations and their Resolutions This section explains some of the situations in which your system may operate in an unexpected manner, and some possible resolutions. FC and FCoE Driver Situations and their Resolutions Table 4-1 lists the FC and FCoE driver situations and their resolutions. Table 4-1 FC and FCoE Driver Situations and their Resolutions Situation Resolution FC link fails to come up.
PAGE 875
4. Troubleshooting Situations and their Resolutions Table 4-1 FC and FCoE Driver Situations and their Resolutions (Continued) Situation Resolution rmmod fails to unload driver due to device or resource busy. This message occurs when you attempt to remove the driver without first stopping the OneCommand Manager application or the fcauthd daemon when the OneCommand Manager application is installed and running, or when FC disks connected to a LightPulse adapter are mounted.
PAGE 876
4. Troubleshooting Situations and their Resolutions Table 4-1 FC and FCoE Driver Situations and their Resolutions (Continued) Situation Resolution Unloading the FC and FCoE driver on These messages are normal output from the SLES 11 SPx SLES 11 SPx may cause a message to be hotplug scripts and can be safely ignored. logged in the system log such as the following: umount: /dev/disk/bypath/pci-0000:02: 04.0-scsi-0:0:1:0: not mounted Driver installation fails.
PAGE 877
4. Troubleshooting Situations and their Resolutions Table 4-1 FC and FCoE Driver Situations and their Resolutions (Continued) Situation Resolution The Emulex driver for Linux does not load in ramdisk for a custom-built kernel. Custom built kernels are not supported by Emulex. However, the Emulex install script attempts to install the driver into a ramdisk that follows the naming scheme used by Red Hat or SLES kernels. • The Red Hat naming scheme for ramdisk images is: /boot/initrd-KERNELVERSION.img.
PAGE 878
4. Troubleshooting Situations and their Resolutions Ethernet Driver Situations and their Resolutions Table 4-2 lists the Ethernet driver situations and their resolutions. Table 4-2 Ethernet Driver Situations and their Resolutions Situation Resolution The Ethernet driver works but the transmit and receive data rates are not near a 10 Gb/s line rate. There could be several reasons for poor performance. For best performance practices, see “Network Performance Tuning” on page 868.
PAGE 879
4. Troubleshooting Situations and their Resolutions iSCSI Driver Situations and their Resolutions Table 4-3 lists the iSCSI driver situations and their resolutions for the OneConnect UCNA. Table 4-3 iSCSI Driver Situations and their Resolutions Situation Resolution When you log out of a target while an I/O is running and you log into the target again, you will get an error trace in “/var/log/messages” beginning with the error message, “trying to free buffer.” No solution available.
PAGE 880
4. Troubleshooting Log Messages Log Messages FC and FCoE Driver Log Messages Retrieving FC and FCoE Driver Log Messages LPFC error log messages are logged in the /var/log/messages file. An example of an LPFC message: Jul 2 04:23:34 daffy kernel: lpfc 0000:03:06.0: 0:1305 Link Down Event x2f2 received Data: x2f2 x20 x110 In this example:    lpfc 0000:03:06.0 – identifies the PCI location of the particular LPFC hardware port.
PAGE 881
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0115: Unknown ELS command received from NPORT Received an unsupported ELS command from a remote N_Port. Data: None Severity: Error Log: Always Action: Check the remote N_Port for a potential issue. 0125: FDISC Failed (x%x). Fabric out of resources The fabric rejected an FDISC because the switch cannot support additional virtual ports.
PAGE 882
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0136: PLOGI completes to NPort completion A PLOGI has completed for which there is no NDLP. Data: (1) ulpStatus (2) ulpWord[4] Severity: Error Log: LOG_ELS Action: None required. 0137: No retry ELS command to remote Data: (1) ulpStatus (2) ulpWord[4] Severity: Error Log: LOG_ELS Action: None required. 0138: ELS rsp: Cannot issue reg_login for REG_LOGIN mailbox command failed.
PAGE 883
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0143: SLI4 Adapter Hardware Error Data: / The HBA has encountered an unrecoverable error. Data: None Severity: Error Log: LOG_INIT Action: Use hbacmd to retrieve a dump file. 0144: Not a valid WCQE code: The completion queue handler detected an invalid type. Data: None Severity: Error Log: LOG_SLI Action: None required.
PAGE 884
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0203: Devloss timeout on WWPN
NPort A remote N_Port that was discovered by the driver disappeared for more than lpfc_devloss_tmo seconds.
PAGE 885
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0223: Timeout while waiting for NameServer login Our login request to the NameServer was not acknowledged within R_A_TOV. Data: None Severity: Error Log: Always Action: Check the fabric configuration. The driver recovers from this and continues with device discovery. 0224: NameServer Query timeout Node authentication timeout, node Discovery timeout.
PAGE 886
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0233: Nodelist not empty Driver unloaded or hotplug detected a node still in use. Data: None Severity: Error Log: LOG_DISCOVERY Action: None required. 0237: Pending Link Event during Discovery: State Received link event during discovery. Causes discovery restart. Data: None Severity: Warning Log: LOG_DISCOVERY verbose Action: None required, unless this issue persists.
PAGE 887
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0253: Register VPI: Can’t send mbox\ Could not issue the REG_VPI mailbox command for this VPort. Data: None Severity: Error Log: LOG_MBOX Action: None required. 0254: Register VPI: no memory” goto mbox_err_exit Could not allocate memory for the REG_VPI mailbox command. Data: None Severity: Error Log: LOG_MBOX Action: None required. 0255: Issue FDISC: no IOCB All of the pre-allocated IOCBs are in use.
PAGE 888
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0260: Register NameServer error: The REG_LOGIN mailbox command has failed for the NameServer. Data: None Severity: Error Log: LOG_ELS Action: Check the switch configuration 0261: Cannot register NameServer login: Either a memory allocation issue or an invalid parameter was sent to the REG_LOGIN.
PAGE 889
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0268: NS cmd Error ( ) The NameServer CT request failed. Data: None Severity: Error Log: LOG_DISCOVERY Action: Check the port and switch configurations. 0271: Illegal State Transition: node event , state Data: The current node state does not have a handler for this event.
PAGE 890
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0277: lpfc_enable_node: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp->kref.refcount) Enable node was attempted on an inactive node. Data: None Severity: Warning Log: LOG_NODE Action: None required. 0278: lpfc_enable_node: ndlp:x%pusgmap:x%x refcnt:%d, void *)ndlp, ndlp->nlp_usg_map, atomic_read(&ndlp->kref.refcount) Enable node was attempted on an inactive node.
PAGE 891
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0285: Allocated DMA memory size is less than the requested DMA memorysize Memory allocation was truncated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0286: lpfc_nlp_state_cleanup failed to allocate statistical data buffer Memory allocation failed for node’s statistical data. Data: None Severity: Error Log: LOG_INIT Action: None required.
PAGE 892
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0293: PM resume failed to start worker thread: error= The PCI resume (hotplug) could not start the worker thread for the driver. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver. 0294: PM resume Failed to enable interrupt The PCI resume (hotplug) could not get an interrupt vector. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver.
PAGE 893
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0302: REG_LOGIN: no buffers The driver attempted to issue a REG_LOGIN mailbox command to the adapter, but there no buffers were available. Data: (1) Did, (2) flag Severity: Warning Log: LOG_MBOX verbose Action: This message indicates: (1) Kernel virtual memory is depleted. Check that the system meets minimum RAM requirements for the Emulex FC adapter. Try closing other applications to free some memory.
PAGE 894
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0312: Ring handler: portRspPut is bigger then rsp ring The IOCB command rings put pointer is ahead of the get pointer. Data: None Severity: Error Log: LOG_SLI Action: None required. 0313: Ring handler: unexpected Rctl Type received The RCTL/Type of a received frame did not match any for the configured masks for the specified ring.
PAGE 895
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0320: CLEAR_LA mbxStatus error hba state The driver Data: Severity: Log: Action: issued a CLEAR_LA mailbox command to the HBA that failed. None Error Always This error could indicate a firmware or hardware issue. Report these errors to Technical Support.
PAGE 896
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0334: Unknown IOCB command Received an unknown IOCB command completion. Data: (1) type (2) ulpCommand (3) ulpStatus (4) ulpIoTag (5) ulpContext) Severity: Error Log: Always Action: This error could indicate a software driver or firmware issue. If this issue persists, report these errors to Technical Support. 0335: Unknown IOCB command Received an unknown IOCB command completion.
PAGE 897
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0343: Ring Cannot find buffer for an unsolicited iocb tag There are no more pre-allocated buffers available to handle unsolicited buffers. Data: None Severity: Error Log: LOG_SLI Action: None required. 0344: Ring Cannot find buffer for an unsolicited iocb tag There are no more pre-allocated buffers available to handle unsolicited buffers.
PAGE 898
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0350: rc should have been MBX_BUSY Attempting to unregister a default RPI from an interrupt context and the mailbox state is not busy. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 0351: Config MSI mailbox command failed, mbxCmd , mbxStatus The mailbox command sent to the firmware to configure the adapter to use MSI-X has failed.
PAGE 899
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0360:Unsupported EQ count. Cannot create an event queue of this size. Data: None Severity: Error Log: LOG_SLI Action: None required. 0361:Unsupported CQ count. Cannot create an completion queue of this size. Data: None Severity: Error Log: LOG_SLI Action: None required. 0362:Unsupported MQ count. Cannot create MQ of this size.
PAGE 900
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0368: Mis-matched fast-path completion queue identifier: eqcqid=%d, fcpcqid=%d The CQID in the event queue entry does not match the fcp_cqid that was passed into the routine. Data: None Severity: Error Log: LOG_SLI Action: None required. 0369: No entry from fast-path completion queue fcpcqid= There were no completions in the completion queue referenced by fcp_cqid.
PAGE 901
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0375: FCP cmdiocb not callback function iotag: The IOCB found for this iotag does not have a completion handler set in it. Data: None Severity: Warning Log: LOG_SLI Action: None required. 0377: Error parsing vpd. Using defaults. Could not parse the VPD data, so the driver is using the default values. Data: None Severity: Error Log: Always Action: None required.
PAGE 902
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0384: There is pending active mailbox cmd The mailbox commands have overlapped. This command should have been added to the mailbox queue. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 0385: rc should have been MBX_BUSY The completion handler for REG_LOGIN detected the IMMED_UNREG flag and tried to issue the UNREG_LOGIN command from an interrupt level.
PAGE 903
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0394: Failed to allocate CQ_EVENT entry The asynchronous event handler was unable to allocate an event queue entry to which to transfer the asynchronous event. Data: None Severity: Error Log: LOG_MBOX, LOG_SLI Action: This could be a V-LINK clear from the switch or a fatal error from the firmware. Perform a dump from the OneCommand Manager application.
PAGE 904
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0400: lpfc_nodev_tmo attribute cannot be set to , allowed range is [, The attempt to set the devloss timeout value failed because the value is out of the allowable range. Data: None Severity: Error Log: LOG_INIT Action: Use a value between the minimum and maximum values.
PAGE 905
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0406: Adapter maximum temperature exceeded , taking this port offline The driver has received an error for the HBA indicating that the maximum allowable temperature has been exceeded. Data: (1) work_hs (2) work_status[0] (3) work_status[1] Severity: Error Log: LOG_INIT Action: Ensure the server fans are not blocked. Shut down the server if the airflow is restricted.
PAGE 906
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0424:lpfc_"#attr" attribute cannot be set to %d, allowed range is ["#minval", "#maxval"] This is a compile time macro that is used by several module parameters to set the value. Data: None Severity: Error Log: LOG_INIT Action: Set the module parameter between the minimum and maximum values.
PAGE 907
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0433: Wakeup on signal: rc= A signal other than the LPFC_DATA_READY was received on the worker thread. Data: None Severity: Error Log: LOG_ELS Action: Unload and reload the driver. 0434: PM resume failed to start worker thread: error= The driver's power management resume function could not start the worker thread. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver.
PAGE 908
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0440: Adapter failed to init, READ_REV has missing revision information A firmware revision initialization error was detected. Data: None Severity: Error Log: Always Action: This error could indicate a hardware or firmware issue. Install the latest firmware revision. If this issue persists, report the error to Technical Support.
PAGE 909
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0449: lpfc_%attr attribute cannot be initialized to %d, allowed range is [%min, %max] The sysfs attribute value written exceeds attribute range. Data: (1) attribute name (2) value written (3) minimum value (3) maximum value Severity: Error Log: Always Action: Write a value within the supported range.
PAGE 910
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0457: Adapter Hardware Error The driver Data: Severity: Log: Action: received an interrupt indicating a possible hardware issue. (1) status (2) status1 (3) status2 Error Always This error could indicate a hardware or firmware issue. If this issue persists, report the error to Technical Support. 0458: Bring adapter online The FC driver has received a request to bring the adapter online.
PAGE 911
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0469: lpfc_link_speed attribute cannot be set to %d, allowed range is [0, 8] The link speed module parameter is invalid. Data: None Severity: Error Log: LOG_INIT Action: Use a link speed parameter in the valid range. 0472: PCI channel I/O permanent failure The PCI bus has detected an error. Data: None Severity: Error Log: LOG_INIT Action: Issue an HBA reset.
PAGE 912
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0483:Invalid link-attention link speed: x%x", bf_get(lpfc_acqe_link_speed, acqe_link). The link speed reported in the link attention interrupt is invalid. Data: None Severity: Error Log: LOG_INIT Action: Check the switch configuration. 0485: MSI-X slow-path request_irq failed (). The request_irq kernel API has failed.
PAGE 913
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0495: SLI_FUNCTION_RESET mailbox failed with status add_status , mbx status . Mailbox command failed. Data: None Severity: Error Log: LOG_INIT Action: Reset the HBA. 0496: Failed allocate slow-path EQ The event queue for the slow path was not allocated. Data: None Severity: Error Log: LOG_INIT Action: Unload and reload the driver.
PAGE 914
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0504: Failed allocate slow-path ELS WQ Failed to allocate slow-path ELS WQ. Data: None Severity: Error Log: LOG_INIT Action: None required. 0505: Failed allocate slow-path ELS MQ Data: None Severity: Error Log: LOG_INIT Action: None required. 0506: Failed allocate receive HRQ\n Data: None Severity: Error Log: LOG_INIT Action: None required. 0507: Failed allocate receive DRQ Failed to allocate receive DRQ.
PAGE 915
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0527: Failed setup of fast-path FCP CQ , rc = The fast-path FCP CQ setup failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 0528: Mailbox CQ not allocated The mailbox CQ is not allocated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0530: ELS CQ not allocated The ELS CQ is not allocated Data: None Severity: Error Log: LOG_INIT Action: None required.
PAGE 916
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0540: Receive Queue not allocated The Receive Queue is not allocated. Data: None Severity: Error Log: LOG_INIT Action: None required. 0542: lpfc_create_static_vport failed to allocate mailbox memory Failed to allocate mailbox memory for VPort creation. Data: None Severity: Error Log: LOG_INIT Action: None required.
PAGE 917
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0582: Error during sgl post operation The SGL post operation failed. Data: None Severity: Error Log: LOG_MBOX, LOG_IP verbose Action: None required. 0602: Failed to allocate CQ_EVENT entry Failed to allocate a CQ_EVENT entry. Data: None Severity: Error Log: LOG_SLI Action: None required. 0603: Invalid work queue CQE subtype (x%x)\n", cq- Invalid work queue CQE.
PAGE 918
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0711: detected queue full - lun queue depth adjusted to%d The driver reported. Data: Severity: Log: Action: detected a queue full status on a SCSI command response. New LUN queue depth is (1) New LUN queue depth Warning LOG_FCP verbose This may indicate an oversubscribed target array. Check your SAN configuration and I/O workload. 0713: SCSI layer issued Device Reset (%d, %d) A device reset was issued.
PAGE 919
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0724: I/O flush failure for context <“LUN”,”TGT”,”HOST”,”Unknown”>: cnt The I/O flush to the LUN, target, or host has failed. Data: None Severity: Error Log: LOG_FCP Action: None required. 0727: TMF to TGT LUN failed (, ) The task management command failed.
PAGE 920
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 0749: SCSI layer issued abort device The SCSI layer aborted a device. Data: (1) ret, (2) id, (3) lun, (4) snum Severity: Warning Log: LOG_FCP verbose Action: None required. 0915 Register VPI failed: Could not register the VPI. Data: None Severity: Error Log: LOG_MBOX Action: None required. 1005: AUTHENTICATION_FAILURE Nport: The system detected DHCHAP authentication failure on a port.
PAGE 921
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1010: Bad Tag 1 DHCHAP Authentication process failed when bad Tag was detected. Data: (1) message Severity: Error Log: LOG_SECURITY Action: Software driver Error. If this issue persists, report errors to the Technical Support. 1011: Auth_neg no hash function chosen DHCHAP Authentication process failed when an incorrect hash function was specified.
PAGE 922
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1017: dhchap challenge could not find DH Group DHCHAP Authentication process failed due to uncorroborated Challenge Group. Data: None Severity: Error Log: LOG_SECURITY Action: Software driver Error. If this issue persists, report errors to the Technical Support. 1018: dhchap challenge No Public key for non-NULL DH Group There is no Public key for the non-NULL DH Group.
PAGE 923
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1029: Reauthentication Failure The driver Data: Severity: Log: Action: encountered errors and there was a failure to re-authenticate. None Error LOG_SECURITY Software driver Error. If this issue persists, report errors to the Technical Support. 1031: Start Authentication: Get config failed The authentication failed due to some error during port configuration.
PAGE 924
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1039: Not Expecting Reply - rejecting. State An unanticipated reply was received during authentication and was subsequently rejected. Data: (1) auth_state. Severity: Error Log: LOG_SECURITY Action: Software driver Error. If this issue persists, report errors to the Technical Support. 1040: Bad Reply trans_id- rejecting.
PAGE 925
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1053: Start Authentication: Security service offline The authentication failed because security service was unavailable. Data: None Severity: Error Log: LOG_SECURITY Action: Software driver Error. If this issue persists, report errors to the Technical Support.
PAGE 926
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1211: genreq alloc failed\n"); Resource allocation failure. Data: (1) return code Log: LOG_LIBDFC Severity: Error Action: Kernel memory resources too low. 1213: FCoE cmd overflow: off <#> + cnt <#> > cmdsz <#> Application has tried to read more data than originally requested. Data: (1) response offset (2) size (3) cmd size Log: LOG_LIBDFC Severity: Error Action: Application may have sent a invalid command.
PAGE 927
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1227: FCoE IOCB TMO: handler set for The management command for the LPFC 2100 has timed out. Data: None Severity: Warning Log: LOG_LIBDFC Action: None required. 1228: FCoE IOCB TMO: handler set for A management IOCB for the LPFC 2100 has timed out Data: None. Severity: Warning Log: LOG_LIBDFC Action: None required.
PAGE 928
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1240: Unable to allocate command buffer memory Could not allocate memory for the command buffer. Data: None. Severity: Error Log: LOG_LINK_EVENT Action: None required. 1243: Menlo command error. code=%d.\n", mlorsp->code The Menlo maintenance command failed. Data: None. Severity: Error Log: LOG_LINK_EVENT Action: None required. 1244: Unable to allocate response buffer memory.
PAGE 929
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1250: Menlo command error. code=<#> The IOCB driver sent to check FCoE state has bad header size. Data: (1) return code Log: LOG_LINK_EVENT Severity: Error Action: Try resetting the FCoE to operational mode. 1251: Menlo command error. code=<#> The IOCB driver sent to check FCoE state has failed, no resources.
PAGE 930
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1302: Invalid speed for this board: Reset link speed to auto: The driver Data: Severity: Log: Action: is re-initializing the link speed to auto-detect. None Warning LOG_LINK_EVENT verbose None required. 1303: Link Up Event received A link up event was received. It is possible for multiple link events to be received together.
PAGE 931
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1310: Menlo Maint Mode Link up Event rcvd The link is up in maintenance mode; only management commands are allowed. Data: (1) fc_eventTag (2) port_state (3) vport fc_flag Severity: Error Log: LOG_LINK_EVENT Action: None required. 1312: Link Down Event received Maintenance mode link up notification received without entering link down.
PAGE 932
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1405: Failed to initialize iocb list. Driver resource initialization failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 1406: Failed to set up driver resource. Initialization failed to set up driver resource. Data: None Severity: Error Log: LOG_INIT Action: None required. 1407: Failed to create scsi host. Initialization failed to create SCSI host.
PAGE 933
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1412: Failed to set up driver resource. Initialization failed to set up driver resource. Data: None Severity: Error Log: LOG_INIT Action: None required. 1413: Failed to initialize iocb list. Initialization failed to initialize the IOCB list. Data: None Severity: Error Log: LOG_INIT Action: None required. 1414: Failed to set up driver resource. Initialization failed to set up driver resource.
PAGE 934
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1420: Invalid HBA PCI-device group: Invalid HBA PCI-device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1421: Failed to set up hba Initialization failed to set up the HBA. Data: None Severity: Error Log: LOG_INIT Action: None required.
PAGE 935
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1427: Invalid PCI device group: Invalid HBA PCI-device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1428: Invalid PCI device group: Invalid HBA PCI-device group detected. Data: None Severity: Error Log: LOG_INIT Action: None required. 1429: Invalid PCI device group: Invalid HBA PCI-device group detected.
PAGE 936
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1477: Failed to set up hba Failed to set up the HBA. Data: None Severity: Error Log: LOG_INIT Action: None required. 1603: Loopback test did not receive expected data length. actual length expected length . The loopback test did not receive the same amount of data that it transmitted. Data: None Severity: Error Log: LOG_LIBDFC Action: None required.
PAGE 937
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1819: Unrecognized lpfc_sli_mode parameter: The user has attempted to set the SLI mode to an invalid value. The valid values for the SLI mode are 0, 2, and 3. Data: (1) lpfc_sli_mode Severity: Error Log: LOG_VPORT verbose Action: The lpfc_sli_mode driver parameter setting must be corrected. Valid values are 0, 2, and 3. 1820: Unable to select SLI-3. Not supported by adapter.
PAGE 938
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1825: Vport Created. This message is displayed to indicate that a port was created in the system. It is displayed at this level to ensure it is always appears at all log levels. Data: None Severity: Error Log: LOG_VPORT verbose Action: No action, informational. 1826: Vport Disabled. The port had to be disabled in the system. Data: None Severity: Error Log: LOG_VPORT verbose Action: No action, informational.
PAGE 939
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 1832: No pending MBOX command to handle Data: None Severity: Error Log: LOG_MBOX Action: None required. 1835: Vport discovery quiesce failed: state fc_flags wait msecs Could not pause discovery on this VPort. Data: None Severity: Error Log: LOG_VPORT Action: None required.
PAGE 940
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2002: Error Could not grow rpi count An error occurred because the RPI count could not be increased. Data: None Severity: Error Log: LOG_SLI Action: None required. 2004: Failed to allocate XRI.last XRITAG is Max XRI is , Used XRI is . All XRIs are in use. Data: None Severity: Warning Log: LOG_SLI Action: None required.
PAGE 941
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2011: Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command. Data: None Severity: Error Log: LOG_SLI Action: None required. 2012: Mailbox failed , mbxCmd READ_CONFIG, mbxStatus The READ_CONFIG mailbox command failed. Data: None Severity: Error Log: LOG_SLI Action: None required.
PAGE 942
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2020: Failed to allocate mbox for ADD_FCF cmd Failed to allocate mailbox for ADD_FCF command. Data: None Severity: Error Log: LOG_INIT Action: None required. 2022: VPI Mailbox failed status , mbxStatus The INIT VPI mailbox command has failed. Data: None Severity: Error Log: LOG_SLI Action: None required. 2401: Failed to allocate memory for ELS XRI management array of size .
PAGE 943
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2504: RQ_CREATE mailbox failed with status add_status , mbx status The mailbox command sent to create the receive queue has failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2505: EQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the event queue has failed.
PAGE 944
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2510: RQ_DESTROY mailbox failed with status add_status , mbx status The mailbox command sent to delete the work queue has failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2511: POST_SGL mailbox failed with status add_status , mbx status n The mailbox command sent to post the SGL pages to the firmware has failed.
PAGE 945
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2516: DEL FCF of default FCF Index failed mbx status , status add_status The mailbox command to delete the FCF record has failed. Data: None Severity: Error Log: LOG_SLI Action: None required. 2517: Unregister FCFI command failed status %d, mbxStatus x%x", rc, bf_get(lpfc_mqe_status, &mbox->u.
PAGE 946
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2524: Failed to get the non-embedded SGE virtual address The READ_FCF_RECORD mailbox command could not retrieve the SGE that was requested. Data: None Severity: Error Log: LOG_MBOX Action: None required. 2527: Failed to allocate non-embedded SGE array. Failed to allocate the non-embedded SGE array. Data: None Severity: Error Log: LOG_MBOX Action: None required.
PAGE 947
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2535: Unsupported RQ count. () The receive queue ring can only be 512, 1024, 2048, or 4096. Data: None Severity: Error Log: LOG_SLI Action: None required. 2536: Unsupported RQ count. () The receive queue ring can only be 512, 1024, 2048, or 4096. Data: None Severity: Error Log: LOG_SLI Action: None required.
PAGE 948
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2543: Mailbox command () cannot issue The mailbox command does not have all of the fields set correctly. Data: (1) sli_mbox_opcode (2) sli_flag (3) flag Severity: Error Log: LOG_MBOX, LOG_SLI Action: None required. 2544: Mailbox command () cannot issue The HBA cannot be accessed on the PCI bus.
PAGE 949
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2551: UNREG_FCFI mbox allocation failed HBA state The allocation for the UNREG_FCFI mailbox command has failed. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required. 2552: UNREG_FCFI issue mbox failed rc HBA state . The UNREG_FCFI mailbox command has failed. Data: None Severity: Error Log: LOG_DISCOVERY, LOG_MBOX Action: None required.
PAGE 950
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2558: ADD_FCF_RECORD mailbox failed with status add_status The ADD_FCF_RECORD mailbox command has failed. Data: None Severity: Error Log: LOG_INIT Action: None required. 2559: Block sgl registration required DMA size great than a page. Attempting to register more SGEs with the firmware than can fit in a page.
PAGE 951
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2566: Failed to allocate table entry Failed to allocate connection table entry. Data: None Severity: Error Log: LOG_INIT Action: None required. 2567: Config region 23 has bad signature The driver Data: Severity: Log: Action: was unable to read Config Region 23 because it has an invalid signature. None Error LOG_INIT None required.
PAGE 952
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2574: Not enough EQs () from the pci function for supporting FCP EQs () Failed to create the minimum fast-path event queues. Data: None Severity: Error Log: LOG_INIT Action: None required.
PAGE 953
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2581: Not enough WQs () from the pci function for supporting FCP WQs () The driver Data: Severity: Log: Action: was not configured with the minimum number of fast-path work queues. None Error LOG_INIT None required.
PAGE 954
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2605: lpfc_dump_static_vport: memory allocation failed Failed to allocate mailbox memory. Data: None Severity: Error Log: LOG_MBOX Action: None required. 2606: No NPIV Fabric support No NPIV Fabric support. Data: None Severity: Error Log: LOG_ELS Action: None required. 2607: Failed to allocate init_vpi mailbox Failed to allocate the INIT_VPI mailbox command.
PAGE 955
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2619: Config region 23 has bad signature Configuration region 23 has an invalid signature. Data: None Severity: Error Log: LOG_INIT Action: None required. 2620: Config region 23 has bad version Configuration region 23 has an invalid version. Data: None Severity: Error Log: LOG_INIT Action: None required. 2621: Failed to allocate mbox for query firmware config cmd Failed to allocate mailbox memory.
PAGE 956
4. Troubleshooting Log Messages Table 4-4 LPFC Error Log Messages and their Descriptions (Continued) 2718: Clear Virtual Link Received for VPI tag A Clear virtual link was received from the Fabric for this VPI. Data: None Severity: Error Log: LOG_DISCOVERY Action: None required. 2719: Invalid response length: tgt lun cmnd rsplen The response length for this FCP command is not supported. Data: None Severity: Error Log: LOG_FCP Action: None required.
PAGE 957
4. Troubleshooting Log Messages Ethernet Driver Log Messages Retrieving Ethernet Driver Log Messages Ethernet driver messages are logged in the /var/log/messages file. This log file is an ASCII text file and can be viewed and searched with a text editor such as vim. A log file automatically rotates as it gets larger. Rotated log files are named messages.x, where “x” is an integer.
PAGE 958
4. Troubleshooting Log Messages Table 4-5 Ethernet Driver Log Messages of Type (Continued) Ethernet Log Message Description Type could not create sysfs group The creation of the “flash_fw” entry under the /sys/class/net/eth failed. The driver is fully functional but you cannot install later firmware versions on the adapter. Could not enable VLAN Promiscuous mode Firmware command failed to enable VLAN promiscuous mode.
PAGE 959
4. Troubleshooting Log Messages Table 4-5 Ethernet Driver Log Messages of Type (Continued) Ethernet Log Message Description Type INTx Request IRQ failed – err The request for INTx interrupt registration failed. The driver is non-functional if the INTx interrupt cannot be registered. Error Invalid cookie. FW image may be corrupted The firmware image under /lib/firmware/ does not have the expected cookie. The firmware in this file will not be flashed.
PAGE 960
4. Troubleshooting Log Messages Table 4-5 Ethernet Driver Log Messages of Type (Continued) Ethernet Log Message Description Type Pause param set failed The firmware command to set pause frame settings Warning failed. POST timeout; stage=
The power-on self test of the adapter failed. This is Error an indication of a hardware or firmware issue. Try rebooting the system after a reset. queue_setup failed Firmware command failed to create requested number of queues.
PAGE 961
4. Troubleshooting Log Messages iSCSI Driver Log Messages Retrieving iSCSI Driver Error Log Messages Note: These error log messages are specific to the open-iscsi be2iscsi driver. For Linux systems, the iSCSI driver generates log messages to the /var/log/messages file. The log file is an ASCII text file and can be viewed and searched with your preferred text editor.
PAGE 962
4. Troubleshooting Log Messages Table 4-6 iSCSI Log Messages and Descriptions (Continued) Log Message Description BM_# : EEH : State PERM Failure Driver pci error message. PCI error cannot be recovered. BM_# : AER EEH Resume Failed Driver pci error message. Driver failed to resume after PCI error recovery via a chip reset. beiscsi_ep_connect shost is NULL Driver session management error message. This host no longer exists.
PAGE 963
Appendix A. iSCSI Driver Appendix A. iSCSI Driver iSCSI Driver Parameter Descriptions Table A-1 lists the user-configurable iSCSI driver parameters for the OCe10102 adapter. It includes a description of the parameters, default values, and their configuration value range. Note: If the value provided for a parameter exceeds the parameter’s defined minimum or maximum value, the driver logs an error in the event log, and continues to load using the parameter’s default value.
PAGE 964
Appendix A. iSCSI Driver Configuring the iSCSI Driver Parameters Configuring the ETO and LDTO Parameters ETO and LDTO values are configurable during insmod time. The ETO value specified during insmod is the default ETO value that is applied to all targets. The following example configures the LDTO and ETO during insmod of the driver. These settings must be used every time the iSCSI driver is loaded by insmod. insmod be2iscsi.
PAGE 965
Appendix A. iSCSI Driver alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapter1 usb-storage alias scsi_hostadapter2 be2iscsi options be2iscsi eto=0 ldto=0 large_io=512 alias eth1 be2net alias eth2 be2net After adding the options line, save the file, and then rebuild initrd. Configuring the im_policy Parameter The interrupt moderation policy setting (im_policy parameter) controls the rate of interrupts for the OneConnect adapter. Table A-2 defines the available im_policy settings.
PAGE 966
Appendix A. iSCSI Driver To permanently set large_io on every iSCSI boot, edit the /etc/modprobe.conf file, type options be2iscsi eto=0 ldto=0 large_io=512 im_policy=1 After adding the options line, save the file, and then rebuild initrd. iSCSI Error Handling Error Handling using ETO and LDTO Parameters The goal of iSCSI error handling is to be tolerant of link-level and target-level failures up to configured timeout values so that I/O errors are not seen by the application or operating system.
PAGE 967
Appendix A. iSCSI Driver iSCSI Driver Log Messages Retrieving iSCSI Driver Error Log Messages Note: These error log messages are specific to the proprietary be2iscsi driver. For Linux systems, the iSCSI driver generates log messages to the /var/log/messages file. The log file is an ASCII text file and can be viewed and searched with your preferred text editor.
PAGE 968
Appendix A. iSCSI Driver Table A-3 iSCSI Driver Error Log Messages (Continued) iSCSI Error Log Message Description Extended Timeout Expired. Loss of connection to target exceeded ETO limits. Session ID = 0xX Check the connection to the target or the state of the target device. If the target is made available, any sessions that existed previously will be reestablished and the devices will be available for I/O.
PAGE 969
Appendix A. iSCSI Driver Table A-3 iSCSI Driver Error Log Messages (Continued) iSCSI Error Log Message Description Unrecoverable Error UE_LOW = 0xX UE_HIGH = 0xX Firmware Line Number = 0xX This may be due to hardware errors or due to unhandled exceptions in the hardware or firmware. Emulex Drivers Version 10.2 for Linux User Manual P010081-01A Rev.
PAGE 970
Appendix B. Configuring iSCSI Through DHCP IP Address Reservation Appendix B. Configuring iSCSI Through DHCP IP Address Reservation If you are using the Dynamic Host Configuration Protocol (DHCP) server to obtain an IP address for your iSCSI initiator, Emulex recommends that you set up a reservation. A reservation assigns a specific IP address based on the MAC address of your iSCSI function.
PAGE 971
Appendix B. Configuring iSCSI Through DHCP DHCP Option 43 (Vendor-Specific Information) Table B-1 DHCP Option 43 (Vendor-Specific Information) (Continued) Parameter Description Field Type Replace with either “E” or “D”. • “E” denotes that the data digest is enabled. • “D” denotes that the data digest is disabled. Optional If a value is not provided, it is assumed that the Data Digest is disabled by default. If applicable, replace with “D”, “E”, or “M”.
PAGE 972
Appendix B. Configuring iSCSI Through DHCP DHCP Option 43 (Vendor-Specific Information)     InitiatorName: Not specified. Use the Initiator name already configured. Use the default name if none was configured. HeaderDigest: Enabled DataDigest: Not specified. Assume disabled. AuthenticationType: One-way CHAP is enabled. Default TCP and Mutual CHAP Settings Example The following is an example of default TCP port and mutual CHAP settings. iscsi:”192.168.0.2”::”000000000000000E”:”iqn.2009-4.
PAGE 973
Appendix C. OneConnect 10 GbE Adapter Port Speed Specifications Port Speed Negotiation on Non-Mezzanine Cards Appendix C. OneConnect 10 GbE Adapter Port Speed Specifications Port Speed Negotiation on Non-Mezzanine Cards OneConnect 10 GbE adapters can support only one Ethernet port speed at a time. On non-mezzanine cards, its preference is 10 Gb/s. The type of module used (copper/optical) does not make a difference.
PAGE 974
Appendix D. Updating Ethernet Firmware Appendix D. Updating Ethernet Firmware Note: Before performing a firmware update, driver installation is required. See “Installing the Ethernet Driver Kit” on page 818. The Emulex Ethernet driver supports updating the firmware image in the adapter flash through the request_firmware interface in Linux. You can perform this update when the adapter is online and passing network/storage traffic. To update the Ethernet firmware image: 1.
PAGE 975
Appendix E. Ethtool -S Option Statistics Appendix E. Ethtool -S Option Statistics Table E-1 contains a list of ethtool -S option statistics and their descriptions. Table E-2 contains a list of transmit/receive statistics per receive queue basis. Table E-1 Ethtool -S Option Statistics Name Description rx_crc_errors The number of packets dropped due to CRC errors. rx_alignment_symbol_errors The number of packets dropped due to L1 alignment errors. This counter is on a per-port basis.
PAGE 976
Appendix E. Ethtool -S Option Statistics Table E-1 Ethtool -S Option Statistics (Continued) Name Description rx_priority_pause_frames The number of Ethernet priority pause frames (priority flow control) received per port. tx_priority_pause_frames The number of Ethernet priority pause frames transmitted per port. pmem_fifo_overflow_drop Received packets dropped when an internal FIFO going into main packet buffer tank (PMEM) overflows. jabber_events The number jabber packets received.
PAGE 977
Appendix E. Ethtool -S Option Statistics Table E-2 Transmit/Receive Queue Statistics (Continued) Statistic Description rxq:rx_post_fail The number of times the driver could not post received buffers to ASIC. rxq:rx_drops_no_skbs The number of times the driver could not allocate socket buffers. rxq:rx_drops_no_frags Packets dropped due to insufficient buffers posted by the driver. txq:tx_compl The number of transmit completions signaled by ASIC.
PAGE 978
Appendix F. lpfc Driver BlockGuard Functionality Overview Appendix F. lpfc Driver BlockGuard Functionality Overview Emulex BlockGuard™ provides a way to check the integrity of data read and written from the host to the disk and back through the SAN. This check is implemented through the Data Integrity Field (DIF) defined in the ANSI T10 standard. The Emulex lpfc driver supports T10 DIF Type 1. In the Type 1 implementation, the 8-byte DIF consists of a Ref Tag (or LBA), an App Tag, and a Guard Tag (or CRC).
PAGE 979
Appendix F. lpfc Driver BlockGuard Functionality Enabling BlockGuard typically passed as the Guard Tag between the Initiator Host and the HBA. The HBA hardware will translate the IP Checksum into a CRC, or visa versa, on data being sent/received on the wire. The CRC is called a DIF protection type, and the IP Checksum is referred to as DIX protection type. Enabling BlockGuard BlockGuard is disabled by default. To enable it, the parameter lpfc_enable_bg must be passed to the driver as follows: insmod lpfc.
PAGE 980
Appendix F. lpfc Driver BlockGuard Functionality SCSI Command Support Figure F-2 Data Transfer between Initiator Host and the HBA The Initiator Operations are listed in Table F-1. Table F-1 Initiator Operations Initiator Operation Initiator Host <-> HBA HBA <-> Target Comment NORMAL Unprotected Unprotected Used for unprotected I/O READ_INSERT Protected Unprotected Reads the data from the target.
PAGE 981
Appendix F. lpfc Driver BlockGuard Functionality lpfc Driver Module Parameters Table F-1 Initiator Operations (Continued) Initiator Operation Initiator Host <-> HBA HBA <-> Target Comment READ_PASS Protected Protected Reads the data and protection data from the target on the SAN. The HBA will verify data integrity and transfer both data and protection data to the Initiator host. The HBA can convert the protection data guard tag from CRC to IP CSUM.
PAGE 982
Appendix F. lpfc Driver BlockGuard Functionality lpfc Driver Module Parameters Table F-3 Protection Data Placement for Supported Profiles Flag Value BlockGuard Profile Operation SHOST_DIF_TYPE1_PROTECTION 1 A1 READ_STRIP / WRITE_INSERT SHOST_DIX_TYPE0_PROTECTION 8 AST2 READ_INSERT / WRITE_STRIP SHOST_DIX_TYPE1_PROTECTION SHOST_DIF_TYPE1_PROTECTION 17 AST1 / C1 READ_PASS / WRITE_PASS lpfc_prot_guard This parameter correlates to the SCSI_host_guard_type of the Linux kernel.
PAGE 983
Appendix G. Installing and Updating Scientific Linux 6.5 Appendix G. Installing and Updating Scientific Linux 6.5 Perform the following steps to install and update Scientific Linux 6.5. 1. Download the Scientific Linux 6.5 iso image from: https://www.scientificlinux.org/download/ 2. Create an operating system bootable DVD using any DVD writer software. 3. Boot from the DVD and install using the installation menu. 4. Update the kernel to 2.6.32-279.22.1 using yum. For example: # yum install kernel-2.6.
PAGE 984
Installation Instructions for DKMS Drivers System: Date: Linux RHEL 5 and SLES 10 distributions November 2013 DKMS-enabled drivers are provided for supported Linux RHEL 5 and SLES 10 distributions. To install these drivers, do the following: 1. Set up the DKMS environment on the target system. 2. Install the DKMS drivers using the standard Linux RPM installation command, rpm -ivh. To update the DKMS drivers, use the standard Linux RPM update command, rpm -Uvh.
PAGE 985
® Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev.
PAGE 986
EMULEX CONFIDENTIAL. Copyright © 2003–2014 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.
PAGE 987
1. Introduction ESXi Compatibility 1. Introduction This product supports the Emulex® OneConnect™ and LightPulse® families of adapters. The VMware ESXi drivers support the Fibre Channel (FC), FC over Ethernet (FCoE), Ethernet (or network interface card–NIC), and Internet Small Computer System Interface (iSCSI) protocols.
PAGE 988
1. Introduction Supported Guest Operating Systems Supported Guest Operating Systems The Emulex driver supports the following guest operating systems:          CentOS 5.x CentOS 6.x RHEL 5.x RHEL 6.x RHEL 7.x SLES 11.
PAGE 989
1.
PAGE 990
1.
PAGE 991
2. Installation ESXi 5.5 Overview 2. Installation ESXi 5.5 Overview With the release of ESXi 5.5 and vSphere 5.5, VMware has introduced a new driver model called native mode. Emulex has endorsed the native mode driver model for ESXi 5.5 with the following drivers:   For FC and FCoE functionality, the out-of-box driver is the native mode “lpfc” driver for OneConnect OCe10100-series, OCe11100-series, OCe14000-series, LPe16202/OCe15100, LPe16000-series, LPe12000-series, and LPe11000-series adapters.
PAGE 992
2. Installation Preparing to Upgrade to ESXi 5.5 Driver Parameters Migration When Upgrading to ESXi 5.5 VMware's ESXi 5.5 release has two driver models:   vmklinux – the legacy driver model native mode – the new driver model vmklinux is a Linux compatibility layer for device drivers in all ESX releases from ESX 2.x to ESXi 5.1. This vmklinux layer allows IHVs to use their Linux drivers in ESXi with only a few modifications.
PAGE 993
2. Installation Preparing to Upgrade to ESXi 5.5 And to verify that the value has been reprogrammed: ~ # esxcfg-module -g lpfc lpfc enabled = 1 options = 'lpfc_lun_queue_depth=8' Once verification has completed, reboot the server to activate the command and burn the new driver parameters into the initial ram disk. Ethernet Driver Example This example assumes a single OCe10100 or OCe11100-series adapter in the host, since the max_vfs parameter receives the number of VFs for each PF.
PAGE 994
2. Installation Installing the FC/FCoE Driver Installing the FC/FCoE Driver This section provides installation information for the driver and the Emulex CIM Provider using the FC/FCoE interface on ESXi systems. Before using this product, you need a working knowledge of FC/FCoE and network storage devices. Installing the FC/FCoE Driver and Management Software The Emulex driver is available through the VMware support site. Refer to the VMware support website for further details. For VMware ESXi 5.0, 5.
PAGE 995
2. Installation Installing the FC/FCoE Driver For additional information, see the OneCommand Manager for VMware vCenter User Manual. Uninstalling the FC/FCoE Driver See the VMware Patch Download page for instructions. Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev.
PAGE 996
2. Installation Installing the NIC Driver Installing the NIC Driver This section provides installation information for the NIC driver. Before using this product, you need a working knowledge of NIC and network-storage devices. Installing the NIC Driver and Management Software For ESXi 5.0, 5.1, and 5.5 systems, the latest Emulex NIC driver is available out-of-box. Refer to the operating system guide for installation instructions.
PAGE 997
2. Installation Installing the NIC Driver Note: The following command can be used to get the value: #esxcli network nic list The output should look similar to the following: Name PCI Device Driver Link Speed Duplex MAC Address MTU Description ---- ----------- ------- ---- ----- ------- ------------- --- ------------------ vmnic2 0000:003:00.0 elxnet Up 10000 Full 00:00:c9:bb:16:a6 1500 Emulex Corporation OneConnect 10Gb NIC (be3) vmnic3 0000:003:00.
PAGE 998
2. Installation Installing the NIC Driver All vNICs are fully functional and support the same capabilities as a standard NIC.
PAGE 999
2. Installation Installing the NIC Driver # esxcfg-module -s max_vfs=x1,y1,x2,y2,x3,y3 be2net ESXi 5.
PAGE 1000
2. Installation Installing the NIC Driver  To configure multichannel using the OneCommand Manager for VMware vCenter application, see the latest OneCommand Manager for VMware vCenter User Manual. Refer to the Emulex Universal Multichannel Reference Guide for additional information on multichannel. Using ARI When multichannel is enabled on an OCe14000-series network adapter, each port may be partitioned into isolated PFs (channels).
PAGE 1001
2. Installation Installing the NIC Driver Default VLAN Tagging When default VLAN tagging is configured on a VF, a VLAN ID is automatically added to and removed from every packet sent and received over the VF. To configure a default VLAN tag: 1. Power off the VM before proceeding to the next step. 2. Edit the .vmx file corresponding to the VM from the vmfs Datastore under /vmfs/volumes/Datastore//. 3. Append the following line: pciPassthru.
PAGE 1002
2. Installation Installing the NIC Driver   To configure SR-IOV using the adapter BIOS, see the Boot for NIC, iSCSI, FCoE, and RoCE Protocols User Manual. To configure SR-IOV using the OneCommand Manager for VMware vCenter application, see the OneCommand Manager for VMware vCenter User Manual. NPar enables the capability to divide a 10Gb port into multiple physical functions, with flexible bandwidth capacity allocation, that appear to the operating system and network as separate physical devices.
PAGE 1003
2. Installation Installing the NIC Driver Using NParEP Notes:    NParEP is available only on OCe14000-series adapters. 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 can be configured on the OCe14000 family of adapters by using the adapter BIOS utility or the OneCommand Manager for VMware vCenter application.
PAGE 1004
2. Installation Installing the NIC Driver esxcli software vib list | grep be2net net-be2net 2011-05-31 4.0.227.1-1OEM.369055 Emulex Community Supported To get information on the install NIC driver on ESXi 5.5 systems, enter esxcli software vib list | grep elxnet This is the sample output: esxcli software vib list | grep elxnet ~ # esxcli software vib list | grep elxnet elxnet 10.0.575.9-1OEM.550.0.0.1338210 Emulex VMware Certified 2013-09-24 Emulex Drivers Version 10.
PAGE 1005
2. Installation Installing the iSCSI Driver Installing the iSCSI Driver This section provides installation information for the Emulex iSCSI driver. Before using this product, you need a working knowledge of iSCSI and network-storage devices. Installing the iSCSI Driver and Management Software For ESXi 5.0, 5.1 and 5.5 systems, the Emulex iSCSI driver is available out-of-box. A direct link to the iSCSI driver available for download from VMware is provided on the Downloads page on the Emulex website.
PAGE 1006
3. Configuration ESXi Command Line Tool Transition 3. Configuration ESXi Command Line Tool Transition For the ESXi 5.5 release and all subsequent operating system releases, VMware is starting the transition from esxcfg commands to esxcli commands. This section describes the transition to the esxcli commands. Note: Both sets of commands are supported in the ESXi 5.5 release. ESXi 5.0 and 5.1 Implementation For ESXi 5.0 and 5.
PAGE 1007
3. Configuration ESXi Command Line Tool Transition ESXi 5.5 Implementation With the ESXi 5.5 release, Emulex has started using the esxcli version of the command sequence, which uses a different command syntax.
PAGE 1008
3. Configuration ESXi Command Line Tool Transition Name Type emi_canceller int Value Enable or disable the EMI Canceller. Description max_vfs array of int The number of virtual functions.
PAGE 1009
3. Configuration ESXi Command Line Tool Transition Name Type Value Description emi_canceller int 1 Enable or disable the EMI Canceller. max_vfs array of int The number of virtual functions.
PAGE 1010
3. Configuration FC and FCoE Driver Configuration FC and FCoE Driver Configuration You can configure driver parameters using native ESXi tools, the Emulex OneCommand Manager application (for use in non-lockdown mode only), or the OneCommand Manager for VMware vCenter application (for use in both lockdown and non-lockdown modes). This document describes how to configure parameters using native ESXi tools. For a more comprehensive description of ESXi tools, refer to VMware’s public website.
PAGE 1011
3. Configuration FC and FCoE Driver Configuration To make changes that impact all adapters in the system (global changes): 1. From the Troubleshooting Administrative Shell environment’s terminal window, use one of the following commands: For ESXi 5.5 systems, type esxcli system module parameters set -p param1=value param2=value ... -m lpfc For ESXi 5.0 and 5.1 systems, type esxcfg-module -s “param=value param2=value...” The is obtained from the vmkload_mod -l call.
PAGE 1012
3. Configuration FC and FCoE Driver Configuration Examples of Permanent Per-Adapter Configuration The following example sets lun_queue_depth to 20 (default is 30) for adapter #1. 1. Set the adapter-specific value using one of the following commands: For ESXi 5.5 systems, type esxcli system module parameters set -p lpfc1_lun_queue_depth=20 -m lpfc For ESXi 5.0 and 5.1 systems, type esxcfg-module -s “lpfc1_lun_queue_depth=20” lpfc820 2.
PAGE 1013
3. Configuration FC and FCoE Driver Configuration Dynamically Adding LUNs For instructions on dynamically adding LUNs, refer to the “Using Rescan” section of the VMware SAN Configuration documentation. Dynamically Adding Targets VMware does not provide a native mechanism for this process. After all target/LUN configuration steps have been successfully completed, add the target to the intended fabric zone. To get the driver to log into the target, either the target or initiator link must be bounced.
PAGE 1014
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter throttle_log_ time Description ESXi 5.0, 5.1 Legacy Driver Model Values Do not exceed ‘throttle_log_cnt’ number of logs within this time limit (seconds) ESXi 5.5 OP Native Mode Driver Model Values Comments Def = 300 Min = 5 For the native mode driver. Max = 86400 Works with throttle_log_cnt.
PAGE 1015
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter use_mq Description Use MQ Kernel API for ESXi 5.x operating systems. 0 = Disable MQ ESXi 5.0, 5.1 Legacy Driver Model Values ESXi 5.
PAGE 1016
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter scan_down topology ESXi 5.0, 5.1 Legacy Driver Model Values ESXi 5.5 OP Native Mode Driver Model Values Comments Start scanning for devices from highest AL_PA to lowest Def = 1 Def = 1 Min = 0 Min = 0 Max = 1 Max = 1 Select FC topology.
PAGE 1017
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter max_scsicmpl_ time Description ESXi 5.0, 5.1 Legacy Driver Model Values Use SCSI command Def = 0 completion time to control Min = 0 queue depth to the device. Max = 60000 0 – SCSI command ESXi 5.5 OP Native Mode Driver Model Values Comments Def = 0 No changes Min = 0 Max = 60000 Completion time is not used for controlling I/O queue depth.
PAGE 1018
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter Description ESXi 5.0, 5.1 Legacy Driver Model Values ESXi 5.5 OP Native Mode Driver Model Values Comments enable_rrq Enable RRQ functionality. Def = 2 Def = 0 Min = 0 Min = 0 Max = 2 Max = 1 The native mode driver will migrate to 2, 0, 2 in a future release. 0x0: disabled, XRI/OXID use not tracked. 0x1: XRI/OXID reuse is timed with ratov, RRQ sent.
PAGE 1019
3. Configuration FC and FCoE Driver Configuration Table 3-1 FC and FCoE Driver Parameters (Continued) Module Parameter Description nlp_slab_cnt NLP Slab entries ESXi 5.0, 5.1 Legacy Driver Model Values ESXi 5.5 OP Native Mode Driver Model Values Comments Def = 64 Min = 32 rb_slb_cnt Receive Buffer slab entries Max = 1024 Controls the size of the driver’s node table. This table in turn limits the driver’s ability to discover remote ports, fabric, initiator, and targets in a zone.
PAGE 1020
3. Configuration FC and FCoE Driver Configuration Using the OneCommand Manager Application for VMware vCenter The OneCommand Manager application for VMware vCenter plug-in software uses the standard CIM interfaces to manage the adapters and supports CIM-based device and adapter management. The OneCommand Manager application for VMware vCenter plug-in software also supports existing adapter management functionality based on its proprietary management stack and the standard HBAAPI interface.
PAGE 1021
3. Configuration NIC Driver Configuration NIC Driver Configuration Configuring ESXi 5.5 NIC Driver Parameters Table 3-2, ESXi 5.5 Ethernet Driver Parameters lists the Ethernet driver module parameters, their descriptions, and their corresponding values in previous ESXi environments and in ESXi 5.5 native mode. Table 3-2 ESXi 5.5 Ethernet Driver Parameters Module Parameter Description ESXi 5.0, 5.1 Legacy Driver Model Values ESXi 5.
PAGE 1022
3. Configuration NIC Driver Configuration New Module Options In the elxnet driver, there are two new module parameters: 1. Enable or disable MSI-X support. The driver default is to have MSI-X enabled. 2. Enable or disable vxlan_offload support. The driver default is to have vxlan_offload enabled. Note: The following output is for illustrative purposes only. Actual output may vary depending on the adapter installed in the system.
PAGE 1023
3. Configuration NIC Driver Configuration Configuring ESXi 5.0 and 5.1 NIC Driver Parameters The following table lists the user-configurable NIC driver parameters for ESXi 5.0 and 5.1. It includes a description of the parameter and its default value. Table 3-3 User-configurable NIC Driver Parameters Parameter Default Value Description heap_initial 32 MB The size of the memory heap, in bytes, that should be initially allocated for the driver.
PAGE 1024
3. Configuration NIC Driver Configuration Enabling Jumbo Frames Enabling jumbo frames reduces CPU utilization and is a recommended practice. To use jumbo frames, you must increase the MTU size in the vSwitch and also in the guest operating system. Emulex adapters support MTU sizes between 64 bytes and 9000 bytes. For optimal performance, set the MTU size to the maximum value supported by your network environment. The desired MTU size must be configured in the vSwitch as well as the guest operating systems.
PAGE 1025
3. Configuration NIC Driver Configuration # ethtool -S eth where eth is the name of the Ethernet device you are working on (for example, eth0). Table 3-4 contains a list of ethtool -S option port statistics counters and their descriptions. To view the port statistics counters on ESXi 5.
PAGE 1026
3. Configuration NIC Driver Configuration Table 3-4 Port Statistics Counters (Continued) Ethtool Statistics Counter Name Description rx_crc_errors The number of packets received with CRC errors. rx_frame_errors The number of packets received with a frame alignment error. rx_fifo_errors The number of received packets dropped when FIFO entering the packet demux block overflows, or an internal FIFO going into the main packet buffer tank (PMEM) overflows.
PAGE 1027
3. Configuration NIC Driver Configuration To view the VxLAN statistics, run the following command: # esxcli elxnet stats get -p | grep vxlan The output should look similar to the following: # esxcli elxnet stats get -p 0000:008:00.
PAGE 1028
3. Configuration iSCSI Driver Configuration iSCSI Driver Configuration Configuring iSCSI Driver Options The following table lists the user configurable iSCSI driver options. It includes a description of the parameters, default values, and the limits within which they can be configured. Note: If the value given for a parameter is outside the supported range (Minimum and Maximum values), then the driver will log an error in the Event Log and continue to load using the default value of the parameter.
PAGE 1029
3. Configuration iSCSI Driver Configuration To configure the ESXi Server to load the iSCSI driver with this value after each reboot, run the following commands and reboot the system: # esxcfg-module -s "ldto=25" be2iscsi # /usr/sbin/esxcfg-boot -r # reboot The im_policy (Interrupt Moderation policy) parameter configures the Emulex iSCSI driver to use different settings for Interrupt Moderation.
PAGE 1030
3. Configuration iSCSI Driver Configuration The maximum value allowed for MaximumSGList is 255 or 0xFF. For the particular value of 0xFF, the internal value passed to Windows is increased to 0x101, allowing support for a full 1-MB transfer (2 MB for 64-bit). The MaximumSGList is 129 for a 512-KB transfer. Other guest operating systems may also need to be tuned similarly. Consult the tuning guides that accompany those operating systems.
PAGE 1031
3. Configuration iSCSI Driver Configuration iSCSI Error Handling The goal of iSCSI error handling is to be tolerant of link level and/or target level failures up to configured timeout values so that I/O errors are not seen by the application or operating system. The error handling is triggered under the following conditions:  Loss of immediate link to the initiator (for example, cable disconnect/port failure). The firmware detects and notifies the driver of a loss of the link.
PAGE 1032
3. Configuration iSCSI Driver Configuration # vmkload_mod be2iscsi ldto=25 To configure ESXi Server to load the iSCSI driver with this value after each reboot, run the following commands and reboot the system: # esxcfg-module -s "ldto=25" be2iscsi # /usr/sbin/esxcfg-boot -r # reboot Multipath I/O Support This section describes the installation and login processes for multipath I/O support.
PAGE 1033
3. Configuration iSCSI Driver Configuration 9. Click Close. 10. A dialog box indicates that a rescan is needed. Click Yes. The configured LUNs are displayed. 11. Repeat the steps to log into the other target portal to set up MPIO. 12. To check that both paths are connected to the same LUN, follow these steps: a. Select the LUN and right-click. b. Click Manage Paths. Multipaths on the LUN are displayed.
PAGE 1034
3. Configuration iSCSI Driver Configuration  echo 0xff > /proc/be2iscsi/log_level – This command sets the log_level value in the driver to enable the desired logging. See Table 3-8 for a list of available log level values. Table 3-8 Log Level Values log_level Value Description 0x01 Enables logging in the iSCSI driver initialization and unload path. 0x02 Enables logging in the iSCSI driver I/O path. 0x04 Enables logging in the iSCSI driver error handling path.
PAGE 1035
4. Troubleshooting Troubleshooting the FC/FCoE Driver 4. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. This section explains many of these circumstances and offers one or more workarounds for each situation. Troubleshooting the FC/FCoE Driver General Situations Table 4-1, General Driver Situations, identifies some of the common situations and their potential resolutions.
PAGE 1036
4. Troubleshooting Troubleshooting the FC/FCoE Driver Table 4-1 General Driver Situations (Continued) Situation Resolution The LPFC driver does not discover all remote ports in the configuration switch zone. Some initiators or targets may appear to be missing. Evaluate your switch zone. Count how many entries there are and add at least seven more (to account for fabric logins). If the sum exceeds 64, you must increase the driver's node table size. The following commands increase it to 128 entries.
PAGE 1037
4. Troubleshooting Troubleshooting the FC/FCoE Driver LPFC Log Messages Log messages have traditionally been organized into logical groups based on code functionality in the FC driver. With the introduction of the latest Emulex adapters, that grouping is modified to account for additional behaviors. The traditional grouping is maintained, but recently added messages are no longer grouped together. The messages provided in this section are unmaskable error conditions.
PAGE 1038
4. Troubleshooting Troubleshooting the FC/FCoE Driver Table 4-2 Message Log Table for ESXi 5.0 and 5.1 Systems (Continued) LOG Message Verbose Mask Definition Verbose Bit Verbose Description LOG_FCP_UNDERRUN 0x100000 FCP underruns LOG_TRC_NODE 0x00200000 Node Trace Events LOG_ALL_MSG 0x7fffffff Log all messages Table 4-3 Message Log Table for ESXi 5.
PAGE 1039
4. Troubleshooting Troubleshooting the FC/FCoE Driver ESXi 5.5 Message Log Example The following is an example of a LOG message on ESXi 5.5 systems: 2013-09-10T16:50:13.137Z cpu7:33329)WARNING: lpfc: lpfc_mbx_cmpl_read_topology:3154: 1:1305 Link Down Event x12 received Data: x12 x20 x110 x0 In the above LOG message:     lpfc - driver binary lpfc_mbx_cmpl_read_topology - function generating the log 1: identifies Emulex HBA1. 1305 identifies the LOG message number.
PAGE 1040
4. Troubleshooting Troubleshooting the FC/FCoE Driver ELS Events (0100 - 0199) elx_mes0100: FLOGI failure Status:/ TMO: DESCRIPTION: An ELS FLOGI command that was sent to the fabric failed. DATA: (1) ulpStatus, (2) ulpWord[4], (3) ulpTimeout ACTION: This error could indicate a fabric configuration error or internal driver issue. If this issue persists, report the error to Emulex technical support.
PAGE 1041
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0125: FDISC Failed (value). Fabric out of resources DESCRIPTION: The fabric rejected an FDISC because the switch can not support any more virtual ports. DATA: None ACTION: Reconfigure the switch to support more NPIV logins. If this issue persists, contact Emulex technical support. elx_mes0126: FDISC failed (ulpStatus/ulpWord[4])\n DESCRIPTION: The ELS FDISC command has failed. DATA: None ACTION: Check the port and switch configuration.
PAGE 1042
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0137: No retry ELS command to remote DESCRIPTION: DATA: (1) ulpStatus, (2) ulpWord[4] ACTION: None required. elx_mes0138: ELS rsp: Cannot issue reg_login for DESCRIPTION: REG_LOGIN mailbox command failed. DATA: (1) nlp_DID, (2) nlp_state, (3) nlp_flag, (4) nlp_rpi ACTION: None required. elx_mes0140: PLOGI Reject: invalid nname DESCRIPTION: Invalid node WWN provided. DATA: None ACTION: None required.
PAGE 1043
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0148: Failed to allocate memory for LOGO event DESCRIPTION: Memory could not be allocated to send the LOGO event to the FC transport. DATA: None ACTION: None required. elx_mes0154: Authentication not complete DESCRIPTION: Memory could not be allocated to send the LOGO event to the FC transport. DATA: None ACTION: None required. Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev.
PAGE 1044
4. Troubleshooting Troubleshooting the FC/FCoE Driver Link Discovery Events (0200 - 0299) elx_mes0200: CONFIG_LINK bad hba state DESCRIPTION: A CONFIG_LINK mailbox command completed and the driver was not in the right state. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support.
PAGE 1045
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0223: Timeout while waiting for NameServer login DESCRIPTION: Our login request to the NameServer was not acknowledged within RATOV. DATA: None ACTION: Check the fabric configuration. The driver recovers from this and continues with device discovery. elx_mes0224: NameServer Query timeout DESCRIPTION: Node authentication timeout, node Discovery timeout.
PAGE 1046
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0237: Pending Link Event during Discovery: State DESCRIPTION: DATA: None ACTION: None required. elx_mes0241: NameServer Rsp Error Data: DESCRIPTION: DATA: None ACTION: None required. elx_mes0246: RegLogin failed DESCRIPTION: The firmware returned a failure for the specified RegLogin. DATA: (1) Did, (2) mbxStatus, (3) hbaState ACTION: This message indicates that the firmware could not perform a RegLogin for the specified DID.
PAGE 1047
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0254: Register VPI: no memory goto mbox_err_exit DESCRIPTION: Could not allocate memory for the REG_LOGIN mailbox command. DATA: None ACTION: None required. elx_mes0255: Issue FDISC: no IOCB DESCRIPTION: All of the pre-allocated IOCBs are in use. DATA: None ACTION: None required. elx_mes0256: Issue FDISC: Cannot send IOCB DESCRIPTION: Unable to send the fabric IOCB. DATA: None ACTION: Check the switch configuration.
PAGE 1048
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: At least one message (0142 0121 0133 0134 0135) should precede this message. elx_mes0262: No NPIV Fabric support DESCRIPTION: The switch to which the port is connected does not support NPIV. DATA: None ACTION: Check the switch configuration. elx_mes0263: Discovery Mailbox error: state: : DESCRIPTION: Either the driver could not allocate resources or it could not send sparam_mbox or cfglink_mbox.
PAGE 1049
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0271: Illegal State Transition: node event , state Data: DESCRIPTION: The current node state does not have a handler for this event. DATA: (1) nlp_rpi, (2) nlp_flag ACTION: Verify that all targets are still visible to the SCSI mid-layer.
PAGE 1050
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes0287: lpfc_alloc_bucket failed to allocate statistical data buffer DESCRIPTION: Memory allocation failed for node’s statistical data. DATA: None ACTION: None required. elx_mes0288: Unknown FCoE event type event tag DESCRIPTION: The firmware has detected an unknown FCoE event. DATA: None ACTION: Check the FCoE switch configuration and the adapter DCBX mode.
PAGE 1051
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0297:invalid device group DESCRIPTION: While unloading the driver, the driver detect a PCI device that it should not have claimed. DATA: None ACTION: None required. elx_mes0299: Invalid SLI revision DESCRIPTION: While processing a host attention or unrecoverable error, the driver detected an invalid SLI revision. DATA: None ACTION: None required. Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev.
PAGE 1052
4. Troubleshooting Troubleshooting the FC/FCoE Driver Mailbox Events (0300 - 0339) elx_mes0300: LATT: Cannot issue READ_LA: Data: DESCRIPTION: The link attention handler could not issue a READ_LA mailbox command. DATA: None ACTION: None required. elx_mes0303: Ring handler: portRspPut is bigger then rsp ring DESCRIPTION: The port rsp ring put index is larger than the size of the rsp ring.
PAGE 1053
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0311 Mailbox command cannot issue Data: DESCRIPTION: The driver detected an HBA error and can't issue the mailbox. DATA: (1) sli flags (2) hba flags ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes0312: Ring handler: portRspPut is bigger then rsp ring DESCRIPTION: The IOCB command rings put pointer is ahead of the get pointer.
PAGE 1054
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: This error could indicate a firmware or hardware issue. Report these errors to Emulex technical support. elx_mes0323: Unknown Mailbox command Cmpl DESCRIPTION: A unknown mailbox command completed. DATA: None ACTION: This error could indicate a software driver, firmware or hardware issue. Report these errors to Emulex technical support.
PAGE 1055
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0338: IOCB wait timeout error - no wake response Data DESCRIPTION: Driver issued I/O did not get a wake signal in polling mode. DATA: (1) wait time (2) wake value ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes0340: Adapter temperature is OK now DESCRIPTION: Adapter temperature has reverted to normal range.
PAGE 1056
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0345: Resetting board due to mailbox timeout DESCRIPTION: A mailbox command failed to complete. The driver is resetting the port. DATA: None ACTION: If the mailbox command fails again, set the lpfc_log_verbose to LOG_MBOX and retry. elx_mes0346: Ring handler: unexpected ASYNC_STATUS evt_code DESCRIPTION: The adapter received an asynchronous event that was not a temperature event. DATA: None ACTION: None required.
PAGE 1057
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0352: Config MSI mailbox command failed, mbxCmd , mbxStatus DESCRIPTION: The mailbox command sent to the firmware to configure the adapter to use MSI-X has failed. DATA: None ACTION: Ensure the hardware platform supports MSI-X. elx_mes0359: Not a valid slow-path completion event: majorcode=, minorcode= DESCRIPTION: SLI-4: The EQE is not valid. DATA: None ACTION: None required.
PAGE 1058
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0366: Not a valid fast-path completion event: majorcode=, minorcode= DESCRIPTION: The major or minor code in the Event Queue field is not valid. DATA: None ACTION: None required. elx_mes0367: Fast-path completion queue does not exist DESCRIPTION: The fast path completion queue referenced by the CQID does not exist. DATA: None ACTION: None required.
PAGE 1059
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0376: READ_REV Error. SLI Level FCoE enabled DESCRIPTION: This SLI-4 only adapter setup function was called for a non-SLI-4 device. DATA: None ACTION: None required. elx_mes0377: Error parsing vpd. Using defaults. DESCRIPTION: Could not parse the VPD data, so the driver is using the default values. DATA: None ACTION: None required. elx_mes0381: Error during queue setup.
PAGE 1060
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0385: rc should have been MBX_BUSY DESCRIPTION: The completion handler for REG_LOGIN detected the IMMED_UNREG flag and tried to issue the unreg_login command from an interrupt level. The mailbox status should still be busy. DATA: None ACTION: None required. elx_mes0387: Failed to allocate an iocbq DESCRIPTION: Failed to get an IOCBQ from the list of available IOCBQs. DATA: None ACTION: None required.
PAGE 1061
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes0396: The lpfc_dmabuf allocation failed DESCRIPTION: The asynchronous link event handler could not allocate a DMA buffer for the mailbox command to issue the READ_LA (read link attention) mailbox command. DATA: None ACTION: None required. elx_mes0397: The mbuf allocation failed DESCRIPTION: The asynchronous link event handler could not allocate DMA-able memory for the READ_LA mailbox command.
PAGE 1062
4. Troubleshooting Troubleshooting the FC/FCoE Driver Initialization Events (0400 - 0599) elx_mes0400: Phys Attribute Count Exceeded, Max , Actual DESCRIPTION: Too many driver configuration parameters have been set. The limit is given as Max. DATA: (1) Maximum number (2) Actual number ACTION: Reduce the number of actual parameters. elx_mes0402: Cannot find virtual addr for buffer tag on ring DESCRIPTION: A DMA buffer is not available for this unsolicited command.
PAGE 1063
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0408: Cannot create debugfs root DESCRIPTION: DATA: None ACTION: None required. elx_mes0409: Cannot create debugfs nodelist DESCRIPTION: DATA: None ACTION: None required. elx_mes0410: Cannot find virtual addr for mapped buf on ring DESCRIPTION: The driver cannot find the specified buffer in its mapping table. Thus it cannot find the virtual address needed to access the data.
PAGE 1064
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0415: Cannot create debugfs slow_ring trace DESCRIPTION: DATA: None ACTION: None required. elx_mes0416: Cannot create debugfs slow_ring buffer DESCRIPTION: DATA: None ACTION: None required. elx_mes0417: Cannot create debugfs DESCRIPTION: DATA: None ACTION: None required. elx_mes0418: Cannot create debugfs disc trace buffer DESCRIPTION: DATA: None ACTION: None required.
PAGE 1065
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0425: lpfc_"#attr" attribute cannot be set to , allowed range is [min, max] DESCRIPTION: Driver attribute lpfc_#attr was defined with an out-of-range value. DATA: None ACTION: Set the parameter between the minimum and maximum value. elx_mes0426: lpfc_enable_auth attribute cannot be set to , allowed range is [, ] DESCRIPTION: DATA: None ACTION: None required. elx_mes0427: Cannot re-enable interrupt after slot reset.
PAGE 1066
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0435: Adapter failed to get Option ROM version status . DESCRIPTION: The driver could not read the adapter’s option ROM. DATA: None ACTION: Reset the adapter. Ensure that the adapter’s firmware is current. elx_mes0436: Adapter failed to init, timeout, status reg DESCRIPTION: The adapter failed during power-up diagnostics after it was reset. DATA: None ACTION: This error could indicate a hardware or firmware issue.
PAGE 1067
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0442: Adapter failed to init, mbxCmd CONFIG_PORT, mbxStatus DESCRIPTION: Adapter initialization failed when issuing a CONFIG_PORT mailbox command. DATA: (1) hbainit ACTION: This error could indicate a hardware or firmware issue. If the issue persists, report the error to Emulex technical support. elx_mes0443: Adapter failed to set maximum DMA length mbxStatus .
PAGE 1068
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Write the default value. elx_mes0450: lpfc_%attr attribute cannot be set to , allowed range is [%min, %max] DESCRIPTION: Sysfs attribute value written exceeds attribute range. DATA: (1) attribute name, (2) value written, (3) minimum value, (3) maximum value ACTION: Write a value within the supported range. elx_mes0451: Failed to enable interrupt DESCRIPTION: DATA: None. ACTION: None required.
PAGE 1069
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0472: Unknown PCI error state: DESCRIPTION: The PCI bus has detected an error. DATA: (1) state value ACTION: Driver resets the adapter and attempts recovery. If the issue persists, contact Emulex technical support. elx_mes0474: Unable to allocate memory for issuing "MBOX_CONFIG_MSI command” DESCRIPTION: Mailbox memory pool allocation error. DATA: None ACTION: None required.
PAGE 1070
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0492: Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command DESCRIPTION: A memory allocation fault occurred when issuing a mailbox. DATA: None ACTION: This could be a transient error. If this issue persists, report these errors to Emulex technical support. elx_mes0493: SLI_CONFIG_SPECIAL mailbox failed with status . DESCRIPTION: Mailbox command failed. DATA: None ACTION: Ensure the adapter’s firmware is current.
PAGE 1071
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0499: Failed allocate fast-path FCP CQ (). DESCRIPTION: The completion queue event for the fast path could not be allocated. DATA: None ACTION: The driver fails to load. Contact Emulex technical support. elx_mes0500: Failed allocate slow-path mailbox CQ DESCRIPTION: Failed to allocate slow-path mailbox CQ. DATA: None ACTION: The driver fails to load. Contact Emulex technical support.
PAGE 1072
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0520: Slow-path EQ not allocated DESCRIPTION: The slow-path EQ is not allocated. DATA: None ACTION: The driver fails to load. Contact Emulex technical support. elx_mes0521: Failed setup of slow-path EQ rc = DESCRIPTION: The slow-path EQ setup failed with status rc. DATA: (1) status code ACTION: The driver fails to load. Contact Emulex technical support.
PAGE 1073
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes0530: ELS CQ not allocated DESCRIPTION: The ELS CQ is not allocated. DATA: None ACTION: The driver fails to load. Contact Emulex technical support. elx_mes0531: Failed setup of slow-path ELS CQ: rc = DESCRIPTION: The ELS CQ is allocated, but failed initial setup. DATA: (1) status ACTION: The driver fails to load.
PAGE 1074
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0539: Failed setup of slow-path MQ: rc = DESCRIPTION: The slow-path MQ is allocated, but failed initial setup. DATA: (1) status ACTION: The driver fails to load. Contact Emulex technical support. elx_mes0540: Receive Queue not allocated DESCRIPTION: The Receive Queue is not allocated. DATA: None ACTION: The driver fails to load. Contact Emulex technical support.
PAGE 1075
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0602: Failed to allocate CQ_EVENT entry DESCRIPTION: Failed to allocate a CQ_EVENT entry. DATA: None ACTION: None required. elx_mes0603: Invalid work queue CQE subtype DESCRIPTION: Invalid work queue CQE. DATA: None ACTION: None required. FCP Traffic History (0700 - 0799) elx_mes0700: Bus Reset on target failed DESCRIPTION: The bus reset for the specified target failed. DATA: None ACTION: None required.
PAGE 1076
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes0718: Unable to dma_map single request_buffer: DESCRIPTION: The driver could not map a single virtual address to a DMA address. DATA: (1) DMA mapping error ACTION: None. The driver fails the I/O back to ESXi. elx_mes0720: FCP command residual overrun error. Data: DESCRIPTION: DATA: None ACTION: None required. elx_mes0721: Device Reset rport failure: rdata DESCRIPTION: The reset of the Rport failed.
PAGE 1077
4. Troubleshooting Troubleshooting the FC/FCoE Driver Node Table Events (0900 - 0999) elx_mes0915: Register VPI failed: DESCRIPTION: Could not register the VPI. DATA: None ACTION: None required. Security Events (1000 - 1099) elx_mes1000: Authentication is enabled but authentication service is not running DESCRIPTION: DATA: None ACTION: None required. elx_mes1005: AUTHENTICATION_FAILURE Nport: DESCRIPTION: DATA: None ACTION: None required.
PAGE 1078
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1010: Bad Tag 1 DESCRIPTION: DATA: None ACTION: None required. elx_mes1011: Auth_neg no has function chosen. DESCRIPTION: DATA: None ACTION: None required. elx_mes1012: Auth_negotiate Bad Tag 2 DESCRIPTION: DATA: None ACTION: None required. elx_mes1013: Auth_negotiate no DH_group found. DESCRIPTION: DATA: None ACTION: None required. elx_mes1014: dhchap challenge bad name tag. DESCRIPTION: DATA: None ACTION: None required.
PAGE 1079
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1018: dhchap challenge No Public key for non-NULL DH Group. DESCRIPTION: DATA: None ACTION: None required. elx_mes1021: ERROR: attempted to queue security work, when no workqueue created. DESCRIPTION: DATA: None ACTION: None required. elx_mes1028: Start Authentication: No buffers DESCRIPTION: DATA: None ACTION: None required. elx_mes1029: Reauthentication Failure DESCRIPTION: DATA: None ACTION: None required.
PAGE 1080
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes1036: Authentication transaction reject - re-auth request reason exp DESCRIPTION: DATA: None ACTION: None required. elx_mes1037: Authentication transaction reject - restarting authentication. reason exp DESCRIPTION: DATA: None ACTION: None required. elx_mes1039: Not Expecting Reply - rejecting. State DESCRIPTION: DATA: None ACTION: None required.
PAGE 1081
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1049: Authentication is enabled but authentication service is nor running DESCRIPTION: DATA: None ACTION: None required. elx_mes1050: Authentication mode is disabled, but is required by the fabric. DESCRIPTION: DATA: None ACTION: None required. elx_mes1053: Start Authentication: Security service offline. DESCRIPTION: DATA: None ACTION: None required. elx_mes1055: Authentication parameter is disabled, but is required by the fabric.
PAGE 1082
4. Troubleshooting Troubleshooting the FC/FCoE Driver Miscellaneous and FCoE Events (1200 - 1299) elx_mes1201: Failed to allocate dfc_host DESCRIPTION: Driver failed to allocate a DFC host and bind it to the management stack. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1209: C_CT Request error Data: DESCRIPTION: IOCTL CT response error - driver is failing the IOCTL request.
PAGE 1083
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1215: Cannot issue FCoE cmd: not ready or not in maint mode DESCRIPTION: DATA: None ACTION: None required. elx_mes1216: FCoE IOCB failed: DESCRIPTION: DATA: None ACTION: None required. elx_mes1223: menlo_write: couldn’t alloc genreq DESCRIPTION: DATA: None ACTION: None required.
PAGE 1084
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1240: Unable to allocate command buffer memory. DESCRIPTION: DATA: None ACTION: None required. elx_mes1243: Menlo command error. code=. DESCRIPTION: DATA: None ACTION: None required. elx_mes1244: Unable to allocate response buffer memory. DESCRIPTION: DATA: None ACTION: None required. elx_mes1246: FCoE chip is running golden firmware. Update FCoE chip firmware immediately DESCRIPTION: DATA: None ACTION: None required.
PAGE 1085
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1250: Menlo command error. code= DESCRIPTION: DATA: None ACTION: None required. elx_mes1251: Menlo command error. code= DESCRIPTION: DATA: None ACTION: None required. elx_mes1252: Menlo command error. code= DESCRIPTION: DATA: None ACTION: None required. elx_mes1262: Failed to allocate dfc_host DESCRIPTION: Could not allocate memory the dfc_host_struct. DATA: None ACTION: None required. Emulex Drivers Version 10.
PAGE 1086
4. Troubleshooting Troubleshooting the FC/FCoE Driver Link Events (1300 - 1399) elx_mes1300: Link Down Event in loop back mode DESCRIPTION: Driver received a link down event while in loopback mode unexpected event. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1302: Invalid speed for this board: Reset link speed to auto: DESCRIPTION: Driver detected an invalid link speed. Resetting Link to Auto mode.
PAGE 1087
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes1309: Link Down Event received Data DESCRIPTION: The port generated a link down event to the host. DATA: (1) fc_eventTag (2)port_state (3) VPort fc_flag ACTION: None required. elx_mes1310: Link Up Event npiv not supported in loop topology DESCRIPTION: Loop topologies are not supported when NPIV is enabled. DATA: None ACTION: Put link into Fabric mode.
PAGE 1088
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1405: Failed to initialize iocb list. DESCRIPTION: IOCB initialization failed. DATA: None ACTION: None required. elx_mes1406: Failed to set up driver resource. DESCRIPTION: Initialization failed to set up driver resource. DATA: None ACTION: None required. elx_mes1407: Failed to create scsi host. DESCRIPTION: Initialization failed to create SCSI host. DATA: None ACTION: None required.
PAGE 1089
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1413: Failed to initialize iocb list. DESCRIPTION: Initialization failed to initialize the IOCB list. DATA: None ACTION: None required. elx_mes1414: Failed to set up driver resource. DESCRIPTION: Initialization failed to set up driver resource. DATA: None ACTION: None required. elx_mes1415: Failed to create scsi host. DESCRIPTION: Initialization failed to create SCSI host. DATA: None ACTION: None required.
PAGE 1090
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1422: Unrecoverable Error Detected during POST uerr_lo_reg=, uerr_hi_reg= DESCRIPTION: The adapter has notified the driver that it has encountered an unrecoverable error. DATA: None ACTION: A dump from the OneCommand Manager application should be taken. Then, the driver should be unloaded and reloaded.
PAGE 1091
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes1429: Invalid PCI device group: DESCRIPTION: Invalid adapter PCI-device group detected. DATA: None ACTION: None required. elx_mes1430: Failed to initialize sgl list. DESCRIPTION: Failed to initialize SGL list. DATA: None ACTION: None required. elx_mes1431: Invalid HBA PCI-device group: DESCRIPTION: Invalid adapter PCI-device group detected. DATA: None ACTION: None required.
PAGE 1092
4. Troubleshooting Troubleshooting the FC/FCoE Driver VPort Events (1800 - 1832) elx_mes1800: Could not issue unreg_vpi DESCRIPTION: Driver attempt to unregister VPI failed. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1801: Create vport work array FAILED: cannot do scsi_host_get DESCRIPTION: Driver failed to create working list of VPorts. DATA: None ACTION: Software driver error.
PAGE 1093
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1806: Mbox failed. No vport. DESCRIPTION: A mailbox command could not be communicated because there was no VPort associated with the mailbox command. DATA: (1) mbxCommand ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1807: IOCB failed.
PAGE 1094
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1812: vport_delete failed: Cannot delete physical host DESCRIPTION: An attempt to delete a port failed because it was to delete a physical port and not a virtual port. Only VPorts on physical ports can be deleted on an NPIV system. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1813: Create VPORT failed. Cannot get sparam.
PAGE 1095
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1821: Create VPORT failed. Invalid WWN format DESCRIPTION: The port could not be created due to an invalid WWNN or WWPN format. DATA: None ACTION: Provide a valid WWN when creating VPorts. elx_mes1822: Invalid : DESCRIPTION: An invalid WWN was used when creating a VPort. DATA: (1) type_name, (2) wwn[1], (3) wwn[3], (3) wwn[5], (4) wwn[7] ACTION: When creating a VPort you must furnish a valid WWN.
PAGE 1096
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1830: Signal aborted mbxCmd DESCRIPTION: A pending mailbox command was aborted because the thread received a signal. DATA: None ACTION: The command is retried. elx_mes1831: Create VPORT Interrupted. DESCRIPTION: The port creation process was unexpectedly interrupted at a critical time and the operation was unsuccessful. DATA: None ACTION: The process was interrupted while creating a VPort. Retry the command.
PAGE 1097
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1839: Create VPORT failed. vname allocation failed. DESCRIPTION: Driver failed to allocate buffer for Virtual Machine name. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1840: Delete VPORT cannot proceed at this time due to SCSI layer busy. DESCRIPTION: DATA: None ACTION: None required.
PAGE 1098
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1929: Exec format error DESCRIPTION: No dfchba instance available for IOCTL loopback XRI read - dropping. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support.
PAGE 1099
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes1950: ENOMEM IOCB resource not available DESCRIPTION: Driver could not allocate IOCBs needed to post loopback receive buffers. DATA: (1) (2) (3) ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes1951: ENOMEM MBUF resource not available DESCRIPTION: Driver failed to get memory buffer needed for loopback test. DATA: None ACTION: Software driver error.
PAGE 1100
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2007: Only Limited Edition cmd Format supported DESCRIPTION: SLI-4 only supports the Limited Edition command format. DATA: None ACTION: None required. elx_mes2008: Error posting all rpi headers DESCRIPTION: The RPI headers could not be posted to the firmware. DATA: None ACTION: None required.
PAGE 1101
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2014: Invalid command DESCRIPTION: The IOCB command is invalid. DATA: None ACTION: None required. elx_mes2015: Invalid CT command DESCRIPTION: Invalid Command-Type in the IOCB is not supported. DATA: None ACTION: None required. elx_mes2017: REG_FCFI mbxStatus error HBA state . DESCRIPTION: The REG_FCFI mailbox command has failed.
PAGE 1102
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2501: CQ_CREATE mailbox failed with status add_status , mbx status DESCRIPTION: The mailbox command sent to create the completion queue has failed. DATA: None ACTION: None required. elx_mes2502: MQ_CREATE mailbox failed with status add_status , mbx status DESCRIPTION: The mailbox command sent to create the mailbox queue has failed. DATA: None ACTION: None required.
PAGE 1103
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2508: WQ_DESTROY mailbox failed with status add_status , mbx status DESCRIPTION: The mailbox command sent to delete the work queue has failed. DATA: None ACTION: None required. elx_mes2509: RQ_DESTROY mailbox failed with status add_status , mbx status DESCRIPTION: The mailbox command sent to delete the receive queue has failed.
PAGE 1104
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2514: POST_RPI_HDR mailbox failed with status add_status , mbx status DESCRIPTION: The mailbox command sent to post the RPUI header pages to the firmware has failed. DATA: None ACTION: None required. elx_mes2515: ADD_FCF_RECORD mailbox failed with status DESCRIPTION: The mailbox command to add the FCF record has failed. DATA: None ACTION: None required.
PAGE 1105
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2527: Failed to allocate non-embedded SGE array. DESCRIPTION: Failed to allocate the non-embedded SGE array. DATA: None ACTION: None required. elx_mes2528: Mailbox command cannot issue DESCRIPTION: The mailbox command could not be issued because the mailbox interrupt is disabled. DATA: (1) mbxCommand, (2) sli_flag, (3) flag ACTION: None required.
PAGE 1106
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2536: Unsupported RQ count. (). DESCRIPTION: The receive queue ring can only be 512, 1024, 2048, or 4096. DATA: None ACTION: None required. elx_mes2537: Receive Frame Truncated! DESCRIPTION: The receive unsolicited handler detected a truncated frame. DATA: None ACTION: None required.
PAGE 1107
4. Troubleshooting Troubleshooting the FC/FCoE Driver DATA: None ACTION: None required. elx_mes2549: FCF disconnected from network index tag . DESCRIPTION: The FCF has disconnected from the network. DATA: None ACTION: None required. elx_mes2550: UNREG_FCFI mbxStatus error HBA state . DESCRIPTION: The unregistered FCFI has failed. DATA: None ACTION: None required. elx_mes2551: UNREG_FCFI mbox allocation failed HBA state .
PAGE 1108
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2555: UNREG_VFI mbxStatus error HBA state DESCRIPTION: The unregister VFI mailbox command has failed. DATA: None ACTION: None required. elx_mes2556: UNREG_VFI mbox allocation failed HBA state DESCRIPTION: Could not allocate memory for UNREG_VFI mailbox command. DATA: None ACTION: None required.
PAGE 1109
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2563: Failure to allocate an ELS mbuf: DESCRIPTION: DATA: None ACTION: None required. elx_mes2564: POST_SGL_BLOCK mailbox command failed status add_status mbx status DESCRIPTION: The list of XRI SGEs failed to be registered with the firmware. DATA: None ACTION: None required. elx_mes2566: Failed to allocate connection table entry DESCRIPTION: Failed to allocate connection table entry.
PAGE 1110
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2574: Not enough EQs () from the pci function for supporting FCP EQs () DESCRIPTION: Failed to create the minimum fast-path event queues. DATA: None ACTION: None required. elx_mes2576: Failed allocate memory for fast-path EQ record array DESCRIPTION: Failed to allocate memory for the fast-path EQ record array. DATA: None ACTION: None required.
PAGE 1111
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2600: failed to allocate mailbox memory DESCRIPTION: Failed to allocate mailbox memory. DATA: None ACTION: None required. elx_mes2605: lpfc_dump_static_vport: memory allocation failed DESCRIPTION: Memory allocation failed. DATA: None ACTION: None required. elx_mes2606: No NPIV Fabric support DESCRIPTION: No NPIV Fabric support. DATA: None ACTION: None required.
PAGE 1112
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2620: Config region 23 has bad version DESCRIPTION: Configuration region 23 has an invalid version. DATA: None ACTION: None required. elx_mes2707: Ring handler: Failed to allocate iocb Rctl Type received DESCRIPTION: Could not allocate an IOCB with which to associate this received frame. DATA: None ACTION: None required.
PAGE 1113
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2719: Invalid response length: tgt lun cmnd rsplen DESCRIPTION: The response length for this FCP command is not supported. DATA: None ACTION: None required. elx_mes2723 PCI channel I/O abort preparing for recovery DESCRIPTION: Driver is preparing port PCI channel for reset/recovery after I/O error. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support.
PAGE 1114
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes2746: Requesting for FCF rediscovery failed status add_status DESCRIPTION: DATA: None ACTION: None required.
PAGE 1115
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: If the issue persists, report the error to Emulex technical support. elx_mes2753: PLOGI failure DID: Status:/. DESCRIPTION: A PLOGI to was failed either by the driver, firmware, or target. The and indicates why the PLOGI failed. DATA: None ACTION: If the issue persists, report the error to Emulex technical support.
PAGE 1116
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2759: Failed to allocate memory for round robin FCF failover bmask. DESCRIPTION: The driver failed to allocate memory for the round robin FCF failover bmask. DATA: None ACTION: Make sure system has enough kernel memory, might need to reload the driver after memory issue resolved. elx_mes2762: FCF reached driver’s book keeping dimension: DESCRIPTION: DATA: None ACTION: Inform Emulex about this.
PAGE 1117
4. Troubleshooting Troubleshooting the FC/FCoE Driver New Events elx_mes2796: Mailbox memory allocation failed DESCRIPTION: The driver failed to get memory resources to release an RPI. DATA: None. ACTION: None. The driver's heap is exhausted. A server reboot is required to fix the exhaustion. Contact Emulex technical support if the issue persists. elx_mes2798: Unreg_vpi failed vpi , mb status = DESCRIPTION: The driver attempted to unregister a virtual port index and failed.
PAGE 1118
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: A system reboot may be required to fully recover. Contact Emulex technical support if issues persist. elx_mes2825: Unknown PCI error state: DESCRIPTION: The driver writes this message to the console when the PCI subsystem has detected an error on an Emulex port and called the driver. The driver reacts by resetting the port. DATA: None ACTION: None required. The driver resets the device in an attempt to recover.
PAGE 1119
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2856: Config Port Security Crypto Error: , pmb->u.mb.un.varCfgPort.sec_err DESCRIPTION: DATA: None ACTION: None required. elx_mes2858: FLOGI failure Status:/ TMO: DESCRIPTION: The driver issued a FLOGI, but never received any completion with the timeout period. The driver is marking the FLOGI as failed and stops discovery. DATA: None ACTION: Check your Fabric to ensure it is operating correctly.
PAGE 1120
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2878: ELS XRI exchange busy wait time: seconds DESCRIPTION: An ELS exchange cannot be released - no port completion. Driver is waiting. DATA: None ACTION: Software driver error. If this issue persists, report these errors to Emulex technical support. elx_mes2881: RRQ failure DID: Status:/ DESCRIPTION: Driver RRQ request failed - driver write target DID and status values. DATA: None ACTION: Software driver error.
PAGE 1121
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes2888: Unrecoverable port error following POST: port status reg , port smphr reg , error 1=, error 2= DESCRIPTION: DATA: None ACTION: None required. elx_mes2889: Port Overtemperature event, taking port DESCRIPTION: DATA: None ACTION: None required.
PAGE 1122
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2895: Non FC link Event detected.() DESCRIPTION: DATA: None ACTION: None required. elx_mes2897: The mboxq allocation failed DESCRIPTION: DATA: None ACTION: None required. elx_mes2898: The lpfc_dmabuf allocation failed DESCRIPTION: DATA: None ACTION: None required. elx_mes2899: The mbuf allocation failed DESCRIPTION: DATA: None ACTION: None required.
PAGE 1123
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2929: Resource Extent Opcode is unsupported DESCRIPTION: DATA: None ACTION: None required. elx_mes2930: Failed to get resource extents Status Add'l Status DESCRIPTION: DATA: None ACTION: None required. elx_mes2936: Could not find Vport mapped to vpi DESCRIPTION: DATA: None ACTION: None required.
PAGE 1124
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes2954: SLI_CONFIG(hbd) wr to interface type: DESCRIPTION: DATA: None ACTION: None required. elx_mes2999: Unsupported SLI4 Parameters Extents and RPI headers enabled. DESCRIPTION: DATA: None ACTION: None required. elx_mes3008: No available Resource Extents for resource type : Count: , Size DESCRIPTION: DATA: None ACTION: None required.
PAGE 1125
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes3061: Last IDX DESCRIPTION: DATA: None ACTION: None required. elx_mes3069: Clearing FCP rules DESCRIPTION: DATA: None ACTION: None required. elx_mes3070: lpc_clr_ndlps_pri: fcp_priority sz = DESCRIPTION: DATA: None ACTION: None required. elx_mes3071: no memory for priority rules DESCRIPTION: DATA: None ACTION: None required.
PAGE 1126
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes3105: failed to allocate mailbox memory DESCRIPTION: DATA: None ACTION: None required. elx_mes3112: lpfc_link_speed attribute cannot be set to . Speed is not supported in loop mode. DESCRIPTION: DATA: None ACTION: None required. elx_mes3113: Loop mode not supported at speed DESCRIPTION: DATA: None ACTION: None required.
PAGE 1127
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes3144: Port Down: Debug Dump DESCRIPTION: DATA: None ACTION: None required. elx_mes3145: Port Down: Provisioning DESCRIPTION: DATA: None ACTION: None required. elx_mes3147: Fast-path EQs not allocated DESCRIPTION: DATA: None ACTION: None required. elx_mes3148: Fast-path FCP CQ array not allocated DESCRIPTION: DATA: None ACTION: None required. elx_mes3149: Fast-path FCP WQ array not allocated DESCRIPTION: DATA: None ACTION: None required.
PAGE 1128
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: Contact Emulex technical support. elx_mes3153: Fail to perform the requested access: DESCRIPTION: Driver failed to execute the requested management action. DATA: Register action. ACTION: Contact Emulex technical support. elx_mes3154: BLS ABORT RSP failed, data DESCRIPTION: Driver issued BLS ABORT Response failed to complete. DATA: I/O status and I/O reason ACTION: Contact Emulex technical support.
PAGE 1129
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes3249: Unable to allocate memory for QUERY_FW_CFG mailbox command DESCRIPTION: DATA: None ACTION: None required. elx_mes3250: QUERY_FW_CFG mailbox failed with status add_status , mbx status DESCRIPTION: DATA: None ACTION: None required. elx_mes3252: WQ doorbell offset not supported DESCRIPTION: DATA: None ACTION: None required. elx_mes3262: RQ doorbell format not supported DESCRIPTION: DATA: None ACTION: None required.
PAGE 1130
4. Troubleshooting Troubleshooting the FC/FCoE Driver elx_mes3270: RQ doorbell format not supported: DESCRIPTION: DATA: None ACTION: None required. elx_mes3279: Invalid provisioning of rpi DESCRIPTION: DATA: None ACTION: None required. elx_mes3280: Invalid provisioning of vpi DESCRIPTION: DATA: None ACTION: None required. elx_mes3281: Invalid provisioning of xri DESCRIPTION: DATA: None ACTION: None required. elx_mes3282: Invalid provisioning of vfi DESCRIPTION: DATA: None ACTION: None required.
PAGE 1131
4. Troubleshooting Troubleshooting the FC/FCoE Driver ACTION: None required. elx_mes3321: Recovered mailbox DESCRIPTION: DATA: None ACTION: None required. elx_mes9000: Allocated DMA memory size () is less than the requested DMA memory size () DESCRIPTION: DATA: None ACTION: None required. Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev.
PAGE 1132
4. Troubleshooting Troubleshooting the NIC Driver Troubleshooting the NIC Driver The following section includes NIC troubleshooting information. Be sure to check the readme.txt file located on CD1 for other troubleshooting issues. The following table provides troubleshooting information for the NIC driver. Table 4-4 Troubleshooting the NIC Driver Issue Resolution 1) When there is a great deal of network traffic in some VMs, a few VMs appear to have lost network connectivity.
PAGE 1133
4. Troubleshooting Troubleshooting the NIC Driver NIC Event/Error Logging for ESXi 5.0 and 5.1 Retrieving ESXi Server NIC Error Log Codes For ESXi Server systems, the NIC driver generates error codes to the /var/log/vmkernel log file. The vmkernel log file is an ASCII text file that can be viewed and searched with a text editor such as vim. The vmkernel log file is automatically rotated as it gets larger, and the rotated log files are named vmkernel.x, where x is an integer.
PAGE 1134
4. Troubleshooting Troubleshooting the NIC Driver Table 4-5 ESXi Server NIC Event Log Entries (Continued) Severity Displayed Message Description Warning WARNING: Found a OneConnect card in Gen x PCI-e slot. Should be in Gen 2, x8 slot for best performance The adapter is an x8, Gen2 PCI-e device. For best performance, the adapter should be installed in a Gen2 PCI-e slot 8 or 16 channels wide. The driver displays this warning if it finds the device in a slower or narrower PCI-e slot.
PAGE 1135
4. Troubleshooting Troubleshooting the NIC Driver Table 4-5 ESXi Server NIC Event Log Entries (Continued) Severity Displayed Message Description Warning Invalid MTU requested. MTU must be between 64 and 9000 bytes. Invalid MTU size in MTU configuration IOCTL. The MTU will not be changed. Warning Invalid vlan priority labeled. Must be 0 - 7 A request to set a VLAN priority tag was made with an invalid value.
PAGE 1136
4. Troubleshooting Troubleshooting the iSCSI Driver Troubleshooting the iSCSI Driver The following table provides information on troubleshooting the iSCSI driver. Table 4-6 Troubleshooting the iSCSI Driver Issue Resolution Mutual CHAP authentication cannot be One-way CHAP is the only authentication method that can be configured with the vSphere client. configured with the vSphere Client. In order to set Mutual CHAP authentication, you must use iSCSISelect.
PAGE 1137
4. Troubleshooting Troubleshooting the iSCSI Driver Table 4-7 iSCSI Error Log Code Entries (Continued) Severity Message Recommended Resolution Error The be2iscsi driver ignored a configuration entry since the entry was invalid. Check the registry configuration for any recent entries added for driver parameters. The invalid entry must be removed or corrected. Error The be2iscsi driver failed to load due to memory allocation failure.
PAGE 1138
4. Troubleshooting Troubleshooting the iSCSI Driver Table 4-7 iSCSI Error Log Code Entries (Continued) Severity Message Recommended Resolution Warning A connection to the target was lost for a period exceeding the Extended Timeout (ETO). The error log entry immediately following this entry will indicate the session ID of the target that lost the connection. There will be event log entries from the disk subsystem indicating that the drives were lost.
PAGE 1139
4. Troubleshooting Troubleshooting the iSCSI Driver Additional iSCSI Driver Messages The following iSCSI error messages are returned when you specify illegal options when loading the driver: Table 4-8 Additional iSCSI Driver Messages Message “be2iscsi : WARNING: dic value = %d out of range. Valid range is 0 - 1. Using default value = 1” “be2iscsi : WARNING: eto value = %d out of range. Valid range is 0 - 3600.
PAGE 1140
4. Troubleshooting Troubleshooting the iSCSI Driver Table 4-9 Data String Parameters for Option 43 (Continued) Parameter Description Field Type It is hexadecimal representation of Logical Unit number of Optional the boot device. If not provided, LUN 0 is assumed to be the boot LUN. It is an eight-byte number which should be specified as a hexadecimal number consisting of 16 digits, with an appropriate number of 0’s padded to the left, if required.
PAGE 1141
4. Troubleshooting Troubleshooting the iSCSI Driver Header Digest: Enabled Data digest: Not specified. Assume disabled. Authentication Type: 1-way CHAP. The following is an example of Default TCP Port and Mutual CHAP Settings: iscsi:”192.168.0.2”::”000000000000000E”:”iqn.2009-4.com:1234567890” ::”E”:”D”:”M” where the following is: Target IP address: 192.168.0.2 Target TCP port: Use default from RFC 3720 (3260) Target boot LUN: 0x0E Target iqn name: iqn.2009-04.com:1234567890 Initiator name: Not specified.
PAGE 1142
4. Troubleshooting ESXi 5.5 Native Mode NIC Driver Troubleshooting Support ESXi 5.5 Native Mode NIC Driver Troubleshooting Support Table 4-10 lists the troubleshooting support provided by the earlier vmklinux driver in terms of the proc interface and the equivalent support provided by the native mode NIC driver through either the esxcli plug-in or the VmkMgmtKeyVal interface. Table 4-10 ESXi 5.
PAGE 1143
4. Troubleshooting ESXi 5.5 Native Mode NIC Driver Troubleshooting Support Table 4-10 ESXi 5.5 Native Mode NIC Driver Troubleshooting Support (Continued) Troubleshooting Items from Earlier vmklinux Driver using the proc Interface Description pci_read ESXi 5.5 Native Mode Driver Support (VmkMgmtKeyVal interface) Read the 32-bit register value from the PCI space at the offset set through the “pci_read” file ESXi 5.5 Native Mode Driver Support (esxcli plug-in)  Usage in ESXi 5.
PAGE 1144
4. Troubleshooting ESXi 5.5 Native Mode NIC Driver Support for ethtool Commands ESXi 5.5 Native Mode NIC Driver Support for ethtool Commands Table 4-11 lists the ethtool support provided by the earlier vmklinux driver and the equivalent support provided through the esxcli and vsish commands. Table 4-11 ESXi 5.5 Native Mode NIC Driver Support for ethtool Commands ethtool Command Description ethtool -a|--show-pause DEVNAME Show pause options ethtool -A|--pause DEVNAME Set pause options ESXi 5.
PAGE 1145
4. Troubleshooting ESXi 5.5 Native Mode NIC Driver Support for ethtool Commands Table 4-11 ESXi 5.5 Native Mode NIC Driver Support for ethtool Commands (Continued) ethtool Command Description ethtool -K|--offload DEVNAME Set protocol offload ESXi 5.0 vmklinux Driver Support (VmkMgmtKeyVal interface) Not implemented ESXi 5.
PAGE 1146
Appendix A. Configuring iSCSI Through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations Appendix A. Configuring iSCSI Through DHCP Dynamic Host Configuration Protocol (DHCP) Recommendations If you are using a DHCP server to obtain an IP address for your iSCSI initiator, Emulex recommends that you set up a reservation. A reservation assigns a specific IP address based on the MAC address of your iSCSI function.
PAGE 1147
CIM Provider Package Version 10.2 Installation Guide P010091-01A Rev.
PAGE 1148
114 Copyright © 2011-2014 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.
PAGE 1149
1. Introduction Supported Platforms 1. Introduction The Emulex® CIM Provider enables comprehensive management of Emulex host bus adapters (HBAs), converged fabric adapters (CFAs), and universal converged network adapters (UCNAs). It uses an industry standard Application Programming Interface (API) Common Manageability Programming Interface (CMPI v2.0) to manage various Emulex adapters.
PAGE 1150
1. Introduction Supported CIM Provider Profiles     PCI Device – DMTF DSP1075 Physical Assets Profile – DMTF DSP1011 Storage HBA – SNIA SMI-S 1.5 Part 6 Clause 6 Indication Profile (partial) – DMTF DSP1054 Emulex UCNAs Only       Ethernet Port – DMTF DSP1014 Host LAN Network Port – DMTF DSP1035 IP Interface – DMTF DSP1036 Diagnostics (CDMv2) – DMTF DSP1002 iSCSI Initiator – SNIA SMI-S 1.5 Part 6 Clause 9 iSCSI Initiator Ports Profile – SNIA SMI-S 1.
PAGE 1151
2. Installing the Emulex CIM Provider Prerequisites 2.
PAGE 1152
3. Using the Adapter Updating the Firmware on an Emulex Adapter 3. Using the Adapter This section describes updating firmware, enabling logs, using diagnostics, and discovering vNICs. If you require additional information, contact an authorized Emulex technical support representative at tech.support@emulex.com, 800-854-7112 (US/Canada toll free), +1714-885-3402 (US/International), or +44 1189-772929 (Europe, Middle East, and Africa).
PAGE 1153
3. Using the Adapter Enabling Logs and Collecting Symptoms wbemcli -nl -noverify cm 'https://root:@/root/emulex:' InstallFromURI.URI="",Target= Enabling Logs and Collecting Symptoms The Record Log profile is supported on both the Emulex UCNA CIM Provider and the Emulex FC HBA CIM Provider. To enable provider logs: 1.
PAGE 1154
3. Using the Adapter Executing a Diagnostic Test 4. Start the CIMOM and enumerate the Emulex classes in the “root/emulex” namespace. 5. Perform the operation which is not working as expected. The provider logs are available in specified in step 2. 6. Contact an Emulex technical support representative with the provider logs and the system logs (/var/log/syslog.log).
PAGE 1155
3. Using the Adapter Discovering vNICs Using the Emulex CIM Provider Executing a Diagnostic Test with an Emulex FC Adapter To execute a diagnostic test with an FC adapter: 1. Get the instance of the managed element (ELXHBA_PortController). For example: wbemcli -noverify ein ‘https://root:@/root/emulex:elxhba_portcontroller’ -nl 2. Get the instance of the ELXHBA_FCHBADiagnostictest class.
PAGE 1156
3. Using the Adapter Discovering vNICs Using the Emulex CIM Provider To Determine vNICs Hosted by the UCNA or CFA in FCoE+NIC Mode in a Particular Host 1. Find the CIM_Card instance for the UCNA or CFA in FCoE+NIC mode. 2. Find the vNICs in the host as detailed earlier, based on the version of the CIM Provider. 3. For each CIM_EthernetPort representing a vNIC: a. Find the instance of CIM_ControlledBy associating the CIM_EthernetPort to an instance of CIM_PortController.
PAGE 1157
4. Troubleshooting 4. Troubleshooting The following error message may appear if the CIM hosts are not properly added to the OCM application: “Unknown or invalid host specified” There could be instances when even with all the drivers, CIM Provider, and the CIM Client on a Windows machine properly installed, the CIM hosts might still not be added to the OCM application. Listed below are the most common reasons for this.
PAGE 1158
™ OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1159
115 Copyright © 2011-2014 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.
PAGE 1160
1. Introduction 1. Introduction Emulex® OneCommand Manager™ for VMware vCenter integrates the in-depth management of Emulex host bus adapters (HBAs), universal converged network adapters (UCNAs), and converged fabric adapters (CFAs) into the VMware vCenter management console.
PAGE 1161
1. Introduction Channel over Ethernet (FCoE) + network interface card (NIC) mode, it functions as a UCNA. OneCommand Manager for VMware vCenter supports Emulex OCe14101 and OCe14102 UCNAs. The features available in OneCommand Manager for VMware vCenter are determined by the version of Emulex CIM provider installed. The following table lists the Emulex OneCommand Manager application support provided by each Emulex CIM provider package and the individual FC and UCNA providers in each package.
PAGE 1162
1. Introduction Table 1-1 Support Provided by Emulex CIM Provider Versions (Continued) Emulex OneCommand Manager Application Features ELX CIM Provider Package v10.0 ELX CIM Provider Package v10.2 OneCommand OneCommand Manager for Manager for VMware VMware vCenter vCenter v10.0 v 10.
PAGE 1163
1. Introduction Table 1-1 Support Provided by Emulex CIM Provider Versions (Continued) Emulex OneCommand Manager Application Features ELX CIM Provider Package v10.0 ELX CIM Provider Package v10.2 OneCommand OneCommand Manager for Manager for VMware VMware vCenter vCenter v10.0 v 10.
PAGE 1164
1.
PAGE 1165
1.
PAGE 1166
1. Introduction Abbreviations RHEL Red Hat Enterprise Linux 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 SIMode IBM term for UMC (switch independent mode). Previously known as vNIC2.
PAGE 1167
1. Introduction Abbreviations VM virtual machine Xmt transmitted XRI exchange resource indicator XML extensible markup language OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1168
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Best Installation Practices 2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Best Installation Practices 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.
PAGE 1169
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Installing OneCommand Manager for VMware vCenter Installing OneCommand Manager for VMware vCenter Note: 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.
PAGE 1170
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Installing OneCommand Manager for VMware vCenter 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. If the port numbers are already in use, a warning appears next to the port number.
PAGE 1171
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Installing OneCommand Manager for VMware vCenter 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.
PAGE 1172
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Installing OneCommand Manager for VMware vCenter 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 vSphere Console 3.
PAGE 1173
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Enabling and Disabling OneCommand Manager for VMware vCenter Enabling and Disabling OneCommand Manager for VMware vCenter If you disable OneCommand Manager for VMware vCenter, the Emulex OneCommand tab immediately disappears from the vSphere console. If you enable OneCommand Manager for VMware vCenter, the Emulex OneCommand tab immediately appears on the vSphere console.
PAGE 1174
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Registering and Unregistering OneCommand Manager for VMware vCenter Figure 2-8 Register/Unregister Dialog Box 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.
PAGE 1175
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Uninstalling OneCommand Manager for VMware vCenter Uninstalling OneCommand Manager for VMware vCenter 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.
PAGE 1176
2. Installing and Uninstalling OneCommand Manager for VMware vCenter Components Reinstalling OneCommand Manager for VMware vCenter 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.
PAGE 1177
3. Using OneCommand Manager for VMware vCenter Behavior of OneCommand Manager for VMware vCenter Settings in the ESXi Server 3. Using OneCommand Manager for VMware vCenter Behavior of OneCommand Manager for VMware vCenter Settings in the ESXi Server Active Directory 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.
PAGE 1178
3. Using OneCommand Manager for VMware vCenter vSphere Console Views Accessing the vSphere Console To 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. 2. Select a cluster or host in the vSphere console tree-view and click the Emulex OneCommand tab to perform active management on a cluster or a host. 3. A Security Alert is displayed, click Yes. The vSphere console is displayed.
PAGE 1179
3. Using OneCommand Manager for VMware vCenter vSphere Console Views Note: The User Preferences window logs only up and down events for the port. Other events, such as temperature, are not posted. 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.
PAGE 1180
3. Using OneCommand Manager for VMware vCenter Accessing OneCommand Manager for VMware vCenter from the VMware Web Client Figure 3-2 Host View Accessing OneCommand Manager for VMware vCenter from the VMware Web Client You can run OneCommand Manager for VMware vCenter from within the vSphere Web Client. Note: The web client for OneCommand Manager for VMware vCenter was registered as part of the installation.
PAGE 1181
3. Using OneCommand Manager for VMware vCenter Accessing OneCommand Manager for VMware vCenter from the VMware Web Client Enabling OneCommand Manager for VMware for vCenter Server Appliance (vCSA) vCSA 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.
PAGE 1182
3. Using OneCommand Manager for VMware vCenter Accessing OneCommand Manager for VMware vCenter from the VMware Web Client . Figure 3-3 vSphere Web Client Plug-In Management Page 2. In the Plug-In Management page, select Emulex OneCommand Web and right-click under the State 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.
PAGE 1183
3. Using OneCommand Manager for VMware vCenter Accessing OneCommand Manager for VMware vCenter from the VMware Web Client 4. Go to the Classic solutions tab to access the OneCommand Manager for VMware vCenter. 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.
PAGE 1184
4. Managing Clusters Viewing Information in a Cluster 4. Managing Clusters 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 18.
PAGE 1185
4. Managing Clusters Viewing Information in a Cluster Hosts Information Field Definitions         IP Address – The IP address of the host in the cluster. Operating System – The operating system 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.
PAGE 1186
4. Managing Clusters Viewing Information in a Cluster Adapters Information 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 UCNAs this field shows the board type and revision code. Description – The type of adapter. To navigate the Adapter Information page: 1. Use the Filter list to filter the adapter information.
PAGE 1187
4. Managing Clusters Viewing Information in a Cluster Figure 4-4 Close-Up of Host-Centric Cluster View Host centric Information 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. Driver Version – The version of the installed driver.
PAGE 1188
4. Managing Clusters Viewing Information in a Cluster Figure 4-5 Virtual Port Cluster View Virtual Port Information 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. Filtering Host Information To filter the host information: 1.
PAGE 1189
4. Managing Clusters Viewing Information in a Cluster Figure 4-6 Fabric-Centric Cluster View Note: iSCSI and NIC ports are not attached to any fabric, so they are listed under “No Fabric Attachment” Figure 4-7 Close-up of Fabric-Centric Cluster View OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1190
4. Managing Clusters Viewing Information in a Cluster 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 firmware version.
PAGE 1191
5. Managing Hosts Viewing Information and Driver Parameters in a Host 5. Managing Hosts Viewing Information and Driver Parameters in a Host Viewing Information for a Single Host To view host information: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. The Host Information tab is selected by default and the information of the selected host appears.
PAGE 1192
5. Managing Hosts Viewing Information and Driver Parameters in a 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.
PAGE 1193
5. Managing Hosts Viewing Information and Driver Parameters in a Host Figure 5-2 Host Driver Parameters Pane 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.
PAGE 1194
5. Managing Hosts Setting Driver Parameters for All Adapters in a Host Viewing Firmware Information for All Adapters in a Host For updating firmware, see “Updating Firmware on 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: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. 2. Select the Maintenance tab.
PAGE 1195
5. Managing Hosts Setting Driver Parameters for All Adapters in a Host 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.
PAGE 1196
6. Managing Adapters and Ports FC and FCoE Ports 6. Managing Adapters and Ports The adapter information that is displayed depends upon the type of adapter you select; LightPulse (FC) or OneConnect. FC and FCoE Ports Viewing FC Adapter Information When 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: 1.
PAGE 1197
6. Managing Adapters and Ports FC and FCoE Ports  causes of system cooling issues include clogged air filters, inoperable fans and air conditioning problems that cause high ambient air temperatures. 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 problem and fix it before resuming operation. Check for system cooling issues.
PAGE 1198
6. Managing Adapters and Ports FC and FCoE Ports 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. 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”.
PAGE 1199
6. Managing Adapters and Ports FC and FCoE Ports Port Speed Area The Port Speed field indicates the current port speed of the selected adapter port. Viewing FCoE Port Details Use the Port Details tab to view general attributes associated with the selected FCoE port. To view port details for an FCoE port: 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 FCoE port whose details you want to view. 3.
PAGE 1200
6. Managing Adapters and Ports FC and FCoE Ports            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. Firmware Version – The version of Emulex firmware currently active on the adapter port.
PAGE 1201
6. Managing Adapters and Ports FC and FCoE Ports Figure 6-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.
PAGE 1202
6. Managing Adapters and Ports FC and FCoE Ports Viewing FC/FCoE Port Statistics When you select an FC/FCoE port from the discovery-tree, the Port Statistics tab provides cumulative totals for various error events and statistics on the port. Some statistics are cleared when the adapter is reset. To view statistics for a port: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. 2.
PAGE 1203
6. Managing Adapters and Ports FC and FCoE Ports Providing notification of configuration changes and loop failures.  Placing loop ports in the monitoring state. 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.
PAGE 1204
6. Managing Adapters and Ports FC and FCoE Ports To view transceiver information for an FC port: 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 port whose transceiver information you want to view. 3. Select the Transceiver Data tab. Figure 6-6 FC Port Transceiver Tab Transceiver Information Field Definitions Module Attributes Area           Vendor – The name of the vendor.
PAGE 1205
6. Managing Adapters and Ports FC and FCoE Ports     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.
PAGE 1206
6. Managing Adapters and Ports FC and FCoE Ports Viewing Maintenance Information and Firmware Versions for an FC/FCoE Port The Maintenance tab shows firmware information for an FC/FCoE port. To view firmware information for a port: 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 port whose firmware information you want to view. 3. Select the Maintenance tab. Figure 6-8 FC Port Maintenance tab .
PAGE 1207
6. Managing Adapters and Ports FC and FCoE Ports Maintenance Tab Field Definitions FC Port Firmware Area        Current Version – The Emulex firmware version number for this model of 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.
PAGE 1208
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs  Reset – Click to reset the adapter port. Refer to “Viewing FC/FCoE Port Driver Parameters” on page 57 for more information. Maintenance Tab Buttons (FC only)  Update Firmware – Click to update firmware on the selected port.
PAGE 1209
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs   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.
PAGE 1210
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Figure 6-11 Enable ExpressLane LUN Pull Down Menu The LUN icon changes to . Note: The ExpressLane state of a LUN is enabled at the driver (active) level and the configured level (persists across reboots). Figure 6-12 FC/FCoE LUN with ExpressLane Enabled OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1211
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Disabling ExpressLane LUNs You can disable a specific ExpressLane LUN or disable all ExpressLane LUNS for a port. To disable a specific ExpressLane LUN: 1. 2. 3. 4. In the Emulex Device Management tree-view, expand the FC/FCoE adapter port. Expand the FC/FCoE target. Right-click the LUN for which you want to disable ExpressLane. Select Disable ExpressLane LUN from the pull down menu. To disable all ExpressLane LUNs for a port: 1. 2. 3. 4.
PAGE 1212
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Viewing Flash Contents for an FC Port To view the flash contents for an FC port: 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 port whose Flash contents you want to view. 3. Select the Flash Contents tab. The Flash Contents information pane appears. Figure 6-14 FC Port Flash Contents 4.
PAGE 1213
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Figure 6-15 FCoE Port PCI Registers Tab Configuring FCoE Initialization Protocol (FIP) The FIP tab allows you to view configure FIP for an FCoE adapter port. To configure FIP: 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 FCoE adapter port whose FIP properties you want to configure. 3. Select the FIP tab. 4.
PAGE 1214
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs . Figure 6-16 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: In Figure 6-16, 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) was the current DCBX mode, “Active” would be in the “CIN (Non-FIP) Settings” area.
PAGE 1215
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Configuring DCB Parameters for FCoE Adapter Ports To view the DCB parameters for FCoE adapter ports: 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 FCoE adapter port whose FIP properties you want to configure. 3. Select the DCB tab.
PAGE 1216
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs  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. Error – The FCoE error state.
PAGE 1217
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Figure 6-18 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 Port The Maintenance tab enables you to change the WWPN and the WWNN of a selected adapter port.
PAGE 1218
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs 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.
PAGE 1219
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Figure 6-19 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.
PAGE 1220
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs 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.
PAGE 1221
6. Managing Adapters and Ports Viewing and Managing FC/FCoE LUNs Enabling and Disabling FC Ports Using 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 a black 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: 1.
PAGE 1222
6. Managing Adapters and Ports iSCSI 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. 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: = 5. Click Apply to apply your configuration changes.
PAGE 1223
6. Managing Adapters and Ports iSCSI Port 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-22 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.
PAGE 1224
6. Managing Adapters and Ports iSCSI Port  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. 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.
PAGE 1225
6. Managing Adapters and Ports iSCSI Port Figure 6-23 iSCSI Port, PCI Registers Tab Viewing iSCSI iSNS Server Information If the server has been set up as an Internet Storage Name Server (iSNS), the iSNS tab shows the IP address and TCP Port for the selected iSCSI port. To view iSNS server 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 iSCSI port for which you want to view iSNS information. 3.
PAGE 1226
6. Managing Adapters and Ports iSCSI Port iSNS Tab Field Definitions iSNS Server   IP Address - The IP address of the iSNS server. TCP Port - The TCP port number for the connection to the iSNS server. Disabling the iSNS Server To disable the iSNS server, click Clear iSNS on the iSNS tab. Changing the iSNS Server To change the iSNS server: 1. On the iSNS tab, click Add/Update iSNS. The Update iSNS Server dialog box is displayed. Figure 6-25 iSCSI Port, Update iSNS Server Dialog Box 2.
PAGE 1227
6. Managing Adapters and Ports iSCSI Port Figure 6-26 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.
PAGE 1228
6. Managing Adapters and Ports iSCSI Port              Last Failure Type – A description of the last failure. 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.
PAGE 1229
6. Managing Adapters and Ports iSCSI Port Figure 6-27 iSCSI Initiator Logon Options Tab To view iSCSI initiator default login options: 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 iSCSI initiator for which you want to view Initiator Login information. 3. Click the iSCSI Initiator LoginOptions tab. 4. Click View Default Login. The Initiator Default Login Options window appears.
PAGE 1230
6. Managing Adapters and Ports iSCSI Port 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. Initiator Login Options Area    Immediate Data – If set to Yes, the initiator can append unsolicited data to an iSCSI command.
PAGE 1231
6. Managing Adapters and Ports iSCSI Port 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.
PAGE 1232
6. Managing Adapters and Ports iSCSI Port Viewing iSCSI Target Discovery Information The 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: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. 2.
PAGE 1233
6. Managing Adapters and Ports iSCSI Port Viewing iSCSI Target Information The iSCSI Target Information tab shows information about the target. You can also view information about a target session. To view iSCSI target discovery 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 iSCSI target for which you want to view target discovery information. The iSCSI Target Information tab is displayed.
PAGE 1234
6. Managing Adapters and Ports iSCSI Port Figure 6-31 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 – “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, unknown).
PAGE 1235
6. Managing Adapters and Ports iSCSI Port          MaxConnections – The maximum number of connections to targets that are allowed within a single session. 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.
PAGE 1236
6. Managing Adapters and Ports iSCSI Port    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.
PAGE 1237
6. Managing Adapters and Ports iSCSI Port Figure 6-32 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. Serial Number – The vendor’s serial number for the LUN. LUN Capacity Area   Capacity – The capacity of the LUN, in megabytes. Block Size – The length of a logical unit block in bytes.
PAGE 1238
6. Managing Adapters and Ports iSCSI Port Figure 6-33 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. 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).
PAGE 1239
6. Managing Adapters and Ports iSCSI Port Figure 6-34 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.
PAGE 1240
6. Managing Adapters and Ports iSCSI Port   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.
PAGE 1241
6. Managing Adapters and Ports iSCSI Port Figure 6-35 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. Configure DCB Dialog Box Field Definitions DCBX Settings Area    Enabled – DCBX can be enabled or disabled.
PAGE 1242
6. Managing Adapters and Ports iSCSI Port      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. Receive Enabled – LLDP Receive can be enabled or disabled.
PAGE 1243
6. Managing Adapters and Ports iSCSI Port  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.
PAGE 1244
6. Managing Adapters and Ports NIC Port NIC Port Viewing NIC Port Information When 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.
PAGE 1245
6. Managing Adapters and Ports NIC Port                       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).
PAGE 1246
6. Managing Adapters and Ports NIC Port 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 (iBFT) format. PXE – to boot from a network interface using a preboot execution environment (PXE). None – to disable the network boot functions. Enabling SR-IOV To enable SR-IOV, check Enable SR–IOV. To disable SR-IOV, clear the Enable SR-OV checkbox.
PAGE 1247
6. Managing Adapters and Ports NIC Port  VEPA is only available for NIC ports. Figure 6-37 NIC Port Information Tab, VEPA Enabled Viewing PCI Registers for a NIC Port The PCI Registers tab contains PCI information about the selected NIC function. To view a NIC port’s PCI registers: 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 NIC port for which you want to view PCI information.
PAGE 1248
6. Managing Adapters and Ports NIC Port 3. Select the PCI Registers tab. Figure 6-38 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: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. 2.
PAGE 1249
6. Managing Adapters and Ports NIC Port 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 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).
PAGE 1250
6. Managing Adapters and Ports NIC Port Displaying Virtual Functions on a Host Operating System OneCommand Manager for VMware vCenter can discover the VFs running on the discovered physical functions and display them in the discovery-tree as shown in Figure 7-41. Figure 6-40 Virtual Functions Discovered on the Physical Function on the Host Operating System Select the VF under the host operating system in the discovery-tree to display the Port Information tab.
PAGE 1251
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters OCe10100–Series and OCe11100–Series Adapters Viewing OCe10100–Series and OCe11100–Series Adapter Information The Adapter Information tab contains general attributes associated for the selected UCNA. You can also use this tab to view and enable licenses. See “Viewing FC Port Details and Changing Link State” on page 54 for more information. To view information for a UCNA: 1.
PAGE 1252
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters          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 hardware 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 speed of the PCI bus in which the adapter running.
PAGE 1253
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters   Current Management Type – Displays 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.
PAGE 1254
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Figure 6-43 OneConnect OCe11102 Adapter Information Tab Viewing Licenses To view available licenses for an OCe10100-series or an OCe11100-series adapter: 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 an adapter whose licenses you want to view. 3. Select the Adapter Information tab.
PAGE 1255
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Figure 6-44 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.
PAGE 1256
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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. Managing Port Channels Using Channel Management Note: Channel management is not available for the LPe16202 CFA and OCe10100-series adapters.
PAGE 1257
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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. Configuring Channel Management for OCe11100–Series Adapters When you select an OCe11102 adapter port with channel management enabled, the Channel Mgmt tab is available.
PAGE 1258
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters      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.
PAGE 1259
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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 problem and that the changes were not saved.
PAGE 1260
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters  Max. BW – Maximum bandwidth at which the port is guaranteed to run. Viewing the Channel Management Tab for UFP 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 6-47. Note: UFP is supported only on IBM virtual fabric adapters.
PAGE 1261
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Viewing OCe10100–Series and OCe11100–Series Adapter Firmware Information Unlike LightPulse adapters, OCe10100-series and OCe11100-series adapter firmware is maintained on an adapter-specific basis instead of port-specific basis. To view firmware information for an adapter: 1. Select a host in the vSphere console tree-view and select the Emulex OneCommand tab. 2.
PAGE 1262
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Maintenance Tab Button The Update Firmware button updates firmware on the selected adapter. Refer to “Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters” on page 161 for more information.
PAGE 1263
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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 digital audio cable length in meters.
PAGE 1264
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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.
PAGE 1265
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Figure 6-51 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.
PAGE 1266
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Viewing Port Transceiver Information for OCe10100–Series and OCe11100–Series Adapters The 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: 1.
PAGE 1267
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters   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. RX Input Power – The measured RX input power.
PAGE 1268
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters 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.
PAGE 1269
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters   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.
PAGE 1270
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters Figure 6-54 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 Cisco-Intel-Nuova (CIN).
PAGE 1271
6. Managing Adapters and Ports OCe10100–Series and OCe11100–Series Adapters    Transmit System Description Enabled – Provides a description of the network entity in an alpha-numeric format. This includes system's name and versions of hardware, operating system and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418.
PAGE 1272
6. Managing Adapters and Ports OCe14100–Series Adapters 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.
PAGE 1273
6. Managing Adapters and Ports OCe14100–Series Adapters 2. In the Emulex Device Management tree-view, select an adapter. The Adapter Configuration tab is displayed. Configuring OCe14000–Series Adapters When 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.
PAGE 1274
6. Managing Adapters and Ports OCe14100–Series Adapters  The display in the lower area of the tab depends upon 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).
PAGE 1275
6. Managing Adapters and Ports OCe14100–Series Adapters adapter supports multiple NIC configurations (profiles), you must select a NIC-Only configuration from the NIC-Only configuration list. Note: If you choose the NIC-Only No ETS configuration, SR-IOV is automatically enabled on each NIC function and allows up to 63 virtual functions. If you choose the NIC-Only configuration, SR-IOV is not supported. 4. Click Apply. A message appears notifying you of the profiles activation requirements.
PAGE 1276
6. Managing Adapters and Ports OCe14100–Series Adapters Mixed Mode Configuration When mixed mode is available, up to two functions per port can be configured. The first function will be NIC. The second function can be a storage protocol or “None”. When you click on the second function's pull down menu, the available storage protocols for the function are displayed.
PAGE 1277
6. Managing Adapters and Ports OCe14100–Series Adapters Concurrent Mode When concurrent mode is available, up to three functions per port are configurable. Figure 6-59 Concurrent Storage Configuration View The pull down menu for selecting a storage protocol to run on the second and third functions is the same as the pull down menu for mixed mode storage. Concurrent Storage Configuration is subject to the following rules:    The first function must be NIC.
PAGE 1278
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-60 Concurrent Storage Configuration Choices for the Third Function UMC Configuration View When UMC is available and the UMC radio button is selected, the Adapter Configuration tab looks like the following: Figure 6-61 UMC View (four ports) OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1279
6. Managing Adapters and Ports OCe14100–Series Adapters UMC 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.
PAGE 1280
6. Managing Adapters and Ports OCe14100–Series Adapters   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.
PAGE 1281
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-63 MultiChannel vNIC View (Mixed Mode Storage) The Channel Configuration table shows the channel properties for vNIC. There are drop-downs 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.
PAGE 1282
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-64 MultiChannel SIMode View Other than the names, SIMode and UMC configuration is exactly the same. See “UMC Configuration View” on page 135. Multichannel UFP Configuration When UFP is selected, the Adapter Configuration tab looks like the following: Figure 6-65 MultiChannel UFP View (concurrent mode storage) The Channel Configuration table shows the channel properties for multichannel UFP.
PAGE 1283
6. Managing Adapters and Ports OCe14100–Series Adapters   The second and third channels can be assigned the following:  NIC  None (channel 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.
PAGE 1284
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-66 Dell Two Port NPar Configuration, NParEP Mode Disabled If the NParEP Mode check box is cleared (disabled), 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.
PAGE 1285
6. Managing Adapters and Ports OCe14100–Series Adapters Four Port Adapters Dell four port adapters allow up to two or four partitions per port, depending upon whether the NParEP Mode check box is checked or cleared.
PAGE 1286
6. Managing Adapters and Ports OCe14100–Series Adapters NParEP Mode Enabled Figure 6-69 Dell Four Port NPar Configuration, NParEP Mode Enabled If the NParEP Mode check box is selected (enabled), up to four partitions per port can be configured. 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.
PAGE 1287
6. Managing Adapters and Ports OCe14100–Series Adapters You can switch between showing eight functions and showing sixteen functions for a given adapter, if NPar is 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.
PAGE 1288
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-71 OCe14100-Series Adapter, DCB Tab (FCoE/iSCSI Adapter Port Selected) 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.
PAGE 1289
6. Managing Adapters and Ports OCe14100–Series Adapters  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      State – Enabled indicates that there is flow control in both directions (receive and transmit). Sync’d – If Yes, the PFC priorities have been set by the peer. This parameter cannot be set.
PAGE 1290
6. Managing Adapters and Ports OCe14100–Series Adapters Figure 6-72 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. Operating Version – The operating version of the DCBX protocol.
PAGE 1291
6. Managing Adapters and Ports OCe14100–Series Adapters     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 hardware, operating system and networking software supported by the device.
PAGE 1292
6. Managing Adapters and Ports OCe14100–Series Adapters   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.
PAGE 1293
7. Updating Firmware Performing a Batch Firmware Update in Cluster View 7. Updating Firmware 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.
PAGE 1294
7. Updating Firmware Performing a Batch Firmware Update in Cluster View 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. Once compatible adapters are found, the following is displayed in the Batch Firmware Download dialog box:  The Firmware File field shows the selected image file name.
PAGE 1295
7. Updating Firmware Performing a Batch Firmware Update in Cluster View Figure 7-3 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).
PAGE 1296
7. Updating Firmware Performing a Batch Firmware Update in Cluster View Figure 7-4 Batch Firmware Update Jobs Window Batch Firmware Update 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. Port – The Port WWN for an FC adapter. This field is blank for a UCNA. Start Time – The time the job is submitted.
PAGE 1297
7. Updating Firmware Updating Firmware on Adapters in a Host Considerations for Firmware Updates      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 also be tracked in the VMware tasks window.
PAGE 1298
7. Updating Firmware Updating Firmware on Adapters in a Host Figure 7-5 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. Once compatible adapters are found, the Firmware File field of the Batch Firmware Download dialog box shows the selected image file name.
PAGE 1299
7. Updating Firmware Updating Firmware on Adapters in a Host 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.
PAGE 1300
7. Updating Firmware Updating Firmware on Adapters in a Host Jobs Window Field Definitions Active Jobs Area       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 UCNA. Start Time – The time that the job is submitted. Status Message – The status of the job.
PAGE 1301
7. Updating Firmware Updating Firmware on Adapters in a Host Updating Firmware for an Adapter To update firmware for an FC port: 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 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 appears. Figure 7-8 Firmware Download dialog box 4.
PAGE 1302
7. Updating Firmware Updating Firmware on Adapters in a Host  The firmware update progresses in the background until all the jobs are completed. During this period you can still browse through the other tabs. OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1303
7. Updating Firmware Updating Firmware on Adapters in a Host Jobs Window for an FC Port The Jobs window provides information and active and completed jobs. Figure 7-9 Jobs Window Jobs Window Field Definitions Active Jobs Column Definitions        User – The user who triggered the firmware update. Host – The IP address of the ESXi host to which the adapter or port belongs. Adapter – The model of the adapter selected for the firmware update request.
PAGE 1304
7. Updating Firmware Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters   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.
PAGE 1305
7. Updating Firmware Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters 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.
PAGE 1306
8. Exporting SAN Information in Cluster View Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters 8. Exporting SAN Information in Cluster View Exporting 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: 1.
PAGE 1307
8. Exporting SAN Information in Cluster View Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters 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. OneCommand Manager for VMware vCenter Version 10.
PAGE 1308
8. Exporting SAN Information in Cluster View Updating Firmware for OCe10100–Series, OCe11100–Series, and OCe14100–Series Adapters Completed Jobs Column Definitions      User – The user who triggered the firmware update. Start Time – The time the job is submitted. 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.
PAGE 1309
9. Diagnostics LightPulse FC HBA Diagnostic Tests 9. Diagnostics LightPulse FC HBA Diagnostic Tests When running port diagnostic tests using OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host. Running Loopback Tests There 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.
PAGE 1310
9. Diagnostics LightPulse FC HBA Diagnostic Tests 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 appears: Figure 9-2 Diagnostic Tests Warning 4. Click Yes. A progress bar shows that the test is running. 5.
PAGE 1311
9. Diagnostics LightPulse FC HBA Diagnostic Tests    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.
PAGE 1312
9. Diagnostics LightPulse FC HBA Diagnostic Tests 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 is displayed. If all tests do not pass, the Failed result in shown in the Test Phase Results. See Figure 9-6 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.
PAGE 1313
9. Diagnostics LightPulse FC HBA Diagnostic Tests Figure 9-5 D_Port Tests Dialog Box - Passed Results Figure 9-6 D_Port Tests Dialog Box - Failed Results OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1314
9. Diagnostics LightPulse FC HBA Diagnostic Tests 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 and in the Standard Tests area, click Start Test. A progress window appears, showing the progress of the POST test. 3.
PAGE 1315
9. Diagnostics LightPulse FC HBA Diagnostic Tests Setting Up a Test Pattern Enter a custom test pattern to be used in tests that transfer data. The test pattern can be up to eight hexadecimal bytes. Test Status The Test Status area shows how many completed cycles of each test ran, as well as the number of errors. Saving the Log File You 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.
PAGE 1316
9. Diagnostics LightPulse FC HBA Diagnostic Tests 2. Browse to the desired directory, change the log file name if you want and click Save to File. Creating FC Port Diagnostic Dumps Diagnostic 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: 1.
PAGE 1317
9. Diagnostics LightPulse FC HBA Diagnostic Tests 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.
PAGE 1318
9. Diagnostics LightPulse FC HBA Diagnostic Tests 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). 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.
PAGE 1319
9. Diagnostics OneConnect Diagnostic Tests OneConnect Diagnostic Tests Running Loopback Tests Note: When running port diagnostic tests using OneCommand Manager for VMware vCenter, do not perform any active management operations on the ESXi host. Run 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.
PAGE 1320
9. Diagnostics OneConnect Diagnostic Tests 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 (Figure 9-14). Using Beaconing Beaconing can force an adapter’s LEDs to blink in a particular sequence.
PAGE 1321
9. Diagnostics OneConnect Diagnostic Tests Setting Up Diagnostic Test Options Setting Up a Test Failure Error Action There 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 Cycles Specify one of the following test cycles:    Select an established cycle count by clicking on the corresponding radio button.
PAGE 1322
9. Diagnostics OneConnect Diagnostic Tests Figure 9-14 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.
PAGE 1323
9. Diagnostics OneConnect Diagnostic Tests Figure 9-15 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.
PAGE 1324
9. Diagnostics OneConnect Diagnostic Tests Viewing Diagnostic Dumps Files Diagnostic 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, click Show Dump Files.
PAGE 1325
10. Troubleshooting Security 10. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains some of these circumstances and offers one or more solutions for each issue. Security The 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.
PAGE 1326
10. Troubleshooting Security 2. Confirm or accept the certificate warning. 3. Refresh the vSphere web client tab or window. Figure 10-2 Blocked Content in the Firefox or Chrome Browser Installing a Security Certificate A 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.
PAGE 1327
10. Troubleshooting Security Figure 10-4 Certificate Dialog Box 5. Click Install Certificate.... The Certificate Import Wizard opens. Figure 10-5 Certificate Import Wizard 6. Follow the wizard instructions and install the certificate to the Trusted Root Certification Authorities location. OneCommand Manager for VMware vCenter Version 10.2 User Manual P010089-01A Rev.
PAGE 1328
10. Troubleshooting Security Table 10-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.
PAGE 1329
10. Troubleshooting Security Table 10-1 Troubleshooting Issues and Resolutions (Continued) Issue Resolution On a Windows 7 x64 operating system, 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.
PAGE 1330
11. Using OneCommand Manager for VMware vCenter Command Line Interface 11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Line Interface (CLI) client component of OneCommand Manager for VMware vCenter is installed as part of OneCommand Manager for VMware vCenter installation. OneCommand Manager for VMware vCenter CLI can manage Emulex adapters in systems with VMware ESXi 5.0, 5.1, and 5.5 environments. In order to run any of the CLI commands you must run the elxvcpcmd.
PAGE 1331
11. Using OneCommand Manager for VMware vCenter Command Line Interface Using the CLI Client Using the CLI Client Syntax Rules The syntax rules for CLI commands are as follows:       All commands must start with elxvcpcmd.exe. The requested operation must contain at least three characters, or as many as needed to distinguish it from any other operation. Whenever a WWPN is specified, individual fields are separated by colons (:) When a MAC address is specified, the fields are separated by a dash (-).
PAGE 1332
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Table 11-1 Group and Supported Commands Group Definition General General commands that can be run “setvccred” on the OneCommand Manager “version” application for VMware servers. AdapterLicense A set of commands used to read and manage personality licenses for an Emulex adapter.
PAGE 1333
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Table 11-1 Group and Supported Commands (Continued) Group Definition Supported Commands Diagnostic A set of commands used to run different diagnostic tests for an Emulex adapter or port. “D_Port” (Also known as ClearLink.
PAGE 1334
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Table 11-1 Group and Supported Commands (Continued) Group Definition Supported Commands SR-IOV A set of commands that allows “listvfuncs” multiple VFs to be created on a NIC “sriovenable” PF for an adapter port. Note: SR-IOV is not supported with UMC channel management.
PAGE 1335
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description This command changes the valid personality of the adapter to which the specified port belongs. Note: This command is not supported for the OCe14000–series adapters. Use the "setadapterportconfig" command for these adapters. Parameters= 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.
PAGE 1336
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Parameters h The IP address of the ESXi host with Emulex adapters. WWPN The port’s WWPN. ReadType 0 = Volatile, 1 = Non-volatile. clearisnsserver Syntax elxvcpcmd.exe v= u= p= h= clearisnsserver Description This command clears the configured iSNS server and disables iSNS target discovery for a given port.
PAGE 1337
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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 WWPN of an FCoE function on the physical port. MAC MAC address of any NIC function on the physical adapter port. Example (all NIC) elxvcpcmd.exe v=10.20.30.40 u=username p=password h=10.11.12.
PAGE 1338
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Configured mode: UMC Available modes: UMC Func# ----0 1 2 3 Type ----NIC iSCSI NIC NIC MAC Address LPVID Min BW Max BW ----------------- ----- ------ -----00-00-c9-12-34-56 2 25 50 00-00-c9-12-34-57 n/a 30 100 00-00-c9-12-34-58 4 25 50 00-00-c9-12-34-59 5 20 50 elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.
PAGE 1339
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference cmmode Syntax elxvcpcmd.exe v= u= p= h= cmmode Description This command enables or disables channel management on an adapter. Note: A system reboot is required for the change to take effect. Parameters v The vCenter server IP address. u The user name for the vCenter server. p The user password for the vCenter server.
PAGE 1340
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference When in channel management mode, you can disable a channel’s logical link by setting the minimum bandwidth and the maximum bandwidth to 0. If a channel’s protocol is set to None, the minimum and maximum bandwidth must be 0. Setting the minimum bandwidth to a value greater than 0 enables the channel if it was previously disabled.
PAGE 1341
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference deletedumpfiles Syntax elxvcpcmd.exe v= u= p= h= deletedumpfiles Description This command deletes all diagnostic dump files for a given 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.
PAGE 1342
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description The D_Port diagnostic is also known as ClearLink. The D_Port diagnostic is run from the OneCommand Manager for VMware vCenter CLI by specifying the d_Port command. Parameters 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.
PAGE 1343
11.
PAGE 1344
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference dump Syntax elxvcpcmd.exe v= u= p= h= dump core [Options] Description This command performs a core dump on a local port (OCe11102 or OCe10102). The dump file is placed in the dump directory with the following filename format: __.
PAGE 1345
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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.
PAGE 1346
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference exportsaninfo 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. Syntax elxvcpcmd.
PAGE 1347
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Procedure 1. Run the firmwareupdate command. A list of adapter serial numbers (for UCNAs) 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.
PAGE 1348
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Note: For multichannel and NPar configurations, this command only shows the port protocol assignments. For the entire multichannel configuration use the cmgetparams command. 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 the FCoE port.
PAGE 1349
11.
PAGE 1350
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Note:(pN) labels are the port parameter names to use in the SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI). getbeacon Syntax elxvcpcmd.exe v= u= p= h= getbeacon 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.
PAGE 1351
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference getdriverparams Syntax elxvcpcmd.exe v= u= p= getdriverparams Description This command shows the driver parameters 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.
PAGE 1352
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description This command shows the dump file directory for the FCoE, NIC or iSCSI port in the host. Note: The dump directory applies to all adapters in the server. There is not a separate dump directory for each adapter. 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.
PAGE 1353
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. getfipparams Syntax elxvcpcmd.
PAGE 1354
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. getiscsiluns Syntax elxvcpcmd.
PAGE 1355
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference getlunlist Syntax elxvcpcmd.exe v= u= p= getlunlist Description This command shows the LUNs attached to the FC and FCoE target of the specified FC/FCoE port. Parameters v The vCenter server IP address. u The user name for the vCenter server. p The user password for the vCenter server.
PAGE 1356
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Option Valid options: 0: Get information from the driver 1: Get information from configuration Example elxvcpcmd.exe v=10.192.000.000 u=user p=password h=10.192.87.
PAGE 1357
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description This command shows the priorities and bandwidth percentages for all the priority groups for the port. Additionally, this command displays the number of priority groups supported by an adapter. 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.
PAGE 1358
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. getsessioninfo Syntax elxvcpcmd.
PAGE 1359
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. getwwncap Syntax elxvcpcmd.
PAGE 1360
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference hbaattributes Syntax elxvcpcmd.exe hbaattributes v= u= p= Description This command shows a list of all adapter attributes for the specified port on the adapter. This command is supported only at the host level. Parameters v The vCenter server IP address. u The user name for the vCenter server. p The user password for the vCenter server.
PAGE 1361
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference listvfuncs Syntax elxvcpcmd.exe v= u= p= h= listvfuncs Description This command shows a list of all the virtual functions discovered. 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.
PAGE 1362
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference listprofiles Syntax elxvcpcmd.exe v= u= p= ListProfiles 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 profiled IDs.
PAGE 1363
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference h= listsessions Description This command lists all the sessions on a specified target. The iSCSI target name instructs the command to gather the information from the listed iSCSI target name. 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.
PAGE 1364
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference h= listvports 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 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.
PAGE 1365
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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.
PAGE 1366
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. portattributes Supported by Windows Syntax elxvcpcmd.exe v= u= p= PortAttributes Description This command shows a list of all port attributes for the port specified on the adapter.
PAGE 1367
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference WWPN The WWPN of a port on the ESXi host with Emulex adapters. MAC The MAC address of the NIC or iSCSI port. readwwn Syntax elxvcpcmd.exe v= u= p= showpersonalities [ReadType] Description This command shows the WWN details of the specified port and category. Parameters v The vCenter server IP address. u The user name for the vCenter server.
PAGE 1368
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference  For FCoE ports, this command only resets the driver to update changed driver parameters that require a driver reset. It does not cause a hardware reset of the adapter 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.
PAGE 1369
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Syntax elxvcpcmd.exe v= u= p= h= saveconfig 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.
PAGE 1370
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. setadapterportconfig (OCe14000–Series Only) Syntax elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.203.
PAGE 1371
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference            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.
PAGE 1372
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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.
PAGE 1373
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference SetAdapterPortConfig command (e.g. p0=NIC,FCoE p1=NIC,iSCSI) Concurrent Mode with Two Ports elxvcpcmd.exe v=10.192.000.000 u=root p=vmware h=10.192.000.
PAGE 1374
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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 = Off 1 = On setcablenvp Note: This command supports only OCe11100 T 10GBASE-T–series adapters. Syntax elxvcpcmd.
PAGE 1375
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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. BW0 to BW7 The bandwidth for priority group 0 to 7.
PAGE 1376
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Default – Setting the SetDCBParam arguments to default sets all UCNA DCB parameters (including priority groups) to their default values. Example: elxvcpcmd setdcbparam defaults Link Layer Discovery Protocol (LLDP) Parameters and Values (1= enabled 0 = disabled) TxState (Transmit State) – DCBX uses Link Layer Discovery Protocol (LLDP) to exchange parameters between two link peers.
PAGE 1377
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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 priority group IDs (PGID) 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.
PAGE 1378
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference 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.
PAGE 1379
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference setdriverparamdefaults 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 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.
PAGE 1380
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Example: elxvcpcmd 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. setfipparams Syntax elxvcpcmd.
PAGE 1381
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Note: A masked LUN cannot be enabled for ExpressLane. Parameters wwpn The WWPN of the FC/FCoE function connected to the target. Targetwwpn The WWPN of the target.
PAGE 1382
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Note: The PFC Throttle state is returned by the PortAttributes command for UCNAs. However for UCNAs with older firmware that does not support PfcThrottle and for FC adapters, the PFC Throttle state is not returned by the PortAttributes command. Parameters v The vCenter server IP address. u The user name for the vCenter server. p The user password for the vCenter server.
PAGE 1383
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Example: The following example 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 setportenabled Syntax elxvcpcmd.
PAGE 1384
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Note: The retention count applies to all adapters in the server. 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.
PAGE 1385
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference showisnsserver Syntax elxvcpcmd.exe v= u= p= h= showisnsserver < MAC> Description This command shows the currently configured Internet Storage Name Server. This command also indicates whether or not iSNS discovery is enabled. Parameters v The vCenter server IP address. u The user name for the vCenter server. p The user password for the vCenter server.
PAGE 1386
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description This command shows the license ID of the adapter to which the specified port belongs. 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.
PAGE 1387
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference showtarget Syntax elxvcpcmd.exe v= u= p= showtarget Description This command shows the iSCSI target details of the adapter to which the specified iSCSI port belongs. 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.
PAGE 1388
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference targetmapping Syntax elxvcpcmd.exe v= u= p= targetmapping Description This command shows the targets attached to the FC and FCoE 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.
PAGE 1389
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference Description This 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. Parameters v The vCenter server IP address. u The user name for the vCenter server.
PAGE 1390
11. Using OneCommand Manager for VMware vCenter Command Line Interface The Command Reference updateisnsserver Syntax elxvcpcmd.exe v= u= p= h= updateisnsserver Description This command updates the configured iSNS server. This command requires the server IP and port number of the iSNS server be available to respond to the iSNS requests. Parameters v The vCenter server IP address.
PAGE 1391
11. Using OneCommand Manager for VMware vCenter Command Line Interface Viewing Audit Logs Using the CLI Command MAC The MAC address of the iSCSI port. Port (0/1) Port number of the iSNS server to configure (value: 1024-65535). version Syntax elxvcpcmd.exe version Description This command shows the version of the CLI installed. Parameters None. Viewing Audit Logs Using the CLI Command Note: All active management actions performed are saved to a log file specific to the action.
PAGE 1392
11. Using OneCommand Manager for VMware vCenter Command Line Interface Viewing Audit Logs Using the CLI Command setdcbparam Shows the changes to the DCB parameters on the UCNA. setbeacon Shows the beacon settings on the UCNA. setfipparam Shows the changes to the FIP parameters on the UCNA. download Shows the firmware download activities performed. reset Shows the port reset activities performed. changewwn Shows the WWN change activities performed.
PAGE 1393
12. Troubleshooting Security 12. Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains some of these circumstances and offers one or more solutions for each issue. Security The 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.
PAGE 1394
12. Troubleshooting Security 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. 3. Refresh the vSphere web client tab or window. Figure 12-2 Blocked Content in the Firefox or Chrome Browser Installing a Security Certificate A permanent solution to the security warnings is to install the correct security certificate. To install a security certificate: 1.
PAGE 1395
12. Troubleshooting Security 4. Click View certificates in the Certificate Error list. The Certificate dialog box opens. Figure 12-4 Certificate Dialog Box 5. Click Install Certificate.... The Certificate Import Wizard opens. Figure 12-5 Certificate Import Wizard OCM for VMware vCenter Version 10.2 User Manual P009805-01A Rev.
PAGE 1396
12. Troubleshooting Security 6. Follow the wizard instructions and install the certificate to the Trusted Root Certification Authorities location. Table 12-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”.
PAGE 1397
12. Troubleshooting Security Table 12-1 Troubleshooting Issues and Resolutions (Continued) Issue Resolution On a Windows 7 x64 operating system, 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.
PAGE 1398
Boot Version 10.2 for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1399
139 Copyright © 2003-2014 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.
PAGE 1400
1. Introduction Abbreviations 1. Introduction This manual describes installing, updating, enabling, and configuring Emulex® Fibre Channel (FC) boot code. This manual also describes the Emulex boot from SAN implementation and its operation with distinct hardware and operating system requirements. Boot from SAN is booting servers directly from disk operating system images located on a storage area network (SAN) by way of Emulex LightPulse® adapters using Emulex FC boot code.
PAGE 1401
1.
PAGE 1402
1.
PAGE 1403
1. Introduction Emulex Boot Code Files VLAN virtual local area network VM virtual machine VMQ virtual machine queue WDS Windows Deployment Services WWN world wide name WWNN world wide node name WWPN world wide port name x Used to designate a variable. For example, SPx includes SP1, SP2, etc.
PAGE 1404
2. Boot from SAN Emulex Boot Code Files 2. Boot from SAN This document provides instructions for installing and using all of the types of boot code provided by Emulex. Note: Not all procedures are required. Emulex host bus adapters (HBAs) usually ship from the factory with the latest version of boot code installed and enabled, so you do not need to install or enable boot code in those cases. However, if boot code is not installed, you must install it, and if it is not enabled, you must enable it.
PAGE 1405
2. Boot from SAN Windows Server 2008, 2008 R2, 2012 and 2012 R2 Windows Server 2008, 2008 R2, 2012 and 2012 R2 Configure Boot from SAN on Windows Server 2008, 2008 R2, 2012 and 2012 R2 (x64) 1. If necessary, update the boot code on the adapter (see “Update and Enable Boot Code” on page 1416). 2. If necessary, enable the boot code on the adapter (see “Update and Enable Boot Code” on page 1416). 3. Enable the adapter to boot from SAN (see “Enable an Adapter to Boot from SAN” on page 1418). 4.
PAGE 1406
2. Boot from SAN Windows Server 2008, 2008 R2, 2012 and 2012 R2 4. Boot the host server with the Windows Server 2008, 2008R2, 2012, or 2012 R2 DVD inserted. Follow the on-screen prompts to install the appropriate version of Windows Server. The Windows installation exposes all available and visible LUNs as disks and partitions numbered 0 to N, where N is the highest number available. These numbers typically are the LUN numbers assigned by the array. 5.
PAGE 1407
2. Boot from SAN Windows Server 2008, 2008 R2, 2012 and 2012 R2 The GUID Partition Table The GUID Partition Table (GPT) was introduced as part of the EFI initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that has been common to PCs. MBR supports 4 primary partitions per hard drive and a maximum partition size of 2 terabytes (TB).
PAGE 1408
2. Boot from SAN Linux and VMware 10. Select the same drive you configured as the boot device (see “Configure Boot Devices” on page 1419). Linux and VMware Configure Boot from SAN on Linux or VMware (x86 and x64) 1. If necessary, install or update the boot code on the adapter (see “Update and Enable Boot Code” on page 1416). 2. If necessary, enable the boot code on the adapter (see “Update and Enable Boot Code” on page 1416). 3.
PAGE 1409
2. Boot from SAN Solaris 3. At the Installation Settings screen, after configuring the desired partitions, select the Expert tab. 4. Select Booting to change the bootloader configuration. 5. The Boot Loader Settings window appears. Select the Boot Loader Installation tab. 6. In the section labeled Boot Loader Location, select Custom Boot Partition, then select root partition (or boot partition, if you configured one) from the drop-down box. 7. Click Boot Loader Options.
PAGE 1410
2. Boot from SAN Solaris Found Fibre Channel device(s): Node WWN:50060e8003823800 Device Type:Disk device Logical Path:/dev/rdsk/c5t226000C0FF9833AFd6s2 Node WWN:50060e8003823800 Device Type:Disk device Logical Path:/dev/rdsk/c5t226000C0FF9833AFd6s2 Node WWN:50060e8003823800 Device Type:Disk device 3. Copy the /dev/rdsk/nnn part of the path statement for a drive. 4.
PAGE 1411
2. Boot from SAN Solaris show-devs The ID information for each found adapter is displayed, such as: /pci@5d,700000/emlx@2 4. Enable boot from SAN on each Emulex adapter in the system by typing the following set of commands, replacing adapter_id with the ID information for each Emulex adapter in turn. There is a space between the first quotation mark and the first character of the adapter ID. " adapter_id" select-dev [for example, “/pci@5d,700000/emlx@2” select-dev] set-sd-boot unselect-dev 5.
PAGE 1412
2. Boot from SAN Solaris c. Modify the lpfc.conf file to use persistent binding. For more information, refer to the Emulex Drivers for Solaris User Manual available on the Emulex website. 5. Copy the DVD image in the drive to the install server's hard disk. # ./setup_install_server install_dir_path install_dir_path specifies the directory where the DVD image is to be copied. The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images.
PAGE 1413
2. Boot from SAN Solaris # shareall 7. Change directories to root (/). # cd / 8. Eject the Solaris DVD. 9. (Optional) Patch the files that are located in the miniroot on the net install image that was created by setup_install_server. Patching a file might be necessary if a boot image has problems. For more information, refer to the Sun Microsystems Solaris 10 10/08 Installation Guide. Install Solaris by Migrating an Image from a Local SCSI Disk 1.
PAGE 1414
2. Boot from SAN Solaris Example 3: did=6312200, lun=25 (hexadecimal) and target id=f (hexadecimal): did 6312200 25 f set-boot-id 5. Boot to the original local disk to set up the newly defined FC disk. Type boot local_disk where local_disk is the complete path or the alias of the original boot disk. Note: If the FC disk is not found when the system is rebooted, enter touch/ reconfigure and reboot. If the disk is still not discovered, edit the /kernel/drv/lpfc.
PAGE 1415
2. Boot from SAN Solaris /dev/dsk/c0t0d0s1 (swap) /dev/dsk/c0t0d0s0 and /dev/rdsk/c0t0d0s0 (root) /dev/dsk/c0t0d0s6 and /dev/rdsk/c0t0d0s6 (usr) /dev/dsk/c0t0d0s7 and /dev/rdsk/c0t0d0s7 (export) Edit the file to show: /dev/dsk/c1t1d1s1 (swap) /dev/dsk/clt1d0s0 and /dev/rdsk/c1t1d0s1 (root) /dev/dsk/clt1d0s6 and /dev/rdsk/c1t1d0s6 (usr) /dev/dsk/clt1d0s7 and /dev/rdsk/c1t1d0s7 (export) 17. Reboot the system: sync sync halt reset-all 18. Boot to disk: boot disk The system should boot to the FC disk. 19.
PAGE 1416
3. Update and Enable Boot Code 3. Update and Enable Boot Code Use Emulex utilities to install boot code, update boot code to a newer version, and enable boot code. The utility that you will use depends on the operating system and, in some cases the driver type or system architecture. Table 3-1 indicates the utilities you can use to install and update boot code, and Table 3-2, Utilities that Enable Boot Code indicates the utilities you can use to enable boot code.
PAGE 1417
4. Emulex BIOS Utility Start the Emulex BIOS Utility 4. Emulex BIOS Utility Before using the Emulex BIOS utility, ensure that the boot code is loaded and enabled on the adapter as described in “Update and Enable Boot Code” on page 1416. Note: This section reflects the most recent release of the BIOS utility. Some selections may not be available if you are using an older version of the utility. Note: Changes made to parameters common to EFI and x86 drivers are changed in both driver configuration utilities.
PAGE 1418
4. Emulex BIOS Utility Start the Emulex BIOS Utility (Figure 4-2). Figure 4-2 Main Configuration Menu Under normal circumstances, you would first configure boot devices using the BIOS Utility (page 1419). However, in the following two situations, you must perform the indicated procedure first:   The adapter is not enabled to boot from SAN: You must enable the adapter’s BIOS to boot from SAN (See “Enable an Adapter to Boot from SAN” on page 1418).
PAGE 1419
4. Emulex BIOS Utility Configure Boot Devices Figure 4-3 BIOS Status Screen Configure Boot Devices This option supports FC_AL: (public and private loop) and fabric point-to-point. When operating in loop (FC_AL) topology, the system automatically determines whether you are configured for a public or private loop. The BIOS looks for a fabric loop (FL_Port) first. If a fabric loop is not detected, the BIOS looks for a private loop.
PAGE 1420
4. Emulex BIOS Utility Configure Boot Devices Figure 4-4 List of Saved Boot Devices Screen 2. Select a boot entry. A screen similar to Figure 4-5 is displayed. Figure 4-5 Device Selection List Example (Array) Screen Note: To minimize the amount of time needed to locate the boot device, Emulex recommends that you select the drive with the lowest ALPA as the boot device when connected to devices on a FC arbitrated loop. 3.
PAGE 1421
4. Emulex BIOS Utility Configure Boot Devices 4. If you select a device, you are asked for the starting LUN. Enter the starting LUN (Figure 4-6). The starting LUN can be any number from 0 to 255. Figure 4-6 LUN listing Screen You can define 256 LUNs per adapter, but the screen displays only 16 consecutive LUNs at a time. In front of each entry, B#D or B#W specifies the boot entry number and whether the device boots by DID or WWPN. For example, B1D means that boot entry 1 boots from the DID.
PAGE 1422
4. Emulex BIOS Utility Configure Adapter Parameters Identifier). Then, based on this DID, it continues with the remainder of the scanning. If you select to boot this device by DID, the earlier selected entry is saved in the flash memory. Figure 4-8 Primary Boot Device Set Up Screen 7. Press until you exit the BIOS utility. 8. Reboot the system for the new boot path to take effect.
PAGE 1423
4. Emulex BIOS Utility Configure Adapter Parameters When the main configuration menu (Figure 4-2) is displayed, select Configure Advanced Adapter Parameters. The adapter configuration menu is displayed. Figure 4-9 Adapter Configuration Menu Default settings are acceptable for most installations. To reset all values to their defaults, from the main configuration menu (Figure 4-2) select Reset Adapter Defaults.
PAGE 1424
4. Emulex BIOS Utility Configure Adapter Parameters 2. Select Change Default ALPA of this adapter. Information similar to Figure 4-10 is displayed. Figure 4-10 Change Default ALPA Screen 3. Change the default ALPA by using the arrow keys to scroll through the valid ALPAs. Table 4-1 below lists the valid ALPA values. 4. Press until you exit the BIOS utility. 5. Reboot the system. Note: If the adapter's ALPA is changed, it does not show on the NVRAM ALPA until the system has been reset.
PAGE 1425
4. Emulex BIOS Utility Configure Adapter Parameters Table 4-1 Valid ALPA Values (Continued) 0x9D 0x9E 0x9F 0xA3 0xA5 0xA6 0xA7 0xA9 0xAA 0xAB 0xAC 0xAD 0xAE 0xB1 0xB2 0xB3 0xB4 0xB5 0xB6 0xB9 0xBA 0xBC 0xC3 0xC5 0xC6 0xC7 0xC9 0xCA 0xCB 0xCC 0xCD 0xCE 0xD1 0xD2 0xD3 0xD4 0xD5 0xD6 0xD9 0xDA 0xDC 0xE0 0xE1 0xE2 0xE4 0xE8 0xEF Change the PLOGI Retry Timer This option is especially useful for Tachyon-based RAID arrays.
PAGE 1426
4. Emulex BIOS Utility Configure Adapter Parameters 3. Select the retry timer interval. 4. Press until you exit the BIOS utility. 5. Reboot the system Change Topology Emulex drivers support arbitrated loop and point-to-point topologies. If it is necessary to change the topology, do so before you configure boot devices. The default topology is auto topology with loop first. For FC-AL, each adapter has a default ALPA of 01 (Hex).
PAGE 1427
4. Emulex BIOS Utility Configure Adapter Parameters Enable or Disable the Spinup Delay This option allows you to enable or disable the disk spinup delay. The factory default setting is disabled. If at least one boot device has been defined, and the spinup delay is enabled, the BIOS searches for the first available boot device.   If a boot device is present, the BIOS boots from it immediately.
PAGE 1428
4. Emulex BIOS Utility Configure Adapter Parameters entries are configured to boot from DID or WWPN. The factory default is disabled. If there is more than one adapter with the same PCI Bus number in the system, and each has a boot drive attached, the first PCI-scanned adapter is the boot adapter. The first adapter is usually in the lowest PCI slot in the system.
PAGE 1429
4. Emulex BIOS Utility Configure Adapter Parameters Enable or Disable EDD 3.0 Enhanced Disk Drive (EDD) 3.0 provides additional data to the operating system boot loader during the INT-13h function 48h (get device parameters) call. This information includes the path to the boot device and disk size. The default setting for EDD 3.0 is enabled. Note: If EDD 3.0 is disabled, then EDD 2.1 is enabled. To enable or disable EDD 3.0: 1.
PAGE 1430
4. Emulex BIOS Utility Configure Adapter Parameters 2. Select Enable or Disable. The Enable or Disable Start Unit Command screen (Figure 4-16) is displayed. Figure 4-16 Enable or Disable Start Unit Command Screen 3. Press until you exit the BIOS utility. 4. Reboot the system. Enable or Disable the Environment Variable This option sets the boot controller order if the system supports the environment variable. The default setting is disabled. To enable or disable the environment variable: 1.
PAGE 1431
4. Emulex BIOS Utility Configure Adapter Parameters 4. Reboot the system. Enable or Disable Auto Boot Sector This option automatically defines the boot sector of the target disk for the migration boot process, which applies only to HP MSA1000 arrays. If there is no partition on the target, the default boot sector format is 63 sectors. The default setting is disabled. To enable or disable auto sector format select: 1.
PAGE 1432
4. Emulex BIOS Utility Configure Adapter Parameters   8 Gb/s 16 Gb/s Note: Emulex 8 Gb/s adapters do not support 1 Gb/s link speed. Emulex 16 G/bs adapters do not support 1 Gb/s or 2 Gb/s link speed. Additionally, some older devices do not support auto link speed detection, therefore the link speed must be forced to match the speed of those devices. To change the adapter’s link speed: 1. From the main configuration menu (Figure 4-2), select Configure Advanced Adapter Parameters.
PAGE 1433
4. Emulex BIOS Utility Configure Adapter Parameters Table 4-2 Adapter Defaults (Continued) Parameter Default Valid Values EDD 3.0 EDD 3.0 Disabled (EDD 2.1) Enabled (EDD 3.
PAGE 1434
4. Emulex BIOS Utility Configure Adapter Parameters To reset parameters to their factory default settings: 1. On the main configuration menu (Figure 4-2) select Reset Adapter Defaults. A screen is displayed that asks if you want to reset to the defaults. Figure 4-20 BIOS Utility Screen 2. Press . All settings revert to their factory default values. Note: After exiting the FC BIOS configuration utility, the system will reboot whether or not any changes were made.
PAGE 1435
4. Emulex BIOS Utility Configure Adapter Parameters However, Multi-boot allows changing the boot order in the server BIOS, which allows any disk to become the C drive. Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1436
5. OpenBoot Attribute Commands 5. OpenBoot OpenBoot commands are supported by the Sun SPARC system. Attribute Commands .boot-id Syntax ..boot-id Description Shows the current boot device ID. Parameters None devalias Syntax .devalias Description Shows the boot list. Parameters None .fcode Syntax ..fcode Description Shows the current version of OpenBoot. Parameters None host-did Syntax .host-did Description Shows the actual current ALPA of the adapter.
PAGE 1437
5. OpenBoot Attribute Commands .nvram Syntax ..nvram Description Shows the current flags for OpenBoot. show-devs "/pci@1f,0/pci@1/lpfc@1" select-dev /* select lpfc@1 (for example) */ .nvram Parameters None probe-scsi-all Syntax .probe-scsi-all Description Shows the current SCSI and FC devices. Parameters None show-devs Syntax .show-devs Description Shows a list of the devices found. Parameters None .topology Syntax ..topology Description Shows the current topology.
PAGE 1438
5. OpenBoot Functional Commands Functional Commands .remove-boot-id Syntax .remove-boot-id Description Removes the boot ID from the boot list. "/pci@1f,0/pci@1/lpfc@1" select-dev remove-boot-id /* to clear boot id settings */ unselect-dev or "/pci@1f,0/pci@1/lpfc@1" select-dev set-default-mode /* to clear boot id settings */ unselect-dev Parameters None set-default-mode Syntax set-default-mode Description Resets to the default value mode.
PAGE 1439
5. OpenBoot Functional Commands set-max-lun Syntax set-max-lun Description Shows the current maximum LUN support. Changes and sets the support setting, the default max lun is 256. Parameters 0=Set Max Lun to 255 (Default) 1=Set Max Lun to 1023 2=Set Max Lun to 2047 3=Set Max Lun to 4095 set-post-linkup Syntax set-post-linkup Description Controls if a linkup is to occur during a POST. The default is off.
PAGE 1440
6. EFIBoot Install the EFI Utility 6. EFIBoot The Emulex EFIBoot boot code can be used on server platforms with EFI or UEFI-based system firmware, with or without an EFI shell. If your system firmware is EFI version 1.1 or UEFI version 2.0, the EFI utility can be invoked from the EFI Shell prompt. If your system firmware is UEFI 2.1 or newer, it expects the HII (Human Interface Infrastructure) interface to be present and implemented by the server manufacturer.
PAGE 1441
6. EFIBoot Install the EFI Utility A list of drive names is displayed (Figure 6-2). Figure 6-2 Drive List Example 4. Change to the desired drive by entering the drive name followed by a colon. For example, type fs0: 5. Load the EFI utility file: load filename.efi where filename is name of the Emulex EFIBoot file. The following message is displayed: load elxcli400A2.efi load:Image fs0: \elxcli400A2.
PAGE 1442
6. EFIBoot Install the EFI Utility A list of drivers is displayed (Figure 6-3). Figure 6-3 Driver Listing Screen 2. Run the drvcfg command followed by the driver image handle for the Emulex SCSI Pass Thru Driver, for example, C2 (your driver image handle number may be different): drvcfg -s c2 A list of all the adapters in the system is displayed (Figure 6-4). Your list may vary depending on the boot package you are using. Locate the adapter to enable, update, configure or troubleshoot.
PAGE 1443
6. EFIBoot Install the EFI Utility The EFI Main Utility menu is displayed (Figure 6-5). Figure 6-5 Main EFI – Bios Utility Menu EFI Utility Conventions The EFI utility has menus and configuration screens with a navigation bar at the bottom of the each one:      Press the up/down arrows on your keyboard to move through and select menu options or configuration fields. Screens with adapter listings and information display up to eight rows at a time.
PAGE 1444
6. EFIBoot Configure EFIBoot via EFI Shell Invocation Configure EFIBoot via EFI Shell Invocation The EFI utility has many options that can be modified to provide for different behavior. Use the EFI utility to do the following tasks:      Enable or disable the BIOS Configure HBA parameters Configure boot parameters Reset an adapter to its default values Save and restore configurations Note: You must issue a connect - r command in the EFI shell or reboot for any changes to take effect.
PAGE 1445
6. EFIBoot Enable or Disable the BIOS 2. Select 1. Enable or Disable BIOS and press . The current BIOS status is displayed (Figure 6-7). Figure 6-7 BIOS Status Screen 3. If the current status is disabled, select Enabled and press . The status changes to enabled (Figure 6-8). Figure 6-8 BIOS Enabled Screen You can configure EFIBoot systems for up to eight boot devices. Configure one boot device at a time. Press to return to the EFI utility menu.
PAGE 1446
6. EFIBoot Configure Adapter Parameters Configure Adapter Parameters The EFI utility enables you to configure the following adapter parameters:     Default ALPA Topology Port login (PLOGI) retry timer Link speed To configure adapter parameters: From the EFI – BIOS Setup Utility menu (Figure 6-6) select 2. Configure HBA Parameters and press . The Adapter Configuration (Figure 6-9) is displayed.
PAGE 1447
6. EFIBoot Configure Adapter Parameters To change the default ALPA: 1. On the Adapter Configuration menu, select 1. Default ALPA of this adapter and press . A screen similar to Figure 6-10 is displayed. Figure 6-10 Default ALPA Setup Screen 2. Select the HardALPA value field, use the up/down arrows to change the default value, and press . The new value is displayed. 3. Press to return to the EFI utility menu.
PAGE 1448
6. EFIBoot Configure Adapter Parameters 3. Press to return to the EFI utility menu. Change the PLOGI Retry Timer This option allows you to set the interval for the port login (PLOGI) retry timer. This option is especially useful for Tachyon-based RAID arrays. Under very rare occasions, a Tachyon-based RAID array resets itself and the port goes offline temporarily in the loop. When the port comes to life, the PLOGI retry interval scans the loop to discover this device. To change timer values: 1.
PAGE 1449
6. EFIBoot Configure Adapter Parameters To change the link speed: 1. On the Adapter Configuration menu, select 4. Force Link Speed and press . A screen similar to Figure 6-13 is displayed. Possible link speeds depend upon your adapter model. Figure 6-13 Force Link Speed Setup Screen 2. Use the up/down arrows to select a link speed and press .
PAGE 1450
6. EFIBoot Configure Boot Parameters Configure Boot Parameters The EFI utility enables you to configure the following boot parameters:      Device path Maximum LUNs per target Boot target scan Boot devices Delay device discovery To configure boot parameters: From the EFI – BIOS Setup Utility menu (Figure 6-6), select 3. Configure Boot Parameters and press . The menu shown in Figure 6-14 is displayed.
PAGE 1451
6. EFIBoot Configure Boot Parameters To change the device path: 1. On the Boot Configuration menu, select 1, Device Path Selection and press . The screen shown in Figure 6-15 is displayed. Figure 6-15 Device Path Screen 2. Use the up/down arrows to change the path and press . The screen is refreshed with the new value. The device path is typically not changed. The SCSI device path is used for legacy systems. 3. Press to return to the EFI utility menu.
PAGE 1452
6. EFIBoot Configure Boot Parameters 256 is the default, and typical, number of LUNs in a device. 3. Press any key to return to the configuration menu. Set Up Boot Target Scan This option is available only if none of the eight boot entries are configured to boot from DID or WWPN. The Configure Boot Devices menu is used to configure up to eight boot entries for fabric point-to-point, public loop or private loop configurations. With boot scan enabled, the first device issues a Name Server Inquiry.
PAGE 1453
6. EFIBoot Configure Boot Parameters the EFIBoot Configuration utility, or by using third-party software from the EFI shell command prompt. If you select Boot Scan from EFIFCScanLevel:  If the EFIFCScanLevel variable already exists, the screen in Figure 6-18 shows the current setting and allows you to select a new setting.
PAGE 1454
6. EFIBoot Configure Boot Parameters Configure Boot Devices This list allows you to select up to eight boot devices that will be enumerated by the boot driver. Whether they are used for boot or not depends on how you configure the boot manager in the EFI system firmware or boot code. To configure an EFI boot device: 1. On the Boot Configuration menu, select 4. Configure Boot Devices and press . The screen shown in Figure 6-20 is displayed. Figure 6-20 Device Rows Screen 2.
PAGE 1455
6. EFIBoot Configure Boot Parameters 4. Select 1. Scan Targets and press . The system scans the adapter and shows your targets, as shown in Figure 6-22. Figure 6-22 Target Listing Screen Eight targets are displayed per screen. If more than eight targets are configured, press the right arrow key to view additional targets eight at a time. 5. Select a target row and press . LUNs for the target are displayed, as shown in Figure 6-23.
PAGE 1456
6. EFIBoot Configure Boot Parameters 6. Select a LUN and press . The screen shown in Figure 6-24 is displayed. Figure 6-24 LUN Boot Options Menu 7. Press to return to the list of devices. 8. Select 1. Boot this device via WWN and press . Figure 6-25 shows the LUN selected in step 5. Figure 6-25 Device Rows with a Selected LUN to Boot with WWNN Screen 9. Press until you return to the EFI utility menu. Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1457
6. EFIBoot Configure Boot Parameters Cancel a Boot Device To cancel boot device: 1. On the Boot Configuration menu, select 4. Configure Boot Devices and press . The screen shown in Figure 6-26 is displayed. Figure 6-26 Boot LUNs 2. Select a device row and press . The screen shown in Figure 6-27 is displayed. Figure 6-27 Selected Boot Device 3. Select 2. Clear Flash Boot Info and press . The system clears the target as the remote boot device.
PAGE 1458
6. EFIBoot Configure Boot Parameters Change Device Discovery Delay This parameter sets a delay to occur after an loop initialization and before a scan is initiated to discover the target. The default is off or 0 seconds. Change the default if you have an HP MSA1000 or HP MSA1500 RAID array and if both of the following conditions exist:   The MSA array is directly connected or part of an arbitrated loop (for example, daisy chained with a JBOD). The boot LUN is not reliably discovered.
PAGE 1459
6. EFIBoot Reset to Default Values Reset to Default Values The EFI utility enables you to reset EFI boot parameter to their factory default settings. These defaults are listed in Table 6-1.
PAGE 1460
6. EFIBoot Save and Restore Configurations To reset parameters to their factory default settings: 1. From the EFI-BIOS Setup Utility menu (Figure 6-6) select 4. Reset to Default Values and press . The screen shown in Figure 6-29 is displayed. Figure 6-29 Force Defaults Dialog Screen 2. Press . All settings revert to their factory default values.
PAGE 1461
6. EFIBoot Save and Restore Configurations Save the Configuration to a File Saving a configuration to a file allows you to reuse the configuration at a later time, such as to restore a changed configuration or to migrate the configuration across other adapters or systems. The file must be saved to a formatted storage medium with a valid file system recognized by the EFI system firmware or boot code.
PAGE 1462
6. EFIBoot Save and Restore Configurations Batch Configuration Batch configuration migrates an adapter’s configuration across several adapters at the same time. Note: No other adapter functions can be performed while batch configuration is in progress. There are two ways to perform batch configuration: 1. Migrate the configuration of one adapter to other adapters in the system. 2. Migrate the configuration stored in a previously saved configuration file to the adapters in the system.
PAGE 1463
6. EFIBoot Save and Restore Configurations 2. Select 1. Read Configuration from NVRAM and press . A list of the adapters in the system is displayed (Figure 6-34). Figure 6-34 Select Source Adapter for Configuration Listing Screen 3. Use the up and down arrows on your keyboard to select the source adapter for the configuration and press . A menu of all adapters in your system, except the source adapter, is displayed (Figure 6-35).
PAGE 1464
6. EFIBoot Save and Restore Configurations 5. Press
to configure the selected adapters. If the adapters are configured successfully, a screen similar to Figure 6-36 is displayed. Figure 6-36 Successful Batch Configuration Screen If all adapters are not configured successfully, a screen similar to Figure 6-37 is displayed. Figure 6-37 Unsuccessful Adapter Configuration Screen To migrate the configuration stored in a configuration file to the adapters in the system: 1.
PAGE 1465
6. EFIBoot Update an Adapter’s Firmware or Boot Code 2. Select 2. Read Configuration From File. The screen shown in Figure 6-38 prompts you to enter a directory path to the previously saved configuration file. Figure 6-38 Read Configuration Path Screen 3. Enter the directory path and file name and press . A list of the adapters in the system is displayed (Figure 6-35). 4. Select (check) the adapters that are to be batch configured. To select an adapter, highlight the row and press the space bar.
PAGE 1466
6. EFIBoot Update an Adapter’s Firmware or Boot Code 2. On the Firmware Update Utility menu, select 1. Update Selected Adapter and press . Figure 6-39 Update Selected Adapter 3. Enter the directory path and filename in the screen that is displayed (Figure 6-40). Press . Figure 6-40 Directory Path and Filename Information Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1467
6. EFIBoot Update an Adapter’s Firmware or Boot Code The boot code is updated on the selected adapter. Information similar to Figure 6-41 is displayed. Figure 6-41 Successful Boot Code Update Screen 4. Reboot the system for this change to take effect. Update Firmware or Boot Code Across Multiple Adapters 1. On the main EFI utility menu select 2. Firmware Update and press . The Firmware Update Utility menu is displayed (Figure 6-39). 2. Select 2. Batch Mode Update, and press .
PAGE 1468
6. EFIBoot Update an Adapter’s Firmware or Boot Code 4. Press
to update the firmware or boot code. You are prompted for a directory path and file name for the firmware or boot code image file (Figure 6-43). Enter the path and file name, and then press . Figure 6-43 Batch Mode Update path Screen The boot code update begins on the first adapter.
PAGE 1469
6. EFIBoot EFIBoot Reference After all adapters are updated, a listing with success or failure status is displayed (Figure 6-45). Figure 6-45 Successful Batch Update Screen EFIBoot Reference Driver Handle Table Column Definitions To view Emulex driver handle information, at the shell prompt type: drivers A list of drivers is displayed. Figure 6-46 Driver Listing Screen Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1470
6. EFIBoot EFIBoot Reference Driver Handle Table Column Definitions Drv The device driver handle number. Version The driver version. Type The device type. D indicates a device driver. B indicates a bus driver. Cfg If this column is marked with an X, the driver is supported by the EFI utility (configuration protocol). Diag If this column is marked with an X, the driver is supported by the EFI diagnostic protocol. #D The number of devices for the driver.
PAGE 1471
6. EFIBoot EFIBoot Reference  RSCN and LOGO/PRLO are handled by the driver. Reception of either causes new discovery/logins to take place. Note: In a fabric environment, the order in which disk devices are created is based on the name server response data (which is not guaranteed to be in any special order). Between successive boots, the same device may be identified with a different physical device number.
PAGE 1472
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Start the Emulex Configuration Utility 7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System EFIBoot is not supported on legacy converged network adapters (CNAs) such as the LP21000 and LP21002. If you have several adapters in your system, the UEFI system firmware or boot code uses the highest version driver that is on one of your adapters.
PAGE 1473
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Start the Emulex Configuration Utility The Emulex Adapter Configuration Main Menu is displayed. Select the function you want and press . Figure 7-2 Emulex Adapter Configuration Main Menu EFI Utility Conventions in UEFI/HII The EFI utility has menus and configuration screens.
PAGE 1474
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure EFIBoot in UEFI/HII Configure EFIBoot in UEFI/HII The EFI utility has numerous options that can be modified to provide for different behavior.
PAGE 1475
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Scan for Fibre Devices 3. Make your selection and press . The utility displays the new boot from SAN setting. Figure 7-4 New Boot From SAN Setting Scan for Fibre Devices To scan for fibre devices: 1. From the Adapter Selection screen, select the adapter that you want to scan for Fibre devices and press . 2. From the Main menu, select Scan for Fibre Devices and press .
PAGE 1476
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Add Boot Devices determine SAN connectivity. To add or configure boot devices, see the following sections. Figure 7-5 Discovered Targets Screen Add Boot Devices To add a boot device: 1. From the Adapter Selection screen, select the adapter to which you want to add a boot device and press . Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1477
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Add Boot Devices 2. From the Main menu, select Add Boot Device and press . A screen appears displaying the discovered targets. Figure 7-6 Discovered Targets Screen 3. Select the target you want and press . A list of bootable LUNS is displayed. Figure 7-7 Boot Device Screen Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1478
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Delete Boot Devices 4. Select the boot device you want to add and press . A menu appears enabling you to commit or discard your changes. Figure 7-8 Commit/Discard Changes Menu 5. Select Commit Changes and press . Delete Boot Devices To delete boot devices: 1. From the Adapter Selection screen, select the adapter from which you want to delete a boot devices and press .
PAGE 1479
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Delete Boot Devices 2. From the Main menu, select Delete Boot Device and press . A list of boot devices is displayed. Figure 7-9 Boot Device Screen 3. Select the boot device you want to delete and press the space bar. The device appears with an X beside it. Figure 7-10 Selected Boot Device Appears with an X Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1480
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Change Boot Device Order Note: This screen is different for LPe16000 adapters, but the functionality is the same. 4. Select Commit Changes and press . Change Boot Device Order To change boot device order: 1. From the Adapter Selection screen, select the adapter whose boot device order you want to change and press . 2. From the Main menu, select Change Boot Device Order and press .
PAGE 1481
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Change Boot Device Order 3. Select Boot Device Order and press . A screen appears displaying the boot device order. Figure 7-12 Boot Device Order Screen 4. Press . The Boot Device Order menu screen appears. Figure 7-13 Boot Device Order Menu Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1482
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Adapter Parameters 5. From the menu, select the device whose boot order you want to change. Use the <+> or <-> keys to change the order of the selected device and press . A screen appears showing the new boot device order. 6. Press to confirm the changes.
PAGE 1483
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Adapter Parameters Change the Topology Emulex drivers support arbitrated loop and point-to-point topologies. You can configure:     Auto Loop first – default Auto point to point first Point to point FCAL To change the topology: 1. From the Adapter Selection screen, select the adapter whose topology you want to change and press . 2.
PAGE 1484
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Adapter Parameters Change the PLOGI Retry Timer This option allows you to set the interval for the PLOGI retry timer. This option is especially useful for Tachyon-based RAID arrays. Under very rare occasions, a Tachyon-based RAID array resets itself and the port goes offline temporarily in the loop. When the port comes to life, the PLOGI retry interval scans the loop to discover this device.
PAGE 1485
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Adapter Parameters Change the Link Speed Use this feature to change, or force, the link speed between ports instead of auto-negotiating. The supported link speeds depend upon the adapter. The menu only displays options that are valid for the selected adapter. Note: The Link Speed setting will be overwritten by the FC driver and will not take effect during a regular boot into the local OS.
PAGE 1486
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Boot Parameters Note: Emulex 8 Gb/s adapters do not support 1 Gb/s link speed. Emulex 16 Gb/s adapters do not support 1Gb/s or 2 Gb/s link speed. The screen is refreshed with the new value. 4. Press to return to the EFI utility menu. 5. Select Commit Changes and press .
PAGE 1487
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Boot Parameters 3. Type the maximum LUN value (between 1 and 4096) and press Enter. The screen is refreshed with the new value. Note: 256 is the default, and typical, maximum number of LUNs in a target device. A higher number of maximum LUNs causes the discovery to take more time. 4. Press to return to the EFI utility menu. 5. Select Commit Changes and press .
PAGE 1488
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Boot Parameters 2. From the Configure Boot Parameters menu, navigate to Boot Target Scan Method and press . The Boot Target Scan Method menu appears. Figure 7-19 Boot Target Scan Method Menu Screen 3. Select a boot scan setting and press .The screen is refreshed with the new value. If you have a large SAN and set the boot path to “Boot Path Discovered Targets,” discovery takes a long time. 4.
PAGE 1489
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Configure Boot Parameters If both of the conditions exist, typically set this parameter to 20 seconds. However, the delay only needs to be long enough for the array to be reliably discovered after a reset. Your value may be different. To change the delay device discovery value: 1. From the Adapter Selection screen, select the adapter whose device discovery delay settings you want to change and press . 2.
PAGE 1490
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Reset Emulex Adapters to Default Values Reset Emulex Adapters to Default Values The EFI utility enables you to clear the NVRAM target list and set all boot device WWNNs back to 0. These defaults are listed in Table 7-1.
PAGE 1491
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Reset Emulex Adapters to Default Values 2. From the Main menu, select Set Emulex Adapters to Default Settings and press . A menu screen appears enabling you to set defaults or cancel default settings. Figure 7-21 Adapter Defaults Menu 3. Select Set Adapter Defaults and press . The Adapter Selection screen appears.
PAGE 1492
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Display Adapter Information 4. Select the adapter whose setting you want to return to their defaults and press . The Main Configuration Menu appears. 5. Select Set Emulex Adapter to Default Settings and press . The Adapter Default Settings menu screen appears. Figure 7-23 Adapter Defaults Menu 6. Select Set Adapter Defaults and press . The adapter is returned to its default settings.
PAGE 1493
7. Configure EFIBoot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System Display Adapter Information 2. From the Adapter configuration Main menu, select Display Adapter Info and press . A screen appears displaying information about the selected adapter. Figure 7-24 Adapter Information Screen Note: This screen is different for LPe16000 adapters, but the functionality is the same. Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1494
8. Troubleshooting x86 BootBIOS 8. Troubleshooting There are circumstances in which your system may operate in an unexpected manner. This section explains several of these circumstances and offers one or more workarounds for each situation. x86 BootBIOS Table 8-1 x86 BootBIOS Troubleshooting Issue Situation The Bootup Message Does Not Appear As the System Boots You want to access Make sure that x86 BootBIOS has been loaded and enabled. the BIOS utility, but the bootup message does not appear.
PAGE 1495
8. Troubleshooting OpenBoot OpenBoot Table 8-2 OpenBoot Troubleshooting Issue Situation Resolution The System Cannot mount or fsck /etc/vfstab a FC Boot Disk (Solaris LPFC Driver) During the boot process, the system cannot mount or fsck /etc/vfstab a FC boot disk. Make sure that persistent binding is implemented correctly. A Loaded File Is Not Executable (Solaris LPFC Driver) After entering boot disk, a The boot block may not be installed correctly to the FC message states that the file that drive.
PAGE 1496
8. Troubleshooting EFIBoot Diagnostic Utility EFIBoot Diagnostic Utility The EFI Diagnostic Utility tests all adapters in your system. Conventions           Press the up/down arrows on your keyboard to move through and highlight menu options or configuration fields. Menus with adapter listings and information display up to eight rows at a time. If applicable, press the up/down arrows to scroll to additional adapters.
PAGE 1497
8. Troubleshooting Access the EFI Diagnostic Utility 3. Press . Information similar to Figure 8-1 is displayed (listing all adapters in the system): Figure 8-1 Adapter Listing Screen 4. Use the up/down arrows and to select (highlight) an adapter and press . The Diagnostic Main menu is displayed. Figure 8-2 Diagnostic Main Menu Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1498
8. Troubleshooting Run Loopback Tests Run Loopback Tests Test patterns for the PCI Loopback, Internal Loopback, and External Loopback tests may be selected to be run individually. Test indicators are Passed, Failed, or Unsupported. Unsupported is displayed if the test is not supported. For example, if an unsupported link speed is selected, a test is not performed at the unsupported speed, and a status of Unsupported is displayed in front of the link speed on the link speed menu. To run a single test: 1.
PAGE 1499
8. Troubleshooting Run Loopback Tests 3. Another menu is displayed. Select one or more individual patterns for the diagnostic test. For example: Figure 8-4 PCI Loopback Test Data Patterns Menu 4. Press one or more times as necessary to display the Diagnostic Tests menu. 5. Use the up/down arrow keys to highlight <5>. Execute Selected Diagnostic and press . The selected tests run. After tests are performed, the status of each selected pattern is displayed.
PAGE 1500
8. Troubleshooting Run Loopback Tests Diagnostic Test Specifics PCI Loopback Test The PCI loopback test executes the RunBuiDiag64 mailbox command once for each test pattern. The data length for each test is 128 bytes. A loopback connector is required for this test. Internal and External Loopback Tests Internal and external loopback tests execute the ElsEcho FCP command to send 124 bytes from the transmit to the receive side of an FC port. A loopback connector is required for the external loopback test.
PAGE 1501
8. Troubleshooting Run Adapter Diagnostic Tests As tests are performed a screen similar to the following is displayed: Figure 8-8 Internal Loopback Test Progress Screen Test results are displayed on the Test Data Pattern menu and saved to results log. Figure 8-9 Internal Loopback Test Data Pattern Results Screen Run Adapter Diagnostic Tests The Adapter Diagnostic Tests include adapter restart, display of some configuration parameters, results of linkup and target login.
PAGE 1502
8. Troubleshooting Run Adapter Diagnostic Tests When you run adapter diagnostic tests, a screen similar to the following is displayed: Figure 8-10 Running Adapter Diagnostic Tests In Progress Screen If all tests pass, “Passed” is displayed on the Diagnostic Utility menu. For example: Figure 8-11 Select Diagnostic Tests – Adapter Diagnostic Tests Passed Screen If any one of these tests fail, Failed is displayed on the Select Diagnostic Tests screen.
PAGE 1503
8. Troubleshooting Run Adapter Diagnostic Tests Examples Figure 8-13 Configuration Information Screen Figure 8-14 Firmware Information Screen Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1504
8. Troubleshooting Run Adapter Diagnostic Tests Figure 8-15 Vendor Product Data (VPD) Screen Figure 8-16 Controller Information Screen Figure 8-17 Service Level Interface Memory (SLIM) Information Screen Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1505
8. Troubleshooting Run Adapter Diagnostic Tests Figure 8-18 Peripheral Component Interconnect (PCI) Information Screen Note: View up to 256 bytes of PCI configuration space using paging. 128 bytes are displayed at a time. Use the key to select byte, word, or dword display. View Device Data The device data is stored in the results log and is displayed on the console in ASCII and hexadecimal format. To view data for attached block devices: 1.
PAGE 1506
8. Troubleshooting Run Adapter Diagnostic Tests 2. Use the up/down arrow keys to highlight an attached block I/O device and press . A screen similar to Figure 8-20 is displayed. Figure 8-20 Device Data Screen 3. To read the individual block from the media, specify the logical block address (LBA) and press . 256 bytes of sector data display per screen. Use the left/right arrow keys to scroll through the data.
PAGE 1507
8. Troubleshooting Run Adapter Diagnostic Tests To view the results log: Access the Diagnostic Main menu (Figure 8-2) and select <4>. View Results Log. Press . A screen similar to the following is displayed: Figure 8-22 Results Log Screen To scroll through the results log:   Use the up/down arrow keys to scroll one row at a time. Use the Home/End keys to scroll one page at a time. Note: The Page Up and Page Dn keys do not navigate the results log. To view help on the results log screen.
PAGE 1508
8. Troubleshooting Run Adapter Diagnostic Tests Once the file is successfully saved, a screen similar to the following is displayed: Figure 8-24 Successful Log to File Screen To clear the log result, press . The results on the diagnostic tests are erased, and a new time and date is written to the log. Boot for the Fibre Channel Protocol User Manual P010096-01A Rev.
PAGE 1509
Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1510
EMULEX CONFIDENTIAL. Copyright © 2003–2014 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.
PAGE 1511
1. Introduction Overview 1. Introduction Overview This manual describes installing, enabling, and configuring boot code for Emulex® network interface card (NIC), Internet Small Computer System Interface (iSCSI), and Fibre Channel over Ethernet (FCoE) adapters. This manual also describes the Emulex boot from SAN implementation and its operation with distinct hardware and operating system requirements.
PAGE 1512
1. Introduction Abbreviations Configuring boot devices and advanced adapter parameters iSCSISelect Utility  Setting up a basic configuration  Configuring and managing iSCSI initiators and targets   The boot code is distributed in the same image used to flash the firmware. Several methods are available for flashing the firmware and boot code image. See the documentation accompanying each utility for additional information on the flash procedure.
PAGE 1513
1.
PAGE 1514
1.
PAGE 1515
1. Introduction Abbreviations UNDI Universal Network Device Interface USB Universal Serial Bus VF virtual function VLAN virtual local area network VM virtual machine VMQ virtual machine queue vNIC virtual NIC WDS Windows Deployment Services WWN world wide name WWNN world wide node name WWPN world wide port name x Used to designate a variable. For example, SPx includes SP1, SP2, etc. ZB zettabyte Boot Version 10.
PAGE 1516
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Pre-OS 2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Note: This section applies to LPe16202, OCe10100, and OCe11100-series adapters. See chapter 3., “Configuring PXE Boot for NIC on OCe14000-series Adapters,” on page 1534 for information specific to those adapters. Note: The LPe16202 adapter may be reported as an OCe15100 adapter by certain applications.
PAGE 1517
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters PXE Boot Process Figure 2-1 PXE Boot Process Figure 2-1 shows the boot process. 1. The PXE boot ROM sends a DHCP request extended with PXE specific options (step 1 in the figure). 2. The DHCP responses contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot server lists (steps 2 through 5). 3.
PAGE 1518
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, and 2012 R2 Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, and 2012 R2 For remote installation with PXE, a network driver for the Emulex adapter must be part of the client's installation image on the server.
PAGE 1519
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility For remote installation with PXE, a network driver for the Emulex adapter must be part of the client's installation image on the server. Your current Linux distribution may or may not include network drivers for Emulex adapters. If they do, the driver may need to be added to your operating system’s installation image, or added during installation.
PAGE 1520
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility performed in the UEFI configuration utility. See chapter 11., “Configuring UEFI for Ethernet,” on page 1625 for more information. Setting Up a PXE Bootable Network After the PXE boot BIOS initializes, you can use the PXESelect utility to set up a PXE bootable network by configuring your controllers. To configure controllers for PXE boot: 1.
PAGE 1521
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Note: On 4-port controllers, the Advanced Mode setting is not provided in the PXESelect utility.  Personality – This option specifies a list of available protocols that can be configured on an adapter. For additional information on adapter personality, see “Personality Option” on page 1521. Note: Changing the Personality setting requires a reboot before the change will take effect.
PAGE 1522
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility The menu only displays the available personalities, including both free and licensed personalities. The NIC personality implies that all the enabled functions provide NIC/TOE functionality. Note: TOE is not supported on LPe16202/OCe15000-series adapters. iSCSI and FCoE personalities are enabled on one function per adapter port and include NIC functionality on the other enabled functions.
PAGE 1523
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility 3. If multichannel is enabled, on the Multichannel Configuration screen select the specific function and press . A pop-up menu is displayed. Figure 2-6 Custom Personality Selection on Multichannel Configuration Screen Note: If multichannel is disabled, on the Port Configuration screen select the specific function and press . A pop-up menu is displayed. 4.
PAGE 1524
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Note: Advanced Mode is not supported on OCe10100-series controllers. Table 2-1 Advanced Mode Capabilities (by Operating System) Operating System Advanced Mode Enabled Advanced Mode Disabled (Legacy Mode) Windows 16 RSS queues 4 RSS Queues Note: Only supported on Windows Server 2008 R2, 2012, and 2012 R2. Remains four queues for earlier Windows versions.
PAGE 1525
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Configuring Ports When Multichannel is Disabled or Not Supported Note: If your adapter has multichannel enabled, refer to “Configuring Universal Multichannel” on page 1528. If you are using an IBM adapter, refer to “Configuring Multichannel for IBM Adapters” on page 1530.
PAGE 1526
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Configuring SR-IOV If your system BIOS supports SR-IOV, you can enable it on the adapter. SR-IOV support can only be enabled when multichannel is disabled or not supported. For more information on SR-IOV configuration, see the appropriate Emulex driver manual. To configure SR-IOV: 1. On the configuration screen, use the key to select the SR-IOV setting and a pop-up menu appears. 2.
PAGE 1527
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Physically Identifying the Port To physically determine which port you are configuring by causing the link and activity LEDs of that port to blink: 1. On the configuration screen, select Port Identification and press . The Port Identification screen appears. Figure 2-10 Port Identification Screen 2. The LEDs on your controller begin blinking.
PAGE 1528
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Configuring Universal Multichannel Note: UMC support is only available on OCe11100-series adapters. Note: If your adapter has multichannel enabled and also supports IBM Virtual Fabric Mode or IBM Unified Fabric Protocol Mode, refer to “Configuring Multichannel for IBM Adapters” on page 1530 for additional information.
PAGE 1529
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility 2. From the MultiChannel Configuration screen, you can perform the following tasks:  Configure PXE boot support – see “Configuring PXE Boot Support” on page 1525 for instructions.  Configure PXE VLAN ID/Priority – see “Configuring the PXE VLAN ID and Priority” on page 1526 for instructions.  Identify ports – see “Physically Identifying the Port” on page 1527 for instructions.
PAGE 1530
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility Note: LPVIDs also need to be configured on the switch port. Each LPVID must be unique and is relevant for NIC traffic only. The LPVID is not supported for storage functions. For iSCSI storage functions, you must configure a VLAN ID through iSCSISelect or through the host. For additional information, see “Configuring VLAN ID and VLAN Priority” on page 1604.
PAGE 1531
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility  Disabled Note: For more information on the available Multichannel Modes, see “Multichannel Modes”. 3. Select Save and press . 4. To proceed, select Continue and press . With the Multichannel Mode selected, you can now configure multichannel support. See “Multichannel Configuration” for more information.
PAGE 1532
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters Using the PXESelect Utility When configuring multichannel on adapters that support IBM Virtual Fabric and UFP modes, the configuration screen will depend on the Multichannel Mode that has been selected. Note: For illustration purposes, the screen displays in this section are for a system with IBM Virtual Fabric Mode enabled.
PAGE 1533
2. Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters PXE Boot Parameters Default Values Note: An LPVID is optional for IBM Virtual Fabric Mode, but it is required for every function when using Switch Independent Mode. Note: When IBM Virtual Fabric Mode or Unified Fabric Protocol Mode is enabled, you must configure the minimum and maximum bandwidth settings on the switch.
PAGE 1534
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Pre-OS 3. Configuring PXE Boot for NIC on OCe14000-series Adapters Note: This section applies only to OCe14000-series adapters. See chapter 2., “Configuring PXE Boot for NIC on LPe16202, OCe10100, and OCe11100-series Adapters,” on page 1516 for information specific to those adapters.
PAGE 1535
3. Configuring PXE Boot for NIC on OCe14000-series Adapters PXE Boot Process Figure 3-1 PXE Boot Process Figure 3-1 shows the boot process. 1. The PXE boot ROM sends a DHCP request extended with PXE specific options (step 1 in the figure). 2. The DHCP responses contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot server lists (steps 2 through 5). 3. The PXE client attempts to download the specified NBP over TFTP from one of the specified boot servers (steps 6 and 7). 4.
PAGE 1536
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, and 2012 R2 Remotely Installing with PXE for Windows Server 2008, 2008 R2, 2012, and 2012 R2 For remote installation with PXE, a network driver for the Emulex adapter must be part of the client's installation image on the server.
PAGE 1537
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility For remote installation with PXE, a network driver for the Emulex adapter must be part of the client's installation image on the server. Your current Linux distribution may or may not include network drivers for Emulex adapters. If they do, the driver may need to be added to your operating system’s installation image, or added during installation.
PAGE 1538
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility configuration that can be performed in the PXESelect utility can instead be performed in the UEFI configuration utility. See chapter 11., “Configuring UEFI for Ethernet,” on page 1625 for more information. Setting Up a PXE Bootable Network After the PXE boot BIOS initializes, you can use the PXESelect utility to set up a PXE bootable network by configuring your controllers. To configure controllers for PXE boot: 1.
PAGE 1539
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Note: On HP systems, you can select either Disable or Flex-10 for the MultiChannel setting. When Flex-10 is selected, the settings are display only and cannot be configured. Note: A reboot will occur when you exit the PXESelect utility if the multichannel mode has changed since the last boot.  Personality – This option specifies a list of available protocols that can be configured on an adapter.
PAGE 1540
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility   If multichannel is enabled, refer to “Configuring Multichannel” on page 1547 for additional configuration information. If multichannel is enabled and you are using IBM adapters, refer to “Configuring Multichannel for IBM Adapters” on page 1553 for additional configuration information.
PAGE 1541
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Use the left or right arrow keys to select the desired personality. Figure 3-5 Configure Controller Screen – Personality Selection 2. Press to save. Note: Changing the Personality setting requires a reboot before the change will take effect. A reboot will occur when you exit the PXESelect utility if the Personality setting has changed since the last boot.
PAGE 1542
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility 2. Use the left or right arrow keys to enable or disable SRIOV. 3. Press to save. For more information on SR-IOV configuration, see the appropriate Emulex driver manual. Configuring NIC Mode Note: This setting is only available when SR-IOV is enabled, Personality is set to “NIC”, and a two-port OCe14000-series adapter is in use. This setting allows you to control the VF count on a two-port OCe14000-series adapter.
PAGE 1543
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility 2. Select the port you want to configure and press . The Port Menu appears. Figure 3-7 Port Menu Screen The Port Menu screen enables you to perform the following tasks:    View NIC configuration information – see “Viewing NIC Configuration Information” on page 1543 for additional information. Configure boot options – see “Configuring Boot Options” on page 1544 for instructions.
PAGE 1544
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility  If the Personality setting is set to NIC or NIC+RoCE, the Configure Channel screen appears. Figure 3-9 Configure Channel Screen 2.
PAGE 1545
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Configuring Port Options To view the Port Configuration screen: 1. From the Port Menu (Figure 3-7), select 3. Port Configuration and press . The Port Configuration screen appears. Figure 3-11 Port Configuration Screen 2. From the Port Configuration screen, you can perform the following tasks:  View the physical link speed and link status.
PAGE 1546
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Physically Identifying the Port To physically determine which port you are configuring by causing the link and activity LEDs of that port to blink: 1. On the Port Configuration screen, press . 2. The LEDs on your controller begin blinking. The selected port’s LED status indicators blink on your controller for approximately 15 seconds. Note: Not all controllers have LEDs that are visible externally.
PAGE 1547
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Configuring Multichannel Note: If your adapter has multichannel enabled and also supports IBM Virtual Fabric Mode or IBM Unified Fabric Protocol Mode, refer to “Configuring Multichannel for IBM Adapters” on page 1553 for additional information. If multichannel is disabled or not supported on the adapter, refer to “Configuring Ports When Multichannel is Disabled or Not Supported” on page 1540.
PAGE 1548
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility ARI Support The OCe14000-series adapters support ARI, which provides the ability to configure additional PCI functions or I/O channels for each physical adapter port when multichannel is enabled. You can configure up to 16 functions on a one-port OCe14400-series adapter, up to eight functions per port on a one or two-port OCe14100-series adapter, and up to four functions per port on a four-port OCe14100-series adapter.
PAGE 1549
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility To select the personality of the adapter: 1. From the Configure Controller screen (Figure 3-12), use the up or down arrow keys to select Personality. 2. Use the left or right arrow keys to select the desired personality. 3. Press to save. Note: Changing the Personality setting requires a reboot before the change will take effect.
PAGE 1550
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Selecting a Port Once you have set the options in the Configure Controller screen, ensure that you have saved your changes. To save the current settings, press . To proceed to the Port Selection menu: 1. From the Configure Controller screen, press . The Port Selection Menu appears. Figure 3-13 Port Selection Menu Note: The Port Selection Menu only appears if there are two or more ports connected. 2.
PAGE 1551
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Configuring Multichannel Options To configure the multichannel options: 1. From the Port Menu screen, use the up or down arrow keys to select 1. MultiChannel Configuration and press . The Channel(s) List screen appears. Figure 3-15 Channels List Screen 2. Select a channel using the up or down arrow keys and press . The Configure Channel screen appears. Figure 3-16 Configure Channel Screen 3.
PAGE 1552
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Note: SR-IOV is automatically disabled when multichannel is enabled. Note: Your adapter or system may not support all multichannel options. Configuring Minimum and Maximum Bandwidth To configure bandwidth: 1. On the Configure Channel screen, use the use the up or down arrow keys to select Min BW or Max BW. 2. Use the left or right arrow keys to select the desired bandwidth value.
PAGE 1553
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility PXE Install OS PXE Server configured with VLAN 5 PXE VLAN=5 LPVID for function 0=5 To configure LPVID: 1. On the Configure Channel screen, use the use the up or down arrow keys to select LPVID. 2. Use the left or right arrow keys to select the desired LPVID value. The LPVID range is 2-4094. A value of 0 disables the LPVID. 3. Press to save.
PAGE 1554
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility With the Multichannel Mode selected, you can now configure multichannel support. See “Multichannel Configuration” for more information. Multichannel Modes Note: The following modes are only available on IBM adapters and systems that support IBM Virtual Fabric and Unified Fabric Protocol modes.
PAGE 1555
3. Configuring PXE Boot for NIC on OCe14000-series Adapters Using the PXESelect Utility Note: For illustration purposes, the screen displays in this section are for a system with the IBM Virtual Fabric Mode multichannel mode selected. Figure 3-18 IBM Virtual Fabric Mode MultiChannel Configuration Screen Note: If your system does not support some of the multichannel options, those unavailable options are disabled on the MultiChannel Configuration screen. 2.
PAGE 1556
3. Configuring PXE Boot for NIC on OCe14000-series Adapters PXE Boot Parameters Default Values PXE Boot Parameters Default Values The default settings for the PXE Boot parameters are listed in the following table. Table 3-1 PXE Boot Parameter Default Values Parameter Default Value Valid Values Multichannel The default for this parameter varies depending on the vendor configuration.
PAGE 1557
3. Configuring PXE Boot for NIC on OCe14000-series Adapters PXE Boot Parameters Default Values Table 3-1 PXE Boot Parameter Default Values (Continued) Parameter Default Value Valid Values PXE Boot Support The default for this parameter varies depending on the vendor configuration. Enabled Disabled Enabled PXE VLAN Disabled Disabled PXE VLAN ID 0 0–4094 PXE VLAN Priority 0 0–7 Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1558
4. Configuring Boot from SAN for the FCoE Protocol Windows Server 2008, Windows Server 2012, and Windows Server 2012 R2 4. Configuring Boot from SAN for the FCoE Protocol When booting from SAN, the storage device is typically identified by its WWPN and a LUN. By extending the server system BIOS, boot from SAN capability is provided by the boot BIOS contained on an Emulex adapter in the server.
PAGE 1559
4. Configuring Boot from SAN for the FCoE Protocol Windows Server 2008, Windows Server 2012, and Windows Server 2012 R2 Configuring Boot from SAN on Windows (UEFI) To configure boot from SAN: 1. If necessary, update the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 2. If necessary, enable the boot code on the adapter. See “Enabling an Adapter to Boot from SAN” on page 1579 for more information. 3. Configure boot devices.
PAGE 1560
4. Configuring Boot from SAN for the FCoE Protocol Windows Server 2008, Windows Server 2012, and Windows Server 2012 R2 loader utility. Windows Boot Manager can be found in the Start Options menu of the Host Server UEFI. 9. The Windows Boot Manager option is inserted as the first boot option in the boot order list of the Host Server UEFI. The CD/DVD boot is the second device in the boot order list. 10. Upon reboot, the system boots from the LUN set up on the SAN.
PAGE 1561
4. Configuring Boot from SAN for the FCoE Protocol Installing Windows Server 2008, 2008 R2, 2012, or 2012 R2 on a Boot Disk (x64) For more information on the GUID partition table, see the Microsoft website and search for the terms Windows and GPT FAQ. Installing Windows Server 2008, 2008 R2, 2012, or 2012 R2 on a Boot Disk (x64) This procedure installs Windows Server 2008, 2008 R2, 2012, or 2012 R2 onto an unformatted disk drive and configures the system to boot from the SAN disk drive.
PAGE 1562
4. Configuring Boot from SAN for the FCoE Protocol Linux, Citrix, and VMware Linux, Citrix, and VMware Configuring Boot from SAN on Linux, Citrix, or VMware (x86 and x64) To configure boot from SAN: 1. If necessary, update the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 2. If necessary, enable the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 3.
PAGE 1563
4. Configuring Boot from SAN for the FCoE Protocol Solaris Solaris Configuring Boot from SAN on Solaris SFS (x86 and x64) To configure boot from SAN: 1. If necessary, update the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 2. If necessary, enable the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 3. Enable the adapter to boot from SAN.
PAGE 1564
4. Configuring Boot from SAN for the FCoE Protocol Solaris Configuring Boot from SAN on Solaris SFS (SPARC) To configure boot from SAN: 1. If necessary, update the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 2. If necessary, enable the boot code on the adapter. See chapter 7., “Updating and Enabling Boot Code,” on page 1595 for more information. 3.
PAGE 1565
4. Configuring Boot from SAN for the FCoE Protocol Solaris 3. Create a directory to contain the DVD image. # mkdir -p install_dir_path Install_dir_path specifies the directory where the DVD image is to be copied. 4. Change to the Tools directory on the mounted disc. # cd /cdrom/cdrom0/Solaris_10/Tools Note: For Solaris 10 only: a. Remove the SUNWemlxu and SUNWemlxs from /install_dir_path/Solaris/Tools/Boot. b.
PAGE 1566
4. Configuring Boot from SAN for the FCoE Protocol Solaris   If the nfsd daemon is online, continue to step c. If the nfsd daemon is not online, start it. Type the following command: # svcadm enable svc:/network/nfs/server  If the install server is running the Solaris 9 operating system, or compatible version, type the following command: # ps -ef | grep nfsd   If the nfsd daemon is running, continue to step c. If the nfsd daemon is not running, start it. # /etc/init.d/nfs.server start c.
PAGE 1567
4. Configuring Boot from SAN for the FCoE Protocol Solaris where:    wwpn|did|alpa is the device WWPN, DID, or AL_PA of the storage device. lun is the LUN number in hexadecimal. To enter it in decimal, enter d# [lun]. target_id is the target ID in hexadecimal. To enter it in decimal, enter d# [target_id]. Note: Emulex recommends using the WWPN in most cases.
PAGE 1568
4. Configuring Boot from SAN for the FCoE Protocol Solaris umount /usr2 14. Copy the export/home file system: mount /dev/dsk/clt1d0s7 /export2 ufsdump 0f - /dev/rdsk/c0t0d0s7 | (cd /export2; ufsrestore rf -) umount /export2 15. Perform copy: mount /dev/dsk/clt1d0s0 /root2 ufsdump 0f - /dev/rdsk/c0t0d0s0 | (cd /root2; ufsrestore rf -) 16. Edit /root2/etc/vfstab, changing the controller number, target number and LUN number to point to the new FC boot disk.
PAGE 1569
4. Configuring Boot from SAN for the FCoE Protocol Solaris Booting Solaris 10 from the Network on SPARC Machines To boot from the network: 1. Set up the install server and the boot server (if required). See the topic for Network-Based Installations in the Solaris 10 10/09 Installation Guide. 2. Obtain the MAC address of the OCE port used for the net boot: a.
PAGE 1570
4. Configuring Boot from SAN for the FCoE Protocol Solaris subsystem-id subsystem-vendor-id revision-id device-id vendor-id 0000e602 000010df 00000002 00000700 000019a2 3. Add the MAC address from step 2 as an installation client to the Install/Boot server. 4. Power on the client machine and wait for the ok prompt. 5. Set the net device alias for the device selected in step 2.  If the net device alias is already set to the network device to be used for the net boot, skip this step.
PAGE 1571
5. Configuring x86/x64 Platforms for the iSCSI Protocol iSCSI Overview 5. Configuring x86/x64 Platforms for the iSCSI Protocol iSCSI Overview iSCSI is an IP-based standard for linking data-storage devices over a network and transferring data by carrying SCSI commands over IP networks. An iSCSI network consists of one or more iSCSI storage units (targets) connected through a copper or optical networking cable to 10Gb Ethernet network switches and/or IP routers.
PAGE 1572
5. Configuring x86/x64 Platforms for the iSCSI Protocol Managing an iSCSI Session Managing an iSCSI Session To transmit information from an iSCSI initiator to an iSCSI target, the initiator must first establish a session with the target through an iSCSI login process. The login process:    Starts a TCP/IP connection. Verifies that the iSCSI initiator has access to the iSCSI target (authentication). Allows negotiation of various parameters.
PAGE 1573
5. Configuring x86/x64 Platforms for the iSCSI Protocol Configuring for the iSCSI Protocol Windows Server To set up boot from SAN for iSCSI on Windows Server: 1. Log into the iSCSISelect utility by pressing when prompted. 2. Use the iSCSISelect utility to log into a target from one adapter and configure it for boot. For more information, see chapter 9., “Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility,” on page 1599 and chapter 10.
PAGE 1574
5. Configuring x86/x64 Platforms for the iSCSI Protocol Configuring for the iSCSI Protocol ESXi Server To install and configure boot from SAN on ESXi Server: 1. Log into the iSCSISelect utility pressing when prompted. 2. Use the iSCSISelect utility to log into a target from one adapter and configure it for boot. For more information, see chapter 9., “Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility,” on page 1599 and chapter 10.
PAGE 1575
5. Configuring x86/x64 Platforms for the iSCSI Protocol Configuring for the iSCSI Protocol Protocol be disabled on any ports that are connected to Windows Server 2008 or 2012 hosts booting via iSCSI. The Spanning Tree Protocol is used to calculate the best path between switches where there are multiple switches and multiple paths through the network. 3. Install a Windows Server operating system over the iSCSI LUN. 4.
PAGE 1576
5. Configuring x86/x64 Platforms for the iSCSI Protocol Configuring for the iSCSI Protocol 3. Install a Linux operating system over the iSCSI LUN. For more information refer to the Emulex Driver for Linux User Manual, which is available on the Emulex website. For iSCSI boot, you will need the following information: For RHEL operating systems: a. When running the vmlinuz command, include the dd parameter to indicate that a driver update will be done. b.
PAGE 1577
5. Configuring x86/x64 Platforms for the iSCSI Protocol Configuring for the iSCSI Protocol e. Select the same LUN you chose for your initial boot LUN, then press to set it to bootable. f. Follow the instructions on the bottom of the menu screens until you are prompted to exit. g. Save your changes before you exit. h. Press to exit the iSCSISelect utility. 9. After Linux boots up, the MPIO installs drivers on the second path and prompts you to reboot. Reboot the server. ESXi 5.0, 5.1, or 5.
PAGE 1578
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Navigating the FCoE BIOS Utility 6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Before using the FCoE BIOS utility, ensure that the boot code is loaded and enabled on the adapter as described in “Updating and Enabling Boot Code” on page 1595. Note: This section reflects the most recent release of the FCoE BIOS utility. Some selections may not be available if you are using an older version of the utility.
PAGE 1579
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Enabling an Adapter to Boot from SAN Figure 6-1 Emulex Adapter Listing 2. Select the adapter to configure and press . The main configuration menu is displayed (Figure 6-2). Figure 6-2 Main Configuration Menu Under normal circumstances, you would first configure boot devices using the BIOS Utility. However, if the adapter is not enabled to boot from SAN, you must first enable the adapter to do so.
PAGE 1580
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Scanning for Target Devices Figure 6-3 BIOS Status Scanning for Target Devices To scan for target devices: 1. From the Main configuration menu, select Scan for Target Devices. This option only displays a list of discovered target devices. It allows you to quickly verify zoning and SAN connectivity while providing a mechanism to log in ports for zoning. Figure 6-4 Devices Present on the Adapter 2.
PAGE 1581
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Boot Devices Configuring Boot Devices To configure boot devices: 1. On the main configuration menu (Figure 6-2), select Configure Boot Devices and press . A list of eight boot devices is shown (Figure 6-5). Emulex recommends that you configure only the bootable devices. The primary boot device is the first entry shown. It is the first bootable device.
PAGE 1582
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Boot Devices 3. Select <00> and press to clear the selected boot entry, or select a device to configure booting by WWPN or DID and press . 4. If you select a device, you are asked for the starting LUN. Use the up and down arrows to enter the starting LUN in hexadecimal format and press . (Figure 6-7). The starting LUN can be any number from 0 to 255. Figure 6-7 LUN Listing Screen 5.
PAGE 1583
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Boot Devices The Boot Devices menu is displayed. Figure 6-9 Boot Devices Menu 6. Use the up and down arrows to select the boot method. If you select to boot the device by WWPN, the WWPN of the earlier selected entry is saved in the flash memory. However, during the initial BIOS scan, the utility issues a Name Server Inquiry GID_PN (Get Port Identifier). Then, based on this DID, it continues with the remainder of the scanning.
PAGE 1584
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring CEE Parameters Configuring CEE Parameters Note: For DCBX configuration, the adapter is always in CEE mode. To configure CEE parameters: 1. If multiple VLANs or FCoE switches are set up and you want to select a particular VLAN to boot from every time, select Configure FCF CEE Parameters from the main configuration menu (Figure 6-2) and press . A list of discovered FCF is displayed. Figure 6-11 FCF Listing 2.
PAGE 1585
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters    Enable or disable the start unit command Enable or disable the environment variable Enable or disable the auto boot sector To access the adapter configuration menu, from the main configuration menu (Figure 6-2), select Configure Advanced Adapter Parameters and press . The adapter configuration menu is displayed.
PAGE 1586
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters 2. Select Change Default ALPA of this adapter and press . Information similar to Figure 6-14 is displayed. Figure 6-14 Change Default ALPA Screen 3. Change the default AL_PA, use the up and down arrow keys to scroll through the valid AL_PAs. Table 6-1 lists the valid AL_PA values. 4. Press to accept the new value. 5. Press to return to the advanced adapter configuration menu. 6.
PAGE 1587
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters Changing the PLOGI Retry Timer This option is especially useful for Tachyon-based RAID arrays. Rarely, a Tachyon-based RAID array resets itself and the port goes offline temporarily. When the port returns to operation, the PLOGI retry interval scans the loop to discover this device. The PLOGI retry interval is the time it takes for one PLOGI to scan the whole loop.
PAGE 1588
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters Enabling or Disabling the Spinup Delay This option allows you to enable or disable the disk spinup delay. The factory default setting is disabled. If at least one boot device has been defined, and the spinup delay is enabled, the boot BIOS searches for the first available boot device.   If a boot device is present, the boot BIOS boots from it immediately.
PAGE 1589
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters Setting Auto Scan This option allows you to set auto scan and enable the first device in the boot entry list to issue a Name Server Inquiry. Auto scan is available only if none of the eight boot entries is configured to boot from DID or WWPN. The factory default is disabled.
PAGE 1590
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters Enabling or Disabling EDD 3.0 EDD 3.0 provides additional data to the operating system boot loader during an INT-13h function 48h call (get device parameters). This information includes the path to the boot device and the disk size. The default setting for EDD 3.0 is enabled. When EDD 3.0 is disabled, the setting reverts to EDD 2.1. To enable or disable EDD 3.0: 1.
PAGE 1591
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters Figure 6-19 Enable or Disable Start Unit Command Screen 3. 4. 5. 6. Select whether to enable or disable the start unit command. Press to select the change. Press to return to the advanced adapter configuration menu. For changes to take effect, reboot the system.
PAGE 1592
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Using Multi-Path Boot from SAN Enabling or Disabling Auto Boot Sector This option automatically defines the boot sector of the target disk for the migration boot process, which applies only to HP MSA1000 arrays. If there is no partition on the target, the default boot sector format is 63 sectors. The default setting is disabled. To enable or disable the auto boot sector format: 1.
PAGE 1593
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Resetting to Default Values The order of boot entries exported to Multi-boot (BBS) is boot_entry0, boot_entry1, boot_entry2, and boot_entry3. However, Multi-boot allows changing the boot order in the server BIOS, which allows any disk to become the C drive. Resetting to Default Values The BIOS utility enables you to reset BIOS boot parameters to their factory default settings. These defaults are listed in Table 6-2.
PAGE 1594
6. Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Resetting to Default Values To reset parameters to their factory default settings: 1. On the main configuration menu (Figure 6-2) select Reset Adapter Defaults and press . A screen is displayed that asks if you want to reset to the defaults. Figure 6-22 Reset Adapter Configuration to Defaults Screen 2. Press . All settings revert to their factory default values. 3. Press to go to the previous menu. Boot Version 10.
PAGE 1595
7. Updating and Enabling Boot Code 7. Updating and Enabling Boot Code Emulex provides utilities to update and enable boot code. The utility that you use depends on the operating system and, in some cases, the driver type or system architecture. Table 7-1 indicates the utilities that are currently available for each operating system.
PAGE 1596
8. Configuring iSCSI Boot Support with the iSCSISelect Utility Navigating the iSCSISelect Utility 8. Configuring iSCSI Boot Support with the iSCSISelect Utility This section provides quick installation instructions for setting up a basic boot configuration. For more information on setting up an iSCSI initiator and adding an iSCSI target, see chapter 9., “Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility,” on page 1599 and chapter 10.
PAGE 1597
8. Configuring iSCSI Boot Support with the iSCSISelect Utility Setting Up a Basic iSCSI Boot Configuration 3. Select Save and press to save your initiator name. Figure 8-1 iSCSI Initiator Configuration Menu 4. Select Controller Configuration and press . If you are running a single controller, the Controller Configuration menu is displayed (Figure 8-3). If you are running multiple controllers, the Controller Selection menu is displayed (Figure 8-2). Figure 8-2 Controller Selection Menu 5.
PAGE 1598
8. Configuring iSCSI Boot Support with the iSCSISelect Utility Booting the System 10. From the Controller Configuration menu, select Network Configuration and press . The Network Configuration screen appears. Figure 8-5 Network Configuration Screen 11. Configure a network IP address. From the Network Configuration screen, you can do the following:  Select the IP version. You can choose IPv4 or IPv6. For more information, see “Selecting the IP Version” on page 1604.  Set up an IP address.
PAGE 1599
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring the iSCSI Initiator Name 9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility The iSCSI initiator or host (also known as the iSCSI client) is a system such as a server, which attaches to an IP network and initiates requests and receives responses from an iSCSI target. Each iSCSI host is identified by a unique IQN.
PAGE 1600
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Selecting a Controller name on this menu so that the iSCSI Initiator Name on all the controllers match. If there were pre-existing sessions before the iSCSI Initiator Name change, the pre-existing sessions use the original name that was used to login the very first time. The new name is used for any sessions added after the name change. 3. Select Save and press to save the iSCSI initiator name.
PAGE 1601
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Viewing the Controller Properties Viewing the Controller Properties The Controller Properties screen displays controller information and allows you to configure controller options, such as boot support, IPv4 boot target discovery using DHCP, and MPIO port configuration. To view the controller properties: 1. From the Controller Configuration menu (Figure 9-3), select Controller Properties and press .
PAGE 1602
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Viewing the Controller Properties Enabling IPv4 Boot Target Discovery using DHCP To enable IPv4 boot target discovery using DHCP: 1. From the Controller Properties screen (Figure 9-4), select Discover IPv4 Boot Target via DHCP and press . A pop-up menu appears. Figure 9-6 Controller Properties Screen with Discover IPv4 Boot Target via DHCP Pop-up Menu 2. Select Enabled or Disabled and press . 3.
PAGE 1603
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties To enable MPIO support: 1. From the Controller Properties screen (Figure 9-4), select MPIO Port and press . A pop-up menu appears. Figure 9-7 Controller Properties Screen with MPIO Port Pop-up Menu 2. Select Enabled or Disabled and press . 3. To save your changes, select Save and press .
PAGE 1604
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties Selecting the IP Version To select the IP version: 1. From the Network Configuration screen (Figure 9-8), select IP Version and press . A pop-up menu appears. Figure 9-9 Network Configuration Screen with IP Version Pop-up Menu 2. Select IPv4 or IPv6 and press . Configuring VLAN ID and VLAN Priority A Virtual Local Area Network (VLAN) is a way of partitioning the network.
PAGE 1605
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties 4. Set a VLAN Priority, if necessary. This unique value assigns a priority to outbound packets containing a specified VLAN ID. Valid values range from 0 -7, with 0 the highest priority level. 5. Select Save and press . 6. Press to return to the Network Configuration screen.
PAGE 1606
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties  Ping the iSCSI initiator. See “Pinging the iSCSI Initiator” on page 1608 for more information. Enabling DHCP Enabling DHCP provides the initiator with an IP address. Note: If you are using the DHCP server to obtain an IP address for your iSCSI initiator, set up a reservation. A reservation assigns a specific IP address based on the MAC address of your iSCSI function.
PAGE 1607
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties  Ping the iSCSI initiator. See “Pinging the iSCSI Initiator” on page 1608 for more information. Enabling Auto Configuration To automatically configure the IPv6 address, from the Configure IPV6 Address screen (Figure 9-13), select Enabled from the Auto Configuration pop-up menu and press .
PAGE 1608
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Configuring Network Properties Configuring a Static IPv6 Address If Auto Configuration is disabled, you must manually configure a static IPv6 address. To configure a static IP address: 1. From the Configure IPV6 Address screen (Figure 9-13), select Configure Static IP Address and press . The Static IP Address dialog box is displayed. Figure 9-15 Static IP Address Dialog Box for IPv6 2.
PAGE 1609
9. Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility Identifying a Port If you cannot verify the network interface, there may be a number of reasons why. For more information, see “Troubleshooting for the iSCSI Protocol” on page 1715. Identifying a Port Port identification, or beaconing, helps you physically determine which port you are configuring by blinking both the link and the activity LEDS of that port.
PAGE 1610
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Adding iSCSI Targets 10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility An iSCSI target is any device that receives iSCSI commands. The device can be an end node, such as a storage device, or it can be an intermediate device, such as a bridge between IP and FC devices. Each iSCSI target is identified by a unique IQN, and each port on the controller (or on a bridge) is identified by one or more IP addresses.
PAGE 1611
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Adding iSCSI Targets Using SendTargets Discovery to Add an iSCSI Target SendTargets discovery asks an iSCSI target to provide the list of target names that can be logged into by the initiator. The iSCSI initiator then uses the SendTargets Discovery option to perform the device discovery. Use this method if an iSCSI node has a large number of targets.
PAGE 1612
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Adding iSCSI Targets iSCSI Boot Configuration” on page 1596. Note: You must enable the Boot Target option after you add the target via SendTargets (see step 16). 10. Change the ISID qualifier value, if necessary. A unique ISID value is necessary if you connect dual sessions to the same target portal group. Enter a number up to 65535. For more information, see “Setting an ISID Value” on page 1616. 11.
PAGE 1613
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Adding iSCSI Targets 16. After you have added your targets, from the Controller Configuration menu, select iSCSI Target Configuration and press to view the added target information. Figure 10-4 iSCSI Target Configuration Screen Note: If you set the Boot Target option in step 5 before adding the target, the Boot Target displays No on this menu. To enable Boot Target, go to step 17. 17.
PAGE 1614
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target 12. Select Yes from the Data Digest pop-up menu if you want to enable Data Digest. When set to Yes, and the iSCSI initiator is set accordingly, the integrity of an iSCSI PDU’s data segment is protected by CRC32C checksum. The default setting is No. 13. Select the Authentication Method. For more information, see “Enabling CHAP Authentication” on page 1616. 14. Select Save/Login and press .
PAGE 1615
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target Editing a Target Configuration Once you have added a target, you can edit your iSCSI target configuration or apply other management options to the target. Note: If you want to change the target name, you must delete the existing target and add it again with the new target name. To edit a target configuration: 1. From the iSCSI Target Configuration dialog box, select the target and press .
PAGE 1616
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target The iSCSI Target Configuration appears with the revised information. Setting an ISID Value The ISID qualifier is a unique ISID value to specify if you are connecting dual sessions to the same target portal group. This value ensures that you do not log into the same session twice. A combination of the initiator name, ISID qualifier, target name, and target portal group defines an iSCSI session.
PAGE 1617
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target 4. From the Controller Configuration menu, select iSCSI Target Configuration and press . 5. Select Add New iSCSI Target and press . 6. Follow steps 5–11 in the procedure “Using SendTargets Discovery to Add an iSCSI Target” on page 1611. 7. In the Add/Ping iSCSI Target dialog box, select Authentication Method, select One-Way Chap, and press .
PAGE 1618
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target To enable mutual CHAP authentication: 1. Log into the iSCSISelect utility by pressing when prompted. 2. Select Controller Configuration and press . A list of controllers is displayed. 3. Select a controller and press . The Controller Configuration menu is displayed. 4. From the Controller Configuration menu, select iSCSI Target Configuration and press . 5.
PAGE 1619
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target Pinging a Target To ping a target: 1. From the Controller Configuration menu, select iSCSI Target Configuration and press . 2. Select Add/Ping iSCSI Target or Edit/Ping iSCSI Target and press . The “iSCSI Target IP Address” is the address that will be pinged. 3.
PAGE 1620
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target Configuring LUN Settings A LUN represents an individually addressable logical device that is part of a target. An initiator negotiates with a target to establish connectivity to a LUN. To configure a LUN: 1. From the iSCSI Target Configuration screen, press to display the LUNs associated with the iSCSI node. Figure 10-11 LUN Configuration Menu 2.
PAGE 1621
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Managing an iSCSI Target To log out of a target, from the iSCSI Target Configuration screen, select the target and press . To log into a target, from the iSCSI Target Configuration screen, select the target and the disconnected target, and then press to establish the target session. Booting the System After you have configured the iSCSI initiator and target, you must reboot the system for the configurations to take effect.
PAGE 1622
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Discovering Targets through DHCP for iSCSI Discovering Targets through DHCP for iSCSI For your target to be discovered by the initiator through DHCP, you must add the root path to the DHCP server: 1. From the DHCP server screen, select Scope Options, then right-click and select Configure Options. Figure 10-12 DHCP Server Screen Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1623
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Discovering Targets through DHCP for iSCSI 2. From the General tab, scroll down the list of available options and select 017 Root Path. Figure 10-13 DHCP Server Scope Options 3. In the String Value box, add the location of the iSCSI target you want to use for iSCSI boot. Enter the string in the following format: iscsi: ::: For example: iscsi:010.010.010.001:0:3260:0:iqn.
PAGE 1624
10. Configuring and Managing iSCSI Targets with the iSCSISelect Utility Enabling DHCP Discovery Through the iSCSISelect Utility Enabling DHCP Discovery Through the iSCSISelect Utility If your DHCP server supports DHCP discovery and you added the root path to the DHCP server, you can enable Discover Boot Target via DHCP using the iSCSISelect utility. By enabling Discover IPv4 Boot Target via DHCP, you can use DHCP discovery to provide the boot path from the DHCP server.
PAGE 1625
11. Configuring UEFI for Ethernet Overview 11. Configuring UEFI for Ethernet Overview UEFIBoot supports:        uEFI version – uEFI 2.3.1 compatible drivers (backward compatible with 2.
PAGE 1626
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Starting the Emulex NIC Configuration Utility Depending on the OEM UEFI configuration, the Emulex NIC configuration utility may appear under different setup menus in the OEM system firmware or BIOS (such as System Settings > Network). To start the Emulex NIC configuration utility via the HII: 1. The Network screen shows a list of the adapters in the system. Your list may vary depending on the installed adapters.
PAGE 1627
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility 2. Select an adapter and press . The Emulex NIC Selection Screen appears. Figure 11-2 Emulex NIC Selection Screen The Emulex NIC Selection screen displays the following adapter information and configuration options:           Firmware Version – the current firmware version installed on the adapter. The firmware version is the same as the boot version.
PAGE 1628
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility    Emulex Flash Update Utility – for more information, see “Downloading Firmware and Boot Code” on page 1656. Port Identification – for more information, see “Identifying a Port” on page 1659. Erase Configuration – for more information, see “Erasing Ports and Controller Configuration” on page 1660. Advanced Mode Support Advanced Mode is a driver compatibility option.
PAGE 1629
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility To enable Advanced Mode support: Note: Changing the Advanced Mode setting requires a reboot. 1. On the Emulex NIC Selection Screen, select Advanced Mode and press . The Advanced Mode pop-up menu appears. 2. Select Enable and press . 3. Reboot the system. Configuring Boot Mode This setting configures the boot mode.
PAGE 1630
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Configuring iBFT Note: Boot mode must be set to Disable to access the iBFT Configuration menu. iSCSI configuration through the NIC interface (iBFT) is exactly the same as normal iSCSI configuration except it is performed through the NIC interface. In order for this to occur, you must use the operating system’s NIC driver and an iBFT-aware operating system. To configure iBFT: 1.
PAGE 1631
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Changing the iSCSI Name To edit the iSCSI initiator name: 1. On the iBFT Configuration screen, highlight iSCSI Name and press . This is a global setting. The iSCSI initiator name configured on one adapter is reflected on all adapters in the system. Note: HP systems are an exception to the previous statement. Each port on an HP system can be configured with a unique initiator name.
PAGE 1632
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility 2. From the CHAP Authentication Mode pop-up menu, select None, One-way CHAP, or Mutual CHAP and press .  One-way CHAP – With one-way CHAP authentication, the target authenticates the initiator. Use one-way CHAP authentication for a one-way challenge/response security method – you must configure the CHAP ID and CHAP Secret, which is authenticated by the target.
PAGE 1633
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Note: This option is only available when TCP/IP parameters via DHCP is enabled.  Select virtual LAN mode Once you have completed the network configuration, you must save your changes. To save changes: 1. Press to return to the iBFT Configuration screen. 2. Press again to return to the NIC Selection Menu. 3. Select Save Changes and press .
PAGE 1634
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Selecting Virtual LAN Mode When virtual LAN mode is enabled, a VLAN tag can be used by iSCSI boot. To enable virtual LAN mode: 1. On the Network Configuration screen (Figure 11-5), select Virtual LAN Mode and press . 2. From the Virtual LAN Mode pop-up menu, select Enabled and press . Configuring the Primary and Secondary Targets To configure the iSCSI target parameters: 1.
PAGE 1635
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility  Target’s CHAP ID and secret Note: These options are only available when the initiator’s CHAP authentication mode has been properly set. Once you have completed the primary or secondary target configuration, you must save your changes. To save changes: 1. Press to return to the NIC Selection Menu. 2. Select Save Changes and press . Configuring the Boot Target Note: Only one boot target can be enabled at a time.
PAGE 1636
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility To configure the target’s ISID qualifier: 1. On the Primary Target screen, select ISID Qualifier and press . 2. Enter the target’s ISID qualifier value and press . Configuring the Target’s TCP Port To configure the target’s TCP port: 1. On the Primary Target screen, select TCP Port and press . 2. Enter the target’s TCP port value and press .
PAGE 1637
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility  Custom – For more information on the Custom personality, see “Selecting the Custom Personality” on page 1639. The menu only displays the available personalities, including both free and licensed personalities. To view the personalities supported on the adapter: 1. Select Personality on the Emulex NIC Selection Screen (Figure 11-2), and then press . The Personality Selection screen appears. 2.
PAGE 1638
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Selecting the NIC+RoCE Personality Note: The NIC+RoCE personality is available only on OCe14000-series adapters running Windows with multichannel and SR-IOV disabled. The NIC+RoCE personality implies that all the enabled functions provide RoCE functionality. When NIC+RoCE is enabled, you must select a NIC+RoCE profile. The NIC+RoCE profile allows you to select the appropriate profile for your particular system setup.
PAGE 1639
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Selecting the Custom Personality The Custom personality allows you to select the protocol type for each function. iSCSI and FCoE personalities may only be enabled on one function per adapter port. Note: There cannot be two iSCSI functions and two FCoE functions on a single port. To select the Custom personality: 1. From the Personality Selection screen (Figure 11-7), select Custom and press .
PAGE 1640
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Configuring the Controller When Multichannel is Disabled or Not Supported Note: If your adapter has Multichannel Mode enabled, refer to “Configuring Universal Multichannel” on page 1644. If you are using an IBM adapter, refer to “Configuring Multichannel for IBM Adapters” on page 1649.
PAGE 1641
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Viewing the Configuration To view the current configuration: 1. On the Controller Configuration screen, select View Configuration and press . The View Configuration screen appears.
PAGE 1642
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility To configure SR-IOV: 1. On the Controller Configuration screen, select Configure SRIOV and press . The Configure SRIOV screen appears. Figure 11-12 Configure SRIOV Screen 2. Select the current setting for a particular NIC function and a pop-up menu appears. 3. Select Enable or Disable and press . 4. When you are finished, press to return to the Controller Configuration screen.
PAGE 1643
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility To select the NIC Mode: 1. From the Configure SRIOV screen (Figure 11-12), select the NIC Mode setting for a particular NIC function and a pop-up menu appears. Figure 11-13 Configure NIC Mode Pop-up Menu 2. Select NIC Only Profile or NIC-ETS Disabled and press . 3. When you are finished, press to return to the Controller Configuration screen.
PAGE 1644
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Configuring Universal Multichannel Note: UMC is only available on OCe11100-series and OCe14000-series adapters. Note: If your adapter has Multichannel Mode enabled and also supports IBM Virtual Fabric Mode or IBM Unified Fabric Protocol Mode, refer to “Configuring Multichannel for IBM Adapters” on page 1649 for additional information.
PAGE 1645
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility To configure the multichannel configuration: 1. On the Emulex NIC Selection screen, select Controller Configuration and press . A list of available options is displayed. Figure 11-14 Controller Configuration Screen The Controller Configuration screen enables you to perform the following tasks:     View the current configuration of each function. Configure the minimum and maximum bandwidth percentage.
PAGE 1646
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility RHEL 6.4 and newer versions  SLES 11 SP2 and newer versions  ESXi 5.0 and newer versions The application management tools, including the OneCommand Manager application must support ARI. ARI must be enabled in the firmware using the OneCommand Manager application.
PAGE 1647
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Configuring Minimum and Maximum Bandwidth To configure bandwidth: 1. On the Controller Configuration screen, select Configure Bandwidth and press . The Configure Bandwidth screen appears. Figure 11-16 Configure Bandwidth Screen 2. Select a specific function under Configure Minimum Bandwidth or Configure Maximum Bandwidth and press .
PAGE 1648
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Configuring the LPVID The LPVID is used to enforce a VLAN ID on all traffic originating from an IP address, channel, or PCI function. If the operating system for that PCI function has set up a VLAN ID, then the operating system-configured VLAN ID takes precedence over the LPVID for transmit packets while the operating system-configured VLAN ID and LPVID-tagged packets will both be received.
PAGE 1649
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility 4. When you are finished configuring LPVIDs, press to return to the Controller Configuration screen. Saving the Configuration To save the configuration changes, on the Controller Configuration screen, select Save Configuration and press .
PAGE 1650
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility  Disabled Note: For more information on the available Multichannel Modes, see “Multichannel Modes”. With the Multichannel Mode selected, you can now configure multichannel support. See “Multichannel Configuration” on page 1650 for more information. Multichannel Modes Note: The following modes are only available on certain adapters and systems that support IBM Virtual Fabric and Unified Fabric Protocol modes.
PAGE 1651
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility IBM Virtual Fabric Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to IBM Virtual Fabric Mode: 1. On the Emulex NIC Selection screen, select Controller Configuration and press . A list of available options is displayed. Figure 11-19 IBM Virtual Fabric Mode Controller Configuration Screen 2.
PAGE 1652
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility IBM Unified Fabric Protocol Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to IBM Unified Fabric Protocol Mode: 1. On the Emulex NIC Selection screen, select Controller Configuration and press . A list of available options is displayed. Figure 11-20 IBM Unified Fabric Protocol Mode Controller Configuration Screen 2.
PAGE 1653
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Switch Independent Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to Switch Independent Mode: 1. On the Emulex NIC Selection screen, select Controller Configuration and press . A list of available options is displayed. Figure 11-21 Switch Independent Mode Controller Configuration Screen 2.
PAGE 1654
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility Port Management Note: The Port Management functionality is only available on IBM NIC adapters, and the configuration menu is only available on port 0. The Port Management option is used to enable or disable the physical ports. When port 0 is disabled, it brings down the physical link for port 0 and the power consumption of the adapter is lowered; however, the PCI functions associated with that port must remain enabled.
PAGE 1655
11. Configuring UEFI for Ethernet Starting the Emulex NIC Configuration Utility 5. Press to return to the Controller Configuration screen. Note: A reboot is required for this setting to take effect. Feature on Demand Note: The Feature on Demand functionality is only available on some IBM adapters. FoD is an IBM proprietary protocol that enables storage functions on Emulex adapters. This feature requires a unique license key to be applied from IBM's IMM.
PAGE 1656
11. Configuring UEFI for Ethernet Downloading Firmware and Boot Code FoD Status: The FoD Status field indicates whether a license key has been applied properly or not.   When the FoD status field is set to “Enabled”, it indicates that the FoD license key has been successfully applied and FoD is enabled. When FoD is enabled, you will see all of the storage personalities under the Personality menu option, including NIC, iSCSI, and FCOE.
PAGE 1657
11. Configuring UEFI for Ethernet Downloading Firmware and Boot Code Update Utility screen is displayed. This utility displays all available media and installs the flash file on the adapter. Figure 11-25 Emulex Flash Update Utility 5. Press to select the media containing the flash file. Figure 11-26 Emulex Flash Update Utility with Directory Name Dialog Box Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1658
11. Configuring UEFI for Ethernet Downloading Firmware and Boot Code 6. Navigate to the directory containing the flash file and press . Figure 11-27 Emulex Flash Update Utility with Flash File Name Dialog Box Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1659
11. Configuring UEFI for Ethernet Identifying a Port 7. Use the arrow keys to select the flash file and press to begin the update process. It takes about two minutes to complete. Figure 11-28 Emulex Flash Update Utility, Flash Updating Note: This firmware flash procedure only flashes the physical interface which was selected in the HII menu. All Emulex adapters must contain the same firmware version to function properly.
PAGE 1660
11. Configuring UEFI for Ethernet Erasing Ports and Controller Configuration Note: If port identification is not supported on your system, you will receive a message stating that it is not supported. Erasing Ports and Controller Configuration Note: When selecting this setting, all previous configuration settings are returned to their factory default settings except for the current personality selection.
PAGE 1661
11. Configuring UEFI for Ethernet Erasing Ports and Controller Configuration UEFI NIC Diagnostics The UEFI NIC driver diagnostics protocol can be used to run diagnostic tests on each NIC function of the card. This protocol is used by a platform management utility to allow you to run driver specific diagnostics on a controller.
PAGE 1662
11. Configuring UEFI for Ethernet Erasing Ports and Controller Configuration The drvdiag command list all the devices available for diagnostics. Each Ctrl [XXX] corresponds to a NIC function, which may be physical or virtual. The command returns handles for NIC functions on both ports.
PAGE 1663
12. Configuring UEFI for iSCSI Overview 12. Configuring UEFI for iSCSI Note: For systems with multiple adapters, the UEFI system firmware or boot code uses the highest version driver installed on any of the adapters. Adapters with older versions of EFIBoot are managed by the more recent version, but only as long as the adapter with the most recent version is in the system.
PAGE 1664
12. Configuring UEFI for iSCSI Starting the Emulex iSCSI Configuration Utility Starting the Emulex iSCSI Configuration Utility Depending on the OEM UEFI configuration, the Emulex iSCSI configuration utility may appear under different setup menus in the OEM system firmware or BIOS (such as Storage). To start the Emulex iSCSI configuration utility: 1. Select the Emulex iSCSI Utility for a particular function and press . Figure 12-1 Storage Screen Boot Version 10.
PAGE 1665
12. Configuring UEFI for iSCSI Configuring MPIO The Controller Configuration Menu screen is displayed. Figure 12-2 Controller Configuration Menu Screen 2. Highlight iSCSI Initiator Name and press to edit the initiator name. This is a global setting. The initiator name configured on one adapter is reflected on all adapters in the system. Note: HP systems are an exception to the previous statement. Each port on an HP system can be configured with a unique initiator name. 3.
PAGE 1666
12. Configuring UEFI for iSCSI Configuring MPIO 3. Install third-party MPIO software for your operating system. 4. Configure the second path to a single boot LUN through the Emulex iSCSI configuration utility. To configure MPIO: 1. From the Controller Configuration Menu screen, select MPIO Configuration and press . Figure 12-3 Controller Configuration Menu Screen with MPIO Configuration Setting Highlighted 2. From the MPIO Configuration pop-up menu, select Enable or Disable and press . 3.
PAGE 1667
12. Configuring UEFI for iSCSI Configuring Boot Support Configuring Boot Support Boot support is provided for each port or function. If boot support is enabled, you can boot from the specified function. If boot support is disabled, you will not be able to boot from the function. To configure boot support: 1. From the Storage screen (Figure 12-1), select the Emulex iSCSI Utility for a particular function and press . The Controller Configuration Menu is displayed.
PAGE 1668
12. Configuring UEFI for iSCSI Viewing the Controller Properties Viewing the Controller Properties To view the controller properties: 1. From the Storage screen (Figure 12-1), select the Emulex iSCSI Utility for a particular function and press . The Controller Configuration Menu is displayed (Figure 12-2). 2. From the Controller Configuration Menu screen, select Controller Properties and press . The Controller Properties screen is displayed.
PAGE 1669
12. Configuring UEFI for iSCSI Configuring the Network Configuring the Network To configure the network: 1. From the Controller Configuration Menu screen (Figure 12-2), select Network Configuration and press . The Network Configuration screen is displayed. Figure 12-6 Network Configuration Screen The Network Configuration screen displays the MAC address, port speed, and link status for the adapter.
PAGE 1670
12. Configuring UEFI for iSCSI Configuring the Network Configuring the IP Version To configure the IP version: 1. On the Network Configuration screen (Figure 12-6), select IP version and press . Figure 12-7 Network Configuration Menu Screen with IP Version Setting Highlighted 2. From the IP Version pop-up menu, select IPV4, IPV6, or DUAL MODE and press . 3. To save your changes, select Save Changes and press . Boot Version 10.
PAGE 1671
12. Configuring UEFI for iSCSI Configuring the Network Configuring an IPV4 Address To configure an IPv4 address: 1. On the Network Configuration screen (Figure 12-6), ensure the IP version is set to IPV4 or DUAL MODE. 2. Select Configure IPV4 Address and press . The Configure IPV4 Address screen is displayed. Figure 12-8 Configure IPV4 Address Screen 3. From the Configure IPV4 Address screen, you can do the following:  Enable DHCP for automatic assignment of the IP address through a DHCP server.
PAGE 1672
12. Configuring UEFI for iSCSI Configuring the Network Manually Assigning an IP Address To manually assign an IP address: 1. On the Configure IPV4 Address screen (Figure 12-8), ensure that the Initiator IP via DHCP is set to . If you change this setting from to , select Save DHCP Settings and press . 2. Select Configure Static IP Address and press . The Configure Static IP Address screen appears. Figure 12-9 Configure Static IP Address Screen 3.
PAGE 1673
12. Configuring UEFI for iSCSI Configuring the Network Configuring an IPV6 Address To configure an IPv6 address: 1. On the Network Configuration screen (Figure 12-6), ensure the IP version is set to IPV6 or DUAL MODE. 2. Select Configure IPV6 Address and press . The Configure IPV6 Address screen is displayed. Figure 12-10 Configure IPV6 Address Screen 3. From the Configure IPV6 Address menu, you can do the following:  Enable automatic configuration of the IP address.
PAGE 1674
12. Configuring UEFI for iSCSI Configuring the Network Configuring the IPv6 Address To configure the IPv6 address: 1. On the Configure IPV6 Address screen (Figure 12-10), select Configure IPV6 Address and press . The Configure IPV6 Address screen appears. Figure 12-11 Configure IPV6 Address Settings Screen 2. Enter the link local address, IPv6 address, routable address 1, routable address 2, and default gateway address in the corresponding fields. 3. Press to exit the menu.
PAGE 1675
12. Configuring UEFI for iSCSI Configuring the Network Configuring VLAN ID/Priority A VLAN is a way of partitioning the network. If the LAN is made up of all devices within a broadcast domain, a VLAN is a broadcast domain made up of switches. You first create a VLAN and then assign ports to a VLAN. All ports in a single VLAN are in a single broadcast domain. You do not have to configure VLANs unless your network is already using them.
PAGE 1676
12. Configuring UEFI for iSCSI Updating Firmware a. Select VLAN ID and press . This is a unique value you assign to each VLAN on a single device. There are a maximum of 4093 possible values ranging from 2-4094. b. Enter a VLAN ID value and press . 4. To set a VLAN priority, if necessary: a. Select VLAN PRIORITY and press . This unique value assigns a priority to outbound packets containing a specified VLAN ID. Valid values range from 0-7, with 0 the highest priority level. b.
PAGE 1677
12. Configuring UEFI for iSCSI Adding and Configuring Targets 3. Reboot the system. 4. On the Controller Configuration menu (Figure 12-2), select iSCSI Target Configuration and press . The iSCSI Target Configuration screen shows the discovered targets. Note: For more information on configuring a DHCP boot target, refer to “Discovering Targets through DHCP for iSCSI” on page 1622.
PAGE 1678
12. Configuring UEFI for iSCSI Adding and Configuring Targets Note: Only the first 64 sessions are returned during a single discovery session. 7. Enter the iSCSI target IP address. 8. Change the TCP port number value, if necessary. The default target port number is 3260. 9. Change the ISID qualifier value, if necessary. A unique ISID value is necessary if you connect dual sessions to the same target portal group. Enter a number up to 65535. 10.
PAGE 1679
12. Configuring UEFI for iSCSI Adding and Configuring Targets Figure 12-14 Discovered Targets Screen 16. After you have added your targets, from the Controller Configuration menu, select iSCSI Target Configuration and press to view the added target information. Note: If you set the Boot Target option in step 5 before adding the target, the Boot Target displays No on this menu. To enable Boot Target, proceed to step 17. 17.
PAGE 1680
12. Configuring UEFI for iSCSI Adding and Configuring Targets 4. On the iSCSI Target Configuration screen, select Add Targets and press . The Add/Ping iSCSI Target screen is displayed. Figure 12-15 Add/Ping iSCSI Target Screen 5. Enter the target IP address and TCP port number (the default target port number is 3260). 6. Change the ISID qualifier value, if necessary. A unique ISID value is necessary if you connect dual sessions to the same target portal group. Enter a number up to 65535.
PAGE 1681
12. Configuring UEFI for iSCSI Adding and Configuring Targets Setting a Boot Target The discovered target must be set as a boot target to enable iSCSI boot. To set a boot target: 1. On the iSCSI Target Configuration screen, select the target name and press . The Edit/Ping Target screen is displayed. Figure 12-16 Boot Target Option on the Edit/Ping Target Screen 2. Select the Boot Target option and press . 3. Select Primary or Secondary from the pop-up menu and press . 4.
PAGE 1682
12. Configuring UEFI for iSCSI Adding and Configuring Targets Selecting an Authentication Method The Emulex iSCSI configuration utility uses CHAP to authenticate initiators and targets for added network security. By using a challenge/response security mechanism, CHAP periodically verifies the initiator's identity. This authentication method depends on a secret known only to the initiator and the target.
PAGE 1683
12. Configuring UEFI for iSCSI Adding and Configuring Targets Note: When you configure the CHAP parameters, verify that those parameters match the parameters on the storage side. 4. Select Save/Login and press . Pinging a Target Note: If you want to verify that you can connect to a target before you log in, you must ping the target before you configure the target on the Edit/Ping Target screen. To ping a target: 1. On the iSCSI Target Configuration screen, select the target name and press .
PAGE 1684
12. Configuring UEFI for iSCSI Adding and Configuring Targets 2. From the Add/Ping iSCSI Target screen or the Edit/Ping Target screen, select Ping and press . If the ping is successful, a screen similar to the following is displayed. Figure 12-19 Successful Target Ping If the ping is not successful, a failure message is displayed. Viewing Advanced Properties To view advanced properties: 1. On the Edit/Ping Target screen (Figure 12-18), select Advanced Properties and press .
PAGE 1685
12. Configuring UEFI for iSCSI Adding and Configuring Targets Note: You may need to select ..more to display additional configuration options. Figure 12-20 Advanced iSCSI Target Information Screen Logging In or Logging Out of a Target To log in or out of a target: 1. On the Edit/Ping Target screen (Figure 12-18), select Login or Logout to explicitly log in or log out of a target, and then press . Note: You may need to select ..more to display additional configuration options.
PAGE 1686
12. Configuring UEFI for iSCSI Adding and Configuring Targets Configuring LUNs To configure LUNs: 1. On the Edit/Ping Target screen (Figure 12-18), select LUN Configuration and press . The LUN Configuration screen is displayed. Note: You may need to select ..more to display additional configuration options. Figure 12-21 LUN Configuration Screen 2. If the target is a boot target, select any single LUN as a boot LUN using the bar.
PAGE 1687
12. Configuring UEFI for iSCSI Adding and Configuring Targets iSNS Configuration Note: This functionality is only available on UEFI-capable HP adapters. The Internet Storage Name Service (iSNS) Protocol allows automated discovery, management and configuration of iSCSI and FC devices (using iFCP gateways) on a TCP/IP network. To view the iSNS Configuration screen: 1. On the Controller Configuration menu (Figure 12-2), select iSCSI Target Configuration and press .
PAGE 1688
12. Configuring UEFI for iSCSI Adding and Configuring Targets Enabling iSNS Discovery This option enables or disables iSNS discovery. iSNS targets are only discovered when this option is enabled. To enable or disable iSNS discovery: 1. From the iSNS Configuration screen, select iSNS Discovery Mode and press . Figure 12-24 iSNS Discovery Mode Screen 2. Select either Enable or Disable and press . 3. Select Save Changes and press to save the current settings.
PAGE 1689
12. Configuring UEFI for iSCSI Adding and Configuring Targets Figure 12-25 iSNS Server Discovery via DHCP Screen 2. Select either Enable or Disable and press . 3. Select Save Changes and press to save the current settings. Configuring the iSNS Server IP Address and TCP Port Number Manually An iSNS server can also be configured manually by entering the server IP address and the TCP port. Only one iSNS server can be configured at present.
PAGE 1690
12. Configuring UEFI for iSCSI Adding and Configuring Targets Figure 12-26 iSNS Server IP Screen 2. Enter the iSNS server’s IP address and press . 3. Select iSNS TCP Port and press . The default iSNS Port is 3205. The valid range is 1024–65535. 4. Select Save Changes and press to save the current settings. The added server is displayed under the Available Servers list. Figure 12-27 Available Servers Screen Boot Version 10.
PAGE 1691
12. Configuring UEFI for iSCSI Adding and Configuring Targets Discovering Targets Using the iSNS Server To configure targets using the iSNS server, from the iSNS Configuration screen (Figure 12-22), select the iSNS server under the Available Servers list and press . Figure 12-28 iSNS Server Options Screen The iSNS server IP and TCP port information is displayed.
PAGE 1692
12. Configuring UEFI for iSCSI Erasing the Configuration Erasing the Configuration Erase Configuration erases the configuration of a single controller. Configuration data is erased for both ports on the selected controller. Erase configuration restores the default settings only for that particular controller. When an initiator name is global for all adapters, the IQN configured on the first adapter is reflected on all controllers.
PAGE 1693
13. Configuring UEFI for FCoE Overview 13. Configuring UEFI for FCoE Note: If you have several adapters in your system, the UEFI system firmware or boot code uses the highest version driver installed on any of the adapters. Adapters with older versions of EFIBoot are managed by the more recent version, but only as long as the adapter with the most recent version is in the system.
PAGE 1694
13. Configuring UEFI for FCoE Starting the Emulex FCoE Configuration Utility  Select Back to Display Adapters and RECONNECT DEVICES from the Emulex Adapter Configuration Main Menu when you are finished to ensure the changes are made active; otherwise, a system restart is required to make your changes active.You are then returned to the adapter list.
PAGE 1695
13. Configuring UEFI for FCoE Updating Firmware and Boot Code The Emulex Adapter Configuration Main Menu is displayed. Figure 13-3 Emulex Adapter Configuration Main Menu Note: The DCBX mode is always set to CEE and cannot be configured. Updating Firmware and Boot Code To update the firmware and boot code to the latest versions, you must use the NIC firmware update utility, which revises the FCoE function with a single firmware and boot code image.
PAGE 1696
13. Configuring UEFI for FCoE Configuring CEE FCF Parameters Configuring CEE FCF Parameters To configure CEE FCF parameters: 1. From the Device Manager screen (Figure 13-2), select the adapter to configure and press . 2. From the Emulex Adapter Configuration Main Menu (Figure 13-3), select Configure CEE FCF Parameters and press . A listing of current CEE FCF record information is displayed. Figure 13-4 CEE Record Selection List Boot Version 10.
PAGE 1697
13. Configuring UEFI for FCoE Configuring CEE FCF Parameters 3. Select the CEE FCF record to modify and press . The current record information is displayed. Figure 13-5 CEE FCF Record Information 4. Change the record information as needed.  Set Record State can be set to unused, active, or boot.  VLAN ID must be a three digit hexadecimal number.  Switch Name (Low). Enter the low bits of the FC switch’s WWN to which to connect. This must be an 8-digit hexadecimal number.  Switch Name (Hi).
PAGE 1698
13. Configuring UEFI for FCoE Scanning for Fibre Devices Scanning for Fibre Devices When LUNs are set up on the SAN before POST has completed (that is, before the boot driver has been started), you can select 'Scan for Fibre Devices' or 'Add Boot Device' to discover all available LUNs. Although this procedure does not perform a complete HBA initialization, it executes faster than selecting “Reconnect Devices”.
PAGE 1699
13. Configuring UEFI for FCoE Adding Boot Devices 2. From the Emulex Adapter Configuration Main Menu (Figure 13-3), select Add Boot Device and press . Discovered targets are displayed. Figure 13-6 SAN Discovery Targets List 3. Select a target and press . 4. Select a LUN from the list and press . The target list is displayed. Figure 13-7 LUN Listing Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1700
13. Configuring UEFI for FCoE Deleting Boot Devices 5. Select Commit Changes and press . The Emulex Adapter Configuration Main Menu is displayed. Figure 13-8 Commit/Discard Change Deleting Boot Devices To delete boot devices: 1. From the Device Manager screen (Figure 13-2), select the adapter from which you want to delete a boot device and press . 2. From the Emulex Adapter Configuration Main Menu (Figure 13-3), select Delete Boot Device and press .
PAGE 1701
13. Configuring UEFI for FCoE Changing Boot Device Order 3. Select the device and press . The Delete Boot Device menu for that device is displayed. Figure 13-9 Delete Boot Device Screen 4. Select either KEEP or DELETE and press . 5. Select Commit Changes and press . The Emulex Adapter Configuration Main Menu is displayed. Changing Boot Device Order Note: The boot device order has no relationship to the system BIOS boot device order.
PAGE 1702
13. Configuring UEFI for FCoE Changing Boot Device Order 3. Select Boot Device Order and press . Figure 13-10 Change Boot Device Order Screen 4. Select a device from the list of eight boot devices and press . Figure 13-11 Boot Device Order Screen Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1703
13. Configuring UEFI for FCoE Changing Boot Device Order 5. Use the <+> or <-> keys to change the order of the selected device on the dialog box and press . A screen shows the new boot device order. Figure 13-12 Change Boot Device Order Screen 6. Verify that the boot device list order is correct. Press . Figure 13-13 Change Boot Device Order Screen with Revised Boot Order Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1704
13. Configuring UEFI for FCoE Configuring Adapter Parameters 7. Select Commit Changes and press . The revised order is saved to the NVRAM. The Emulex Adapter Configuration Main Menu is displayed. Figure 13-14 Change Boot Device Order 8. From the Emulex Adapter Configuration Main Menu, select Back to Display Adapters and RECONNECT DEVICES to complete configuration or select another configuration option.
PAGE 1705
13. Configuring UEFI for FCoE Configuring Adapter Parameters 2. From the Emulex Adapter Configuration Main Menu (Figure 13-3), select Configure HBA Parameters and press . The Configure HBA Parameters screen is displayed. 3. From the Configure HBA Parameters screen, select PLOGI Retry Timer and press . The PLOGI Retry Timer menu is displayed. Figure 13-15 PLOGI Retry Timer 4. Select a retry timer option and press . The screen is refreshed with the modified value.
PAGE 1706
13. Configuring UEFI for FCoE Configuring Adapter Parameters 3. From the Configure HBA Parameters screen, select Maximum LUNs/Target and press . Figure 13-16 Configure HBA Parameters – Maximum LUNs/Target Field 4. Type a decimal value between 1 and 4096 and press . The screen is refreshed with the modified value. Note: The default and typical maximum number of LUNs in a target device is 256. A higher number of maximum LUNs causes the discovery to take more time. 5.
PAGE 1707
13. Configuring UEFI for FCoE Configuring Adapter Parameters   EFIFCScanLevel: NVRAM Targets – Boot scan sets the EFIFCScanLevel environment variable to inform the driver to configure only targets in the NVRAM boot table. EFIFCScanLevel - Discovered Targets – Boot scan sets the EFIScanLevel environment variable to inform the driver to configure all available targets on the SAN. To change the boot target scan method: 1.
PAGE 1708
13. Configuring UEFI for FCoE Configuring Adapter Parameters Changing Device Discovery Delay This parameter sets a delay to occur after an loop initialization and before a scan is initiated to discover the target. The default is off or 0 seconds. Change the default if you have an HP MSA1000 or HP MSA1500 RAID array and if both of the following conditions exist:   The MSA array is direct connected or part of an arbitrated loop (for example, daisy chained with a JBOD).
PAGE 1709
13. Configuring UEFI for FCoE Resetting Emulex Adapters to Default Values 4. Use the +/- keys to change the delay device discovery value in increments of 10 seconds and press . The screen is refreshed with the modified value. 5. Select Commit Changes and press . The Emulex Adapter Configuration Main Menu is displayed.
PAGE 1710
13. Configuring UEFI for FCoE Resetting Emulex Adapters to Default Values Table 13-1 Adapter Default Values (Continued) Parameter Default Value Valid Values Bandwidth 0% Must have a total of 100% across all ports. LPVID 0 2–4094 Switch Option (IBM Virtual Fabric-capable configuration, if available) IBM Virtual Fabric Mode IBM Virtual Fabric Mode IBM Unified Fabric Protocol Mode Switch Independent Mode Note: The following example sets the default values for FC and FCoE adapters only.
PAGE 1711
13. Configuring UEFI for FCoE Displaying Adapter Information Displaying Adapter Information The Adapter Information screen shows the following information about the selected adapter:        Adapter status Network boot status Link speed Topology Firmware version – refer to this firmware version if reporting a problem to Emulex Technical Support Universal boot version EFI Boot version To display adapter information: 1.
PAGE 1712
14. Troubleshooting Troubleshooting for the NIC Protocol 14. Troubleshooting Troubleshooting for the NIC Protocol Issues During the PXE Boot Process Situation: If any of the following occur during the boot process:     The PXE boot ROM sends a DHCP request extended with PXE specific options, but the request is not received. The DHCP responses do not contain the DHCP options (DHCPOFFERs) that include the NBP filename and boot server lists.
PAGE 1713
14. Troubleshooting Troubleshooting for the NIC Protocol Table 14-1 PXE Error Codes (Continued) Error Codes Possible Reason Comment/Solution ARP/TFTP Error Codes PXE-E11:ARP timeout An ARP request is tried four times Check the DHCP server settings. If and the client did not receive an you are connected through a ARP reply. switch, also check the switch settings. PXE-E32: TFTP Open timeout.
PAGE 1714
14. Troubleshooting Troubleshooting for the NIC Protocol Table 14-1 PXE Error Codes (Continued) Error Codes Possible Reason PXE-E55: Proxy DHCP service The client issued a proxyDHCP did not reply to request on port request to the DHCP server on 4011. port 4011 but did not receive a reply. Comment/Solution Check that the DHCP server and TFTP server are properly configured on different servers. This issue may happen only when both are configured on separate servers.
PAGE 1715
14. Troubleshooting Troubleshooting for the iSCSI Protocol Table 14-1 PXE Error Codes (Continued) Error Codes Possible Reason PXE-E77: Bad or missing discovery server list. There are two possible reasons. One is that Multicast and Broadcast discovery are both disabled. The other is that Multicast and Broadcast are enabled, but the server list tag is not found or is invalid. Comment/Solution PXE-E78: Could not locate boot server.
PAGE 1716
14. Troubleshooting Troubleshooting for the iSCSI Protocol Table 14-2 Troubleshooting the iSCSISelect Utility (Continued) Issue Answer/Solution Unable to ping iSCSI target IP address • Check cable connections and make sure they are securely connected at both ends. Make sure the link light is ON at both ends of the cable. • Verify that you have assigned a valid IP address with the correct subnet mask to the interfaces that are connected to the network. • Check for duplicate IP addresses.
PAGE 1717
14. Troubleshooting Troubleshooting for the iSCSI Protocol Table 14-2 Troubleshooting the iSCSISelect Utility (Continued) Issue Answer/Solution Unable to boot from the iSCSI target. • Check the target setup. Check the target ACL to verify that the initiator's iSCSI name is listed and can be recognized. • Check the initiator name and make sure it is correct. • If applicable, verify that you have selected the iSCSI LUN as the boot LUN in your system BIOS setting.
PAGE 1718
14. Troubleshooting Troubleshooting for the FCoE Protocol Table 14-2 Troubleshooting the iSCSISelect Utility (Continued) Issue Answer/Solution You receive any of the following POST error messages or warnings: Redboot Initialization failed... Firmware Load failed... DDR config failed... DDR callibrate failed... DDR test failed... SEEPROM checksum failed... Secondary firmware image loaded...
PAGE 1719
Appendix A. Configuring iSCSI through a DHCP Server using Vendor-Specific Option 43 Overview Appendix A. Configuring iSCSI through a DHCP Server using Vendor-Specific Option 43 Overview An iSCSI initiator requires the following parameters to boot from a target:        Its IP address Its unique node name The boot iSCSI target’s IP address The boot target’s name. If not available, this may be discovered using the iSCSI discovery protocol.
PAGE 1720
Appendix A. Configuring iSCSI through a DHCP Server using Vendor-Specific Option 43 Format of Vendor-Specific Option 43 Replace this parameter with a decimal number indicating the TCP port. The default TCP port is 3260. Replace this parameter with a decimal number ranging from 1 to 65535 (inclusive). It is an optional field. This parameter is a hexadecimal representation of logical unit number of the boot device. It is an optional field.
PAGE 1721
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure PXE configuration requires a PXE server and the PXE client.
PAGE 1722
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure 7. The default file’s contents should look similar to the following: prompt 1 default linux timeout 100 label linux kernel vmlinuz append initrd=initrd.img ramdisk_size=9216 noapic acpi=off PXE Server NFS Server Configuration Script [root@bglinux156 ~]# mkdir /work [root@bglinux156 ~]# mount 10.192.194.
PAGE 1723
Appendix B.
PAGE 1724
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure flags = IPv4 } [root@bglinux156 ~]# /sbin/chkconfig --level 345 xinetd on [root@bglinux156 ~]# /sbin/chkconfig --level 345 tftp on [root@bglinux156 ~]# service xinetd restart DHCP Server Configuration 1. Install the following RPMs in the server if not installed: [root@bglinux156 ~]# rpm -qa | grep dhcp dhcpv6-client-1.0.10-18.el5 dhcp-devel-3.0.5-23.
PAGE 1725
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure Starting dhcpd: [ OK ] PXE Boot Server Configuration [root@bglinux156 ~]# rpm -qa | grep system-config-netboot system-config-netboot-cmd-0.1.45.1-1.el5 system-config-netboot-0.1.45.1-1.
PAGE 1726
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure 2. The Configure Network Installations window is displayed. Click Add. Figure B-2 Configure Network Installations Window 3. The Network Installation Dialog window is displayed. Figure B-3 Network Installation Dialog Window     Enter the operating system identifier and description. Select pxe as the protocol for installation.
PAGE 1727
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure The Network Installation and Diskless Environment window shows the IP address of the TFTP server. Figure B-4 Network Installation and Diskless Environment Window with IP Address Configuring the Host To configure the host: 1. Double-click on the IP address row in the Network Installation and Diskless Environment window (Figure B-4).
PAGE 1728
Appendix B. Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure 4. Select the operating system identifier to install on this client. The list is populated from the network install instances created from the Network Installation dialog box. 5. If you use a serial console, check the Serial Console check box. 6. Specify the location of a kickstart file, such as http://server.example.com/kickstart/ks.cfg.
PAGE 1729
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for SLES11 SPx Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for SLES11 SPx [root@orleansrhel5564 ~]# ls /root/sles11sp164/ SLES-11-SP1-DVD-x86_64-GM-DVD1.iso [root@orleansrhel5564 ~]# mkdir test1 [root@orleansrhel5564 ~]# mkdir test2 [root@orleansrhel5564 ~]# mount -o loop sles11sp164/SLES-11-SP1-DVD-x86_64-GM-DVD1.
PAGE 1730
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for SLES11 SPx NFS Server Configuration Script [root@bglinux156 ~]# /etc/rc.d/init.d/portmap restart Stopping portmap: [ OK ] Starting portmap: [ OK ] [root@bglinux156 ~]# /etc/rc.d/init.d/nfslock restart Stopping NFS locking: [ OK ] Stopping NFS statd: [ OK ] Starting NFS statd: [ OK ] [root@bglinux156 ~]# /etc/rc.d/init.
PAGE 1731
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for SLES11 SPx 100005 1 tcp 831 mountd 100005 2 udp 828 mountd 100005 2 tcp 831 mountd 100005 3 udp 828 mountd DHCP Server Configuration [root@orleansrhel5564 ~]# cat /etc/dhcpd.conf 1. Install the following RPMs in the server if not installed: [root@bglinux156 ~]# rpm -qa | grep dhcp dhcpv6-client-1.0.10-18.el5 dhcp-devel-3.0.5-23.el5 dhcp-3.0.5-23.el5 2. Make the following entry in /etc/dhcpd.
PAGE 1732
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for RHEL 6.x ###Address to match that of the NIC in the client box ###The IP address that follows the next-server option should be the IP ###address of the tftp server [root@bglinux156 ~]# service dhcpd restart Shutting down dhcpd: [ OK ] Starting dhcpd: [ OK ] TFTP Server Setup [root@orleansrhel5564 ~]# cat /etc/xinetd.
PAGE 1733
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for RHEL 6.
PAGE 1734
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for RHEL 6.x server server_args per_source cps flags = = = = = /usr/sbin/in.
PAGE 1735
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for RHEL 6.x initrd /initrd.im Configuring DHCP [root@orleans ~]# cat /etc/dhcpd.conf # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample ddns-update-style interim; ignore client-updates; #allow booting; #allow bootp; subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.50 192.168.1.90; default-lease-time 3600; max-lease-time 4800; option subnet-mask 255.255.255.
PAGE 1736
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ Configuring the IBM HS22 Blade with e-Raptor MEZZ To install and update the driver, follow these steps: 1. Press during the system boot and log into the System Configuration and Boot Management screen. Figure C-1 System Configuration and Boot Management Screen Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1737
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 2. Select Boot Manager and press . The Boot Manager screen is displayed. Figure C-2 Boot Manager Screen Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1738
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 3. Select Boot from File and press . The File Explorer screen is displayed. Figure C-3 File Explorer Screen 4. Select the card from which the UEFI NIC boot is to be performed. Press . A message similar to the following is displayed. Figure C-4 ELILO Boot Message Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1739
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 5. The Language Selection menu is displayed. Select a language and click OK. Figure C-5 Language Selection Menu 6. The Main menu is displayed. Select Expert and click OK. Figure C-6 Main Menu Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1740
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 7. The Expert menu is displayed. Select Kernel Modules (Hardware Drivers) and click OK. Figure C-7 Expert Menu 8. The Kernel Modules (Hardware Drivers) menu is displayed. Select Add Driver Update and click OK. Figure C-8 Kernel Modules (Hardware Drivers) Menu Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1741
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 9. The Driver Update Medium Selection listing is displayed. Select a medium and click OK. Figure C-9 Driver Update Medium Selection Listing 10. The Driver Update List confirmation dialog box is displayed. Click OK. Figure C-10 Driver Update List Dialog Box 11. The Expert menu (Figure C-7) is displayed. Click Back. 12. The Main menu (Figure C-6) is displayed.
PAGE 1742
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 14. The Network Protocol Selection menu is displayed. Select NFS and click OK. Figure C-12 Network Protocol Selection Menu 15. The Network Device Selection listing is displayed. Select the device and click OK. Figure C-13 Network Device Selection Listing 16. The DHCP request is sent. A dialog box prompts you to enter the IP address of the NFS server.
PAGE 1743
Appendix C. Examples for Configuring and Booting UEFI NIC Configuring the IBM HS22 Blade with e-Raptor MEZZ 17. Enter the IP address and press . A dialog box prompts you to enter the directory path of the server. Figure C-15 Server Directory Dialog Box 18. Enter the directory path and press . Information similar to the following is displayed. Figure C-16 Starting Script Figure C-17 Driver Update Confirmation Boot Version 10.
PAGE 1744
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 Setup Information PXE server: CISCO UCS C240 with SLES11 SP2 operating system PXE client server: DELL R620 Server F6PCP adapter installed PXE Server Setup Launch ‘yast2’ Configure Network Adapter 1. In the Network Devices section, select Network Settings. 2. Select the adapter port you wish the PXE server to use, then click Edit. 3.
PAGE 1745
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 Configure DHCPD6 Brussels-sles11sp2:~ # vim /etc/dhcpd6.conf default-lease-time 2592000; preferred-lifetime 604800; option dhcp-renewal-time 3600; option dhcp-rebinding-time 7200; allow leasequery; option dhcp6.name-servers fc00:ba49:1625:fb0f::1; option dhcp6.domain-search "pxetest.org"; option dhcp6.info-refresh-time 21600; option dhcp6.
PAGE 1746
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 Configure ELILO Boot Loader Retrieve ELILO from the installation DVD and create a configuration file: 1. Place the first SUSE Linux Enterprise Server install DVD in your DVD drive of the PXE Server. 2. Open a root terminal. 3. Mount the boot image and copy the contents.
PAGE 1747
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 # sites. However, some broken FTP clients such as "ncftp" and "mirror" assume # the presence of the "-R" option, so there is a strong case for enabling it. # #ls_recurse_enable=YES # # You may specify a file of disallowed anonymous e-mail addresses. Apparently # useful for combatting certain DoS attacks. # #deny_email_enable=YES # # (default follows) # #banned_email_file=/etc/vsftpd.
PAGE 1748
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 #local_max_rate=7200 # Anonymus FTP user Settings # # Allow anonymous FTP? # anonymous_enable=YES # # Anonymous users will only be allowed to download files which are # world readable. # anon_world_readable_only=YES # # Uncomment this to allow the anonymous FTP user to upload files. This only # has an effect if the above global write enable is activated.
PAGE 1749
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 # syslog_enable=YES # # Uncomment this to log all FTP requests and responses. # #log_ftp_protocol=YES # # Activate logging of uploads/downloads. # #xferlog_enable=YES # # You may override where the log file goes if you like. The default is shown # below. # #vsftpd_log_file=/var/log/vsftpd.log # # If you want, you can have your log file in standard ftpd xferlog format.
PAGE 1750
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 # # Enable this and the server will recognise asynchronous ABOR requests. Not # recommended for security (the code is non-trivial). Not enabling it, # however, may confuse older FTP clients. # #async_abor_enable=YES # # By default the server will pretend to allow ASCII mode but in fact ignore # the request.
PAGE 1751
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 write_enable=YES listen=NO listen_ipv6=YES Restart the Necessary Services Service Service Service Service nfsserver restart xinetd restart vsftpd restart dhcpd6 restart PXE Client Setup To set up the PXE client: 1. 2. 3. 4. 5. Boot the server and press to enter system setup. Select System BIOS Settings > Boot Settings and change boot mode to UEFI. Reboot the server.
PAGE 1752
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 7. Press and enter the UEFI boot manager. The Boot Manager Main Menu is displayed. Figure C-19 Boot Manager Main Menu Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1753
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 8. Select UEFI Boot Menu. The UEFI Boot Menu is displayed. Figure C-20 UEFI Boot Menu 9. Select Boot From File. The File Explorer screen is displayed. Figure C-21 File Explorer Screen Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1754
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 10. Select the port on the client through which PXE boot must be performed and press . A status message is displayed and then the Language Selection menu is displayed. Figure C-22 Language Selection Menu 11. Select a language and click OK. The Main Menu is displayed. Figure C-23 Main Menu Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1755
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 12. Select Expert and click OK. The Expert menu is displayed. Figure C-24 Expert Menu 13. Select Kernel Modules (Hardware Drivers) and click OK. The Kernel Modules (Hardware Drivers) menu is displayed. Figure C-25 Kernel Modules (Hardware Drivers) Menu Boot Version 10.2 for NIC, iSCSI, FCoE, and RoCE Protocols User Manual P010097-01B Rev.
PAGE 1756
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 14. Select Add Driver Update and click OK. The Driver Update Medium Selection list is displayed. Figure C-26 Driver Update Medium Selection List 15. Select a medium from the list and click OK. The Expert menu (Figure C-24) is displayed. 16. Click Back. The Main Menu (Figure C-23) is displayed. 17. Select Start Installation and click OK. The Source Medium list is displayed.
PAGE 1757
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 18. Select Network and click OK. The Network Protocol list is displayed. Figure C-28 Network Protocol List 19. Select FTP and click OK. The Network Device list is displayed. Figure C-29 Network Device List 20. Select the device and click OK. A dialog box prompts you for automatic configuration via DHCP. Figure C-30 Automatic Configuration via DHCP Dialog Box Boot Version 10.
PAGE 1758
Appendix C. Examples for Configuring and Booting UEFI NIC UEFI NIC IPv6 PXE Setup Procedure for SLES11 SP2 21. Click Yes. The DHCP6 request is sent. A dialog box prompts you to enter the IPv6 address of the FTP server. Figure C-31 FTP Server IPv6 Address Dialog Box 22. Enter the IPv6 address and press . A dialog box prompts you to enter the directory path of the server. Figure C-32 Server Directory Path Dialog Box 23. Enter the server’s directory path and press .
PAGE 1759
Appendix D. Example for Installing and Booting UEFI FCoE Appendix D. Example for Installing and Booting UEFI FCoE The following steps use the Linux SLES operating system as an example. 1. Boot to UEFI linux from DVD. 2. Select UEFI boot from the BIOS boot manager or boot to shell and execute /efi/boot/elilo.efi from removable media. 3. Follow normal boot instructions from YaST. 4. During the Installation Settings, select Partitioning, then select Custom partitioning (for experts). 5.
PAGE 1760
Appendix D. Example for Installing and Booting UEFI FCoE 10. To add an UEFI system partition (VFAT or FAT), click Add. 11. Select a custom size (100-400MB) depending on what EFI driver and utilities you want to store on the UEFI system partition. In general, using 200 MB is sufficient if the plug-in card detail for UEFI system partition is unknown. 12. In the Formatting options dialog box, select Format Partition > File system > FAT. 13. Under Mounting options, select /boot/efi and click Finish.
PAGE 1761
Appendix E. Loading and Unloading UEFIBoot from the UEFI Shell Loading UEFIBoot from the UEFI Shell Appendix E. Loading and Unloading UEFIBoot from the UEFI Shell Loading UEFIBoot from the UEFI Shell The UEFI boot code is distributed with the firmware in a .UFI file. This file may be downloaded to a NIC, iSCSI, or FCoE adapter through the HII interface in the NIC UEFI code. Unloading UEFIBoot from the UEFI Shell To unload UEFIBoot: 1.
PAGE 1762
Appendix F. Dell UEFI Accessing the Main Configuration Page Appendix F. Dell UEFI The following sections define and describe the fields and configuration settings for Dell adapters using the Dell UEFI utility. The Dell UEFI adapter configuration utility is a unified configuration utility that enables you to configure all of the available protocols through a single GUI interface, unlike individual configuration utilities.
PAGE 1763
Appendix F. Dell UEFI Main Configuration Page Main Configuration Page This page displays device information and enables you to configure device parameters. Figure F-2 Main Configuration Page Table F-1 Main Configuration Page Menu Options Menu Option Description and Available Settings Firmware Image Properties View adapter firmware version information. See “Firmware Image Properties Page” on page 1765 for more information. FCoE Configuration Configure FCoE boot parameters.
PAGE 1764
Appendix F. Dell UEFI Main Configuration Page Table F-1 Main Configuration Page Menu Options (Continued) Menu Option Description and Available Settings Virtualization Mode Specify the virtualization mode setting of the adapter. Available settings include: • None (default) • NPar • SR-IOV Note: Some menu options are not available when the Virtualization Mode is set to “None”. NIC Mode Always enabled. Blink LEDs Identify the physical port by blinking the port LED for up to 15 seconds.
PAGE 1765
Appendix F. Dell UEFI Main Configuration Page Firmware Image Properties Page This page displays adapter firmware version information. Figure F-3 Firmware Image Properties Page Table F-2 Firmware Image Properties Page Menu Options Menu Option Description and Available Settings Family Firmware Version Firmware version information for the installed adapter. Controller BIOS Version BIOS version information for the installed adapter. EFI Version EFI driver version information for the installed adapter.
PAGE 1766
Appendix F. Dell UEFI Main Configuration Page FCoE Configuration Page This page allows you to configure FCoE boot parameters. Figure F-4 FCoE Configuration Page Table F-3 FCoE Configuration Page Menu Options Menu Option Description and Available Settings FCoE General Parameters Configure FCoE general parameters. See “FCoE General Parameters Page” on page 1767 for more information. World Wide Port Name Target The first FCoE storage target’s WWPN.
PAGE 1767
Appendix F. Dell UEFI Main Configuration Page FCoE General Parameters Page This page allows you to configure FCoE general parameters. Figure F-5 FCoE General Parameters Page Table F-4 FCoE General Parameters Page Menu Options Menu Option Description and Available Settings Link Up Delay Time Specify how long (in seconds) the FCoE Initiator waits after an Ethernet link is established before sending any data over the network. The valid range is 0–255 seconds.
PAGE 1768
Appendix F. Dell UEFI Main Configuration Page Table F-4 FCoE General Parameters Page Menu Options (Continued) Menu Option Description and Available Settings Boot Scan Selection Specify the adapter’s initiator behavior for booting the system from specified FC boot targets or fabric discovered targets. Available settings include: • Disabled (default) – Initiator does not attempt to boot. • First LUN – Attempt boot from the first bootable LUN of the targets discovered by adapter.
PAGE 1769
Appendix F. Dell UEFI Main Configuration Page NIC Configuration Page This page allows you to configure the boot protocol, Wake on LAN, link speed, and VLAN. Figure F-6 NIC Configuration Page Table F-5 NIC Configuration Page Menu Options Menu Option Description and Available Settings Legacy Boot Protocol Select a non-UEFI network boot protocol. Available settings include: • PXE • iSCSI • FCoE • None (default) Wake On LAN Enable or disable Wake On LAN.
PAGE 1770
Appendix F. Dell UEFI Main Configuration Page Table F-5 NIC Configuration Page Menu Options (Continued) Menu Option Description and Available Settings Link Speed Specify the port speed used for the selected protocol. Available settings include: • Auto Negotiated (default) • 1 Gbps • 10 Gbps Option ROM Enable or disable legacy boot protocols in the Option ROM.
PAGE 1771
Appendix F. Dell UEFI Main Configuration Page iSCSI Configuration Page This page allows you to configure general, initiator, and target parameters for iSCSI boot. Figure F-7 iSCSI Configuration Page Table F-6 iSCSI Configuration Page Menu Options Menu Option Description and Available Settings iSCSI General Parameters Configure general iSCSI parameters. See “iSCSI General Parameters Page” on page 1772 for more information. iSCSI Initiator Parameters Configures iSCSI initiator parameters.
PAGE 1772
Appendix F. Dell UEFI Main Configuration Page iSCSI General Parameters Page This page allows you to configure the general iSCSI parameters. Figure F-8 iSCSI General Parameters Page Table F-7 iSCSI General Parameters Page Menu Options Menu Option Description and Available Settings TCP/IP Parameters via DHCP Control the source of the initiator IP address: DHCP or static assignment. Available settings include: • Enabled • Disabled (default) Note: This option is specific to IPv4.
PAGE 1773
Appendix F. Dell UEFI Main Configuration Page Table F-7 iSCSI General Parameters Page Menu Options (Continued) Menu Option Description and Available Settings CHAP Authentication Enable the ability of the initiator to use CHAP authentication when connecting to the iSCSI target. Available settings include: • Enabled • Disabled (default) CHAP Mutual Authentication Setting to enable mutual CHAP authentication between the iSCSI initiator and target.
PAGE 1774
Appendix F. Dell UEFI Main Configuration Page iSCSI Initiator Parameters Page This page allows you to configure the iSCSI initiator parameters. Figure F-9 iSCSI Initiator Parameters Page Table F-8 iSCSI Initiator Parameters Page Menu Options Menu Option Description and Available Settings IP Address Specify the iSCSI initiator’s IP address. The value should be in either IPv4 or IPv6 format and can be 2–39 characters long. IPv4 Address Specify the iSCSI initiator’s IPv4 address.
PAGE 1775
Appendix F. Dell UEFI Main Configuration Page Table F-8 iSCSI Initiator Parameters Page Menu Options (Continued) Menu Option Description and Available Settings CHAP ID Specify the initiator CHAP ID. The valid range is 0–128 characters in length. If this can be set on a per target basis, then the first target value must be stored here. CHAP Secret Specify the ISCSI initiator’s CHAP Secret. The valid range is 0 or 12–16 characters in length.
PAGE 1776
Appendix F. Dell UEFI Main Configuration Page Table F-9 iSCSI First Target Parameters Page Menu Options (Continued) Menu Option Description and Available Settings Boot LUN Specify the first iSCSI storage target’s boot LUN. The valid range is 0–18446744073709551615. iSCSI Name Specify the first iSCSI storage target’s initiator IQN. The valid range is 0–223 characters. CHAP ID Specify the first ISCSI storage target’s CHAP ID. The valid range is 0–128 characters in length.
PAGE 1777
Appendix F. Dell UEFI Main Configuration Page iSCSI Second Target Parameters Page This page allows you to enable a connection for the second iSCSI target and configure parameters. Figure F-11 iSCSI Second Target Parameters Page Table F-10 iSCSI Second Target Parameters Page Menu Options Menu Option Description and Available Settings Connect Enable connecting to the second iSCSI target. Available settings include: • Enabled • Disabled (default) IP Address Specify the second target’s IP address.
PAGE 1778
Appendix F. Dell UEFI Main Configuration Page Table F-10 iSCSI Second Target Parameters Page Menu Options (Continued) Menu Option Description and Available Settings IP Version Control whether IPv4 or IPv6 network addressing is used for the second iSCSI target. Available settings include: • IPv4 (default) • IPv6 iSCSI Secondary Device Parameters Page This page allows you to configure the MAC address for a secondary iSCSI boot adapter.
PAGE 1779
Appendix F. Dell UEFI Main Configuration Page Device Level Configuration Page This page displays the global device level parameters and allows you to configure them. Figure F-13 Device Level Configuration Page Table F-12 Device Level Configuration Page Menu Options Menu Option Description and Available Settings Flow Control Setting Configure the type of flow control used by the adapter.
PAGE 1780
Appendix F. Dell UEFI Main Configuration Page Table F-12 Device Level Configuration Page Menu Options (Continued) Menu Option Description and Available Settings PCI Virtual Functions Advertised The number of PCI VFs to be advertised on this port in non-NPar mode. The valid range is 0–256. This value varies based on the adapter in use. NIC Partitioning Configuration Page This page displays NIC partition information and allows you to configure their functionality.
PAGE 1781
Appendix F. Dell UEFI Main Configuration Page Global Bandwidth Allocation Page This page allows you to configure the TX bandwidth allocation across enabled partitions on the port. Figure F-15 Global Bandwidth Allocation Page Table F-14 Global Bandwidth Allocation Page Menu Options Menu Option Description and Available Settings Partition n Minimum TX Bandwidth The minimum transmit bandwidth value is the least amount of bandwidth that the partition can provide. It is represented as a percentage.
PAGE 1782
Appendix F. Dell UEFI Main Configuration Page Partition Configuration Page This page displays information for a particular partition and allows you to configure some partition parameters. There is a separate page for each available partition. Note: There can be only one storage function on each port. Once a storage function is enabled on a partition, the storage protocols appear as unavailable on the other partitions.
PAGE 1783
Appendix F. Dell UEFI Main Configuration Page Table F-15 Partition Configuration Page Menu Options (Continued) Menu Option Description and Available Settings PCI Address The PCI address for the partition. This value is assigned by the system BIOS. MAC Address The permanent MAC address assigned at the factory. iSCSI Offload MAC Address The permanent MAC address for iSCSI offload assigned at the factory. FIP MAC Address The permanent FIP-MAC address for FCoE assigned at the factory.
PAGE 1784
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems Running the PXESelect Utility Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems This section describes how to use the PXESelect utility to set up a PXE bootable network by configuring your Dell OCe10100-based controllers. Note: For Dell OCe14000-based adapters, see appendix H., “Configuring PXE Boot for NIC on Dell OCe14000-based Systems,” on page 1791.
PAGE 1785
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems Setting Up a PXE Bootable Network  Press to return to the previous menu or page, cancel a selection or dialog box, or exit the utility. Setting Up a PXE Bootable Network After the PXE boot BIOS initializes, you can use the PXESelect utility to set up a PXE bootable network by configuring your controllers. To configure controllers for PXE boot: 1.
PAGE 1786
Appendix G.
PAGE 1787
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems Setting Up a PXE Bootable Network Configuring PXE Boot Support To configure PXE boot support: 1. On the configuration screen, use the key to select the PXE Boot Support setting and a pop-up menu appears. 2. Select Enabled or Disabled and press . 3. Select Save and press . Note: During system startup, PXE contacts the DHCP server for an IP address to boot from the network.
PAGE 1788
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems Setting Up a PXE Bootable Network Configuring SR-IOV If your system BIOS supports SR-IOV, you can enable it. For more information on SR-IOV configuration, see the appropriate Emulex driver manual. 1. On the configuration screen, use the key to select the SR-IOV setting and a pop-up menu appears. 2. Select Enabled or Disabled and press . 3. Select Save and press .
PAGE 1789
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems Setting Up a PXE Bootable Network 2. The LEDs on your controller begin blinking. The selected port’s LED status indicators blink on your controller until you select Done on this screen and press . Note: Not all controllers have LEDs that are visible externally. If you are using an add-in card in a blade server environment, the port identification or beaconing capability does not work.
PAGE 1790
Appendix G. Configuring PXE Boot for NIC on Dell OCe10100-based Systems PXE Boot Parameters Default Values PXE Boot Parameters Default Values The default settings for the PXE Boot parameters are listed in the following table.
PAGE 1791
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Running the PXESelect Utility Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems This section describes how to use the PXESelect utility to set up a PXE bootable network by configuring your Dell OCe14000-based controllers. Note: For Dell adapter models D6T93, F6PCP, JJPC0, and P3V42, PXE boot can be performed only on the first NIC partition on each port in the legacy x86 BIOS.
PAGE 1792
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network     Press the left or right arrows on your keyboard to move through and select setting options. Press to accept a selection, select a menu option, or to change a configuration default. Press to save the changes on the screen. Press to return to the previous menu or page, cancel a selection or dialog box, or exit the utility.
PAGE 1793
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network For additional information on NPar support, see “Configuring NPar” on page 1794. SRIOV – if your system BIOS supports SR-IOV, you can select this virtualization mode. SR-IOV support can only be enabled when NPar support is disabled. For more information on SR-IOV configuration, see the appropriate Emulex driver manual.
PAGE 1794
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network Select the desired configuration option and press . Figure H-4 Port Menu Configuring NPar NPar support provides the ability to configure multiple physical functions or I/O partitions for each physical adapter port. Notes:   The settings in this menu can only be configured when the virtualization mode is set to “NPar”. Otherwise, the settings in this menu are for display purposes only.
PAGE 1795
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network 2. Select the partition you want to configure and press . The Configure Partition screen appears. Figure H-6 Configure Partition Screen 3. From the Configure Partition screen, you can perform the following tasks:  View the function number.  Select the protocol for each function, except for PF #0 and PF #1.
PAGE 1796
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network Note: Changing the protocol setting requires a reboot before the change will take effect. A reboot will occur when you exit the PXESelect utility if the protocol selection has changed since the last boot. Configuring Minimum and Maximum Bandwidth To configure bandwidth: 1.
PAGE 1797
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network If these conditions are not met, you may be able to configure more than eight functions, but only up to eight functions will be running and discovered after a reboot. To enable NParEP: 1. From Controller Configuration screen (Figure H-2), highlight the NParEP Support menu item. 2. Select Enabled and press to save.
PAGE 1798
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network  Configure the boot retry count – see “Configuring the Boot Retry Count” on page 1798 for instructions. Configuring PXE Boot Support To configure PXE boot support: 1. On the Boot Configuration screen, use the left or right arrow keys to enable or disable the PXE Boot setting. 2. Press to save.
PAGE 1799
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network Configuring Port Options To view the Port Configuration screen: 1. From Port Menu (Figure H-4), select 3. Port Configuration and press . The Port Configuration screen appears. Figure H-9 Port Configuration Screen 2. From the Configure Partition screen, you can perform the following tasks:  Set the configured port speed – see “Setting the Configured Port Speed” on page 1799 for instructions.
PAGE 1800
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems Setting Up a PXE Bootable Network Configuring Flow Control This setting allows you to configure the type of flow control used by the adapter. Note: Ethernet flow control cannot be changed when priority flow control is enabled on the switch ports and enabled in the firmware (through the OneCommand Manager application). To configure flow control: 1.
PAGE 1801
Appendix H. Configuring PXE Boot for NIC on Dell OCe14000-based Systems PXE Boot Parameters Default Values Erasing Ports and Controller Configuration Note: When selecting this setting, all previous configuration settings are returned to their factory default settings including the current protocol selection. Emulex recommends performing this action to provide a clean environment for new configuration settings to take effect. To erase the ports and controller configuration: 1.
PAGE 1802
Appendix H.
PAGE 1803
Appendix I. Booting the Solaris Operating System from the Network on SPARC Systems Appendix I. Booting the Solaris Operating System from the Network on SPARC Systems To boot the Solaris operating system from the network on SPARC systems: 1. Set up the Jumpstart server and automated install (AI) server. 2. Obtain the MAC address of the ELXNIC port used for the net boot:. a.
PAGE 1804
Appendix I. Booting the Solaris Operating System from the Network on SPARC Systems fcode-rom-offset vf-stride first-vf-offset total-vfs initial-vfs #vfs port-type interrupts cache-line-size class-code subsystem-id subsystem-vendor-id revision-id device-id vendor-id 0003c600 00000001 00000020 00000020 00000020 00000020 PCIE-Endpoint 00000001 00000010 00020000 0000e800 000010df 00000010 00000720 000010df 3. Add the MAC address from step 2 as an installation client to the install or boot server. 4.
PAGE 1805
Adapter Installation Manual P010288-01A Rev.
PAGE 1806
180 Copyright © 2014 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.
PAGE 1807
1. Introduction Adapter Identification 1. Introduction This manual describes how to install an Emulex adapter. Illustrations in this manual are only examples. The actual hardware may vary. Figure 1-1 Two Port Adapter Figure 1-2 Single Port Adapter Adapter Identification Each adapter ships with several numbers clearly marked on the board. Emulex recommends recording these numbers before installation.
PAGE 1808
1. Introduction Adapter Identification  Serial number – assigned by Emulex and used when communicating with Emulex Note: If the adapter has two ports, it has two IEEE addresses and two WWNs, one for each port. Emulex Adapter Installation Manual P010288-01A Rev.
PAGE 1809
2. Installation Preparing the Adapter for Installation 2. Installation The Emulex adapter can be connected to fiber optic cables (used with embedded optical transceivers) or DAC cables. Additional information for these cable connections and other installation procedures are described in the following sections. Preparing the Adapter for Installation Before installing the adapter, you should perform the following steps: 1. Turn off the computer and unplug it. 2. Remove the computer case.
PAGE 1810
2. Installation Preparing the Adapter for Installation Figure 2-2 Releasing the Latch on an Optical Transceiver 6. Observing Electrostatic Discharge (ESD) precautions, store the transceiver in an ESD-safe place. 7. Remove the mounting bracket screws from the top of the adapter. Figure 2-3 shows the screws that are removed from the bracket. Figure 2-3 Removing the Bracket 8. Remove the bracket and store it for future use. 9. Align the new mounting bracket tabs with the holes in the adapter.
PAGE 1811
2. Installation Installing the Adapter 11. Re-install the transceiver by sliding it into the housing. When the latch engages, it clicks. 12. Push the bail back into place. Installing the Adapter To install the adapter: 1. Turn off and unplug the computer. 2. Remove the computer case. 3. Remove the blank panel from an empty PCIe bus slot. See “Preparing the Adapter for Installation” on page 1809 to change the brackets if needed. Note: Place the adapter into an empty PCIe x8 or x16 slot.
PAGE 1812
2. Installation Attaching Devices Figure 2-4 Installing an Optical Transceiver Once the optical transceivers are installed, insert the optical cable into the LC connectors on the adapter (see Figure 2-5). Figure 2-5 Connecting a Fiber Optic Cable When connecting a DAC cable, ensure the SFP+ cages do not have optical transceivers installed in them. To remove optical transceivers, see step 5 on page 1809.
PAGE 1813
2. Installation Applying Power . Figure 2-6 Connecting a DAC Cable 2. After the appropriate cable is connected to the adapter, connect the other end of the cable to a suitable device, such as a Top of Rack (TOR) EE switch. After the device is connected to the adapter, you are ready to apply power to the computer. Applying Power To apply power: 1. 2. 3. 4. Verify that the adapter is securely installed in the computer. Verify that the correct device is attached. Plug in and turn on the computer.
PAGE 1814
2. Installation Viewing the LEDs Viewing the LEDs You can view green and yellow LEDs through openings in the adapter's mounting bracket. The green LED indicates firmware operation and the yellow LED indicates port activity or link speed. Each port has a corresponding set of green and yellow LEDs. Figure 2-7 LED Indicators Viewing the LEDs for Converged Network Adapters Each port connector has two LEDs: an amber LED and a green LED.
PAGE 1815
2. Installation Viewing the LEDs Note: For the Link Rate conditions, there is a 1 second pause when the LED is off between each group of fast blinks (2, 3, or 4). Observe the LED sequence for several seconds to be sure you have correctly identified the pattern.