Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
- Administer the NNM iSPI Performance for Traffic
- Initial Configuration of the iSPI Performance for Traffic
- Configure Threshold to Monitor Traffic Flow
- Manage the NNM iSPI Performance for Traffic
- Manage Securities
- Tune the NNM iSPI Performance for Traffic
- Maintain Reports
- Maintain the NNM iSPI Performance for Traffic
- NNM iSPI Performance for Traffic Logging
- Deploy NNM iSPI Performance in GNM
Maintain the NNM iSPI Performance for Traffic
This topic includes the following sections:
The NNM iSPI Performance for Traffic enables you to back up and restore the configuration files and the embedded database on the Master Collector and Leaf Collector. This chapter explains the scripts that the NNM iSPI Performance for Traffic provides to back up and restore Master Collector and Leaf Collector database and configuration files.
This chapter also describes the changes that are required when you change the hostname of the NNMi management server, Master Collector, Leaf Collector, or NPS.
Upgrade the Operating System of the Collector Systems
Before you perform an in-place operating system upgrade of Leaf Collector and Master Collector systems, stop the collector processes.
On the Master Collector system:
- Log on as root or administrator.
-
Run the following command to stop the collector:
On Windows
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl
On the Leaf Collector system:
- Log on as root or administrator.
-
Run the following command to stop the collector:
On Windows
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl
After the operating system upgrade is complete, run the following command to start the collectors:
-
To start the Master Collector:
On Windows
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl
-
To start the Leaf Collector:
On Windows
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl
Change Hostnames
You can change the hostname of the NNMi management server, Master Collector, Leaf Collector, and NPS. Whenever you change hostname for one of the servers, the dependent server must be made aware of the change. For example, if the hostname of the NNMi management server changes, you must update the Master Collector and NPS with the new hostname. The following sections describe the changes required when one of the hostname changes.
Change the NNMi Hostname
If you change the NNMi hostname, you must update the following NNM iSPI Performance for Traffic components:
- NNMi Extension for iSPI Performance for Traffic
- Master Collector
- Leaf Collector
On the NNMi Extension for iSPI Performance for Traffic system:
-
Log on to the NNMi management server as an administrator on Windows and as root on Linux.
-
Run the following command:
On Windows
%NnmInstallDir%\bin\nnmsetofficialfqdn.ovpl
On Linux
/opt/OV/bin/nnmsetofficialfqdn.ovpl
On the Master Collector system:
- Log on to the Master Collector system as an administrator on Windows and as root on Linux.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-master\conf or %TrafficDataDir%\nmsas\traffic-master\conf
On Linux
/var/opt/OV/nmsas/traffic-master/conf
- Open the nms-traffic-master.address.properties file with a text editor.
- Modify the value of jboss.nnm.host property to the hostname of the NNMi management server.
- Save and close the file.
- Open the nnm.extended.properties file with a text editor.
-
Modify the value of the com.hp.ov.nms.spi.traffic-master.nnm.hostname property to the hostname of the NNMi management server.
If the NNMi management server is configured for application failover, modify the value of the com.hp.ov.nms.spi.traffic-master.nnm.secondary.hostname property to the hostname of the NNMi management server and restart the Master Collector.
- Save and close the file.
-
Navigate to the following directory:
On Windows
%NnmInstallDir%\traffic-master\server\conf\ or %TrafficDataDir%\trafficmaster\server\conf\
On Linux
/opt/OV/traffic-master/server/conf/
- Open the login-config.xml file with a text editor.
-
Search for the following string:
<application-policy name="nnm">
-
Modify the hostname of the NNMi management server in the following properties:
- <login-module code="com.hp.ov.nms.as.server.security.NmsSPILoginModule"flag="sufficient"> <module-optionname="nnmAuthUrl">http://<nnmhostname>:<nnmport>/spilogin/auth</moduleoption><module-option name="password-stacking">useFirstPass</module-option></login-module>
- <login-module code="com.hp.ov.nms.as.server.security.NmsSPILoginModule"flag="sufficient"><module-optionname="nnmAuthUrl">https://<nnmsecurehostname>:<nnmsecureport>/spilogin/auth</module-option><module-option name="password-stacking">useFirstPass</moduleoption></login-module>
- Save and close the file.
-
Move the content of the following directory to a different directory path if the Master Collector is not installed on the same system as NNMi:
On Windows
%NnmDataDir%\shared\nnm\certificates
On Linux
/var/opt/OV/shared/nnm/certificates
-
Generate new certificates again using the following commands if the Master Collector is not installed on the same system as NNMi:
On Windows
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -genkey -alias <MasterFQDN>.selfsigned -keyalg rsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<MasterFQDN> -keypass nnmkeypass -validity 36500 -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.keystore" -storepass nnmkeypass
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -export -file“%TrafficDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.keystore" -alias <MasterFQDN>.selfsigned -storepass nnmkeypass
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -importcert -file“%TrafficDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.truststore" -storepass ovpass -noprompt
If the Master Collector is configured for secure communication, you must add the certificates from the NNMi management server to the nnm.truststore again. For more information, see "Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic" on page 20.
On Linux
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -genkey -alias <Master FQDN>.selfsigned -keyalg rsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<Master FQDN> -keypassnnmkeypass -validity 36500 -keystore“/var/opt/OV/shared/nnm/certificates/nnm.keystore" -storepass nnmkeypass
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -export -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.keystore" -alias <MasterFQDN>.selfsigned -storepass nnmkeypass
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -importcert -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.truststore" -storepass ovpass -noprompt
If the Master Collector is configured for secure communication, you must add the certificates from the NNMi management server to the nnm.truststore again. For more information, see "Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic" on page 20.
-
Restart the Master Collector system.
On the Leaf Collector system that is installed on the NNMi management server:
No changes are required on the Leaf Collector system when Leaf Collector is not installed on the NNMi management server.
- Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-leaf\conf
On Linux
/var/opt/OV/nmsas/traffic-leaf/conf
- Open the nms-traffic-leaf.address.properties file with a text editor.
- Modify the value of leaf.host property to the hostname of the NNMi management server.
- Save and close the file.
-
Navigate to the following file:
On Windows
%NnmDataDir%\nmsas\traffic-leaf\ or %TrafficInstallDir%\nmsas\traffic-leaf\
On Linux
/var/opt/OV/nmsas/traffic-leaf
- Open the server.properties file.
- Modify the value of java.rmi.server.hostname property to the hostname of the NNMi management server.
- Save and close the file.
- Restart the Leaf Collector system.
Change the Master Collector Hostname
If you change the Master Collector hostname, you must update the following NNM iSPI Performance for Traffic components:
- NNMi Extension for iSPI Performance for Traffic
- Master Collector
On the NNMi Extension for iSPI Performance for Traffic system:
- Log on to the NNMi management server.
-
Navigate to the following directory:
On Windows
%NnmInstallDir%\support
On Linux
/opt/OV/support
-
Run the following commands:
- nnmtwiddle.ovpl -host <nnm hostname> -port 80 -u system -p <passwd> invokecom.hp.ov.nms.topo:service=NetworkApplication removeApplication traffic
-
nnmtwiddle.ovpl -host <nnm hostname> -port 80 -u system -p <NNMi system userpasswd> invoke com.hp.ov.nms.topo:service=NetworkApplicationsetApplicationService traffic <master hostname - new one> http 12080
- nnmtwiddle.ovpl -u system -p <nnm system passwd> invokecom.hp.ov.nms.topo:service=NetworkApplication printConfiguration
-
Restart the NNMi management server.
On the Master Collector system:
- Log on to the Master Collector system.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-master or %TrafficDataDir%\nmsas\traffic-master
On Linux
/var/opt/OV/nmsas/traffic-master
- Open the server.properties file with a text editor.
- Modify the value of java.rmi.server.hostname property to the hostname of the Master Collector.
- Save and close the file.
-
Navigate to the following directory:
On Windows
%trafficinstalldir%\traffic-master\server or %nnminstalldir%\traffic-master\server
On Linux
/opt/OV/traffic-master\server
- Open the server.properties file with a text editor.
- Modify the value of java.rmi.server.hostname property to the hostname of the Master Collector.
- Save and close the file.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-master\conf or %TrafficDataDir%\nmsas\traffic-master\conf
On Linux
/var/opt/OV/nmsas/traffic-master/conf
- Open the nnm.extended.properties file with a text editor.
-
Modify the value of the com.hp.ov.nms.spi.traffic-master.spi.hostname property to the hostname of the Master Collector.
- Save and close the file.
- Move the content of the <NnmDataDir>\shared\nnm\certificates to a different directory path if the Master Collector is not installed on the same system as NNMi.
-
Generate new certificates again using the following commands if the Master Collector is not installed on the same system as NNMi:
On Windows
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -genkey -alias <MasterFQDN>.selfsigned -keyalg rsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<MasterFQDN> -keypass nnmkeypass -validity 36500 -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.keystore" -storepass nnmkeypass
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -export -file“%TrafficDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.keystore" -alias <MasterFQDN>.selfsigned -storepass nnmkeypass
- “%TrafficInstallDir%\nonOV\jdk\nnm\bin\keytool" -importcert -file“%TrafficDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%TrafficDataDir%\shared\nnm\certificates\nnm.truststore" -storepass ovpass -noprompt
If you have enabled secure communication (HTTPS) between the Master Collector and the NNMi management server, see "Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic" on page 20.
On Linux
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -genkey -alias <Master FQDN>.selfsigned -keyalg rsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<Master FQDN> -keypassnnmkeypass -validity 36500 -keystore“/var/opt/OV/shared/nnm/certificates/nnm.keystore" -storepass nnmkeypass
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -export -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.keystore" -alias <MasterFQDN>.selfsigned -storepass nnmkeypass
- “/opt/OV/nonOV/jdk/nnm/bin/keytool" -importcert -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.truststore" -storepass ovpass -noprompt
If you have enabled secure communication (HTTPS) between the Master Collector and the NNMi management server, see "Enabling Secure Communication between NNMi and the NNM iSPI Performance for Traffic" on page 20.
- Restart the Master Collector.
Change the Leaf Collector Hostname
If you change the Leaf Collector hostname, follow these steps on the Leaf Collector system:
- Log on to the Leaf Collector system.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-leaf\conf or %TrafficDataDir%\nmsas\traffic-leaf\conf
On Linux
/var/opt/OV/nmsas/traffic-leaf/conf
- Open the nms-traffic-leaf.address.properties file with a text editor.
- Modify the value of leaf.host property to the hostname of the Leaf Collector.
-
Save and close the file.
-
Navigate to the following directory:
On Windows
%NnmInstallDir%\nmsas\traffic-leaf\conf or %TrafficInstallDir%\nmsas\traffic-leaf\conf
On Linux
/opt/OV/traffic-leaf\conf
- Open the nms-traffic-leaf.address.properties file with a text editor.
-
Modify the value of leaf.host property to the hostname of the Leaf Collector.
-
Save and close the file.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-leaf or %TrafficDataDir%\nmsas\traffic-leaf
On Linux
/var/opt/OV/nmsas/traffic-leaf
- Open the server.properties file with a text editor.
- Modify the value of the java.rmi.server.hostname property to the hostname of the NNMi management server.
- Save and close the file.
-
Move the content of the following directory to a different directory path if the Leaf Collector is configured for secure communication with the Master Collector:
On Windows
%NnmDataDir%\shared\nnm\certificates
On Linux
/var/opt/OVshared/nnm/certificates
-
Generate new certificates again using the following commands if the Leaf Collector is configured for secure communication with the Master Collector:
On Windows
- “%NnmInstallDir%>\nonOV\jdk\nnm\bin\keytool" -genkey -alias <LeafFQDN>.selfsigned -keyalg rsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<LeafFQDN> -keypass nnmkeypass -validity 36500 -keystore“%NnmDataDir%\shared\nnm\certificates\nnm.keystore" -storepass nnmkeypass
- “%NnmInstallDir%\nonOV\jdk\nnm\bin\keytool" -export -file“%NnmDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%NnmDataDir%\shared\nnm\certificates\nnm.keystore" -alias <Leaf FQDN>.selfsigned-storepass nnmkeypass
- “%NnmInstallDir%\nonOV\jdk\nnm\bin\keytool" -importcert -file“%NnmDataDir%\shared\nnm\certificates\nnm.cert" -keystore“%NnmDataDir%\shared\nnm\certificates\nnm.truststore" -storepass ovpass -noprompt
If the Leaf Collector is configured for secure communication, you must import the certificates from the Leaf Collector to the nnm.truststore again. For more information, see "Enabling Secure Communication between the Master and the Leaf Collector" on page 26.
On Linux
-
“/opt/OV/nonOV/jdk/nnm/bin/keytool" -genkey -alias <Leaf FQDN>.selfsigned -keyalgrsa -sigalg SHA1withRSA -keysize 2048 -dname cn=<Leaf FQDN> -keypass nnmkeypass -validity 36500 -keystore “/var/opt/OV/shared/nnm/certificates/nnm.keystore" -storepass nnmkeypass
-
“/opt/OV/nonOV/jdk/nnm/bin/keytool" -export -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.keystore" -alias <Leaf FQDN>.selfsigned-storepass nnmkeypass
-
“/opt/OV/nonOV/jdk/nnm/bin/keytool" -importcert -file“/var/opt/OV/shared/nnm/certificates/nnm.cert" -keystore“/var/opt/OV/shared/nnm/certificates/nnm.truststore" -storepass ovpass -noprompt
If the Leaf Collector is configured for secure communication, you must import the certificates from the Leaf Collector to the nnm.truststore again. For more information, see "Enabling Secure Communication between the Master and the Leaf Collector" on page 26.
- Restart the Leaf Collector system.
- Log on to the NNMi console with the administrator privileges.
- Go to the Configuration workspace.
- Double-click NNM iSPI Performance for Traffic Configuration. The NNM iSPI Performance for Traffic form opens.
-
Log on to the NNM iSPI Performance for Traffic form with the system user account created during the installation of the Master Collector.
-
Delete the Leaf Collector instances and the Leaf Collector Systems. For more information, see the Configuring Leaf Collector Instances and the Configuring Leaf Collector Systems sections in the Network Node Manager iSPI Performance for Traffic Software Online Help.
-
Add the Leaf Collector instances and the Leaf Collector Systems. For more information, see the Configuring Leaf Collector Instances and the Configuring Leaf Collector Systems sections in the Network Node Manager iSPI Performance for Traffic Software Online Help.
Change the NPS Hostname
If you change the NPS hostname, you must update the following:
- NNMi management server
- Master Collector
On the NNMi management server:
-
Log on to the NNMi management server.
-
Navigate to the following directory:
On Windows
%NnmInstallDir%\bin
On Linux
/opt/OV/bin
- Run the nnmenableperfspi.ovpl -disable command at the command prompt.
- Run the nnmenableperfspi.ovpl command and provide the hostname when prompted.
-
Share the %NnmDataDir%\shared\perfSpi\datafiles directory again on the network for the user with the web server client role. Make sure that the user has the read/write access to this directory. For more information, see Preinstallation Tasks in the Installing the Master Collector section in the Network Node Manager iSPI Performance for Traffic Software Interactive Installation Guide.
On the Master Collector system:
- Log on to the Master Collector system.
-
Navigate to the following directory:
On Windows
%NnmDataDir%\nmsas\traffic-master\conf or %TrafficDataDir%\nmsas\traffic-master\conf
On Linux
/var/opt/OV/nmsas/traffic-master/conf
- Open the nps.extended.properties with a text editor.
-
Modify the value of the following property:
com.hp.ov.nms.spi.traffic-master.nps.hostname
- Save and close the file.
Backup and Restore Commands
The NNM iSPI Performance for Traffic provides you with the following scripts to back up and restore database and configuration files:
- nmstrafficmasterbackup.ovpl: Creates a complete backup of all the Master Collector database and configuration files.
- nmstrafficmasterresetdb.ovpl: Deletes the existing Master Collector database and recreates the Master Collector database and tables.
- nmstrafficmasterrestore.ovpl: Restores the backup that was created by using the nmstrafficmasterbackup.ovpl script.
- nmstrafficleafbackup.ovpl: Creates a complete backup of all the Leaf Collector database and configuration files.
- nmstrafficleafresetdb.ovpl: Deletes the existing Leaf Collector database and recreates the Leaf Collector database and tables.
- nmstrafficleafrestore.ovpl: Restores the backup that was created by using the nmstrafficleafbackup.ovpl script.
For more information, see the appropriate reference page.
The scripts provided by the NNM iSPI Performance for Traffic enable you to back up and restore files when NNMi and Master Collector or Leaf Collector are not installed on the same system.
Back up Master Collector
To back up the Master Collector:
- Log on to the Master Collector system as an administrator on Windows and as root on Linux.
-
Stop the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl
-
Run the following command to start the back up of Master Collector database and configuration files:
nmstrafficmasterbackup.ovpl -target <Full path of the target archived file> -scope [all|db]
In this instance, <Full path of the target archived file> is the directory where you want to store the backup file.
The option all enables you to back up the database and configuration files.
The option db enables you to back up the database only.
The backup script creates a tar file of the backup data.
-
Start the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl
Reset Master Collector Database
To reset the Master Collector database:
- Log on to the Master Collector system as an administrator on Windows and as root on Linux.
-
Stop the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl
-
Run the following command to reset the Master Collector database:
nmstrafficmasterresetdb.ovpl -start
-
Start the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl
Restore the Master Collector
Before you restore the Master Collector database, you must reset the Master Collector database as described in "Resetting Master Collector Database" above.
To restore the Master Collector database:
- Log on to the Master Collector system as an administrator on Windows and as root on Linux.
-
top the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstop.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstop.ovpl
-
Run the following command:
On Windows
<Install_Dir>\traffic-master\bin\nmstrafficmasterresetdb.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterresetdb.ovpl
-
Run the following command to restore the Master Collector configuration files and database:
nmstrafficmasterrestore.ovpl -source <Full path of the archived file to restore> -scope[all|db]
In this instance, <Full path of the archived file to restore> is the full path of the backup file that you want to restore.
Option all restores the backup of the database and configuration files. You can restore the backup using the option all only if you have previously backed up the database and configuration files using the option all in Step 3 in "Backing up Master Collector" on page 72.
Option db restores the backup of the database only. You can restore the backup using the option db only if you have previously backed up the database using the option db in Step 3 in "Backing up Master Collector" on page 72.
-
If the FQDN of the new system is different from the original Master Collector system (where you took the backup), follow the steps in "Changing the Master Collector Hostname" on page 67.
-
Start the Master Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl or
%TrafficInstallDir%\traffic-master\bin\nmstrafficmasterstart.ovpl
On Linux
/opt/OV/traffic-master/bin/nmstrafficmasterstart.ovpl
Back up Leaf Collector
To back up the Leaf Collector:
-
Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.
-
Stop the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl
-
Run the following command to start the back up of Leaf Collector database and configuration files:
nmstrafficleafbackup.ovpl -target <Full path of the target archived file> -scope [all|db]
In this instance, <Full path of the target archived file> is the directory where you want to store the backup file.
The option all enables you to back up the database and configuration files.
The option db enables you to back up the database only.
The backup script creates a tar file of the backup data.
-
Start the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl
Reset Leaf Collector Database
To reset the Leaf Collector database:
-
Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.
-
Stop the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl
-
Run the following command to reset the Leaf Collector database:
nmstrafficleafresetdb.ovpl -start
-
Start the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl
Restore Leaf Collector
Before you restore the Leaf Collector database, you must reset the Leaf Collector database as described in "Resetting Leaf Collector Database" above.
To restore the Leaf Collector database:
- Log on to the Leaf Collector system as an administrator on Windows and as root on Linux.
-
Stop the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstop.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstop.ovpl
-
Run the following command to restore the Leaf Collector configuration files and database:
nmstrafficleafrestore.ovpl -source <Full path of the archived file to restore> -scope [all|db]
In this instance, <Full path of the archived file to restore> is the full path of the backup file that you want to restore.
Option all restores the backup of the configuration files and database. You can restore the backup using the option all only if you have previously backed up the configuration files and database using the option all in Step 3 in "Backing up Leaf Collector" on the previous page.
Option db restores the backup of the database only. You can restore the backup using the option db only if you have previously backed up the database using the option db in Step 3 in "Backing up Leaf Collector" on the previous page.
-
If the FQDN of the new system is different from the original Leaf Collector system (where you took the backup), follow the steps in "Changing the Leaf Collector Hostname" on page 69.
-
Start the Leaf Collector by running the following command:
On Windows
%NnmInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl or
%TrafficInstallDir%\traffic-leaf\bin\nmstrafficleafstart.ovpl
On Linux
/opt/OV/traffic-leaf/bin/nmstrafficleafstart.ovpl
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: