Message Control for SNMP servers

This article describes how to control some SNMP servers. Some configuration problems are involved. And log management methods. Let's take a look at the content of the article. When sending restrictions on history tables such as SNMP servers, we can use the following operations to configure.

Restrict log sending to history tables and SNMP servers

After sending the System Log message Trap to the SNMP Network Management site, you can use the "snmp-server enable trap" global configuration command to change the level of message sending and store it in the switch history table, you can also change the number of messages stored in the History Table. The message is stored in the History Table because SNMP Trap does not guarantee that each message can reach its destination. By default, a warning-level message and a low-number level message are stored in history tables, and even System Log traps are not enabled.

In Privileged EXEC mode, the following steps change the default size of the level and history table.

Step 2: Enter the global configuration mode.

Switch # configure terminal

Step 2: change the level of system log messages stored in history files and sent to the SNMP server.

Switch (config) # logging history level

Step 2: specify the number of system log messages that can be stored in the History Table.

Switch (config) # logging history size number

Step 2: return the Privileged EXEC mode.

Switch (config-if) # end

Step 2: Verify the configuration.

Switch # show running-config
 
Step 2: Save the modified configuration.

Switch # copy running-config startup-config

When the history table is full, the earliest messages are deleted from the table, allowing new messages to be stored.

Return the System log message to the default level and use the "no logging history" global configuration command. Return the number of messages in the history Table to the default value. Use the "no logging history size" global configuration command.