|
|
|
|
Traverse components are started and stopped using the <TRAVERSE_HOME>/etc/traverse.init script. You should execute this script with the start parameter from /etc/rc.local or another startup directory relevant to your operating system. This enables Traverse components to start automatically when the system starts.
Before you can use the script, you must edit the script and uncomment the components you want to operate on the server. For example, if you are operating the Web Application and DGE monitor components on the same host, edit traverse.init as follows:
PROVDB="N"
BVEAPI="N"
WEBAPP="Y"
MESSAGE="Y"
DGE="Y"
SLAMGR="Y"
Each Traverse component has its own startup script. This allows you to start and stop individual components. The scripts are in the <TRAVERSE_HOME>/etc directory and are described in the following table:
Traverse Service Start/Stop Scripts
Script Name |
Description |
|
Traverse BVE API |
|
Traverse Correlation & Summary Engine |
|
Traverse Data Gathering Engine |
|
Traverse File Synchronization Server |
|
Traverse Flow Analysis Engine |
|
Traverse Internal Communication Bus |
|
Traverse Message Handler |
|
Traverse Network Configuration Management |
|
Traverse Performance and Event Database |
|
Traverse Provisioning Database |
|
Traverse Remote Access Gateway |
|
Traverse Service Level Assurance Manager |
|
Traverse Web Application |
|
(shell script to start/stop Traverse components) |
Each of these scripts starts and stops with the start and stop command line option.
To start Traverse, execute the following command:
sh# /etc/init.d/traverse.init start
If you start Traverse by starting individual services, make sure you start the Provisioning Database first. This is because all other Traverse components request configuration information from the Provisioning Database during startup.
Start the DGE database and monitors after the Provisioning Database. They provide the status of all configured devices and tests. Then, start the Web Application, followed by the BVE socket server.
To stop Traverse, execute the following command:
% <TRAVERSE_HOME>/etc/traverse.init stop
When shutting down Traverse by shutting down individual components, make sure you shut down the components in the opposite order they are required to be started as described above.
If you want to stop the components of Traverse that read configuration files (so that they can read the configuration files again), execute the following command:
% <TRAVERSE_HOME>/etc/traverse.init stopcore
This command does not stop the databases or the messaging bus.
Note: After you shut down the Provisioning Database, wait at least 10 to 20 seconds before attempting to start Provisioning Database. If you attempt to restart the Provisioning Database too soon, the startup scripts inform you that the Poet database is unable to start-up properly.
Verifying Proper Operation
Use the status parameter with the traverse.init script to display the status of the different components. For example:
./traverse.init status
performance and event database ... running
internal communication bus ... running
central configuration database ... running
configuration file synchronization server ... running
network configuration management ... running
correlation and summary engine ... running
dge (monitor) components ... running
traffic flow analysis engine (flowqueryd) ... running
remote access gateway (dropbear) ... running
application server (tomcat) ... running
messages and alarm receiver ... running
Alternatively, you can use status parameter with other startup scripts to check the status of individual components.
Troubleshooting Traverse Startup
See the following Kaseya community page articles if you cannot verify proper operation.