Media Flow Controller Logs : Configuring Service Logs

Configuring Service Logs
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 “System Logging Options” on page 95 for details on syslog options. Unless otherwise indicated, this procedure applies to the accesslog, cachelog, errorlog, fmsaccesslog, fmsedgelog, fuselog, streamlog, and tracelog. Note, “<*>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, once 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.
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.
accesslog on-the-hour {disable | enable}
7.
<*>log syslog replicate enable
8.
service restart mod-log
9.
upload <*>log {current | all} <scp://username[:<password>]@<hostname><path>
Example using accesslog:
test-vos (config) # no accesslog enable
test-vos (config) # accesslog enable
test-vos (config) # accesslog filename sv05accesslog.log
test-vos (config) # accesslog format %h %V %u %t %s %b %N
test-vos (config) # accesslog copy scp://joe@sv01/home/joe
Password: *******
test-vos (config) # accesslog rotate filesize-MB 75 time-interval 1
test-vos (config) # accesslog on-the-hour enable
test-vos (config) # accesslog syslog replicate enable
test-vos (config) # service restart mod-log
test-vos (config) # upload <*>log current scp://joe@sv01/home/joe
Password: *******
test-vos (config) #
To make these configurations using the Management Console, go to the Service Config tab, <*>log page. After making changes use EZconfig page Service Restart area to restart the appropriate log service. Be sure to click Apply at each section and Save at the top right of the page to make the changes persistent across reboots/restarts.
 

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.