Driver for Linux Release Notes
Contents
1. copyright the software and 2 offer you this license which gives you legal permission to copy distribute and or modify the software Also for each author s protection and ours we want to make certain that everyone understands that there is no warranty for this free software If the software is modified by someone else and passed on we want its recipients to know that what they have is not the original so that any problems introduced by others will not reflect on the original authors reputations Finally any free program is threatened constantly by software patents We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses in effect making the program proprietary To prevent this we have made it clear that any patent must be licensed for everyone s free use or not licensed at all The precise terms and conditions for copying distribution and modification follow TERMS AND CONDITIONS FOR COPYING DISTRIBUTION AND MODIFICATION 0 This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License The Program below refers to any such program or work and a work based on the Program means either the Program or any derivative work under copyright law that is to say a work containing the Program or a portion of it either verbatim or with modifications and or translated into2. 0 13_0 27 in their name For example rpm Uhv elx lpfc kmp default 8 3 7 27 3 0 13 0 27 1 slesllsp2 x86 64 rpm 11 LILO Boot Loader is not supported on i386 and x86_64 architectures The LILO Boot Loader on i386 and x86_64 architectures is not supported for this driver If the LILO boot loader is used after the LPFC driver package is installed and upon reboot an incorrect initial ramdisk is used and the system might not boot correctly Workaround The boot loader supported with this driver is GRUB which is the default boot loader for most of the Linux distributions LILO is an older boot loader used on i386 and x86_64 architectures only GRUB works correctly with the driver package s installation script 12 Suspend to disk command results in a kernel Oops If you attempt to suspend to disk using the command echo disk gt sys power state the LPFC driver encounters a kernel Oops The sysfs parameter sys power state is used to suspend and resume the system The LPFC driver does not support the suspend to disk and resume command Do not attempt to use this sysfs parameter when the LPFC driver is loaded Workaround None 13 Potential error messages during the driver kit removal process As part of the driver kit removal process initiated via the Ipfc install u command the previous in box LPFC driver version which was saved as part of the current driver kit install process is restored and becomes the active dri
3. 76 0 11 default k vmlinuz 3 0 76 0 11 default f iscsi Features e acpi e dm e multipathd e kms e block e usb e network e multipath e kpartx e resume userspace e resume kernel e kdump SLES 11 SP2 example linux 8vq8 boot mkinitrd i initrd 3 0 13 0 27 default k vmlinuz 3 0 13 0 27 default f iscsi Features e acpi e dm e multipathd Driver for Linux Release Notes 16 P010082 01A Rev A J M gt Q EMULEX e block e usb e iscsi e multipath e kpartx e resume userspace e resume kernel g To automatically include the iSCSI script to login to the boot iSCSI target boot the system using open be2iscsi Reboot the system and wait until it fails to mount root and exits into a command shell h Run the following commands from the command shell to login to the boot target iscsid n iscsiadm m fw l i Type exit to exit the shell and the system will continue to boot with the iSCSI target j After the system has booted up with the open be2iscsi driver using the workaround the boot initrd must be regenerated to include iscsi sh Note iscsi sh is needed for the init script to login to the iSCSI boot target This workaround is required because mkinitrd will only include iscsi sh in the initrd if there is an entry such as sys firmware iscsi_boot which can only be created if Open iSCSI boot is enabled In addition f multipath must be added to the mkinitrd command if multipath is being use
4. However this causes all multicast traffic to be received Driver for Linux Release Notes 8 P010082 01A Rev A gt EMULEX e Alternatively you can configure the unicast IPv6 address assigned to the VM interface on the MacVTap interface in the hypervisor This results in the Ethernet mcast MAC address being configured in the NIC interface Use the following command ifconfig macvtap lt x gt inet6 add lt ipv6 address gt where macvtap lt x gt is the MacVTap interface in the hypervisor and lt ipv6 address gt is the unicast IPv6 address assigned to the VM interface 4 When SR IOV is enabled NIC priority group PG and priority flow control PFC are not supported Workaround None 5 In certain skews of controllers when the driver is loaded with num_vfs 32 the initialization of two of the VFs fails and only 30 VF interfaces are created Workaround None 6 In certain configurations timeout errors may occur during maximum performance MPx socket testing Workaround For Linux Xen e Only configure interfaces created with the netfront source model and ignore the second set of interfaces created with 8139cp For Linux KVM e Use the virtio device model instead of Hypervisor Default 7 When using bonding on top of VLANS on a RHEL based system networking appears to hang during system boot or when restarting the network On a RHEL based system having a bond on top of a VLAN while using
5. THERE IS NO WARRANTY FOR THE PROGRAM TO THE EXTENT PERMITTED BY APPLICABLE LAW EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESSED OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU SHOULD THE PROGRAM PROVE DEFECTIVE YOU ASSUME THE COST OF ALL NECESSARY SERVICING REPAIR OR CORRECTION 12 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER OR ANY OTHER PARTY WHO MAY MODIFY AND OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE BE LIABLE TO YOU FOR DAMAGES INCLUDING ANY GENERAL SPECIAL INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES Driver for Linux Release Notes 20 P010082 01A Rev A
6. To find the module parameters supported by an LPFC driver module type modinfo lt driver dir gt lpfc ko 14 Potential connection loss due to an FCF Failover issue with a Cisco FCoE switch An issue was discovered with Cisco Nexus 5000 series FCoE switch firmware 4 1 3 N2 1 or earlier in NPV mode that may cause the loss or interruption of SCSI connections when used with the Emulex OneConnect UCNAs The switch incorrectly sends out a Discovery Advertisement to All ENode MACs from the FCF MAC with which the FC uplink was down The end result is that sometimes the UCNA hangs on to an offline FCF or experiences back to back FCF failover and it may potentially lead to a Linux SCSI mid layer devloss timeout Workaround It has been verified that Cisco s 4 2 1 N1 1 release has corrected the issue Emulex highly recommends that you upgrade your Cisco Nexus 5000 series FCoE switch firmware to 4 2 1 N1 1 or later to avoid this issue If you decide to use 4 1 3 N2 1 or earlier firmware with your Cisco Nexus 5000 series FCoE switch and this issue is encountered increase the FC transport dev_loss_tmo parameter to 60 seconds This can be accomplished in one of two ways e Update the FC transport dev_loss_tmo parameter For example echo 60 gt sys class fc_remote ports rport 3 0 1 dev_loss_tmo or e Update the LPFC driver s lpfc_nodev_tmo parameter For example echo 60 gt sys class scsi_host host3 lpfc_ nodev_tmo 15 Potential multip
7. at all For example if a patent license would not permit royalty free redistribution of the Program by all those who receive copies directly or indirectly through you then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program If any portion of this section is held invalid or unenforceable under any particular circumstance the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system it is up to the author donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License 8 If the distribution and or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces the original copyright holder who places the Program under this License may add an explicit geographical
8. 0 series adapter with the open iSCSI driver the OEMSEAaddSendTargetPortal command does not work Workaround When installing a new SLES 11u1x32 or SLES 11u2x32 operating system ensure that the open iSCSI rpm package that came on the installation CD is used during the installation Other rpm packages may not work Copyright 2012 2014 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 Note References to OCe11100 series products also apply to OCe11100R series products Driver for Linux Release Notes 18 P010082 01A Rev A gt EMULEX GNU GENERAL PUBLIC LICENSE Version 2 June 1991 Copyright C 1989 1991 Free Software Foundation Inc 51 Franklin Street Fifth Floor Boston MA 02110 1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document but changing it is not allowed Preamble The licenses for most software are designed to take away your free
9. ONBOOT yes can cause the system to hang during boot or when restarting the network The system will appear to hang while trying to start one of the slave interfaces For example if you have a configuration similar to the following DEVICE bond0 ROADCAST 10 255 255 255 ATEWAY 10 0 0 254 ETMASK 255 0 0 0 B G IPADDR 10 0 0 14 N ONBOOT yes BONDING OPTS mode 0 miimon 100 DEVICE eth2 2 BOOTPROTO none ONBOOT yes Driver for Linux Release Notes 9 P010082 01A Rev A y M gt Q EMULEX MASTER bond0 SLAVE yes VLAN yes DEVICE eth3 2 BOOTPROTO none ONBOOT yes MASTER bond0 SLAVE yes VLAN yes This system hangs because the RHEL networking scripts try to bring up the eth2 2 and eth3 2 interfaces twice It will bring them up once because the bonding interface specifies them as slave interfaces and then it tries to bring them up a second time because it sees the ONBOOT yes parameter on a VLAN device The issue occurs because after the devices are first brought up the MAC addresses of the interfaces changes Usually the first interface s MAC address is set on the rest of the interfaces When the device is brought up a second time the MAC address of the interface no longer matches the HWADDR field The network scripts will wait for an interface with a matching MAC address to appear which does not occur Workaround Set the ONBOOT parameter to n
10. SCS Select or a new unique one Note The name must conform to the standard ION c Optional step Change directory to boot copy the default initrd to a new name and create a boot entry in boot grub menu Ist for this new initrd name using the same kernel This step ensures that the system can still boot if something goes wrong d Install the Emulex Open iSCSI driver rpm file e If this is not an iSCSI boot system reboot and follow the Open iSCSI instructions to log into targets you do not need to continue following these steps If this is an iSCSI boot system that previously used the proprietary iSCSI driver do not reboot Instead continue with the next step f Change directory to boot rebuild the initrd to include the iscsi feature The output of this command lists the capabilities included in the initrd Make sure iscsi is listed This option includes capabilities such as iscsiadm in the initrd For example linux fiai boot mkinitrd i initrd 3 0 76 0 11 default k vmlinuz 3 0 76 0 11 default f iscsi g The previous step did not include the iSCSI script to log into the boot iSCSI target To include it automatically boot the system using the Emulex Open iSCSI driver Reboot the system and wait until it fails to mount root and exit into a command shell h Run the following command from the command shell to log into the boot target iscsiadm m fw l i Exit the shell using exit for the system to contin
11. another language Hereinafter translation is included without limitation in the term modification Each licensee is addressed as you Activities other than copying distribution and modification are not covered by this License they are outside its scope The act of running the Program is not restricted and the output from the Program is covered only if its contents constitute a work based on the Program independent of having been made by running the Program Whether that is true depends on what the Program does 1 You may copy and distribute verbatim copies of the Program s source code as you receive it in any medium provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty keep intact all the notices that refer to this License and to the absence of any warranty and give any other recipients of the Program a copy of this License along with the Program You may charge a fee for the physical act of transferring a copy and you may at your option offer warranty protection in exchange for a fee 2 You may modify your copy or copies of the Program or any portion of it thus forming a work based on the Program and copy and distribute such modifications or work under the terms of Section 1 above provided that you also meet all of these conditions a You must cause the modified files to carry prominent notices stating that you changed the files and the date of any cha
12. ath path loss on the SLES 11 SP3 operating system During the controller failback test multipath cannot recover all paths For SLES 11 SP3 there is a new uid_attribute method to obtain the LUN serial number which is defined in the multipath conf file This method will call scsi_id to send the sg_io If any IOs are returned with a busy status multipath will not reinstate that path Work around Edit the multipath conf file and replace uid attribute ID SERIAL with getuid callout lib dev scsi_id whitelisted device dev n Driver for Linux Release Notes 7 P010082 01A Rev A gt EMULEX NIC 1 ifconfig displays RUNNING flag when the cable is not connected This is a known issue in the Linux operating system stack Workaround Use ip link show to properly display the Oper status value 2 Incertain skews of controllers PING is not working when attempting to bridge the 1G or 10G ports to the virtual machines when SR IOV is enabled for 10G ports in the BIOS This issue occurs due to limitations of the virtual Ethernet bridge All transmitted broadcast packets are looped back by the controller This affects the functionality of the Linux bridge as it appears as if the same ARP broadcast packets are received on two different interfaces Workaround a Set the aging of the bridge to 0 using the following command brctl setageing lt bridge gt 0 This causes the bridge to behave like a hu
13. b and flood the packet to all the ports except the one on which the packet arrived every time This may impact performance If you have only two interfaces on this bridge one NIC interface and virbr0 nic there is no performance impact b Another option may be to use the MacVTap interface to the guest instead of the bridge interface The MacVTap interface is only available in the RHEL 6 3 or newer kernels 3 Unable to ping the RHEL 6 4 KVM guest VM from a remote host when using the MacVTap driver and IPv6 When an IPV6 unicast address is configured the Linux kernel also configures an Ethernet multicast MAC address in the format 33 33 xx xx xx xx In the context of a guest operating system VM the mcast address that needs to be configured comes into existence after the VM is booted up and the unicast IPv6 address is configured in the guest operating system When using a MacVTap interface to bridge the NIC interface to the VM s interface the previously mentioned Ethernet MAC address configuration in the VM does not reach the MacVTap interface automatically Since the MacVTap interface does not put the NIC interface into promiscuous mode this results in an IPv6 ping failure from the remote host to the VM s interface Workaround Select one of the following workaround options e Use the following command ifconfig eth lt x gt allmulti where eth lt x gt is the interface in the hypervisor to which the MacVTap interface is bridged
14. boot it has to be the same name used in iSCSIselect One method to obtain the current adapter iqn when running the proprietary be2iscsi is cat sys class scsi_ host host4 adapter iqn etc iscsi initiator name iscsi Example InitiatorName iqn 1996 04 de suse 01 619c53c296b2 Driver for Linux Release Notes 15 P010082 01A Rev A c e gt EMULEX Optional step Change the directory to boot copy the default initrd to a new name and create a boot entry in boot grub menu I st for this new initrd name using the same kernel This step ensures that the system can still be rebooted if something unexpected occurs Install the be2iscsi Open iSCSI driver rpm SLES 11 SP 2 example linux 8vq8 SLES11 64 rpm Uhv be2iscsi kmp default 10 0 739 0 3 0 13 0 27 1 slesllsp2 x86 64 rpm SLES 11 SP 3 example linux oe3a tmp rpm Uhv be2iscsi kmp default 10 0 713 0 3 0 76 0 11 1 slesllsp3 x86 64 rpm If this is a non iSCSI boot system reboot and follow the Open iSCSI instructions to login to targets If this is an iSCSI boot system that previously used the proprietary be2iscsi do not reboot continue to the next step Change directory to boot and rebuild the initrd to include the iSCSI feature The output of this command will list the features included in the initrd Note Make sure iSCSI is listed This feature will include iscsiadm in the initrd SLES 11 SP 3 example linux oe3a boot mkinitrd i initrd 3 0
15. cables replace each cable one at a time and allow discovery to finish before replacing the next cable To determine if discovery is finished read the state sysfs parameter e When swapping cables allow devloss timeout to fire before replacing the cables this fails all outstanding I O 10 Driver package installation failure may occur when installing on systems with SLES11 SP2 maintenance kernel version 3 0 80 0 7 The SLES11 SP2 maintenance kernel release with version 3 0 80 0 7 has a kernel version higher than the latest SLES11 SP3 GM release which was 3 0 76 0 11 1 This is a non standard kernel versioning scheme that is used by Linux operating system vendors See the related SuSE KB article at https www suse com support kb doc php id 7012717 This non standard versioning scheme causes the Emulex driver package installation scripts to fail when an attempt is made to install the packages on this specific SLES11 SP2 maintenance release Workaround To install the driver on this specific SLES11 SP2 maintenance kernel version 3 0 80 0 7 you should not use the driver package s installation script Instead you should manually install the driver binary RPM built for the SLES11 SP2 GM kernel version 3 0 13 0 27 Driver for Linux Release Notes 5 P010082 01A Rev A gt EMULEX and corresponds to the architecture of the target system for example x86_64 PPC and so on These driver binary RPMs include the kernel version 3
16. cted automatically When the open iSCSI be2iscsi driver is installed as bootable any non bootable iSCSI LUNs configured in iSCSISelect will not get detected automatically Configure the isCSI LUNs using iscsiadm or the OneCommand Manager application 6 When Oracle UEK 6 5 x64 and RHEL 6 x and 5 x systems are used with the OCe14102 UM adapter with iSCSI NIC enabled iSCSI BIOS can fail to boot from the iSCSI LUN and kernel panic can occur Workaround a Boot the system with the rdshell option in the kernel parameter When the system cannot find or mount the boot partition it will exit to the basic command shell b Manually run iscsistart b This will add the boot target to the system c Type exit and the system will continue to boot normally Driver for Linux Release Notes 13 P010082 01A Rev A gt EMULEX Technical Tips 1 On systems running RHEL 6 4 or later when upgrading or downgrading from the proprietary be2iscsi driver to the open be2iscsi driver you must install the Dracut network RPM package and pass the netroot command parameter into Dracut to build the initramfs image To update the proprietary iSCSI driver to the Open iSCSI driver for SLES 11 SP2 and later you must do the following a Make sure the Open iSCSI package is installed If it is not mount the installation CD and install it b Edit etc iscsi initiatorname iscsi to add the initiator IQN name This name can be the same name as in i
17. d SLES 11 SP3 example linux oe3a boot mkinitrd i initrd 3 0 76 0 11 default k vmlinuz 3 0 76 0 11 default f multipath Features e acpi e dm e multipathd e kms e block e usb e network e iSCSI e multipath e kpartx e resume userspace e resume kernel Driver for Linux Release Notes 17 P010082 01A Rev A gt EMULEX SLES 11 SP2 example linux 8vq8 boot mkinitrd i initrd 3 0 13 0 27 default k vmlinuz 3 0 13 0 27 default f multipath Features e acpi e dm e multipathd e block e usb e iSCSI e multipath e kpartx e resume userspace e resume kernel k Reboot the system again it should boot normally 1 If the system has other non boot iSCSI targets follow the Open iSCSI instructions to log in to those targets 5 Additional physical NICs added to the XenServer do not show up in the XenCenter Workaround See the following link for instructions on adding an additional physical NIC to the XenServer http support citrix com article CTX121615 6 The Open iSCSI driver persistent targets are maintained in the Host Nodes database The driver recognizes only the boot target that is persistent and is not aware of any non boot persistent targets on the adapter Recommendation Do not use iSCSISelect to configure persistent non boot targets for all variants of RHEL 6 RHEL 7 and SLES 11 releases 7 When the SLES 11u1x32 or SLES 11u2x32 operating systems are used with the OCe1110
18. distribution limitation excluding those countries so that distribution is permitted only in or among countries not thus excluded In such case this License incorporates the limitation as if written in the body of this License 9 The Free Software Foundation may publish revised and or new versions of the General Public License from time to time Such new versions will be similar in spirit to the present version but may differ in detail to address new problems or concerns Each version is given a distinguishing version number If the Program specifies a version number of this License which applies to it and any later version you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation If the Program does not specify a version number of this License you may choose any version ever published by the Free Software Foundation 10 If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different write to the author to ask for permission For software which is copyrighted by the Free Software Foundation write to the Free Software Foundation we sometimes make exceptions for this Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally NO WARRANTY 11 BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE
19. dom to share and change it By contrast the GNU General Public License is intended to guarantee your freedom to share and change free software to make sure the software is free for all its users This General Public License applies to most of the Free Software Foundation s software and to any other program whose authors commit to using it Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead You can apply it to your programs too When we speak of free software we are referring to freedom not price Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software and charge for this service if you wish that you receive source code or can get it if you want it that you can change the software or use pieces of it in new free programs and that you know you can do these things To protect your rights we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights These restrictions translate to certain responsibilities for you if you distribute copies of the software or if you modify it For example if you distribute copies of such a program whether gratis or for a fee you must give the recipients all the rights that you have You must make sure that they too receive or can get the source code And you must show them these terms so they know their rights We protect your rights with two steps 1
20. e incorrect references to ethX Y For more information see https bugzilla redhat com show_bug cgi id 723936 8 The 16Gb LPe16000B and LPe16002B adapters are not supported with the RHEL 5 9 and RHEL 6 4 inbox FC FCoE drivers The RHEL 5 9 inbox FC FCoE LPFC driver version 8 2 0 128 3p and the RHEL 6 4 inbox FC FCoE LPFC driver version 8 3 5 86 1p do not support the 16Gb LPe16000B and LPe16002B adapters PCI Express 3 0 Bus Type However these driver versions do support the 16Gb LPe16000 and LPe16002 adapters PCI Express 2 0 Bus Type In Boot from Storage Area Network SAN configurations over the unsupported LPe16000B and LPe16002B adapters the process of booting from SAN will fail In standard local disk boot configurations although the FC FCoE driver will load upon system boot the target storage LUNs will not be discovered Note You can use the Linux lspci utility to determine whether an adapter is LPe1600xB or LPe1600x and therefore whether it is supported by the RHEL 5 9 inbox LPFC driver version 8 2 0 128 3p or the RHEL 6 4 inbox LPFC driver version 8 3 5 86 1p Executing the lspci x Linux utility displays the PCI configuration space for each device in the form of lt bus slot function info gt lt strings matching vendor id etc gt OO xx XX KX XX 10 xx XX XX XX For example for the Emulex 16Gb adapter 0a 00 1 Fibre Channel Emulex Corporation Lancer X LightPulse Fibre Channel Host Ada
21. ease Notes 1 P010082 01A Rev A gt EMULEX Known Issues Firmware version 10 2 370 19 includes new features that required new flash regions to support them Firmware versions earlier than 10 0 803 37 did not have the ability to configure the flash regions to support these new features If you are updating from a firmware version earlier than 10 0 803 37 use one of these methods to update the firmware to 10 2 370 19 e Use the ISO flash tool e Use the released 10 2 version of the ethtool utility You must perform the firmware update procedure twice to ensure that the flash regions are properly configured and you must reboot the system after each firmware update Note Do not use Linux inbox drivers when performing the firmware update Note After you have updated the firmware you must not downgrade the firmware to a version earlier than 10 0 803 37 If you are updating from firmware version 10 0 803 37 or later use one of these methods to update the firmware to 10 2 370 19 e Use the ISO flash tool e Use the released 10 2 version of the ethtool utility and reboot the system after the firmware update It is not necessary to perform the firmware update process twice Note Do not use Linux inbox drivers when performing the firmware update Note After you have updated the firmware you must not downgrade the firmware to a version earlier than 10 0 803 37 FC FCoE 1 Link Aggregation Control Protocol LACP cannot be
22. en recreate a new interface discovery and login Driver for Linux Release Notes 12 P010082 01A Rev A gt EMULEX 3 There is a known Dracut issue that occurs on some systems with specific network settings where iSCSI BIOS can fail to boot from the iSCSI LUN and kernel panic can occur Workaround a Boot the system with the rdshell option in the kernel parameter When the system cannot find or mount the boot partition it will exit to the basic command shell b Manually run iscsistart b This will add the boot target to the system c Type exit and the system will continue to boot normally 4 The open iSCSI driver be2iscsi depends on some operating systems utilities and packages If these packages are not present the session establishment may not be possible after successful installation of the driver rpm Normally a system previously installed with iSCSI hardware will have these packages installed automatically In some corner cases such as a new iSCSI adapter that was installed after the operating system installation these rpm packages will need to be installed manually These packages can be found on the installation CD For RHEL 6 x and RHEL 7 the dependencies will be e dracut network e iscsi initiator utils For SLES 11 SPx the dependency will be e open iscsi 5 Insystems with an open iSCSI be2iscsi driver installed but not used as bootable any iSCSI LUN configured in iSCSISelect will not get dete
23. nge b You must cause any work that you distribute or publish that in whole or in part contains or is derived from the Program or any part thereof to be licensed as a whole at no charge to all third parties under the terms of this License c If the modified program normally reads commands interactively when run you must cause it when started running for such interactive use in the most ordinary way to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty or else saying that you provide a warranty and that users may redistribute the program under these conditions and telling the user how to view a copy of this License Exception if the Program itself is interactive but does not normally print such an announcement your work based on the Program is not required to print an announcement These requirements apply to the modified work as a whole If identifiable sections of that work are not derived from the Program and can be reasonably considered independent and separate works in themselves then this License and its terms do not apply to those sections when you distribute them as separate works But when you distribute the same sections as part of a whole which is a work based on the Program the distribution of the whole must be on the terms of this License whose permissions for other licensees extend to the entire whole and thus to each and every part regardless of who wrote it Th
24. o on the slave interfaces This prevents the system network scripts from trying to bring up the interface a second time This will not negatively affect the operation of the bonded interface because the ifcfg bond0 file still has ONBOOT set to yes The networking scripts will attempt to bring up the bond0 interface on boot which will cause the slave interfaces to be brought up and configured correctly If you are only using bonding without VLAN the network scripts do not bring up slave interfaces so the issue is avoided The issue occurs only when bonding is on top of VLAN interfaces 8 The description for OCe14102 U3 D shows as unknown device 0720 in the Xen Center for Xen 6 1 Workaround Run the update pciid command to display the correct adapter name 9 Firmware dump using ethtool W is not supported for the OCe14000 series adapters Workaround None 10 When a CNA is configured for a NIC iSCSI profile the NIC and iSCSI traffic can be configured to share the total bandwidth In such a scenario the NIC traffic will be assured a minimum bandwidth In such a configuration a VF interface will inherit the minimum bandwidth of the PF while the OneCommand Manager and BIOS components will display the minimum and maximum bandwidths configured and the PF will display the total bandwidth available Driver for Linux Release Notes 10 P010082 01A Rev A gt EMULEX 11 The following log message was not included in the Linux D
25. pter 00 daf 10 00 e2 46 00 10 00 00 00 04 Oc 10 00 80 00 Driver for Linux Release Notes 4 P010082 01A Rev A gt EMULEX 10 Oc 00 cd f1 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 df 10 00 e2 30 00 00 00 00 54 00 00 00 00 00 00 00 Ob 02 00 00 The 9th byte offset 0x8 of the PCI configuration space of the LPe1600x LPe1600xB adapters indicates the Revision ID register value of the adapter e If the Revision ID register value is 0x00 this represents an LPe1600x adapter e Ifthe Revision ID register value is 0x10 this represents an LPe1600xB adapter In the example above the value of the byte with offset 0x8 is 0x00 therefore this represents an LPe1600x adapter so the RHEL 5 9 inbox FC FCoE LPFC driver version 8 2 0 128 3p and RHEL 6 4 inbox FC FCoE LPFC driver version 8 3 5 86 1p do support this adapter Workaround Support for the 16Gb LPe16000B and LPe16002B adapters will be provided with the FC FCoE LPFC driver included in the RHEL 6 5 release In addition support is provided for the RHEL 5 9 and later releases through independent out of box FC FCoE LPFC driver packages hosted on the Emulex website 9 Devloss timeout after swapping ports The driver may not finish discovery when two initiator ports are swapped This causes all devices accessible through one or both of these initiator ports to time out and all I O to fail Workaround Do one of the following e When swapping
26. rivers manual in the Ethernet Driver Log Messages and their Description section Ethernet Log Message Description Type Debug data event lt DDDD gt These log messages are generated by firmware to identify Information lt DDDD gt lt DDDD gt lt DDDD gt certain infrequent hardware and firmware events and aid further analysis if required These messages by themselves are not indicative of any problem Data from these logs may help Emulex troubleshoot other problems if any that are observed along with these messages 12 Assigning VFs to a VM on the SLES Operating System To assign VFs to the VM in the SLES Xen kernel the VF must be unbound from the NIC module and then bound to the pciback module Note In the following steps 0000 07 0b 5 is used as an example To match those instances to the port that you want to use you will need to select the entry which matches the PCI bus device or function which corresponds to the port that you want to assign The ethtool utility can be used to determine this information such as ethtool i eth0 where eth0 is the interface you want to assign a Load the pciback driver modprobe pciback b Navigate to the sys bus pci drivers pciback directory and ensure that the following is displayed Panama Slesllsp2 sys bus pci drivers pciback ls lrt total 0 WroTTttnr 1 root root 4096 Sep 5 15 29 unbind E 1 root root 4096 Sep 5 15 29 uevent Spese 1 root roo
27. root 0 Sep 5 15 32 0000 07 0b 0 gt devices pci0000 00 0000 00 09 0 0000 07 0b 0 d Unbind the VF from the be2net driver echo n 0000 07 0b 5 gt sys bus pci drivers be2net unbind e Bind the driver to the pciback module echo n 0000 07 0b 5 gt sys bus pci drivers pciback new slot echo n 0000 07 0b 5 gt sys bus pci drivers pciback bind f Navigate to the directory sys bus pci drivers pciback and ensure that the device 0000 07 0b 5 is listed under it In addition check that dmesg logs report the same device g You can now launch qemu kvm and attach VF 0000 07 0b 5 to any desired VM iSCSI 1 The limitations specified in the iSCSI Driver Configuration section of the Emulex Drivers for Linux User Manual also apply to Appendix A of the user manual 2 The Open iSCSI administration utility binds the MAC address of each iSCSI port as an identity to create a configuration database If a MAC address for an iSCSI port changes the configuration data will be invalid MAC addresses can be changed via firmware updates or by changing the profile or personality of the adapter Non boot persistent sessions will no longer work Therefore all previously mounted partitions will not be found When iscsid attempts to open sessions through the iscsi port with a changed MAC address expect to see the following message beiscsi_ep connect shost is NULL Workaround Clean up the saved configuration and th
28. t 4096 Sep 5 15 29 slots De N 1 root root 4096 Sep 5 15 29 remove slot Wasa 1 root root 4096 Sep 5 15 29 remove _ id Ywr n 1 root root 4096 Sep 5 15 29 quirks Ywr n 1 root root 4096 Sep 5 15 29 permissive s snas 1 root root 4096 Sep 5 15 29 new id lrwxrwxrwx 1 root root 0 Sep 5 15 29 module gt module pciback a SSeS aS 1 root root 4096 Sep 5 15 34 new slot T 1 root root 4096 Sep 5 15 34 bind c Navigate to the sys bus pci drivers be2net directory and ensure that the following is displayed 0 n 1 root root 4096 Sep 5 15 32 uevent m 1 root root 4096 Sep 5 15 32 remove_id e S 1 root root 4096 Sep 5 15 32 new id Driver for Linux Release Notes 11 P010082 01A Rev A gt EMULEX lrwxrwxrwx 1 root root 0 Sep 5 15 32 module gt module be2net 0 n 1 root root 4096 Sep 5 15 32 bind W An 1 root root 4096 Sep 5 15 33 unbind lrwxrwxrwx 1 root root 0 Sep 5 15 32 0000 07 0b 5 gt Aevices pci0000 00 0000 00 09 0 0000 07 0p 5 lrwxrwxrwx 1 root root 0 Sep 5 15 32 0000 07 0b 4 gt devices pci0000 00 0000 00 09 0 0000 07 0b 4 lrwxrwxrwx 1 root root 0 Sep 5 15 32 0000 07 0b 3 gt devices pci0000 00 0000 00 09 0 0000 07 0b 3 lrwxrwxrwx 1 root root 0 Sep 5 15 32 0000 07 0b 2 gt devices pci0000 00 0000 00 09 0 0000 07 0b 2 lrwxrwxrwx 1 root root 0 Sep 5 15 32 0000 07 0b 1 gt devices pci0000 00 0000 00 09 0 0000 07 0b 1 lrwxrwxrwx 1 root
29. ted so long as such parties remain in full compliance 5 You are not required to accept this License since you have not signed it However nothing else grants you permission to modify or distribute the Program or its derivative works These actions are prohibited by law if you do not accept this License Therefore by modifying or distributing the Program or any work based on the Program you indicate your acceptance of this License to do so and all its terms and conditions for copying distributing or modifying the Program or works based on it 6 Each time you redistribute the Program or any work based on the Program the recipient automatically receives a license from the original licensor to copy distribute or modify the Program subject to these terms and conditions You may not impose any further restrictions on the recipients exercise of the rights granted herein You are not responsible for enforcing compliance by third parties to this License 7 If as a consequence of a court judgment or allegation of patent infringement or for any other reason not limited to patent issues conditions are imposed on you whether by court order agreement or otherwise that contradict the conditions of this License they do not excuse you from the conditions of this License If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations then as a consequence you may not distribute the Program
30. this package is not already installed on your system it is available from the Oracle Linux 5 LATEST channel on the Unbreakable Linux Network Advisory ELBA 2013 2544 released Aug 29 2013 and from Oracle s public yum at http public yum oracle com repo OracleLinux OL5 latest Note Package updates are not required in Oracle Linux 6 Unbreakable Enterprise Kernel systems You can perform this update when the UCNA is online and passing network or storage traffic To update the Ethernet firmware image a Copy the latest firmware image to the lib firmware directory using the following command cp be3flash ufi lib firmware b Start the update process using the following command ethtool f eth lt X gt be3flash ufi 0 c Reboot the system to enable the new firmware image 4 Upgrading the be2iscsi driver from proprietary to Open iSCSI in SLES11 SP2 and SP3 a Ensure that the Open iSCSI package is installed If it is not mount the installation CD and install it SLES 11 SP 3 example linux oe3a media SLES 11 SP3 DVD x86 6407031 SuSE x86 64 rpm ihv open iscsi 2 0 873 0 21 1 x86 64 rpm SLES 11 SP 2 example linux 8vq8 media SLES 11 SP2 DVD x86 6407551 SuSE x86 64 rpm ihv open iscsi 2 0 872 0 35 1 x86 64 rpm b Edit etc iSCSI initiatorname iscsi to add the initiator iqn name This name can be the same name as in iSCSIselect or a new unique one Note The name must conform to the standard iqn and for iSCSI
31. ue to boot with the iSCSI target j Regenerate the boot initrd to include iscsi sh iscsi sh is needed for the initialization script to log into the iSCSI boot target This is necessary because mkinitrd will include iscsi sh in the initrd only if there is an entry such as sys firmware iscsi_boot which can only be created under Open iSCSI boot k Reboot the system again It should boot normally 1 If the system has other non boot iSCSI targets follow the Open iSCSI instruction to log into those targets 2 Red Hat does not officially support saving kdump files to iSCSI targets In RHEL 6 4 and later to save kdump files to iSCSI targets a The system must reserve at least 256 MB for the crash dump Issue the kernel command with the option crashkernel 256M Reboot the system for this change to take effect Driver for Linux Release Notes 14 P010082 01A Rev A gt EMULEX b Copy the initramfs image to the initrd kdump image or build a new initramfs image using Dracut and rename it to initrd kdump c Restart the kdump service 3 Updating OneConnect UCNA firmware in Oracle Linux 5 Unbreakable Enterprise Kernel systems The Emulex Ethernet driver for OneConnect adapters supports updating the firmware image in the UCNA flash through the request_firmware interface in Linux For Oracle Linux 5 Unbreakable Enterprise Kernel systems an updated version of the ethtool package ethtool 6 4 0 1 el5 lt arch gt rpm is required If
32. und The Emulex driver kit installation script always places the LPFC module at the end of the INITRD_MODULES list before building the initrd image However if this problem is Driver for Linux Release Notes 3 P010082 01A Rev A gt EMULEX observed make sure no SCSI drivers are added right after the LPFC module in the INITRD_MODULES list 7 The physical interface can improperly name eth0 123 when the etc sysconfig network scripts ifcfg eth0 123 file contains a HWADDR declaration When using VLAN on RHEL 6 x the main interface is not created and the VLAN interface does not actually work correctly as a VLAN This is an issue with the udev script in RHEL 6 x In RHEL 6 x the udev scripts interpret the HWADDR field in an ifcfg ethX Y configuration file to mean that the configuration belongs to a real interface It does not check for the existence of the VLAN field to exclude the field as a real interface Therefore you may see unpredictable behavior when including the HWADDR field in the ifcfg ethX Y file for a VLAN The setting may or may not work When this setting does not work it is because the scripts have created or renamed the main interface as ethX Y instead of just ethX Later when adding the VLAN interface it fails because ethX does not exist Workaround Remove the HWADDR line in ifcfg ethX Y files that refer to VLAN configurations You must also clean up the etc udev rules d 70 persistent net rules file to remove all th
33. us it is not the intent of this section to claim rights or contest your rights to work written entirely by you rather the intent is to exercise the right to control the distribution of derivative or collective works based on the Program In addition mere aggregation of another work not based on the Program with the Program or with a work based on the Program on a volume of a storage or distribution medium does not bring the other work under the scope of this License 3 You may copy and distribute the Program or a work based on it under Section 2 in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following a Accompany it with the complete corresponding machine readable source code which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange or b Accompany it with a written offer valid for at least three years to give any third party for a charge no more than your cost of physically performing source distribution a complete machine readable copy of the corresponding source code to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange or c Accompany it with the information you received as to the offer to distribute corresponding source code This alternative is allowed only for noncommercial distribution and only if you received the program in object code or e
34. used on the same port as FCoE or iSCSI Workaround None 2 PCI Hot Plug may cause applications such as the OneCommand Manager application or third party applications that use the Emulex libraries for example HBAAPI to misbehave or malfunction Workaround a Stop all applications that are accessing LPFC s HBAAPI interface OneCommand Manager application or third party applications before performing PCI Hot Plug of an LPFC adapter b Use the following command to stop the OneCommand Manager application usr sbin hbanyware stop ocmanager c After performing PCI Hot Plug of the adapter you can restart the applications Driver for Linux Release Notes 2 P010082 01A Rev A gt EMULEX 3 Deletion of Vports PCI Hot Unplug On occasion the kernel might report SCSI errors when deleting Vports via the sysfs interface or performing a PCI Hot Unplug of an Emulex adapter kernel Synchronizing SCSI cache for disk kernel FAILED Or SCSI error return code 0x00010000 Workaround None These messages do not indicate a functional failure and can be ignored 4 Deleting Vports while devices are in use Emulex provides management utilities that allow you to delete Vports However there is no mechanism for the LPFC driver to detect whether devices accessed through that Vport are in use This means you can delete a Vport when devices accessible through the Vport are mounted or when I O is outstanding to the device When file s
35. ver However the driver kit un install process does not remove any entries in the Linux distribution configuration file modprobe conf As such parameters that would have been valid for the just removed driver versions and entered in the modprobe conf file are also used to load the just restored in box driver version This can potentially create problems when e The just removed driver version might include module parameters that did not exist in the older just restored driver version e One or more of these module parameters are included in the configuration file modprobe conf If the above criteria are met an error message may be displayed during the uninstallation process of the driver kit such as Loading LPFC Driver FATAL Error inserting lpfc lib modules lt kernel_revision gt kernel drivers scsi lpfc lpfc ko Unknown symbol in module or unknown parameter s dmesg For example this issue can be observed when uninstalling an 8 2 0 x driver kit which had DH CHAP functionality enabled on a Linux distribution with an older 8 1 10 x in box driver version Driver for Linux Release Notes 6 P010082 01A Rev A gt EMULEX Workaround If such an error is seen during the kit removal process edit the Linux configuration file modprobe conf and remove all entries that list LPFC driver module parameters that is entries that start with options lpfc s s Then attempt to uninstall the driver kit again Note
36. xecutable form with such an offer in accord with Subsection b above The source code for a work means the preferred form of the work for making modifications to it For an executable work complete source code means all the source code for all modules it contains plus any associated interface definition files plus the scripts used to control compilation and installation of the executable However as a special exception the source code distributed need not include anything that is normally distributed in either source or binary form with the major components compiler kernel and so on of the operating system on which the executable runs unless that component itself accompanies the executable Driver for Linux Release Notes 19 P010082 01A Rev A gt EMULEX If distribution of executable or object code is made by offering access to copy from a designated place then offering equivalent access to copy the source code from the same place counts as distribution of the source code even though third parties are not compelled to copy the source along with the object code 4 You may not copy modify sublicense or distribute the Program except as expressly provided under this License Any attempt otherwise to copy modify sublicense or distribute the Program is void and will automatically terminate your rights under this License However parties who have received copies or rights from you under this License will not have their licenses termina
37. y M gt S EMULEX Driver for Linux Release Notes Versions Driver for Linux FC FCoE Version 10 2 370 12 RHEL SLES OL Driver for Linux NIC Version 10 2 363 0 RHEL SLES OL Debian Ubuntu Driver for Linux Open iSCSI Version 10 2 365 0 RHEL 6 SLES 11 OL Driver for Linux Proprietary iSCSI Version 10 0 719 1009 RHEL 5 OL Date September 2014 Purpose and Contact Information These release notes describe the new features resolved known issues and current known issues associated with these Emulex driver for Linux releases 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 e Supports up to four functions per port on 4 port OCe14000 series adapters when Alternate Routing ID Interpretation ARI is available e Supports the Red Hat Enterprise Linux RHEL 7 operating system Note RoCE support is available as a Technical Preview offering See the RoCE Driver for Linux Technical Preview Guide for more information Resolved Issues FC FCoE There are no resolved issues for this release NIC There are no resolved issues for this release iSCSI There are no resolved issues for this release Driver for Linux Rel
38. ystems are mounted on Vports and Vports are deleted the file systems still appear to be mounted however they will be inaccessible Workaround Before deleting Vports you must prepare the system affected by the Vport deletion accordingly by unmounting all the devices accessible through the Vports and ensuring there is no outstanding I O 5 Support of 4Gb s adapters in Direct I O virtualized environments Default driver configuration fails to initialize 4 Gb s adapters in virtualized environments that use Direct I O or SFPT This may result in a system hang or an uninitialized LPFC adapter in Intel VT d and AMD V IOMMU systems Workaround In these virtualized environments that use Direct I O or SFPT and 4 Gb s adapters you must load the LPFC driver with the following driver parameters set e lpfc_hostmem_hgp 1 e lpfc_sli_mode 2 For example modprobe lpfc lpfc_ hostmem 1 lpfc sli mode 2 Note A consequence of this resolution is that virtual ports are no longer supported by the LPFC driver when the Ipfc_sli_mode parameter is set to 2 6 Order of LPFC module in the initrd module list On SLES 11 systems if another SCSI driver such as aic79xx is loaded right behind the LPFC driver through the initrd image the SCSI mid layer discovery process may be interrupted on the LUNs connected to the LPFC driver This causes the SCSI discovery reference count put on the LPFC driver to not release and the LPFC driver cannot unload Workaro
Download Pdf Manuals
Related Search