Run the nnmcluster -display command on server X and search the displayed results for the term ACTIVE, such as ACTIVE_NNM_STARTING or ACTIVE_ SomeOtherState. Wait a few minutes for server X to become the first active server in the cluster. Starts the NNMi services on NNMi management server X (the active server).įor details, see the nnmcluster Reference Page. NNMi management server X assumes the active state. On server X, start the NNMi cluster manager: nnmcluster -daemonĪfter you run the nnmcluster -daemon command on NNMi management server X, the NNMi cluster manager goes through the following startup routine:Ĭonnects NNMi management server X to the cluster.ĭetects that there are no other NNMi management servers present. Server X and server Y are running different NNMi versions.įor example, server X might be running NNMi 10-10 and server Y a patched version of NNMi 10-10.
Hp nnmi 9.2 perl folder backup windows#
Server X and server Y are running different operating systems.įor example, server X might be running a Linux operating system and server Y a Windows operating system. Make sure you merged the nnm.keystore files and the nnm.truststore files. The key CRCs might be different on server X and server Y.Ĭheck the contents of the following file on both server X and server Y:Ī firewall on server X or server Y might be preventing the nodes from communicating. The cluster names might be different on server X and server Y. Here are some things to check for and correct before continuing: The nodes are not communicating with each other. If information about both nodes is not displayed, If NNMi is configured correctly, the display lists both server X and server Y. To terminate the command, press the Enter key and then enter the command quit. Local? NodeType State OvStatus Hostname/Addresses Run the following command on both server X and server Y: nnmclusterĮach server displays something similar to the following: = Current cluster state =ĭate/Time: 15 3 2011 - 09:37:58 (GMT+0900)Ĭluster name: ThisCluster (key CRC:626,187,650) $NnmDataDir/shared/nnm/conf/nnmcluster/cluster.keystoreĬonfigure the NIC that is used for cluster communication between both nodes.įor details, see 16.3.2 Setting application failover communications.
You must choose your approach and complete one set of instructions.īack up the source files, which will be used when canceling the application failover configuration, and then copy the following When configuring the application failover feature, you must merge both nodes' nnm.keystore file contents into a single nnm.keystore file and both nodes' nnm.truststore file contents into a single nnm.truststore file. Add the hostnames of all nodes in the cluster to the com.hp.ov. parameter in the nms-cluster.properties file:Ĭom.hp.ov. = fqdn_for_active,fqdn_for_standbyĬonfigure the NNMi certificate (use nnm.keystore and nnm.truststore files or a certification organization).ĭepending on the method you selected, complete the set of instructions described in 8.3 Configuring application failover to use self-signed certificates or 8.4 Configuring the application failover feature to use CA certificates. Specifying this parameter enables the application failover feature:Ĭom.hp.ov.=M圜luster c. SpecifyĪlphanumeric characters for the name, which is case-sensitive.
Use the same name when configuring both the active and standby servers. Declare a unique name for the NNMi cluster. $NnmDataDir/shared/nnm/conf/props/nms-cluster.properties b. %NnmDataDir%shared\nnm\conf\props\nms-cluster.properties Use the procedure shown below.Įdit in the following steps means to uncomment (remove the leading #! from) the lines in the text block within the file and to modify the text. Run the ovstop command on each server to shut down NNMi.Ĭonfigure server X (active) and server Y (standby) for the application failover feature using guidance from the detailed instructionsĬontained in the nms-cluster.properties file.
Hp nnmi 9.2 perl folder backup install#
Install a permanent license in each server, as described in 3.3 Licensing NNMi in the manual Job Management Partner 1/Consolidated Management 2/Network Node Manager i Installation Guide. Install NNMi on the active server, server X, and on the standby server, server Y, as described in the manual Job Management Partner 1/Consolidated Management 2/Network Node Manager i Installation Guide. 16.3 Configuring NNMi for application failover
0 kommentar(er)
