System Baseline And Health; Table 15 Syslog Severity Levels - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Log (streamlog)" on page
specific delivery situation; see
Set counter thresholds with
See logging
The System Log keeps track of all system activities, similar to syslog on a UNIX system. The
System Log provides this information, in this order:
•
Date and time
•
Media Flow Controller hostname and process name (ends with colon)
•
Process date and time, in brackets (may be missing)
•
Event information, may include severity level in brackets, see
Example:
Jan 6 00:10:00 test-vos httpd: [Wed Jan 06 00:10:00 2010] [notice] Apache configured -- resuming
normal operations
Jan 6 05:58:50 test-vos pm[4617]: [pm.NOTICE]: Output from nknlogd (Nokeena Log Manager):
Debuglog socket 17 closed
Jan 6 08:58:27 test-vos login: ROOT LOGIN ON ttyS0: user admin (System Administrator)
Table 15 Syslog Severity Levels
Level
emergency
alert
critical
error
warning
notice
info
debug

System Baseline and Health

Logging can provide more information than any one person can process during any given
moment; finding the required information can be a daunting task. This problem can be reduced
if you take time with each installed system to perform a baseline audit. A baseline audit
identifies normal activity for your system, normal system log entries, normal network traffic for
the system, and how the system reacts to certain conditions.
A baseline audit helps you get the most value from syslog data. In particular, a baseline audit
helps identify what the system was like before you became suspicious of its behavior and
helps you determine what has changed. On a day to day basis the system logs can be used to
determine network health and how well the network and computer systems are running. This
provides the ability to proactively solve issues before the user is aware.
220. The Trace Log can be used to track down problems with a
"Trace Log (tracelog)" on page 223
stats commands; set email notifications with
for CLI details. See Table
An error from which the system cannot recover/system unusable
An error requiring immediate action for operation to continue
An unexpected condition/response causing an error for unknown reasons
An unexpected condition/response causing an error for known reasons
An anomalous condition that can be ignored and functioning continue but may affect
operations
Normal but significant condition/response that could affect operations
Normal but significant condition/response that does not affect operations
Messages generated by the debugging utility
Configuring and Using Media Flow Controller Logs and Alarms
15, for severity level options.
Description
for details.
email commands.
Table 15, for levels
System Log 221