emulex boot code user manual

emulex boot code user manual

By continuing to browse the site you are agreeing to our use of cookies.You can change lines. For any questions, contact us. The translation is for reference only. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).Then, restart the browser. For example: All boot code image files are expected to be in the. The HBA types are always Emulex model names. For example, an Emulex model An adapter's Elxflash model name can be seen by. This guide is intended for technical specialists, sales specialists, sales engineers, and IT architects who want to learn more about the adapters and consider their use in IT solutions. They also seamlessly support Brocade ClearLink diagnostics through Emulex HBA Manager (formerly named Emulex OneCommand Manager), ensuring the reliability and management of storage network when connected to Brocade FC SAN fabrics. This is essential when ports are used in active-standby mode. These low latency HBAs can also improve your VDI experience, providing noticeable improvements during boot storms, and allow faster data warehousing and meet the massive bandwidth requirements of flash storage arrays. Allows the IT administrator to detect faulty cables and optics in minutes versus hours. Brocade ClearLink is also seamlessly integrated into Emulex HBA Manager. VMware vCenter plug-in provides HBA Manager support within a VMware environment. Note: Other transceivers are not supported. Automated installation and configuration of driver and management tools simplifies deployment of multiple adapters within Windows environments. A single installation of driver and management application eliminates multiple reboots and ensures that each component is installed correctly and the HBA is ready to use.http://effectlabindia.com/userfiles/daewoo-fridge-service-manual.xml

• emulex boot code user manual, emulex boot code user manual pdf, emulex boot code user manual user, emulex boot code user manuals, emulex boot code user manual download.

Powerful automation capabilities facilitate remote driver parameter, firmware, and boot code upgrades. In addition to the GUI interface, management functions can also be performed through a scriptable command-line interface (CLI) and a web browser. See the DB Series product guides for models and configuration options: When installed in a supported server, the adapters assume the servers’s base warranty and any Lenovo Services warranty upgrade. A current list of Lenovo trademarks is available on the Web at. Please check your inbox, and if you can’t find it, check your spam folder to make sure it didn't end up there. Please also check your spam folder. No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex. 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 or related rights of Emulex. All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations. 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 manual, Emulex disclaims any undertaking to give notice of such changes. From the main Emulex Web site, click Support. Each adapter, driver, firmware and boot code has documentation posted to the Web site. From the main Emulex Web site, click Support, then click knowledgebase. In addition to the Emulex Web site, the README.http://www.geoexcel.com/fckuploads/daewoo-fridge-manual.xml

txt file included in the distribution kit contains information describing what is included, how to install it, how to get started, a change history and any known issues. Check with your account vendor for the current supported version since it may vary from the Emulex current version. If necessary, load and update firmware using the Emulex Offline utility; (see the Offline Utility Manual for Emulex Utilities). From the main Emulex Web site, click Support, then click the link for your operating system (OS). The driver kit includes the lpfc base driver and the HBAnyware utility. Links to the Solaris’ SFS FCA drivers are provided as well. The driver kit download includes the base driver and the lputil utility. The downloads include the base driver only (no utilities). Click Support to go to the Support page, then click the link for your adapter model. A page appears with downloads for firmware, boot code, drivers and utilities. Download the firmware, and then use the HBAnyware utility to update the firmware on the adapter. You must ensure that the correct driver version is loaded for the device to function properly. You must load the Intel driver separately from the other software drivers and packages. See the Intel Web site for Intel drivers. This testing ensures that each supported configuration performs as indicated and operates successfully in an enterprise installation. Storage and system providers’ web sites are the best sources for this information. Because these parameters can significantly change the behavior of the Emulex product, great care must be taken in the setting or changing of the parameters. Storage and system providers put forth great effort in determining what particular configuration parameters must be set to in order to provide optimal storage area SAN performance. Doing so can alter performance of the SAN and place the SAN in a configuration that is not supported, or cause it to operate improperly. The device driver acts upon these parameters.

Emulex configuration parameters are NOT stored in the adapter flash memory. Unlike other SCSI and Fibre Channel (FC) adapters, Emulex does not store any configuration information such as timers, FC topology or link speed in the adapter flash. When an Emulex adapter is installed into a server, there is no separate configuration step required for the adapter. Proper driver configuration is generally all that is required. The exception to this is if you boot from SAN. In this case, you must use the adapter BIOS utility to configure the boot device. The adapter must be told which FC device contains the boot volume, and that information is stored in the flash. These settings are only in effect at boot time. Once the operating system (OS) loads the device driver, most settings of the driver are used and the adapter BIOS no longer functions. These utilities are: Ask the following questions. For example, a commonly overlooked SAN change is a switch firmware upgrade. Even something as seemingly innocuous as an upgrade to disk drive firmware in a RAID storage system can have unexpected effects on a SAN. For example, a planned storage fail-over during system maintenance takes eight minutes to occur, but was expected to complete in two minutes. Observe behavior on two levels. For example, users experienced an outage of eight minutes. For example, the storage controller is reporting an error. For example, is a manually initiated path fail-over of two minutes supported by the storage and path management software providers. A storage provider can only support two-minute failovers when their internal Redundant Array of Independent Disks (RAID) controller cache is disabled. If yes, can it be repeated on a non-production test system. Collecting information such as system error logs is often needed.

Since production systems are not generally set up to collect this information in normal operation, it is important to be able to configure the system to collect data and recreate the problem on a non-production test system. Check the adapter and switch LEDs to determine the status. If the LEDs stop flashing or flash an error code, this indicates the adapter may need to be returned to Emulex for repair. See “LED Reference Information” on page 18. This manual does not contain the procedures themselves. It serves as a guide to the publication that contains the procedures you need. Prerequisites ? Local boot disk. ? The intended Fibre Channel target should be big enough to hold all system files and the swap slice of the current local boot disk. Things to Know Before You Download. Before you download the OneConnect or LightPulse files, create a directory for them. ? As a measure of protection, ensure that critical files on your local boot disk are backed up. ? Firmware may be bundled with boot code. Boot code allows you to designate a device that is attached to the adapter as a boot drive. If you select a firmware image that includes boot code, the update procedure will load both the new firmware and the boot code at the same time. After updating, refer to the Emulex Boot Manual for procedures on enabling the boot code on your adapter. ? Emulex firmware files support both OneConnect and LightPulse adapters. ? For OneConnect adapters. Firmware and boot code are provided in a single flash image called a.UFI file. ? The UFI file contains all of the files that support all OneConnect adapters. The latest files for your adapter are installed automatically when you use an Emulex utility to update the firmware. ? The UFI file contains both firmware and boot code. ? For LightPulse adapters. Firmware is provided in a.ZIP file as a.ALL file or a.AWC file. You must manually unzip the.ALL or.AWC file from the.ZIP file before you can use an Emulex utility to install it. ?

Firmware differs between adapter models. Make sure you download the appropriate firmware for your adapter. ? The.ZIP file may or may not include a boot code (.PRG) file. Company Emulex Categories Networks Cards Model Emulex LP11002-M4 Description Firmware Operating Systems Firmware Version Firmware 2.10a7 Size Firmware 332Kb File Name bf210a7.zip Information Fibre Channel Host Bus Adapters for Fujitsu Primequest Servers Group Compatibility: This kit supports the LP11002 PCI host adapter. Discover everything Scribd has to offer, including books and audiobooks from major publishers. Start Free Trial Cancel anytime. Report this Document Download Now Save Save Emulex Solaris User Manual For Later 0 ratings 0% found this document useful (0 votes) 259 views 68 pages Emulex Solaris User Manual Uploaded by J. Jonas Janson Description: para emulex hba Full description Save Save Emulex Solaris User Manual For Later 0% 0% found this document useful, Mark this document as useful 0% 0% found this document not useful, Mark this document as not useful Embed Share Print Download Now Jump to Page You are on page 1 of 68 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language. Learn more Today, it is a modern IT system largely delivered as a service. Now updated for Version 2009 (Build 13231.20262), released on Sep. 28, 2020. Now, a new app wants to build on those efforts by identifying communities (often down to the Zip Code) that are being aggressive or lenient in. Here’s what you need to know. UI and auto-fill fresheners Do those claims stack up? I’m still skeptical of Windows 10 version 2004, but it’s getting closer to stable. Give it another month. That could mean more security, or more headaches for users. Sign up for our free newsletters. Data Protection Features End-to-end data protection with hardware parity, CRC, ECC and other advanced error checking and correcting algorithms ensure data is safe from corruption.

T10-PI provides additional protection against corruption in Oracle Unbreakable Linux environments. Deployment and Management Features Universal boot capability, allows the appropriate boot environment to be automatically selected for any given hardware. Boot from SAN capability reduces system management costs and increases uptime. Detailed, real-time event logging and tracing enables quick diagnosis of SAN problems. Beaconing feature flashes the HBA LEDs, simplifying their identification within server racks. Environmental monitoring feature helps optimize SAN availability. Management Features The Emulex AutoPilot Installer automates the HBA installation process and significantly reduces time to deployment and administrative costs. Automated installation and configuration of driver and management tools simplifies deployment of multiple adapters within Windows environments. A single installation of driver and management application, eliminates multiple reboots and ensures that each component is installed correctly and the HBA is ready to use. Powerful automation capabilities facilitate remote driver parameter, firmware and boot code upgrades. Advanced diagnostic features, such as adapter port beaconing and adapter statistics, help optimize management and network performance, while the environmental monitoring feature helps to maintain optimum host-to-fabric connections. In addition to the GUI interface, management functions can also be performed via a scriptable Command Line Interface (CLI) as well as a web browser. Within-band and out-of-band management capabilities, Emulex provides data center administrators with the greatest level of management flexibility. Emulex’s management instrumentation complies to Open Management Standards, such as SMI-S and common HBA API support, which enables seamless upward integration into enterprise storage and server management solutions. User Manual All rights reserved worldwide.

No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of 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 or related rights of Emulex. All other brands or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations. Emulex may make improvements and changes to the product described in this manual at any time and without any notice. Periodic changes are made to information contained herein; although these changes will be incorporated into new editions of this manual, Emulex disclaims any undertaking to give notice of such changes. This manual also describes the Emulex boot from SAN implementation and its operation with distinct hardware and operating system requirements. Boot from SAN is booting servers directly from disk operating system images located on a storage area network (SAN) by way of Emulex LightPulse adapters using Emulex FC boot code. When booting from SAN, the storage device is typically identified by its World Wide Port Name (WWPN) and a logical unit number (LUN). When properly configured, the adapter then permanently directs the server to boot from a logical unit (disk) on the SAN as if it were a local disk. Notes Emulex drivers support multi-path boot configurations. Refer to your storage vendor s documentation for details on how to configure multi-path booting. Screenshots in this manual are for illustrative purposes only. Your system information can vary. Emulex Boot Code Files Emulex is unique in providing Universal Boot and Pair Boot images of boot code. Universal Boot images contain x86 BootBIOS, OpenBoot, and EFIBoot boot code.

Pair Boot boot code images contain x86 BootBIOS and EFIBoot boot code. These images provide multi-platform support for boot from SAN. Universal Boot and Pair Boot transparently determine your system platform type and automatically execute the proper boot code image in the adapter. These boot code images reside in the adapter s flash memory, allowing for easier adapter portability and configuration between servers. Emulex provides the following types of boot code: x86 BootBIOS works with the existing system BIOS on x64 and x86 systems. OpenBoot works with the existing system firmware on SPARC systems. OpenBoot is also called FCode. UEFIBoot provides system boot capability through the use of the Unified Extensible Firmware Interface (UEFI) shell. It also functions on UEFI 2.x-based x64 platforms through the Human Interface Infrastructure (HII) interface. When booting from SAN, the storage device is typically identified by its WWPN and a LUN. By extending the server system BIOS, boot from SAN capability is provided by the boot BIOS contained on an Emulex adapter in the server. If properly configured, the adapter then permanently directs the server to boot from a logical unit (disk) on the SAN as if it were a local disk. Note: Not all procedures are required. Emulex HBAs usually ship from the factory with the latest version of boot code installed and enabled, so you do not need to install or enable boot code in those cases. However, if boot code is not installed, you must install it, and if it is not enabled, you must enable it. Check the Emulex website at for the latest version of boot code. This section describes setting up a system to boot from SAN. The specific procedure to follow is determined by the system architecture and the operating system. Table 2-1 Boot from SAN Procedures Architecture Operating System Procedure x86 and x64 Windows Server Installing Windows Server on an FC Boot Disk on page 16.

Linux Configuring Boot from SAN on Linux or VMware (x86 VMware and x64) on page 17. Solaris (SFS driver) Configuring Boot from SAN on Solaris (SPARC) on page 18. SPARC and PowerPC Linux Configuring Boot from SAN on Linux or VMware (UEFI) on page 17. Solaris (SFS driver) Configuring Boot from SAN on Solaris (x86 and x64) on page 17. 14 2. Booting from SAN Windows Server 14 Windows Server This section describes configuring boot from SAN for Windows systems and installing Windows Server on an FC boot disk. Configuring Boot from SAN on Windows Server (x64) To configure boot from SAN: 1. If necessary, update the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 2. If necessary, enable the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 3. Enable the adapter to boot from SAN (see Enabling an Adapter to Boot from SAN on page 27). 4. By default, the boot adapter uses auto topology with loop first. You can set the boot adapter to use a different topology (see Changing Topology on page 34). 5. Configure boot devices (see Configuring Boot Devices on page 27). 6. If desired, configure the boot options on the adapter (see Configuring Adapter Parameters on page 31). 7. Install the operating system on an FC boot disk (see Installing Windows Server on an FC Boot Disk on page 16). Follow the on-screen prompts to install the appropriate version of Windows Server. The Windows installation exposes all available and visible LUNs as disks and partitions numbered 0 to N, where N is the highest number available. These numbers typically are the LUN numbers assigned by the array. 5. Select the disk on which you want to install the operating system. 6. Follow the system prompts in the Windows installation. Note: The operating system image is installed with the GPT disk partition. See The GUID Partition Table on page 15 for a brief description of GPT disk partitions. 15 2.

Booting from SAN Windows Server 15 After the installation is complete, a Boot Option variable called Windows Boot Manager is populated with a Media Device path pointing to the Windows boot loader utility. The Windows Boot Manager can be found in the Start Options menu of the host server UEFI. The Windows Boot Manager option is inserted as the first boot option in the boot order list of the Host Server UEFI. Upon reboot, the system boots from the LUN set up on the SAN. Directing a UEFI-based Server to a Windows Server Operating System Image (Installed as UEFI-Aware) Already Installed on the SAN This installation procedure assumes a LUN exists in the SAN storage device, is zoned appropriately to the host adapter s WWN, and a UEFI-aware operating system resides on the target LUN. The Start Options list now reflects the boot order changes. Upon reboot, the server is able to boot from this target LUN on the SAN. The GUID Partition Table The GPT provides a more flexible mechanism for partitioning disks than the older MBR partitioning scheme that has been common to PCs. MBR supports four primary partitions per hard drive and a maximum partition size of 2 TB. If the disk is larger than two TB (the maximum partition size in a legacy MBR), the size of this partition is marked as 2 TB and the rest of the disk is ignored. The GPT disk itself can support a volume up to 2 64 blocks in length (for 512-byte blocks, this is 9.44 ZB). The GPT disk can also theoretically support unlimited partitions. 16 2. Booting from SAN Linux,Citrix, and VMware 16 Note: By default, Microsoft Windows Server operating systems install with a GPT-formatted disk on a UEFI-aware server. For more information on the GUID partition table, see the Microsoft website and search for the terms Windows and GPT FAQ. Installing Windows Server on an FC Boot Disk This procedure installs Windows Server onto an unformatted FC disk drive and configures the system to boot from the SAN disk drive.

Note: The computer s system BIOS may require that another controller take precedence over the Emulex adapter during boot. If this occurs, you must disconnect or disable the other adapter. This allows you to configure and build the operating system on the drive connected to the Emulex adapter. To install Windows Server on a boot disk: 1. Install the Emulex driver for Windows as described in the Emulex Drivers Version for Windows User Manual. 2. In Windows Explorer, navigate to the folder you specified during driver installation. 3. In the \AutoPilot Installer\Drivers\drivername folder, open the folder that corresponds to your computer type, such as x64.The Install Windows splash screen is displayed. 6. Verify and if necessary change the Language, Time and Date, and Keyboard values. Click Next. Another splash screen is displayed. 7. Click Install Now. The Where do you want to install Windows.Once selected, the correct driver location and driver are displayed under the Select driver to be installed screen. 9. Select Next. After the driver is loaded, the Where do you want to install Windows.Linux,Citrix, and VMware This section describes configuring boot from SAN on Linux, Citrix, and VMware operating systems. 17 2. Booting from SAN Solaris 17 Configuring Boot from SAN on Linux or VMware (x86 and x64) To configure boot from SAN: 1. If necessary, install or update the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 2. If necessary, enable the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 3. Enable the adapter to boot from SAN (see Enabling an Adapter to Boot from SAN on page 27). 4. By default, the boot adapter uses auto topology with loop first. If you want to set the boot adapter to use a different topology, change it (see Changing Topology on page 34). 5. Configure boot devices (see Configuring Boot Devices on page 27). 6.

If desired, configure the boot options on the adapter (see Configuring Adapter Parameters on page 31). 7. Use the driver on the operating system distribution disk to boot the system. If necessary, you can then update the driver to the desired version. Configuring Boot from SAN on Linux or VMware (UEFI) Solaris To configure boot from SAN: 1. If necessary, update the latest boot code on the adapter (see Updating and Enabling Boot Code on page 24). 2. If necessary, enable the boot code on the adapter (see Updating and Enabling Boot Code on page 24) 3. Configure boot devices. See Enabling an Adapter to Boot from SAN on page 27 for more information. 4. If desired, configure the boot options on the adapter. See Configuring Adapter Parameters on page 31 for more information. 5. Use the driver on the operating system distribution disk to boot the system. If necessary, you can update the driver to the latest version. This section explains how to configure boot from SAN on the Solaris operating system. Configuring Boot from SAN on Solaris (x86 and x64) To configure boot from SAN: 1. If necessary, update the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 2. If necessary, enable the boot code on the adapter (see Updating and Enabling Boot Code on page 24). 18 2. Booting from SAN Solaris Enable the adapter to boot from SAN (see Enabling an Adapter to Boot from SAN on page 27). 4. By default, the boot adapter uses auto topology with loop first. You can set the boot adapter to use a different topology (see Changing Topology on page 34). 5. Configure boot devices (see Configuring Boot Devices on page 27). 6. If desired, configure the boot options on the adapter (see Configuring Adapter Parameters on page 31). 7. Boot the Solaris installation CD and follow the prompts. Note: If you need help determining the LUNs to select for boot from SAN, Determining LUNs to Select for Boot from SAN on page 18.

Determining LUNs to Select for Boot from SAN To determine which LUNs to select: 1. Open a terminal window and leave it open. 2. In the terminal window, select the LUN you are going to use as the SAN boot disk (not the local drive) using the luxadm probe command. This shows all the available LUNs. Record this LUN information, which is used throughout this procedure. Installing Solaris from a Network Image The system must have a DVD drive and must be part of the site's network and naming service. If you do not use a naming service, you must distribute information about this system by following your site's policies. Note: This procedure assumes that the system is running the Volume Manager. To determine available disk space, use the df -kl command. 6. Decide whether you need to make the install server available for mounting: If the install server is on the same subnet as the system to be installed or you are using DHCP, you do not need to create a boot server. Patching a file may be necessary if a boot 21 2. Booting from SAN Solaris 21 image has problems. For more information, see the Solaris operating system documentation.Note: Emulex recommends using the WWPN in most cases. Create temporary mount points for the new partitions: mkdir root2 mkdir usr2 mkdir export2 13. For example, if the FC boot disk is c1t1d0, replace all local disk entries of c0t0d0 with c1t1d0. Reboot the system: sync sync halt reset-all 18. Boot to disk: boot disk The system should boot to the FC disk. 19. View the current dump device setting: dumpadm 20. The utility that you use depends on the operating system and, in some cases, the driver type or system architecture. Table 3-1 indicates the utilities you can use to install and update boot code.

Table 3-1 Utilities that Update and Enable Boot Code CIM Provider Operating System OneCommand Manager GUI OneCommand Manager CLI UEFI Utility (VMware only; see the CIM Provider Package Installation Guide) FCA emlxadm Offline Utilities Windows Linux Solaris VMware After you decide which utility to use, see the appropriate procedure: OneCommand Manager GUI: See the OneCommand Manager User Manual. OneCommand Manager CLI: See the OneCommand Manager Command Line Interface User Manual. UEFI utility: See Configuring Boot via UEFI HII (Human Interface Infrastructure) in a UEFI 2.1 System on page 50. FCA emlxadm utility: See the FCA Utilities User Manual. Offline utility: See the Offline and Online Adapter Management Utilities User Manual. 25 4. Emulex BIOS Utility Navigating the FCoE BIOS Utility Emulex BIOS Utility Before using the Emulex BIOS utility, ensure that the boot code is loaded and enabled on the adapter as described in Updating and Enabling Boot Code on page 24. Notes This section reflects the most recent release of the BIOS utility. Some selections may not be available if you are using an older version of the utility. Changes made to parameters common to UEFI and x86 drivers are changed in both driver configuration utilities. Navigating the FCoE BIOS Utility Use the following methods to navigate the BIOS utility. Press the up and down arrows on your keyboard to move through and select menu options or configuration fields. Press to scroll to the previous page. Press to scroll to the next page. Press to select a menu option, to select a changed value, to select a row in a screen, or to change a configuration default. Press to go back to the previous menu. Starting the Emulex BIOS Utility To start the Emulex BIOS Utility: 1. Turn on the computer and press and hold down or and press immediately (within five seconds) when the Emulex bootup message to enter the BIOS utility is displayed. An adapter listing screen is displayed (Figure 4-1 on page 26).http://eastwestrubbertrading.com/images/bryant-ac-service-manual.pdf