![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference
This subsection describes items to be checked before you start installation of PFM - RM for Platform.
- Organization of this subsection
- (1) Prerequisites
- (2) Information needed for setting up PFM - RM for Platform for logical host operation
- (3) Notes about logical host failover
- (4) Notes about upgrading when logical operation is used
(1) Prerequisites
Following are the prerequisites for using PFM - RM for Platform in a cluster system.
(a) Cluster system
Make sure that the following conditions are satisfied:
- The cluster system is controlled by cluster software.
- The cluster software is set up in such a manner that it controls startup and termination of the PFM - RM for Platform that is running on the logical host.
(b) Shared disk
Make sure that the following conditions are satisfied:
- A shared disk is available to each logical host and information can be inherited from the executing node to the standby node.
- The shared disk is connected to each node physically by Fibre Channel or SCSI.#1
- The shared disk can be placed offline forcibly by means such as the cluster software in order to implement failover even when there is still an active process that is using the shared disk.
- If multiple PFM products are running on the same logical host, the shared disk uses the same directory names.#2
- #1
- Performance Management does not support a configuration that uses a network drive or a disk replicated via the network as the shared disk.
- #2
- You can change the storage location of the Store database and store it in a different directory on the shared disk.
(c) Logical host names and logical IP addresses
Make sure that the following conditions are satisfied:
- Each logical host has a logical host name and a corresponding logical IP address, and that this information can be inherited from the executing node to the standby node.
- The logical host names and logical IP addresses are set in the hosts file and name server.
- If DNS operation is employed, the host name without the domain name is used as the logical host name, not the FQDN name.
- All physical and logical host names are unique within the system.
- Note
- Do not specify a physical host name (host name displayed by the uname -n command) as a logical host name. If you do so, normal communication processing may not occur.
- A logical host name is expressed as 1 to 32 bytes of alphanumeric characters. None of the following symbols nor the space character can be used:
/ \ : ; * ? ' " < > | & = , .
- A logical host name cannot begin with localhost, an IP address, or the hyphen (-).
(d) SSH connection
Make sure that the following conditions are satisfied:
- A private key with the same path is available in the environments for both the executing node and the standby node.
- That private key can be used to connect to the monitored hosts.
- Note
- If you use the private key that is created automatically when you install PFM - Remote Monitor for Platform, use one of the following methods to register the private and public keys:
- Copy the private key created at the executing server to the standby server, and then establish its correspondence with the public key that is distributed from the executing server to the monitored host.
- Create public keys at both executing and standby servers, and then establish correspondence between them by registering both public keys at the monitored hosts.
For details about the SSH connection settings, see 2.2.5 SSH connection setting method.
(2) Information needed for setting up PFM - RM for Platform for logical host operation
If you run PFM - RM for Platform on a logical host, you need the information listed in the table below in addition to the environment information that is needed for setting up a normal PFM - RM for Platform.
Table 3-3 Information needed for setting up PFM - RM for Platform for logical host operation
No. Item Example 1 Logical host name 2 Logical IP address 3 Shared disk If multiple Performance Management programs are running on the same logical host, all of them must use directories on the same shared disk
For details about the space requirements on the shared disk, see A. Estimating System Requirements.
(3) Notes about logical host failover
If you employ a system configuration in which PFM - RM for Platform runs on a logical host, evaluate whether the entire logical host should failover in the event of a PFM - RM for Platform failure.
If a PFM - RM for Platform failure is to result in failover of the entire logical host, any other job application that is running on the logical host will also result in failover, which may affect the job adversely.
Typically, we recommend that you use one of the following cluster software settings so that errors on PFM - RM for Platform do not affect the operation of other applications:
- Operation of PFM - RM for Platform is not monitored.
- Detection of PFM - RM for Platform errors does not result in failover.
(4) Notes about upgrading when logical operation is used
To upgrade a PFM - RM for Platform that is running on a logical host, you must mount the shared disk at either the executing node or the standby node.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.