QConvergeConsole CLI Readme. QLogic Corporation All rights reserved

Transcription

1 QConvergeConsole CLI Readme QLogic Corporation All rights reserved Note: Please check the driverdownloads.qlogic.com website for the most up-to-date readme information for this application Table of Contents 1 Package Contents 2 Hardware Requirements 3 OS Support 4 Supported Features 5 Using the QCC CLI 6 Additional Notes 6.1 Features Not Available When Running FCoE Windows Driver with NPIV Enabled 6.2 Features Not Available When Running VMware Driver 6.3 Features Not Available when Running FCoE Sysfs Inbox Driver 6.4 Warning Messages on Startup 6.5 VLAN & Teaming Driver Support 6.6 VLAN & Teaming Save and Restore Features 6.7 QLE82xx Internal and External Loopback Diagnostics Features 6.8 iscsi QLE82xx Features Currently Not Supported 6.9 QLogic iscsi IOCTL Module Required On Linux Operating Systems 6.10 Actions prior to the installation/upgrade of drivers 6.11 Issue with the BSG on Oracle UEK 6.12 OS Hot fix for performance issues on Windows Server 2008 R Firmware for IPv6 support 6.14 RHEL6.0 Inbox iscsi driver info 6.15 RHEL6.x Installation of 32-bit compatibility libs 6.16 RHEL6.x Releases, iscsi 6.17 Red Hat 6.x with the x86_x64 architecture, iscsi 6.18 SLES 11 SP1 Error Message, iscsi 6.19 iscsi QL4xxx cards support 6.20 A card reset if in a boot from SAN configuration 6.21 Features Currently not Supported in Windows PE 6.22 Action prior to the installation/upgrade of QCC CLI 7 Known Issues and Workarounds 7.1 SLES 11 SP1 - Error message 7.2 Smart Screen Filter feature on Windows platform 7.3 Updating NIC parameters that affect the link, as well as running loopback test under a PXE boot issue 8 Contacting Support 1. Package Contents The QConvergeConsole Command Line Utility (QCC CLI) package contains the following files: Windows x64:

2 * qaucli.exe - QCC CLI main executable * enable_disable_x64.exe - QCC CLI Support EXE * ncli.dll - Networking protocol DLL * icli.dll - iscsi protocol DLL * Fibre Channelapi_x64.dll - Fibre Channel protocol DLL * ql_p3p_npar.dll * NPAR DLL - fcscli-exitcodes.txt * Fibre Channel supporting TXT * Readme.txt - Readme TXT * npiv.bat - Fibre Channel MOF file installer * iscli.bat - iscsi BAT * netscli.bat - Networking BAT * qldiag.bat - QLDiag BAT * scli.bat - Fibre Channel BAT * iscli.cfg - iscsi trace configuration * netscli.cfg - Networking trace configuration * qaucli.cfg - QCC CLI trace configuration * drivers - DIR - Networking /IM driver files * nvramdefs - DIR - NVRAM defines * VlanTeaming - DIR Series VLAN/Teaming Driver files Additional various DLL, BAT, and properties files Windows x86: * qaucli - QCC CLI main executable * enable_disable_x32.exe - QCC CLI Support EXE * ncli.dll - Networking protocol DLL * icli.dll - iscsi protocol DL * fcapi_x32.dll - Fibre Channel protocol DLL * ql_p3p_npar.dll - NPAR DLL * fcscli-exitcodes.txt - Fibre Channel supporting TXT * Readme.txt - Readme TXT * npiv.bat - Fibre Channel MOF file installer * iscli.bat - iscsi BAT * netscli.bat - Networking BAT * qldiag.bat - QLDIag BAT * scli.bat - Fibre Channel BAT * iscli.cfg - iscsi trace configuration * netscli.cfg - Networking trace configuration * qaucli.cfg - QCC CLI trace configuration * drivers - DIR - Networking/IM driver files * nvramdefs - DIR - NVRAM define * VlanTeaming - DIR 8100 Series VLAN/Teaming Driver files Additional various DLL, BAT, and properties files Linux: * qaucli - QCC CLI main executable * scli - Fibre Channel SHELL * iscli - iscsi SHELL * netscli - Networking SHELL * readme.txt - QCC CLI - Readme * iscli.cfg - iscsi trace configuration * netscli.cfg - Networking trace configuration * qaucli.cfg - QCC CLI trace configuration * nvramdefs - DIR - NVRAM defines

3 * agent.properties - QCC CLI configuration Additional various properties files Solaris: * qaucli - QCC CLI main executable * scli - Fibre Channel SHELL * iscli - iscsi SHELL * netscli - Networking SHELL * readme.txt - QCC CLI - Readme * iscli.cfg - iscsi trace configuration * netscli.cfg - Networking trace configuration * qaucli.cfg - QCC CLI trace configuration * nvramdefs - DIR - NVRAM defines * agent.properties - QCC CLI configuration Additional various properties files 2. Hardware Requirements The QCC CLI requires the following minimum hardware: * One or more of the following QLogic adapters: o 2400, 2500 and 2600 Series Fibre Channel Adapters o 3200 Series Intelligent Ethernet Adapters o 8100, 8200 and 8300 Series Converged Network Adapters * Single- or multi-processor server or workstation * Pentium II class 300MHz, 64MB RAM, 25MB disk space 3. OS Support The QCC CLI runs on the following operating system (OS) platforms: OS Name OS Type Hardware Platform Windows Server bit - Windows Server bit Windows Server bit Windows Server 2008 R2 64-bit Windows PE 64-bit Windows PE 32-bit Red Hat RHEL AS/ES 6.x 32-bit x86 Red Hat RHEL AS/ES 6.x 64-bit x64 Red Hat RHEL AS/ES bit x86 Red Hat RHEL AS/ES bit x64 Red Hat RHEL AS/ES bit x86 Red Hat RHEL AS/ES bit x64 Red Hat RHEL AS/ES bit x86 Red Hat RHEL AS/ES bit x64 Novell SLES 11 SP2/SP1 32-bit x86 Novell SLES 11 SP2/SP1 64-bit Intel 64, AMD64 Oracle UEK R2 ( / )

4 Solaris 11 Solaris 11 Solaris 10 Solaris 10 Sparc x86 Sparc x86 Xen Server 5.6, 6.x NOTE: For specific OS service packs (SPs) and updates, refer to the descriptions where this software version is posted on the QLogic Web site: 4. Supported Features QCC CLI can configure adapters with the following protocols: * Networking * iscsi * Fibre Channel/Fibre Channel over Ethernet (FCoE) For details on the supported features, see the QConvergeConsole Command Line Utility User's Guide. 5. Using the QCC CLI The QConvergeConsole Command Line Utility User's Guide provides procedures for installing, starting, and removing the QCC CLI. It also provides detailed explanations of command line options. You can download a copy of this document from the driver download page for your adapter at QLogic's Driver Downloads/Documentation Web page: 6 Additional Notes 6.1 Features Not Available When Running FCoE Windows Driver with NPIV Enabled When running the FCoE driver with NPIV enabled on Windows, the following features are not available with virtual port: * Adapter parameters settings * Adapter parameters restore default * Flash update from file * Saving flash to file * Adapter parameters update from file * Saving adapter parameters to file * Adapter parameters update from templates * Target link speed * Boot device settings * Driver settings

5 * Adapter beacon 6.2 Features Not Available When Running VMware ESX Driver When running the VMware ESX driver on a VMware OS, the following features are not available with virtual ports: * Adapter parameters settings * Adapter parameters restore default * Flash update from file * Flash save to file * Adapter parameters update from file * Adapter parameters save to file * Adapter parameters update from templates * iidma (intelligent interleaved direct memory access) settings * Boot device settings * Driver settings * Adapter beacon 6.3 Features Not Available when Running FCoE Sysfs Inbox Driver When running the FCoE Sysfs Inbox Driver on a Linux OS, the following features are not available: * Persistent binding * Selective LUN * Adapter port statistics * Driver settings 6.4 Warning Messages on Startup When launching QCC CLI, the following warning messages may appear on the console: * qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0) * qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0) The FCoE driver displays these messages when it is unable to read SFP data. You can safely ignore them. 6.5 VLAN & Teaming Driver Support The QConvergeConsole CLI s VLAN & Teaming features are not compatible with the older VLAN and Teaming drivers distributed with the SANsurfer Converged Network Adapter Networking CLI

6 versions and earlier. To use the QConvergeConsole CLI s VLAN & Teaming features, this old VLAN and Teaming driver must be removed and the newer VLAN and Teaming driver must be installed. This newer driver is available in the latest version of the QLogic Windows SuperInstaller. 6.6 VLAN & Teaming Save and Restore Features The QConvergeConsole CLI s VLAN & Teaming feature to save and restore VLAN and Teaming configuration uses a file format that is only valid for the QConvergeConsole CLI and is not compatible with any other applications at this time. 6.7 QLE82xx Internal and External Loopback Diagnostics Features At this time the internal and external loopback features are not supported on the QLE82xx for iscsi, FCoE, or NIC protocols. 6.8 iscsi QLE82xx Features Currently Not Supported At this time the following features are not supported for the QLE82xx with the iscsi protocol: - Retrieval of the firmware coredump record is not supported. - Configuration of the CNA level parameters is not supported, except for the CNA level alias. - Configuration of port (duplex, flow control, link speed, DCBX parameters is not supported. 6.9 QLogic iscsi IOCTL Module Required On Linux Operating Systems To properly discover QLE82xx iscsi ports on Linux operating systems a QLogic iscsi Linux IOCTL module is required to be installed and loaded. This IOCTL module, "qisioctl", is included in the iscsi Linux driver packages posted to the QLogic web site. Use the command "lsmod grep qis" to confirm that the IOCTL module, "qisioctl" is loaded. If this module is not loaded, then use the command "modprobe -v qisioctl" to load the module Actions prior to the installation/upgrade of drivers The QConvergeConsole Command Line Utility (QCC CLI) should be closed prior to installing or upgrading the FCoE, NIC or iscsi drivers: 6.11 Issue with the BSG on Oracle UEK An operating system patch to Oracle UEK is required to allow QCC CLI to run properly. Without this patch the application can lock up.

7 The patch fixes an operating system issue with BSG support. The patch is available at the following web link location (all three lines below need to be concatenated into one line in your web browser): a=commitdiff;h=84eb8fb42c120ff32b201c1cdd910033c888f699; hp=0f19bc681ed0849a2b a0a8132e3700e OS Hot fix for performance issues on Windows Server 2008 R2 Poor performance has been observed on some computers that have NUMA-based processors and are running Windows Server 2008 R2. This issue occurs for applications with threads that request a large amount of memory. A correction to this problem is available in Windows Server 2008 R2 SP1, but if the user cannot upgrade to SP1, then a hot fix is available at: Firmware for IPv6 support Firmware version or newer is required for IPv6 support RHEL6.0 Inbox iscsi driver info On RHEL6.0, Inbox iscsi driver does not have the interfaces to support QConvergeConsole GUI or QConvergeConsole CLI applications. Please download the RHEL6.0 Out of Box iscsi driver and QConvergeConsole applications from the QLogic web site RHEL6.x Installation of 32-bit compatibility libs Installation Sequence: * Select RHEL Server-x86_64-DVD1.iso to mount with Raritan to install system Kernel version : el6.x86_64 * Choose installation with Basic Video driver * Select Basic storage device * Install software for software development work machines and extra install compatibility libraries Compatibility library rpms list. Compat-db el6,x86_64 Compat-expat el6.x86_64 Comapt-glibc x86_64 Compat-libgfortran el6.x86_64 Compat-libstdc el6.x86_64 Compat-libstdc el6.x86_64 Compat-libtermcap el6.x86_64 Compat-openldap _ el6.x86_64 Openssl098e-0.9.8e-17.el6.x86_64

8 * Configure the network, make sure iptables/firewall is disabled * Install QCC CLI * Install below library RPMs in sequence. libxau el6.i686.rpm libxcb-1.5.1el6.i686.rpm libx el6.i686.rpm libxext el6.i686.rpm libxp el6.i686.rpm * Run QCC CLI application 6.16 RHEL6.x Releases, iscsi For RHEL6.x releases, external QLogic iscsi Linux driver and IOCTL packages are required to be installed to discover and manage the iscsi adapters. The inbox iscsi driver does not have the interfaces to support the QConvergeConsole CLI and SANsurfer iscsi HBA Manager applications. Download RHEL 6.x QLogic iscsi Linux driver and QConvergeConsole CLI from the QLogic driver downloads Web site Red Hat 6.x with the x86_x64 architecture, iscsi For QConvergeConsole CLI to install and run correctly on Red Hat 6.x with the x86_x64 architecture, you must install the additional packages listed in the following procedure: Installation Sequence: 1. Select RHEL Server-x86_64-DVD1.iso to mount with Raritan. to install the system kernel version el6.x86_ Choose the installation with the Basic Video driver. 3. Select the Basic storage device. 4. Install the software for "software development work machines" and extra install compatibility libraries: Compatibility library rpms list: Compat-db el6,x86_64 Compat-expat el6.x86_64 Comapt-glibc x86_64 Compat-libgfortran el6.x86_64 Compat-libstdc el6.x86_64 Compat-libstdc el6.x86_64 Compat-libtermcap el6.x86_64 Compat-openldap _ el6.x86_64 Openssl098e-0.9.8e-17.el6.x86_64 5. Configure the network and make sure iptables/firewall is

9 disabled. 6. Install SANsurfer iscsi CLI. 7. Install the library RPMs in the following sequence: libxau el6.i686.rpm libxcb-1.5.1el6.i686.rpm libx el6.i686.rpm libxext el6.i686.rpm libxp el6.i686.rpm 8. Run the SANsurfer iscsi CLI application SLES 11 SP1 Error Message, iscsi In some scenarios on SLES 11 SP1, the iscsi ports may not be discovered, and the following error message may be seen in the system error log: FATAL: module '/lib/modules/ default/extra/qlgc-qla4xxx/qisioctl.ko' is unsupported use --allow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules 1) Add the Module.supported file with the following contents in the qla4xxx directory to include qisioctl as a supported module for Sles11SP1: qla4xxx.ko external qisioctl.ko external 2) Rebuild the modules after the inclusion of the Module.supported file. 3) The qisioctl module should be loaded after loading the qla4xxx driver and before starting QConvergeConsole CLI: modprobe qisioctl NOTE: For details on building and installing the driver and IOCTL module, refer to the Linux driver readme iscsi QL4xxx cards support QConvergeConconsole CLI v and newer versions support iscsi QL4xxx cards. For Linux RHEL 4.x, 5.x and SLES 10 & 11 operating system versions a separate IOCTL module component, available on the QLogic driver downloads Web site, needs to be installed. For RHEL 6.x the iscsi Linux driver with IOCTL module support is available on the QLogic driver downloads Web site and needs to be installed A card reset if in a boot from SAN configuration Firmware flash update when in boot from SAN configuration: If the CNA is in either an iscsi or FCoE protocol boot from SAN configuration, then to ensure correct card reset logic protection is active, use the same protocol used for the boot from SAN configuration for firmware flash update commands. For example if configured for an iscsi boot from SAN configuration, then use the command line switch:

10 qaucli pr iscsi f <hba_port_inst> <MBI firmware flash file> If configured for an FCoE boot from SAN configuration, then use the command line switch: qaucli pr fc b <hba inst> <hba wwpn> <all> [-rg <all>] <img file> The above process will prevent a card reset when in a boot from SAN configuration that can cause unpredictable operating system behavior or in some cases cause the operating system to lock up Features Currently not Supported in Windows PE At this time the following features are not supported on Windows PE: - Virtual port - FCoE Information - DCBX Parameters (TLV) - Persistent binding - Selective LUN 6.22 Action prior to the installation/upgrade of QCC CLI The QCC GUI agents (NIC/iSCSI/FCoE) should be stopped prior to installing or upgrading the QConvergeConsole CLI. Make sure to restart all the QCC GUI agents once the QCC CLI installation is complete. 7. Known Issues and Workarounds 7.1 SLES 11 SP1 - Error message In some scenarios on SLES 11 SP1 the iscsi ports may not be discovered and the following error message may be seen in the system error log: FATAL: module /lib/modules/ default/extra/qlgc-qla4xxx/qisioctl.ko is unsupported use --allow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules Workaround: * Add Module.supported file with the following contents in qla4xxx directory to include qisioctl as a supported module for Sles11SP1: qla4xxx.ko external qisioctl.ko external * Rebuild the modules after inclusion of Module.supported file * qisioctl module should be loaded after loading qla4xxx driver and before starting QConvergeConsole CLI: modprobe qisioctl * NOTE: For details on building and installing the driver & IOCTL module refer to the Linux driver readme.

11 7.2 Smart Screen Filter feature on Windows platform Whenever you execute a file that you have downloaded from the Internet, it is first checked by SmartScreen Filter against a database. Files that cannot be identified are blocked automatically, and a warning is displayed instead. The only two options on the screen are the highlighted OK button, and a more info link that is nearly as distinguishable from the background. A click on OK closes the message and blocks the executable from being started. If you want to start the program, you need to click on More Info. You can disable SmartScreen Filter in the Windows Control Panel. Use Windows-Pause to bring it up, and click on Control Panel in the address bar afterwards. Select System and Security and then Action Center afterwards. Select Change SmartScreen Settings on the left. This opens a menu where you can turn Windows SmartScreen off. 7.3 Updating NIC parameters that affect the link, as well as running loopback test under a PXE boot issue Any operation that will result in loss of network connectivity shall not be performed when the rootfs is mounted over nfs. Loopback, some of the parameter updates can result in link loss and are not supported. 8. Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: support@qlogic.com Copyright All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.