1. Log Events

This chapter provides general information about the log events described in this guide.

For more information about log events and event logging, refer to the 7705 SAR System Management Guide.

Note:

This guide contains all log events supported by the Service Router Operating System (SR OS). Not all events are supported by the 7705 SAR.

1.1. Overview of Log Events

Log events that are forwarded to a destination are formatted in a way that is appropriate for the specific destination; for example, whether it is to be recorded to a file or sent as an SNMP trap. However, log events also have common elements or properties. All application-generated events have the following properties:

a timestamp in UTC or local time
the generating application
a unique event ID within the application
a router name identifying the VRF ID that generated the event
a subject identifying the affected object
a short text description; for further information on variables found in the message format strings, refer to the associated SNMP Notification definition in the 7705 SAR MIBs

The general format for a log event with a memory, console, or file destination is as follows.

nnnn YYYY/MM/DD HH:MM:SS.SS TZONE <severity>: <application> #<event_id> <router-

name> <subject> <message>

The following is a log event example:

252 2017/05/07 16:21:00.76 UTC WARNING: SNMP #2005 Base my-interface-abc

"Interface my-interface-abc is operational"

The specific elements that make up the general format are described in Table 1.

Table 1: Log Event Element Descriptions

Label	Description
nnnn	The log entry sequence number
YYYY/MM/DD	The UTC or local date stamp for the log entry YYYY — year MM — month DD — day
HH:MM:SS.SS	The UTC timestamp for the event HH — hours (24-hour format) MM — minutes SS.SS — seconds
TZONE	The timezone (for example, UTC, EDT) as configured by configure log log-id log-id time-format
<severity>	The severity level of the event CRITICAL MAJOR MINOR WARNING INFO CLEARED
<application>	The name of the application generating the log message
<event_id>	The application event ID number for the event
<router>	The router name representing the VRF ID that generated the event
<subject>	The subject/affected object for the event
<message>	A text description of the event

1.2. Log Event Example

Table 2 is a log event entry from this guide for the cli_config_io log event.

Table 2: cli_config_io properties

Property name	Value
Application name	L1
Event ID	2115
Event name	cli_config_io
SNMP notification prefix and OID	N/A
Default severity	minor
Message format string	User from $srcAddr$: $prompt$ $message$
Cause	A valid CLI command was entered in the configuration node.
Effect	Configuration was changed by CLI command.
Recovery	No recovery is required.

The table title for a log event entry is the event name. Each entry contains the information described in Table 3.

Note:

Not all log event entries have values in every field.

Table 3: Log Event Entry Field Descriptions

Label	Description
Application name	The name of the application generating the log message
Event ID	The application event ID number for the event
Event name	The name of the event
SNMP notification prefix and OID	The prefix and OID of the SNMP notification associated with the log event
Default severity	The default severity level of the event CRITICAL MAJOR MINOR WARNING INFO CLEARED
Message format string	A text description of the event
Cause	The cause of the event
Effect	The effect of the event
Recovery	How to recover from this event, if necessary