Combined Boot User Manual
Page 20
Loading OpenBoot
You can use one of the following utilities to load the OpenBoot image on the HBA:
•
lputil: See
Load OpenBoot using lputil
on page 20.
•
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:
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.)
8.
To exit lputil, press
0
twice.
9.
Follow the instructions in
Creating a Fibre Channel Remote Boot Disk
on page 21.
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
Note:
This step applies only to Solaris PCI systems, not to Solaris SBus systems.
