|
|
|
|
This section includes general troubleshooting information for both Windows and UNIX operating systems.
Log Files
Several log files can be useful in troubleshooting. All log files are located under <TRAVERSE_HOME>\logs directory.
Log File |
Used By |
|
All startup scripts, monitors |
|
Any warning, error or critical level messages generated by the application are logged in this file. |
|
Information on monitors are logged to this file as tests are performed, actions triggered, etc. |
|
All user tasks, both in the Web Application and BVE socket server are logged to this file. Tasks include create, delete, update, suspend and resume tasks performed on devices, departments, users, etc. |
|
Any errors generated inside JSP pages in the Web Application component is logged in this file. |
|
Provisioning Database specific errors |
Troubleshooting the DGE-BVE Connection
Upon startup, each DGE component connects to the Provisioning Database located on the provisioning server and downloads all tests that are configured for that DGE. The DGE components maintain a connection to the Provisioning Database at all times. As devices and tests are added, updated, or removed, the provisioning server notifies the relevant DGE of the changes in real time.
If the communications link between the Provisioning Database and the DGE is broken, the DGE repeatedly attempts to restore the connection, while continuing to monitor, using the configuration information that it has cached in memory. Once the connection to the Provisioning Database is restored, the DGE shuts down. A cron job restarts the DGE shortly thereafter. The reason for the shutdown and restart is that while the DGE was unable to communicate with the provisioning server, it may have missed notices about changes to device/test configurations. In the process of restarting, the DGE downloads a fresh copy of the list of tests and proceeds with normal operation.
Querying SNMP Devices Manually
To query SNMP devices manually, execute the following commands:
cd <TRAVERSE_HOME>
bin\snmpwalk -m "" -c public -v 2c ipAddress:port mib
Example
bin\snmpwalk -m "" -c public -v 2c 10.1.2.3 .1.3.6.1.2
cd $TRAVERSE_DIR
bin/snmpwalk -m "" -c public -v 2c ipaddr:port mib