OneCommand Manager Application for the Drivers for Linux Release Notes Version: 5.2.12.2-1 System: SLES 10 SP3 and SP4 (X86, X64 and PPC) SLES 11 SP1 (X86, X64, IA64 and PPC) RH 5.5(X86, X64, IA64 and PPC) RH 5.6 (X86, X64, IA64 and PPC) RH 5.7 (X86, X64, IA64 and PPC) RH 6.0 (X86, X64 and PPC) RHEL 6.1 (X86, X64 and PPC) Date: September 2011 Purpose and Contact Information These release notes describe the new features, resolved known issues and current known issues associated with this OneCommand Manager application version for the Emulex drivers for Linux release. For the latest product documentation, go to www.emulex.com. If you have questions or require additional information, contact an authorized Emulex technical support representative at tech.support@emulex.com, 800-854-7112 (US/Canada toll free), +1 714-885-3402 (US/International), or +44 1189-772929 (Europe, Middle East, and Africa). New Features 1. Host grouping display for discovery-tree fabric view. 2. Fabric-centric port selection is included on the Batch Operation dialog box. 3. In the discovery-tree, you can now search with the host name. 4. PCI Express bus speed and bus width information are added to a universal converged network adapter (UCNA) Info tab. 5. Supports diagnostic dumps for OneConnect OCe10102-x UCNAs and OneConnect OCe11102-x UCNAs. 6. Supports IPv6 remote management. 7. Supports OneConnect OCe11102-xT 10GBASE-T UCNAs. 8. New adapter management relative to application programming interfaces (APIs). New adapter management includes the Resource Management Application Programming Interface (RMAPI) library, Common Information Model (CIM) and Simple Network Management Protocol (SNMP). SNMP is supported for network interface card (NIC) and iscsi only. 9. View Vital Product Data (VPD) for NIC-only and iscsi OneConnect OCe1110x UCNAs. You cannot view NIC or iscsi VPD on the OneConnect OCe1010x UCNAs. OneCommand Manager Application for the Drivers for Linux Release Notes 1
Resolved Issues 1. When rapidly selecting or deleting iscsi targets from the One Command Manager application Target List box, a parse error message could have occurred. This issue has been corrected. Known Issues 1. For iscsi ports, if you enable the Dynamic Host Configuration Protocol (DHCP) from the Port Information tab s Modify TCP/IP Configuration dialog box and VLAN is already enabled, the following TCP/IP addresses may not be obtained from the DHCP server (remaining 0.0.0.0): IP address, subnet mask and gateway address. You may encounter this known issue if your DHCP Server is not VLAN-aware or is not configured for VLAN. Use one of the following workarounds: Use a DHCP Server that is VLAN-aware and properly configured. Follow these steps to disable and enable DHCP and VLAN: a) On the Port Information tab, click Modify. The Modify TCP/IP Configuration dialog box is displayed. b) Clear the VLAN Enabled and DHCP Enabled checkboxes. c) Click OK. The Port Information tab is displayed. d) On the Port Information tab, click Modify. The Modify TCP/IP Configuration dialog box is displayed. e) Check the VLAN Enabled and DHCP Enabled checkboxes. f) Click OK. 2. OneConnect OCe1010x UCNAs are not taken offline. When you start the diagnostic tests, there is the following message: "The test sequence you are about to run will result in taking the selected adapter off line... Click 'OK' to run the test, or 'Cancel to skip it.' However, when you click OK the adapter is NOT taken offline. Unplug the port on the OneConnect OCe1010x UCNA before running the desired diagnostic test. 3. Diffie-Hellman Challenge Handshake Authentication Protocol (DH-CHAP) is not supported on SLES 11 SP1 and RH6 systems. The fcauthd authentication daemon is supported for RH 5.5 and RH 5.7 systems. The fcauthd authentication daemon is not supported for SL11 SP1, RH 5.6 and RH6 systems. 4. OneConnect upgrade path order recommendation. When upgrading UCNA driver and firmware versions, it is best to upgrade both the driver and the firmware without any reboot in between to minimize the possibility of operating with mismatched versions of driver and firmware. OneCommand Manager Application for the Drivers for Linux Release Notes 2
5. The NIC driver must be installed to run the OneCommand Manager application on an FCoE adapter. If the OneConnect FCoE adapter is run without the NIC driver installed, many of the management functions are unavailable. The management functions that are unavailable are: 1. Firmware download Active and flash firmware versions Firmware status BIOS version Boot code version All diagnostics including beaconing Transceiver data display Port disable Physical port link status All CEE settings Event log display (CLI only) Diagnostic dumps 6. CLI (hbacmd.exe) path change. Prior to version 5.1, the hbacmd executable file was installed in /usr/sbin/hbanyware directory. For OneCommand Manager version 5.2, this installation directory has been moved to usr/sbin/ocmanager. However, to allow scripts with hard coded paths to the hbacmd executable in the hbanyware directory to continue to run, a copy of the hbacmd executable is still available in the hbanyware directory. 7. Restriction in assigning DCB priorities to priority groups. Although there are eight priority groups to which priorities can be assigned, you are able to assign priorities and bandwidths to only two of the priority groups. To one priority group you must assign the FCoE or iscsi priority and to the other priority group you must assign the other seven (NIC) priorities. Note: If you are using a DCBX enabled switch to configure the priority groups, configure it for only two priority groups to work correctly with the OneConnect adapter. 8. Requirement for unloading or loading Emulex Device Drivers (FC/FCoE, NIC and iscsi). If you load or unload an Emulex device driver for Linux (FC/FCoE, NIC and iscsi) after the machine is rebooted, you must perform the following steps in the following order: 1. Close any open Emulex OneCommand Manager applications. OneCommand Manager Application for the Drivers for Linux Release Notes 3
2. Restart OneCommand Manager application daemons. To restart OneCommand Manager application daemons, the daemons must be stopped and started. a) Run the /usr/sbin/ocmanager/stop_ocmanager script. b) Run the /usr/sbin/ocmanager/start_ocmanager script. 3. Run the Emulex OneCommand Manager application GUI and/or the CLI clients applications. 9. If both VLAN and DCBX are disabled, the iscsi priority configured in the CEE tab is not set in the iscsi packets sent out by the port. Enable or disable VLAN from the iscsi Port Info tab in the OneCommand Manager application. 10. DH-CHAP authentication is not supported for OneConnect adapters. There is currently no support for DH-CHAP authentication for OneConnect adapters. The DH-CHAP tab is not displayed by the OneCommand Manager application when an FCoE node of a OneConnect port is selected in the discovery-tree. In the CLI, authentication commands return an error indicating the command is not supported when the OneConnect FCoE port is specified. 11. DH-CHAP authentication is not supported on SLES 11 SP 1 and RH6 systems. The kernel has removed this feature from the FC device driver module layer. 12. Transceiver data is unavailable for OneConnect OCe11102x UCNAs. The transceiver data is not displayed in the OneCommand Manager application or the OneCommand Manager CLI for OneConnect OCe1110x UCNAs. 13. The adapter s WWN may interfere with the OneCommand Manager application s ability to make permanent changes to the adapter s WWN. Some newer adapters (for example, CNAs) on some newer systems employ techniques in the BIOS code at boot time to configure the adapter. This may include the adapter WWN. In such cases, this may interfere with the OneCommand Manager application s ability to make permanent (non-volatile) changes to the adapter s WWN. 14. iscsi InitialR2T is not supported for iscsi OneConnect adapters. Although both the OneCommand Manager application GUI and CLI (hbacmd) clients allow the configuring of the iscsi InitialR2T parameter to yes or no, the adapter does not recognize the setting. The adapter always operates with InitialR2T set to "yes". OneCommand Manager Application for the Drivers for Linux Release Notes 4
15. On SLES 11 SP1 and RH6.0 systems, an unavailable in-band remote OneCommand Manager host causes a 30-second window of vulnerability. When an in-band remote OneCommand Manager application host becomes unavailable for any reason (for example, a cable pull or a machine reboot) there is a 30 second window of vulnerability such that FC-CT commands originating from the SL11 SP1 machine to the remote host during this period hang due to a function call that generates an ioctl to the kernel that does not return. The calling process thread is hung. This problem is due to kernel code (new bsg interface) and a kernel fix is in process. This issue has been addressed in the RH6.1 kernel. Inclusion is also expected in SLES 11 SP2. Emulex recommends avoiding use of in-band management for SLES 11 SP1 and RH 6.0 systems. 16. FC-CT commands to the switch that timeout can cause the OneCommand Manager application processes to hang. The OneCommand Manager application uses FC-CT commands to the switch name server to obtain local HBA symbolic name information. FC-CT commands to the switch originating from a SL11 SP1 or RH6.0 machine that time out cause the OneCommand Manager application process sending the FC-CT command to hang. This problem has been found to be located in kernel code (new bsg interface) and a kernel fix is in process. Scenarios that might result in this behavior include disabling a switch port and modifying VLAN configuration either on the switch or on the host machine via the OneCommand Manager application. No workaround at this time. This issue has been addressed in the RH6.1 kernel. Inclusion is also expected in SLES11 SP2. 17. Messages appear on the terminal during Web-Launch install/uninstall. On Linux SLES11 SP1 systems, when the OneCommand Manager Web-launch feature is installed or uninstalled using wsinstall and wsuninstall scripts respectively, the following messages are displayed to the terminal. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. These are warning messages that do not affect the operation or installation of the Web-launch feature. They appear on SLES 11 SP1 specific versions of the relevant software (insserv and jexec). The scripts invoke this software via invocation of the standard Linux chkconfig utility typically used for daemon installations. None required. OneCommand Manager Application for the Drivers for Linux Release Notes 5
18. On SLES 11 systems, the Open-FCoE RPM package (open-fcoe-1.0.4-10.2) is incompatible with the OneCommand Manager application package and must be removed from the target host machine. The HBA API library that the open-fcoe package installs (libhbalinux.so.1) causes all OneCommand Manager application processes to crash with a segmentation violation. To recover you must reinstall OneCommand Manager application. 19. On RHEL 5.5 systems, the core kit (elxocmcore RPM) and enterprise kit (elxocm RPM) does not install due to a missing Libnl (NetLinks) library. The OneCommand Core RPM requires Libnl. Unlike other supported operating systems, RHEL 5.5 does not install the Libnl package during a default installation. Install the libnl package from the RHEL 5.5 distribution media. 20. On RHEL 5.5 systems, the OneCommand iscsi SNMP daemon does not start. The OneCommand iscsi SNMP daemon does not start if the package that holds the file is not found. s If the OneCommand Manager application is not installed, install the lm_sensors-2.10.0-3.1 or higher RPM from the Red Hat distribution media. Install the OneCommand Manager application. If the OneCommand Manager application is installed, run the stop_ocmanager script to stop the OneCommand Manager application daemons. Install the lm_sensors-2.10.0-3.1 or higher RPM from the Red Hat distribution media. Run the start_ocmanager script to start the OneCommand Manager application daemons. 21. On RHEL 5.4 x86 64 and ppc 64 systems, the Red Hat 32-bit and 64-bit libhbaapi RPMs treat /etc/hba.conf as a configuration file. If no application has modified /etc/hba.conf, this file is deleted when the Red Hat libhbaapi RPM is uninstalled. If an application has modified /etc/hba.conf (example: OneCommand Manager application), this file is moved to /etc/hba.conf.rpmsave when the Red Hat libhbaapi RPM is uninstalled. In either case, uninstalling the 32-bit or 64-bit Red Hat libhbaapi RPMs breaks the OneCommand Manager application because it requires Emulex entries in /etc/hba.conf. If the OneCommand Manager application is installed, do not uninstall the Red Hat 32-bit or 64-bit libhaapi RPM. 22. Unloading the NIC driver from the Linux machine causes the OneCommand Manager application to lose connectivity. If you unload the NIC driver from the Linux machine, any OneCommand Manager application (the GUI or the CLI client) running on the machine loses connectivity with the NIC and related configuration data. OneCommand Manager Application for the Drivers for Linux Release Notes 6
To recover, you must perform the following steps in the following order: 1. Stop the OneCommand Manager applications and daemons using the stop_ocmanager script. 2. Reload the NIC driver using modprobe. 3. Restart the OneCommand Manager application daemons using the start_ocmanager script. 4. Restart the desired OneCommand Manager application (GUI or CLI client). 23. When MILI and SNMP daemons start, they trigger warning messages within SELinux for certain operations. To avoid SElinux warning messages, disable SELinux. 1. To disable SElinux, open a terminal and enter the following command at prompt: echo 0 > /selinux/enforce 2. To enable SElinux, open a terminal and enter the following command at prompt: echo 1 > /selinux/enforce 24. A permanent driver parameter change fails if the system is rebooted too soon. When you make permanent driver parameter changes via the OneCommand Manager application, the application automatically makes the required entry in the /etc/modprobe.conf or equivalent file. Because the lpfc driver loads so early in the Linux machine boot sequence, the new contents of the /etc/modprobe.conf file must be re-inserted into the Linux system initrd file (via "mkinitrd" utility) for the driver to pick up the new driver parameter value on the next boot. Failure to generate the new initrd file causes the driver to fail to get the new driver parameter value on subsequent driver loads (machine boots). The OneCommand Manager application automatically does this for you (re-creates initrd via mkinit function); however, it can take as long as 45-60 seconds after the driver parameter is changed for a complete initrd re-build. Thus, if you reboot the machine immediately after the driver parameter change is made, the auto-recreation of the initrd file by the OneCommand Manager application may fail to complete. In these cases, this failure causes the driver to not obtain the new driver parameter value upon subsequent reboots. Wait a minimum of 45-60 seconds after making the driver parameter change before rebooting the machine. 25. An unaligned access message can appear on the Linux command shell. When running the HBACMD CLI client, the following unaligned access message can appear on the Linux command shell: elxdiscoveryd(24489): unaligned access to 0x200...008005f1c, ip=0x20...8fa680 These messages are "informational" only and do not cause any inaccuracies in the OneCommand Manager application configuration or status reporting. These messages are OneCommand Manager Application for the Drivers for Linux Release Notes 7
indications that the OneCommand Manager application code execution is sometimes referencing data aligned to four bytes instead of eight and the IA64 architecture issues a page fault to accomplish it (causing a slight performance hit). These messages can be turned off with the prtcl or dmesg Linux commands. 26. Requirement if Data Center Bridging (DCB) settings are connected to a non-dcbx switch. If DCB settings are required when connected to a non-dcbx switch (or a switch with DCBX disabled), DCBX must be disabled on the OneConnect adapter to use the adapter s configured parameters. If DCBX is enabled, DCB PFC and Priority Groups are ignored (the adapter assumes the switch does not support these features) and for FCoE adapters, the FCoE priority (COS) is 3. 27. Newly added LUNs on a storage array may not appear on the host machine Linux operating system or the OneCommand Manager application. Do one of the following: Run the following script from the command shell: /usr/sbin/lpfc/lun_scan all Reboot the host machine after the LUN has been added at the target array. 28. When using IET software, more than 60 iscsi targets may not be discovered. When using the open source iscsi Enterprise Target (IET) software package to present targets to the iscsi initiator, adding target portals that contain greater than 60 targets fails the resulting target discovery operation. This is due to an error in the IET target implementation. 29. Logged in iscsi targets retain login options through reboots. When an iscsi target is discovered by adding target portal, that target takes the target portal s login options. The target portal s login options are taken from the initiator login options. However, you can modify them when adding the target portal. If a target is discovered by isns, it gets its default login options from the initiator login options. Once a target is discovered, its login properties are not changed when the initiator login options are changed. When you log into a target, the login properties used at the time of login are remembered. If you reboot, the logged in targets are logged in again with the remembered login options (i.e. initiator login options are not used). When you remove the targets (and the target portal if that s how they were discovered) and then cause the targets to be rediscovered, the targets login properties are defined once again by how they are discovered as described at the beginning of this known issue. 30. A physical loopback diagnostic test fails if no transceiver is present on a OneConnect OCe1010x UCNA port. OneCommand Manager Application for the Drivers for Linux Release Notes 8
Insert a transceiver into the port before you run a physical loopback diagnostic test. 31. A MAC loopback diagnostic test may fail if the cable is plugged into a OneConnect OCe1010x UCNA port. Unplug the port on the OneConnect OCe1010x UCNA before running the MAC loopback diagnostic test. 32. On RHEL 6.0 and RHEL 6.1 systems, the OneCommand Manager application installation may fail as the OCM JRE required the RHEL6 library file: Libstdc++.5.so and that file is not installed by default. Install the compat-libstdc++-33 RPM included in the RHEL 6 distribution. 33. On RHEL 6.0 and RHEL 6.1 systems, an issue exists with the Java Runtime that may result in the inability to run OCManager on a RHEL 6 host. This problem usually occurs on Blade platforms. This issue causes the OneCommand Manager application to crash immediately upon invocation. Use one of the following management methods: Command Line Utility (HBACMD) Manage the problematic RHEL 6 host from a remote host that is running the OneCommand Manager application. Install WebLaunch services on the RHEL6 host, then point a browser on another host to that RHEL 6 host. 34. When you start a diagnostic test on a OneConnect OCe1010x UCNA port, the following message is displayed: "The test sequence you are about to run will result in taking the selected adapter off line... Click 'OK' to run the test, or 'Cancel to skip it.' However, after you click OK, the adapter is not taken offline. Unplug the port on the OneConnect OCe1010x UCNA before running the desired diagnostic test. 35. An end-to-end (ECHO) diagnostic test fails if the corresponding targets are not supported. Check to be sure the connect targets are supported. 36. On a OneConnect OCe1110x UCNA, running tests using the Diagnostics tab may result in an IOCTL error 0x45. None required. This error only appears in the MILI log (not out to the display) and can safely be ignored. OneCommand Manager Application for the Drivers for Linux Release Notes 9
37. On an OneConnect OCe1110x UCNA, installing or uninstalling the OneCommand Manager application may result in an IOCTL error 0x45. None required. This error only appears in the MILI log (not out to the display) and can safely be ignored. Technical Tips 1. In the OneCommand Manager application version 5.1, the basic and advanced login options were in different dialog boxes. In the OneCommand Manager application version 5.2, the iscsi Target Discovery tab includes these basic and advanced login options: Manually Add Target Add Portal Target Login Copyright 2011 Emulex. All rights reserved worldwide. This document refers to various companies and products by their trade names. In most, if not all cases, their respective companies claim these designations as trademarks or registered trademarks. This information is provided for reference only. Although this information is believed to be accurate and reliable at the time of publication, Emulex assumes no responsibility for errors or omissions. Emulex reserves the right to make changes or corrections without notice. This report is the property of Emulex and may not be duplicated without permission from the Company. OneCommand Manager Application for the Drivers for Linux Release Notes 10