-
Troubleshooting: Unable to collect PDH data
PROBLEM: Unable to collect PDH data All PDH tests to a specific device start reporting "Unable to collect PDH data". Other regular WMI test monitoring to the device is not impacted. RESOLUTION: * Perform a manual test discovery. From experience, we have seen this rectify the issue. Please navigate to Administration -->…
-
Troubleshooting: Data Gathering Engine component does not remain in running state
PROBLEM: Data Gathering Engine component does not remain in running state CAUSE: Not all network packets from DGE(x) reach the BVE server. The issue of dropped packets can be viewed by capturing a packet dump at BVE and DGE(x) end simultaneously and then open it in Wireshark tool. Log entries similar to the below will also…
-
Requesting a xml rules file for syslog entries from a device
QUESTION: How do I request a Syslog xml rules file? PROBLEM: To allow syslog entries to be displayed intelligibly, and to associate the proper priority, a rules file is generally created. You may read up more about rules files under the chapter "Message Handler for Traps and Logs"…
-
Duplicate tests are provisioned
PROBLEM: Duplicate tests are provisioned RESOLUTION: Should you notice that duplicate tests are being provisioned, note the sub-types (a.k.a. categories) of these tests. Review the signature files under both 'TRAVERSE_HOME\plugin' and 'TRAVERSE_HOME\etc\typedef' to determine if these sub-types are defined in more than one…
-
How to pass special characters in REST commands?
QUESTION: How to pass special characters in REST commands RESOLUTION: Occasionally it may be necessary to include 'special' characters within REST commands that would otherwise be interpreted as meta-data. This may be done by substituting the URL character code in place of the character itself. For example, the following…
-
Troubleshooting: Reviewing all incoming syslog data
PROBLEM: Syslog data that is not matched by a rule will not be displayed in the logs by default RESOLUTION: The rules source file has a tag <logunmatched>. This needs to be set to true. NOTE: When troubleshooting is completed, please ensure that <logunmatched> is set back to false Details: * It is recommended that changes…
-
How to install a Traverse patch
QUESTION: How may I install an emergency Traverse patch provided by Kaseya Support? RESOLUTION: Note: This example uses Windows path notation. Note: This examples uses traverse-9.3.jar. Your release number and patch file name may be named differently. Substitute the appropriate file name in place of traverse-9.3.jar in the…
-
Purpose of exporting a device or tests to another department
QUESTION: What is the purpose of exporting a device or tests to another department? RESOLUTION: Exporting one or more tests to another department allows the result/status to be shared across departments while only polling the metric (test) once. Also, only a single device entitlement is consumed. One example where this…
-
Troubleshooting: Testing connectivity to 7651
QUESTION: Do I have connectivity to the BVE on port 7651? SOLUTION: * With a client such as putty, connect to the BVE on port 7651. Wait for a couple minutes. If you are greeted with a timeout message as below, it implies the DGEX does not have connectivity to the BVE No timeout message indicates successful connectivity.…
-
Troubleshooting: Traverse CMR support
QUESTION: What files and logs to provide to troubleshoot Traverse CMR issues? RESOLUTION: From the DGEX receiving the CMR records, * please zip and attach the logs to the ticket * please identify the device and tests in question * please zip and attach TRAVERSE_HOME/utils/spool/cmr/input to the ticket * please run this…