Viewing The Accesslog; Reading The Accesslog - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide

Viewing the Accesslog

You can schedule automatic uploads of completed accesslogs with the accesslog copy
command; a completed accesslog is one that has reached its set rotate criteria (default is
filesize-MB = 100). Only completed accesslogs can be uploaded with the accesslog
copy command, to see accesslogs more frequently you might want to reduce the
maximum filesize with this command accesslog rotate filesize-MB 1. In that way, after an
accesslog reaches 1 megabyte (rather than the default 100 megabytes) it uploads
automatically to the specified URL.
To immediately complete and upload an accesslog, run this command accesslog copy
scp://<URL>, followed by the service restart accesslog command. Now you can access
the compressed accesslog at the specified system, move it (if needed), uncompress it,
and view its contents.
The default log filename format is <logfile>.#.yyyymmdd_hour:min:sec; you can
change that with the filename command.
To view the Media Flow Controller accesslog:
Web interface—Media Flow Controller accesslog entries are available for viewing on the
Web interface Logs > Service Logs page.
CLI—To upload the accesslog, run upload accesslog {current | all} scp://<URL>.
Choose all to upload all existing accesslogs. Default is current. See
page 30

Reading the Accesslog

The accesslog (shown as Service Log in the Web interface) provides this information, in this
order (by default—the order changes if you change the accesslog format):
IP address and domain requested
Date and time, in brackets
HTTP method and path of file, in quotes
Status code (see
Bytes returned
Referrer, in quotes
Agent, in quotes
Status sub-code (see
Example:
172.19.172.192 172.19.172.130 - [04/Jan/2010:20:33:40 +0000] "GET /HNAP1/ HTTP/1.1" 404 0 "-"
"Mozilla/4.0 (compatible; MSIE 5.5; Win32)" 52004
172.19.172.192 172.19.172.130 - [04/Jan/2010:20:33:43 +0000] "GET /TEADevInfo/ HTTP/1.1" 404 0 "-"
"Mozilla/4.0 (compatible; MSIE 5.5; Win32)" 52004
172.19.172.192 172.19.172.130 - [04/Jan/2010:20:33:46 +0000] "GET / HTTP/1.0" 404 0 "-" "Mozilla/
4.0 (compatible; MSIE 5.5; Win32)" 52004
for the scp URL format and requirements.
"Logging Status (%s) Codes" on page
"Logging Status Sub-Codes" on page
Configuring and Using Media Flow Controller Logs and Alarms
"Terminology" on
210)
211)
Service Log (accesslog)
213

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents