HP NonStop G-Series - Manual (Page 104)

Appendix G: Transporting Thresholds 104
d.
Enter the OVNM license key.
Hit for .
You should have a separate license key for the remote node. It is possible that if you are evaluating the
product, you will use the same key for all nodes. The response to this prompt must be 20 characters. If
you want to use the current key for the new system as well, just press the key.
e.
Enter the TCP/IP process name to be used for Elink.
Hit for $xxxx.
The utility will pick up the TCP/IP process from the OVNM database specified in the first prompt. If you
want to keep that value for the duplicated database, you can just press the enter key. Otherwise, enter
the name of the TCP/IP process that will be used for the communication between the HP NonStop node
and the workstations.
f.
Enter the port number to be used for Elink.
Hit for 9999.
The utility will pick up the port number from the OVNM database specified in the first prompt. If you
want to retain the value for the duplicated database, you can just press the enter key. Otherwise, enter
the new port number that will be used for the communication between the HP NonStop node and the
workstations.
The port number must be a value from 5000 to 10000.
This utility will:
• Dup Files from $vol.subvol to \remote.$vol.subvol.
• Change node name references to \remote.
• Use the same TCP process name ($xxxx). (Or Change TCP process from $xxxx to $yyyy.)
• Use the same port (9999). (Or Change the port number from 9999 to 8888.)
• Use the same license key (<current key>). (Or Change the license key from to
.)
g.
If everything is correct, enter YES.
Otherwise, enter the number of the item you want to change.
Once you have responded to all of the prompts, the utility will display this information for you to review
and approve before actually doing anything. If all of the information is correct, you will enter “yes”. If
you want to change something, enter the number of the item you want to change. The utility will keep
displaying the information above until you enter “yes”.
The utility creates a new database and the process completes with the display of a few messages.
NOTE: The MOVEDB utility will DUPLICATE all the files from the sending node to the receiving node and the
version of the software running on the sending node will be installed on the receiving node. This utility is NOT
the best way to duplicate thresholds from node to node. With OVNM 5.0, this function can be performed
effectively using the Object Configuration Client (OCC).
NOTE: MOVEDB supports relocation of the OVNM database from one subvolume to another on the same
node.
The PLUGPLAY thresholds will not be transported correctly to the new location due to the changes in LDEV
number. Therefore, after running the MOVEDB utility, all of these thresholds will show as in violation. The
workaround is to delete and add PLUGPLAY thresholds again.
A
pp
en
di
x G