Home

Emulex Drivers for Linux User Manual

Contents

1. 4 Installing into an Upgraded Kernel ccccecccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetes 4 Uninstalling the Source based RPM FC and FCoE Driver Kit eeen 5 Installing the Binary RPM FC and FCoE Driver Kit cc eeeeeeeeeeeeeeeeeeeee eens 5 Uninstalling the Binary RPM FC and FCoE Driver Kit eeens 6 Installing the Ethernet Driver Kit ccssseeneseceeeeeeeeceesenneeceneoennereeeeeeens 7 Uninstalling the Ethernet Driver Kit 00 0 0 8 Installing the iSCSI Driver Wil s csccceoecdasstececctecedcesdennasacsceeeddescece decteateeemeeccents 8 Uninstalling the iSCSI Driver Kit nn de 9 Booting From a Non Zero LUN Attached to an Emulex Adapter 9 Installing the OneCommand Manager Application ceeeeeeeeeeeeeeeeeeeeeees 10 ConfiguratiOm sssini amaaa aaa a aa ei Eaa aa 11 FC and FCoE Driver Configuration icsciesccsssecssetoncsccu iad cdeencterends sacetinncnederwoeaials 11 FC and FCoE Driver Configuration Methods Using modprobe and letc modprobe conf ec cceeeeeeeeeeeeeeecaeeeeeeeeeeeeeeaaaaeeeeeeeeeecaaaaeeeeeeeeeessaaaeeeeseeeeeesaaaeeees 11 Temporary Configuration Method 0 cccceeeeeeeeceeneeeeeeeeeeeaeeeeeeeeeeeeeaaeananeeees 11 Persistent Configuration Method i iii iiiiiiireeenees 11 Temporary FC and FCoE Driver Configuration by Read Write to sysfs 12 Creating a New Ramdisk Image 00 00 nnn nn nnn nn nn nn innit 13
2. Cannot See Multiple Zones from the Management Server Cannot see multiple zones on the same screen of my management server running the OneCommand Manager application version 5 2 Provide a physical FC connection into each of the zones For each zone you want to see connect an Emulex OneCommand Manager application version 5 2 enabled port into that zone Use Out of Band discovery Ethernet to connect to the undiscovered server Linux iSCSI Situations and their Resolutions The following table provides Linux iSCSI troubleshooting information for the OneConnect UCNA Table 10 Linux iSCSI Situations and their Resolutions Situation Resolution When you logout of a target while I O is running and you log into the target again you will get an error trace in var log messages beginning with the error message trying to free buffer There is no solution to this issue Emulex Drivers for Linux User Manual Troubleshooting Page 38 gt EMULEX Table 10 Linux iSCSI Situations and their Resolutions Continued Situation Resolution With SLES11 SP1 you cannot upgrade from an iSCSI v2 0 driver to an iSCSI v2 3 or 2 4 driver using the elx_iscsi_install sh script provided with the package The script will indicate the installation is complete but modinfo or OCM will still display the older version of the driver and a system reboot will not upgrade the driver
3. uninstall option Type elx_net_install sh uninstall Installing the iSCSI Driver Kit The iSCSI driver kit includes the driver that supports the iSCSI protocol The iSCSI driver kit consists of the following e A zipped tar file that includes the driver binary RPMs for a specific driver version and for all of the supported Linux distribution kernels Note The driver binary RPM packages only support officially released Linux distribution kernels and do not support subsequent errata kernels or pre release distribution kernels e An installation script elx_iscsi_install sh which installs by default the iSCSI driver binary RPM that corresponds to the target system s architecture and kernel memory variant e A README file that provides a description of the kit structure its contents and distribution support scope Once the RPM is installed the elx_net_install script creates a new ramdisk for the currently running kernel so that the iSCSI driver is loaded when the kernel is initialized during system startup Note The OneCommand Manager application must be installed separately from the driver Refer to the Installing the OneCommand Manager Application on page 10 for more information To install the iSCSI driver for Linux 1 Install a supported Emulex adapter in the system Refer to the adapter s installation manual for specific hardware installation instructions 2 Remove any previously installed iSCS
4. For Installed FC and FCoE Driver Kits ccccccceceneeeeeeeeeceeeeeeeeeeeeeeeeeaeees 13 For Distribution In Box FC and FCoE Drivers cceceeeceeeeeeeeeeeeeeeeeeeeaes 13 Dynamically Adding LUNs and Targets c ccsesceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeesaaaaaaaaeeeeeees 13 FC and FCoE Driver Parameters Reference Table cceeceeeteeeeeetteteneeeeenteeennnee 14 Using udev for Persistent NAMing cccccccccccecceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetntas 17 Using udev to Discover Logical to Physical Mappings for sd Devices 17 Configuring the System to Boot From SAN Using Persistent Names 18 Using udev with st D VICES cc ecccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteeees 18 Further Information About Persistent Names cceeeeeeeeeeeeeeeeeeeeeeeneeees 20 Emulex Drivers for Linux User Manual Page iv gt EMULEX NIC Driver C nfig ratiO N csiis ie e aeaa aaa 20 iSCSI Driver Configuration seeeeeseseeeeereseeesrrrrrrrrtrrrrresssrrrrrterrrrrnrrnssrrr rrene 20 Interrupt Moderation Policy Settings ce eeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaaeeaaaaaaaaaaaaaaaaaaeeeeeees 22 Working with Virtual Ports VPOMS scsccciencicstecteatsitmentbucddducstiacictantdeeeddtuagevavioes 23 Creating Deleting and Displaying VPorts 00 0 0 rr i ii niin 23 The mkvport sh Script ccccccccceeeeeeeeeeeeeeeaeeeeeeeeeee
5. gt EMULEX Table 9 General Driver Situations and their Resolutions Continued Situation Resolution The Emulex driver for Linux does not load in ramdisk for a custom built kernel Custom built kernels are not supported by Emulex However the Emulex install script attempts to install the driver into a ramdisk that follows the naming scheme used by Red Hat or SLES kernels The SLES naming scheme for IA64 ramdisk images is boot efi efi suse initrd e The SLES naming scheme for ramdisk images on all other architectures is boot initrd If a custom built kernel has a ramdisk image that does not follow the appropriate naming scheme the name of the image can be changed using the following procedure 1 Change the name of the ramdisk image to match the SLES naming scheme 2 Update any file links to the ramdisk image 3 Edit the boot loader configuration file i e etc lilo conf etc yaboot conf boot grub grub conf boot grub menu Ist find any references to the old ramdisk image name and replace them with the new name 4 Reboot the system to verify the changes 5 Install the Emulex Ipfc Linux driver kit The Linux SCSI subsystem only sees 8 LUNs when more are present Some SCSI drivers will not scan past eight LUNs when the target reports as a SCSI 2 device Force SCSI bus scan with usr sbin Ipfc lun_scan SUSE supplies bin rescan scsi bus sh which can be changed to scan everything
6. 2 Stop the OneCommand Manager application version 5 2 3 Stop Device Mapper rmmod of Ipfc driver hangs and module reference count is 0 Emulex Drivers for Linux User Manual Troubleshooting Due to a small race condition in the kernel it is possible for an rmmod command to hang Issue the rmmod w command If this does not help reboot the computer Page 35 gt EMULEX Table 9 General Driver Situations and their Resolutions Continued Situation Resolution rmmod fails to unload driver due to Device or resource busy This message occurs when you attempt to remove the driver without first stopping the OneCommand Manager application version 5 2 or the fcauthd daemon when the OneCommand Manager application version 5 2 is installed and running or when FC disks connected to a LightPulse adapter are mounted Stop the OneCommand Manager application version 5 2 before attempting to unload the driver The script is located in the usr sbin hbanyware directory Type stop_ocmanager Unmount any disks connected to the adapter Unload the driver Type rmmod Ipfcdfc Type rmmod Ipfc An Ispci shows recent Emulex adapters as unknown This is because of the delay of getting new product ID s into the Linux development cycle Slow targets or extended link faults on the storage side may result in storage being marked off line by the mid layer and remaining off line not recovered when the lin
7. LOG_SLI ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 53 gt EMULEX elx_mes2518 Requested to send 0 NOP mailbox cmd DESCRIPTION DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes2520 NOP mailbox command failed status x x add_status x x mbx status x x shdr_status shdr_add_ status rc DESCRIPTION The NOP mailbox command has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes2539 Dropped frame rctl lt RCTL TYPE gt type lt FH TYPE gt DESCRIPTION The receive frame has an unsupported RCTL or FH_TYPE DATA None SEVERITY Warning LOG LOG_ELS ACTION None required elx_mes2540 Ring lt ring gt handler unexpected Rctl lt fh_rctl gt Type lt fh_type gt DESCRIPTION The received frame has an unsupported RCTL or FH_TYPE DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes2542 Try to issue mailbox command lt vpi gt lt mbxCommand gt synchronously ahead of async mailbox command queue DESCRIPTION Attempting to send a synchronous mailbox command ahead of the asynchronous mailbox commands DATA 1 sli4_mbx_opcode 2 sli_flag 3 flag SEVERITY Warning LOG LOG_MBOX LOG_SLI ACTION None required elx_mes2559 Block sgl registration required DMA size lt reqlen gt great than a page DESCRIPTION Attempting to register more SGEs with the firmware than can fi
8. Reset link speed to auto lt cfg_link_speed gt DESCRIPTION The driver is reinitializing the link speed to auto detect DATA None SEVERITY Warning LOG LOG_LINK_EVENT verbose ACTION None required elx_mes1304 Link Up Event ALPA map DESCRIPTION A link up event was received DATA 1 wd1 2 wd2 3 wd3 4 wd4 SEVERITY Warning LOG LOG_LINK_EVENT verbose ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network elx_mes1801 Create vport work array FAILED cannot do scsi_host_get DESCRIPTION The driver was unable to get a reference to a SCSI host DATA None SEVERITY Warning LOG LOG_VPORT verbose ACTION Software driver warning If this problem persists report these errors to Technical Support elx_mes1816 FLOGI NPIV supported response data lt port gt DESCRIPTION The fabric reports support for NPIV upon FLOGI DATA 1 response_multiple_NPort SEVERITY Warning LOG LOG_VPORT verbose ACTION No action needed informational elx_mes1817 Fabric does not support NPIV configuring single port mode DESCRIPTION The fabric reports no support for NPIV upon FLOGI DATA None SEVERITY Warning LOG LOG_VPORT verbose ACTION No action needed informational elx_mes2004 Failed to allocate XRI last XRITAG is lt XRI gt Max XRI is lt MAX_XRI gt Used XRI is lt USED_XRI gt DESCRIPTION All XRIs are in use DATA None SEVERITY Warning LOG
9. This entry displays the maximum number of VPorts that are supported by the fc_hosts underlying hardware This sysfs entry will only exist if the vport_create and vport_delete sysfs entries exist If an fc_host does not support NPIV then this sysfs entry may not exist Note Use this sysfs entry along with npiv_vports_inuse to determine whether the maximum number of VPorts have been created on this fc_host vport_create write WWPN sys class fc_host hostX vport_create only WWNN This entry creates a VPort on the physical port that hostX is located on The new VPort will have present a WWPN and WWNN on the fabric as indicated by the WWPN and WWNN that is input to this sysfs entry This sysfs entry will return a 0 if the VPort creation was successful A non zero value indicates that the VPort failed to be created If an fc_host does not support NPIV then this sysfs entry may not exist Note It is possible for the VPort creation to succeed but for the VPort to be in a failed or inoperative state Use the new sysfs tree created by the new VPort to check the state of the new VPort Emulex Drivers for Linux User Manual Configuration Page 26 Table 7 VPort sysfs Entries Continued gt EMULEX VPort sysfs Entries Type ae Location and Description vport_delete write WWPN sys class fc_host hostX vport_ delete only WWNN This entry deletes a VPort on the physical port that hostX is locate
10. X RHEL 6 1 5 2 11 1 X XenServer 5 6 SPx and 6 0 Emulex Drivers for Linux User Manual Page iii gt EMULEX Table of Contents Installaatio Mieis asaan eaea aaa aa scene eases enc adden ene 1 Driver Information sctscracamnctssuceansbnsactaines bn icstndsiesnssanaiaindensmsadisdantesndidenasacessntbesantentinies 1 Supported Features cccccccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeecaaeeeeeeeeeeeeeeaaaeeeeeeeeeeeaaaeeeeteeeeeeeaas 1 New Features in this Release cccccceeecceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaaageeeeeeeeeeaaaaneeneeees 1 PHEPEQUISILOS iios cceea antes cave cual eealuedavevivanecealede dived ivaue dened eadedivevetned aude AEA aa 2 COP AI h geeerreereeeee reer E creer reer reer tes teres rhein len ste namrere crete str 2 Prior to Download 0 ccc cceeeeeeeeeeeeeceeeeeeeeeeeeeeeeaaaeeeeeeeeeeeeaaaaaeeeeeeeeeesaaaaaeeeeeeeseeeaaaeneeeeeess 2 IKMOWMISSUCS niaaa ohacatahacttats tans tasantanaetatanasahatsceneemtase e A 2 Installing the Source based RPM FC and FCoE Driver Kit seeeeeees 3 Install Script Options 20 0 2 ccc cee eeeeee cece cee eeeeeeeeee eee eaaaaaeeeeeeeeeeaaaaeeeeeeeeeesaaaaeeeeeeeeeeeeaaaaees 4 Directory Structure sisisi iiia A A A A A AT A A E 4 Installing on Unsupported Linux Distributions eceeecccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaaeeees 4 Upgrading the Kernel or Applying a Distribution Service Pack or Update
11. exit all applications that use Fibre Channel attached drives then unmount the drives If you cannot exit all applications that use Fibre Channel attached drives the uninstall works properly but you must reboot after the uninstallation is complete 3 Stop the OneCommand Manager application version 5 2 Type cd usr sbin ocmanager stop_ocmanager 4 Uninstall the Applications Kit Refer to the OneCommand Manager Application Version 5 2 User Manual on the Emulex website for instructions 5 Copy the Ipfc install script to the temporary directory For example cp usr src lpfc lpfc install tmp 6 Execute the LPFC install script with the uninstall option Type tmp lpfc install uninstall Installing the Binary RPM FC and FCoE Driver Kit The binary RPM FC and FCoE driver kit includes the driver that supports the FC and FCoE protocols The binary RPM FC and FCoE driver kit consists of the following e A zipped tar file that includes the driver binary RPMs for a specific driver version and Linux distribution Note The driver binary RPM packages only support officially released Linux distribution kernels and do not support subsequent errata kernels or pre release distribution kernels If errata kernel support is required the standard source based RPM FC and FCoE driver kit should be used instead e An installation script elx_lpfc_install sh which installs by default the FC and FCoE driver binary RPM that corresponds
12. The Ethernet driver kit consists of the following e A zipped tar file that includes the driver binary RPMs for a specific driver version and for all of the supported Linux distribution kernels Note The driver binary RPM packages only support officially released Linux distribution kernels and do not support subsequent errata kernels or pre release distribution kernels e An installation script elx_net_install sh which installs by default the Ethernet driver binary RPM that corresponds to the target system s architecture and kernel memory variant e A README file that provides a description of the kit structure its contents and distribution support scope Once the RPM is installed the elx_net_install script creates a new ramdisk for the currently running kernel so that the Ethernet driver is loaded when the kernel is initialized during system startup Note The OneCommand Manager application must be installed separately from the driver Refer to the Installing the OneCommand Manager Application on page 10 for more information To install the Ethernet driver for Linux 1 Install a supported Emulex adapter in the system Refer to the adapter s installation manual for specific hardware installation instructions 2 Remove any previously installed Ethernet driver kits and or Application Helper Modules that were installed from the Emulex CD or downloaded from the Emulex website i e not part of a distribution s
13. You must supply the physical port s host number WWPN and WWNN when using the mkvport sh script Note It is possible for a VPort to be created successfully but be in failed state For example loop devices and NPIV are not supported on the same port simultaneously If you are running a loop topology and you create a VPort the VPort s link state will be off line The rmvport sh Script You can use the rmvport script to delete VPorts To see the usage information run the script with no parameters specified The rmvport sh script uses the following syntax rmvport sh lt Virtual Port s Host number gt Or rmvport sh lt Port Name gt lt Node Name gt For example gt rmvport sh 10000000c94ac63a 20010000c94ac63a would delete the VPort with port name of 10000000c94ac63a and node name of 20010000c94ac63a This script will fail if the VPort is not deleted and may take up to 30 seconds to complete Note You must un map un mount and flush I O to VPort connected devices before deleting the VPort The Isvport sh Script You can use the Isvport script to list the VPorts and physical ports that are present on the system Run the script with no parameters to display port information For example root curly scripts lsvport sh lpfcO host6 10000000c93a5b5e 20000000c93a5b5e LP10000 NPIV Not Supported lpfcl host7 10000000c93a5b5d 20000000c93a5b5d LP10000 NPIV Not Supported lpfc2 host8 10000000c93cc
14. and x86_64 e SCSI FCP e FCP 2 FC Tape profile including use of ADISC instead of PLOGI e FC initiator mode and FCoE e Tested up to 32 adapter ports e Dynamic parameter setting using the Emulex OneCommand Manager application as part of a master kit enabling GUl based driver configuration and persistent binding management including in band FC and out of band TCP IP remote SAN management capability diagnostics loopback and diagnostics dump virtual port support personality change and more See the OneCommand Manager Application Version 5 2 User Manual on the Emulex website for a complete list of supported features e Support for common host bus adapter application programming interface HBA API e Batch firmware download capability e Support for the sysfs interface e PCI hot plug support e Vital Product Data VPD support e Linux Tools hyperlink provided in the Linux portion on the Emulex website e Supports NPIV virtual ports New Features in this Release e Support for OneConnect OCe11102 xT 10GBASE T UCNAs Support for the RHEL 6 1 driver e Support for the XenServer 6 0 driver Emulex Drivers for Linux User Manual Installation Page 1 56 EMULEX Prerequisites To install the standalone driver kits the appropriate distribution kernel development packages must be installed for the currently running kernel which include the gcc compiler and the kernel sources The standalone driver kits s
15. atomic_read amp ndlp gt kref refcount DESCRIPTION A kref_put was called again after the node was already inactive DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0276 lpfc_nlp_get ndlp x pusgmap x x refcnt d void ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION A kref_get was attempted on a node that was being released DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0277 Ipfc_enable_node ndlp x pusgmap x x refcnt d void ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION Enable node was attempted on an inactive node DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0278 Ipfc_enable_node ndlp x pusgmap x x refent d void ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION Enable node was attempted on an inactive node DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0280 Ipfc_cleanup_node ndlp x pusgmap x x refcnt d void ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION Node clean up was attempted on a node that has already been marked for memory free DATA None SEVERITY Warning LOG LOG_NODE ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 46 gt EMULEX elx_mes0281 Ipfc_cleanup_node ndlp x pusgmap x x refcnt d v
16. change Variable Default Min Max Comments Ipfc_cr_count 1 1 255 This parameter determines the values for I O coalescing for cr_count outstanding commands Not applicable for OneConnect UCNAs Ipfc_cr_delay 0 0 63 This parameter determines the values for I O coalescing for cr_delay msec outstanding commands Not applicable for OneConnect UCNAs Ipfc_devloss_tmo 30 0 255 Seconds to hold I O error if device disappears Ipfc_fdmi_on 0 0 2 False 0 if disabled 1 or 2 if enabled depending on type of support needed Ipfc_link_speed 0 0 auto select Sets link speed 1 1 Gb s Note This variable does not affect FCoE 10 Gb s 2 2 Gb s capable adapters 4 4 Gb s 8 8 Gb s Ipfc_log_verbose 0x0 0x0 Oxffff bit mask Extra activity logging Emulex Drivers for Linux User Manual Configuration Page 16 gt G EMULEX Table 3 LPFC Dynamic Parameters Do not require a driver reload to change Continued Variable Default Min Max Comments Ipfc_nodev_tmo 30 1 255 Seconds to hold I O error if device disappears depreciated This parameter will not work if you altered lpfc_devloss_tmo Note This is a deprecated field and Ipfc_devloss_tmo should be used instead Ipfc_pci_max_read 2048 512 1024 2048 Maximum DMA read byte count 4096 Ipfc_poll 0 1 poll with Sets FCP ring polling mode control interrupts enabled 3 poll and disable FCP ring interrupts Ipfc_
17. failed The Power On Self Test of the UCNA failed This is an indication of a hardware or firmware issue Try rebooting the system after a reset Error Emulex OneConnect 10Gbps Initialization of the UCNA or allocation of some NIC initialization faileg source for initializing the driver failed In most cases this message is accompanied by another more specific error message Try rebooting the system after power cycling If the issue persists this could be a symptom of a hardware issue or corrupted firmware Error mbox_db poll timed out A firmware command did not complete in reasonable time This is most likely due to a firmware or hardware issue Try rebooting the system Error Invalid mailbox The driver got an unexpected completion status completion for a firmware command Error Error in cmd completion A firmware command failed with the indicated status compl extd status code and extended status code lt DDD gt lt DDD gt Warning MSIX request IRQ failed The request for MSIX interrupt registration failed err lt DDD gt The driver should still work with INTx interrupts Warning Module param rx frag_size An unsupported receive buffer size was passed must be 2048 4096 8192 for module parameter rx_frag_size The driver will ae ignore the specified value and work with the Using 2048 default RX buffer size of 2048 Warning MTU must be between 256 Request to change the MTU was issued with and 9000 bytes invalid MTU The reques
18. following command tar xzf elx lpfc dd lt Linux distribution version gt lt driver version gt tar gz 5 Change to the directory that is extracted cd elx lpfc dd lt Linux distribution version gt lt driver version gt 6 Execute the elx_Ipfc_install script with no options to install the new driver kit Type elx_lpfc_install sh Once the elx_Ipfc_install script has completed successfully the Emulex new FC and FCoE driver is loaded and devices that are properly connected to the system are accessible Reboot the system now to enable the newly added driver options in the ramdisk You can also reboot the system later if you want Uninstalling the Binary RPM FC and FCoE Driver Kit Note You must run the uninstall script that shipped with the version of the driver kit you want to remove To uninstall the binary RPM FC and FCoE driver 1 Log on as root 2 If possible exit all applications that use Fibre Channel attached drives then unmount the drives If you cannot exit all applications that use Fibre Channel attached drives the uninstall works properly but you must reboot after the uninstallation is complete 3 Execute the elx_lpfc_install sh script with the uninstall option Type elx_lpfc_install sh uninstall Emulex Drivers for Linux User Manual Installation Page 6 gt EMULEX Installing the Ethernet Driver Kit The Ethernet driver kit includes the driver that supports the NIC protocol
19. found for this iotag does not have a completion handler set in it DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes0378 No support for fcpi mode DESCRIPTION Could not configure the port to run in FCP initiator mode DATA None SEVERITY Warning LOG LOG_MBOX LOG_SLI ACTION None required elx_mes0379 Feature Mismatch Data lt req ftr word2 hex gt lt req_ftr word3 hex gt lt cfg_enable_npiv gt lt max vpi hex gt DESCRIPTION The features passed in to the driver as module parameters do not match what the firmware can do Setting to default values DATA None SEVERITY Warning LOG LOG_MBOX LOG_SLI ACTION None required elx_mes0383 Error lt rc gt during scsi sgl post operation DESCRIPTION The SGL entries could not be registered with the adapter DATA None SEVERITY Warning LOG LOG_MBOX LOG_SLI ACTION Reset the adapter using hbacmd elx_mes0386 ELS complete with no corresponding cmdiocb iotag lt iotag gt DESCRIPTION The completion that the ISR is handling cannot find a tag associated with the IOTAG DATA None SEVERITY Warning LOG LOG_SLI ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 49 gt EMULEX elx_mes0421 MSI X slow path request_irq failed lt rc gt DESCRIPTION The kernel API to request an IRQ has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION Use module parameter Ipfc_use_msi 0 IntX elx
20. gt lt EMULEX Emulex Drivers for Linux User Manual Emulex Connects P006994 01A Rev A Servers Storage and People gt EMULEX EMULEX CONFIDENTIAL Copyright 2003 2011 Emulex All rights reserved worldwide Unpublished work No part of this document may be reproduced by any means or translated to any electronic medium without a the prior written consent of Emulex and b the preservation of this notice on all copies and partial copies Copying access use or distribution requires an applicable written agreement approved by Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright trade secret or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this documentation as is without any warranty of any kind either expressed or implied in
21. kernel before proceeding Refer to Uninstalling the Source based RPM FC and FCoE Driver Kit on page 5 for more information 3 Download the driver kit from the Emulex website or copy it to the system from the installation CD 4 Log on as root to a terminal and unpack the tarball with the following command tar xzf elx be2net dd lt driver version gt tar gz 5 Change to the directory that is extracted cd elx be2net dd lt driver version gt 6 Execute the elx_net_install script with no options to install the new driver kit Type elx_net_install sh Once the elx_net_install script has completed successfully the Emulex Ethernet driver is loaded and devices that are properly connected to the system are accessible Reboot the system now to enable the newly added driver options in the ramdisk You can also reboot the system later if you want Emulex Drivers for Linux User Manual Installation Page 7 gt EMULEX Uninstalling the Ethernet Driver Kit Note You must run the uninstall script that shipped with the version of the driver kit you want to remove To uninstall the Ethernet driver 1 Log on as root 2 If possible exit all applications that use Ethernet attached drives then unmount the drives If you cannot exit all applications that use Ethernet attached drives the uninstall works properly but you must reboot after the uninstallation is complete 3 Execute the elx_net_install sh script with the
22. reboot you must add the following line to the file etc modprobe conf options be2net rx_frag_size 4096 iSCSI Driver Configuration Table 5 iSCSI Driver Configuration Options lists the user configurable iSCSI driver options It includes a description of the parameters default values and the limits within which they can be configured Note If the value provided for a parameter is outside the supported range minimum and maximum values the driver will log an error in the event log and continue to load by taking the parameter s default value Emulex Drivers for Linux User Manual Configuration Page 20 gt EMULEX Table 5 iSCSI Driver Configuration Options Default oe Maximum er Parameter Minimum Value Description Value Value LDTO 20 secs 0 secs 3600 sec Link Down Timeout in Seconds This parameter determines the amount of time the initiator driver waits for the controller s physical link to become available before reporting that the LUNs are unavailable to the operating system ETO 30 secs 0 secs 3600 secs Extended Timeout in Seconds This parameter determines the amount of Note If the minimum value time the initiator driver will wait for the is set between 0 19 target to become available once it has the driver will assume lost connection to the target during an a value of 20 I O operation internally No modifications will be seen in the registry im_policy 2 0 4 This parameter co
23. rx usecs and tx usecs are incremented by 8 and range from 0 to 96 To change the limits run the ethtool commands ethtool C lt ethN gt rx usecs high 40 ethtool C lt ethN gt rx usecs low 8 where lt ethN gt is the number of the Ethernet interface you are working on The granularity for delay is 8 microseconds If the application requires low or predictive latency it is recommended that you turn off adaptive interrupt coalescing and set rx usecs to 0 Emulex Drivers for Linux User Manual Configuration Page 31 gt EMULEX CPU Binding Considerations When using MSI X for best performance the RX and TX interrupts from the OneConnect UCNA must be distributed across all available CPUs The irqbalance service strives to achieve this automatically In some cases you can get more optimal performance by disabling irqbalance and manually binding the interrupts to specific CPUs Read proc interrupts to see the current distribution of interrupts cat proc interrupts CPUO CPU1 0 1556391 0 IO APIC edge timer T 30 2206 IO APIC edge i8042 8 1 0 IO APIC edge rtc 9 0 0 IO APIC level acpi 12 96 0 IO APIC edge i8042 74 2846 7013 IO APIC level libata 82 0 0 IO APIC level uhci_hcd usb1 98 0 IO APIC level uhci_hcd usb2 114 104806161 PCI MSI X eth0O rx 122 47578488 PCI MSI X eth0O tx 130 48014463 PCI MSI X ethl rx 0 0 0 0 138 17150482 0 PCI MSI X eth1 tx 1 0 0 3 169 6 IO APIC level se_ec3210 177 6 IO APIC level
24. the parent fc_host that this virtual port was created from Z indicates the instance of virtual port created from the parent fc_host A B and C indicate the PCI hierarchy for each physical LPFC port In other words hostY is the new host created for the new virtual port vport X 0 Z uniquely identifies the VPort and indicates the parent host structure XXX that this virtual port was created by For example when we create a VPort from host5 we get a new scsi_host fc_host fc_vport and a new entry under the bus tree as well root doc ls sys class scsi_host host0 hosti host4 host5 host6 root doc ls sys class fc_host host4 host5 host6 root doc ls sys class fc_vports vport 5 0 0 FC and FCoE Driver Version 8 3 5 x sysfs Structure In the 8 3 5 x FC and FCoE driver the transport creates an fc_vport directory that you can use to monitor VPorts This directory is populated entirely of VPorts and has links from each to the fc_host associated with that VPort root doc ls sys class fc_vports vport 5 0 0 root doc ls d sys bus pci drivers lpfc host host sys bus pci drivers lpfc 0000 03 06 1 host5 vport 5 0 0 host6 root doc ls sys devices pci host5 vport 5 host6 power rport 6 0 0 rport 6 0 1 rport 6 0 2 uevent root doc ls sys devices pci host5 vport 5 host6 rport sys devices pci00 03 00 03 06 1 host5 vport 5 0 0 host6 rport 6 0 0 power uevent sys devices pci00
25. to the target system s architecture and kernel memory variant e A README file that provides a description of the kit structure its contents distribution support scope and any release notes that apply on this driver version and distribution Emulex Drivers for Linux User Manual Installation Page 5 gt EMULEX e The driver changelog file Once the RPM is installed the elx_Ipfc_install script creates a new ramdisk for the currently running kernel so that the FC and FCoE driver is loaded when the kernel is initialized during system startup Note The OneCommand Manager application must be installed separately from the driver Refer to the Installing the OneCommand Manager Application on page 10 for more information To install the binary RPM FC and FCoE driver for Linux 1 Install a supported Emulex adapter in the system Refer to the adapter s installation manual for specific hardware installation instructions 2 Remove any previously installed Ethernet driver kits and or Application Helper Modules that were installed from the Emulex CD or downloaded from the Emulex website i e not part of a distribution s kernel before proceeding Refer to Uninstalling the Source based RPM FC and FCoE Driver Kit on page 5 for more information 3 Download the appropriate driver kit from the Emulex website or copy it to the system from the installation CD 4 Log on as root to a terminal and unpack the tarball with the
26. value of 64 for private loop topologies regardless of the configured value If there are multiple ports configured on the host the value of 64 is only used for those ports that are connected in a private loop topology The configured value is used for all other ports Ipfc_enable_da_id 0 0 Disabled This parameter controls whether the Yes default FC and FCoE driver will issue a 1 enable a DA_ID CT command to the fabric DA_ID CT when VPorts logout of the fabric command is sent to the fabric when logging out Ipfc_enable_hba_ 1 0 heartbeat Controls the adapter heartbeat logicin Yes heartbeat disabled the FC and FCoE driver If the 1 heartbeat heartbeat is enabled and the enabled heartbeat logic detects that the adapter is nonfunctional the FC and FCoE driver will shutdown the adapter lpfc_enable_hba_reset 1 0 hba reset Controls whether hba_resets will be Yes disabled allowed by the FC and FCoE driver to 1 hba reset pass to the adapter This is used as a enabled debugging tool Emulex Drivers for Linux User Manual Configuration Page 14 gt EMULEX Table 2 LPFC Static Parameters Requires a driver reload to change Continued Variable Default Min Max Comments Visible using sysfs Ipfc_enable_npiv This parameter controls the FC and FCoE driver s ability to use NPIV to create virtual ports It defaults to off 0 which prevents the FC and FCoE driver from creating any virtual ports Wh
27. virtual port must perform discovery independently As more VPorts are configured the amount of time that the driver and adapter take to finish discovery of remote ports on the SAN will increase To compensate for this extended amount of time taken in discovery it is recommended that the user set the lpfc_devloss_tmo parameter to 60 when npiv is enabled Note Ensure you are using the latest recommended firmware for VPort functionality Check the Emulex website for the latest firmware Note Loop devices and NPIV are not supported on the same port simultaneously If you are running a loop topology and you create a VPort the VPort s link state will be offline Note You can only create virtual ports on 4 Gb s 8 Gb s and 10 Gb s adapters You cannot create virtual ports on 1 Gb s and 2 Gb s adapters The mkvport sh Script You can use the mkvport script to create VPorts To see the usage information run the script with no parameters specified The mkvport sh script uses the following syntax mkvport sh lt Physical Port s Host number gt lt Port Name gt lt Node Name gt For example gt mkvport sh host7 10000000c94ac63a 20010000c94ac63a Emulex Drivers for Linux User Manual Configuration Page 23 gt EMULEX would create a VPort with port name of 10000000c94ac63a and a node name of 20010000c94ac63a on the physical port with scsi_host name host7 This script will fail if the VPort is not created Note
28. 0000 gt proc sys net core rmem max echo 32000000 gt proc sys net core wmem default echo 32000000 gt proc sys net core wmem max echo 0 gt proc sys net ipv4 tcp_timestamps echo 0 gt proc sys net ipv4 tcp_sack ifconfig eth lt X gt txqueuelen 100 The above settings assume ideal conditions such as low latency zero or close to zero packet loss in the network enough free memory and 10 Gb s path to peer system The tcp_rmem and tcp_wmem values above are also the default values in recent updates of Linux distributions If the application requires best throughput with a very small number of connections less than four it may help to increase the tcp_rmem and tcp_wmem to much larger values echo 4096 87380 16777216 gt proc sys net ipv4 tcp_rmem echo 4096 65536 16777216 gt proc sys net ipv4 tcp_wmem TCP Segmentation Offload TSO TCP Segmentation Offload TSO is enabled by default In networks with very little loss TSO improves performance considerably and must remain enabled The proc variable proc sys net ipv4 tcp_tso_win_divisor controls how aggressive the network stack can be in making TSO requests TSO divisor values in the range 2 to 16 are recommended for a low loss network The default value of 3 in the RHEL 6 and SLES 11 SP1 distributions seem to be the optimal one for a no loss network Smaller divisor values result in larger TSO chunks and better throughput as well as CPU utilization However if the receiver or t
29. 03 00 03 06 1 host5 vport 5 0 0 host6 rport 6 0 1 power uevent sys devices pci00 03 00 03 06 1 host5 vport 5 0 0 host6 rport 6 0 2 power target6 0 0 uevent The new host for the virtual port is host6 It appears in the usual directories and now there is a new entry in the fc_vports directory for the VPort that indicates that the VPort was created from host5 and is the first 0 VPort to be created on that fc_host There is also a new directory in the bus tree to indicate that host6 was created under vport 5 0 0 that was created from host5 Emulex Drivers for Linux User Manual Configuration Page 25 gt EMULEX VPort sysfs Entries The following table describes VPort sysfs entries Note VPort sysfs entries in Table 5 are only present if the driver was loaded with Ipfc_enable_npiv enabled Table 7 VPort sysfs Entries Range VPort sysfs Entries Type Input Location and Description npiv_vports_inuse read integers sys class fc_host hostX npiv_vports_inuse only This entry displays the number of VPorts that were created on this fc_host This sysfs entry will only exist if the vport_create and vport_delete sysfs entries exist If an fc_host does not support NPIV then this sysfs entry may not exist Note Use this sysfs entry along with max_npiv_vports to determine whether the maximum number of VPorts have been created on this fc_host max_npiv_vports read integers sys class fc_host hostX max_npiv_vports only
30. 8dd 20000000c93cc8dd LPe12000 NPIV Physical lpfc4 host10 10000000c94ac63a 20010000c94ac63a NPIV Virtual VPI 1 lpfc3 host9 10000000c93cc8dc 20000000c93cc8dc LPe12000 NPIV Physical root curly scripts For LPFCO and LPFC1 NPIV Not Supported means that this adapter firmware combination does not support the creation of VPorts For LPFC2 NPIV Physical refers to a physical port of this adapter For LPFC4 NPIV Virtual refers to a VPort of this adapter The VPort Sysfs Tree When a VPort is created three new directories are created in the class tree sys class scsi_ host hosty sys class fc_host hostyY sys class fc_vports vport X 0 Z Emulex Drivers for Linux User Manual Configuration Page 24 gt G EMULEX Creating a new VPort also creates a new sysfs directory in the bus and devices tree sys bus pci drivers lpfc 0000 A B C hostX vport X 0 Z hostY sys devices pci0000 A 0000 A B C hostX vport X 0 Z hostY In both directories there is a hostY directory that contains the remote ports that this new host can access sys bus pci drivers lpfc 0000 A B C hostX vport X 0 Z hostY sys bus pci drivers lpfc 0000 A B C hostX vport X 0 Z hostY rport Y 0 0 sys bus pci drivers lpfc 0000 A B C hostX vport X 0 Z hostY rport Y 0 1 sys bus pci drivers lpfc 0000 A B C hostX vport X 0 Z hostY rport Y 0 2 Y indicates the new host value for the virtual port that was created X indicates the host value for
31. C and FCoE driver parameters are available as files Reading a file displays the current value of a driver parameter If the permissions allow it you can write a value to the file and it will take effect immediately For example root emulex cat sys class scsi_host host7 lpfc_log_ verbose 0 Emulex Drivers for Linux User Manual Configuration Page 12 gt EMULEX Notice that the current value of Ipfc_log_verbose is zero To set it to Oxffff root emulex echo Oxffff gt sys class scsi_host host7 lpfc_log verbose root emulex cat sys class scsi_host host7 lpfc_log verbose Oxfffft Creating a New Ramdisk Image The Ipfc install script creates a ramdisk containing the FC and FCoE driver for the currently running kernel Note You must perform this step whenever the LPFC options in etc modprobe conf are changed and you want the change to take effect on the next reboot For Installed FC and FCoE Driver Kits To create a new initial ramdisk image 1 su to root 2 Type cd usr src lpfc 3 Execute the Ipfc install script using the createramdisk option Type lpfc install createramdisk For Distribution In Box FC and FCoE Drivers To create a new initial ramdisk image e For SLES11 SP1 distributions type mkinitrd k vmlinuz i initrd e For RHEL6 distributions type mkinitrd f boot initrd lt kernel version gt img lt kernel version gt Dynamically Adding LUNs and Targets The FC and
32. Down Timeout Expired Please check the Physical Link to OneConnect Check the links to the UCNA If the link is reestablished any sessions that existed previously will be reestablished and the devices will be available for I O Extended Timeout Expired Loss of connection to target exceeded ETO limits Session ID 0xX Check the connection to the target or the state of the target device If the target is made available any sessions that existed previously will be reestablished and the devices will be available for I O Received unsupported Task Management Function Task Management Function code 0xX The operating system version is not supported Received a TMF Abort for an IO that is not present with the driver This may indicate a slow connection to the target Check network connectivity to the target for any errors Received invalid iSCSI Command Sequence Number update from Target Session Handle 0xX MaxCmdSN 0xX ExpCmdSN 0xX Check for any errors reported at the target The Emulex iSCSI initiator is only supported with certified targets Check for software updates at the target vendor s website and the Emulex website If the above fails contact technical support Emulex Drivers for Linux User Manual Troubleshooting Page 43 gt EMULEX Table 13 Linux iSCSI Error Log Entries Continued Message Recommended Resolution Did not receive an iSCSI Command win
33. ERITY Warning LOG LOG_INIT ACTION None required elx_mes2717 CT context array entry lt index gt over run oxid lt fh_ox_id gt sid lt fh_SID gt DESCRIPTION All of the array slots to hold buffers that are passed to the application are in use DATA None SEVERITY Warning LOG LOG_ELS ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 55 gt EMULEX elx_mes2718 Clear Virtual Link Received for VPI lt index gt tag lt event_tag gt DESCRIPTION A Clear virtual link was received from the Fabric for this VPI DATA None SEVERITY Error LOG LOG_DISCOVERY ACTION None required elx_mes2719 Invalid response length tgt lt TGT_ID gt lun lt LUN gt cmnd lt CMD gt rsplen lt RSPLEN gt DESCRIPTION The response length for this FCP command is not supported DATA None SEVERITY Error LOG LOG_FCP ACTION None required elx_mes2721 ndlp null for oxid x SID x n icmd gt ulpContext dfchba gt ct_ctx tag SID DESCRIPTION The Node value for this SID is not in the node list DATA None SEVERITY Warning LOG LOG_ELS ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 56 gt EMULEX APPENDIX A Open iSCSI Support Open iSCSIl is a high performance transport independent multi platform implementation of RFC 3720 iSCSI The inbox Open iSCSI driver is supported Due to limitations in the current Open iSCSI distribution tools the
34. FCoE driver enables you to dynamically add LUNs and targets without unloading or reloading the Ipfc module and without resetting the adapter To rescan an adapter s targets with sysfs given the adapter s host number in this example 3 type echo gt sys class scsi_host host3 scan To limit the rescan to a particular target given the adapter s host number in this example 3 and the target number in this example 2 type echo 2 gt sys class scsi_host host3 scan You can also use the Emulex lun_scan script in usr sbin Ipfc Emulex Drivers for Linux User Manual Configuration Page 13 gt EMULEX FC and FCoE Driver Parameters Reference Table The FC and FCoE driver parameters determine some aspects of the driver s behavior The following tables list the FC and FCoE driver parameters Some FC and FCoE driver parameters can be modified and take effect only on a driver load while others can be modified dynamically and take effect immediately The tables also list the default minimum and maximum values for these parameters Table 2 LPFC Static Parameters Requires a driver reload to change Visible Variable Default Min Max Comments using sysfs Ipfc_ackO 0 0 Off 1 On Uses ACKO for class 2 Yes Ipfc_discovery_threads 32 1 64 Specifies the maximum number of No ELS commands that can be outstanding for a discovery Note The discovery_threads parameter defaults to a
35. I driver kits and or Application Helper Modules that were installed from the Emulex CD or downloaded from the Emulex website i e not part of a distribution s kernel before proceeding Refer to Uninstalling the Source based RPM FC and FCoE Driver Kit on page 5 for more information 3 Download the driver kit from the Emulex website or copy it to the system from the installation CD 4 Log on as root to a terminal and unpack the tarball with the following command tar xzf elx be2iscsi dd lt driver version gt tar gz 5 Change to the directory that is extracted cd elx be2iscsi dd lt driver version gt Emulex Drivers for Linux User Manual Installation Page 8 6 gt EMULEX Execute the elx_iscsi_install script with no options to install the new driver kit Type elx_iscsi_install sh Once the elx_iscsi_install script has completed successfully the Emulex iSCSI driver is loaded and devices that are properly connected to the system are accessible Reboot the system now to enable the newly added driver options in the ramdisk You can also reboot the system later if you want Uninstalling the iSCSI Driver Kit Note You must run the uninstall script that shipped with the version of the driver kit you want to remove To uninstall the iSCSI driver 1 2 Log on as root If possible exit all applications that use iSCSl attached drives then unmount the drives If you cannot exit all applications that
36. Install Script Options The following options are available for use with the Emulex install script for the source based RPM FC and FCoE driver for Linux e h help Prints a help message describing command line parameters e u uninstall Uninstalls the currently installed driver kit e createramdisk Creates a new ramdisk image Use this option after you have modified driver parameters in the etc modprobe conf file Directory Structure After installation the following directory is created on the system Table 1 Driver Kit Directory Structure Directory Description usr src lpfc Driver source files Installing on Unsupported Linux Distributions The Emulex version 8 3 5 x drivers for Linux are not intended for and do not operate on any kernel prior to 2 6 32 If you are using an earlier 2 6 kernel version see the Emulex website for additional driver configuration driver version and operating system support information To install the Emulex FC and FCoE driver on an unsupported distribution of Linux refer to the distribution s website or http kernel org Upgrading the Kernel or Applying a Distribution Service Pack or Update You can install the driver kit into an upgraded kernel The installation of an update or service pack generally involves updating the kernel Installing into an Upgraded Kernel To install the source based RPM FC and FCoE driver kit into an upgraded kernel 1 Execute
37. To work around this issue follow these steps 1 Determine whether your current iSCSI driver is a v2 0 driver by running the following command modinfo be2iscsi The version 2 0 driver usually starts out with 2 102 xyz x 2 Find the location of the driver module under lib by typing find lib name be2iscsi ko print For example the output would look something like this lib modules 2 6 32 12 0 7 default updates be2iscsi ko this is the module file to remove 2 102 348 0 lib modules 2 6 32 12 0 7 default kernel drivers scsi be2iscsi be2iscsi ko this is the open be2iscsi do not remove 3 Remove the old module by typing rm f lib modules 2 6 32 12 0 7 default updates be2iscsi ko 4 Update the system with the new driver via rpm or elx_iscsi_install sh Linux NIC Situations and their Resolutions The following table provides Linux NIC troubleshooting information for the OneConnect UCNA Table 11 Linux NIC Situations and their Resolutions Situation Resolution The driver works but the transmit and receive data rates are not near a 10 Gb s line rate There could be several reasons for poor performance The driver logs a warning message if the card is found ina suboptimal slot If you see this message in var log messages move the card to the proper slot For more information on getting the best performance from a OneConnect UCNA see Network Driver Performance Tuning on pa
38. ULT 1IBM ULTRIUM TD2 1110133831 SYMLINK fc_ lun _st n BUS scsi RESULT 1IBM ULTRIUM TD2 1110133994 SYMLINK fc_ lun _st n Create a new file named etc udev rules d 45 local rules and put the appropriate rule in it Then run udevtrigger to reload the udev rules Emulex Drivers for Linux User Manual Configuration Page 19 gt EMULEX And finally here is the output of the rule root localhost udevtrigger root localhost ls al dev fc lrwxrwxrwx 1 root root 3 Apr 7 15 03 fc_lun_st0 gt sto lrwxrwxrwx 1 root root 3 Apr 7 15 03 fc_lun_st1 gt stl Further Information About Persistent Names Refer to the following references for more information on persistent naming http www reactivated net udevrules php by Daniel Drake dsd http kernel org pub linux utils kernel hotplug udev_vs_devfs by Greg Kroah Hartman http linux dell com devlabel devlabel htm NIC Driver Configuration The NIC driver has a single user configurable option rx_frag_size Table 4 NIC Driver Configuration Option describes the option in more detail Table 4 NIC Driver Configuration Option Parameter Possible Values Default Value Description rx_frag_size 2048 2048 The size of fragments used to DMA received data 4096 8192 To load the NIC driver with an rx_frag_size value of 4096 insmod be2net ko rx frag_size 4096 To configure Linux to automatically load the driver with this option after each
39. _mes0429 MSI X fast path request_irq failed lt rc gt DESCRIPTION The driver received an error for the request_irq_call DATA None SEVERITY Warning LOG LOG_INIT ACTION Unload and reload the driver elx_mes0458 Bring adapter online DESCRIPTION The FC driver has received a request to bring the adapter online This may occur when running Iputil DATA None SEVERITY Warning LOG LOG_INIT verbose ACTION None required elx_mes0460 Bring adapter offline DESCRIPTION The FC driver has received a request to bring the adapter offline This may occur when running Iputil DATA None SEVERITY Warning LOG LOG_INIT verbose ACTION None required elx_mes0466 Outstanding IO when bringing Adapter offline DESCRIPTION IO is still pending while attempting to stop the driver DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes0478 MSI request_irq failed lt rc gt DESCRIPTION The request_irq kernel API has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION Set Ipfc_use_msi 0 Emulex Drivers for Linux User Manual Troubleshooting Page 50 gt EMULEX elx_mes0485 MSI X slow path request_irq failed lt rc gt DESCRIPTION The request_irq kernel API has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION Set module parameter Ipfc_use_msi 0 elx_mes0486 MSI X fast path lt index gt request_irq failed lt rc gt DESCRIPTION The request_irq ker
40. _table size Ipfc_sli_mode 0 auto default 2 SLI 2 mode 3 SLI 3 mode This parameter allows you to force the SLI mode requested by the adapter driver This parameter has no effect on OneConnect UCNAs No Emulex Drivers for Linux User Manual Configuration Page 15 gt EMULEX Table 2 LPFC Static Parameters Requires a driver reload to change Continued Visible Variable Default Min Max Comments using sysfs Ipfc_max_luns 255 0 65535 Specifies the maximum number of Yes LUN IDs per target A value of 19 means LUN IDs from 0 to 19 are valid The SCSI layer scans each target until it reaches the specified LUN ID Ipfc_max_scsicmpl_tim 0 0 6000 Uses command completion time to Yes e control queue depth lpfc_multi_ring_rctl 4 1 255 Identifies RCTL for additional ring Yes configuration Note Only used when multi_ring_support is enabled Ipfc_multi_ring_support 1 1 2 Determines the number of primary SLI Yes rings over which to spread IOCB entries Ipfc_multi_ring_type 5 1 255 Identifies TYPE for additional ring Yes configuration Note Only used when multi_ring_support is enabled Ipfc_use_msi 0 0 MSI disabled Controls whether the driver uses Yes 1 MSI enabled Message Signaled Interrupts 2 MSI X enabled All LPFC dynamic parameters are read write using sysfs Table 3 LPFC Dynamic Parameters Do not require a driver reload to
41. a persistent name for a boot device SLES 11 SP1 1 In boot grub menu lst find the kernel line for the default boot For example kernel boot vmlinuz root dev sda2 vga 0x314 2 Find the persistent name for the root partition following root on the kernel line by using the instructions in Using udev to Discover Logical to Physical Mappings for sd Devices on page 17 3 Inthe same file boot grub menu lst replace the text after root with the partition s persistent name For example kernel boot vmlinuz root dev disk by id scsi 32000000c5005d6e6 part2 vga 0x314 4 Change any mounts listed in etc fstab which refer to this root partition by either it s dev sd name or a file system LABEL to use the persistent name as well To use a persistent name for a boot device RHEL 6 1 In boot grub grub conf find the kernel line for the default boot For example kernel boot vmlinuz lt kernel version gt ro root dev sda2 2 Find the persistent name for the root partition following root on the kernel line by using the instructions in Using udev to Discover Logical to Physical Mappings for sd Devices on page 17 3 Inthe same file boot grub menu I st replace the text after root with the partition s persistent name For example kernel boot vmlinuz lt kernel version gt ro root dev disk by id scsi 32000000c5005d6e6 part2 4 Change any mounts listed in etc fstab which refer to this root partition by e
42. aanannadnabaneeanonanboannbanbbanbbedaad leds 33 ISCS Emon Hamlin iee a E AOO tele idn elses OOOO 33 Configuring LDTO and ETO eececccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetenees 34 Error Handling Under MultiPath MPIO and Cluster Configurations 34 TROUMBISS NOGGIN G isiin nandean danatan aa aaa ana aaae aiaia aa aE 35 DIRT VGN A estate EE E ad nena eee met create E EE 35 General Driver Situations and their Resolutions cceeeeeeeeeeeeeeeeeeeeeeneees 35 Linux iSCSI Situations and their Resolutions cececeeeeeeeeeeeeeeeeeeeeeeeaaeees 38 Linux NIC Situations and their Resolutions 0 ieee ee eee eee eeeeeeeeeeeeeaaeees 39 Lin x Log IWS SA a ah esc nat eases anaE 40 Retrieving Linux NIC Error Log Codes 0 ce eeererrrre i i naan 40 Linux NIC Event Log EntrieS 0000000 nn de 40 Retrieving Linux iSCSI Error Log Codes ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeteeteieiiniiinieeeeeaa 42 Linux ISCSI Error Log Entries seerste E ETATER 43 LPFG Pag MSS AG eS oieracea ra aaaea pa eenia ae 45 aiia alU a ie 1 PPEP EEE EE E Lees 45 Message Log Examples 0 c c c 5c teeta iaaa 45 LOG MeSSaGeS aisssssas isa seacieaeieis eee eaea eea eE EEEE ead cae cada aad 45 Appendix A Open iSCSI SUpport cece cee ce eee ee ee eee eee eeeeeeeeeeeeaeeeeeeeseeesaeeeeneeeeeeeaees 57 Emulex Drivers for Linux User Manual Page v Connecting to the iSCSI Target ggasi onsonieevedecusinet
43. ad and the throughput and latency offered by these iSCSI targets On systems capable of sustaining a higher interrupt rate and when the number of targets that will be connected is less up to 8 the more Aggressive setting will result in lower latency and higher values of I O operations per second IOPs However the higher interrupt rate could also result in system stalls and freezes especially during higher values of queue depth and smaller sized I O requests Though on a configuration that involves a large number of iSCSI targets more than 32 or 64 and higher values of queue depth the default setting may prove to be too aggressive and the interrupt moderation setting may need to be changed to Conservative or Very Conservative Though this will increase latency of an I O request the lower interrupt rate may allow the system to be functional under a high load Working with Virtual Ports VPorts Creating Deleting and Displaying VPorts VPorts are created through sysfs entries that are presented in the physical port s sysfs directory The vport_create and vport_delete sysfs entries are discussed in the sysfs section but there are also three scripts for creating deleting and displaying VPorts The scripts reside in the usr sbin Ipfc directory and are part of the OneCommand Manager Applications kit When NPIV is enabled and VPorts are configured it may take longer for the adapter to finish discovery in some cases due to the fact that each
44. ameters Table 14 Mandatory and Optional Parameters for Vendor specific Option 43 describes the parameters used in the data string for option 43 Table 14 Mandatory and Optional Parameters for Vendor specific Option 43 Parameter Description Field Type lt TargetIP gt Replace with a valid IPv4 address in dotted Mandatory decimal notation Emulex Drivers for Linux User Manual Configuring iSCSI Through DHCP Page 59 Table 14 Mandatory and Optional Parameters for Vendor specific Option 4 gt EMULEX 3 Parameter Description Field Type lt TargetTCPPort gt Replace with a decimal number ranging from 1 to 65535 inclusive The default TCP port 3260 is assumed if a value is not specified Optional lt LUN gt A hexadecimal representation of the Logical Unit Number of the boot device Replace with an eight byte number that should be specified as a hexadecimal number consisting of 16 digits with an appropriate number of Os padded to the left if required If a value is not provided LUN 0 is assumed to be the boot LUN Optional lt TargetName gt Replace with a valid iSCSI target iqn name of up to 223 characters Mandatory lt InitiatorName gt Replace with a valid iSCSI iqn name of up to 223 characters If a value is not provided the default initiator name generated by the OneConnect UCNA based on the board s MAC address will be used Optional lt Head
45. andling is to be tolerant of link level and target level failures up to configured timeout values so that I O errors are not seen by the application or operating system The error handling is triggered under the following conditions e Loss of immediate link to the initiator such as cable disconnect or port failure The UCNA firmware detects and notifies the driver of a loss of the link When this happens the driver queues the I O requests internally up to a configured timeout period so that the operating system does not see I O errors This timeout is known as a link down timeout LDTO e Loss of connection to the target due to target and or network disconnection at the target If the driver has I O requests pending with the target and the target becomes unavailable due to target going down or failing over or network issues at the target the driver queues up the I O request internally up to a configured timeout period This timeout is known as an extended timeout ETO When the configured threshold for LDTO and ETO is reached and the initiator is still unable to connect to the target the driver fails all I O requests At this point I O errors are seen by the application and operating system Note Following a link up switch ports can take a long time to initialize and go to forwarding state Because of this additional time should be added to the ETO and LDTO settings to eliminate I O disruption or target unavailability If the sw
46. are issue Internal API failed during Initialization This failure may indicate a low memory condition OSM Resource Allocation Failure The operating system failed to allocate resources for the device Check low memory conditions and operating system hardware resource conflicts All messages are preceded by a prefix of scsiX if the SCSI host controller can be determined with X being a number representing the Linux SCSI host controller All iSCSI error messages are preceded with OneConnect iSCSI Driver The 0xX message returned with some errors indicates a Ox with X being a number following 0x For example scsi2 OneConnect iSCSI Driver Rejected IOCTL since buffer size limit exceeded scsi2 OneConnect iSCSI Driver Subsystem Opcode 0x12345678 0x11223344 scsi2 OneConnect iSCSI Driver Payload Length 0x1000 Emulex Drivers for Linux User Manual Troubleshooting Page 44 gt EMULEX LPFC Log Messages Introduction This section lists the log messages for the FC and FCoE driver LPFC error log messages go to var log messages Message Log Example The following is an example of a LOG message Jul 2 04 23 34 daffy kernel lpfc 0000 03 06 0 0 1305 Link Down Event x2f2 received Data x2f2 x20 x110 In the above LOG message e Ipfc 0000 03 06 0 identifies the identifies the pci location of the particular Ipfc hw port 0 identifies Emulex adapter0 e 1305 identifies the LOG message nu
47. arget name you want to log into lt ip port gt is the IP address and port number and lt iface gt is the name of the iface created in step 1 9 Verify that the disk shows up by running this command fdisk 1 10 Log out by running this command iscsiadm m node T lt targetname gt p lt ip port gt I lt iface gt u where lt targetname gt is the target name lt ip port gt is the IP address and port number and lt iface gt is the name of the iface created in step 1 For example iscsiadm m iface o new I ifaceo iscsiadm m iface I ifaceO op update n iface hwaddress v 00 0F 1F 62 2B BF iscsiadm m iface I iface0 op update n iface transport name v be2iscsi service open iscsi restart iscsiadm m discovery t st p 20 0 0 107 3260 I iface0 P 1 iscsiadm m iface I iface0 op update n iface hwaddress v 00 0F 1F 92 6B BF iscsiadm m iface I iface0 o update n iface ipaddress v 20 0 0 107 iscsiadm m node T iqn tgt0 p 20 0 0 107 3260 I iface0 1 fdisk 1 iscsiadm m node T iqn tgt0 p 20 0 0 107 3260 I iface0 u Emulex Drivers for Linux User Manual Open iSCSI Support Page 58 J gt EMULEX APPENDIX B Configuring iSCSI Through DHCP DHCP Recommendations If you are using the Dynamic Host Configuration Protocol DHCP server to obtain an IP address for your iSCSI initiator Emulex recommends that you set up a reservation A reservation will assign a specific IP address based on the MAC ad
48. aximum transfer size in a single SCSI command By default the iSCSI driver supports up to 128 KB and 32 Scatter Gather entries in a single SCSI command If applications issue I O requests that are larger than 128 KB or need more than 32 Scatter Emulex Drivers for Linux User Manual Configuration Page 21 gt EMULEX Gather entries the request will be split into multiple requests by the driver By specifying large_io 512 the iSCSI driver can support up to 512 KB of data and a total of 128 Scatter Gather entries in a single SCSI command Note that by setting the option to 512 the amount of physical memory consumed by the driver increases In addition though intermediate values between 64 and 512 will be accepted the memory used by the driver is the same as what is used for large_io 512 To set the large_io parameter enter the following command insmod be2iscsi ko large _io 512 To manually set the large_io parameter type the following command insmod be2iscsi ko large _io 512 To permanently set large_io on every iSCSI boot edit the etc modprobe conf file by following the example below The alias lines are added automatically when the driver is installed The options line needs to be added manually for all non default options such as large_io Example alias eth0 tg3 alias scsi_hostadapter ata_piix alias scsi_hostadapterl usb storage alias scsi_hostadapter2 be2iscsi options be2iscsi eto 0 ldto 0 large _io 512 al
49. blem persists try flashing after a system reboot Error Could not get cre from The driver could not enough get information from flash not flashing redboot the NIC to decide whether or not Redboot the primary boot program should be flashed The driver will skip updating this section This is a very unlikely error Error cmd to write to flash rom Firmware command to update OneConnect UCNA failed type op lt D gt lt D gt with new firmware failed with the indicated error code Error Firmware load error Updating the OneConnect UCNA with new firmware failed Usually this message is accompanied by other detailed messages on the failure Error Flash cookie not found in The firmware image under lib firmware firmware image lt filename gt does not have the expected cookie The firmware in this file will not be flashed Copy the proper file and try flashing again Error Could not create sysfs The creation of flash_fw entry under the sys group class net eth lt x gt failed The driver will be fully functional but you will not be able to update the firmware on the OneConnect UCNA Information Flashing firmware file This is an informational message that the firmware 24 V enames in the OneConnect UCNA is being updated with the firmware image in the file indicated Information Firmware flashed This is an informational message that the firmware in the OneConnect UCNA has been updated Retrieving Linux iSCSI Error Log Codes Fo
50. boot grub menu lst to change all hd1 references to hd0 Emulex Drivers for Linux User Manual Installation Page 9 gt EMULEX Installing the OneCommand Manager Application The OneCommand Manager application version 5 2 is a powerful centralized adapter management suite providing discovery reporting and management of local and remote adapters from a single console anywhere in the SAN and across platforms Both a graphical user interface GUI and command line interface CLI are provided This remote configuration capability can be provided by either Fibre Channel FC access via host systems on the same FC Storage Area Network SAN or by Transmission Control Protocol Internet Protocol TCP IP access from IP addresses of remote machines Refer to the OneCommand Manager Application Version 5 2 User Manual which is available on the Emulex website for instructions on installing and using the OneCommand Manager application version 5 2 Emulex Drivers for Linux User Manual Installation Page 10 5G EMULEX Configuration FC and FCoE Driver Configuration You can configure the FC and FCoE driver by e Setting module parameters using modprobe and etc modprobe conf e Using the sysfs interface for parameters that can be changed after loading the FC and FCoE driver Using the OneCommand Manager application See the OneCommand Manager Application Version 5 2 User Manual for more information Note FC and FCoE driver parameter cha
51. box command failed mbxCmd lt u mb mbxComm gt mbxStatus lt u mb mbxStatus gt DESCRIPTION The mailbox command sent to the firmware to configure the adapter to use MSI X has failed DATA None SEVERITY Warning LOG LOG_MBOX ACTION Ensure the hardware platform supports MSI X elx_mes0357 MSI X interrupt with no EQE DESCRIPTION SLI 4 adapter interrupt on the slow path but there is no associated EQE DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes0358 MSI X interrupt with no EQE DESCRIPTION SLI 4 adapter interrupt on the fast path but there is no associated EQE DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes0373 FCP complete error status lt status gt hw_status lt hw status gt to tal_data_specified lt total data transferred gt parameter lt rsp word 4 gt word3 lt wcqe word 3 gt DESCRIPTION Logs the FCP failure Status and parameter are equivalent to ulpStatus and ulpWord 4 DATA None SEVERITY Warning LOG LOG_SLI ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 48 gt EMULEX elx_mes0374 FCP complete with no corresponding cmdiocb iotag lt iocb iotag gt DESCRIPTION There was no IOCB on the in progress list that matched this iotag DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes0375 FCP cmdiocb not callback function iotag lt iocb iotag gt DESCRIPTION The IOCB
52. cd var log vim messages A message is displayed similar to the following Aug 15 09 57 48 S74 kernel Invalid MTU requested Must be between 256 and 8974 bytes Linux NIC Event Log Entries The following is a list of Linux network driver error log messages When reporting a problem with the OneConnect UCNA check the kernel message log using the command dmesg or the file var log messages and report any of these entries that may be present All NIC warning messages logged by a OneConnect UCNA start with be2net lt BID gt where lt BID gt is the PCI bus identifier string For example be2net 0000 0d 00 1 MTU must be between 256 and 9000 bytes Note In the following table lt D gt lt DD gt or lt DDD gt in the Message Displayed column refers to decimal values that appear in the error messages Table 12 Linux NIC Warning Log Entries Severity Message Displayed Description Error INTx Request IRQ failed The request for INTx interrupt registration failed The driver is non functional if the INTx interrupt err lt DDD gt cannot be registered Emulex Drivers for Linux User Manual Troubleshooting Page 40 Table 12 Linux NIC Warning Log Entries Continued gt EMULEX Link up Severity Message Displayed Description Error Could not set PCI DMA The operating system call to set the DMA mask Mask failed Error POST
53. cluding but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product described in this manual at any time and without any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this documentation Emulex disclaims any undertaking to give notice of such changes Emulex 3333 Susan Street Costa Mesa CA 92626 Emulex Drivers for Linux User Manual Page ii Supported Driver Versions gt EMULEX DUP Out of Driver Version Inbox DUD Box OS Versions Supported Comments FC and FCoE Drivers 8 3 5 8 1p X SLES 11 SP1 8 3 5 17 X RHEL 6 8 3 5 44 4p X SLES 11 SP1 RHEL 6 RHEL 6 1 8 3 5 44 4p X XenServer 5 6 SPx and 6 0 8 3 5 44 4p X XenServer 6 0 8 3 5 44 4p X RHEL 6 1 X SLES 11 SP1 X RHEL 6 1 Ethernet Drivers 2 102 147s X SLES 11 SP1 2 102 426r X RHEL 6 4 0 359 0 X SLES 11 SP1 RHEL 6 RHEL 6 1 4 0 317 0 X XenServer 5 6 SPx and 6 0 4 0 317 0 X XenServer 6 0 4 0 359 0 X RHEL 6 1 X SLES 11 SP1 X RHEL 6 1 iSCSI Drivers 2 102 527 0 X SLES 11 SP1 2 0 527 0 X RHEL 6 4 0 323 0 X SLES 11 SP1 RHEL 6 4 0 323 0 X XenServer 6 0 4 0 323 0 X RHEL 6 1 X SLES 11 SP1
54. d on The VPort matching the WWPN and WWNN will be immediately deleted This entry returns a 0 if the VPort deletion was successful A non zero value indicates that the VPort failed to be deleted If an fc_host does not support NPIV then this sysfs entry may not exist Note This entry will delete the VPort even if there are mounted file systems being accessed through this VPort and or open files node_name read 16 byte sys class fc_host hostX node_name sys only hex class fc_vports vport X 0 Z node_name value This entry displays physical or virtual port s node name This is the value that is assigned by you upon creation and transmitted to the fabric upon fabric login port_name read 16 byte sys class fc_host hostX port_name sys only hex class fc_vports vport X 0 Z port_name value This entry displays physical or virtual port s port name This is the value that you assign when you create a VPort It is transmitted to the fabric upon fabric login Ipfc_peer_port_login read 0 Off sys class scsi_host hostx write default lpfc_peer_port login 1 On This entry sets the port s behavior when discovering targets in the SAN The default behavior 0 will only login to nports that are physically located on a different port The port will still attempt to login to targets on all other ports including the other port in a dual ported adapter If this parameter is turned on 1 then the port will attempt to login to all nports even if they are
55. dow update from Target for at least 25 Secs Session Handle Check for any errors reported at the target The Emulex iSCSI initiator is only supported with certified targets Check for software updates at the target vendor s website and the Emulex website If the above fails contact technical support Error during iSCSI offload Session Handle Firmware Error code This may indicate a target is in error or may point to transient network connectivity issues It may also indicate a firmware error Rejected IOCTL since buffer size limit exceeded Subsystem Opcode 0xX 0xX Payload Length 0xX This error may indicate an incorrect configuration option for the iSCSI driver It may also indicate a low memory condition Unrecoverable Error UE_LOW 0xX UE HIGH 0xX Firmware Line Number 0xX This may be due to hardware errors or due to unhandled exceptions in the hardware or firmware OSM Hardware Initialization Failure This failure indicates that the hardware has not been initialized or is malfunctioning This may also indicate that the firmware is not running correctly Initialization Failure This failure may be due to the firmware not being present or running currently This failure may also indicate a hardware issue Initialization failure during Power Management Bootup This failure may be due to the firmware not being present or running currently This failure may also indicate a hardw
56. dress of your iSCSI function If you do not reserve an IP address through DHCP you must set the lease length for the iSCSI initiator s IP address to unlimited This allows the IP address lease not to expire Vendor Specific Option 43 This section describes the format for the data returned in DHCP vendor specific option 43 The method and format for specifying the Vendor ID is outside the scope of this document and is not included here The initiator offers this Vendor ID to the DHCP server to retrieve data in the format described in the following section Format of Vendor Specific Option 43 The following describes the format of option 43 and includes guidelines for creating the data string iscsi lt TargetIP gt lt TargetTCPPort gt lt LUN gt lt TargetName gt lt InitiatorName gt lt HeaderDigest gt lt DataDigest gt lt AuthenticationType gt Strings shown in quotes are part of the syntax and are mandatory e Fields enclosed in angular brackets including the angular brackets should be replaced with their corresponding values Some of these fields are optional and may be skipped e Ifan optional field is skipped a colon must be used as a placeholder to indicate the default value for that field When specified the value of each parameter should be enclosed in double quotes See Examples e All options are case sensitive Description of Mandatory and Optional Par
57. e already configured Use the default name if none was configured Header Digest Enabled Data digest Not specified Assume disabled Authentication Type 1 way CHAP The following is an example of default TCP port and mutual CHAP settings iscsi 192 168 0 2 000000000000000E iqn 2009 4 com 1234567890 E D M where the following is Target IP address 192 168 0 2 Target TCP port Use default from RFC 3720 3260 Target boot LUN 0x0E Target iqn name iqn 2009 04 com 1234567890 Initiator name Not specified Use the Initiator name already configured Use the default name if none was configured Header Digest Enabled Data digest Data Digest disabled Authentication Type Mutual CHAP Emulex Drivers for Linux User Manual Configuring iSCSI Through DHCP Page 61 y gt EMULEX APPENDIX C OneConnect Modules Port Speed Specifications OneConnect can support only one Ethernet port speed at a time and the preference is always for 10 Gb s The type of module used copper optical does not make a difference As soon as a 10 Gb s module is plugged into one of the ports OneConnect switches to a 10 Gb s speed no matter what speed the other port is running or even if I O is running on that port This behavior is an adapter constraint another adapter can be running on a different speed Table 15 Negotiated Speed Specifications per Adapter Port Connection lists negotiated speed specif
58. eeeaaaeeeeeeeeeeeeaaaeeeeeeeeeeeaas 23 TREMVPOR SH Senpleman aa aaa aaa a diaanannaanand 24 The Isvport Sh SCript cccccecccceeeeeeeeeeeeeeeaeeeeeeeeeeeeeeaaaeeeeeeeeeeesaaaaeeeeeeeeeeeaea 24 The VPorn Sysis Mees csiis aan AE E EEA AAAA E AAE EAA E 24 FC and FCoE Driver Version 8 3 5 x sysfs Structure sssessssssssesrsererrtertrerterrerrerree 25 WPortSyStS EMOS cecidere ien ennen EEEE EEEE 26 V Port Comfiguiration LIMIS cccetecetecenedecetetatetedetetetebecetecebenetecebecetecebecetecebecetecebeceteceteeeteces 27 Network Driver Performance TUNING 2 2 10 c eeeeeee cence seneeeeeecceeeneeeeneneenes 28 Improving Performance with PCI Express Bandwidth ccceeeeeeeeeeeeeeeeeeeeeeeees 28 Improving Performance with TCP Offload ceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeenennes 28 Network Buffer Sizes and TCP Parameters ccccccccceeeeeeteeeeeeeeeeeeeeeeeeeeeeees 29 TCP Segmentation Offload TSO 0 00 29 FLOW COMIN oorr aaa E AAAA ATEO TETO 30 RX Frame Coalescing GRO eeren iii 31 Maximum Transmission Unit MTU eeeeeeeesessesssnsssssssrssssrrrrrrrrrnnssssssn 31 Interrupt CoaleSCing oenina aranana nanana AAAA AAAA AAAA AAAA 31 CPU Binding Considerations ccccccccceeecceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetentees 32 MSI X Interrupts incicccicccsnncccecccecesnsssasacesdencacncnaeaacecheadadedsaneacedaendadadsuesseneaensnaaaee 33 SELINUX AUGIUING ucisi d
59. en enabled set to 1 it enables you to create and delete virtual ports if supported by the fabric Yes Ipfc_fcp_class The FC class for FCP data transmission Yes pfc_fcp_eq_count Sets the number of fast path FCP event queues if available Only applicable for OneConnect UCNAs Yes Ipfc_fcp_imax 10000 636 651042 Sets the maximum number of fast path FCP interrupts per second Only applicable for OneConnect UCNAs Yes Ipfc_fcp_wq_count 32 Sets the number of fast path FCP work queues if available Only applicable for OneConnect UCNAs Yes Ipfc_hba_queue_depth 8192 32 8192 The maximum number of FCP commands that can queue to an Emulex adapter Yes Ipfc_lun_queue_depth 30 128 The default maximum commands sent to a single logical unit disk Yes Ipfc_restrict_login 0 Off 1 On Restricts virtual ports login to remote initiators No Ipfc_scan_down 0 Off 1 On Selects method for scanning ALPA to assign a SCSI ID Yes Ipfc_sg_seg_cnt 64 50 for SLI 4 CNA 64 50 for SLI 4 CNA 4096 Controls the max scatter gather segment count passed to the FC and FCoE driver Note This variable is per SCSI command On OneConnect UCNAs these values are restricted by the FC and FCoE driver to specific values due to restrictions imposed by the hardware The possible values are 50 114 242 and 498 Yes sg
60. encnradestencavnduad Iuddeadendouananes 57 Appendix B Configuring iSCSI Through DHCP 0 ccceeeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeaees 59 DHCP RecommendationS i sicdeidiconeetaatecsnannseiadinndeaindeceiuceducsuatemibiesdeieitecnadeneceea 59 Vendor Specific Option 43 ssscsvsstucetinnsdsxnasonensdien Semedoienddeashive lanes kebes dake ivawioadand 59 Format of Vendor Specific Option 43 ccceccccceeeeeeeeeeeeeeeeeeeeeeeeeeeecaeaaeeeeeeeeeeeaaeanees 59 Description of Mandatory and Optional Parameters 0 ccccccccceeeeeeeeeeeeeeeeenensneeees 59 Appendix C OneConnect Modules Port Speed Specifications 0c00 62 Negotiating Speed on UCNA Mezzanine Cards cccceeeeeeeeeeeeeeeeeeeeeeees 62 Emulex Drivers for Linux User Manual Page vi gt lt EMULEX Installation Driver Information Supported Features e SNIA CTP compliant SMI S 1 1 Provider e Topology support Fibre Channel Arbitrated Loop FC AL point to point fabric with auto topology negotiation and Fibre Channel over Ethernet FCoE e Supports 1 2 4 and 8 Gb s capable FC adapters with auto rate negotiation The driver does not support a 1 Gb s rate on 8 Gb s FC adapters e Supports 10 Gb s Universal Converged Network Adapters UCNAs e Protocols e iSCSI supported Linux kernel is SLES 11 SP1 supported kernel variants for x86 and x86_64 e NIC supported Linux kernel is SLES 11 SP1 supported kernel variants for x86
61. erDigest gt Replace with either E or D E denotes that the header digest is enabled D denotes that the header digest is disabled Optional lt DataDigest gt Replace with either E or D E denotes that the data digest is enabled D denotes that the data digest is disabled If a value is not provided it is assumed that the Data Digest is disabled by default Optional lt AuthenticationType gt If applicable replace with D E or M D denotes that authentication is disabled E denotes that one way CHAP is enabled the username and secret to be used for one way CHAP must be specified by non DHCP means M denotes that mutual CHAP is enabled user name and passwords required for mutual CHAP authentication must be specified by non DHCP means If a value is not specified this field defaults to authentication disabled Optional Examples The following is an example of defaultinitiator name and data digest settings iscsi 192 168 0 2 3261 000000000000000E iqn 2009 4 com 1234567890 E E where the following is e Target IP address 192 168 0 2 e Target TCP port 3261 e Target boot LUN 0x0E e Target iqn name iqn 2009 04 com 1234567890 Emulex Drivers for Linux User Manual Configuring iSCSI Through DHCP Page 60 gt EMULEX Initiator name Not specified Use the Initiator nam
62. ernels with Version_Release strings that do not match those of the original distribution kernel To install the source based RPM FC and FCoE driver for Linux 1 Install a supported Emulex adapter in the system Refer to the adapter s installation manual for specific hardware installation instructions Remove any previously installed FC and FCoE driver kits that were installed from the Emulex CD or downloaded from the Emulex website i e not part of a distribution s kernel before proceeding Refer to Uninstalling the Source based RPM FC and FCoE Driver Kit on page 5 for more information Download the driver kit from the Emulex website or copy it to the system from the installation CD Log on as root to a terminal and unpack the tarball with the following command tar xzf lpfc_2 6 lt driver_kit gt lt driver version gt tar gz Change to the directory that is extracted cd lpfc_2 6 driver _kit lt driver version gt Execute the Ipfc install script with no options to install the new driver kit Type lpfc install Once the Ipfc install script has completed successfully the source based RPM FC and FCoE driver is loaded and Fibre Channel disks that are properly connected to the system are Emulex Drivers for Linux User Manual Installation Page 3 y gt EMULEX accessible Reboot the system now to enable the newly added driver options in the ramdisk You can also reboot the system later if you want
63. ers for Linux User Manual Configuration Page 18 gt EMULEX Below is another example for a different FC Tape Vendor Notice that the answer is similar with respect to the leading digit and the WWPN root localhost sbin scsi_id g s sys class scsi_tape nst0 35005076300015101 Below is an example of a FC SCSI Tape device Notice that when the Emulex driver loads the SCSI midlayer discovers the SCSI tape devices as follows scsi scan INQUIRY to host 14 channel 0 id 0O lun 0 scsi unknown device type 12 Vendor ADIC Model SNC 4000 Rev 42d4 Type RAID ANSI SCSI revision 03 Attached scsi generic sg5 at scsil4 channel 0 id 0 lun 0 type 12 scsi scan INQUIRY to host 14 channel 0O id O lun 1 Vendor ADIC Model Scalar 24 Rev 227A Type Medium Changer ANSI SCSI revision 02 Attached scsi generic sg6 at scsil4 channel 0 id 0 lun 1 type 8 scsi scan INQUIRY to host 14 channel 0 id 0 lun 2 Vendor IBM Model ULTRIUM TD2 Rev 38D0 Type Sequential Access ANSI SCSI revision 03 Attached scsi tape st0 at scsil4 channel 0 id 0 lun 2 st0 try direct i o yes alignment 512 B max page reachable by HBA 4503599627370495 Attached scsi generic sg7 at scsil4 channel 0 id 0 lun 2 type 1 scsi scan INQUIRY to host 14 channel 0 id O lun 3 Vendor IBM Model ULTRIUM TD2 Rev 38D0 Type Sequential Access ANSI SCSI revision 03 Attached scsi tape stl at scsil4 channel 0 id 0 lun 3 stl try direct i o yes alignment 512 B max
64. est is already running it can be bound to a set of CPUs by specifying the bit mask of the CPUs and the PID of the process For example if the PID of the process is 2045 taskset p OxA 2045 sets the affinity to CPUs 1 and 3 Note For the best send and receive performance use quad core CPUs with large shared L2 L3 cache Emulex Drivers for Linux User Manual Configuration Page 32 56 EMULEX MSI X Interrupts If both the computer and Linux version support MSI X the NIC driver automatically uses MSI X interrupts This helps to distribute the RX and TX completion processing load for the two ports across a maximum of four CPU cores and get the best throughput If you do not want to use MSI X and use INT X interrupts instead use the driver module parameter msix 0 SELinux Auditing Turning off auditing and SELinux can improve CPU utilization and in some cases give better throughput You can disable auditing by appending audit 0 in the boot command line You can turn off SELinux by specifying selinux 0 in the boot command line For example the boot command line kernel boot vmlinux 2 6 18 ro root dev md0 selinux 0 audit 0 boots the Linux kernel with selinux and audit features disabled You can get better CPU utilization and in some cases better throughput by disabling kernel debug options such as CONFIG_DEBUG_SLAB This requires you to build the kernel image and modules iSCSI Error Handling The goal of iSCSI error h
65. ge 28 Flow control setting is not stored per port after rebooting the system With flow control there is no persistence across reboot Always starts with both RX and TX on For persistence a config command should be invoked from an RC file executed at reboot Emulex Drivers for Linux User Manual Troubleshooting Page 39 gt EMULEX Table 11 Linux NIC Situations and their Resolutions Continued Situation Resolution When MILI and SNMP daemons start they This is a known issue and there is no solution However to trigger warning messages within SELinux avoid SElinux warning messages you can disable SELinux for certain operations Following are the two commands which are used to disable or enable SELinux 1 To disable SElinux open a terminal and enter the following command at the prompt echo 0 gt selinux enforc 2 To enable SElinux open a terminal and enter the following command at the prompt echo 1 gt selinux enforc Linux Log Messages Retrieving Linux NIC Error Log Codes Like all other driver and operating system messages all NIC driver messages are logged in the file var log messages This log file is an ASCII text file and can be viewed and searched with a text editor such as vim Large log files automatically rotate Rotated log files are named messages x where x is an integer To search the log file for error messages at the command prompt type
66. gt where lt ifacename gt is the name of the iface created in step 1 and lt NIC mac_address gt is the NIC MAC Address you are adding for discovery 3 Add the Transport Name by running this command iscsiadm m iface I lt ifacename gt op update n iface transport_ name v be2iscsi where lt ifacename gt is the name of the iface created in step 1 4 Restart the service by running this command service open iscsi restart 5 Perform target discovery using SendTargets by running this command iscsiadm m discovery t st p lt ip port gt I ifaceO P 1 where lt ip port gt is the IP address and port number and lt iface gt is the name of the iface created in step 1 Emulex Drivers for Linux User Manual Open iSCS Support Page 57 gt EMULEX 6 Add the iSCSI driver MAC address by running this command iscsiadm m iface I lt ifacename gt op update n iface hwaddress v lt iSCSI MAC Address gt where lt ifacename gt is the name of the iface created in step 1 and lt iSCSI MAC Address gt is the iSCSI MAC Address 7 Setthe initiator s IP address by running this command iscsiadm m iface I lt ifacename gt o update n iface ipaddress v lt IP gt where lt ifacename gt is the name of the iface created in step 1 and lt IP gt is the IP address 8 Log into the target by running this command iscsiadm m node T lt targetname gt p lt ip port gt I lt iface gt 1l where lt targetname gt is the t
67. he network is dropping frames too many retransmits on transmit side as indicated by netstat st it may help to make TSO less aggressive by increasing the divisor value or even turn off TSO To set the divisor to 8 run echo 8 gt proc sys net ipv4 tcp_tso win divisor To turn TSO on or off run the ethtool commands ethtool K lt ethX gt tso off ethtool K lt ethX gt tso on Emulex Drivers for Linux User Manual Configuration Page 29 gt EMULEX where ethX is the name of the Ethernet device you are working on Flow Control The UCNA supports IEEE 802 3x standard flow control which uses control packets to temporarily pause the transmission of packets between two endpoints These control messages are point to point they are not forwarded by switches or routers You must configure both endpoints for flow control The UCNA can either respond to flow control packets by temporarily pausing transmits or send flow control PAUSE packets when the transmitter is overwhelming the system s receive bandwidth For best performance flow control must be enabled on the switches as well as on UCNAs Receive and transmit flow control are on by default Flow control has limited usefulness at 10 Gb s network speeds because it only allows the receiver to completely turn off the incoming flow of packets it cannot just slow down the rate Current 10 Gb s devices tend to cause a dip in performance because the exceedingly fast pipeline of packets wil
68. ias ethl be2net alias eth2 be2net After adding the options line save the file and then rebuild initrd Interrupt Moderation Policy Settings Interrupt moderation policy settings control the rate of interrupts for the OneConnect UCNAs By default the driver implements an interrupt moderation scheme that is based on the I O load and the interrupt rate The default setting for the interrupt moderation policy tries to vary the interrupt rate between 3500 to 10000 interrupts per second Table 6 Interrupt Moderation Policy Settings describes the optional configuration settings Table 6 Interrupt Moderation Policy Settings Setting Parameter Description Disabled im_policy 0 Interrupt moderation algorithm is turned off in the driver Aggressive im_policy 1 Achieves the highest interrupt rate among all available settings Moderate im_policy 2 The default value Conservative im_policy 3 Achieves a lower interrupt rate than Moderate Very conservative im_policy 4 Achieves the minimum interrupt rate among all available settings Emulex Drivers for Linux User Manual Configuration Page 22 gt EMULEX While the default setting of Moderate may work for most configurations there are instances when the setting may need to be altered Changing the interrupt moderation policy setting should be based on the initiator system configuration the number of iSCSI targets that will be connected the I O lo
69. ications per adapter port connection Table 15 Negotiated Speed Specifications per Adapter Port Connection Port 0 Port 1 Port Link Status Speed 10 Gb s 10 Gb s Both ports are link up 10 Gb s 10 Gb s 1 Gb s Only Port 0 is link up 10 Gb s 1 Gb s 10 Gb s Only Port 1 is link up 10 Gb s 1 Gb s 1 Gb s Both ports are link up 1 Gb s 1 Gb s Only Port 0 is link up 1 Gb s 1 Gb s Only Port 1 is link up 1 Gb s 10 Gb s Only Port 0 is link up 10 Gb s 10 Gb s Only Port 1 is link up 10 Gb s Negotiating Speed on UCNA Mezzanine Cards For UCNA mezzanine cards the first negotiated speed is retained This could be either 10 Gb s or 1 Gb s depending on the switch connected To change the speed on these cards 1 Remove the switch from both of the ports 2 Insert the switch for one port and wait for the link to come up The UCNA will retain this speed until both links are down Emulex Drivers for Linux User Manual OneConnect Modules Port Speed Specifications Page 62
70. iguration fault tolerant software is present on the system that makes the iSCSI driver error handling redundant These configurations also require that I O errors be reported as soon as they are detected so that the software can fail over to an alternate path or an alternative node as quickly as possible When the iSCSI driver is run under these configurations the error handling implemented in the driver must be turned off by setting the default value of LDTO and ETO to 0 The changes will take effect during the next driver load Emulex Drivers for Linux User Manual Configuration Page 34 Troubleshooting Introduction gt EMULEX There are several circumstances in which your system may operate in an unexpected manner The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation General Driver Situations and their Resolutions Table 9 General Driver Situations and their Resolutions Situation Resolution FC link fails to come up If an FC link fails to come up verify that an 8 Gb s adapter is not attempting to connect to a 1 Gb s device Only 2 4 and 8 Gb s devices are supported on 8 Gb s adapters For LP21000 series adapters ensure the adapter is not in maintenance mode and that it is not running the manufacturing firmware Error states Authentication is enabled but authentication service is not running If you see this message in var l
71. inbox driver does not support ISNS or iSCSI boot features If you need these features use the out of box iSCSI driver provided by Emulex The Open iSCSI tools support the inbox driver so use them to configure and manage Open iSCSl The Emulex OneCommand Manager application supports the out of box iSCSI driver provided by Emulex The applications are not interchangeable between the drivers The iscsiadm utility is a command line tool allowing discovery of and logging into iSCSI targets as well as access and management of the open iSCSI database on all Linux installations The utility presents a set of operations that you can perform on iSCSI nodes sessions connections and discovery records Connecting to the iSCSI Target The following instructions describe the iscsiadm commands and examples you can use to discover targets and create iSCSI connections through open iSCSIl After setting up the target and initiator machines perform the following steps to discover the targets and create iSCSI connections Note The following instructions assume that the initiator machine is a Linux machine with a OneConnect UCNA installed 1 Create a new interface iface by running this command iscsiadm m iface o new I lt ifacename gt where lt ifacename gt is the name you provide for the iface 2 Add a NIC MAC address by running this command iscsiadm m iface I lt iface_ name gt op update n iface hwaddress v lt NIC mac_address
72. ipt installs the Ipfcdriver_2 6 RPM The RPM Installs the driver source files to the usr src Ipfc directory Builds the driver for the currently running kernel Installs the driver to the proper directory for the currently running kernel Maintenance and errata kernels are supported Once the RPM is installed the Ipfc install script creates a new ramdisk for the currently running kernel so that the FC and FCoE driver is loaded when the kernel is initialized during system startup Note You must uninstall any previous FC and FCoE driver kits that were installed from the Emulex CD or downloaded from the Emulex website i e not part of a distribution before installing this driver kit This installation will fail if a previous version of the FC and FCoE driver kit is detected Refer to Uninstalling the Source based RPM FC and FCoE Driver Kit on page 5 for more information When invoked without options the Ipfc install script automatically archives any driver that is shipped as part of the distribution s kernel during the installation procedure Old drivers that are archived during installation are then restored when the driver kit is uninstalled Note The OneCommand Manager application version 5 2 must be installed separately from the driver Refer to the OneCommand Manager Application Version 5 2 User Manual for more information Note The Ipfc install script does not support custom kernels For example k
73. itch port is connected to a single host then PortFast mode can be enabled on the switch port to eliminate delays in transitioning to forwarding state Emulex Drivers for Linux User Manual Configuration Page 33 gt EMULEX Configuring LDTO and ETO The following table lists the default values of LDTO and ETO and the limits within which they can be configured Table 8 LDTO and ETO Values Value perault Minimum Value an Value Value LDTO 20 secs 0 secs 3600 sec ETO 30 secs 0 secs 3600 secs Note If the ETO value is set to a number between 0 and 19 the driver assumes a value of 20 secs internally You will not see any modification to the registry LDTO and ETO values are configurable during insmod time The ETO value specified during insmod is the default ETO value that is applied to all targets The following example configures the LDTO and ETO during insmod of the driver These settings must be used every time the iSCSI driver is loaded using insmod insmod be2iscsi ko ldto 25 eto 20 In order to pass module parameters to the iSCSI driver when it is being used as a boot controller edit the file or etc modprobe conf file and add or modify the following line options be2iscsi paraml valuel param2 value2 Then type mkinitrd The change will take effect the next time the system is booted Error Handling Under MultiPath MPIO and Cluster Configurations In an MPIO or cluster conf
74. ither it s dev sd name or a file system LABEL to use the persistent name as well Using udev with st Devices The udev rules for tape devices are the same for disk devices There must be a unique ID that persists across initiator reboots and persists regardless of discovery order Another thing to consider is whether or not the tape device is one of many SCSI tape devices residing behind an FC controller or if it is an FC Tape device If it an FC Tape device then the WWPN is unique and can be used to create the persistent name In fact the scsi_id program should return this as the unique identifier with a single digit prefix If the FC controller has multiple SCSI tape devices behind it the WWPN is not unique and the persistent name must use multiple information elements to build the unique ID Below are examples of each scenario The first example is that of an FC Tape device This example uses SCSI generic sg rather than the SCSI tape driver root localhost scsi_id g s sys class scsi_generic sg0 350060b000029b592 The value returned has a leading prefix of 3 This value is the NAA type and what follows is the controller s WWPN Below is an example of the same tape device and a scsi_id call The response is the same root localhost scsi_id g s sys class scsi_tape nsto 350060b000029b592 In both examples g was needed because the vendor and model for this tape device were not in etc scsi_id config Emulex Driv
75. k faults are corrected None at this time This version of the driver should eliminate this problem However should you experience off line device issues increase the SCSI command timeout to a value greater than or equal to sixty seconds Emulex also provides a script which addresses this issue for 2 6 kernels To access the lun_change_state sh script click http www emulex com support linux index jsp then click the link to the appropriate driver and click the Linux tools link Under certain conditions of an I O load some targets cannot retire an I O issued by a Linux initiator within the default timeout of 30 seconds given by the scsi midlayer If the situation is not corrected the initiator to target condition deteriorates into abort recovery storms leading to I O failures in the block layer These types of failures are preceded by a SCSI IO error of hex 6000000 Emulex provides a script which addresses this issue To access the set_target_timeout sh script click http www emulex com support linux index jsp then click the link to the appropriate driver and click the Linux tools link FC and FCoE driver fails to recognize an adapter and logs unknown IOCB messages in the system log during driver load The adapter is running outdated firmware Upgrade adapter firmware to minimum supported revision listed in installation guide or newer Loading the FC and FCoE driver on SLES 11 SP1 reports unsuppo
76. l drain before the flow control can resume sending The ideal situation is a continuous pipeline of packets flowing between the endpoints not a start and stop flow Some examples where flow control greatly improves performance include e The UCNA is installed in 4x PCI Express slot or an underpowered server system If the PCI Express bus does not provide 10 Gb s of throughput due to chipset limitations or the bus width the UCNA cannot maintain 10 Gb s of incoming receive data It starts dropping packets quickly In this situation it may be beneficial to enable receive flow control in the UCNA and enable flow control in the attached switch for all devices This helps to slow down the transmitters e The UCNA transmits to 1 Gb s devices especially non TCP protocol If the UCNA transmits to a 10 Gb s switch with attached 1 Gb clients the UCNA may overwhelm the switch The switch is then forced to start dropping packets because although it may receive a 10 Gb s stream the client can only sink a 1 Gb stream In this situation it may be beneficial to enable transmit flow control in the UCNA and enable flow control for the 10 Gb s switch port You can enable and disable the OneConnect UCNA to respond to flow control pause frames from the other side switch or router using the following ethtool commands ethtool A lt ethN gt pause rx on ethtool A lt ethN gt pause rx off where lt ethN gt is the number of the Ethernet interface you a
77. loaded after a system reboot after upgrading the kernel These three situations may be resolved by upgrading the kernel There are two ways to install the driver into an upgraded kernel The method you use depends on whether or not you are upgrading the driver e Upgrade the kernel using the same version of the driver e Upgrade the kernel using a new version of the driver See the Installation section for these procedures Driver uninstall fails The Ipfc install uninstall script fails with an error Try the following solutions e Uninstall the OneCommand Manager application and SSC software packages These can be removed by running the uninstall script from the OneCommand Manager application installation directory e Unmount all FC disk drives Unload the Ipfcdfc and FC and FCoE driver e Use rpm e Ipfcdriver and e ocmanager and uninstall the new kits Ipfc install script exit code The Ipfc install script contains exit codes that can be useful in diagnosing installation problems See the Ipfc install script for a complete listing of codes and definitions The OneCommand Manager application software package does not install An error message states that inserv Service Elxlpfc has to be enabled for service ElxDiscSrvinserv exiting now sbin inserv failed exit code 1 Reinstall the driver with the Ipfc install script Emulex Drivers for Linux User Manual Troubleshooting Page 37
78. mber Note If the word Data is present in a LOG message any information to the right of Data is intended for Emulex technical support engineering use only Log Messages elx_mes0217 Block sgl registration required DMAsize lt reqlen gt great than a page DESCRIPTION The request to post SGL pages does not fit on a page DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes0221 FAN timeout DESCRIPTION A link up event was received without the login bit set so the driver waits E_D_TOV for the Fabric to send a FAN If no FAN if received a FLOGI will be sent after the timeout DATA None SEVERITY Warning LOG LOG_DISCOVERY verbose ACTION None required The driver recovers from this condition by issuing a FLOGI to the fabric elx_mes0237 Pending Link Event during Discovery State lt hba_state gt DESCRIPTION Received link event during discovery Causes discovery restart DATA None SEVERITY Warning LOG LOG_DISCOVERY verbose ACTION None required unless problem persists If persistent check cabling Emulex Drivers for Linux User Manual Troubleshooting Page 45 gt EMULEX elx_mes0274 Ipfc_nlp_put ndlp x pusgmap x x refcnt d void ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0275 lpfc_nlp_put ndlp x pusgmap x x refcnt d void ndlp ndlp gt nlp_usg_map
79. me did not match any for the configured masks for the specified ring DATA None SEVERITY Warning LOG LOG_SLI verbose ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support elx_mes0322 Ring lt ringno gt handler unexpected completion loTag lt loTag gt DESCRIPTION The driver could not find a matching command for the completion received on the specified ring DATA 1 ulpStatus 2 ulpWord 4 3 ulpCommand 4 ulpContext SEVERITY Warning LOG LOG_SLI verbose ACTION This error could indicate a software driver or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for Linux User Manual Troubleshooting Page 47 gt EMULEX elx_mes0328 Rsp Ring lt ring number gt error IOCB Data DESCRIPTION The firmware has returned an error for this IOCB DATA 1 lt iocb word 0 iocb word 7 gt 2 lt rsp word 0 rsp word 7 gt SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes0336 Rsp Ring lt ringno gt error OCB DESCRIPTION An IOCB error has occurred on the specified ring DATA 1 ulpWord 0 2 ulpWord 1 3 ulpWord 2 4 ulpWord 3 5 ulpWord 4 6 ulpWord 5 7 irsp 6 8 irsp 7 SEVERITY Warning LOG LOG_SLI verbose ACTION If the problem persists check the targets If the targets are okay report the error to Technical Support elx_mes0351 Config MSI mail
80. nel API has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION Set module parameter Ipfc_use_msi 0 elx_mes0490 MSI request_irq failed lt rc gt DESCRIPTION The request_irq kernel API has failed DATA None SEVERITY Warning LOG LOG_INIT ACTION Set module parameter Ipfc_use_msi 0 elx_mes0544 Ipfc_create_static_vport failed to issue dump mailbox command ret lt rc gt status lt mbxStatus gt DESCRIPTION Failed to issue a dump mailbox command for static VPort creation DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes0546 Ipfc_create_static_vport failed to create vport DESCRIPTION Failed to create a VPort DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes0704 At limitation of lt total gt preallocated command buffers DESCRIPTION The maximum number of command buffers have already been allocated DATA None SEVERITY Warning LOG LOG_FCP verbose ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 51 gt EMULEX elx_mes0705 Allocation request of lt num gt command buffers will exceed max of lt hba_queue_depth gt Reducing allocation request to lt size gt DESCRIPTION The number of command buffers requested will exceed the maximum so a smaller quantity will be allocated DATA None SEVERITY Warning LOG LOG_FCP verbose ACTION None required elx_mes0708 Allocation request of lt num_to_all
81. nges made using modprobe conf or the OneCommand Manager application version 5 2 persist if the FC and FCoE driver is uninstalled To return to the default settings you must modify the settings in modprobe conf FC and FCoE Driver Configuration Methods Using modprobe and etc modprobe conf The following sections describe how to set FC and FCoE driver parameters using the modprobe command and by manually editing etc modprobe conf Note Emulex recommends using the OneCommand Manager application version 5 2 or the OneCommand Manager Application CLI to change parameters See the OneCommand Manager Application Version 5 2 User Manual for more information Temporary Configuration Method When you manually load the FC and FCoE driver as a module using the modprobe command and change one or more driver parameter values it is a temporary configuration These changes are considered temporary because they are valid for the current session only or until the FC and FCoE driver is unloaded again Modprobe uses the modprobe conf file but parameters passed to it using the command line override parameters in the modprobe conf file Values can be expressed in hexadecimal or decimal notation Example of Temporary Configuration You want to temporarily set lun_queue_depth to 20 default is 30 for all host bus adapters in your system Load the FC and FCoE driver with the following command modprobe lpfc lpfc_lun queue _depth 20 Persistent Configura
82. ning Network driver performance tuning improves performance of the network driver the Linux Server operating system and ESX Server The UCNA is an x8 Generation 2 Gen 2 or Gen2 PCI Express device and requires substantial memory bandwidth in a system to support 10 Gb s data streams Improving Performance with PCI Express Bandwidth UCNA performance can be improved by selecting a more efficient PCle packet payload size If the system BIOS allows selection of a larger PCle packet size selecting at least a 512 byte PCle packet payload size provides the best efficiency for PCle data transfers Improving Performance with TCP Offload TCP offload helps memory bandwidth significantly by eliminating the data copy of receive packets This higher memory bandwidth leads to better network performance Most computers offer multiple distinct memory channels or memory interleaves which may not be enabled by default Check the manufacturer s documentation and BIOS parameters for details ion enabling optimal memory bandwidth features Typically all the DIMM slots must be populated to make use of all the memory channels As a general rule more DIMMs provide better performance by allowing a higher degree of memory access interleaving to occur Emulex Drivers for Linux User Manual Configuration Page 28 gt EMULEX Some servers may allow memory mirroring where the total memory is divided in half and each location is stored twice This allows faul
83. ntrols the rate of interrupts for OneConnect UCNAs large_io 128 128 512 The maximum transfer size in a single I O request in KB By default the OneConnect iSCSI driver supports a maximum of 128 KB of data in a single I O request This option can be used to enable support for 512 KB of data ina single I O request LDTO and ETO values are configurable during insmod time The ETO value specified during insmod is the default ETO value that is applied to all targets The following example configures the LDTO and ETO during insmod of the driver These settings must be used every time the iSCSI driver is loaded by insmod insmod be2iscsi ko ldto 25 eto 20 In order to pass module parameters to the iSCSI driver when it is being used as a boot controller edit the file etc modprobe conf and add or modify the following line options be2iscsi paraml valuel param2 value2 Then type mkinitrd The change will take effect the next time the system is booted The Interrupt Moderation policy im_policy parameter configures the iSCSI driver to use different settings for interrupt moderation An im_policy value of 1 achieves the highest interrupt rate while a value of 4 provides the least interrupt rate The default value is 2 An im_policy of O disables the interrupt moderation algorithm in the driver For more information see Interrupt Moderation Policy Settings on page 22 The large_io option can be used to modify the m
84. oc gt command buffers did not succeed Allo cated lt num_allocated gt buffers DESCRIPTION The allocation request for the specified command buffers did not succeed However the specified number of buffers has been allocated DATA None SEVERITY Warning LOG LOG_FCP ACTION None required elx_mes0711 detected queue full lun queue depth adjusted to d DESCRIPTION The driver detected a queue full status on a scsi command response New lun queue depth is reported DATA 1 New lun queue depth SEVERITY Warning LOG LOG_FCP verbose ACTION This may indicate an oversubscribed target array Check your SAN configuration and IO workload elx_mes0749 SCSI layer issued abort device DESCRIPTION The SCSI layer aborted a device DATA 1 ret 2 id 3 lun 4 snum SEVERITY Warning LOG LOG_FCP verbose ACTION None required elx_mes1259 mbox Issued mailbox cmd lt u mb mbxCommand gt while in stopped state DESCRIPTION Only the dump mailbox command and reset adapter mailbox command are allowed when in the stopped state DATA None SEVERITY Warning LOG LOG_MBOX ACTION None required elx_mes1268 Find ndlp returned NULL for oxid x x SID x x oxid sid int off rc DESCRIPTION Could not find the node for this DID DATA None SEVERITY Warning LOG LOG_ELS ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 52 gt EMULEX elx_mes1302 Invalid speed for this board
85. og messages and the adapter is in an Error state the fcauthd daemon probably is not running To check if fcauthd is running execute etc init d fcauthd status To start fcauthd execute etc init d fcauthd start If a SAN configuration has 256 targets mapped by the FC and FCoE driver any additional added targets do not get a target ID mapping by the driver and cause target discovery to fail Removing targets or reinitializing the link does not solve the problem Unload and reload the driver to reset available target IDs Ensure that the SAN configuration is correct prior to rebooting the driver This clears the driver s consistent binding table and free target IDs for new target nodes After loading an OEM supplied combined firmware OpenBoot image you may not be able to enable BootBIOS from the Iputil Boot BIOS Maintenance menu 1 Download the current OpenBoot only image for your adapter from the Emulex website 2 Load the current OpenBoot only image following steps listed in Updating BootBIOS section of this manual 3 Run Iputil return to Boot BIOS Maintenance menu 4 Enable BootBIOS rmmod fails to unload FC and FCoE driver module due to ERROR Module Ipfc is in use This message can appear when you attempt to remove the driver and there is a Logical Volume Group dependent on the driver 1 Make the Logical Volume Group unavailable Type Ivchange a n XXXXXXX where xxxxxx is the Volume Group Name
86. oid ndlp ndlp gt nlp_usg_map atomic_read amp ndlp gt kref refcount DESCRIPTION Node clean up was called to prepare the node for release DATA None SEVERITY Warning LOG LOG_NODE ACTION None required elx_mes0301 READ_SPARAM no buffers DESCRIPTION The driver attempted to issue a READ_SPARAM mailbox command to the adapter but there were no buffers available DATA None SEVERITY Warning LOG LOG_MBOX verbose ACTION This message indicates 1 Kernel virtual memory is depleted Check that the system meets minimum RAM requirements for the Emulex Fibre Channel adapter Try closing other applications to free some memory 2 A possible driver buffer management problem If the problem persists report the error to Technical Support elx_mes0302 REG_LOGIN no buffers DESCRIPTION The driver attempted to issue a REG_LOGIN mailbox command to the adapter but there were no buffers available DATA 1 Did 2 flag SEVERITY Warning LOG LOG_MBOxX verbose ACTION This message indicates 1 Kernel virtual memory is depleted Check that the system meets minimum RAM requirements for the Emulex Fibre Channel adapter Try closing other applications to free some memory 2 A possible driver buffer management problem If the problem persists report the error to Technical Support elx_mes0313 Ring lt ringno gt handler unexpected Rctl lt Rctl gt Type lt Type gt received DESCRIPTION The Rctl Type of a received fra
87. ounted and available as sys You must first identify the scsi_host which represents the adapter for which you want to modify the FC and FCoE driver parameters All scsi_hosts bound to the FC and FCoE driver can be viewed with the following command ls d sys bus pci drivers lpfc host Assuming you are interested in adapter scsi_host 7 you can list the FC and FCoE driver parameters for this particular adapter as 1s 1 sys class scsi_host host7 lpfc An example output is as follows r r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_acko r r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_fcp_class rw r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_fdmi_on r r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_link_speed rw r r 1 root root 4096 Feb 28 15 34 sys class scsi_host host7 lpfc_log verbose r r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_lun_queue_ depth rw r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_max_luns rw r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_nodev_tmo rw r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_scan_down r r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_topology rw r r 1 root root 4096 Feb 28 17 03 sys class scsi_host host7 lpfc_use_adisc Notice that the F
88. page reachable by HBA 4503599627370495 Attached scsi generic sg8 at scsil4 channel 0 id 0 lun 3 type 1 This log output shows a controller at LUN 0 the medium changer at LUN 1 and two SCSI tape devices at LUNs 2 and 3 The example below is what the scsi_id call returns root localhost scsi_id g s sys class scsi_tape nsto 1LIBM ULTRIUM TD2 1110133831 root localhost scsi_id g s sys class scsi_tape nstl 1LIBM ULTRIUM TD2 1110133994 Notice that the unique ID is actually comprised of three value with space delimiters A udev rule must have a unique ID for the device meaning all three parts of this returned string are required To do this use the following command root localhost scsi_id u g s sys class scsi_tape nst0 1LIBM ULTRIUM TD2 1110133831 root localhost scsi_id u g s sys class scsi_tape nstl 1LIBM ULTRIUM TD2 1110133994 Creating the udev persistent name for SCSI tape uses the same process as SCSI disk once the SCSI ID call needed to extract a unique ID is known Below is the rule for the FC Tape device BUS scsi SYSFS vendor HP SYSFS model ULTRIUM 3 SCSI PROGRAM sbin scsi_id p 0x83 u g s sys class scsi_tape nst n RESULT 350060b000029b592 SYMLINK fc_lun_st n The rule for the FC SCSI tape device follows BUS scsi SYSFS vendor IBM SYSFS model ULTRIUM TD2 PROGRAM sbin scsi_id p 0x83 u g s sys class scsi_tape nst n RES
89. physically located on the same port Note This parameter was created to reduce the amount of hardware resources RPI that the driver requires In a configuration where there are many VPorts on one physical port this feature will greatly reduce the number of RPI that the driver utilizes VPort Configuration Limits The following is a list of limits that are supported by the 8 3 5 x driver and configurations that were tested with it It is highly recommended that you adhere to these limits Configurations exceeding any one or more of these limits are unsupported These limits are broken up into two groups Enforced limits are limits that the driver is able to enforce and will prevent the user from exceeding Un enforced limits are limits that the driver cannot enforce and configurations that exceed these limits are unsupported Emulex Drivers for Linux User Manual Configuration Page 27 56 EMULEX Configuration limits e All I O to devices accessed through a VPort must be stopped and all file systems must be unmounted before the VPort is deleted or the driver is unloaded For enterprise class adapters the maximum number of virtual ports configurable on a physical port is 64 The hardware will allow more than 64 VPorts to be created but the driver has only been qualified at 64 For mid range adapters the maximum number of VPorts configurable on a physical port is 16 e The maximum number of LUNs supported on each driver po
90. poll_tmo 10 1 255 Milliseconds the driver waits between polling FCP ring interrupts Ipfc_topology 0 0x0 loop FC link topology defaults to loop if it fails then P2P attempts point to point mode Not applicable for 0x2 P2P only OneConnect UCNAs 0x4 loop only 0x6 P2P then loop Ipfc_use_adisc 0 0 Off 1 On Sends ADISC instead of PLOGI for device discovery or RSCN Using udev for Persistent Naming SLES 11 is configured by default with udev to provide persistent names for hard disks including FC attached disks Using udev to Discover Logical to Physical Mappings for sd Devices Persistent names for sd devices are provided in the dev disk by id directory To find the persistent udev name for the disk which is currently sdc type cd dev disk by id ls 1 grep sdc The sample output is shown below lrwxrwxrwx 1 root root 9 2006 08 01 19 08 scsi 32000000c5005d6e6 gt sdc In the above example the disk has no partitions If the disk had two partitions the output would look like the following lrwxrwxrwx 1 root root 9 2006 08 01 19 08 scsi 32000000c5005d6e6 gt sdc lrwxrwxrwx 1 root root 10 2006 08 01 19 08 scsi 32000000c5005d6e6 partl1 gt sdcl lrwxrwxrwx 1 root root 10 2006 08 01 19 08 scsi 32000000c5005d6e6 part2 gt sdc2 Emulex Drivers for Linux User Manual Configuration Page 17 gt EMULEX Configuring the System to Boot From SAN Using Persistent Names To use
91. r Linux systems the iSCSI driver generates warnings to the var log messages log file The log file is an ASCII text file and can be viewed and searched with your preferred text editor Emulex Drivers for Linux User Manual Troubleshooting Page 42 gt EMULEX To search the log file for error messages at the command prompt type cd var log vim messages For example you may see the following message be2iscsi driver detected error 0x12790006 Linux iSCSI Error Log Entries The following is a brief description of the error log codes generated by the iSCSI Linux driver It includes the error code the message displayed and the meaning of the message and the recommended resolution Note Some error log entries may be followed by additional entries that provide further information Table 13 Linux iSCSI Error Log Entries Message Recommended Resolution Hardware Initialization Failed Either Hardware Firmware is not initialized or is malfunctioning This failure indicates that the hardware has not been initialized or is malfunctioning This may also indicate that the firmware is not running correctly Driver version does not match Firmware Please run Installer This failure indicates that the driver version that is running on the system does not match the version of the firmware flashed on the board This issue can be addressed by running the installer from the desired version Link
92. re working on The OneConnect UCNA can be configured to send flow control pause frames using the following ethtool commands ethtool A lt ethN gt pause tx on ethtool A lt ethN gt pause tx off where lt ethN gt is the number of the Ethernet interface you are working on RX and TX flow control are ON by default Refer to the switch router documentation to determine how link level flow control can be configured on the switch router to which the OneConnect UCNA port is connected Note If multiple PCI functions are exposed for a single 10 Gb s Ethernet port such as in a blade configuration the flow control parameter must be set the same on all adapters for the port The results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10 Gb s port Emulex Drivers for Linux User Manual Configuration Page 30 gt EMULEX RX Frame Coalescing GRO The iSCSI driver consolidates small TCP segments into a large frame before passing the frame to the network stack using the Generic Receive Offload GRO mechanism RX frame coalescing can provide considerable boost to TCP receive performance RX frame coalescing is enabled by default In some configurations where the end point for the TCP connection to which the packets belong is not in the current server such as routers and bridges RX coalescing should not be enabled The GRO mechanism takes care of this automatically Maximum Transmis
93. rt is 256 e The maximum number of targets supported for each driver port is 255 The maximum number of driver ports in one zone is 64 This limit is based on the system s ability to recover from link events within the time constraints of the default timers The use cases of NPIV that involve virtual server environment include associating a virtual port with a virtual machine and placing the virtual machine in its own zone This will result in one virtual port per zone In the case of load balanced environments this can increase typically to two virtual ports per virtual machine to a practical limit of something far less than 50 In the NPIV cases not related to virtual server environments zoning will typically be initiator zoning again resulting in one virtual port or a low number of virtual ports in the case of load balancing within a given zone If there are too many virtual ports within a single zone expected behavior will include devices going lost after link events e Minimum lifetime of a virtual port 60 seconds There is an un enforced limit of 60 seconds between the creation of a virtual port and the deletion of the same virtual port Virtual ports are designed to be an entity that lives for a long time in the system and the creation of VPorts is asynchronous This means that a virtual port might not be finished with Fibre Channel or SCSI discovery when the command to create a virtual port is finished Network Driver Performance Tu
94. rted module tainting kernel in system log This message is logged by the kernel whenever a module which is not shipped with the kernel is loaded This message can be ignored System panics when booted with a failed adapter installed Remove the failed adapter and reboot Unloading the FC and FCoE driver on SLES 11 SP1 causes messages like the following to be logged in the system log umount dev disk bypath pci 0000 02 04 0 scsi 0 0 1 0 not mounted These messages are normal output from the SLES 10 hotplug scripts and can be safely ignored Emulex Drivers for Linux User Manual Troubleshooting Page 36 gt EMULEX Table 9 General Driver Situations and their Resolutions Continued Situation Resolution Driver Install Fails The pfc install script fails to install the driver The install script may fail for the following reasons A previous version of the driver is installed Run the lpfc install uninstall script and then try to install the driver e The current driver is already installed Runa supported RHEL or SLES kernel No module Ipfc found for kernel error message When upgrading the kernel rpm generates the following error No module Ipfc found for kernel KERNELVERSION A recently upgraded kernel cannot find the ramdisk After upgrading the kernel the kernel cannot find the ramdisk which halts or panics the system The driver is not
95. se_ec3210 NMI 0 LOC 1555444 155579 ERR 1 MIS 0 In the above example RX and TX interrupts from both portO ethO and port1 eth1 are directed to CPUO This could lead to CPUO becoming very busy making it a bottleneck To direct the RX and TX interrupts from port1 to CPU1 write the CPU mask into smp_affinity mask of the corresponding interrupt vector echo 2 gt proc irg 130 smp_affinity echo 2 gt proc irg 138 smp_affinity If there are more than two cores it is a good idea to direct all the four OneConnect UCNA interrupts to four different cores If the CPU has four cores use the four cores that belong to the same physical CPU for best performance In an SMP system although the scheduler attempts to distribute the load you can achieve more consistent performance by binding the send and receive processes to the appropriate CPU To find the appropriate CPU to bind to first find the current utilization of each CPU using the command top For example in a quad core system if the RX and TX interrupts from portO and port1 are bound to CPUs 0 1 2 and 3 respectively and with the application test running shows that CPUs 0 and 2 are extremely busy and CPUs 1 and 3 are relatively idle it helps to bind the application s send and receive data to CPUs 1 and 3 This can be done using the taskset command For example taskset c 1 3 netserver starts the command netserver with affinity to CPUs 1 and 3 If the application or t
96. sion Unit MTU The Maximum Transmission Unit MTU is the Ethernet packet payload size This does not include the Ethernet frame header or the trailing CRC The NIC driver for Linux supports MTUs between 256 bytes and 9000 bytes The default MTU is set to 1500 If other elements in the network path support a larger MTU you can increase the MTU up to 9000 using the ifconfig command To do this run ifconfig lt ethN gt mtu 9000 where lt ethN gt is the number of the Ethernet interface you are working on The largest MTU that does not cause IP fragmentation in the network path gives the best performance By default the Linux network stack monitors the lowest path MTU along each open network path Path MTU Discovery and adjusts the MSS of established TCP connections to prevent IP fragmentation Interrupt Coalescing On the NIC driver adaptive interrupt coalescing is enabled by default In light traffic the interrupt delay is disabled for lower latency As the number of interrupts per second increases the delay is increased to the default higher limit of 96 microseconds You can disable adaptive interrupt coalescing for both RX and TX by running the ethool command ethtool C lt ethN gt adaptive rx off where lt ethN gt is the number of the Ethernet interface you are working on If adaptive interrupt coalescing is enabled you can change the default lower and higher interrupt delay limits of O and 96 microseconds The coalescing values for
97. t failed and MTU will not be changed Warning Pause param set failed The firmware command to set pause frame settings failed Warning OneConnect card in a Gen lt D gt The driver found a OneConnect UCNA in a Gen1 x lt D gt PCIe slot It should be slot or a PCle slot that is less than x8 wide The in a Gen2 x8 slot for best UCNA will continue to work but will not provide the performance best performance Information MTU changed from lt DDD gt to MTU size changed as requested lt DDD gt Information Link down Informational message about change in Link status Emulex Drivers for Linux User Manual Troubleshooting Page 41 Table 12 Linux NIC Warning Log Entries Continued gt EMULEX successfully Severity Message Displayed Description Error lt D gt pending tx completions The driver did not get completions for some transmit requests from the NIC while unloading the driver This is usually a indication of a problem with the NIC Error Firmware lt filename gt load The firmware image under lib firmware error signature did not lt filename gt did not have the signature of a proper i OneConnect firmware image file The firmware in match this file will not be flashed Copy the proper file and try flashing again Error Memory allocation failure The driver could not allocate memory required for while flashing flashing the firmware image Try flashing after some time If the pro
98. t in a page DATA None SEVERITY Warning LOG LOG_INIT ACTION None required Emulex Drivers for Linux User Manual Troubleshooting Page 54 gt EMULEX elx_mes2569 Ipfc_dump_fcoe_param memory allocation failed DESCRIPTION Memory allocation has failed DATA None SEVERITY Warning LOG LOG_MBOX ACTION None required elx_mes2579 Slow path wqe consume event carries miss matched qid wcqe gid lt wcqe_quid gt sp qid lt sp_quid gt DESCRIPTION The consumed entry does not have the slow path s queuelD DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes2580 Fast path wqe consume event carries miss matched qid wcqe qid lt fcp_waqid gt DESCRIPTION The consumed entry does not have the fast path s queuelD DATA None SEVERITY Warning LOG LOG_SLI ACTION None required elx_mes2582 Not enough WQs lt max_wq gt from the pci function for supporting the requested FCP WQs lt cfg_wq_count gt the actual FCP WQs can be supported lt wq_count gt DESCRIPTION The driver was not configured with enough fast path work queues DATA None SEVERITY Warning LOG LOG_INIT ACTION None required elx_mes2593 The FCP EQ count lt cfg_fcp_eq_count gt cannot be greater than the FCP WQ count lt cfg_fcp_wq_count gt limiting the FCP EQ count to lt cfg_fcp_wq_count gt DESCRIPTION The fast path event queue cannot be greater than the fast path work queue count DATA None SEV
99. t recovery if one memory location detects an error but it greatly reduces the perceived memory bandwidth of the system Nearly any desktop or low end server has enough memory bandwidth for OneConnect UCNAs to support DMA at 20 Gb s of data 10 Gb s read 10 Gb s write However most of the memory demands come from the processor accessing the data for either packet copies in the non offloaded networking stack or application accesses All processor memory accesses use the front side bus FSB The clock speed of this bus is critical for allowing efficient memory bandwidth Note A system with a faster processor front side bus FSB clock speed performs better than a system with a slower FSB clock speed The following section discusses ways to use various driver properties and Linux properties to performance tune a system You can read and set most driver settings by using the ethtool utility Network Buffer Sizes and TCP Parameters The optimal size for the network queues and buffers depends on several factors such as protocol number of streams connections request size and application behavior The following network configuration settings are a good combination to get best bidirectional transmit and receive performance with six or more TCP connections UDP streams echo 4096 87380 4194304 gt proc sys net ipv4 tcp_rmem echo 4096 16384 4194304 gt proc sys net ipv4 tcp_wmem echo 64000000 gt proc sys net core rmem default echo 6400
100. the Ipfc install script with the uninstall option Type usr src lpfc install uninstall 2 Upgrade the kernel and or distribution 3 Reboot the system with the new kernel Download the driver kit from the Emulex website or copy it to the system from the installation CD 5 Log on as root to a terminal and unpack the tarball with the following command tar xzf lpfc_2 6 driver_kit lt driver version gt tar gz Emulex Drivers for Linux User Manual Installation Page 4 gt EMULEX 6 Change to the directory that is extracted cd lpfc_2 6_driver_kit lt driver version gt 7 Execute the Ipfc install script with no options to install the new driver kit Type lpfc install 8 Reboot the system to complete re installation of the Emulex driver Uninstalling the Source based RPM FC and FCoE Driver Kit Note Driver parameter changes made using the OneCommand Manager application version 5 2 or etc modprobe conf persist if the driver is uninstalled To return to the default settings you must modify the settings in etc modprobe conf Note You must run the uninstall script that shipped with the version of the driver kit you want to remove This section describes how to uninstall a previous version of the Emulex 8 x driver for Linux The uninstall procedure automatically restores the archived FC and FCoE driver To uninstall the source based RPM FC and FCoE driver 1 Log on as root 2 If possible
101. tion Method To make the FC and FCoE driver parameters persistent across module loads and reboots modify the etc modprobe conf file If driver parameters are modified in etc modprobe conf the FC and FCoE driver must be reloaded for the parameters to take effect Also a new ramdisk image is required if you want the changes to take effect in the next boot See Creating a New Ramdisk Image on page 13 to learn how Emulex Drivers for Linux User Manual Configuration Page 11 gt EMULEX The FC and FCoE driver parameters are specified in etc modprobe conf via the options command For example the following sets the verbose flag options lpfc lpfc_log_verbose 0xffff If the same option is specified in both the etc modprobe conf and on the modprobe command line the option setting in the command line takes precedence Temporary FC and FCoE Driver Configuration by Read Write to sysfs Sysfs is a virtual filesystem that exposes the structure of the system It also includes interfaces to driver parameters through which the FC and FCoE driver parameters can be viewed and modified Since these interfaces are available only after driver load only those parameters that can be modified dynamically can be changed However all FC and FCoE driver parameters can be read through sysfs Note Sysfs changes only exist during driver load and are lost when the FC and FCoE driver is unloaded or the system is rebooted The sysfs filesystem is m
102. upport the following distributions e Red Hat Enterprise Linux 6 and 6 1 Intel x86 Intel EM64T and AMD64 architectures e SuSE Linux Enterprise Server 11 SP1 Intel x86 Intel EM64T and AMD64 architectures e XenServer 5 6 SPx and XenServer 6 0 Compatibility For a list of adapters that are compatible with the standalone driver kits see the specific driver s Downloads page on the Emulex website For compatible firmware versions see the Downloads page for the specific adapter Note Check the Emulex website for the latest firmware releases Note NPIV is supported on Emulex SLI 4 OCe10100 UCNAs NPIV is also supported on all SLI 3 4 Gb s and 8 Gb s adapters Emulex enterprise class 5 digit adapter model number and midrange class 4 digit adapter model number adapters support SLI 3 The LPFC 8 3 5 x driver supports all adapters running SLI 2 but NPIV support is not available in SLI 2 mode For SLI 4 and SLI 3 supported adapters use the latest recommended firmware for NPIV support Prior to Download e You must uninstall any previous driver kits and or Application Helper Modules that were downloaded and installed from the Emulex website not part of a distribution before installing this driver kit Known Issues e See the product release notes for the latest information Emulex Drivers for Linux User Manual Installation Page 2 gt EMULEX Installing the Source based RPM FC and FCoE Driver Kit The Ipfc install scr
103. use iSCSI attached drives the uninstall works properly but you must reboot after the uninstallation is complete Execute the elx_iscsi_install sh script with the uninstall option Type elx_iscsi_install sh uninstall Booting From a Non Zero LUN Attached to an Emulex Adapter This section describes how to configure SLES 11 SP1 to boot from an FC attached disk device other than dev sda This example uses dev sdb To boot from a non zero LUN attached to an LPFC adapter 1 OO eS 8 9 10 11 12 Configure the Emulex adapter bootBIOS to boot from the desired LUN Start the standard SLES 11 SP1 installation At the Installation Settings screen after configuring the desired partitions select the Expert tab Select Booting to change the bootloader configuration The Boot Loader Settings window appears Select the Boot Loader Installation tab In the section labeled Boot Loader Location select Custom Boot Partition then select the root partition or boot partition if you configured one from the drop down box Click the Boot Loader Options button The Boot Loader Options window appears Select the Write generic Boot Code to MBR checkbox Click OK In the Boot Loader Settings window Click Finish Proceed with the installation During the first boot after the installation use the GRUB command line to change all hd1 references to hd0 then continue the boot process Edit the GRUB configuration in

Download Pdf Manuals

Related Search

Related Contents

Service Manual - Dana Corporation  User's manual  Bedienung des Geräts  Dell OpenManage Server Administrator Version 7.0 Command Line Interface Guide  Brochure LMG95  GE 90-30 PLC Switch User Manual  MODE D`EMPLOI (Français) — - Absolu    Taro-TK-10389 TWP 取扱説明書.jt  BEDIENUNGSANLEITUNG  

Copyright © All rights reserved. Failed to retrieve file