17.4.3 Configuring NNMi for HA (Windows)

If you have not already done so, complete the procedure described in 17.2 Verifying the prerequisites to configuring NNMi for HA.

If you have not already done so, install NNMi, and then verify that NNMi is working correctly.

Use the following command to back up all NNMi settings and data:

Example:

nnmbackup.ovpl -scope all -target nnmi_backups

For details about this command, see Chapter 18. NNMi Backup and Restore Tools.

In the initial status of NNMi cluster environment configuration, the data in the primary cluster node must exactly match the data in the secondary cluster node. Therefore, restore the backup data obtained here during the secondary cluster node configuration procedure.

Provide a shared disk for the NNMi HA resource group.

Important note

Verify that the provided shared disk satisfies the following conditions:

• It has already been formatted.

• It has enough free space.

• It is not being used by any other resource group.

• A user with administrator permissions has the Full Control permission, and a built-in Local Service user (Users group) has the Read & execute permissions.

Stop NNMi:

%NnmInstallDir%bin\ovstop -c

Copy the NNMi files to the shared disk:

%NnmInstallDir%misc\nnm\ha\nnmhadisk.ovpl NNM -to HA-mount-point

Important note

Specify for HA-mount-point the drive of the shared disk or any directory under the shared disk drive (example: Y: or Y:\JP1).

The directory name cannot contain any spaces.

The directory NNM is created immediately below the specified path (example: Y:\NNM or Y:\JP1\NNM).

The storage directory cannot be renamed.

In WSFC, you must perform this step on the node that owns the shared disk. You can determine whether the node owns the shared disk by using Failover Cluster Management.

Create an NNMi HA resource group:

%NnmInstallDir%misc\nnm\ha\nnmhaconfigure.ovpl NNM

For details about the configuration items for this command, see 17.9.2 NNMi-provided HA configuration scripts.

Make sure that you specify disk, not none, for the shared disk type. Specify for the shared disk the path specified in step 3 in subsection (b).

Configuration example

The HA configuration items are listed below in the order they are entered interactively to nnmhaconfigure.ovpl. Enter the appropriate values based on the information provided in Table 17-3 NNMi HA primary cluster node configuration information in 17.4.2 Configuring NNMi for HA.

HA configuration item	Example setting
HA resource group name	jp1ha1
Virtual host name	jp1ha1
Network interface of the virtual host	Local area connection
Type of shared file system	disk (make sure that you specify disk)
Directory to be mounted	Y drive

Important note

Before you execute the configuration command, check the following notes:

• If a value specified in nnmhaconfigure.ovpl is already in use by another resource group or resource, a resource creation error occurs. Before you execute nnmhaconfigure.ovpl, verify that the specified values are not already in use.

• If a specified resource group name, IP address, or disk is already in use, the cluster software command executed to create resources results in an error. If an error occurs, nnmhaconfigure.ovpl terminates abnormally at that point, in which case the resource group and resources that had been created up to that point remain. Delete those remaining resources before you resolve the error and re-execute nnmhaconfigure.ovpl.

• For the network interface for which a virtual address is set, verify the following:

• In WSFC: In Networks in the Failover Cluster Management console, verify the resources that include a network address of logical IP address.

Execution example

The following shows an example screen display in which the example configuration values are specified, where each input item follows a question mark (?).

C:\Program Files (x86)\Hitachi\Cm2NNMi\misc\nnm\ha>nnmhaconfigure.ovpl NNM
QUESTION: Enter the name of HA resource group:  ? jp1ha1
 
A primary node configuration has been discovered.
 
QUESTION: Enter a valid virtual host name:  ? jp1ha1
Available network interface:
 
Network subnet mask  Network interface
255.255.255.0           Cluster network 3
255.255.255.0           Cluster network 1
 
Available value:
1: Cluster network 3
2: Cluster network 1
QUESTION: Enter the type of shared file system:  ? 2
Available value:
1: disk
2: none
QUESTION: Enter the type of shared file system (disk, none):  ? 1
QUESTION: Enter the directory to mount disk:  ? Y:
Creating a resource group.
 
Creating the resource group 'jp1ha1'...
 
Group             Node          Status
-------------------- --------------- ------
jp1ha1               NNMX64-33       Offline
 
 
Creating the resource group 'jp1ha1-Name'...
 
Resource             Group             Node          Status
-----------------------------------------------------------
jp1ha1-Name          jp1ha1               NNMX64-33       Offline
 
 
Making the resource 'jp1ha1-Name' dependent on the resource 'jp1ha1-IP'...
 
Configuring the HA value  C:/ProgramData/Hitachi/Cm2NNMi/shared/nnm/conf/ov.conf.
Disabling the automatic startup of HP OpenView Process Manager service.
[SC] ChangeServiceConfig SUCCESS
Note: Updating NNMi FQDN to match the specified virtual host name. Configuring fqdn to jp1ha1.xxx.xxx.
 
Configuring the domain to xxx.xxx.
 
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
 
Generating a new SSL certificate.
 
Generating a key store certificate of jp1ha1.xxx.xxx.selfsigned.
[Completed successfully]
 
Exporting the generated certificate to the trust store.
 
The certificate has been saved in temporary.cert.
The certificate has been added to the key store.
 
C:\Program Files (x86)\ Hitachi\Cm2NNMi\misc\nnm\ha

In WSFC, register the disk resource to the resource group and set its dependency with the general-purpose script resource.

To register a disk resource, use the Failover Cluster Management console. The following example assumes that a shared disk has been registered to the cluster service:

• In the Failover Cluster Management console, open resource-group.

• Choose Add a disk, and then register an appropriate disk resource.

• Open the Dependencies tab of the resource-group-APP properties.

• Register the disk resource in the dependencies. For AND/OR, select AND.

Configure resource-group in such a manner that failover occurs in the event of a monitoring process error.

In WSFC:

Open the properties of resource-group-APP, and then click the Policies tab.

Verify that If restart is unsuccessful, fail over all resources in this service or application is selected, and then set Maximum restarts in the specified period to 0.

If it is selected, clear the check box If all the restart attempts fail, begin restarting again after the specified period (hh:mm).

Important note

Configuration of resource-group and the resource group registered to resource_group is used to specify actions such as error handling. For details about the role of each configuration item, see the cluster service Help.

On the primary cluster node, restart the cluster service.

By restarting, the specified configuration settings are applied and the NNMi environment variables are loaded. You can start and stop the service by executing the net start ClusSvc and net stop ClusSvc commands, respectively.

Important note

If you use HTTPS communications to access the NNMi server, you must configure the cluster to use an appropriate certificate. For details, see 8.5 Configuring a high availability cluster to use self-signed or Certificate Authority certificates.

Start the NNMi HA resource group.

Execute the start command on the primary cluster node.

• Execute the following start command:

%NnmInstallDir%misc\nnm\ha\nnmhastartrg.ovpl NNM resource-group

• Verify that resource-group has started.

  If NNMi does not start successfully, see 17.8 Troubleshooting the HA Configuration.

NNMi is now running under HA.

Important note

Do not use the ovstart and ovstop commands for normal NNMi operation in the HA configuration. Use these commands only when instructed to do so for HA maintenance purposes. To start and stop NNMi in the HA configuration, start or stop the HA resource group by using the cluster software.

If you have not already done so, complete the procedure described in 17.2 Verifying the prerequisites to configuring NNMi for HA

If you have not already done so, install NNMi, and then verify that NNMi is working correctly.

Restore the backup data.

Restore onto the secondary cluster node the backup data obtained in step 3 in subsection (a) in 17.4.3(2) Configuring NNMi on the primary cluster node.

%NnmInstallDir%bin\nnmrestore.ovpl -force -partial -source backup-data

For details about this command, see Chapter 18. NNMi Backup and Restore Tools.

Stop NNMi.

%NnmInstallDir%bin\ovstop -c

Configure the NNMi HA resource group:

%NnmInstallDir%misc\nnm\ha\nnmhaconfigure.ovpl NNM

Specify the HA resource group name when prompted by the command.

Execution example

C:\Program Files (x86)\Hitachi\Cm2NNMi\misc\nnm\ha>nnmhaconfigure.ovpl NNM
QUESTION: Enter the name of HA resource group:  ? jp1ha1
a secondary node configuration has been discovered.
 
Disabling the automatic startup of HP OpenView Process Manager service.
[SC] ChangeServiceConfig SUCCESS
Note: Updating NNMi FQDN to match the specified virtual host name. Configuring fqdn to jp1ha1.xxx.xxx.
 
Configuring the domain to xxx.xxx.
 
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
 
Generating a new SSL certificate.
 
C:\Program Files (x86)\ Hitachi\Cm2NNMi\misc\nnm\ha

Verify that configuration was successful:

%NnmInstallDir%misc\nnm\ha\nnmhaclusterinfo.ovpl -group resource-group -nodes

This command outputs a list of all nodes that are in the specified HA resource group.

On the secondary cluster node, restart the cluster service.

By restarting, the specified configuration settings are applied and the NNMi environment variables are loaded. You can start and stop the service by executing the net start ClusSvc and net stop ClusSvc commands, respectively.

Optionally, test the configuration by taking the HA resource group on the primary node offline and then bringing the HA resource group on the secondary node online.

Important note

Problems might occur in the created resource group, such as the service no longer starts successfully if the NNMi default values for resource group and resource configuration are changed.

Special care is needed if the following configuration item is changed to a value that is smaller than its default value:

• Length of period during which the cluster service waits until it restarts a resource

WSFC standard installation:

Period on the Policies tab for the resource-group-APP properties (default value: 30:00 minutes)

DeadlockTimeout value for the resource-group-APP properties (default value: 2,700,000 milliseconds)