17.4.2 Configuring NNMi for HA
This subsection explains the procedure for configuring NNMi for HA and the settings that must be determined at the evaluation stage.
The two distinct phases of configuring NNMi for HA are as follows:
-
Copy the NNMi data files to the shared disk.
Perform this task on the primary cluster node.
-
Configure NNMi to run under HA.
-
Perform this task on the primary cluster node.
-
Perform this task on the secondary cluster node.
-
The following shows the configuration procedure.
Designate one HA cluster node as the primary NNMi management server. This is the node you expect to be active most of the time. First, configure the primary cluster node, then configure all other nodes in the HA cluster as secondary cluster nodes.
- Important note
-
If you use HTTPS communication to access NNMi servers, you must set up to use a certificate before you verify startup of the primary cluster node. For details, see 8.5 Configuring a high availability cluster to use self-signed or Certificate Authority certificates.
- Reference note
-
-
You cannot configure NNMi for HA simultaneously on multiple cluster nodes. Once the HA configuration process has been completed on one cluster node, proceed with HA configuration on the next node, and so forth until NNMi has been configured for HA on all nodes in the cluster environment.
-
For HA Monitor, you perform the configuration procedure without using nnmhaconfigure.ovpl. For details about the configuration procedure, see the Release Notes.
-
During failover, the NNMi console is unresponsive. After failover completes, NNMi users must sign in to continue their NNMi console sessions.
- Organization of this subsection
(1) NNMi HA configuration information
The HA configuration script (nnmhaconfigure.ovpl) collects information about the NNMi HA resource group. The table below lists and describes the information that you will need for configuring the primary cluster node. Gather this information before you begin the configuration procedure.
You will enter this information interactively during the configuration process by running an HA configuration script (nnmhaconfigure.ovpl). The information requested depends on the OS in use, the type of HA product, and the system configuration. Enter the requested information by following the instructions.
The character set and the number of characters permitted for the name of the HA resource group for NNMi must comply with the cluster specifications. The following characters are available to name your HA resource group for NNMi:
-
In Windows WSFC
-
Characters:
Alphabetic characters (a to z, A to Z), numeric characters (0 to 9), hyphen (-), underscore (_), period (.)
-
Number of characters: Maximum of 247 characters including the path name %NnmDataDir%hacluster\resource-group
-
-
In Solaris VCS or Solaris SCS, and in Linux VCS or Linux SCS
-
Characters:
Alphabetic characters (a to z, A to Z), numeric characters (0 to 9), hyphen (-), underscore (_)
The name must begin with an alphabetic character.
-
Number of characters: Maximum of 255 characters
-
-
In HP-UX HP SG
-
Characters:
Alphabetic characters (a to z, A to Z), numeric characters (0 to 9), hyphen (-), underscore (_), period (.)
The name must begin with an alphabetic character.
-
Number of characters: Maximum of 31 characters
-
-
In Linux HA Monitor
-
Characters:
Alphabetic characters (a to z, A to Z), numeric characters (0 to 9)
The name must begin with an alphabetic character.
-
Number of characters: Maximum of 8 characters
-