No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-How to Filter Out the Log Messages Frequently Appearing in the logbuffer

Publication Date:  2012-07-27 Views:  136 Downloads:  0

Issue Description

How to filter out the log messages frequently appearing in the logbuffer?

Alarm Information


The following log messages about the NE80E are frequently generated, which brings inconvenience for maintenance.
1. Entries about SNMP community errors: The generation of these entries may be due to the absence or errors of communities in the SNMP packets sent by users. It has been confirmed that the source addresses of these packets are in the PDSN address pool. Now, the sending of such type of packets cannot be prohibited on the PDSN side. Since the associated log messages are useless, they need to be filtered out.
Apr 13 2009 08:59:20 NE80E%%01SNMP/4/COMMUNITY_ERR(l): Failed to login through SNMP, because the community was incorrect. (Ip=113.113.X.X, Times=3)
Apr 13 2009 08:59:14 NE80E %%01SNMP/4/COMMUNITY_ERR(l): Failed to login through SNMP, because the community was incorrect. (Ip=113.113.X.X, Times=2)
Apr 13 2009 08:59:07 NE80E %%01SNMP/4/COMMUNITY_ERR(l): Failed to login through SNMP, because the community was incorrect. (Ip=113.113.X.X, Times=1)
Apr 13 2009 08:58:53 NE80E %%01SNMP/4/COMMUNITY_ERR(l): Failed to login through SNMP, because the community was incorrect. 
(Ip=113.113.X.X, Times=6)

2. Entries about unsuccessful identification of VLAN IDs: The entries may be generated when the NE80E receives tagged user packets that cannot pass through it. Therefore, it is necessary to confirm why the lower-layer device sent these packets to the NE80E. One of the possible causes is that the data configurations are improper. Since these log messages are useless, they need to be filtered out.
Apr 13 2009 09:26:50 NE80E %%01L2ADP/3/TRAP_UNKWN_VLANPKT(l): Discovered unknown VLAN packets. (IfName=GigabitEthernet10/0/0, UnknownVlanNum=271720)
Apr 13 2009 09:21:50 NE80E %%01L2ADP/3/TRAP_UNKWN_VLANPKT(l): Discovered unknown VLAN packets. (IfName=GigabitEthernet10/0/1, UnknownVlanNum=271781)
Apr 13 2009 09:21:50 NE80E %%01L2ADP/3/TRAP_UNKWN_VLANPKT(l): Discovered unknown VLAN packets.

Handling Process

To filter out a type of log messages, you can change the level of log messages allowed to be reported.
1. Run the following command to filter out the previously mentioned log messages about SNMP by changing the level of messages allowed to be reported from Warning to Error.
info-center source SNMP channel logbuffer log level Error
2. Run the following command to filter out the previously mentioned VLAN packets that are denied on the NE80E by changing the level of messages allowed to be reported from Error to Critical.
info-center source L2ADP channel logbuffer log level Critical
3. Other methods used for log message filtering are similar.
Log messages can only be filtered out through the mentioned methods. When some log messages are filtered out, other normal log messages may fail to be output in real time. Therefore, it is necessary to find the real cause of generation of these logs to eradicate any problem in the output of log 

Root Cause


A default level can be set for the reporting of log messages. The following is one command example:
info-center source default channel 2 log level warning

In this example, the default level is set to Warning, which means that only warning messages or more serious messages can be reported. You can modify the level for certain modules to control the output of log messages.