Monitoring System Log Messages
This topic applies only to the J-Web Application package.
Use the monitoring functionality to filter and view system log messages for EX Series switches.
To view events in the J-Web interface, select Monitor > Events and Alarms > View Events.
Apply a filter or a combination of filters to view messages. You can use filters to display relevant events. Table 1 describes the different filters, their functions, and the associated actions.
To view events in the CLI, enter the following command:
Table 1: Filtering System Log Messages
System Log File
Specifies the name of a system log file for which you want to display the recorded events.
Lists the names of all the system log files that you configure.
By default, a log file, messages, is included in the /var/log/ directory.
To specify events recorded in a particular file, select the system log filename from the list— for example, messages.
Select Include archived files to include archived files in the search.
Specifies the name of the process generating the events you want to display.
To view all the processes running on your system, enter the CLI command show system processes.
For more information about processes, see the Junos OS Installation and Upgrade Guide.
To specify events generated by a process, type the name of the process.
For example, type mgd to list all messages generated by the management process.
Specifies the time period in which the events you want displayed are generated.
Displays a calendar that allows you to select the year, month, day, and time. It also allows you to select the local time.
By default, the messages generated during the last one hour are displayed. End Time shows the current time and Start Time shows the time one hour before End Time.
To specify the time period:
Specifies the event ID for which you want to display the messages.
Allows you to type part of the ID and completes the remainder automatically.
An event ID, also known as a system log message code, uniquely identifies a system log message. It begins with a prefix that indicates the generating software process or library.
To specify events with a specific ID, type the partial or complete ID— for example, TFTPD_AF_ERR.
Specifies text from the description of events that you want to display.
Allows you to use regular expressions to match text from the event description.
Note: Regular expression matching is case-sensitive.
To specify events with a specific description, type a text string from the description with regular expression.
For example, type ^Initial* to display all messages with lines beginning with the term Initial.
Applies the specified filter and displays the matching messages.
To apply the filter and display messages, click Search.
Resets all the fields in the Events Filter box.
To reset the field values that are listed in the Events Filter box, click Reset.
Generate Raw Report
Generates a list of event log messages in nontabular format.
To generate a raw report:
Note: Starting in Junos OS Release 14.1X53, a Formatted Report can be generated from event log messages being loaded in an Events Detail table.The Generate Report button appears only after event log messages are completely loaded in the Events Detail table. The Generate Raw Report button is displayed while event log messages are being loaded.
Generates a list of event log messages in tabular format, which shows system details, events filter criteria, and event details.
To generate a formatted report:
Table 2 describes the Event Summary fields.
By default, the View Events page in the J-Web interface displays the most recent 25 events, with severity levels highlighted in different colors. After you specify the filters, Event Summary displays the events matching the specified filters. Click the First, Next, Prev, and Last links to navigate through messages.
Table 2: Viewing System Log Messages
Displays the name and ID of the process that generated the system log message.
The information displayed in this field is different for messages generated on the local Routing Engine than for messages generated on another Routing Engine (on a system with two Routing Engines installed and operational). Messages from the other Routing Engine also include the identifiers re0 and re1 that identify the Routing Engine.
Severity level of a message is indicated by different colors.
A severity level indicates how seriously the triggering event affects switch functions. When you configure a location for logging a facility, you also specify a severity level for the facility. Only messages from the facility that are rated at that level or higher are logged to the specified file.
Displays a code that uniquely identifies the message.
The prefix on each code identifies the message source, and the rest of the code indicates the specific event or error.
The event ID begins with a prefix that indicates the generating software process.
Some processes on a switch do not use codes. This field might be blank in a message generated from such a process.
An event can belong to one of the following type categories:
Displays a more detailed explanation of the message.
Displays the time at which the message was logged.