Emulex OneCommand Manager Application User Manual (P006979-01A Version 5.2, August 2011)

The OneCommand Manager User Manual Page 159
5. Click the type of binding you want to use, and type the WWPN, WWNN or D_ID you want to bind
to the target.
6. Select the Bus ID and Target ID that you want to bind, and click OK.
Adding New Targets Using sd.conf (Solaris 8, 9 and 10)
You can perform on-the-fly configuration changes, without rebooting, using the OneCommand Manager
application. For Solaris 8, you must first add the new targets to the sd.conf file using a text editor.
To add new targets using sd.conf (Solaris 8):
1. Edit the Solaris SCSI configuration file (sd.conf):
#vi /kernel/drv/sd.conf
.
.
.
name="sd" parent="lpfc" target=17 lun=1;
name="sd" parent="lpfc" target=18 lun=10;
name="sd" parent="lpfc" target=19 lun=15;
.
.
.
2. Save the file and exit the text editor.
Configuring Boot from SAN
You can use the OneCommand Manager application to configure a system to boot from an attached FC/
FCoE LUN. Boot from SAN allows servers on a storage network to boot their operating systems directly
from a SAN storage device, typically identified by its WWPN and a LUN located on the device. By
extending the server system BIOS, boot from SAN functionality is provided by the BootBIOS contained
on an Emulex adapter in the server. When properly configured, the adapter then permanently directs the
server to boot from a LUN on the SAN as if it were a local disk. (COMSTAR ports do not support boot
from SAN.)
Boot Types
Using the Maintenance tab, you can enable, disable or configure boot from SAN for x86 BootBIOS,
EFIBoot and OpenBoot (also know as FCode).
• x86 BootBIOS works with the existing BIOS on x64 and x86 systems.
• OpenBoot (FCode) works with the existing system BIOS on Solaris SPARC systems using the
SFS driver and on Linux PowerPC systems. OpenBoot is also called FCode.
• EFIBoot works with Intel Itanium 64-bit and x64-based systems and provides 64-bit system boot
capability through the use of the EFI (Extensible Firmware Interface) Shell.
Emulex provides Universal Boot and Pair Boot code images that contain multiple types of boot code.
These images provide multi-platform support for boot from SAN. Universal Boot and Pair Boot
transparently determine your system platform type and automatically execute the proper boot code
image in the adapter. These code images reside in adapter flash memory, allowing easier adapter
portability and configuration between servers.
Note: A target does not appear on the target list if automapping is disabled and the target
is not already persistently bound.