Table of Contents
Advertisement
Configuring and Using Media Flow Controller Logs and Alarms
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 Web interface, 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.
Media Flow Controller System Logging Overview
The system log (syslog) that records all system activity such as user logins, configuration
changes, and system condition changes. It does not record service activity or errors. The
Media Flow Controller errorlog records service related errors but is mostly useful for
debugging by Juniper Networks Support. Media Flow Controller provides several service-
specific logs, detailed in
Specify, on a global or local level, what system data is collected when; when log files are
deleted, or rotated; where log files are uploaded to; the format for logs; what traps are sent to
syslog; and whether or not to accept log messages from remote servers. See
details.
•
"System Log Severity Levels and Classes" on page 228
•
"Configuring Media Flow Controller System Logging (CLI)" on page 229
System Log Severity Levels and Classes
The logging commands provide pre-defined log severity levels so you can refine what
messages are logged, and pre-defined log classes that divide messages up according to their
origin. Logging severity-level options are:
•
emerg
•
alert
•
—Critical conditions (requires immediate action)
crit
•
—Error conditions (minor issue; for example, "disk went bad")
err
•
warning
•
notice
228
Media Flow Controller System Logging Overview
Chapter 9, "Media Flow Controller Troubleshooting."
—System is unusable (requires immediate action)
—System may become unusable (requires immediate action)
—Warning conditions (functionality OK, but sub-optimal)
—Normal but significant conditions (default)
Media Flow Controller Administrator's Guide
Copyright © 2010, Juniper Networks, Inc.
logging
for CLI
Advertisement
Chapters
Table of Contents
Troubleshooting
