Configuring System Logging for Services Interfaces

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

You specify properties that control how system log messages are generated for the interface as a whole. If you configure different values for the same properties at the [edit services service-set service-set-name] hierarchy level, the service-set values override the values configured for the interface. For more information on configuring service-set properties, see Configuring System Logging for Service Sets.

To configure interface-wide default system logging values, include the syslog statement at the [edit interfaces interface-name services-options] hierarchy level:


            
               syslog {
               
               
                  
                     host hostname {
                     
                     services severity-level;
                     
                     facility-override facility-name;
                     
                     log-prefix prefix-value;
                     
                     }
                  
               
               }

Configure the host statement with a hostname that specifies the system log target server. The hostname local directs system log messages to the Routing Engine. For external system log servers, the hostname must be included in inet.0. You can specify only one system logging hostname.

Table 16 lists the severity levels that you can specify in configuration statements at the [edit interfaces interface-name services-options syslog host hostname] hierarchy level. The levels from emergency through info are in order from highest severity (greatest effect on functioning) to lowest.

Table 16: System Log Message Severity Levels

Severity Level	Description
any	Includes all severity levels
emergency	System panic or other condition that causes the routing platform to stop functioning
alert	Conditions that require immediate correction, such as a corrupted system database
critical	Critical conditions, such as hard drive errors
error	Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels
warning	Conditions that warrant monitoring
notice	Conditions that are not errors but might warrant special handling
info	Events or nonerror conditions of interest

We recommend setting the system logging severity level to error during normal operation. To monitor PIC resource usage, set the level to warning. To gather information about an intrusion attack when an intrusion detection system error is detected, set the level to notice for a specific interface. To debug a configuration or log Network Address Translation (NAT) functionality, set the level to info.

For more information about system log messages, see the JUNOS System Log Messages Reference.

To use one particular facility code for all logging to the specified system log host, include the facility-override statement at the [edit interfaces interface-name services-options syslog host hostname] hierarchy level:


            
               facility-override facility-name;

The supported facilities include authorization, daemon, ftp, kernel, user, and local0 through local7.

To specify a text prefix for all logging to this system log host, include the log-prefix statement at the [edit interfaces interface-name services-options syslog host hostname] hierarchy level:


            
               log-prefix prefix-value;

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]