Unsolved
This post is more than 5 years old
37 Posts
0
22502
February 22nd, 2012 06:00
how does logging work on PC62xx?
I have got a question concering loggin on PC62xx machines.
We use this on our PC6248
logging a.b.c.d
description "syslog server"
level debug
exit
and Buffer Logging: level info
From my understanding this will
log ALL messages to the syslogserver (level 0 - level 7)
log Level 0 - Level 6 to buffer logging
Right or wrong?
Thanks
Thilo
---------------------------------
emergency System is unusable (Severity Level:0)
alert Immediate action needed (Severity Level:1)
critical Critical conditions (Severity Level:2)
error Error conditions (Severity Level:3)
warning Warning conditions (Severity Level:4)
notice Normal but significant conditions (Severity Level:5)
info Informational messages (Severity Level:6)
debug Debugging messages (Severity Level:7)
ThiloWunderlich
37 Posts
0
February 22nd, 2012 08:00
reason for this question is this log:
Notice the missing STP messages in the syslog, though syslog should get ALL messages!
And those STP messages are quite important :)
logging buffered:
Buffer Logging: level info. Buffer Messages: 7499 Logged,
this is "show log"
<189> FEB 21 11:06:35 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7467 %% 1/0/11 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> FEB 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7468 %% Link Up: 1/0/11
<189> FEB 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7469 %% 1/0/11 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> FEB 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7470 %% 1/0/11 is transitioned from the Learning state to the Forwarding state in instance 0
<189> FEB 21 11:12:49 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7471 %% Instance 0 has elected a new STP root: 8000:0021:9bb5:4710
<189> FEB 21 11:12:50 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7472 %% Instance 0 has elected a new STP root: 0000:001e:c988:5930
<189> FEB 21 11:56:34 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7473 %% Link Down: 1/0/13
<189> FEB 21 11:56:34 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7474 %% Link on 1/0/13 is failed
syslog:
Syslog server 172.16.222.31 logging: debug. Messages: 0 dropped
this is from the syslog server:
Feb 21 11:06:35 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7467 %% 1/0/11 is transitioned from the Forwarding state to the Blocking state in instance 0
Feb 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7468 %% Link Up: 1/0/11
Feb 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7469 %% 1/0/11 is transitioned from the Forwarding state to the Blocking state in instance 0
Feb 21 11:06:38 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7470 %% 1/0/11 is transitioned from the Learning state to the Forwarding state in instance 0
Feb 21 11:56:34 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7473 %% Link Down: 1/0/13
Feb 21 11:56:34 172.17.220.161-1 TRAPMGR[152705024]: traputil.c(611) 7474 %% Link on 1/0/13 is failed
Thilo
ThiloWunderlich
37 Posts
0
February 22nd, 2012 23:00
Of course we are running the latest firmware (3.3.2.3), so I think this is a bug
Thanks for your help
Thilo