Monday, 11 February 2013

To change the IP address or hostname of the NNMi 9.20


To change the IP address of the NNMi 9.20 management server, follow these steps:

1 Go to http://www.webware.hp.com.
2 Click Manage Licenses.
3 Log in; then obtain your new license key by following the procedures to complete the move process.
4 Configure the NNMi management server with the new IP address.
5 Configure the DNS servers to recognize the new IP address of the NNMi management server.
6 Reboot the NNMi management server.
7 At a command prompt, enter the following command: nnmlicense.ovpl NNM -g
8 In the Autopass: License Management dialog box, click Remove License Key.
9 Select the license key to remove.
10 Select Remove Licenses permanently.
11 Click Remove; then close the dialog box.
12 Copy the new license key that you obtained in step 3 into a text file named license.txt.
13 At a command prompt, enter the following command:
nnmlicense.ovpl NNM -f license.txt
  
Changing the Hostname or Domain Name of an NNMi 9.20
Management Server
To change the hostname, the domain name, or both, of the NNMi management server,
complete the following tasks:

• Task 1: Prepare the System
• Task 2: Create a New NNMi Public Key Certificate
• Task 3: Change the Fully-Qualified Domain Name of the NNMi Management
Server
• Task 4: Update the HTTPS Configuration with the New Certificate
• Task 5: Restart, Update, and Refresh Systems
• Task 6: Back up NNMi
Task 1: Prepare the System
1 Follow your standard procedure to take a complete NNMi backup.
2 Rename the system.
If necessary, reboot the system. The ovjboss process might not start completely.
3 If the IP address of the NNMi is also changing, complete the steps in Changing
the IP Address of a Standalone NNMi Management Server on page 324.
4 Stop ovjboss:
ovstop ovjboss
5 Change to the directory that contains the NNMi certificates:
• Windows: %NnmDataDir%\shared\nnm\certificates
• UNIX: $NnmDataDir/shared/nnm/certificates
6 For backup purposes, save copies of the following files:
• nnm.keystore
• nnm.truststore
Task 2: Create a New NNMi Public Key Certificate
Create a new certificate for this NNMi management server in the nnm.keystore file.
The next time that the ovjboss process starts successfully, NNMi updates the database
access to use the new certificate.
1 Change to the directory that contains the NNMi certificates:
• Windows: %NnmDataDir%\shared\nnm\certificates
• UNIX: $NnmDataDir/shared/nnm/certificates
Run all commands in this procedure from the certificates directory.
2 Generate a new public/private key pair (certificate) in the keystore by running the
following command:
• Windows:
%NnmInstallDir%\nonOV\jdk\b\bin\keytool -genkey \
-alias "<unique_alias>" -keyalg rsa
-dname "cn=<hostname>, dc=<domain_name_by_parts>" \
-keypass "nnmkeypass" -validity 36500 \
-keystore nnm.keystore -storepass "nnmkeypass"
• UNIX:
$NnmInstallDir/nonOV/jdk/b/bin/keytool -genkey \
-alias "<unique_alias>" -keyalg rsa
-dname "cn=<hostname>, dc=<domain_name_by_parts>" \
-keypass "nnmkeypass" -validity 36500 \
-keystore nnm.keystore -storepass "nnmkeypass"
Replace <alias> with a unique value such as the new hostname of the NNMi
management server, for example: newnnmi
Replace <hostname> with the new fully-qualified domain name of the NNMi
management server, for example: newnnmi.servers.example.com
Replace dc=<domain_name_by_parts> with the individual components of the new
domain in which the NNMi management server resides. For example, for the
NNMi management server newnnmi.servers.example.com, specify:
dc=servers, dc=example, dc=com
For more information about the keytool command, search for “Key and Certificate
Management Tool” at java.sun.com.
Task 3: Change the Fully-Qualified Domain Name of the NNMi Management Server
To set NNMi to use the new fully-qualified domain name of the NNMi management
server, use the nnmsetofficialfqdn.ovpl command. For example:
nnmsetofficialfqdn.ovpl newnnmi.servers.example.com
For more information, see the nnmsetofficialfqdn.ovpl reference page, or the UNIX
manpage.
Task 4: Update the HTTPS Configuration with the New Certificate
Configure the Tomcat server by editing the following file:
$jboss.home.dir/server/nms/deploy/jboss-web.deployer/server.xml
The default value of $jboss.home.dir is as follows:
• Windows: %NnmInstallDir%\nonOV\jboss\nms
• UNIX: $NnmInstallDir/nonOV/jboss/nms
If the NNMi web server uses the HTTPS protocol, update the HTTPS configuration by
following these steps:
1 Open the server.xml file in any text editor.
2 In the uncommented https connector block, change the value of the keyAlias
parameter to match the alias value you used for the new certificate in Task 2:
Create a New NNMi Public Key Certificate.
3 Save the server.xml file.
Task 5: Restart, Update, and Refresh Systems
1 Start ovjboss:
ovstart ovjboss
2 Update the connectivity between the NNMi management server and any
NNM iSPIs running on dedicated servers to use the new fully-qualified domain
name of the NNMi management server.
3 Update the connectivity between the NNMi management server and any
integrated applications to use the new fully-qualified domain name of the NNMi
management server.
If necessary, update the single sign-on configuration for the integrated application
to trust the new NNMi certificate.
4 If the NNMi database contains any encrypted data (such as SNMPv3
passphrases), this data was encrypted with the old security key. The new security
key cannot decrypt the data. Contact your support representative for assistance
deleting and recreating these configuration items.
Task 6: Back up NNMi
Follow your standard procedure to take a complete NNMi backup. Restoring NNMi from a backup made before changing the name of the NNMi management server overwrites the nnm.keystore file, thereby making the NNMi database inaccessible!

No comments:

Post a Comment