Multi-Boot Image for Qxx8xxx Converged Network Adapters

QLogic Corporation. All rights reserved.

Table of Contents

1. Package Contents

2. 10Gb BIOS

2.1 BIOS Package Contents

2.2 Supported Features

2.3 Adapter Configuration (Fast!UTIL)

2.4 Updating the BIOS (FlasUtil)

2.5 Additional Notes

3. 10Gb EFI

3.1 EFI Package Contents

3.2 Supported Features

3.3 Adapter Configuration

3.4 Updating the UEFI (EfiUtilx64)

3.5 Additional Notes

4. 10Gb FCode

4.1 FCode Package Contents

4.2 Supported Features

4.3 Adapter Configuration

4.4 Additional Notes

5. 10Gb PXE

5.1 PXE Package Contents

5.2 Supported Features

5.3 System Configuration

5.4 Updating the PXE (FlasUtil)

5.5 Additional Notes

6. 10Gb FCode

6.1 FCode Package Contents

6.2 Supported Features

6.3 Adapter Configuration

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 1 of 26

6.4 Updating the NIC UEFI (EfiUtilx64)

6.5 Additional Notes

7. Contacting Support

1. Package Contents

The multi-boot package for QLogic 8xxx adapters is a compressed file that contains the Qxx8xxx BIOS, UEFI, PXE, FCode, and firmware. This package also includes the FlasUtil and the VPD applications.

● The multi-boot BIOS contained in this package supports 8xxx adapters on Intel x86/x64 and AMD64 platforms.

● The UEFI Fibre Channel driver contained in this package supports 8xxx adapters on Intel x64 and IA64 platforms.

● The FCode contained in this package supports 8xxx adapters on SPARC platforms.

● Readme.txt is the readme file for the multi-boot package. This readme file contains details for

the multi-boot image, including the BIOS, UEFI code, and FCode contained in the package.

● Release.txt is the release notes for the multi-boot package. This file contains revision notes

for the multi-boot image, including the BIOS, PXE, UEFI code, and FCode contained in the package.

2. 10Gb BIOS

This section provides user notes regarding the BIOS contained in the 10Gb multi-boot package. It includes the following topics:

● 2.1 BIOS Package Contents

● 2.2 Supported Features

● 2.3 Adapter Configuration

● 2.4 Updating the BIOS

● 2.5 Additional Notes

2.1 BIOS Package Contents

The following tables describes the BIOS files included for updating the Adapter BIOS.

Filename Description

Update.bat DOS batch file that calls the executable files to update the adapter BIOS.

FlasUtil.exe Utility to update multi-boot code and firmware.

VPD.exe Utility to update the adapter's vital product data (VPD).

x8xyyyyy.bin Combined binary file, which includes the binaries for the firmware, PXE, FCode, UEFI, and BIOS.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 2 of 26

2.2 Supported Features

● Up to 2031 target IDs

● Up to 256 logical unit numbers (LUNs)

● Point-to-point configuration

● Boot capability in fabric topologies

● Compatible with DOS, Windows Server 2003, Windows Server 2008, Solaris x86, and Linux on IA32, AMD64, and Intel 64-based systems

2.3 Adapter Configuration (Fast!UTIL)

This section describes the adapter parameters.

NOTE: The Fast!UTIL BIOS utility does not run on Sun SPARC systems.

This section provides detailed configuration information for advanced users who want to customize the configuration of the 10Gb adapter and the connected devices. You can configure the adapter using Fast!UTIL.

To access Fast!UTIL, press <ALT>+<Q> or <CTRL>+<Q> during the adapter BIOS initialization (it may take a few seconds for the Fast!UTIL menu to appear). If you have more than one adapter, Fast!UTIL asks you to select the adapter you want to configure. After changing the settings, Fast!UTIL reboots your system to load the new parameters.

CAUTION! If the configuration settings are incorrect, your adapter may not function properly.

The Fast!UTIL Options menu provides the following options:

● Configuration Settings (section 2.3.1)

● Scan Fibre Devices (section 2.3.2)

● Fibre Disk Utility (section 2.3.3)

● Loopback Data Test (section 2.3.4)

● Select Host Adapter (section 2.3.5)

● Exit Fast!UTIL (section 2.3.6)

2.3.1 Configuration Settings

Select this option to access the following configuration settings for the 10Gb adapter:

● Adapter Settings (section 2.3.1.1)

● Selectable Boot Settings (section 2.3.1.2)

● Restore Default Settings (section 2.3.1.3)

● Raw NVRAM Data (section 2.3.1.4)

● Advanced Adapter Settings (section 2.3.1.5)

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 3 of 26

2.3.1.1 Adapter Settings

Setting Values Default Description

Host Adapter BIOS Enabled/Disabled Disabled Disabling this setting disables the ROM BIOS on the adapter, which frees space in upper memory. You must enable this setting if you are booting from an FC disk drive attached to the adapter. See section 3.1.2 for details on specifying the boot device.

Frame Size 512/1024/2048 2048 This setting specifies the maximum frame length supported by the adapter.

Loop Reset Delay 0 - 60 seconds 5 seconds After resetting the loop, the firmware refrains from initiating any loop activity for the number of seconds specified in this setting.

Spin Up Delay Enabled/Disabled Disabled When this bit is set, the BIOS waits up to two minutes to find the first drive.

Fibre Channel Tape Support Enabled/Disabled Enabled This setting enables FCP-2 recovery.

2.3.1.2 Selectable Boot Settings

The Selectable Boot Settings option is accessed from the Configuration Settings menu. If you enable the Host Adapter BIOS in the Adapter Settings, this option allows you to select the boot device as shown in the following table.

Selectable Boot Settings

Enable Selectable Boot Boot WWPN/LUN Device Boot

No x BIOS configures the first disk drive it finds as boot device.

Yes None specified BIOS configures the first disk drive it finds that is also a LUN 0 as boot device.

Yes Specified BIOS scans through the specified Boot WWPN/LUN list until it finds a disk drive. This is configured as boot device.

This option allows you to specify up to four WWPN/LUN as boot devices.

To enable the Selectable Boot option and insert devices into the boot device locations:

1. From the Configuration Settings menu, select Host Adapter Settings.

2. Enable the adapter BIOS, then press ESC to return to the Configuration Settings menu.

3. From the Configuration Settings menu, select Selectable Boot Settings.

4. Press ENTER to enable or disable (toggle) the Selectable Boot option. Use the down arrow key to move to the Primary location of the Selectable Boot List menu.

5. Press ENTER to see a list of accessible devices (in the Select Fibre Channel Device menu).

6. Select a drive using the arrow keys to scroll down to the device you want to put into your Selectable Boot menu list, then press ENTER to select the requested device and load it into the Selectable Boot menu list.

7. Repeat this step to specify a secondary boot device on the QLE256x FC Adapter or up to three alternate boot devices.

NOTES:

● System BIOS Compatibility: In a computer system with a multi-boot system BIOS (CMOS), in order to boot from a QLogic adapter, the adapter must be included in the list of bootable devices in the system's Boot menu.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 4 of 26

● Solaris X86 Boot from a SAN: To boot from an FC drive connected to a QLogic adapter, reboot the system and enter Fast!UTIL. Prior to performing the OS (Solaris X86) installation, enter into the Selectable Boot menu, enable selectable boot, and then insert the BOOT drive in the Primary location of the Selectable Boot menu.

2.3.1.3 Restore Default Settings

Select the Restore Defaults option from the Configuration Settings menu to revert the BIOS settings to the defaults.

2.3.1.4 Raw NVRAM Data

Select the Raw NVRAM Data option to display the adapter’s NVRAM contents in hexadecimal format. This is a QLogic troubleshooting tool; you cannot modify the RAW NVRAM data.

2.3.1.5 Advanced Adapter Settings

Select the Advanced Adapter Settings option to modify the default settings for the 10Gb adapter.

Advanced Adapter Settings

Setting Values Default Description

Execution Throttle 1-65535 16 This setting specifies the maximum number of commands executing on any one target port. After reaching a target port’s execution throttle, it stops issuing new commands until one of the current commands finishes executing.

LUNs per Target 0/8/16/32/64/128/256 128 This setting specifies the number of LUNs supported per target if the target does not support "Report LUN" command. Multiple LUN support typically applies to a redundant array of independent disks (RAID) boxes that use LUNs to map drives.

Enable Target Reset Yes/No Yes This setting enables the drivers to issue a Target Reset command to all devices on the loop when a SCSI Bus Reset command is issued.

Login Retry Count 0 - 255 8 This setting specifies the number of times the software tries to log in to a device.

Port Down Retry Count 0 - 255 seconds 30 seconds This setting specifies the number of seconds the software waits to retry a command to a port returning port down status.

Link Down Timeout 0 - 255 seconds 30 seconds This setting specifies the number of seconds the software waits for a link down to come up.

Operation Mode 0/5/6 0 This setting specifies the reduced interrupt operation (RIO) modes, if supported by the software driver. The RIO modes allow posting multiple command completions in a single interrupt. This option supports the following modes: 0 - Interrupt for every I/O completion 5 - Interrupt when Interrupt Delay Timer expires 6 - Interrupt when Interrupt Delay Timer expires or no active I/Os

Interrupt Delay Timer 0 - 255 seconds 0 This setting contains the value (in 200-microsecond increments) that a timer uses to set the wait time between generating an interrupt.

Enable Interrupt Yes/No No Setting this option to YES enables the BIOS to use the IRQ assigned to the ISP24xx. When set to NO the BIOS will poll for ISP mailbox command completion status.

Primary FCF VLAN ID Enabled/Disabled Disabled This setting enables the primary VLAN ID to be used.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 5 of 26

2.3.2 Scan Fibre Devices

This option scans the FC loop and lists all the connected devices by loop ID. Select the Scan Fibre Devices option to scan the FC devices and list all the connected devices. It lists information about each device (for example, vendor name, product name, and revision). This information helps when configuring your adapter and attached devices.

2.3.3 Fibre Disk Utility

Select the Fibre Disk Utility option to scan the Fibre Channel loop and list all the connected devices by loop ID. You can select a Fibre Channel hard disk and run one of the following tests:

● Perform a low-level format.

● Verify the disk media.

● Verify the disk data.

● Select a disk device.

CAUTION! Performing a low-level format destroys all data on the disk.

2.3.4 Loopback Data Test

Select the Loopback Data Test option to perform an external loopback test.

NOTE: When running the external loopback data test, make sure that the loopback connector is attached to the adapter port(s) before starting the test. Do not run this test with the adapter connected to the fabric switch port.

2.3.5 Select Host Adapter

If you have a multi-port or multiple 8xxx adapters in your system, select the Select Host Adapter option, and then configure or view the settings of a specific adapter port or adapter.

2.3.6 Exit Fast!UTIL

Select the Exit Fast!UTIL option to exit the utility and reboot the system or return to Fast!UTIL. After making changes to the QLogic adapter in Fast!UTIL, make sure you save the changes before you reboot the system.

2.4 Updating the BIOS (FlasUtil)

The QLogic Flash programming utility (FlasUtil) is a DOS utility. To run this utility, boot to a DOS hard drive or USB removable drive.

NOTE: Do not run this utility from drive connected to the 8xxx adapters.

Make sure Flasutil.exe and the x8xyyyyy.bin source files are in the same directory.

2.4.1 Flashing the BIOS

To flash the BIOS:

1. Install the Qxx8xxx adapter in the system.

2. Boot to DOS.

3. At the command prompt, run the update script as follows: C:\>update.bat

This script program updates the BIOS image on the adapter.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 6 of 26

4. Reboot the system.

NOTE: You can also use the SANsurfer GUI or CLI to flash the multi-boot image.

2.4.2 FlasUtil Command Line Options

The executable file, Flasutil.exe, is used by the UPDATE.BAT file to update your adapter BIOS. You

can use the FlasUtil application to read, write, or verify the multi-boot image or the NVRAM on the adapter.

CAUTION! FlasUtil will modify the way your adapter operates. Use it with extreme caution.

NOTE: Specific features (for example, the NVRAM options) may require additional data files and passwords not provided in this file.

The following table describes the command line options available with this utility.

Enter FlasUtil to list QLogic adapters at different I/O addresses. Enter the adapter I/O address to view menu options:

Flasutil /? for command line details.

Option Function

/L xxxx Writes NOVRAM to adapter address xxxx. Using this option without an address writes the NOVRAM to all adapters.

/F xxxx Writes BIOS code to the adapter at I/O address = xxxx. Using this option without an address writes BIOS code to all adapters. If the adapter already contains a valid BIOS, this option preserves the existing NVRAM contents.

/FR xxxxWrites firmware (reduced instruction set computer [RISC] code) to the adapter at address = xxxx. Using this option without an address writes firmware to all adapters.

/D xxxx Copies NVRAM to a file (QLxxNVR.SAV), adapter address = xxxx.

/W xxxxCopies the image of the BIOS from the adapter at address xxxx into a file (for example, QLxxROM.SAV).

/WB xxxx

Copies the 1MB complete boot image from the adapter at address xxxx to a file (for example, QLxxROM.SAV).

Note: This option is not supported on converged network adapters.

/N <filename.dat> Use <filename.dat> instead of Qxxxxxx.DAT.

/O <filename.ext> Use <filename.ext> instead of x8xyyyyy.bin.

/I Ignore Subsystem ID.

/Q Quiet Mode; no messages will be displayed.

/S xxxxDisplays serial number of adapter at address xxxx. Using this option without an address will display the serial numbers of all adapters.

/V xxxxDisplays the current version of the BIOS on adapters at address xxxx. Using this option without an address displays the BIOS version of all adapters.

/C xxxx

Verifies the image of the BIOS on the adapter at address xxxx. Using this option without an address verifies the BIOS images of all adapters.

Note: This option is not supported on converged network adapters.

/X xxxxVerifies the NVRAM of the adapter at address xxxx. Using this option without an address verifies the NVRAM OF all adapters.

/Y xxxx Displays the port name of the adapter at address xxxx. Using this option without an address displays the port name of all adapters.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 7 of 26

For example, for adapters with previously valid Flash and NVRAM contents, use the following command line options:

● To update the Flash on a QLogic adapter: c:\>flasutil /f /o x8xyyyyy.bin

● To update the pre-boot execution environment (PXE) on a QLogic adapter: c:/>flasutil /fp /o Qxxxxxx.bin

● To update the firmware code (only) on a QLogic adapter: c:\>flasutil /fr /o qxxxx.bin (Firmware File)

2.5 Additional Notes

If you used an FC RAID target in a Cluster Environment, you should enable the Enable Target Reset = Enabled (Advanced Adapter Settings).

● Use /I option if the update utility, FlasUtil, does not detect your Fibre Channel adapter.

● From the Flasutil application menu, the only option for dumping/copying is /W, which does the

following: (1) Save/dump a 256 KB image of the file (2) Save/dump the Flash in a file called QLxxROM.SAV

● The /D option dumping/copying the NVRAM saves the NVRAM in a file (QLxxNVR.SAV).

● Some FlasUtil options may require the use of an external file name instead of the default file. For example: C:\Flasutil /C /O x8xyyyyy.bin C:\Flasutil /D /N Qxx8xxx.DAT

NOTE: The preceding option is not supported on converged network adapters.

3. 10Gb EFI

This section provides user notes regarding the Unified Extensible Firmware Interface (UEFI) driver contained in the 10Gb multi-boot image. It includes the following topics:

● 3.1 EFI Package Contents

● 3.2 Supported Features

● 3.3 Adapter Configuration

● 3.4 Utilities

● 3.5 Additional Notes

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 8 of 26

3.1 EFI Package Contents

The following tables describes the files included in the EFI software package.

Filename Description

x8xyyyyy.bin Combined binary file, which includes the binaries for BIOS, FCode, UEFI driver, and RISC firmware.

EfiUtil.EFI or EfiUtilx64.EFI UEFI Utility to update the UEFI driver, firmware, and NVRAM.

QL8XXX.DRV Auxiliary driver file used for updating the adapter.

UPDATE.NSH UEFI script file used to update the adapter on a UEFI system.

IPFCHECK.EFI CPU detection tool used by UPDATE.NSH.

EFICFG.PDF Adapter Configuration and Diagnostic PDF.

EFIUTIL.PDF Adapter EfiUtil Utility PDF.

NOTE: All bin, uefi, and nsh files are required to update the adapter on a UEFI system.

3.2 Supported Features

The UEFI driver supports the following features:

● UEFI Specification 1.10, 2.1

● UEFI protocols: Extended SCSI Pass Thru, Block IO, SCSI IO, Driver Diagnostics, Driver Configuration, Component Name

● 382 targets

● 2047 LUNs per target

● Fabric topology

● Boot from SAN

● Compatible with Red Hat x64 5.3, SLES x64 11, and Windows Server 2008 x64 on UEFI Intel x64 based systems.

3.3 Adapter Configuration

To configure the adapter parameters, refer to the EFICFG.PDF file.

3.4 Updating the UEFI (EfiUtilx64)

For systems that do not include a built-in UEFI Shell, please obtain the UEFI Shell program from the open source site; for example: https://www.tianocore.org/

The EfiUtilx64 is a QLogic Flash programming utility for UEFI. To run the utility, boot to the UEFI shell. Do not run this utility from the drive connected to 8xxx adapters.

Make sure update.nsh, efiutilx64.efi, ql8xxx.drv, and x8xyyzzz.bin source files are in the

same directory.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 9 of 26

3.4.1 Flashing the UEFI

To update the UEFI driver and RISC firmware on all adapters:

1. Unzip and copy the update kit files to the root level of a USB storage device. NOTE: Do not change or rearrange the kit directories or files that were unzipped and copied to the USB storage device.

2. Connect the USB device to the UEFI-based system with the 8xxx adapters.

3. At the system's UEFI shell prompt, use the map -r command to map the USB device file

system. You can check the mapping as follows: map -b

4. Locate the USB device and change to that device. For example, if the USB device is mapped to fs9 after the map -r:

fs9: <ENTER>

The UEFI shell prompt should change as follows: fs9:\>

5. Run the update.nsh script to update the UEFI driver and RISC firmware. For example: fs9:> update.nsh

Update.nsh will call efiutilx64.efi to update all of the adapters.

6. Reboot the system to ensure that the driver and firmware changes take effect.

To update NVRAM or perform other manual EfiUtilx64 flash functions, refer the information in the file, efiutil.pdf.

3.4.2. EfiUtilx64 Options

Use EfiUtilx64 to write, read, or verify the multi-boot image on the adapter.

NOTE: To perform other manual EfiUtilx64 flash functions, refer to efiutil.pdf.

3.5 Additional Notes

None

4. 10Gb FCode

This section provides user notes regarding the FCode contained in the 10Gb multi-boot image. It includes the following topics:

● 4.1 FCode Package Contents

● 4.2 Supported Features

● 4.3 Adapter Configuration

● 4.4 Additional Notes

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 10 of 26

4.1 FCode Package Contents

The following table describes the files included for the FCode software package.

Filename Description

x8xyyzzz.bin Combined binary file, which includes the binaries for the firmware, FCode, UEFI, and BIOS.

4.2 Supported Features

The FCode supports the following features:

● 2048 target ID support

● 16384 LUN/target support for qlc mode

● Converged network adapter support

● Compatible with Sun Solaris 10 SPARC-based systems

NOTE: Issue reset-all when any change is made to the FCode or Fiber link/target.

4.3 Adapter Configuration

This section describes the FC adapter configuration for the FCode that comes packaged in the 10Gb multi-boot image, including:

● Selecting QLogic FCoE Adapter Port at OBP (section 4.3.1)

● Setting and Viewing NVRAM Parameters (section 4.3.2)

● Setting and Viewing FCode Operation Mode (section 4.3.3)

● Setting and Viewing Login-Retry-Count (section 4.3.4)

● Setting and Viewing Link-Down-Timeout (section 4.3.5)

● Setting and Viewing Port-Down-Retry-Count (section 4.3.6)

● Setting and Viewing Max-Frame-Size (section 4.3.7)

● Setting and Viewing Boot-Wait-Time (section 4.3.8)

● Restoring NVRAM Parameter Defaults (section 4.3.9)

4.3.1 Selecting QLogic FCoE Adapter Port at OBP

Prior to setting Fibre Channel adapter NVRAM parameters or executing Diag commands, you must

select the device using either the select-dev or select methods, as shown in the following

examples.

Example 1:

{0} ok " /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1" select-dev

^-- must have leading space.

or

{0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 11 of 26

If you are in a windows environment, you can cut and paste the adapter's device path into the select or select-dev command. To view a list of all devices in the system, enter the show-devs

command.

Another way to show a list of adapter devices attached to the system is to use the show-disks

command, as shown in Example 2.

Example 2:

{0} ok show-disks

a) /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk

b) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1,1/fp@0,0/disk (SUN Adapter Port 1)

c) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk (SUN Adapter Port 0)

d) /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom

e) /pci@7c0/pci@0/pci@1/pci@0/ide@8/disk

f) NO SELECTION

Enter Selection, q to quit: f

/pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk has been selected.

Type ^Y ( Control-Y ) to insert it in the command line.

For example, {0} ok nvalias mydev ^Y

for creating devalias mydev for /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk

{0} ok " /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1" select-dev

^-- enter ^Y here ^-- use backspace to remove fp...

When the adapter device is selected the first time, a banner similar to the following should appear: QLogic Qxx8xxx Host Adapter FCode(SPARC): X Y Firmware version Z

Where: X = FCode Version

Y = Date of FCode version release

Z = Firmware Version

4.3.2 Setting and Viewing NVRAM Parameters

To list all NVRAM and diagnostic commands, enter show-commands at ok prompt. For example:

{0} ok show-commands

NVRAM Parameter commands

show-settings

set-login-count

set-link-timeout

set-port-down-count

set-max-frame-size

set-boot-wait-time

restore-default-settings

Diag Commands

version

selftest

ext-loopback-test

show-children

disk-test

sel-dev

sel-lun

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 12 of 26

See readme.txt for details

To show the current value of all of the NVRAM parameters, as well as the version, serial number, and adapter WWN, enter show-settings. For example:

{0} ok show-settings

QLogic QLE8142 Host Adapter FCode(SPARC): X Y

Firmware version z

MPI FW version vv.vv.vv

Serial# 11S42C1831YK5122P3POUT

node-wwn 20000021 5e4c406d

port-wwn 21000021 5e4c406d

Enode MAC Address: 0 21 5e 4c 40 6d

Current FCF VLAN-ID: Not Valid

Current Adapter MAC Address Mode: FPMA only

Current FW login-retry-count: 8(8)

Current link-down-timeout: 1e(30) seconds

Current port-down-retry-count: 1e(30)

Current max-frame-size: 800(2048)

Current boot-wait-time: DISABLED

Where: X = FCode Version

Y = Date of FCode version release

Z = Firmware version

XXXx = Model number

vv.vv.vv=MPI firmware version

4.3.3 Setting and Viewing FCode Operation Mode

FCode supports two FCode operation modes, qla and qlc (the default is qlc), with the following restriction:

● qla mode requires a driver named qla2300.

● qlc mode requires a driver named qlc.

● qla mode is not supported on Sun (SUNW) branded converged network adapters.

WARNING: Use extreme caution when changing the FCode mode, because changing it may cause Solaris to create new device paths for this adapter, which may affect driver instance numbers and mount points in Solaris.

Example:

{0} ok set-fc-mode

Current Fcode Mode: qlc

Do you want to change it? (y/n) y

Choose Fcode Mode:

0 - qlc

1 - qla

enter: 0

Current Fcode Mode: qlc

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 13 of 26

4.3.4 Setting and Viewing Login-Retry-Count

The login-retry-count NVRAM parameter is used by the FCode to determine the number of login

retries attempted to the boot device. The default value is 8. Use the set-login-count command to

change this parameter. For example:

{0} ok set-login-count

Current login-retry-count: 8(8)

Do you want to change it? (y/n) y

login-retry-count: Enter 1-ff hex: 7

Current login-retry-count: 7(7)

4.3.5 Setting and Viewing Link-Down-Timeout

The link-down-timeout NVRAM parameter is used by the FCode to determine the number of

seconds to wait for the link to come up. The default value is 30. Use the set-link-timeout

command to change this parameter. For example:

{0} ok set-link-timeout

Current link-down-timeout: 1e(30) seconds

Do you want to change it? (y/n) y

link-down-timeout: in Secs. Enter 2-ff hex: 14

Current link-down-timeout: 14(20) seconds

4.3.6 Setting and Viewing Port-Down-Retry-Count

The port-down-retry-count NVRAM parameter is used by the FCode to determine the number of

retries for the start, read, and write SCSI commands. The default value is 30. Use the set-port-

down-count command to change this parameter. For example:

{0} ok set-port-down-count

Current port-down-retry-count: 1e(30)

Do you want to change it? (y/n) y

port-down-retry-count: Enter 1-ff hex: 10

Current port-down-retry-count: 10(16)

4.3.7 Setting and Viewing Max-Frame-Size

The max-frame-size NVRAM parameter is used by the FCode to set the maximum frame length field

in the Firmware Initialization Control Block. The default value is 2048. Use the set-max-frame-size

command to change this parameter. For example:

{0} ok set-max-frame-size

Current max-frame-size: 800(2048)

Do you want to change it? (y/n) y

Choose max-frame-size:

1 - 512

2 - 1024

3 - 2048

enter: 2

Current max-frame-size: 400(1024)

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 14 of 26

4.3.8 Setting and Viewing Boot-Wait-Time

The boot-wait-time NVRAM parameter is used by the FCode to adjust the time to wait in seconds

for the boot device to become online. The default value is DISABLED, which sets it to 8 seconds. The

maximum value is 65,535 seconds (18 hours, 6 minutes). The minimum value is 8 seconds, the same as when disabled. Because this wait time can be very long, the boot process may be aborted at any time by pressing the <ESC> key. Use the set-boot-wait-time command to change this

parameter.

Example 1:

{0} ok set-boot-wait-time

Current boot-wait-time: DISABLED

Do you want to change it? (y/n) y

boot-wait-time: Enter 8-ffff hex: 168

Current boot-wait-time: 168(360) seconds (this example sets it

to 6 minutes)

Example 2:

{0} ok set-boot-wait-time

Current boot-wait-time: 168(360) seconds

Do you want to change it? (y/n) y

Do you want to Disable it? (y/n) y

Current boot-wait-time: DISABLED (this example disables the

parameter)

4.3.9 Restoring NVRAM Parameter Defaults

Use the restore-default-settings command to restore the default values of all NVRAM

parameters used by the FCode. For example:

{0} ok restore-default-settings

Reset all NVRAM values back to defaults. Are you sure? (y/n) y

NVRAM defaults restored

Current Fcode Mode: qlc

Current login-retry-count: 8(8)

Current link-down-timeout: 1e(30) seconds

Current port-down-retry-count: 1e(30)

Current max-frame-size: 800(2048)

Current Boot-WWPN: 0000000000000000, Boot-LUN: 0(0), Boot-Target-ID: 0(0)

{0} ok

4.4 Additional Notes

Additional notes include the following:

● Limitations (section 4.4.1)

● Diagnostic Commands (section 4.4.2)

● Building a Bootable Disk (section 4.4.3)

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 15 of 26

4.4.1 Limitations

You must issue a reset-all after modifying the FCode or Fibre link or target.

4.4.2 Diagnostic Commands

Diagnostic commands include the following:

● Version Command (section 4.4.2.1)

● Beacon Support (section 4.4.2.2)

● selftest (section 4.4.2.3)

● Show-children (section 4.4.2.4)

● Disk-test (section 4.4.2.5)

4.4.2.1 Version Command

To display the current FCode and Firmware version, enter version. For example:

{0} ok version

QLogic Qxx8xxx Host Adapter FCode(SPARC): X Y

Firmware version Z

{0} ok

Where X = FCode Version

Y = Date of FCode version release

Z = Firmware version

4.4.2.2 Beacon Support

Beacon is a feature to allow a specific host adapter to be visually located easily. When the feature is activated, the yellow and amber LEDs on the back of the adapter will flash at approximately one-second intervals.

To enable the Beacon feature:

1. Select the host adapter device you want to locate as described in section 4.3.1.

2. Enter beacon.

The following message is displayed: Flashing adapter LEDs, type any character to quit - The yellow and amber LEDs

on the selected host adapter will flash until any character is entered on the

keyboard.

NOTE: For multi-channel host adapters, only one channel's LED will flash.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 16 of 26

4.4.2.3 Selftest

Selftest is the name of the method that is executed when the test <node path> command is

entered at the ok prompt. For example: {0} ok test /pci@1c,600000/SUNW,qlc@1

An alternative way to test the adapter device is to first select the device you want to test as described in section 4.3.1., and then enter selftest. For example:

{0} ok selftest

nvram ok

FCode Checksum OK

Testing memory, pattern 0 - PASS

Testing memory, pattern ffffffff - Passed

Testing memory, pattern 55aa5555 - Passed

Testing memory, pattern aaaa55aa - Passed

Testing memory, pattern a55aa55a - Passed

Testing memory, pattern 5b5a5a6a - Passed

Testing memory, pattern ff00f0f0 - Passed

Testing memory, pattern 1ff00f0e - Passed

10-bit Internal Loopback Test - Passed

1-bit Internal Loopback Test - Passed

External Internal Loopback Test - Passed

{0} ok

4.4.2.4 Show-children Command

Show-children is the name of the method that is called when probe-scsi-all is executed. The

probe-scsi-all command will show all of the SCSI target/LUNs attached to the system by

executing the show-children method of all devices with the device-type property set to scsi or

scsi-fcp. To show the targets and LUNs of a single adapter, select the adapter device as described

in section 4.3.1, and then enter set-mode. For example:

{0} ok show-children

Adapter portID - 10800

************** Fabric Attached Devices **************

Dev# 0(0) PortID 10b9b Port WWN 216000c0fff02f95

LUN 0(0) SUN StorEdge 3510 421D

Dev# 1(1) PortID 10ba9 Port WWN 216000c0ff702f95

LUN 0(0) DISK SUN StorEdge 3510 421D

LUN 1(1) DISK SUN StorEdge 3510 421D

LUN 2(2) DISK SUN StorEdge 3510 421D

{0} ok

4.4.2.5 Disk-test command

The disk-test was added as a diagnostic tool to allow you to perform a simple, non-destructive,

read/write data test to a selected target.

To execute disk-test:

1. Select the adapter device as described in section 4.3.1.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 17 of 26

2. Execute show-children and then pick a target (Dev#) and LUN from the listed devices.

3. Log in to the target by typing <dev#> sel-dev. For example:

7 sel-dev (will login to Dev# 7)

4. Select a LUN by typing <lun#> sel-lun. For example:

4d sel-lun (will select LUN 4d, hex)

NOTE: You may skip this step if the LUN # = 0, the default.

5. Execute disk-test by typing disk-test. The disk-test will perform a read-write-read-

compare test to the selected target, 64 blocks (32k bytes) at a time. While it is running, it will display the current disk block address. To terminate the test, press any key.

You can also use the disk-test command to locate a specific target, if there is an activity LED on

the target.

4.4.3 Building a Bootable Disk

This procedure assumes the system is already booted from an existing system disk, and that you have already performed a full system backup. The device name shown in this example is for a device on the third PCI bus slot, target ID 130, LUN 0, and slice 0. The device path is different on each system, depending on the PCI bus slot, target ID, LUN, and so on.

You must have already completed the steps listed in the preceding before attempting to create a bootable disk.

This procedure involves using the Solaris command, ufsdump, to create temporary saveset files for each partition on your current boot disk. For this method to be successful, you must have either enough extra disk space to create the saveset files, or your Solaris machine must have a high-capacity tape drive attached.

To build a rebootable disk:

1. Determine the amount of disk space used on your current boot disk. Use the /usr/bin/df -k

-l command for a listing. For example:

# /usr/bin/df -k -l

Filesystem kbytes used avail capacity Mounted on

/dev/dsk/c0t0d0s0 2577118 1650245 875331 66% /

/proc 0 0 0 0% /proc

fd 0 0 0 0% /dev/fd

mnttab 0 0 0 0% /etc/mnttab

swap 1310480 0 1310480 0% /var/run

swap 1311344 864 1310480 1% /tmp

/dev/dsk/c0t0d0s7 5135326 114 5083859 1% /home

This df example shows that the current boot disk is /dev/dsk/c0t0d0s(x). There are two partitions of interest: slice 0 or "/" and slice 7 or "/home". Slice 0 is using 1.6GB and has 875MB free. Slice 7 uses 114KB and has 5GB free. Therefore, Slice 7 or "/home" can be used to store the temporary saveset files. If at least 1.7GB free is not available on this disk, a partition will have to be created on the new bootable disk large enough to hold the largest temporary saveset, plus the largest used space on a partition. In this example, that would be a partition at least 3.2GB(1.6GB+1.6GB).

2. Use the format command to create, label and format partitions on the new bootable disk.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 18 of 26

These partitions must be able to contain the contents of the temporary savesets. If you are not familiar with the format command, carefully read the Solaris documentation and manual

pages for the command. Misuse of format could destroy the data on the current disk drives.

For example:

# format

partition

print

Current partition table (original):

Total disk cylinders available: 3880 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks

0 root wm 0 - 2650 2.73GB (2651/0/0) 5726160

1 swap wu 2651 - 2930 295.31MB (280/0/0) 604800

2 backup wm 0 - 3879 4.00GB (3880/0/0) 8380800

3 unassigned wm 0 0 (0/0/0) 0

4 unassigned wm 0 0 (0/0/0) 0

5 unassigned wm 0 0 (0/0/0) 0

6 unassigned wm 0 0 (0/0/0) 0

7 home wm 2931 - 3879 1000.90MB (949/0/0) 2049840

label

quit

quit

3. Use the newfs command to create the file system. For example:

In case of qlc FCode (fc) mode # newfs -v /dev/rdsk/c5t216000c0ffe02f95d0s0 (/)

# newfs -v /dev/rdsk/c5t216000c0ffe02f95d0s7 (home)

NOTE: The target device ID (t130) is in decimal! The hexadecimal value for the target ID is used in the boot command line shown in step 12.

4. Mount the boot partition to the /mnt mount point. For example:

In case of qlc FCode(fc) mode # mount /dev/dsk/c5t216000c0ffe02f95d0s0 /mnt

5. CD to the root partition mount point. For example: # cd /mnt

6. Use the ufsdump utility to copy the root partition to the new boot disk. For example:

(Same in both qla and qlc operation mode) # ufsdump 0f - / | ufsrestore rf -

7. Execute the following command: # rm restoresymtable

8. Install the boot block on the new boot disk. For example: In case of qlc FCode(fc) mode # installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/

c5t216000c0ffe02f95d0s0

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 19 of 26

9. Edit the new vfstab file to properly mount the new partition(s) during boot. In this case, each reference to c0t0d0s0 would be changed to c5t216000c0ffe02f95d0s0 (qlc mode). For

example: # vi /mnt/etc/vfstab

NOTE: Replace every instance of c0t0d0 with c5t216000c0ffe02f95d0 (in case of qlc

operation mode) in the /mnt/etc/vfstab file.

10. Edit the /mnt/kernel/drv/sd.conf file to add the boot target ID and LUN. For example: name="sd" class="scsi" target=16 lun=6;

11. Shut down the system. For example: # /sbin/init 0

12. Boot from the newly-created boot disk. For example, for qlc FCode(fc) mode: {0} ok boot /pci@1f,700000/SUNW,qlc@3,1/fp@0,0/disk@w216000c0ff898d16,a (Port 1,

Lun No. 10) (In case of RAID)

13. View the current dump device setting as follows: # dumpadm

Dump content: kernel pages

Dump device: /dev/dsk/c0t0d0s1 (swap)

Savecore directory: /var/crash/saturn

Savecore enabled: yes

14. Change the dump device to the swap area of the new boot drive. For example, in case of qlc FCode(fc) mode: # dumpadm -d /dev/dsk/c5t216000c0ffe02f95d0s1

NOTE: The following two steps set the newly-created boot disk to be the default boot disk. These steps are performed at the system OBP (ok) prompt.

15. Create an alias entry for the new boot device (optional). For example, in OBP at the ok

prompt: {0} ok nvalias fibredisk /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ffe02f95

16. Set the default boot device to be the new boot device (optional). For example: {0} ok setenv boot-device fibredisk

NOTE: You can also build a SANboot disk from CD/DVD or boot server as follows:

# ok boot cdrom or

# ok boot net

...Select FC Target for OS install. qlc driver will be installed.

Refer to the Solaris installation manual for detail procedures.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 20 of 26

5. 10Gb PXE

This section provides user notes regarding the pre-boot execution environment (PXE) contained in the 10Gb multi-boot package. It includes the following topics:

● 5.1 PXE Package Contents

● 5.2 Supported Features

● 5.3 Adapter Configuration

● 5.4 Updating the BIOS

● 5.5 Additional Notes

5.1 PXE Package Contents

The following table describes the files included for updating the adapter PXE under the BIOS environment.

Filename Description

x8xyyyyy.bin Combined binary file, which includes the binaries for the firmware, PXE, FCode, UEFI, and BIOS.

readme.txt Text file version of readme file.

release.txt PXE (BIOS) release notes.

update.bat DOS batch file that calls the executable files to update the adapter PXE in the BIOS environment.

FlasUtil.exe Utility to update multi-boot code and firmware.

VPD.exe Utility to update the adapter's Vital Product Data.

5.2 Supported Features

● PXE for the CNA Qxx8yyy adapter under the BIOS environment.

● Compatible with Windows Server 2003, Windows Server 2008, and Linux on IA32, AMD64, and Intel 64-based systems.

5.3 System Configuration

This section provides user notes regarding the BIOS PXE feature contained in the 10Gb multi-boot package.

PXE boot code is already included in the boot code image, x8xyyyyy.bin.

For flashing the BIOS PXE code, refer to the BIOS Readme.txt file.

● QLogic Banner During POST When the server powers on, a Qlogic PXE banner similiar to following appears: QLogic PCI 3.O PXE V1.0x (two banners per adapter; see notes) Copyright (c)

2009 QLogic Corporation

NOTE: PCI 3.0 compliant server: QLogic PCI 3.0 PXE v1.0x is displayed. PCI 2.1 compliant Server: Only QLogic PXE v1.0x is displayed.

● Enable QLogic PXE Check the Server's setting below: Enter Server BIOS settings Select Start Options

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 21 of 26

Enable PXE on Non-Planar Ethernet QLogic PXE Bootprom will automatically detect the Boot Server and start the OS installation. Linux Boot Server: boot: (ENTER to continue) NOTE: To install OS to Server's internal disk QLogic FCoE NIC driver is required. To install OS to Server's SAN disk, both QLogic FCoE NIC and FC driver are required.

● NT Boot Server ... Downloaded WDSNNBD.. Architecture: x64

Contacting Server: xx.xx.xx.xx

TFTP Download: Boot\x64\preboot.com

Press F12 for Network Service Boot.

NOTE: QLogic NIC and FC driver should be installed in the NT PXE Boot Server.

● Errors The following error may occur, if QLogic PXE detects that the link is down: PXE NICStartUp: Link is down The following error may occur, if QLogic PXE did not detect a Boot Server: QLogic UNI vx.xx PXE-x.x (Build xxxx)

Copyright (c) 2009 QLogic Corporation

Client MAC Addr: xx xx xx xx xx xx GUID ....

PXE-E51: No DHCP or Proxy DHCP offers were recieved.

PXE-M0F: Exit QLogic PXE ROM.

...

....

5.4 Updating the PXE (FlasUtil)

The QLogic Flash programming utility is a DOS utility. To run this utility, boot to a DOS hard drive or USB removable drive.

NOTE: Do not run this utility from a drive connected to the 8xxx adapters. Make sure Flasutil.exe

and the x8xyyyyy.bin source files are in the same directory.

To flash the BIOS:

1. Insert the 8xxx adapter in the system.

2. Boot to DOS.

3. Run the update script at the command prompt: C:\>update.bat

This script program updates the BIOS image on the adapter.

4. Reboot the system.

NOTE: You can also use SANsurfer GUI/CLI to flash the multi-boot image, which contains the PXE.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 22 of 26

5.5 Additional Notes

IMPORTANT: When installing an operating system from the PXE Server, ensure that the selected operating system supports the converged network adapter relative to the BIOS or the UEFI environment. Also, ensure that the converged network adapter supporting NIC and Fibre Channel drivers are loaded on the PXE Server.

BIOS Known Issue: If the server reports PCI Resource Allocation Error. This error may be due to the server's Option ROM not being available. If this issue occurs, disable the on-board PXE similar to the setting below:

Enter Server BIOS settings Select Start Options Disable Planar Ethernet pXE/DHCP

6. 10Gb NIC UEFI

This section provides user notes regarding the NIC UEFI contained in the 10Gb multi-boot package. It includes the following topics:

● 6.1 NIC Package Contents

● 6.2 Supported Features

● 6.3 Adapter Configuration

● 6.4 Updating the BIOS

● 6.5 Additional Notes

6.1 NIC Package Contents

The following table describes the files included for updating the adapter NIC UEFI under the UEFI environment.

Filename Description

x8xyyyyy.bin Combined binary file, which includes the binaries for the firmware, PXE, FCode, UEFI, and BIOS.

readme.txt Text file version of readme file.

release.txt Separate PXE (BIOS) and EFI PXE (EFI) release notes.

EfiUtil.EFI or EfiUtilx64.EFI UEFI utility to update the adapter PXE in the UEFI environment.

QL8XXX.DRV Auxiliary driver file used for updating the adapter.

UPDATE.NSH UEFI script file used to update the adapter on a UEFI system.

IPFCHECK.EFI CPU detection tool used by UPDATE.NSH.

EFICFG.PDF Adapter Configuration and Diagnostic PDF.

EFIUTIL.PDF Adapter EfiUtil Utility PDF.

NOTE: All bin, uefi, and nsh files are required to update the adapter on a UEFI system.

6.2 Supported Features

● PXE for the converged network adapter Qxx8xxx under the UEFI environment.

● Compatible with Red Hat x64 5.3, SLES x64 11, and Windows Server 2008 x64 on UEFI Intel x64-based systems.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 23 of 26

6.3 Adapter Configuration

This section provides user notes regarding the UEFI PXE feature contained in the 10Gb multi-boot package.

PXE Boot Code is already included in the Boot Code image, x8xyyyyy.bin.

For flashing the UEFI PXE code, refer to the EFI Readme.txt file.

To set up PXE (example):

1. Boot the UEFI capable server and press <F12> to access the System Configuration and Boot Management Menu.

2. To select and add the boot option, find the MAC address entry for the converged network adapter to add to the boot option menu, and then press <ENTER>.

3. Type in a name and press <ENTER> for the new PXE boot entry. For example: MYPXEBOOT

4. To commit the changes, press <ENTER>.

5. To return to the System Configuration and Boot Management Menu, press <ESC> twice.

6. To select and change the boot order, find the newly-created MYPXEBOOT by pressing the <+> key to move the entry up to the top of the boot list.

7. To commit the changes, press <ENTER>. The next optional step will help create an EFISHELL boot list entry. This step can help save

time if your entry is not correct, because it will boot to the EFI shell as a stopping point.

8. Ensure that you have a DOS bootable USB thumb drive, ensure that you download the EFI Shell file from the IBM Web site, and then copy the file onto the USB drive. Finally, connect the USB drive to the server.

9. To select and add the boot option, find the DOS...USB drive entry to add to the boot option

menu, and then and press <ENTER>.

10. Find the shell.efi entry in the USB drive directory and press then press <ENTER>.

11. Type in a name for the EFI Shell boot entry, and then press <ENTER>. For example: MYEFISHELL

12. To commit the changes, press <ENTER>.

13. To go back to System Configuration and Boot Management Menu, press <ESC> twice.

14. To check the new boot list entries, select Start Options and then review the order of the boot list entries, where the new MYPXEBOOT is at the top of the list and the MYEFISHELL is the second entry from the top.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 24 of 26

To start the PXE Boot:

1. When everything is set up, press <ESC> until you see a message asking for confirmation, and then press <Y>. This will start the process for the boot order list. When the PXE starts, you should see the ELILO boot prompt.

2. Press <ENTER> to start the installation, and then follow the Operating system options.

NOTE: If you see a message that the PXE process failed, check your system setup entries and try again.

6.4 Updating the NIC UEFI (EfiUtilx64)

For systems that do not include a built-in UEFI Shell, obtain the UEFI Shell program from the open source site: https://www.tianocore.org/

The EfiUtilx64 is a QLogic Flash programming utility for UEFI. To run the utility, boot to the UEFI shell. Do not run this utility from the drive connected to the 8xxx adapters.

Make sure update.nsh, efiutilx64.efi, ql8xxx.drv and x8xyyzzz.bin source files are in the same directory.

To update the UEFI Driver and RISC Firmware on all adapters:

1. Unzip and copy the update kit files to the root level of a USB storage device. NOTE: Do not change or rearrange the kit directories or files that were unzipped and copied to the USB storage device.

2. Connect the USB device to the UEFI based system with the 8xxx adapter(s).

3. At the system's UEFI shell prompt, use the map -r command to map the USB device file

system. You can check the mapping as follows: map -b

4. Locate the USB device and change to that device. For example, if the USB device is mapped to fs9 after the map -r:

fs9: <enter>

The UEFI shell prompt should change as follows: fs9:\>

5. Run the update.nsh script to update the UEFI driver and RISC firmware. For example: fs9:> update.nsh

Update.nsh will call efiutilx64.efi to update all of the adapters.

6. Reboot the system to make the Driver/Firmware changes take effect.

To update NVRAM or perform other manual EfiUtilx64 flash functions, refer to the efiutil.pdf.

6.5 Additional Notes

IMPORTANT: When installing an operating system from the PXE Server, ensure the selected operating system supports the converged network adapter relative to the BIOS or the UEFI environment. Also, ensure that the converged network adapter supporting NIC and Fibre Channel drivers are loaded on the PXE Server.

UEFI PXE Known Issue: The initial attempt to connect to the PXE server from the client server may fail. You may need to retry the PXE process several times before establishing a successful PXE connection.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 25 of 26

7. Contacting Support

Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods:

Web: http://support.qlogic.com

Email: support@qlogic.com

Go to Top

© Copyright 2009. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic

Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.

Multi-Boot Image for Qxx8xxx Converged Network Adapters Readme File 26 of 26