Technical data

Using Technician Interface Software
C-8
303561-A Rev 00
You define a range of slot numbers for an entity filter by specifying:
• An upper boundary number (MIB object wfSyslogFltrSlotUppBnd)
• A lower boundary number (MIB object wfSyslogFltrSlotLowBnd)
Syslog considers the upper and lower boundary numbers as part of the range. For
example, you can configure an entity filter for FTP with an event number range of
5 to 27 and a slot number range of 2 to 5. In this case, Syslog forwards to the
associated remote host FTP log messages numbered 5 to 27 logged on slots 2 to 5
only.
You can configure a filter to select messages logged on a specific slot by setting
the upper and lower slot boundary values to the same number.
Mapping Router Event Messages into Syslog Message Format
Syslog running on each slot maps filtered event messages into Syslog message
format. For example, the following system log message:
#1: 02/07/95 16:03:18.679 INFO SLOT2 FTP Code:5
FTP is initializing.
looks as follows in Syslog format:
<AE>FTP: SLOT:2 SEVERITY:Info ENTITY_CODE/EVENT_CODE:88/5
FTP is initializing.
Figure C-3 shows how Syslog encapsulates a message into a UDP packet.
Note:
With both the upper and lower boundary attributes set to 0 (the default
value for those attributes), the filter cannot transition to the active state.