Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure NNMi in a High Availability Cluster > Maintaining the High Availability Configuration

Maintaining the High Availability Configuration

This section describes how to perform the following High Availability configuration maintenance tasks:

Maintaining Add-on NNM iSPIs in an NNMi HA Cluster

Maintenance Mode

When you need to apply NNMi patches or update to a newer version of NNMi, put the NNMi HA resource group into maintenance mode to prevent failover during the process. When the NNMi HA resource group is in maintenance mode, you (or an installation script) can run the ovstop and ovstart commands as needed on the primary (active) cluster node.

Caution Never run the ovstart or ovstop commands on a secondary (backup) cluster node.

Putting an HA Resource Group into Maintenance Mode

Putting an HA resource group into maintenance mode disables HA resource group monitoring. When an HA resource group is in maintenance mode, stopping and starting the products in that HA resource group do not cause failover.

To put an HA resource group into maintenance mode, on the active cluster node, create the following file:

Windows: %NnmDataDir%\hacluster\<resource_group>\maintenance
Linux: $NnmDataDir/hacluster/<resource_group>/maintenance

Note The maintenance file contents are as follows:

To disable monitoring of the HA resource group, create the maintenance file. The file can be empty or can contain the keyword NORESTART.
To prevent NNMi from starting during a configuration procedure, the first line of the maintenance file must contain only the single word:
NORESTART

Removing an HA Resource Group from Maintenance Mode

Taking an HA resource group out of maintenance mode re-enables HA resource group monitoring. Stopping the products in that HA resource group causes the HA resource group to fail over to a passive cluster node.

To remove an HA resource group from maintenance mode, follow these steps:

Verify that NNMi is running correctly:

ovstatus -c

All NNMi services should show the state RUNNING.
Delete the maintenance file from the node that was the active cluster node before maintenance was initiated. This file is described in Putting an HA Resource Group into Maintenance Mode.s

Maintaining NNMi in an HA Cluster

This section describes how to perform the following tasks that might be required to maintain NNMi in a High Availability (HA) Cluster.

Starting and Stopping NNMi

Changing NNMi Hostnames and IP Addresses in a Cluster Environment

Stopping NNMi Without Causing Failover

Restarting NNMi after Maintenance

Starting and Stopping NNMi

Note While NNMi is running under High Availability (HA), do not use the ovstart and ovstop commands unless instructed to do so for HA maintenance purposes.

For normal operation, use the NNMi-provided HA commands or the appropriate HA product commands for starting and stopping HA resource groups.

Changing NNMi Hostnames and IP Addresses in a Cluster Environment

A node in a cluster environment can have more than one IP address and hostname. If a node becomes a member of another subnet, you might need to change its IP addresses. As a result, the IP address or fully-qualified domain name might change.

For example, on Linux systems, the IP address and the related hostname are generally configured in one of the following:

/etc/hosts
Domain Name Service (DNS)
Network Information Service (NIS)

NNMi also configures the hostname and IP address of the management server for the managed node in the NNMi database.

If you are moving from a non-name-server environment to a name-server environment (that is, DNS or BIND), make sure that the name server can resolve the new IP address.

Hostnames work within IP networks to identify a managed node. While a node might have many IP addresses, the hostname is used to pinpoint a specific node. The system hostname is the string returned when you use the hostname command.

When changing the virtual hostname or IP address of the NNMi HA resource group, you must update the licenses.txt file on the shared disk with the new information from the license file on the active node. Complete the following procedure to correctly update the HA configuration.

To change the virtual hostname or IP address of the NNMi HA resource group, perform these steps on the active NNMi cluster node:

If you have purchased NNMi Premium or NNMi Ultimate, you need to use the license keys you requested from the Password Delivery Center for use with application failover or high availability. Be sure to request the following:

High Availability: Obtain a license key for the virtual IP address of the NNMi HA resource group. This license key is initially used on the primary server and then used on the secondary server when needed.
Application Failover: Obtain two license keys; one for the physical IP address of the primary server and one for the physical IP address of the standby server.

Convert the license keys for the prior virtual IP address of the NNMi HA resource group to the new virtual IP address of the NNMi HA resource group.

Caution Do not install the new license keys at this time.
Put the NNMi HA resource group into maintenance mode as described in Putting an HA Resource Group into Maintenance Mode.

Stop the NNMi HA resource group:

Windows:

%NnmInstallDir%\misc\nnm\ha\nnmhastoprg.ovpl NNM <resource_group>

Linux:

$NnmInstallDir/misc/nnm/ha/nnmhastoprg.ovpl NNM <resource_group>

Change the IP address or node name of the NNMi HA resource group:
1. In the ov.conf file, edit the NNM_INTERFACE entry to be the new hostname or IP address.
2. In the ovspmd.auth file, edit any lines containing the old hostname to contain the new hostname.
The ov.conf and ovspmd.auth files are available in the following location:
- Windows: %NnmDataDir%\shared\nnm\conf
- Linux: $NnmDataDir/shared/nnm/conf
If you changed the node name of the NNMi HA resource group, set NNMi to use the new fully-qualified domain name of the NNMi HA resource group with the nnmsetofficialfqdn.ovpl command. For example:
```
nnmsetofficialfqdn.ovpl newnnmi.servers.example.com
```
For more information, see the nnmsetofficialfqdn.ovpl reference page, or the Linux manpage.
Change the cluster configuration to use the new IP address:
- WSFC:
  
  In Failover Cluster Management, open <resource_group>.
  
  Double-click <resource_group>-ip, select Parameters, and the enter the new IP address.
- VCS:
```
$NnmInstallDir/misc/nnm/ha/nnmhargconfigure.ovpl NNM <resource_group> -set_value <resource_group>-ip 
Address <new_IP_address>
```
- RHCS:
  
  On the active HA cluster node, edit the /etc/cluster/cluster.conf file to replace ip address="<old_IP_address>" with ip address="<new_IP_address>". Then run ccs_tool update /etc/cluster/cluster.conf to update all other systems.
Install the license keys for the new virtual IP address of the NNMi HA resource group as described in Apply Licenses.
Update the licenses.txt file on the shared disk with the new information from the LicFile.txt file on the active node. Do one of the following:
- If the licenses.txt file exists in the NNM directory on the shared disk, append the new license keys in LicFile.txt on the active node to licenses.txt on the shared disk.
- If the licenses.txt file does not exist on the shared disk, copy LicFile.txt from the active node to licenses.txt in the NNM directory on the shared disk.
On the active node, the LicFile.txt file is in the following location:
- Windows: %NnmDataDir%\shared\nnm\conf\licensing\LicFile.txt
- Linux: $NnmDataDir/shared/nnm/conf/licensing/LicFile.txt
On the shared disk, example locations of the licenses.txt file are as follows:
- Windows: S:\NNM\licenses.txt
- Linux: /nnmount/NNM/licenses.txt

Start the NNMi HA resource group:

Windows:

%NnmInstallDir%\misc\nnm\ha\nnmhastartrg.ovpl NNM <resource_group>

Linux:

$NnmInstallDir/misc/nnm/ha/nnmhastartrg.ovpl NNM <resource_group>

Verify that NNMi started correctly:

ovstatus -c

All NNMi services should show the state RUNNING.
Take the NNMi HA resource group out of maintenance mode as described in Removing an HA Resource Group from Maintenance Mode.

Stopping NNMi Without Causing Failover

When you need to perform NNMi maintenance, you can stop NNMi on the active cluster node without causing failover to a currently passive node.

Follow these steps on the active cluster node:

Put the NNMi HA resource group into maintenance mode as described in Putting an HA Resource Group into Maintenance Mode.
Stop NNMi:

ovstop -c

Restarting NNMi after Maintenance

If you have stopped NNMi in the manner that prevents failover, follow these steps to restart NNMi and HA monitoring:

Start NNMi:

ovstart -c
Verify that NNMi started correctly:

ovstatus -c

All NNMi services should show the state RUNNING.
Take the NNMi HA resource group out of maintenance mode as described in Removing an HA Resource Group from Maintenance Mode.

Maintaining Add-on NNM iSPIs in an NNMi HA Cluster

The NNM iSPIs are closely linked to NNMi. When add-on NNM iSPIs are installed on the nodes in the NNMi HA cluster, use the NNMi HA cluster maintenance procedures as written.

Send Help Center feedback