Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Using Nonstandard System Log Messages to Trigger Event Policies

Some of the system log messages that you can reference in an event policy are not listed in the output of the set event-options policy policy-name events ? command. These system log messages have an event ID and a message attribute. Event IDs are based on the origin of the message, as shown in Table 1.

Table 1: Event ID by System Log Message Origin

Event IDs

Origin

SYSTEM

Messages from Junos daemons and utilities

KERNEL

Messages from the Junos kernel

PIC

Messages from physical interface cards (PICs)

PFE

Messages from the Packet Forwarding Engine

LCC

On a TX Matrix router, messages from a line-card chassis (LCC)

SCC

On a TX Matrix router, messages from a switch-card chassis (SCC)

To base your event policy on the event types shown in Table 1, include the events event-id statement and the attributes-match statement with the event-id.message matches "message" attribute at the [edit event-options policy policy-name] hierarchy level:

[edit event-options policy policy-name]events event-id;attributes-match {event-id.message matches "message";}

For a configuration example, see Example: Using Nonstandard System Log Messages to Trigger an Event Policy.

Published: 2012-11-05

Published: 2012-11-05