
118APPENDIX A: TROUBLESHOOTING TRAFFIX MANAGER
Table 17 Diagnosing Reporting Problems (continued)
Problem | Cause | Solution |
|
|
|
Reports take very long | Reports using large | ■ Speed up ad hoc report generation by generating reports for |
time to run. | amounts of data can | fewer numbers of devices, groups, protocols or segments. |
| take some time to | ■ Schedule reports to run overnight rather than running ad hoc |
| complete. | |
| reports. | |
|
| |
|
| ■ Use the graphing tools provided from the main window to get |
|
| information quickly. The main window is more suitable for |
|
| |
|
| Graphs”. |
|
| ■ Reduce the number of devices in the Map using the |
|
| Aggregator. See Appendix C, “Aggregating Devices”. |
|
| ■ Activity reports run more quickly than Top N reports. If you |
|
| have established a set of devices or groups which you are |
|
| particularly interested in, create an activity report which covers |
|
| just those devices or groups. |
|
|
|
Scheduled reports do | Traffix Manager | Run the Traffix Control Panel to check the status of the Traffix |
not run. | processes are not | Service. If the Traffix Service is not running, start it. |
| running. | Note that the Traffix Control Panel can only be run directly on the |
|
| |
|
| server. |
|
|
|
Ad hoc reports appear | The reporting | The reporting processes will not start generating ad hoc reports |
as pending but never | processes are busy | until the report they are currently generating is complete. If there |
run. | generating another | is a queue of reports waiting to be run, it may take some time |
| report. | before the ad hoc report is run. Use the Report Manager to see |
|
| which report is currently running. |
|
| You do not need to keep the Run Now progress window open. |
|
| You can request several ad hoc reports at one time and leave |
|
| them running overnight. Use the Report Manager and output |
|
| queue to see when your report is complete. |
|
| See “Monitoring Report Generation and Output” on page 96. |
|
|
|
HTML files are not | Report Manager is | The Report Manager does not delete reports while busy running |
deleted. | busy running reports. | other reports. When the running reports are complete, the HTML |
|
| files will be removed. |
Reports do not contain as much data as expected.
Protocol filter was | Check if you set up protocol filtering on the report. |
enabled on report. |
|
|
|
Internal traffic | Some reports have Internal, External and Overall traffic |
selected. | options. You are unlikely to see any Internal traffic on any |
| network except your own. |
DNS layer selected for connection report is too deep to match any traffic.
In a connection report, you may have selected a DNS layer which is too deep to match any of the conversations that would otherwise contribute to the report. This type of problem may also occur with other grouping schemes. Read the generated title of the connection report carefully to check that it is sensible.
(continued)