| 5.3 |  | Monitoring with Logging and Syslog |
| 5.3.4 |  | Limiting the error message severity level |

| The administrator can limit the number of messages displayed to the selected device by specifying the severity level of the error message. To do so, use the following commands in global configuration mode . To change level and table size defaults, use the commands shown in figure .

The logging console command limits the logging messages displayed on the console terminal to messages with a level number at or below the severity level, which is specified by the level command option. The no logging console command disables logging to the console terminal.

The default is to log messages to the console at the debugging level and those level numbers that are lower, which means all levels. The logging monitor command defaults to the debugging level also. The logging trap command defaults to the informational level.

To display logging messages on a terminal, use the terminal monitor command.

If syslog message traps to be sent to a Simple Network Management Protocol (SNMP) network management station have been enabled with the snmp-server enable trap command, the level of messages sent and stored in a history table on the router can be changed if desired. The number of messages stored in the history table can be changed as well.

Messages are stored in the history table because SNMP traps are not guaranteed to reach their destinations. By default, warning level messages and greater are stored in the history table if syslog traps are not enabled.

Current software generates the following four other categories of error messages :

1. Error messages about software or hardware malfunctions, displayed at levels warnings through emergencies
2. Output from the

debug commands, displayed at the debugging level
- Interface up/down transitions and system restart messages, displayed at the notifications level
- Reload requests and low-process stack messages, displayed at the informational level