Hi,
I've seen those messages in syslog -- when it works. Many of our C3s
(06.42.03.0004) take the habit of just stopping logging after being up 6
weeks or so. But that's another issue.
Let's take a trap from tonight:
Wed Sep 14 00:01:48 2011 Status Events X authenticationFailure
The logging buffer doesn't say anything either although logging level is
debug:
->show logging application
Application Current Severity Level
---------------------------------------------
89 CLIWEB 8
90 SNMP 8
-> show logging buffer
<165>Aug 29 01:54:59 x-1 SIM[192959408]: sntp_client.c(1389) 18715992 %%
SNTP has changed system time.
<165> SEP 07 05:06:08 x-2 SIM[139626200]: osapi.c(3164) 195 %% Stack
manager has changed system time.
<165> SEP 07 05:06:09 x-2 SIM[139626200]: osapi.c(3165) 196 %% Stack
manager has changed system time.
--More-- <space> next page, <cr> one line, <q> quit
<165>Sep 7 08:42:12 x-1 USER_MGR[1]: 19916366 %% User:rw logged in from
y(telnet)
<165>Sep 7 08:44:57 x-1 USER_MGR[1]: 19916433 %% User:admin logged in
from y(telnet)
In the end it's probably some monitoring app gone wild I agree.
> Just set the logging application for SNMP to 8, you will then see the
> source.
>
> set logging application SNMP level 8
>
> When you issue a "show logging buffer" you will see output similar to
> this:
>
> <166>Sep 8 16:34:08 192.168.1.1 SNMP[5]User:public;
> Source:134.141.1.99;
> Auth failure, bad community name.
>
> It is probably a server application hitting the switch with SNMP.
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
