Configuring Media Flow Controller Service Logs (CLI)
227
Media Flow Controller Administrator’s Guide
Configuring and Using Media Flow Controller Logs and Alarms
otherwise indicated, this procedure applies to the accesslog, cachelog, errorlog,
fmsaccesslog, fmsedgelog, fuselog, streamlog, and tracelog (“<*>log” = any service log).
Tip!
You can schedule automatic uploads of completed logs with the <*>log copy command.
A completed log is one that has reached its set filesize-MB (default is 100). Only completed
logs can be uploaded with <*>log copy; to see logs more frequently you could reduce the
maximum filesize with this command <*>log filesize-MB 1. In that way, after a log reaches 1
megabyte (rather than the default 100 megabytes) it uploads automatically to the set URL.
Tip!
If this Media Flow Controller is going to be managed by a CMC server, set the auto-
upload URL to the address of the CMC server and the filepath to /log.
1.
Disable the log (these logs are enabled by default) and enable the log.
no <*>log enable
<*> log enable
2.
Change the default log name, <logfile>.#.yyyymmdd_hour:min:sec, numbered
sequentially by creation time.
<*>log filename <new_name>.log
3.
Change the log format (accesslog and streamlog only). See
accesslog format
Options
, and
streamlog format Options
for details. Add %N for namespace name to be
added to the output.
<*>log format <field1 field2 ...>
4.
Change the log level or module; only for errorlog. The level determines how many
messages are logged; the higher the number (7 is highest) the more messages, default is
1. The module focuses the errorlog, default is any (0x00FFFFFFFFFFFFFF). See
errorlog level Options
and
errorlog module Options
for CLI details.
errorlog level 2
errorlog module
0x00FFFFFFFFFFFFFF
5.
Set automatic rotating of service logs based on log filesize-MB or time-interval. If you set
the copy option, when the log reaches its set filesize-MB (in megabytes), or the set time-
interval, it is copied to the specified machine via SCP (an SCP server must be installed
on the target machine). First set the copy destination, then set the rotate criteria. If you do
not set a copy destination, the rotated log is deleted.
<*>log copy <SCP>
<*>log rotate
{filesize-MB <integer> | time-interval <minutes>}
6.
Enable hourly log rotation, same as setting rotate time-interval 60.
accesslog on-the-hour {disable | enable}
7.
Merge log entries with syslog entries, making them available through the Web interface
System Logs page.
<*>log syslog replicate enable
8.
Restart the log service.
service restart mod-log
9.
Upload the current service log.
upload <*>log {current | all} <scp://
username[:<password>]@<hostname><path>
Содержание MEDIA FLOW CONTROLLER 2.0.4 -
Страница 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Страница 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Страница 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Страница 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Страница 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Страница 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...