LA REINA, FIGURA INSTITUCIONAL EN LA MONARQUÍA ESPAÑOLA
1. ESPOSAS, MADRES, VIUDAS: LA TIPOLOGÍA DE LAS REINAS
1.1. La reina consorte, esposa y madre del rey
This section gives notes on creating an HDLM environment.
For details about notes on operating HDLM, see section 4.1.
3.5.1 Notes on Hardware Settings
The types of HBA that are installed on one host can be mixed. However, the HBAs
connected to an HDLM-managed device must all be of the same type. Also make sure that the HBA driver versions are the same. If the types or versions of HBAs connected to the devices for the HDLM-managed SCSI disks vary, you cannot switch the path when an error occurs.
If you use version 8.00.00, 8.00.00b21-k, or 8.00.01 of the QLogic HBA driver, a path recovered after an error might be unable to be placed in the Online status, such as by an
Online operation or by automatic failback. In this case, take the following procedure:
a) Execute the following command:
# echo "scsi-qlascan" > /proc/scsi/driver-name/host-port-number driver-name: qlaxxxx (the name of the driver being used)
When the path does not recover even if this command is executed, restart the system.
You must not change vendor ID and product ID of the storage subsystem.
If you change these IDs, HDLM cannot recognize the storage subsystem.
Make sure that you start the storage subsystem before starting the host.
When a device is added to a PCI bus, and the IRQ is shared with the HBA and other devices, a problem may occur. When adding a device, make sure that the IRQ is not shared with other devices.
Note the following in an environment where a host is connected to a storage subsystem by using a fibre channel switch.
– If the host starts while the path between the fibre channel switch and the storage subsystem is disconnected, the target ID of the path might be changed after the host restarts. At that time, the disconnected path might not be recoverable while the host is running. Also, when you execute the HDLM command to display the path status, the target ID of the path before the change might be displayed or the disconnected path might not be displayed.
In either case, change the disconnected path so that the configuration is the same as those used when that path operated normally.physically restore the disconnected path in the same configuration where it used to operate normally. If the HDLM device name has been changed, reconfigure the higher-level program
– If the zone setting for the fibre channel switch has changed, the target ID of the path might have also changed. When you execute the HDLM command to display the path status, the target ID of the path before the change might be displayed. In addition, the HDLM device name might be changed after the host is restarted. Check the HDLM device name after the host is restarted. If the HDLM device name has been changed, reconfigure the higher-level program.
However, you can avoid the above situations by setting a permanent target ID for each LU with the HBA driver persistent binding functionality. For details on whether the persistent binding functionality is supported for your HBA driver and the setting method, see the manual provided with the HDLM driver.
To use a QLogic HBA driver under Red Hat Enterprise Linux AS3/ES3, both of the modules qla2300.o and qla2300_conf.o (or qla2200.o and qla2200_conf.o) must be loaded into the kernel.
If you created an environment by using the QLogic HBA driver while SUSE LINUX Enterprise Server 9 is being used, before installing HDLM, make sure that the following coding is in the line for INITRD_MODULES= in the /etc/sysconfig/kernel file.
– When using the QLA22XX HBA:
qla2200
– When using the QLA23XX HBA:
qla2300
If qla2xxx is appears in the file instead of qla2200 or qla2300, change qla2xxx to qla2200 or qla2300 as follows:
INITRD_MODULES="mptscsih qla2300 reiserfs"
After editing the /etc/sysconfig/kernel file, execute the mkinitrd command to re-create an initial RAM disk image.
3.5.2 Notes on Linux
Install and uninstall HDLM in a multi-user mode environment.
Note that if the /var directory is set up on a different partition than the root directory (/), no logs will be output to the /var/log/messages file until the /var directory has been mounted during the OS start process.
If multiple OSs exist on a disk that differs physically or logically within the same host, HDLM can be installed on each OS. Also, if multiple kernels exist on one OS, HDLM can be used only when the kernel installed with HDLM is started.
If a 32-bit distribution of a non-supported kernel package is used on a server that has an AMD 64-bit CPU, when you install HDLM, the KAPL09160-E message might be output, and the installation might fail.
For details about how to check the applicable OSs, the kernel architecture, and the CPU vendor, see 3.1.1.1.
If you use the installhdlm command to install HDLM in Red Hat Enterprise Linux AS3/ES3, the KAPL09093-I message might appear due to a problem with the rpm command.
If you respond with y to this message, installation might terminate abnormally, causing the KAPL09098-E message to appear.
If this situation arises, execute the following command to check the version of the rpm package:
# rpm -q rpm
If the rpm package version is 4.2.1-4.4 or earlier, upgrade the rpm package to version 4.2.2-0.14 or later.
If Red Hat Enterprise Linux is used and an HDLM device is not used as a boot disk, after you upgrade the initscripts package (when HDLM has been installed) and then restart the OS, you need to upgrade or re-install HDLM if all of the following conditions are satisfied:
– There is no HDLM device file (Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 only):
Confirm that there is no HDLM device file by executing the following command:
# ls /dev/sddlm*
If the following message is displayed, it indicates that there is no HDLM device file:
ls: /dev/sddlm*: No such file or directory – The HDLM driver has not been loaded
Confirm the load status of the HDLM driver by executing the following command:
# lsmod | grep sddlmfdrv
If nothing is output after command execution, this indicates that no HDLM driver has been loaded.
– HDLM information is missing in either the /etc/rc.d/rc.sysinit file or the /etc/init.d/halt file
Confirm that the HDLM information is missing by executing the following commands:
# grep DLM /etc/rc.d/rc.sysinit
# grep DLM /etc/init.d/halt
If nothing is output after command execution, this indicates that the HDLM information is missing.
If Red Hat Enterprise Linux is used and an HDLM device is used as a boot disk, after you upgrade the initscripts package (when HDLM has been installed) and then restart the OS, you need to upgrade or re-install HDLM if both of the following conditions are satisfied:
– The HDLM manager is not running
Confirm that the HDLM manager is not running by executing the command below.
# /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv
If Dead is output as follows, this indicates that the HDLM manager is not running.
HDLM Manager Ver WakeupTime Dead
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss
– When HDLM information is missing in either the /etc/rc.d/rc.sysinit file or the /etc/init.d/halt file
Confirm that the HDLM information is missing by executing the following commands:
# grep DLM /etc/rc.d/rc.sysinit
# grep DLM /etc/init.d/halt
If nothing is output after command execution, this indicates that the HDLM information is missing.
For details about upgrade installation or re-installation in an environment in which an HDLM device is used as a boot disk, see 3.7.4.
3.5.3 Notes on Installing HDLM
A license key is required to perform a new installation of HDLM.
To update the HDLM license, execute the dlnkmgr command's set-lic operation. The expiration time of the license key is determined by the type of license key specified in the license key file or entered by the user. For information on license key types and set
operation, see section 6.6.
When the dlmcfgmgr utility is executed to change the HDLM device configuration, memory might become insufficient due to the HAL daemon#. In this case, the host will not respond.
To avoid this, stop the HAL daemon when executing the dlmcfgmgr utility. The following procedure shows how to stop the HAL daemon.
#
The HAL daemon detects hardware configurations changes, for example, when a USB device or CD-ROM is inserted.
To stop the HAL daemon:
1. Check the status of the HAL daemon.
Execute the /sbin/service command to check the HAL daemon status. If the daemon is running, running will appear.
# /sbin/service haldaemon status
If the daemon is not running, stopped will appear.
2. Check the result of step 1. If the HAL daemon is running, stop the daemon.
Execute the /sbin/service command to stop the HAL daemon. Note that it might take a while to stop the daemon completely.
# /sbin/service haldaemon stop
3. Make sure that the HAL daemon is stopped.
Execute the /sbin/service command to make sure that the HAL daemon is not running.
# /sbin/service haldaemon status
4. Execute the dlmcfgmgr utility (dlmcfgmgr -r or dlmcfgmgr -i) to configure the HDLM device.
# /sbin/dlmcfgmgr –r Or
# /sbin/dlmcfgmgr –i
5. Start the HAL daemon.
Execute the /sbin/service command to start the HAL daemon.
# /sbin/service haldaemon start
Make sure that the HAL daemon is running.
Execute the /sbin/service command to make sure that the HAL daemon is running.
# /sbin/service haldaemon status
3.5.4 Notes on an Upgrade Installation or Re-installation of HDLM
A license key is required to perform a re-installation or upgrade installation of HDLM after the valid license period has expired.
To update the HDLM license, execute the dlnkmgr command's set -lic operation. The expiration time of the license key is determined by the type of license key specified in the license key file or entered by the user. For information on license key types and set operation, see 6.6.
The HDLM manager is stopped during an upgrade installation. Therefore, when you perform an upgrade installation, stop any applications that require HDLM manager operations, such as a log output operation.
– Since the HDLM manager is stopped during an upgrade installation, an error log will not be output. Also, you will not be able to set HDLM functions. After the upgrade installation finishes successfully, immediately restart the host.
– Do not cancel an upgrade installation.
3.5.5 Notes on a Device Manager Agent
When installing HDLM on a host where a Device Manager Agent 5.0 or later is installed, do not execute any of the following commands of Device Manager Agent during installation:
hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC