Adding New Targets Using Sd.conf (Solaris 8, 9 And 10); Configuring Boot From San - Emulex ProLiant BL620c - G7 Server User Manual

Figure 77: Bind New Target dialog box
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.
Note: A target does not appear on the target list if automapping is disabled and the target
is not already persistently bound.

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
SAN 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.)
The OneCommand Utility User Manual
.
.
.
.
.
.
Page 134