Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Руководство администратора

Страница: 226 / 400

Configuring and Using Media Flow Controller Logs and Alarms Media Flow Controller Administrator’s Guide
226 About Log Rotation Copyright © 2010, Juniper Networks, Inc.
Viewing the Trace Log
To view the Media Flow Controller trace log:
•
Web interface—Media Flow Controller trace log entries are available for viewing on the
Web interface Trace Logs page.
•
CLI—To upload a trace log, run upload tracelog scp://<URL>. Now you can access the
trace log at the specified system, move it (if needed) and view its contents. See
“Terminology” on page 30 for the scp URL format and requirements.
About Log Rotation
All Media Flow Controller service logs offer log rotation options. It is important to remember
that log rotation parameters are checked only when activity is written to the log. If no activity,
or very widely spaced activity, is being written to the log, the rotation setting may appear to not
be honored. For example, if cachelog on-the-hour enable is set, and data is written to the
cachelog at 1pm and no data is written to it again until 6:30pm, the rotation happens as soon
as data is written to it, in this case 6:30pm; if logging continues, rotation happens again at 7pm
and so on.
Note! Log on-the-hour enable and rotate time-interval 1 both set log rotation to every hour;
the on-the-hour setting takes precedence, if you set both. You cannot set time-interval to
less than 1 (hour). Additionally, if you set on-the-hour enable and filesize-MB, the filesize-
MB setting takes precedence; should this happen between hours, the log is also rotated on
the hour (if active).
Configuring Media Flow Controller Service Logs (CLI)
Most Media Flow Controller logs, allow you to enable/disable, copy (automatically), set filesize
(for auto-copy), set filename, set format/field options, and set syslog replication. See
“Media
Flow Controller System Logging Overview” on page 228 for details on syslog options. Unless
"[SesID: %s] Request to fetch internal meta file %s
issued" SmoothFlow trace; the internal meta file request was
issued.
"[SesID: %s] SmoothFlow assets/metadata
missing. Try to deliver regular file %s" SmoothFlow trace; the meta file or some requested
assets were not found, the default regular file will be
delivered instead.
"[SesID: %s] SmoothFlow AFR Set: %d Bytes/sec" SmoothFlow trace; assured-flow rate is set to given
value.
"[SesID: %s] SmoothFlow AFR request failed: %d.
Please check if network connection max bw is
limiting AFR" SmoothFlow trace; assured-flow rate request failed,
possibly due to a lack of network bandwidth.
"AFR Failed, b/w unavailable" Assured-flow rate could not be met due to lack of
available bandwidth.
Table 16 Delivery Protocol HTTP Trace Points (Continued)
Trace Point Description