Cover User’s Guide Fibre Channel Adapter QLE2660-DEL, QLE2662-DEL, QME2662-DEL, QLE2690-DEL, QLE2690L-DEL, QLE2692-DEL, QLE2692L-DEL, and QME2692-DEL Third party information brought to you courtesy of Dell. CU0354604-00 R October 28, 2019 Marvell.
User’s Guide Fibre Channel Adapter For more information, visit our website at: http://www.marvell.com Notice THIS DOCUMENT AND THE INFORMATION FURNISHED IN THIS DOCUMENT ARE PROVIDED “AS IS” WITHOUT ANY WARRANTY.
Table of Contents Introduction Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User’s Guide Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality and Features . . . . . . . . . . . . . . . . . . .
User’s Guide—Fibre Channel Adapter QLE266x-DEL, QLE269x-DEL, QLE269xL-DEL, and QME26x2-DEL Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installing the ESXi 6.7 U3 and 6.5 U3 Fibre Channel Driver . . . . . . . . 16 Updating an Existing Driver or Installing a New Driver for an Existing ESXi 6.7 U3 and 6.5 U3 Installation with esxcli . . . . . 16 Verifying the Version of the Installed Driver . . . . . . . . . . . . . . . .
User’s Guide—Fibre Channel Adapter QLE266x-DEL, QLE269x-DEL, QLE269xL-DEL, and QME26x2-DEL Setting Fibre Channel Adapter Parameters with Noninteractive QConvergeConsole CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring Target Persistent Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring Persistent Binding with QConvergeConsole GUI. . . . . . .
User’s Guide—Fibre Channel Adapter QLE266x-DEL, QLE269x-DEL, QLE269xL-DEL, and QME26x2-DEL Setting the FA-PWWN from the Adapter . . . . . . . . . . . . . . . . . . . . . . . 65 Setting FA-PWWN with QConvergeConsole GUI. . . . . . . . . . . . 66 Setting FA-PWWN with QConvergeConsole CLI . . . . . . . . . . . . 67 Setting FA-PWWN with QConvergeConsole VMware Plug-ins . 69 Setting the FA-PWWN from the Brocade Switch. . . . . . . . . . . . . . . . . 70 Setting the FA-PWWN from the Switch . . . . . . . . . . .
User’s Guide—Fibre Channel Adapter QLE266x-DEL, QLE269x-DEL, QLE269xL-DEL, and QME26x2-DEL Configuring CS_CTL QoS on the Storage Device. . . . . . . . . . . . . . . . Changing the QoS Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Priority Levels in Windows . . . . . . . . . . . . . . . . . . Changing the Priority Levels in VMware ESXi . . . . . . . . . . . . . . Configuring FDMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—Fibre Channel Adapter QLE266x-DEL, QLE269x-DEL, QLE269xL-DEL, and QME26x2-DEL Configuring D_Port on a Brocade Fibre Channel 16G Switch. . . . . . . Configuring and Running Diagnostics Port on a Cisco Fibre Channel 16 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking D_Port Results from a Brocade Fibre Channel 16G Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction This introductory chapter provides a list of the covered models, describes the intended audience and contents of this guide, lists related documents and the document conventions, describes the product functionality and features, and lists the supported OSs.
Introduction Intended Audience Intended Audience This guide is intended for system administrators and other technical staff members responsible for configuring and managing adapters installed on Dell® PowerEdge® servers in Windows®, Linux®, or VMware® environments.
Introduction Related Materials Related Materials For additional information, refer to the following QLogic documents: QConvergeConsole Help, available after installing QConvergeConsole GUI, provides help topics on configuring and managing host servers and adapters using QConvergeConsole GUI. Installation Guide—QConvergeConsole GUI (part number SN0051105-00) contains instructions for installing and starting QConvergeConsole GUI.
Introduction Documentation Conventions Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings. For example: Click Start, point to Programs, point to Accessories, and then click Command Prompt. Under Notification Options, select the Warning Alarms check box. Text in Courier font indicates a file name, directory path, or command line text. For example: Issue the following command: # sh ./install.
Introduction Functionality and Features [ ] (square brackets) indicate an optional parameter. For example: | (vertical bar) indicates mutually exclusive options; select one option only. For example: on|off 1|2|3|4 ... (ellipsis) indicates that the preceding item may be repeated. For example: [] means specify a file name, or omit it to select the default file name. x... means one or more instances of x. [x...] means zero or more instances of x.
Introduction Functionality and Features QLE2692-DEL: A low profile, Enhanced Gen 5 16Gb, dual-port Fibre Channel-to-PCIe adapter with a full-height bracket installed. QLE2692L-DEL: A low profile, Enhanced Gen 5 16Gb, dual-port Fibre Channel-to-PCIe adapter with a low profile bracket installed.
Introduction Functionality and Features Windows Server 2016 Windows Server 2012 R2 Red Hat® Enterprise Linux (RHEL®) 7.6 RHEL 7.7 RHEL 8.0 RHEL 8.1 SuSE® Linux Enterprise Server (SLES®) 12 SP4 SLES 15 SLES 15 SP1 vSphere®: VMware ESXi 6.5 U3 vSphere: VMware ESXi 6.7 U3 Citrix Hypervisor 8.0 Citrix® XenServer® 7.1 CU2 Red Hat SuSE VMware Citrix NOTE For the most current versions of the OS and drivers supported by the adapter, refer to the release notes file (release.
1 Hardware Installation This chapter provides the hardware and software requirements, safety precautions, a pre-installation checklist, PCIe slot considerations, and procedures for installing the adapter and connecting it to the network. Hardware and Software Requirements Before you install the adapter, verify that the system meets the following hardware and software requirements.
1–Hardware Installation Pre-Installation Checklist Before you touch internal components, verify that the system is powered OFF and is unplugged. Install or remove adapters in a static-free environment. The use of a properly grounded wrist strap or other personal anti-static devices and an anti-static mat is strongly recommended. Pre-Installation Checklist 1. Verify that your system meets the hardware and software requirements listed in “Hardware and Software Requirements” on page 1. 2.
1–Hardware Installation Installing the Adapter Table 1-2 lists the throughput needed to achieve line rates. Table 1-2. Throughput Requirements to Achieve Line Rate Number of 16G FC Ports 1 2 PCIe Throughput Required to Achieve Line Rate Minimum PCIe Gen and Slot Configurations QLE2660_DEL, QLE2690-DEL, QLE2690L-DEL 16GFC (1 16GFC) PCIe 2.0 x8 and higher QLE2662-DEL, QLE2692-DEL, QLE2692L-DEL, QME2692-DEL 32GFC (2 16GFC) Model Number PCIe 3.0 x8 and higher PCIe 2.0 x8 and higher PCIe 3.
1–Hardware Installation Connecting to the SAN QME2662-DEL and QME2692-DEL For installation instructions, refer to the “I/O Module Mezzanine Cards” and “Guidelines for Installing I/O Modules” sections of the Dell PowerEdge Modular Systems Hardware Owner’s Manual: ftp://ftp.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_poweredge/ poweredge-m610x_Owner%27s%20Manual_en-us.pdf Connecting to the SAN Follow the instructions for your adapter model number.
2 Driver Installation and Configuration NOTE If you need to update the Flash memory of multiple adapters simultaneously: For QConvergeConsole GUI, refer to the “Update the Flash Using the Flash Update Wizard” topic in the QConvergeConsole Help. For QConvergeConsole CLI, issue the -flashsupport command to update the Flash memory for all cards supported by the specified file. For example: qaucli -pr nic -flashsupport -i ALL -a p3p11179.
2–Driver Installation and Configuration Windows Driver Installation and Configuration Windows Driver Installation and Configuration NOTE If you are using the 2600 Series Adapters to boot from storage in a Windows Server 2008 R2/SP1 or Windows Server 2012 environment, your adapters may not recognize the storage targets and LUNs when you load the adapter driver the first time. For the adapter to recognize the storage and LUNs, you must load the adapter drivers a second time.
2–Driver Installation and Configuration Windows Driver Installation and Configuration 3. In the QLogic Super Installer—InstallShield® Wizard’s Welcome window (Figure 2-2), click Next. Figure 2-2. QLogic InstallShield Wizard: Welcome Window 4. In the wizard’s License Agreement window (Figure 2-3): a. Read the QLogic End User Software License Agreement. b. To continue, select I accept the terms in the license agreement. c. Click Next. Figure 2-3.
2–Driver Installation and Configuration Windows Driver Installation and Configuration 5. Complete the wizard’s Setup Type window (Figure 2-4) as follows: a. Select one of the following setup types: b. Click Complete to install all program features. Click Custom to manually select the features to be installed. To continue, click Next. If you selected Complete, proceed directly to Step 6 b. Figure 2-4. InstallShield Wizard: Setup Type Window 6.
2–Driver Installation and Configuration Windows Driver Installation and Configuration b. Click Next to continue. Figure 2-5. InstallShield Wizard: Custom Setup Window 7. In the InstallShield Wizard’s Ready To Install window (Figure 2-6), click Install. Figure 2-6.
2–Driver Installation and Configuration Windows Driver Installation and Configuration The InstallShield Wizard installs the QLogic Adapter drivers and Management Software Installer. 8. When the installation is complete, the InstallShield Wizard Completed window appears (Figure 2-7). Click Finish to dismiss the installer. Figure 2-7.
2–Driver Installation and Configuration Windows Driver Installation and Configuration 9. In the Dell Update Package (DUP) window (Figure 2-8), “Complete” indicates successful installation. (Optional) To open the log file, click View Log. The log file shows the progress of the DUP installation, any previous installed versions, any error messages, and other information about the installation. To close the Update Package window, click OK. Figure 2-8.
2–Driver Installation and Configuration Linux Driver Installation and Configuration Examples To update the system silently: .exe /s To extract the update contents to the C:\mydir\ directory: .exe /s /e=C:\mydir To extract the driver components to the C:\mydir\ directory: .exe /s /drivers=C:\mydir To install only the driver components: .exe /s /driveronly To change from the default log location to C:\my path with spaces\log.
2–Driver Installation and Configuration Linux Driver Installation and Configuration Installing the Linux Fibre Channel Driver This section provides procedures for installing the Linux Fibre Channel driver for the following operating systems: Building the Driver for RHEL 7.x and 8.x Building the Driver for SLES 12 SP4 and SLES 15/15 SP 1 Building the Driver for RHEL 7.x and 8.x 1. From the directory that contains the source driver file, qla2xxx-src.vx.xx.xx.xx.xx.x-k.tar.
2–Driver Installation and Configuration Linux Driver Installation and Configuration 4. (Optional) To automatically load the driver each time the system boots, rebuild the RAM disk to include the driver as follows: a. Create a backup copy of the RAMDISK image by issuing the following commands: # cd /boot # cp initramfs-[kernel version].img initramfs-[kernel version].img.bak b. Create the new RAMDISK by issuing the following command: # dracut -f c. To load the driver, reboot the host.
2–Driver Installation and Configuration VMware Driver Installation and Configuration 3. (Optional) Manually load the driver for Linux. Edit the /etc/modprobe.d/unsupported_modules file to make the following change: allow_unsupported_modules 1 (replace 0 with 1) To load the driver using modprobe, issue the following command: # modprobe -v qla2xxx To unload the driver using modprobe, issue the following command: # modprobe -r qla2xxx 4.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Installing the ESXi 6.7 U3 and 6.5 U3 Fibre Channel Driver The operating system manages and controls the driver installation process. To install the ESXi driver, follow the steps in this section. NOTE This section provides the most common ways of installing and upgrading the driver. For other installation procedures, consult the operating system manuals and the driver readme file.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Verifying the Version of the Installed Driver To verify the installed package in the system, issue the following command: esxcli software vib list | grep qlnativefc The driver version is embedded in the VIB version. For example, the output looks like the following: # esxcli software vib list | grep qlnativefc qlnativefc 2.1.50.0-1OEM.600.0.0.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Installation Package Contents The latest version of the QLogic Adapter CIM Provider and QConvergeConsole VMware vCenter Server Plug-in package contains the files needed to install both the Plug-in and the CIM Provider. Required files include the following (where x_x_x is the version number): QLogic_Adapter_VI_Plugin_x_x_x.exe—This file is the QConvergeConsole VMware vCenter Server Plug-in installation package.
2–Driver Installation and Configuration VMware Driver Installation and Configuration The InstallAnywhere wizard opens, as shown in Figure 2-9. Figure 2-9. InstallAnywhere Initial Window 3. In the QLogic Adapter VI Plug-in wizard’s Introduction window (see Figure 2-10), click Next. Figure 2-10.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Wait while the wizard configures the plug-in (see Figure 2-11). Figure 2-11. QLogic Adapter VI Plug-in Wizard: Configuring the Plug-in 4. Select the installation directory, and then click Install (see Figure 2-12). Figure 2-12.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Wait while the wizard performs the installation (see Figure 2-13). Figure 2-13.
2–Driver Installation and Configuration VMware Driver Installation and Configuration 5. Type the requested information in the boxes, and then click Next (see Figure 2-14). Figure 2-14. QLogic Adapter VI Plug-in Wizard: User Input Wait while the wizard finishes configuring the plug-in (see Figure 2-15). Figure 2-15.
2–Driver Installation and Configuration VMware Driver Installation and Configuration 6. When the Registration Result window (Figure 2-16) appears, click Finish to exit. Figure 2-16. QLogic Adapter VI Plug-in Wizard: Registration Result 7. After the installation completes, restart the Tomcat™ service as follows: If the plug-in is installed on the VMware vCenter Server, restart the VMware Virtual Center Management Web services.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Before you can use the script, you must download the appropriate VI SDK from VMware: For Perl VI SDK, download vSphere SDK for Perl: http://www.vmware.com/support/developer/viperltoolkit/ For PowerShell, download vSphere PowerCLI: http://communities.vmware.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Initial Installation Methods Initial installation methods for the CIM Provider include the following: Online. Refer to “Installing the CIM Provider on an ESXi 6.7 U3 or 6.5 U3 Host” on page 25. Offline. Refer to “Existing ESXi Installation Using VMware Update Manager” on page 25. Remote. Refer to “Remote Installation of the CIM Provider on an ESXi Host” on page 26. Installing the CIM Provider on an ESXi 6.
2–Driver Installation and Configuration VMware Driver Installation and Configuration To install the asynchronous drivers: 1. Extract the contents of the asynchronous driver zip file. 2. Identify the offline-bundle.zip file or files. 3. From vCenter Server, go to Home, and then select Update Manager. 4. Click the Patch Repository tab. 5. Click the Import Patches link at the top right of the window. 6. Click Finish. The asynchronous driver is now added to the patch repository. 7.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Subsequent Update Installation To update the QLogic Adapter CIM Provider after a prior VIB installation, follow the instructions in “Uninstalling the QLogic Adapter CIM Provider” on page 27 to remove the existing VIB. After completing the VIB removal, use the same steps in “Initial Installation Methods” on page 25 to install the new VIB.
2–Driver Installation and Configuration VMware Driver Installation and Configuration To uninstall the CIM Provider from a remote host: NOTE Before performing this procedure, make sure that the ESXi system is in Maintenance Mode. To do so using the vSphere Client, select Inventory, select Host, and then select Enter Maintenance Mode. 1. From a console on the host where the vSphere CLI package is installed or vMA is hosted, query and find the Bulletin ID of the existing provider: # vihostupdate.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Installing QConvergeConsole VMware vSphere Web Client Plug-in 1. Run the installer on the server providing the Tomcat service. Enter the information requested by the installer. On Windows, double-click the installer and follow the instructions on the GUI provided. On Linux: a. Make sure the user is the root user (or has root privileges). b. Create the installer executable if one does not already exist.
2–Driver Installation and Configuration VMware Driver Installation and Configuration Uninstalling the QConvergeConsole VMware vSphere Web Client Plug-in To uninstall the QConvergeConsole VMware vSphere Web Client Plug-in, refer to the procedure for Windows or Linux: Windows. Uninstall the QConvergeConsole VMware vSphere Web Client Plug-in on Windows using the Windows Control Panel Uninstall Program window. Follow the uninstaller user interface to remove the plug-in. Linux.
3 Fibre Channel Configuration This chapter provides the following information about configuring Fibre Channel: “Updating the Dell Firmware” on page 32 “Using Fast!UTIL for Custom Configuration” on page 36 “Setting Fibre Channel Adapter Parameters” on page 42 “Configuring Target Persistent Binding” on page 43 “Configuring Boot Devices” on page 45 “Configuring Virtual Ports (NPIV)” on page 46 “Configuring Fibre Channel Driver Parameters” on page 53 “Configuring Selective LUNs”
3–Fibre Channel Configuration Updating the Dell Firmware NOTE For information on configuring the Fibre Channel Adapter using VMware vCenter Server, refer to the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00), available at: www.marvell.com. Updating the Dell Firmware The firmware Dell Update Package (DUP) is a Flash update utility only; it is not used for adapter configuration. To run the firmware DUP, double-click the executable file.
3–Fibre Channel Configuration Updating the Dell Firmware 2. When the DUP splash screen appears (Figure 3-1), click Install to continue. Figure 3-1. Dell Update Package Splash Screen 3. Follow the installer instructions. If a warning message appears (Figure 3-2), click Yes to continue the installation. Figure 3-2.
3–Fibre Channel Configuration Updating the Dell Firmware The installer indicates that it is loading the new firmware (Figure 3-3). Figure 3-3. Loading New Firmware 4. When complete, the installer indicates the result of the installation (Figure 3-4). Click Yes to elect to reboot. Figure 3-4.
3–Fibre Channel Configuration Updating the Dell Firmware 5. To complete the installation, click Finish (Figure 3-5). Figure 3-5. Finish Installation Running the Firmware Update from the Command Line Running the firmware DUP from the command line, with no options specified, results in the same behavior as double-clicking the icon representing the DUP. Note that the actual file name of the DUP will vary. _Firmware___.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration Figure 3-6 shows the options you can use to customize the DUP installation behavior. Figure 3-6. Command Line Options Using Fast!UTIL for Custom Configuration This section provides detailed configuration information for advanced users who want to customize the configuration of the adapters and connected devices using Fast!UTIL (the QLogic Fibre Channel Adapter BIOS utility) in a pre-OS environment.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration 4. A message indicates that the configuration settings have been modified. Select Save changes. 5. To load the new parameters, reboot the system. CAUTION If the configuration settings are incorrect, your 2600 Series Adapter may not function properly.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration Table 3-1. Adapter Settings (Continued) Setting Values Default Description Frame Size 512, 1024, 2048 2048 This setting specifies the maximum frame length supported by the 2600 Series Adapter. Loop Reset Delay 0–60 seconds 5 seconds After resetting the loop, the firmware refrains from initiating any loop activity for the number of seconds specified in this setting.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration Selectable Boot Settings The Configuration Settings menu provides access to the Selectable Boot Settings options. If you enable the Host Bus Adapter BIOS in the adapter settings, you can select the boot device, as shown in Table 3-2. Table 3-2. Selectable Boot Settings Enable Selectable Boot Boot WWPN/ LUN No — The BIOS configures the first disk drive it finds as the boot device.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration NOTE System BIOS compatibility: To boot from a QLogic host 2600 Series Adapter in a computer system with a multiboot system BIOS, the 2600 Series Adapter must be included in the list of bootable devices in the system’s Boot menu. Restore Default Settings The Restore Defaults option restores the BIOS settings back to default.
3–Fibre Channel Configuration Using Fast!UTIL for Custom Configuration Table 3-3. Advanced Adapter Settings (Continued) Setting Values Default Description Port Down Retry Count 0–255 seconds 30 seconds This setting specifies the number of seconds the software waits before resending a command to a port whose status indicates that the port is down. Link Down Timeout 0–255 seconds 30 seconds This setting specifies the number of seconds the software waits for a link that is down to come up.
3–Fibre Channel Configuration Setting Fibre Channel Adapter Parameters Verify the disk data (Some targets do not support this feature.) Select a disk device CAUTION Performing a low-level format destroys all data on the disk.
3–Fibre Channel Configuration Configuring Target Persistent Binding Setting Fibre Channel Adapter Parameters with QConvergeConsole GUI For information about how to set Fibre Channel adapter parameters using QConvergeConsole GUI, refer to the topic about managing Fibre Channel and Fibre Channel over Ethernet (FCoE) adapter ports in the QConvergeConsole Help.
3–Fibre Channel Configuration Configuring Target Persistent Binding Configuring Persistent Binding with QConvergeConsole GUI To bind target devices attached to an adapter port using QConvergeConsole GUI: 1. In the system tree, expand a Fibre Channel node. 2. In the system tree for a 2600 Series Adapter, select the physical port number. 3. Click the Targets tab, and then click the Target Persistent Binding tab. 4.
3–Fibre Channel Configuration Configuring Boot Devices Configuring Persistent Binding with Noninteractive QConvergeConsole CLI To bind a selected target to a specific adapter using the noninteractive mode of QConvergeConsole CLI, issue the following command: # qaucli -pr fc -p ( | ) ( ) Where: hba instance = Adapter number (use the -g command to find) hba wwnn = Worldwide node name of the adapter hba wwpn = Worldwide port name
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) For information, refer to the section about the Fibre Channel interactive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) Configuring NPIV with QConvergeConsole GUI For information about using virtualization (NPIV) in QConvergeConsole GUI, refer to in the QConvergeConsole Help. To access the QConvergeConsole Help system while the GUI utility is running, point to the gear icon , point to Help, and then click Browse Contents. To install QConvergeConsole GUI, see “Installing QConvergeConsole GUI” on page 131.
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) Configuring NPIV Quality of Service The QLogic 2600 Series Adapters solution provides for standards-based quality of service (QoS), ensuring high-quality performance for applications that require preferential delivery. The QLogic QoS solution is based on assigning QoS levels to virtual ports (NPIV ports). You can configure the QoS using the priority method or the bandwidth method, as shown in Figure 3-7. Figure 3-7.
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) The physical port or WWN always has high priority, independent of the bandwidth or priority scheme chosen for created virtual ports. You need not assign a QoS level to every virtual port that you create. If a QoS level is not assigned to a virtual port, the default is low priority (best effort), independent of the bandwidth or priority scheme.
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) When the physical port is partitioned into four virtual ports, the port bandwidth is divided between the virtual ports according to traffic demands. QConvergeConsole lets you configure QoS for each virtual port by setting minimum and maximum percentages of the physical port’s bandwidth for each virtual port.
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) To set the QoS by bandwidth speed with QConvergeConsole GUI: 1. In the QConvergeConsole tree pane on the left, expand a 2600 Series Adapter. 2. Select a virtual port. 3. In the content pane on the right, click the QoS tab. 4. In the QoS Type box, select Bandwidth. 5. In the View By box, select Bandwidth Speed. 6. Move the slider to select the bandwidth speed, as shown in Figure 3-9. Figure 3-9. Setting the QoS by Bandwidth Speed 7.
3–Fibre Channel Configuration Configuring Virtual Ports (NPIV) Setting QoS by Priority To set the QoS by priority with QConvergeConsole GUI: 1. In the QConvergeConsole tree pane on the left, expand a 2600 Series Adapter. 2. Select a virtual port. 3. In the content pane on the right, click the QoS tab. 4. In the QoS Type box, select Priority. 5. Move the slider to select a low, medium, or high priority, as shown in Figure 3-10. Figure 3-10. Setting the QoS by Priority 6. Click Save.
3–Fibre Channel Configuration Configuring Fibre Channel Driver Parameters Configuring Fibre Channel Driver Parameters Use QConvergeConsole GUI, CLI, or VMware plug-in to configure Fibre Channel driver parameters: Configuring Fibre Channel Driver Parameters with QConvergeConsole GUI Configuring Fibre Channel Driver Parameters with Interactive QConvergeConsole CLI Configuring Fibre Channel Driver Parameters with Noninteractive QConvergeConsole CLI Configuring Fibre Channel Driver Parameters wi
3–Fibre Channel Configuration Configuring Selective LUNs Configuring Fibre Channel Driver Parameters with Noninteractive QConvergeConsole CLI To configure driver settings, issue the following command: # qaucli -pr fc -fs ( | ) {( | ) } Where: hba instance = Adapter number (use the -g command to find) hba wwpn = Worldwide port name of the adapter param name = Name of the parameter param alias = Alias of the parameter param value = New value o
3–Fibre Channel Configuration Configuring OoOFR Configuring OoOFR Out-of-order frame reassembly (OoOFR) reassembles out-of-order frames as they are received, minimizing network congestion by eliminating the retransmission of frames and exchanges. To configure OoOFR, use either QConvergeConsole GUI or CLI. Configuring OoOFR with QCC GUI To enable OoOFR with QConvergeConsole GUI: 1. In the QConvergeConsole system tree pane on the left, select a Fibre Channel port. 2.
3–Fibre Channel Configuration Configuring the UEFI Driver Configuring the UEFI Driver This section provides information on configuring the unified extensible firmware interface (UEFI) driver contained in the multiboot image. UEFI 2.x systems use a human interface infrastructure (HII) to configure motherboard devices and plug-in adapters. QLogic Fibre Channel Adapters use an HII to configure adapter parameters and boot-from-SAN settings. To configure the UEFI driver for Dell: 1.
3–Fibre Channel Configuration Configuring the UEFI Driver 3. In the Device Settings window, select your device and then press ENTER. The Main Configuration Page for the selected device appears. The Main Configuration Page is the top-level menu of the adapter configuration pages. Figure 3-12 shows an example of the Main Configuration Page. Figure 3-12. Dell System Setup: Main Configuration 4. On the Main Configuration Page, select Port Configuration Page and press ENTER.
3–Fibre Channel Configuration Configuring the UEFI Driver The Port Configuration Page appears; Figure 3-13 shows an example. Figure 3-13. Dell System Setup: Port Configuration 5. Use the Port Configuration Page to change adapter operational parameters, such as port speed. In most cases, use the default values. Table 3-4 describes the configurable options on the Port Configuration Page. Table 3-4. Port Configuration Page Settings Setting Description Device Name Indicates the name of the adapter.
3–Fibre Channel Configuration Configuring the UEFI Driver Table 3-4. Port Configuration Page Settings (Continued) Setting Description Virtual World Wide Node Name Indicates the adapter port’s unique virtual WWNN. World Wide Port Name Indicates the adapter port’s unique WWPN. Virtual World Wide Port Name Indicates the adapter port’s unique virtual WWPN. 6. To return to the Main Configuration Page, click Back. 7.
3–Fibre Channel Configuration Configuring the UEFI Driver Table 3-5 describes the Firmware and Device Information settings. Table 3-5. Firmware and Device Information Settings Setting Description Chip Type Type of intelligent storage peripheral (ISP) controller used in the adapter. PCI Device ID Unique PCI device ID of the adapter. Bus:Device:Function PCI address of the adapter in the Bus:Device:Function (BDF) notation. Family Firmware Version Adapter firmware version information.
3–Fibre Channel Configuration Configuring the UEFI Driver 10. On the Fibre Channel Target Configuration page, select SAN storage devices for boot from SAN. With selective boot scan enabled, the target configuration determines which target LUNs to map. All other devices are ignored. Table 3-6 describes the Fibre Channel Target Configuration settings. Table 3-6.
3–Fibre Channel Configuration Configuring the UEFI Driver 12. On the Main Configuration Page, select HBA Configuration Page, and then press ENTER. The HBA Configuration Page appears; Figure 3-16 shows an example. Figure 3-16. Dell System Setup: HBA Configuration 13. Use the HBA Configuration Page to configure adapter operational parameters. In most cases, use the default values. Table 3-7 describes the fields on the HBA Configuration Page. Table 3-7.
3–Fibre Channel Configuration Setting Queue Depth Table 3-7. HBA Configuration Page Settings (Continued) Setting Description Port Login Timeout Specifies the time-out in milliseconds that the initiator uses when attempting to log in to the target device port. The range is 0 to 255000. Port Down Retry Count Specifies the number of seconds the software retries a command to a port returning port-down status. The range is 0 to 255.
3–Fibre Channel Configuration Setting Queue Depth Changing the Windows Queue Depth The default queue depth value on Windows is 20 and the range is 0–254. To change the default value: 1. Click Start, select Run, and open the REGEDIT/REGEDT32 program. 2. Select HKEY_LOCAL_MACHINE and then expand the tree structure down to the QLogic driver as follows: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Ql2300 Parameters Device 3. Double-click DriverParameter:REG_SZ:qd=32. 4.
3–Fibre Channel Configuration Setting an FA-PWWN Changing the ESXi Queue Depth The default queue depth value on ESXi is 64 and the range is 0–65535. To change the default value: 1. Issue the following command: $ esxcfg-module -s "ql2xmaxqdepth=X" qlnativefc where X is the new queue depth value. 2. Restart the system.
3–Fibre Channel Configuration Setting an FA-PWWN Setting FA-PWWN with QConvergeConsole GUI Before setting the FA-PWWN, the port name appears on the Port Info page as shown in the example in Figure 3-17. Figure 3-17. Before Setting the FA-PWWN in the GUI To set the FA-PWWN from the adapter using QConvergeConsole GUI: 1. In the QConvergeConsole GUI tree pane on the left, select an adapter, expand the adapter node, and then select a port. 2. In the content pane on the right, click the Parameters tab. 3.
3–Fibre Channel Configuration Setting an FA-PWWN After refreshing the Brocade® switch, the Port Info page shows the Port Name as shown in Figure 3-18. Figure 3-18. New FA-PWNN Port Name in GUI Setting FA-PWWN with QConvergeConsole CLI To set the FA-PWWN from the adapter using QConvergeConsole CLI: 1. In the interactive mode of QConvergeConsole CLI, select Main Menu, and then click Adapter Configuration. 2. Select HBA Parameters. 3. Select the appropriate port. 4.
3–Fibre Channel Configuration Setting an FA-PWWN 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: Hard Loop ID Loop Reset Delay (seconds) Enable BIOS Enable Fibre Channel Tape Support Operation Mode Interrupt Delay Timer (100 microseconds) Execution Throttle1 Login Retry Count Port Down Retry Count Enable LIP Full Login Link Down Timeout (seconds) Enable Target Reset LUNs per Target Enable Receive Out of Order Frame Enable LR Enable Fabric Assign WWN Commit Changes Abort Changes (p or
3–Fibre Channel Configuration Setting an FA-PWWN After refreshing the Brocade switch, the Adapter Information shows the port name as shown in the following example. QConvergeConsole CLI - Version 1.1.3 (Build 22) FC Adapter Information 1: 2: 3: 4: 5: FC FC FC FC FC Adapter Information Port Information VPD Information Target/LUN Information VFC Information (p or 0: Previous Menu; m or 98: Main Menu; ex or 99: Quit) Please enter selection: 2 QConvergeConsole CLI - Version 1.1.
3–Fibre Channel Configuration Setting an FA-PWWN Setting the FA-PWWN from the Brocade Switch From the Brocade switch, you can set a FA-PWWN and a static FA-PWWN. For the most current information, refer to the Brocade switch documentation. Setting the FA-PWWN from the Switch Figure 3-19 shows the FA-PWWN setting from the Brocade switch. Figure 3-19. Setting the FA-PWWN from the Brocade Switch After refreshing the Brocade switch, the Device Port WWN appears in Web Tools as shown in Figure 3-20.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD After refreshing the Brocade switch, the Device Port WWN appears in Web Tools as shown in Figure 3-22. Figure 3-22.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD Figure 3-23 shows an example. Figure 3-23. Enabling Host Bus Adapter Port BIOS To enable fabric-assigned boot LUN: 1. In QConvergeConsole GUI, select the Host tab in the left pane. 2. In the system tree, expand the adapter node and then select a port node. 3. In the content pane on the right, click the Parameters tab. 4. On the Parameters page, click the Boot Device Selection tab. 5.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD Figure 3-24 shows an example. Figure 3-24. Enabling Fabric-Assigned Boot LUN Configuring the Adapter and Boot Devices with QConvergeConsole CLI To configure adapter and boot devices: 1. In QConvergeConsole CLI, navigate to Adapter Configuration and then select HBA Parameters. 2. Enter the port number. 3. Select Configure HBA Parameters. 4. Select Enable BIOS and set it to Enable. 5.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD Figure 3-25 shows an example of the adapter and boot device configuration. Figure 3-25. Configuring Adapter and Boot Device Configuring a Zone in a Brocade Switch To configure a zone in a Brocade switch: 1. Create a boot LUN configuration as follows: bootluncfg --add 50:00:53:37:63:FA:00:05 20:02:00:11:0d:51:5c:01 0000000000000000 2. Create a zone named with the following: 3.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD Figure 3-26 shows an example of a configured zone in a Brocade switch. Figure 3-26. Configuring a Zone in a Brocade Switch Verifying that FA-BLD is Operational To verify if the FA-BLD is operational, use either Fast!UTIL or the system. Figure 3-27 shows Fast!UTIL displaying the boot LUN. Figure 3-27.
3–Fibre Channel Configuration Configuring and Verifying FA-BLD Figure 3-28 shows using the system with a LUN ready to install or OS booted from LUN. Figure 3-28. Verifying FA-BLD from the System Adapter Side Restrictions The known fabric-assigned port world wide name (FA-PWNN) and FA-BLD restrictions include the following: Cannot be fully enabled from Fast!UTIL Do not use Restore Defaults from Fast!UTIL, QConvergeConsole GUI, or QConvergeConsole CLI.
3–Fibre Channel Configuration Using a Fabric-Assigned Boot LUN Using a Fabric-Assigned Boot LUN This section describes how to use a fabric-assigned boot LUN in the following utilities: Using a Fabric-Assigned Boot LUN in QConvergeConsole GUI Using a Fabric-Assigned Boot LUN in Interactive QConvergeConsole CLI Using a Fabric-Assigned Boot LUN with Noninteractive QConvergeConsole CLI Using a Fabric-Assigned Boot LUN with QConvergeConsole Plug-ins Using a Fabric-Assigned Boot LUN in QConvergeC
3–Fibre Channel Configuration Using a Fabric-Assigned Boot LUN Using a Fabric-Assigned Boot LUN with QConvergeConsole Plug-ins For information about using a fabric-assigned boot LUN for QConvergeConsole VMware vSphere Web Client Plug-in, see the section “Configure Fibre Channel Port Boot Parameters” in the User’s Guide—QConvergeConsole Plug-ins for VMware vSphere (part number SN0054677-00). To configure a 2600 Series Adapter boot device with QConvergeConsole VMware vCenter Server Plug-in: 1.
3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route Running Diagnostics—Fibre Channel Ping and Trace Route This section provides the following information on how to run Fibre Channel ping and trace route diagnostics: Pinging and Viewing Trace of Routing Using Topology Map Running a Fibre Channel CT Ping Test Fibre Channel Trace Route Pinging and Viewing Trace of Routing Using Topology Map The QConvergeConsole GUI topology map uses the common transport (CT) layer
3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route Running a Fibre Channel CT Ping Test You can run a Fibre Channel CT ping test from QConvergeConsole GUI, QConvergeConsole CLI, or the QConvergeConsole VMware plug-ins, as described in this section. Running a Fibre Channel CT Ping from QConvergeConsole GUI To run a Fibre Channel CT ping test from QConvergeConsole GUI: 1. In the QConvergeConsole GUI left pane, click the Host tab. 2.
3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route A caution message appears for the diagnostic CT ping test (Figure 3-31). Figure 3-31. CT Ping Test Caution 6. Ensure that the port has no active I/O operations, and then either click Yes to proceed or No to cancel the test. Running a Fibre Channel CT Ping from QConvergeConsole CLI To run a Fibre Channel CT ping test from QConvergeConsole CLI: 1. From the QConvergeConsole CLI FC Diagnostics menu, select 7: CT Ping Test.
3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route ID Port/Loop --------01-0B-01 Data Miscompare ---------0 Link Failure ------0 Sync Loss -------0 Signal Loss --------0 Invalid CRC --------0 Diagnostic Status ---------Success NOTE The default setting will repeat 10 times with output similar to the preceding for each pass of the test.
3–Fibre Channel Configuration Running Diagnostics—Fibre Channel Ping and Trace Route Figure 3-32 shows an example. Figure 3-32. Running Fibre Channel Trace Route from QConvergeConsole GUI The Fibre Channel trace route output from QConvergeConsole GUI shows a symbol of a red payload that starts from the host. The travel across the route is also highlighted in red. The payload enters and exits from the appropriate port on each switch as it traverses the path until it reaches the selected target.
3–Fibre Channel Configuration Configuring CS_CTL QoS Configuring CS_CTL QoS NOTE For information about end-to-end CS_CTL QoS, see “Configuring End-to-End CS_CTL QoS” on page 87.
3–Fibre Channel Configuration Configuring CS_CTL QoS Enabling CS_CTL QoS Mode for the Initiator and Target Ports Figure 3-33 shows how to enable CS_CTL QoS mode for the initiator and target ports. Figure 3-33. Enabling CS_CTL QoS Mode Verifying and Confirming CS_CTL Mode Setup for Each Port Figure 3-34 shows how to verify the CS_CTL mode setup for each port. Figure 3-34.
3–Fibre Channel Configuration Configuring CS_CTL QoS Figure 3-35 shows how to create a virtual port from the adapter’s port in QConvergeConsole GUI. Figure 3-35.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS Setting the QoS Priority Level for a Virtual Port in QConvergeConsole GUI Figure 3-36 shows how to set the QoS priority level for a virtual port in QConvergeConsole GUI. Figure 3-36. Setting the QoS Priority Level NOTE By default, the QoS of the physical port is set to High, and the QoS of the virtual port is set to Low.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS Therefore, when all three entities support QoS (and it is enabled on the switch and the target), a default priority value is populated in all FCP_CMND, FCP_DATA, FCP_XFER_RDY, FCP_RSP, and FCP_CONFIRM frames. i NOTE QoS must be supported by both the switch and target devices. At the time of publication, CS_CTL QoS has been tested only on the Brocade SW6510 switch with Fabric OS (FOS) version 7.3.0a.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS 4. To verify that CS_CTL QoS is enabled, issue the following command: root> configshow -all | grep fos.csctlMode This command should return the following response: fos.csctlMode:1 5. To enable QoS on a switch-port basis, issue the following command: portcfgqos --enable [slot/]port csctl_mode Configuring CS_CTL QoS on the Storage Device See your device’s user guide for QoS configuration instructions.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS 6. To create the vPorts, click Create. Figure 3-37 shows an example. Figure 3-37. Creating vPorts in QConvergeConsole GUI To create a vPort in interactive QConvergeConsole CLI: 1. On the Main Menu, select Adapter Configuration. 2. On the Adapter Type Selection menu, select Virtual Ports (NPIV). 3. On the Virtual Ports menu, select Adapter Port. 4. On the Adapter Port menu, select Create vPorts. 5.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS 7. Set the QoS priority value for the vPort by moving the corresponding slider. 8. Repeat Step 6 and Step 7 for each vPort whose priority you want to change. 9. Click Save. Figure 3-38 shows an example. Figure 3-38. Changing vPort Priority using QConvergeConsole GUI To change the vPort priority level using interactive QConvergeConsole CLI: 1. On the Main Menu, select Adapter Configuration. 2.
3–Fibre Channel Configuration Configuring End-to-End CS_CTL QoS 6. Set the vPort priority as follows: If the vPort is listed under QoS: a. Select the vPort. b. Set the QoS priority value for the vPort by moving the corresponding slider. c. Click Save. Figure 3-39 shows an example. Figure 3-39. Changing vPort Priority Using QConvergeConsole Plug-ins 7. If vPort is not listed under QoS: a. Under QoS, click Add. b. Set the QoS priority value by moving the corresponding slider. c.
3–Fibre Channel Configuration Configuring FDMI Configuring FDMI The fabric device management interface (FDMI) enables the centralized management of devices such as host adapters. Supported configuration for FDMI: i QLogic 2500 and 2600 Series Adapters Brocade 16G switches with Fabric OS (FOS) v7.3 or later Cisco 16G switches with NX-OS v8.3.1 or later NOTE Results can be viewed from Switch CLI. If the Fibre Channel switch does not support FDMI-2, it falls back to FDMI-1 support.
3–Fibre Channel Configuration Configuring FDMI Brocade Switch FOS CLI Figure 3-40 shows the FOS CLI of a Brocade switch. Figure 3-40.
3–Fibre Channel Configuration Configuring FDMI Fabric Features Table 3-9 shows the default configuration for Brocade Fibre Channel fabric features. . Table 3-9. Brocade Fibre Channel Fabric Features—Default Configuration Feature Description Management Tools Default Configuration D_Port Diagnostics port support N/A Diagnostic test; run from switch. Nothing to configure on adapter. FA-PWWN Fabric-assigned port world wide name QConvergeConsole GUI Disabled by default on adapter.
3–Fibre Channel Configuration Configuring FDMI Table 3-10 shows the default configuration for Cisco Fibre Channel fabric features. . Table 3-10. Cisco Fibre Channel Fabric Features—Default Configuration Feature Description Management Tools Default Configuration D_Port Diagnostics port support N/A Diagnostic test; run from switch. Nothing to configure on adapter. FC Ping Ping a Fibre Channel N_Port or end device QConvergeConsole GUI Diagnostic test; nothing to configure.
3–Fibre Channel Configuration Configuring FDMI To verify the additional QLogic adapter attributes registered on the Brocade switch, issue the fdmishow command on Brocade Fibre Channel switches to confirm that all the requested attributes are displayed in the switch. For details, see the Brocade switch documentation. The following shows sample output of the fdmishow command.
3–Fibre Channel Configuration Enabling QLogic Forward Error Correction ROM Ver :3.62 Firmware Ver :8.08.03 (d0d5) Port-id: 21:00:00:24:ff:8f:d8:88 Supported FC4 types:scsi-fcp Supported Speed :4G 8G 16G Current Speed :16G Maximum Frame Size :2048 OS Device Name :qla2xxx:host1 Host Name :localhost.
3–Fibre Channel Configuration Enabling QLogic Forward Error Correction i NOTE Instead of having to request retransmission of the entire data frame, the receiving device can recreate or reconstruct the data stream itself. This process prevents multiple CRC errors from being triggered and causing application performance issues. Enabling QLogic FEC To enable the QLogic FEC feature, submit a case to Technical Support at www.marvell.
3–Fibre Channel Configuration Running Extended Link Service Commands In Figure 3-41, the QConvergeConsole CLI interactive mode Adapter Information menu shows a port with an online FEC status. Figure 3-41.
3–Fibre Channel Configuration Running Extended Link Service Commands Link Cable Beacon Extended Link Service Command NOTE This feature is supported only on QLE2690-DEL and QLE2692-DEL Adapters. Run the LCB test only from a switch with either FOS version 7.4.x or later, or Cisco NX-OS 8.3.1 or later. The link cable beacon (LCB) extended link service command locates the corresponding ends of a cable by flashing the specific LEDs on the corresponding ports of a link.
3–Fibre Channel Configuration Running Extended Link Service Commands Vendor Name: HP-F BROCADE Vendor OUI: 00:05:1e Vendor PN: QK724A Vendor Rev: A Wavelength: 850 (units nm) Options: 003a Loss_of_Sig,Tx_Fault,Tx_Disable BR Max: 0 BR Min: 0 Serial No: HAF314370000B7F Date Code: 140909 DD Type: 0x68 Enh Options: 0xfa Status/Ctrl: 0x30 Pwr On Time: 0.
3–Fibre Channel Configuration Running Extended Link Service Commands Signal Loss (Downstream): -20.3 dBm (9.
4 NVM Express over Fibre Channel This chapter describes the installation and configuration of NVMe over Fibre Channel (FC-NVMe) on the QLogic adapters from Marvell. It covers: Hardware and Software Requirements “Host Setup” on page 106 “Limitations and Known Issues” on page 113 “Unloading and Reloading the Linux Driver” on page 114 For assistance with the installation and configuration of FC-NVMe, contact Marvell Technical Support at this address: https://www.marvell.
4–NVM Express over Fibre Channel Hardware and Software Requirements RHEL 8.1 Microsoft Windows Server (Tech Preview only): Windows Server 2016 Windows Server 2019 Host Software This section lists the required FC-NVMe software, which, unless stated otherwise, is available on the Marvell Web site (see “Documentation Conventions” on page xi).
4–NVM Express over Fibre Channel Host Setup RHEL 7.6 OOB RHEL 8.0 OOB Windows OOB driver version 9.3.3.20, or later (Tech Preview): q23wx64W16Storv9.3.3.20.zip Fibre Channel firmware version 9.02.05 or later Linux QLogic management application, QConvergeConsole CLI version 2.3.00-36 or later: Windows QLogic management application, QConvergeConsole CLI version 2.3.00-36 or later (available from the Dell site): QConvergeConsoleCLI-2.3.00.36.x86_64 QConvergeConsoleCLI-2.3.00.
4–NVM Express over Fibre Channel Host Setup b. Untar and install the Linux driver kit by issuing the following commands: # tar -zxvf qla2xxx-src-v10.01.00.xx.yy.z-k.tar.gz # cd qla2xxx-src-v10.01.00.xx.yy.z-k # ./extras/build.sh install The src driver kits and driver RPM kits have embedded FC-NVMe auto-discovery scripts that are installed when the driver is deployed. c. Verify that the FC-NVMe scripts are installed by issuing the following commands: # ls -l /etc/udev/rules.d/99-nvme-fc.
4–NVM Express over Fibre Channel Host Setup 4. Edit or create the qla2xxx.conf file to add the ql2xnvmeenable option. For example, /etc/modprobe.d/qla2xxx.conf contains: options qla2xxx ql2xnvmeenable=1 For the FC-NVMe option to take effect the system boot image will need to be updated. See Step 2 and Step 5 to install the driver and to rebuild the boot image. 5. Rebuild the RAMDISK image by following the Readme driver guidelines to rebuild the initrd image.
4–NVM Express over Fibre Channel Host Setup NOTE The OOB driver must have the FC-NVMe option enabled to attach to FC-NVMe storage devices. For details on using the FC-NVMe driver option, see either the 10.01.xx.xx.xx.x-x driver documentation or the example shown in Step 11. 11. (Optional) As needed, on the supported Linux OS, create a hostnqn file to attach to remote FC-NVMe Storage Subsystems. a. With the NVMe CLI already installed, issue the following command to verify that the hostnqn file exists.
4–NVM Express over Fibre Channel Host Setup Windows Host Setup NOTE These procedures apply only to the FC-NVMe driver. For the Fibre Channel driver, follow the instructions in the corresponding Readme.txt file. To set up a Windows host: 1. Install the Windows FC driver from the Dell update package. Driver v9.3.3.20 or greater QConvergeConsole CLI v2.3.00-36 or greater Windows Host NQN The driver automatically generates a host NVMe qualified name (NQN).
4–NVM Express over Fibre Channel Host Setup 2. Choose the HBA instance for the adapter that you want to connect to FC-NVMe devices (0 in this example), and then issue the following command: # qaucli -i 0 Running Firmware Version Flash Firmware Version : 9.02.05 (d0d5) : 9.02.05 The preceding output shows the QLE2692-DEL adapter with firmware version 9.02.05 in RAM and flash memory.
4–NVM Express over Fibre Channel Host Setup Example: nvme list Command The following example of a portion of the nvme list output shows the FC-NVMe attached targets. Node SN Model Namespace Usage Format FW Rev ------- ------------------- -------- ---- ---- ----------------------- --------- ----------nvme0n1 00-200100110dd89300 SANBlaze VLUN P3T0 1 67.11 MB / 67.11 MB 512 B + 0 B V8.x-dev nvme1n1 00-200000110dd89200 SANBlaze VLUN P2T0 1 67.11 MB / 67.11 MB 512 B + 0 B V8.
4–NVM Express over Fibre Channel Limitations and Known Issues Figure 4-2 shows the devices in Windows Device Manager. Figure 4-2. FC-NVMe Devices in Windows Device Manager NOTE To support formatting of an FC-NVMe drive on Windows, you may need to add the following Windows Registry entry for some OEM storage: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ ql2300\Parameters\Device]"DriverParameter"="ts=1" NOTE By default, NVMe is disabled.
4–NVM Express over Fibre Channel Unloading and Reloading the Linux Driver Windows Windows FC-NVMe does not support point to point (also called N2N) direct attach to Target/LUN configuration. It does support fabric configuration through FC Switch fabric. Unloading and Reloading the Linux Driver Follow the instructions in this section to unload and reload the Linux driver. To unload and reload the Linux driver: 1.
A Troubleshooting This appendix provides information about Fibre Channel diagnostics and a Fibre Channel troubleshooting diagram, including: Fibre Channel Diagnostics “Fibre Channel Troubleshooting Diagram” on page 118 “Troubleshooting with a Diagnostic Port (D_Port)” on page 119 Fibre Channel Diagnostics Troubleshooting with Fibre Channel diagnostics include: Fibre Channel Diagnostics Using QConvergeConsole GUI Fibre Channel Diagnostics Using Interactive QConvergeConsole CLI Fibre C
A–Troubleshooting Fibre Channel Diagnostics 4. From the Data Size list, click the number of bytes to transfer. Valid values are 8, 16, 32, 64, 128, 256, 512, 1024 and 2048. For Linux operating systems only, you can select data size values from 2048, 4096, 8192 up to 65535 (2K bytes to 64K bytes). 5. 6. 7. To set the test frequency, do one of the following: In the Number of Tests box, type or select the number of tests you want to run. Testing stops when the passes complete.
A–Troubleshooting Fibre Channel Diagnostics To run the beacon on/off test: 1. In the QConvergeConsole GUI main window, click an adapter port in the system tree pane on the left. 2. In the content pane on the right, click the Port Info tab. 3. On the Port Info page, click Beacon On to run the test. To end the test, click Beacon Off. For more information, refer to the topic about performing diagnostics in the QConvergeConsole Help.
A–Troubleshooting Fibre Channel Troubleshooting Diagram Fibre Channel Troubleshooting Diagram Figure A-1 and Figure A-2 provide a two-part troubleshooting flowchart. Figure A-1.
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) 3 Yes Adapter can log into fabric and name server? 2 CoŶĮgure Fibre Channel switch for autonegoƟaƟon and return to “Start” No Verify that cable is connected and link lights are lit No Cable is connected and link lights lit? Yes Contact Technical Support No Are opƟcs QLogic? Yes Check auto-negoƟaƟon on Fibre Channel Fibre Channel switch set for auto-negoƟaƟon? No Yes Replace opƟcs with QLogic opƟcs and return to “Start” Troubl
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) NOTE All QLogic-branded 16GFC SFP+ transceivers can run D_Port tests. If you have a supported non-QLogic branded transceiver, ensure that it supports the optical wrap (OWrap) and electrical wrap (EWrap) capability that is required for D_Port. When a switch port is enabled as a D_Port, the QLogic 2600 Series Adapter automatically runs the basic diagnostic test at both ends of the link.
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) To disable D_Port diagnostic mode: From the Brocade Fibre Channel 16G switch, issue the following commands: # portdisable # portcfgdport ––disable # portenable The D_Port test stops. Configuring and Running Diagnostics Port on a Cisco Fibre Channel 16 Switch The following example configures and starts a diagnostic test on port 2 of a Cisco Fibre Channel 9396S or 97xx switch (NX-OS 8.2.1 or later).
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) To disable the diagnostic port, type the following commands: Cisco#int fc 1/2 Cisco(config-if)# shut Cisco(config-if)# no switchport link-diag Cisco(config-if)# no shut Checking D_Port Results from a Brocade Fibre Channel 16G Switch To view the D_Port test results from a Brocade Fibre Channel 16G switch: 1. To get the port number, issue the switchshow command: # switchshow The following example output identifies port 17: 17 2.
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) Optical loopback 01:46:54 PASSED ----------------Link traffic test -------SKIPPED ----------------============================================================================== Roundtrip link latency: 157 nano-seconds Estimated cable distance: 3 meters Buffers required: 1 (for 2112 byte frames at 16Gbps speed)s Verifying D_Port Mode with QConvergeConsole GUI To verify D_Port mode in QConvergeConsole GUI: 1.
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) The Adapter Information menu shows the affected port with a status of Loop Down, Diagnostic Mo. Figure A-4 shows an example. Figure A-4. D_Port Mode in Interactive QConvergeConsole CLI Verifying D_Port Mode with Noninteractive QConvergeConsole CLI To verify D_Port mode in noninteractive QConvergeConsole CLI, issue the following command: quacli -pr fc -g All the 2600 Series Adapters are listed.
A–Troubleshooting Troubleshooting with a Diagnostic Port (D_Port) For more information, refer to the section about the Fibre Channel noninteractive commands in the User’s Guide—QConvergeConsole CLI (part number SN0054667-00).
B Specifications This appendix provides specifications for the QxE26xx-DEL, QLE269x-DEL, and QLE269xL-DEL Adapters. Physical Characteristics Table B-1 lists the physical characteristics for the QxE26xx-DEL, QLE269x-DEL, and QLE269xL-DEL Adapters. Table B-1. Physical Characteristics Adapter Type Bracket Installed Length Width QLE2660-DEL Low profile PCIe card Full height 6.6 inches 2.54 inches QLE2662-DEL Low profile PCIe card Full height 6.6 inches 2.
B–Specifications Power Requirements Power Requirements Table B-2 lists the power requirements for the QxE26xx-DEL, QLE269x-DEL, and QLE269xL-DEL Adapters. Table B-2. Power Requirements Adapter Nominal Power Maximum Power QLE2660-DEL 13W 15W QLE2662-DEL 14W 16W QME2662-DEL 12W 14W QLE2690-DEL 8.6W 10.65W QLE2690L-DEL 8.6W 10.65W QLE2692-DEL 9.3W 11.5W QLE2692L-DEL 9.3W 11.5W QME2692-DEL 7W 8.
B–Specifications Interface Specifications Interface Specifications Table B-3 list the interface specifications for the QxE26xx-DEL, QLE269x-DEL, and QLE269xL-DEL Adapters. Table B-3. Interface Specifications Port Type 16Gb SFP+ Media SFF-8431 Specification for SFP+, Revision 3.2 Environmental Specifications Table B-4 lists the environmental specifications for the QxE26xx-DEL, QLE269x-DEL, and QLE269xL-DEL Adapters. Table B-4.
C QConvergeConsole GUI This appendix provides the following information about QConvergeConsole GUI: Introduction to QConvergeConsole GUI “Downloading QConvergeConsole Documentation” on page 130 “Downloading and Installing Management Agents” on page 130 “Installing QConvergeConsole GUI” on page 131 “What Is in the QConvergeConsole Help System” on page 134 NOTE For information on installing QConvergeConsole GUI, refer to the Installation Guide—QConvergeConsole GUI (part number SN0051105-0
C–QConvergeConsole GUI Downloading QConvergeConsole Documentation Note the following: QConvergeConsole GUI works with the Windows Server, Red Hat Linux® Advanced Server and Enterprise Server, Novell® SUSE® Linux Enterprise Server (SLES®), and Oracle Linux—Unbreakable Enterprise Kernel (UEK). Multiple operating system support allows control of heterogeneous environments.
C–QConvergeConsole GUI Installing QConvergeConsole GUI 3. On the Downloads and Documentation page, click Adapters, and then select the by Model button. 4. To define a search, click an item in each selection column, and then click Go. 5. Download the following for each adapter on the host server: 6. SuperInstaller Readme and Release Notes Install the agents by running the SuperInstaller. For detailed information on running the SuperInstaller, refer to the Readme and Release Notes.
C–QConvergeConsole GUI Installing QConvergeConsole GUI Installing QConvergeConsole in a Windows Environment The QConvergeConsole Installer for Windows is a self-extracting utility that installs QConvergeConsole and related files. NOTE Before you begin, read the QConvergeConsole Release Notes and Readme documents for important, up-to-date product information. To install QConvergeConsole in a Windows environment: 1.
C–QConvergeConsole GUI Installing QConvergeConsole GUI Installing QConvergeConsole in a Linux Environment You have the option of installing QConvergeConsole in a Linux environment using either a GUI or CLI method. To install from the CLI, see “Installing QConvergeConsole in Silent Mode” on page 134. You can graphically install QConvergeConsole on a Linux host by running a Virtual Network Computing (VNC®) program on a Windows host.
C–QConvergeConsole GUI What Is in the QConvergeConsole Help System 8. In the Pre-Installation Summary dialog box, read the information, and then click Install. During the installation, the installer notifies you of the status. 9. In the Install Complete dialog box, click Done to exit the installer. You have installed QConvergeConsole on your server. Installing QConvergeConsole in Silent Mode You can install QConvergeConsole from a command prompt in silent mode.
C–QConvergeConsole GUI What Is in the QConvergeConsole Help System Managing Fibre Channel and FCoE Adapters describes how to do the following for a Fibre Channel Adapter (2400/2500/2600/2700 Series) or Converged Network Adapter (8100/8200/8300 Series): View and edit adapter-specific information for the selected adapter View and modify adapter configuration and settings Update the adapter’s Flash memory on a Fibre Channel or an FCoE driver Managing Fibre Channel and FCoE Ports describes how to
D Regulatory Information This appendix provides warranty, regulatory, and compliance information for the Fibre Channel Adapters covered in this guide. Warranty For information about your Dell warranty, see your system documentation. Regulatory and Compliance Information Laser Safety, FDA Notice This product complies with DHHS Rules 21CFR Chapter I, Subchapter J. This product has been designed and manufactured according to IEC60825-1 on the safety label of laser product.
D–Regulatory Information Regulatory and Compliance Information Agency Certification The following section contains a summary of EMI/EMC test specifications performed on model HD8310405 and CU0310421 to comply with radiated emission, radiated immunity, and product safety standards. EMI and EMC Requirements FCC Rules, CFR Title 47, Part 15, Subpart B: Class A FCC compliance information statement: This device complies with Part 15 of the FCC Rules.
D–Regulatory Information Regulatory and Compliance Information VCCI: 20011-04; Class A AS/NZS; CISPR 22:2009+A1:2010 Class A Korea Certification KC-RRA KN22 KN24 (2011) Class A Product Name/Model—2600 Series Adapter Certification Holder—QLogic Corporation Manufactured Date—Refer to date code listed on product Manufacturer/Country of Origin—QLogic Corporation/USA A class equipment As this equipment has undergone EMC registration for business purpose, the seller (Business purpose info/ telecommunications eq
E Adapter LEDs This appendix describes the LEDs on the 2600 Series Adapters. Figure E-1 shows the QLE26xx 16Gb Adapter ports with three LEDs: The green LED on the left is 16Gb. The green LED in the middle is 8Gb. The green LED on the right is 4Gb. Figure E-1.
E–Adapter LEDs Table E-1 defines the LED behavior for the QLE26xx 16Gb Adapters. Table E-1.
F Revision History Document Revision History Revision A, November 20, 2012 Revision B, April 8, 2013 Revision C, September 12, 2013 Revision D, June 9, 2014 Revision E, January 22, 2015 Revision F, July 1, 2015 Revision G, March 21, 2016 Revision H, April 19, 2016 Revision J, February 1, 2017 Revision K, August 24, 2017 Revision L, December 19, 2017 Revision M, April 13, 2018 Revision N, January 29, 2019 Revision P, June 14, 2019 Revision R, October 28, 2019 Changes Sections Affected Update to operating
Contact Information Marvell Technology Group http://www.marvell.com Marvell.
