Technical data
Using Syslog Messaging to Monitor Router Events
303561-A Rev 00
C-27
4.
Create a wildcard filter to forward events of type fault, warning, and
debug on slots 2, 3, 4, 5:
a.
Create the filter as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrDelete.
<Host_IP_Address>
.255.1 1;commit
<Host_IP_Address>
is the address of the remote host associated with this
filter.
255 is the wildcard entity number.
1 represents the index number of the filter.
commit commits router system resources to the filter you are creating.
b.
Define the wildcard setting for filtering by event numbers.
The setting causes Syslog to ignore event numbers as a filtering criteria,
and to use instead message severity levels as a filtering criteria.
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrLogEvtLowBnd.
192.32.6.14.255.1 0
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrLogEvtUppBnd.
192.32.6.14.255.1 255
c.
Define a set of message severity levels (a “severity mask”) that causes
Syslog to select and forward only messages that have a severity level
of fault, warning, or debug.
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrSevMask.
192.32.6.14.255.1 "fwd"
The next two commands define the range of slots 2 to 4 as an additional
filtering criterion. The commands cause Syslog to select only messages
logged on slots 2 to 5.
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrSlotLowBnd.
192.32.6.14.255.1 2
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrSlotLowUpp.
192.32.6.14.255.1 4
$: commit