HP Hitachi Dynamic Link Manager Software - Manual (Page 198)

3. Creating an HDLM Environment
174
In an environment where HDLM has been installed, you can use the
dlmcfgmgr
utility to check the correspondence between a SCSI device and a
udev
name.
Figure 3-7: Example of Executing the dlmcfgmgr Utility with the -v and -udev
Parameters Specified shows an example of executing the
dlmcfgmgr
utility with
the
-v
and
-udev
parameters specified.
Figure 3-7: Example of Executing the dlmcfgmgr Utility with the -v and -udev
Parameters Specified
The
HDevName
,
Device
, and
Udev
columns display HDLM devices, SCSI
devices, and
udev
names, respectively.
„ To update the kernel package, you need to perform either of the following
depending on which OS you are using:
• When using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6:
Refer to the information about updating the kernel package in 4.2 Updating
Kernel Packages and Applying OS Update Packages.
• When using Red Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise
Server:
You must first uninstall HDLM before updating the kernel package, and then
re-install it after the update. Note that uninstalling and re-installing HDLM
might change the correspondence between HDLM devices and SCSI
devices.
„ To update the kernel package in an environment that satisfies the following
conditions, you need to change the Persistent Binding setting:
• The host is in a BladeSymphony environment.
• The boot disk is managed by HDLM.
• The Persistent Binding functionality is enabled.
For details about the Persistent Binding setting, see the manual Hitachi Gigabit
Fibre Channel Board User's Guide.
„ If you use HDLM on a boot disk, LUKS cannot be used for the swap partitions.
„ If you use the kdump function in an environment where an HDLM device is used
as a boot disk, you might need to create an initial RAM disk image file for kdump