------------------------------------------------------------------------------- Instructions for Installing Firmware on AIX ------------------------------------------------------------------------------- Copy firmware file (name may vary, but similar to df1060e214105204.00000000000999913934) to target machine in directory /etc/microcode At a command prompt in AIX, type 'diag' Press Enter Press Enter Choose 'Task Selection' and press Enter Choose 'Microcode Tasks' and press Enter Choose 'Download Microcode' and press Enter Choose (by pressing Enter while highlighted) one port from each ASIC of your VenomDL Press F7 to commit to updating selected adapters Choose /etc/microcode and press Enter Choose firmware file (name may vary, but similar to df1060e214105204.00000000000999913934) Press Enter Verify adapter was updated correctly by reading diag screen output. Press Enter after each adapter has finished updating Reboot machine if necessary Verify firmware level by looking at Z9 field after reboot using 'lscfg -vl fcsX' command. Replace 'X' with the number of your fcs device. ------------------------------------------------------------------------------- Instructions for Installing Firmware on Linux using ethtool ------------------------------------------------------------------------------- Use this method to download the new microcode to a Linux system: NOTE: The instructions that follow are specific Linux commands. Linux commands are CASE (lower and upper) SENSITIVE, and must be entered exactly as shown, including filenames. 1) Acquire the .zip file from OSS and place it on the partition or system to which the emulex adapter is allocated. The .zip files have the format VenomDL_FW_ddddd.zip where 'ddddd' is the 5-digit version number of the firmware update you will apply. 2) Unpack the zip file with unzip VenomDL_FW_ddddd.zip 3) Move the .grp file which is extracted into the firmware directory: mv ddddd.grp /lib/firmware You can ignore the other file which is unpacked whose name starts with 16 hexadecimal digits; it is used only for AIX. 4) Identify which interfaces on the partition or system are on the lancer adapter: give the command ifconfig -a | grep eth for each of the ethX names listed, give the command ethtool -i ethX any interface which shows 'be2net' as the driver, for example ltcsatiocp7:~ # ethtool -i eth3 driver: be2net version: 4.4.62.0 firmware-version: 0.0.9999.14246 bus-info: 0002:01:00.0 is based on an emulex adapter. It is possible to have multiple emulex adapters all using the be2net driver allocated to a single partition/system. To identify which type of emulex adapter an interface using the be2net driver is based on, give the command lspci -d 10df: This displays PCI adapters with the PCI ID of the lancer family of adapters, for example 01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) Correlate the bus numbers shown, to the 'bus-info' values from the 'ethtool -i' output as shown above for the interfaces using the be2net driver. Choose one of the set of matching interfaces. 5) Two halves of the venom adapter: The venom adapter consists of two allocable halves each with four ports. In a system using logical partitioning, each half can be allocated to a different partition. If this is the case on your system, each half will present four interfaces using the be2net driver, in the partition it's allocated to. Their bus numbers will be consecutive as in the example 'lspci -d' output in step 4. If both halves are allocated to the same partition, then two groups of four interfaces will be presented, for example: 0000:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0000:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0000:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0000:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0001:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0001:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0001:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0001:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) Each of these halves must be flashed with a firmware update separately. Use the methodology in step 4 to select one interface in each half on which to apply the update for that half. 6) Check the firmware version of the interface(s) you've selected. Using the 'ethtool -i' output obtained in step 4, check whether the interfaces you've selected to apply the firmware update to, need it. The 5-digit 'ddddd' component at the end of the version number should be strictly lower than the equivalent part of the .grp filename. Otherwise, you do not need to apply the update you've acquired from OSS (check there for a newer one ?). If the firmware version currently on your adapter is not in the ddddd format then it is likely outdated and you need to apply the update. 7) Bring the interface(s) up Emulex adapter interfaces must be configured with a IP address in order to use them to flash firmware. Check the current configuration of the interface with 'ifconfig ethX'. If it does not have an IP address assigned, configure one; it can be fictitious (not an allocated address in your network infrastructure) for example: ifconfig ethX 192.168.1.1/24 8) Stop all applications using the interfaces 9) Flash the firmware update and restart For each venom half, flash the firmware update on the interface ethX you've chosen from that half with ethtool -f ethX ddddd.grp The firmware image will be acquired from /lib/firmware and applied to that half of the venom. If the command succeeds, no message will be displayed. If the command fails, a message will be displayed when it completes. You can confirm the success or failure of the firmware flash with tail /var/log/messages | grep -i firmware This will show system log messages indicating the success or failure of the flash. At this point you need to reboot the partition or system in order for the firmware flash to be activated. validate that the firmware has been updated with ethtool -i ethX The firmware version displayed should match that in the name of the .grp file you applied. The procedures in this step need to be done for each half of the venom adapter on which you want to update firmware. Complete all action through the end of a successful reboot and firmware version check on one before starting any activity on the second. ------------------------------------------------------------------------------- Instructions for Installing Firmware on Linux using Emulex DUD ------------------------------------------------------------------------------- This document provides information on installing SLES11-SP2 lpfc and be2net driver updates for Emulex lancer based adapters, including Vanguard, VenomDL, Bluefin, Houston, BountyFC, BountyFCoE, Flintrock. The process is intended for a new installation of SLES11-SP2 on a local HDD or a SAN HDD hosted by one of the above adapters. This document does not cover installing lpfc or be2net driver updates on a system already installed with SLES11-SP2. Prerequisites: - One or more of the above adapters installed in the system or lpar - Current firmware on the installed adapters (check with engineering for current version for your adapter) - Emulex Driver Update Disk for SLES11-SP2 w/ updated lpfc and be2net drivers, physical iso image or virtual iso image - SLES11-SP2 installation media, physical iso image, virtual iso image or NFS,SLP or other installable image Current Emulex Driver Update Disk for SLES11-SP2 w/ updated lpfc and be2net drivers can be downloaded from: http://ausgsa.ibm.com/~rlary/public/emulex/drivers/dud/elx-dud-sles11-sp2-2012-06-19.iso ( you may need gsa account if you do not have one, visit http://ausgsa.ibm.com/gsadoc/index.shtml) If you are installing to an lpar in a system with VIOS or IVM, you can create a Virtual Optical device and copy the DUD iso image to that device. If your lpar or system does not have acess to Virtual Optical device you will need to copy the ISO image on to DVD media and use physical optical device. The following screens are what you will see if you have performed a NIM installation. They maybe different if you install from physical or virtual optical media. You are looking for the screen titled "Main Menu". Once you reach "Main Menu", proceed through the sequence of screens, entering the values shown below. The critical step is where the Driver Update is read: Reading Driver Update... This step must report: Driver Update ok If this step does not report Driver Update ok, there is an issue with your Driver Update media. You can use the md5sum command ( # md5sum /dev/{media_device} it should report: 9d7c60423f3ba46c5a50e4f2e57b0a78 -- Start of installation screens -- >>> SUSE Linux Enterprise Server 11 installation program v3.3.81 (c) 1996-2010 SUSE Linux Products GmbH <<< Starting udev... lpfc 0000:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x20 x0 x0 x0 0 lpfc 0000:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 sd 0:0:1:0: [sda] Assuming drive cache: write through sd 0:0:2:0: [sdb] Assuming drive cache: write through sd 0:0:1:0: [sda] Assuming drive cache: write through sd 0:0:2:0: [sdb] Assuming drive cache: write through sd 0:0:2:0: [sdb] Assuming drive cache: write through sd 0:0:1:0: [sda] Assuming drive cache: write through ok Loading basic drivers... ok Starting hardware detection... ok (If a driver is not working for you, try booting with brokenmodules=driver_name.) Emulex Fibre Channel drivers: lpfc* Emulex Fibre Channel drivers: lpfc* IBM Virtual SCSI 0 drivers: ibmvscsic* IBM Virtual Ethernet card 0 drivers: ibmveth* Make sure that CD number 1 is in your drive. 1) OK 2) Back > 2 >>> Linuxrc v3.3.81 (Kernel 3.0.13-0.27-ppc64) <<< Main Menu 1) Start Installation 2) Settings 3) Expert 4) Exit or Reboot > 3 Expert -- Time: 22:09 1) System Information 2) Kernel Modules (Hardware Drivers) 3) Verify Installation CD-ROM/DVD 4) Eject CD 5) Show config 6) Change config 7) Start shell > 2 Kernel Modules (Hardware Drivers) 1) Load ppc Modules 2) Load USB Modules 3) Load FireWire Modules 4) Load File System Modules 5) Load Unknown Modules 6) Show Loaded Modules 7) Unload Modules 8) Add Driver Update 9) Show Driver Updates > 8 Searching for storage devices... Please choose the Driver Update medium. 1) sr0: CD-ROM, AIX VOPTA 2) sda1: Partition, AIX VDASD 3) sda2: Partition, AIX VDASD 4) sda3: Partition, AIX VDASD 5) sdb1: Partition, AIX VDASD 6) sdb2: Partition, AIX VDASD 7) other device > 1 Reading Driver Update... Driver Update ok Kernel Modules (Hardware Drivers) 1) Load ppc Modules 2) Load USB Modules 3) Load FireWire Modules 4) Load File System Modules 5) Load Unknown Modules 6) Show Loaded Modules 7) Unload Modules 8) Add Driver Update 9) Show Driver Updates > Expert -- Time: 22:09 1) System Information 2) Kernel Modules (Hardware Drivers) 3) Verify Installation CD-ROM/DVD 4) Eject CD 5) Show config 6) Change config 7) Start shell > Main Menu 1) Start Installation 2) Settings 3) Expert 4) Exit or Reboot > 1 Resume installation as normal. ------------------------------------------------------------------------------- END OF README -------------------------------------------------------------------------------