17.2 Verifying the prerequisites to configuring NNMi for HA
An HA cluster in which NNMi is to be run must satisfy the requirements shown in this section.
- Overall system configuration
-
-
NNMi cannot be used in a configuration that includes multiple HA products. NNMi might not be able to correctly recognize the applicable HA product, resulting in a malfunction.
-
Windows: The NNMi installation target (%NnmDataDir% and %NnmInstallDir%) must be the same in all cluster nodes.
-
UNIX (HP Serviceguard): scp -B or rcp must be an executable environment.
-
- Resource group
-
-
NNMi setup must be initiated when there is no resource group to be configured. NNMi cannot be added to an existing resource group.
-
Make sure that the configuration supports virtual IP addresses and shared disks and that it allows NNMi to access them.
-
- Shared disk
-
-
NNMi's shared disk is stored at the location shown below. The directory name cannot contain any spaces; it must always be NNM.
Windows: drive-letter:\NNM (example: Y:\NNM) or drive-letter:\any-directory\NNM (example: Y:\JP1\NNM)
UNIX/Linux: mount-point/NNM (example: /shdsk1/NNM)
-
For a shared disk, use a storage connected by Fibre (FC-SAN), SCSI, or iSCSI. NNMi does not support a configuration that uses NAS with NFS or CIFS connection.
-
In Windows: For a shared disk, use a disk with a drive letter assigned. Do not use a disk that has been mounted by using the mount settings in Disk Manager or the mountvol command. In this manual, information regarding mount applies to UNIX.
-
In Windows: In Windows Server 2008 and Windows Server 2012, dynamic disks are not supported for clustering using Microsoft Cluster Services.
-
- Virtual IP addresses
-
-
Configure virtual IP addresses and virtual host names in such a manner that host names can be converted to IP addresses and vice versa for a name service such as DNS and hosts file.
-
Even if you use a name service such as DNS, the virtual IP addresses and virtual host names must be configured in the hosts file in such a manner that the names can be resolved. This prevents a failover error resulting from a name resolution error in the event of a communication error that leads to failover.
-
If you configure IPv6's logical IP address as a resource, add it manually after you have finished the procedure described in 17.4 Configuring HA. For the configuration procedures, see the cluster software documentation.
The cluster software versions that support IPv6, a configuration using IPv6, and whether IPv6 and IPv4 can be intermixed depend on the cluster software specifications.
-
- Virtual host names
-
When you configure your cluster environment, set virtual host names to be resolved as IPv4 addresses.