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

Using View Events

Figure 32 shows the View Events page. This page provides an easy method to view the events recorded in the system log (also known as system log messages). By default, the View Events page displays a summary of the most recent 25 events, with severity levels highlighted in different colors.

The events summary includes information about the time the event occurred, the name of the process that generated the message, the event ID, and a short description of the event. You can move the cursor over the question mark (?) next to an event ID to display a useful description of the event.

You can select the number of events to be displayed on the screen at a time. You can also filter events by system log filename, event ID, text from the event description, name of the process that generated the event, or time period, to display only the events you want.

Alternatively, enter the following command in the J-Web CLI terminal to display the list of messages and a brief description of each message. For more information about the CLI terminal, see Using the CLI Terminal.



user@host>  help syslog ?

Figure 32: J-Web View Events Page

Image s001122.gif

Viewing Events

The View Events page displays system log messages that record events occurring on the routing platform. Events recorded include those of the following types:

Routine operations, such as creation of an Open Shortest Path First (OSPF) protocol adjacency or a user login into the configuration database
Failure and error conditions, such as failure to access a configuration file or unexpected closure of a connection to a child or peer process
Emergency or critical conditions, such as routing platform power-off due to excessive temperature

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

Understanding Severity Levels

On the View Events page, the severity level of a message is indicated by different colors. The severity level indicates how seriously the triggering event affects routing platform functions.

Table 40 lists the system log severity levels, the corresponding colors and a description of what the severity level indicates.

Table 40: Severity Levels

Color	Severity Level (from Highest to Lowest Severity)	Description
Red	emergency	System panic or other conditions that cause the routing platform to stop functioning.
Orange	alert	Conditions that must be corrected immediately, such as a corrupted system database.
Pink	critical	Critical conditions, such as hard drive errors.
Blue	error	Standard error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels.
Yellow	warning	Conditions that warrant monitoring.
Green	notice	Conditions that are not error conditions but are of interest or might warrant special handling.
	info	Informational messages. This is the default.
	debug	Software debugging messages.
Gray	unknown	No severity level is specified.

Using Filters

On the View Events page, you can use filters to display relevant events. Table 41 lists the different filters, their functions, and the associated actions. You can apply any or a combination of the described filters to view the messages that you want to view. After specifying the filter or filters you want, click OK to display the filtered events.

Table 41: Summary of Event Filters

Event Filter	Function	Your Action
System Log File	Specifies the name of a system log file for which you want to display the recorded events. The list includes the names of all the system log files that you configure. By default, a log file, messages, is included in the /var/log/ directory. For information about how to configure system log files, see the JUNOS System Log Messages Reference.	To specify events recorded in a particular file, select the system log filename from the list—for example, messages.
Event ID	Specifies the event ID for which you want to display the messages. If you type part of the ID, the system completes the remaining ID 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 its partial or complete ID—for example, TFTPD_AF_ERR.
Text in Event Description	Specifies text from the description of events that you want to display. You can use a regular expression to match text from the event description. Note: The regular expression matching is case sensitive. For more information about using regular expressions, see Using Regular Expressions.	To specify events with a specific description, type a text string from the description. You can include a regular expression. For example, type ^Initial* to display all messages with lines beginning with the term Initial.
Process	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 in the J-Web CLI terminal. For more information about processes, see the JUNOS Software 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.
Start Time End Time	Specifies the time period in which the events you want displayed are generated. A calendar allows you to select the year, month, day, and time. It also allows you to select the local time. By default, the messages generated in 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: Click the button next to Start Time and select the year, month, date, and time—for example, 02/10/2006 11:32. Click the button next to End Time and select the year, month, date, and time—for example, 02/10/2006 3:32. To select the current time as the start time, select Local Time.

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