Combined Boot
Version 5.01a0
for Emulex HBAs
User Manual
Known Issues.................................................................................................... 1
Change Topology ............................................................................................ 11
The .prg File Fails During Downloading........................................................... 19
Making a Bootable System Disk...................................................................... 23
Viewing OpenBoot Commands........................................................................ 26
Troubleshooting OpenBoot.................................................................................... 27
Combined Boot User Manual
Page iii
Introduction
Combined Boot contains two types of boot code: x86 BootBIOS for x86 systems, and OpenBoot for
SPARC Peripheral Component Interconnect (PCI) and AIX systems. Combined Boot determines your
system platform (x86 or SPARC) and automatically downloads the proper boot code image to the host
bus adapter (HBA).
x86 BootBIOS works with the existing basic input output system (BIOS) on x86 systems. x86 BootBIOS
allows you to designate a Fibre Channel drive as the boot drive.
OpenBoot is a set of FCode instructions in the HBA flash read-only memory (ROM) that allows you to
designate a Fibre Channel hard drive as the boot drive. OpenBoot works with the existing system BIOS
on SPARC PCI systems.
Compatibility
®
•
Combined Boot is compatible with the following Emulex Fibre Channel PCI HBAs:
•
•
LP9402DC, LP9002DC, LP9002L and LP9000 (minimum firmware version 3.82a1)
LP8000 and LP8000DC (minimum firmware version 2.81)
Things to Know Before You Download
•
Combined Boot is a complete single boot image. Therefore, the HBA utility software enables or
disables two types of boot code (x86 BootBIOS and OpenBoot).
•
•
•
This download assumes that there is already a local boot disk.
As a measure of protection, ensure that critical files on your local boot disk are backed up.
The .PRG files included in this release contain only the boot code overlay (no firmware).
Known Issues
The following issue has been reported at the time of publication.
•
None at this time.
Files Included in This Release
This kit includes the following files:
File Name
readme.txt
cc501a0.prg
dc501a0.prg
Description
Release notes for Combined Boot version 5.01a0
LP9402DC, LP9002DC, LP9002L and LP9000 Combined Boot image
LP8000 and LP8000DC Combined Boot image
Combined Boot User Manual
Page 1
Loading x86 BootBIOS
Before you update x86 BootBIOS, decide which utility to use. Emulex offers a variety of utilities that you
can use to update x86 BootBIOS. The utilities that you can use depend on your operating system and, in
some cases, driver:
Operating System
Windows
lputilnt*
elxcfg**
lputil
lp6dutil***
X
X
X
X
X
Linux
X
X
Solaris (x86 system)
* SCSIport Miniport and Storport Miniport drivers only
** FC Port driver only
*** Requires DOS (will not run in a DOS window)
After you decide which utility to use, see the appropriate update procedures:
•
•
•
•
Load x86 BootBIOS Using lputilnt
Prerequisites
•
One of the following drivers is installed and loaded properly:
•
SCSIport Miniport driver for Windows Server 2003, Windows 2000 Server or Windows
NT.
•
Storport Miniport driver for Windows Server 2003.
•
•
lputilnt is installed properly.
The x86 BootBIOS file has been downloaded from the Emulex Web site and extracted to a folder
on your local hard drive.
•
The system is in a state in which this type of maintenance can be performed:
•
•
I/O activity on the bus has been quieted.
Cluster software, or any other software that relies on the HBA to be available, has been
stopped or paused.
To load x86 BootBIOS using lputilnt:
1. Start lputilnt: Click Start, Programs, Emulex and lputilnt.
2. Select the desired HBA.
3. Select Firmware Maintenance from the Category list.
4. Click Download and locate the new x86 BootBIOS file.
5. Click Open. The new boot code is transferred to flash ROM.
Combined Boot User Manual
Page 2
Figure 1: lputilnt, Program Type list.
7. If the Disable button appears, the boot code is already enabled; skip to step 9. Otherwise,
continue with step 8.
8. Click Enable; the Enable button changes to Disable and the letter W appears to the left of "Boot
Bios Firmware" in the Program Type list. This indicates that x86 BootBIOS is in use.
Load x86 BootBIOS Using elxcfg
Prerequisites
•
•
•
The FC Port driver for Windows Server 2003, Windows 2000 Server or Windows NT is installed.
elxcfg is installed properly.
The x86 BootBIOS file has been downloaded from the Emulex Web site and extracted to a folder
on your local hard drive.
•
The system is in a state in which this type of maintenance can be performed:
•
•
I/O activity on the bus has been quieted.
Cluster software, or any other software that relies on the HBA to be available, has been
stopped or paused.
To load x86 BootBIOS using elxcfg:
1. Start elxcfg: Click Start, Programs, Emulex and elxcfg.
Figure 2: elxcfg Utility, Available Adapters List
3. Select Download Firmware from the Tools menu. A browse window is displayed.
4. Browse to the folder into which you extracted the x86 BootBIOS file and select the file.
5. Click Open. The file is downloaded, and a confirmation window is displayed.
6. Click OK to close the confirmation window.
Combined Boot User Manual
Page 3
Load x86 BootBIOS Using lputil
Prerequisites
•
•
The Emulex driver for Linux or Solaris is installed and loaded properly.
The x86 BootBIOS file has been downloaded from the Emulex Web site and extracted to a
directory on your local hard drive.
•
lputil is installed properly.
To load x86 BootBIOS using lputil:
1. Start lputil by entering the complete path. The path in the example reflects the default installation
path. If the installation path was modified, adjust the command appropriately.
/usr/sbin/lpfc/lputil
2. From the Main menu, enter 3, Firmware Maintenance.
3. From the list that appears, choose the HBA onto which you want to load x86 BootBIOS.
4. Enter 1, Load Firmware Image.
5. Enter the full path to the remote boot image file. The new boot code is transferred to flash ROM.
6. From the Firmware Maintenance menu, press 6, Boot BIOS Maintenance.
7. Press 1, Enable Boot BIOS, to enable the Boot message. (If item 1 is Disable Boot BIOS, the
BIOS message is already enabled.)
Loading x86 BootBIOS Using lp6dutil
Prerequisites
•
The x86 BootBIOS file has been downloaded from the Emulex Web site and extracted to a
directory on your local hard drive.
All lp6dutil tasks can be performed using the graphical user interface (GUI) screen menus. All screens
require navigation and selection using the keyboard.
Note: You cannot start lp6dutil at the screen’s command prompt.
To load x86 BootBIOS using lp6dutil:
1. Start lp6dutil:
a. Boot up your system with DOS.
b. From the directory where the lp6dutil.exe file resides, enter the following command:
lp6dutil
2. Press and hold down the < Alt> key and press L. The flash menu is displayed.
Figure 3: lp6dutil, Flash Menu
Combined Boot User Manual
Page 4
3. Press D. The Download Image window is displayed.
Figure 4: lp6dutil, Download Image Window
4. Specify the location of the image file and the adapter to be updated.
5. Specify the Reset After Download setting.
•
•
Defaults to Yes. If you are updating a single file to one HBA, keep the default setting.
If you are updating several HBAs or several files to one HBA, select No.
6. Tab to the OK button and press <Enter>. The screen closes and the load process begins.
Various steps of the download process are displayed along with the results of the download
(success or error).
8. Press B. The Change Boot BIOS State window is displayed. This window is used to change the
x86 BootBIOS state for an adapter.
Figure 5: lp6dutil, Change Boot BIOS State Window - Disabled BootBIOS Message
9. Highlight the HBA in the Adapters list.
10. Highlight the x86 BootBIOS image in the BIOS Images list.
11. Tab to Change and press <Enter>. The BootBIOS message is enabled for the selected HBA.
12. Tab to OK and press <Enter> to close the window.
Combined Boot User Manual
Page 5
Enable x86 BootBIOS on HBAs Using the BIOS Utility
To use any of its features, x86 BootBIOS must be enabled on at least one installed HBA.
Prerequisites
•
•
x86 BootBIOS is loaded on the HBA.
The BIOS message is enabled.
To enable BootBIOS on the HBA:
1. Boot the system.
2. Press <Alt E> immediately (within five seconds) when the x86 BootBIOS message is displayed
Figure 6: BIOS Utility, HBA Listing
3. Select the HBA by entering the appropriate number.
Figure 7: BIOS Utility, Main Configuration Menu
Combined Boot User Manual
Page 6
Figure 8: BIOS Utility, Adapter Configuration Menu
6. Press 1 to Enable or Disable BIOS.
7. Exit the BIOS utility and reboot the system. After x86 BootBIOS is enabled on the HBAs, refer to
the Configuration section for information on other adapter configuration menu options.
Combined Boot User Manual
Page 7
Configuring x86 BootBIOS
Introduction
The BIOS utility allows you to change HBA parameters (such as topology, PLOGI retry timer and auto scan
setting) and configure boot devices.
•
•
•
Default settings are acceptable for most installations.
In the BIOS utility, press <d> to reset the selected adapter to default values.
The default topology is auto topology with loop first. For FC-AL, each HBA has a default AL_PA
of 01 (Hex). Change this topology setting, if necessary, before configuring boot devices.
•
•
All HBAs or boot drives can be configured to other AL_PAs than their default values.
If more than one HBA is in the system with the same PCI bus number, and each has a boot drive
attached, the first PCI-scan HBA will be the boot HBA. The first HBA is usually in the lowest PCI
slot in the system. This information can be viewed from the BIOS utility.
Start the BIOS Utility
Prerequisites
•
x86 BootBIOS must be loaded and the bootup message enabled on at least one of the host bus
adapters in your system to run the BIOS Utility.
To start the BIOS utility to configure your adapters:
1. Turn on the computer.
2. Press <Alt E> immediately (within five seconds) when the x86 BootBIOS message displays to
start the BIOS Utility. An HBA listing is displayed.
3. Select the adapter to configure by entering the appropriate number.
Figure 9: BIOS Utility, HBA Listing
Combined Boot User Manual
Page 8
4. Select 1 to configure boot devices or 2 to configure the adapter’s parameters.
Figure 10: BIOS Utility, Main Configuration Menu
5. If you select to configure the adapter’s parameters, the adapter configuration menu is displayed.
Figure 11: Adapter Configuration Menu
Adapter Configuration Menu Summaries
1. Enable or Disable BIOS. Enable or disable x86 BootBIOS on the selected adapter. To use any
of its features, x86 BootBIOS must be enabled on at least one installed HBA. See Enable x86
2. Change Default ALPA of this adapter. This option applies only to arbitrated loop (FC-AL). The
information.
3. Change PLOGI Retry Timer(+ Advanced Option+). Set the interval for the port log in retry
page 11 for more information.
4. Topology Selection(+Advanced Option+). If it is necessary to change the topology, do so
5. Enable or Disable Spinup Delay(+ Advanced Option+). Enable or disable the spinup delay.
information.
Combined Boot User Manual
Page 9
6. Auto Scan Setting(+ Advanced Option+). Enable the first device in the boot entry list to issue
information.
7. Enable or Disable EDD 3.0(+ Advanced Option+). Enable or disable the Enhanced Disk
Driver (EDD) option, which is available on Itanium 64-bit servers only. The factory default is
8. Enable or Disable Start Unit Command(+ Advanced Option+). You must know the specific
LUN to issue the SCSI Start Unit Command. The factory default is disabled. See Enable/Disable
9. Enable or Disable Environment Variable(+ Advanced Option+). Enable or disable the ability
to set the boot controller order, if the system supports the environment variable. The factory
A. Auto Sector Format Select(+ For MSA10000 Array use Only+). This option automatically
defines the boot sector (32-sector or 63-sector) of the target disk. The factory default is enabled.
Change the Default AL_PA
This option allows you to change the AL_PA (Arbitrated Loop Physical Address) of the selected adapter.
The default value of the AL_PA for the adapter BIOS is 01 (hex).
Note: This option applies only to arbitrated loop (FC-AL).
To change the default AL_PA:
1. Start the BIOS utility and select the adapter.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 2, Change Default ALPA of this adapter.
Figure 12: Change Default ALPA Screen
4. Type the AL_PA, in hexidecimal notation, to which you want to change the default.
5. Press <x> to exit the BIOS utility and reboot the system.
Note: If the host adapter's AL_PA is changed, it will not show on the NVRAM AL_PA until
the system has been reset.
Combined Boot User Manual
Page 10
Change the PLOGI Retry Timer
This option allows you to set the interval for the PLOGI (port login) retry timer. This option is especially
useful for Tachyon-based RAID arrays. Under very rare occasions, a Tachyon-based RAID array will reset
itself and the port will go offline temporarily in the loop. When the port comes to life, the PLOGI retry
interval scans the loop to discover this device. This default setting is No PLOGI Retry: 0 msec.
To set the interval for the PLOGI retry timer:
1. Start the BIOS utility and select the adapter.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 3, Change PLOGI Retry Timer (+Advanced Option+).
Figure 13: Change the PLOGI Retry Timer Screen
4. Select the PLOGI retry timer interval. The time it takes for one PLOGI to scan the whole loop (if
126 AL_PA are on the loop) is shown below:
•
•
•
50 msec will take 5 to 6 seconds per device.
100 msec will take 12 seconds per device.
200 msec will take 22 seconds per device.
5. Press <x> to exit the BIOS utility and reboot the system.
Change Topology
This option allows you to select the topology for the host adapter.
Note: The default topology is auto topology with loop first. Change this topology
setting, if necessary, before configuring boot devices.
To select the host adapter topology:
1. Start the BIOS utility and select the adapter.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
Combined Boot User Manual
Page 11
3. Select 4, Topology Selection (+Advanced Option+).
Figure 14: Topology Menu
4. Select the topology for the HBA:
•
•
•
•
Select 1 for auto topology with loop first.
Select 2 for auto topology with point-to-point first.
Select 3 for FC-AL.
Select 4 for fabric point-to-point.
5. Press <x> to exit the BIOS utility and reboot the system.
Enable/Disable the Spinup Delay
This option allows you to enable or disable the spinup delay. The factory default setting is disabled.
If at least one boot device has been defined, and the spinup delay is enabled, the BIOS searches for the
first available boot device.
•
•
If a boot device is present, the BIOS boots from it immediately.
If a boot device is not ready, the BIOS waits for the spinup delay and, for up to three additional
minutes, continues the boot scanning algorithm to find another Multi-boot device.
If no boot devices have been defined, and auto scan is enabled, then the BIOS waits for five minutes
before scanning for devices.
•
•
In a private loop, it attempts to boot from the lowest target AL_PA it finds.
In an attached fabric, it attempts to boot from the first target found in the NameServer data.
To enable or disable the spinup delay, do the following:
1. Start the BIOS utility and select the adapter.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 5, Enable or Disable Spinup Delay (+Advanced Option+).
Figure 15: Enable or Disable Spinup Delay Screen
Combined Boot User Manual
Page 12
4. Select 1 to enable the spinup delay, or press 2 to disable it.
5. Press <x> to exit the BIOS utility and reboot the system.
Set Auto Scan
This option allows you to set auto scan. The factory default setting is disabled. Auto Scan is available
only if none of the eight boot entries is configured to boot via DID or WWPN. It is strongly recommended
that you use the Configure Boot Devices menu to configure eight boot entries for fabric point-to-point,
public loop or private loop configurations.
With auto scan enabled, the first device will issue a Name Server Inquiry. The boot device will be either
the first DID, LUN 0, or not LUN 0 device returned, depending on the option you select. Only this device
will be the boot device and it will be the only device exported to the Multi-boot menu.
To set auto scan:
1. Start the BIOS utility and select the adapter for which you want to set auto scan.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 6, Auto Scan Setting (+Advanced Option+).
Figure 16: Set Auto Scan Screen
4. Select the auto scan option:
•
•
Select 1 to disable auto scan.
Select 2 to scan for any first device. The first adapter issues a name server inquiry, and
the first D_ID from the inquiry becomes the boot device. The adapter attempts to log in
to a public loop first. If it fails, it logs in to a private loop. The first successfully scanned
device becomes the boot device. Only this device is exported to the Multi-boot menu.
•
•
Select 3 to scan for the first LUN 0 device.
Select 4 to scan for the first device that is not LUN 0.
5. Press <x> to exit the BIOS utility and reboot the system.
Combined Boot User Manual
Page 13
Enable/Disable EDD 3.0
This option allows you to enable or disable the Enhanced Disk Drive (EDD) option, which is available on
Intel Itanium servers only. Enabling EDD 3.0 displays the path to the boot device. The default setting is
disabled.
Note: An x86 system could hang during Windows 2000 Server installation if EDD
3.0 is enabled.
To enable or disable EDD 3.0:
1. Start the BIOS utility and select the adapter for which you want to enable or disable EDD 3.0.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 7, Enable or Disable EDD 3.0(+Advanced Option+).
Figure 17: Enable or Disable EDD 3.0 Screen
4. Select 1 to enable EDD 3.0, or press 2 to disable it.
5. Press <x> to exit the BIOS utility and reboot the system.
Enable/Disable the Start Unit Command
This command is used to issue the SCSI start unit command. You must know the specific LUN to issue
the SCSI start unit command.The default setting is disabled.
To enable or disable the start unit command:
1. Start the BIOS utility. Select the HBA for which you want to enable or disable the start unit
command.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 8, Enable or Disable Start Unit Command(+Advanced Option+).
Figure 18: Enable or Disable Start Unit Command Screen
4. Select 1 to enable the start unit command, or 2 to disable it.
5. Press <x> to exit the BIOS utility and reboot the system.
Combined Boot User Manual
Page 14
Enable/Disable the Environment Variable
This option allows you to set the boot controller order if the system supports the environment variable.
The default setting is disabled.
To enable or disable the environment variable:
1. Start the BIOS utility and select the adapter for which you want to enable or disable the
environment variable.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select 9, Enable or Disable Environment Variable(+Advanced Option+).
Figure 19: Enable or Disable Environment Variable Screen
4. Select 1 to enable the Environment Variable, or 2 to disable it.
5. Press <x> to exit the BIOS utility and reboot the system.
Enable/Disable Auto Sector Format Select
This option automatically defines the boot sector (32-sector or 63-sector) of the target disk. If there is no
partition on the target, the default boot sector format is 63 sectors. The default setting is enabled.
To enable or disable auto sector format select, do the following:
1. Start the BIOS utility and select the adapter for which you want to enable or disable the
command.
2. When the main menu opens select 2, Configure This Adapter's Parameters. The adapter
3. Select A, Enable or Disable Auto Sector Format Select(+For MSA1000 Array Use Only+).
Figure 20: Enable or Disable Auto Sector Format Select Screen
4. Select 1 to enable auto sector format select, or 2 to disable it.
5. Press <x> to exit the BIOS utility and reboot the system.
Combined Boot User Manual
Page 15
Configure Boot Devices
This option supports FC_AL: (public loop and private loop) and fabric point-to-point. When operating in
loop (FC_AL) topology, the system automatically determines whether you are configured for a public or
private loop. The BIOS looks for a fabric loop (FL_Port) first. If a fabric loop is not detected, the BIOS
looks for a private loop. For the "Configure Boot Devices" option, the 64 boot entries will be zero by
default (<d> key).
To configure boot devices:
1. Start the BIOS utility and select the adapter for which you want to configure boot devices.
2. When the Main menu opens select 1, Configure Boot Devices.
A list of 8 boot devices is shown. We recommend that only the bootable devices be configured.
The primary boot device is the first entry shown, and it is the first bootable device.
•
If the first boot entry fails due to a hardware error, the system can boot from the second
bootable entry.
•
If the second boot device fails, the system will boot from the third bootable entry and so
on.
Figure 21: List of Saved Boot Devices
3. Select a boot entry. The following screen opens:
Figure 22: Device Selection List
Note: We recommend that you select the drive with the lowest AL_PA as the boot device.
4. Select 00 to clear the selected boot entry, or select a device to configure booting via WWPN or
DID. If you select a device, you will be asked for the starting LUN.
Combined Boot User Manual
Page 16
5. Enter the starting LUN. The starting LUN can be any number between 0 and 255.
Figure 23: LUN Listing
There are a possible 256 LUNs that can be defined per adapter, but the screen displays up to 16
consecutive LUNs at a time. In front of each entry, B#D or B#W specifies the boot entry number
and whether the device boots via DID or WWPN. For example, B1D means that boot entry one
will boot via DID. B2W means that boot entry two will boot via WWPN.
6. Select an entry. Another menu displays the following options:
1. Boot this device via WWPN
2. Boot this device via DID
7. Select the desired boot method.
If you select to boot the device via WWPN, the WWPN of the earlier selected entry is saved in
the flash. However, during the initial BIOS scan, it will issue a Name Server Inquiry GID_PN (Get
Port Identifier). Then, based on this DID, it will continue with the remainder of the scanning.
If you select to boot this device via DID, the earlier selected entry will be saved in the flash.
Install Windows 2000 Server on a Fibre Channel Disk
This procedure installs the Windows 2000 Server operating system onto a previously unformatted Fibre
Channel disk drive that is connected to the Emulex adapter.
Note: Your 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 will allow you to configure and build your operating system on
the drive connected to the Emulex adapter.
To install Windows 2000 Server on a Fibre Channel disk:
1. From either the Emulex Web site or the CD-ROM that accompanies your Emulex product,
download the latest version of the Emulex driver for Windows 2000 Server.
2. Extract the driver files onto a formatted floppy disk.
3. Boot with the Windows 2000 Setup Media. (This procedure assumes you are using CD-ROM
medium. See Microsoft documentation for details.) The following message is displayed in the
status bar:
"Setup is detecting your hardware."
4. Press <F6>. The following message is displayed in the status bar:
"Specify additional storage driver"
Combined Boot User Manual
Page 17
5. Press <S> to specify additional drivers.
6. Select Other.
7. Insert the floppy disk onto which you unzipped the Emulex driver in step 2.
8. If you downloaded the port driver, select a topology from the list and press <Enter>.If you
downloaded the miniport driver, select your adapter from the list and press <Enter>.
9. Follow the instructions to complete the Emulex installation.
10. Remove the floppy disk that contains the driver files.
11. Complete the Windows 2000 Server installation.
Use Multi-Boot BIOS
Multi-boot BIOS is in compliance with BIOS Boot Specification (BBS). The system must have a Multi-boot
system BIOS in order to take advantage of this feature. Multi-boot BIOS allows you to select any boot disk
in the system BIOS setup menu. The boot disk can be a Fibre Channel drive, a SCSI drive, an IDE drive or
a floppy drive. The Emulex BIOS supplies the first eight drives to the system BIOS menu. The Multi-boot
BIOS can override the Fibre Channel drive that is selected in the BIOS utility.
For example, the system has only eight Fibre Channel disks. The boot disk has AL_PA 02. However, you
can select AL_PA 23 in the system BIOS setup menu. The boot device will be the Fibre Channel disk
with AL_PA 23 instead of AL_PA 02, as is set in the BIOS utility.
If your system supports Multi-boot BBS, the boot disk (drive C) is the first entry in Multi-boot on the
system BIOS setup menu. The list of entries is determined by the list of configured boot entries in the
BIOS utility. For example:
Adapter 1: boot_entry0, boot_entry1
Adapter 2: boot_entry2, boot_entry3
The order of boot entries that is exported to Multi-boot (BBS) is
boot_entry0, boot_entry1, boot_entry2, and boot_entry3.
However, Multi-boot can overwrite this order by using the following command:
boot_entry2, boot_entry0, boot_entry1, and boot_entry3.
In this case, drive C is
boot_entry2.
Combined Boot User Manual
Page 18
Troubleshooting x86 BootBIOS
There are circumstances in which your system may operate in an unexpected manner. This
Troubleshooting section explains several of these circumstances and offers one or more workarounds for
each situation.
The x86 BootBIOS Message Does Not Appear on Bootup
Situation: You want to access the x86 BootBIOS, but on bootup the x86 BootBIOS message does not
appear.
Resolution: Make sure that x86 BootBIOS has been loaded and enabled.
Retry This Adapter Message
Situation: The message "Retry This Adapter" appears during BIOS scanning.
Resolution: Check the hardware configuration or reconfigure the HBA BIOS using the BIOS utility.
The .prg File Fails During Downloading
Situation: The .prg file fails during downloading. The 1.70a1 version of the BIOS image is 48k, which
may cause the file to fail during downloading.
Resolution:
1. Download the firmware .awc file (without the BIOS image)
2. Download the BIOS image file.
Note: This problem may occur with LP9402DC, LP9002L, LP9002DC, LP9000,
LP952L, LP8000, LP8000DC or LP850 host bus adapters.
Combined Boot User Manual
Page 19
Loading OpenBoot
You can use one of the following utilities to load the OpenBoot image on the HBA:
•
•
lp6dutil Utility for DOS: See the lp6dutil utility for DOS manual (click the HBA’s Troubleshooting
link).
Load OpenBoot using lputil
Prerequisites
•
•
The Emulex driver for Solaris is installed and loaded properly.
The OpenBoot file has been downloaded from the Emulex Web site and extracted to a directory
on your local hard drive.
•
lputil is installed properly.
To load OpenBoot using lputil:
Note: If this is the first time boot code is to be loaded on the adapter, the Device Driver
Instances will be different because boot code adapters are identified by lpfc while
non-boot code adapters are identified by Fibre Channel or the PCI device/vendor ID.
If the driver instances change, it will make existing lpfc.conf configuration settings
(like persistent binding) invalid as well as any previously used /dev and /devices
directory links. To preserve existing configuration changes, enter:
/usr/sbin/lpfc/convert_path_lpfc /etc/path_to_inst
1. Start lputil by entering the complete path. The path in the example reflects the default installation
path. If the installation path was modified, adjust the command appropriately.
/usr/sbin/lpfc/lputil
2. From the Main menu, enter 3, Firmware Maintenance.
3. From the list that appears, choose the adapter onto which you want to load OpenBoot.
4. Enter 1, Load Firmware Image.
5. Enter the full path to the remote boot image file. The new boot code is transferred to flash ROM.
6. From the Firmware Maintenance menu, press 6, Boot BIOS Maintenance.
7. Press 1, Enable Boot BIOS, to enable the BootBIOS message. (If item 1 is Disable Boot BIOS,
the BootBIOS message is already enabled.)
Note: This step applies only to Solaris PCI systems, not to Solaris SBus systems.
8. To exit lputil, press 0 twice.
Combined Boot User Manual
Page 20
Configuring OpenBoot
Creating a Fibre Channel Remote Boot Disk
The procedures in this section explain how to set up your boot disk in a Solaris system.
Note: This section pertains only to Solaris systems. If you are using AIX with the IBM driver,
refer to the documentation from IBM for instructions on configuring OpenFirmware.
From the system monitor prompt:
1. Reset to default value mode.
ok set-default-mode
Note: Always reset the system before making changes to your boot settings. Changes will
not be saved if a reset is not performed first.
2. Show all system devices.
ok show-devs
The actual output will vary depending on your system. The path to the Emulex adapter will end
with lpfc@# or with fibre-channel. If the path ends with fibre-channel, OpenBoot is not loaded in
the adapter's firmware. You must load OpenBoot before continuing with this procedure. This pro-
cedure is an example only.
/pci@1f,2000/lpfc@1
/pci@1f,4000/lpfc@2
/pci@1f,2000/fibre-channel
3. Select the Emulex adapter. Select the second adapter shown above by entering the path to the
adapter. The path you enter will be similar to, but different from, the one entered in this sample
command.
ok" /pci@1f,4000/lpfc@2" select-dev
4. Check the OpenBoot version.
ok .version
5. Check the topology of the current device.
ok show-devs
ok " /pci@1f,4000/lpfc@2" select-dev
ok .topology
ok unselect-dev
6. Use these commands to set the topology for the intended Fibre Channel boot disk to point-to-
point (if the HBA is connected to a switch).
ok" /pci@1f,4000/lpfc@2" select-dev
ok set-ptp
ok unselect-dev
ok reset
Combined Boot User Manual
Page 21
To set the topology back to loop (if the HBA is connected to a hub), enter these commands.
ok" /pci@1f,4000/lpfc@2" select-dev
ok set-fc-al
ok unselect-dev
ok reset
By default, the topology is set to auto-FCAL. To set auto topology with public or private loop first,
enter these commands.
ok" /pci@1f,4000/lpfc@2" select-dev
ok set-auto-fcal
ok unselect-dev
ok reset-all
To set auto topology with point-to-point first, enter these commands.
ok" /pci@1f,4000/lpfc@2" select-dev
ok set-auto-ptp
ok unselect-dev
ok reset-all
7. Determine the device: WWPN, DID, or AL_PA.
ok probe-scsi-all
Make note of the actual DID, WWPN, or AL_PA and the corresponding boot entry.
8. Set the boot device ID.
ok" /pci@1f,4000/lpfc@2" select-dev
ok [wwpn|did|alpa] [lun] [target id] set-boot-id
ok unselect-dev
where [wwpn|did|alpa] - enter the device WWPN (point to point), DID (public loop), or ALPA
(private loop).
[lun] - enter the LUN number in hex. To enter the decimal LUN number, enter d# [lun].
[target id] - enter the target id in hex. To enter the decimal target ID, enter d# [target id].
For example, with alpa=e1, lun=100 (decimal) and target id=10 (decimal):
ok did e1 d# 100 d# 10 set-boot-id
9. Boot to the original local disk to set up the newly defined Fibre Channel disk.
ok boot [local disk]
where [local disk] - enter the complete path or the alias of the original boot disk.
Note: If the Fibre Channel disk is not found when the system is rebooted, enter "touch /
reconfigure" and reboot. If the disk is still not discovered, edit the "/kernel/drv/
lpfc.conf" file and change the topology from 4 to 2 or reverse. It may also be
necessary to add an entry for the boot drive to the sd.conf file.
Table 1: Signature Table
Signature
Valid_flag
OpenBoot signature
internal flag for OpenBoot
Combined Boot User Manual
Page 22
Table 1: Signature Table (Continued)
Signature
Host_did
Enable_flag
Boot_id
Lnk_timer
Plogi_timer
LUN
OpenBoot signature
shows host DID number
internal flag for OpenBoot
shows target ID number
internal use for OpenBoot
internal use for OpenBoot
shows boot LUN in use
shows boot ID in use
DID
WWPN
shows boot WWPN in use
Note: Target ID can be bound to either DID (destination ID) or WWPN (worldwide port
name) and saved in an adapter nvram. It can also be saved in an environmental
variable boot-device.
Making a Bootable System Disk
The examples in this procedure use the logical drive designated as "c1t1d0" (controller 1, target 1, lun
0). Your logical drive may be different.
1. Boot from the local system disk.
2. Run the format utility.
# format
3. Select the logical drive to become the boot disk (in this case, c1t1d0).
4. Select the partition option and partition the disk as desired.
5. Select the label option and write a volume label to the target disk.
For help with the format utility, refer to the man page "man format".
6. Install the boot on partition 0 of the target disk. (Enter this command as one line.)
# installboot /usr/platform/ `uname -i`/lib/fs/ufs/bootblk /dev/
rdsk/c1t1d0s0
7. Create a filesystem for each partition that will contain a mounted filesystem.
# newfs -v /dev/rdsk/c1t1d0s0 (will become root)
# newfs -v /dev/rdsk/c1t1d0s6 (will become usr)
# newfs -v /dev/rdsk/c1t1d0s7 (will become export/home)
8. Create temporary mount points for the new partitions.
# mkdir root2
# mkdir usr2
# mkdir export2
Combined Boot User Manual
Page 23
9. /dev/fd must be unmounted to copy the root file system. First, kill the volume manger.
# ps -ef|grep vold (to obtain the PID or process id)
# kill -9 PID (where PID is obtained above)
# umount /dev/fd
10. Mount, copy, then unmount the usr2 file system.
# mount /dev/dsk/c1t1d0s6 /usr2
# cd /usr
# tar cvf - * | ( cd /usr2; tar xf -)
# umount /usr2
11. Copy the export/home file system.
# mount /dev/dsk/c1t1d0s7 /export2
# cd /export# tar cvf - * | (cd /export2; tar xf -)
# umount /export2
12. Copy the root file system by first building a file list.
# cd /
ls -a > root_copy
13. Use the vi editor to edit root_copy and delete all entries that refer to mount points.
., .., usr, tmp, proc, export, root2, export2, usr2, opt (if a separate mount point)
and any other apparent filesystems displayed by the df command. Your goal in editing this file is
to have the root_copy point to system files on the root directory without pointing to mount points.
14. Join file names so that they are on one line; if you are using vi, press <shift> <j> to do this.
15. Add the tar command to the file list so that the result looks like this:
tar cvf - TT_DB arg bak bin cdrom dev devices doit etc firmware
fun kernel lib mnt mt net platform .Xauthority .cpr_config .dt
.dtprofile sbin timer var x xfn | (cd /root2; tar xf - )
16. Perform copy.
# mount /dev/dsk/c1t1d0s0 /root2
chmod 777 root_copy
sh root_copy
17. Create the additional mount points (filesystem names).
# cd /root2
# mkdir export
# mkdir opt (if opt is a separate mount point)
Combined Boot User Manual
Page 24
# mkdir proc# mkdir tmp
# mkdir vol
# mkdir usr
18. Repeat for any other mounts unique to your system that were excluded in the copy.
19. Edit /root2/etc/vfstab, changing the controller number, target number and LUN number to point
to the new Fibre Channel boot disk. For example, if the Fibre Channel boot disk is c1t1d0,
replace all local disk entries of c0t0d0 with c1t1d0.
Currently file shows:
/dev/dsk/c0t0d0s1 (swap)
/dev/dsk/c0t0d0s0
and /dev/rdsk/c0t0d0s0 (root)
/dev/dsk/c0t0d0s6
and /dev/rdsk/c0t0d0s6 (usr)
/dev/dsk/c0t0d0s7
and /dev/rdsk/c0t0d0s7 (export)
Edit file to show:
/dev/dsk/clt1d1s1 (swap)
/dev/dsk/clt1d0s0
and /dev/rdsk/clt1d0s0 (root)
/dev/dsk/clt1d0s6
and /dev/rdsk/c1t1d0s6 (usr)
/dev/dsk/clt1d0s7
and /dev/rdsk/clt1d0s7 (export)
20. Reboot the system.
# sync
# sync
# halt
ok reset
21. Boot to disk.
ok boot disk
The system should boot to the Fibre Channel disk.
22. View the current dump device setting.
# dumpadm
23. Change the dump device to the swap area of the Fibre Channel drive.
# dumpadm -d /dev/dsk/c1t1d0s1
where /dev/dsk/c1t1d0s1 is a sample path to the swap area of the Fibre Channel drive. Your
path may be different from the one shown here. Enter your path.
Combined Boot User Manual
Page 25
Viewing OpenBoot Commands
Table 2: OpenBoot Commands
Command
Effect
ok .boot - id
Displays current boot device id
ok .version
Displays current version of OpenBoot
Displays current topology
ok .topology
ok .nvram
Displays current flags for OpenBoot
Displays actual current AL_PA of adapter
Resets to default value mode
Removes boot id from boot list
Displays boot list
ok .host-did
ok set-default-mode
ok remove-boot-id
ok devalias
ok show-devs
ok probe-scsi-all
Displays list of devices found
Displays current SCSI and FC devices
Combined Boot User Manual
Page 26
Troubleshooting OpenBoot
There are circumstances in which your system may operate in an unexpected manner. The
Troubleshooting section explains several of these circumstances and offers one or more workarounds
for each situation.
The System Cannot mount or fsck /etc/vfstab Fibre Channel Boot Disk
Situation: During the boot process, the system cannot mount or fsck /etc/vfstab Fibre Channel boot disk.
Resolution: Make sure that persistent binding is implemented correctly.
A Loaded File Is Not Executable
Situation: After entering boot disk, a message states that the file that was loaded is not executable.
Resolution: The boot block may not be installed correctly to the Fibre Channel drive. See the make
bootable system disk procedure.
The System Hangs or Reboots After Displaying Driver Information
Situation: The system hangs for a long time after displaying driver information, or reboots after displaying
driver information.
Resolution: Possible incorrect topology set in the /kernel/drv/lpfc.conf file on the target disk.
Fibre Channel Disk Is Not Found
Situation: You have performed the setup tasks and the Fibre Channel disk is not found when you reboot
the system.
Resolution: Enter "touch/reconfigure" and reboot. If the disk is still not discovered, edit the "kernel/drv/
lpfc.conf" file and change the topology from 4 to 2 or the reverse. It may also be necessary to add an entry
for the boot drive to the sd.conf file.
Combined Boot User Manual
Page 27
|