Hitachi Dynamic Link Manager, User Manual

Page: 234 / 746

3. Creating an HDLM Environment
210
device. Note that if settings are incorrect, the OS might not start.
In this subsection, the procedure assumes that you are using
GRUB
or
ELILO
as the
default boot loader in Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10,
or SUSE LINUX Enterprise Server 11.
To perform an upgrade installation of HDLM in a multi-path boot disk environment
that uses a logical volume (LVM2) on an HDLM device:
1.
Log in to Linux as a user with root permissions.
2. Make sure that the HDLM device is defined in the
/etc/fstab
file.
:
:
/dev/sddlmaa1 /boot ext3 defaults 1 2
:
:
This example assumes that IA32 uses
GRUB
as the boot loader. When you use IPF
that uses
ELILO
as the boot loader, the mount point is displayed as
/boot/efi
instead of
/boot
in the line where
/boot
is coded, and the file system type is
displayed as
vfat
instead of
ext3
.
3. Execute the HDLM-configuration definition utility (
dlmcfgmgr)
with the
-v
parameter specified to check the correspondence between the HDLM device and
the SCSI device.
# dlmcfgmgr -v
HDevName Management Device Host Channel Target Lun
/dev/sddlmaa configured /dev/sda 0 0 0 0
KAPL10302-I /sbin/dlmcfgmgr completed normally.
The
HDevName
column indicates the HDLM device, and the
Device
column
indicates the SCSI device.
4. Edit the
/etc/fstab
file.
Change the
/boot
mount point that you checked in step 2 from the HDLM device
to the SCSI device. Comment out the existing HDLM device specification by
placing a hash mark (
#
) at the beginning of each line, and then add the SCSI
device specification as shown below, based on the correspondence between the
HDLM device and the SCSI device as checked in step 3.
:
:
#/dev/sddlmaa1 /boot ext3 defaults 1 2