Technical data

Using Syslog Messaging to Monitor Router Events
303561-A Rev 00
C-21
4.
Define how router event message severity levels and UNIX system error
levels map to one another.
In most cases, you accept the default mapping and go to Task 7. Otherwise,
continue with the following instructions to customize the message mapping.
Enter at the Technician Interface prompt the command line(s) appropriate for
the message mapping(s) you want to change:
• Change router FAULT message mapping, as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrFaultMap.
<host_IP_address> . <entity_code> . <filter_index> <1 - 8>
The default value of wfSyslogEntFltrFaultMap is 3, mapping router
FAULT level messages to UNIX system level CRIT messages.
• Change router WARNING message mapping, as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrWarningMap.
<host_IP_address> . <entity_code> . <filter_index> <1 - 8>
The default value of wfSyslogEntFltrWarningMap is 5, mapping router
WARNING level messages to UNIX system level WARNING messages.
• Change router INFO message mapping, as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrInfoMap.
<host_IP_address> . <entity_code> . <filter_index> <1 - 8>
The default value of wfSyslogEntFltrInfoMap is 7, mapping router INFO
level messages to UNIX system level INFO messages.
• Change router TRACE message mapping, as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrTraceMap.
<host_IP_address> . <entity_code> . <filter_index> <1 - 8>
The default value of wfSyslogEntFltrTraceMap is 3, mapping router
TRACE level messages to UNIX system level CRIT messages.
• Change router DEBUG message mapping, as follows:
$: set wfSyslogEntFltrEntry.wfSyslogEntFltrDebugMap.
<host_IP_address> . <entity_code> . <filter_index> <1 - 8>
The default value of wfSyslogEntFltrDebugMap is 8, mapping router
DEBUG level messages to UNIX system level DEBUG messages.