Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Booting from SAN
- Chapter 3: Updating and Enabling Boot Code
- Chapter 4: Emulex LightPulse FC BIOS utility
- 4.1 Navigating the Emulex LightPulse FC BIOS Utility
- 4.2 Starting the Emulex LightPulse FC BIOS Utility
- 4.3 Enabling an Adapter to BFS
- 4.4 Scanning for Target Devices
- 4.5 Configuring Boot Devices
- 4.6 Configuring Advanced Adapter Parameters
- 4.6.1 Changing the Default AL_PA
- 4.6.2 Changing the PLOGI Retry Timer
- 4.6.3 Enabling or Disabling the Spinup Delay
- 4.6.4 Setting Auto Scan
- 4.6.5 Enabling or Disabling EDD 3.0
- 4.6.6 Enabling or Disabling the Start Unit Command
- 4.6.7 Enabling or Disabling the Environment Variable
- 4.6.8 Enabling or Disabling Auto Boot Sector
- 4.7 Configuring Adapter Firmware Parameters
- 4.8 Resetting the Adapter to Default Values
- 4.9 Using Multipath BFS
- Chapter 5: OpenBoot
- Chapter 6: Configuring Boot Using the UEFI HII
- 6.1 Prerequisites
- 6.2 Starting the UEFI HII
- 6.3 Configuring Boot in the UEFI HII
- 6.4 Setting Boot from SAN
- 6.5 Scanning for Fibre Devices
- 6.6 Adding Boot Devices
- 6.7 Deleting Boot Devices
- 6.8 Changing the Boot Device Order
- 6.9 Configuring HBA and Boot Parameters
- 6.9.1 Changing the Topology
- 6.9.2 Changing the PLOGI Retry Timer
- 6.9.3 Changing the Link Speed
- 6.9.4 Changing the Maximum LUNs per Target
- 6.9.5 Changing the Boot Target Scan Method
- 6.9.6 Changing the Device Discovery Delay
- 6.9.7 Configuring the Brocade FA-PWWN
- 6.9.8 Configuring the Brocade Boot LUN
- 6.9.9 Configuring 16G Forward Error Correction
- 6.9.10 Selecting Trunking
- 6.10 Resetting Emulex Adapters to Their Default Values
- 6.11 Displaying Adapter Information
- 6.12 Legacy-Only Configuration Settings
- 6.13 Requesting a Reset or Reconnect
- 6.14 Emulex Firmware Update Utility
- 6.15 NVMe over FC Boot Settings
- 6.16 Enabling or Disabling the HPE Shared Memory Feature (HPE Systems Only)
- Chapter 7: Troubleshooting
Broadcom BT-FC-UG126-100
20
Emulex Boot for the Fibre Channel Protocol User Guide
b. Verify that the nfsd daemon is running, or start the nfsd daemon.
If the install server is running the current Solaris release or a compatible version, type the following command.
# svcs -l svc:/network/nfs/server:default
If the nfsd daemon is online, continue to Step c. If the nfsd daemon is not online, start it.
# svcadm enable svc:/network/nfs/server
c. Share the install server.
# shareall
11. Change directories to root (/).
# cd /
12. Eject the Solaris DVD.
13. (Optional) Patch the files that are located in the miniroot on the net install image that was created by
setup_install_server. Patching a file might be necessary if a boot image has problems. For more information, refer
to the Solaris operating system documentation.
2.3.3.1 Installing Solaris by Migrating an Image from a Local SCSI Disk
To install Solaris by migrating an image from a local SCSI disk, perform these steps:
1. Type the following at the OBP prompt:
show-devs
The ID information for each found adapter is displayed, for example:
/pci@5d,700000/lpfc@1 select-dev
2. Select the Emulex adapter on which you want to enable BFS by entering the path to the adapter, for example:
" /pci@5d,700000/lpfc@1" select-dev
3. To view the current boot device ID, type the following command:
show-devs
" /pci@5d,700000/lpfc@1" select-dev /* to select lpfc@1 (for example) */
.boot-id
Make a note of the WWPN, D_ID, or AL_PA returned from the probe and write down the corresponding boot entry.
4. To enable boot from the SAN, set the boot device ID to the SAN device from which you want to boot, for example:
" /pci@5d,700000/lpfc@1" select-dev
wwpn|did|alpa lun target_id set-boot-id
unselect-dev
where:
– wwpn|did|alpa is the device WWPN, D_ID, or AL_PA of the storage device.
– lun is the LUN number in hexadecimal. To enter it in decimal, enter d# [lun].
– target_id is the target ID in hexadecimal. To enter it in decimal, enter d# [target_id].
NOTE: Use the WWPN in most cases. The D_ID and AL_PA might change between boots, causing the SAN boot to fail,
unless the D_ID and AL_PA are specifically configured to not change between boots.
Example 1: alpa = e1, lun = 100 (decimal), and target id = 10 (decimal):
alpa e1 d# 100 d# 10 set-boot-id
Example 2: wwpn = 50000034987AFE, lun = af (hexadecimal), and target id = 10 (decimal):
wwpn 50000034987AFE af d# 10 set-boot-id
Example 3: did = 6312200, lun = 25 (hexadecimal), and target id = f (hexadecimal):
did 6312200 25 f set-boot-id