3Com Traffix Transcend Traffix Manager User Manual page 118

118 A A: T
PPENDIX ROUBLESHOOTING
Table 17 Diagnosing Reporting Problems (continued)
Problem
Reports take very long
time to run.
Scheduled reports do
not run.
Ad hoc reports appear
as pending but never
run.
HTML files are not
deleted.
Reports do not contain
as much data as
expected.
(continued)
T M
RAFFIX ANAGER
Cause Solution
Reports using large
amounts of data can
take some time to
complete.
Traffix Manager Run the Traffix Control Panel to check the status of the Traffix
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.
The reporting The reporting processes will not start generating ad hoc reports
processes are busy until the report they are currently generating is complete. If there
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
Report Manager is The Report Manager does not delete reports while busy running
busy running reports. other reports. When the running reports are complete, the HTML
files will be removed.
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 In a connection report, you may have selected a DNS layer which
connection report is is too deep to match any of the conversations that would
too deep to match any otherwise contribute to the report. This type of problem may also
traffic. occur with other grouping schemes. Read the generated title of
the connection report carefully to check that it is sensible.
Speed up ad hoc report generation by generating reports for
fewer numbers of devices, groups, protocols or segments.
Schedule reports to run overnight rather than running ad hoc
reports.
Use the graphing tools provided from the main window to get
information quickly. The main window is more suitable for
real-time analysis of data. See
Graphs".
Reduce the number of devices in the Map using the
Aggregator. See Appendix
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.
"Monitoring Report Generation and Output"
Chapter 8, "Displaying Traffic in
C, "Aggregating Devices".
on page 96.