how does logging work on PC62xx?

Severity — The following are the available severity logs:

– Emergency — The highest warning level. If the device is down or not functioning properly, an

emergency log message is saved to the specified logging location.

– Alert — The second highest warning level. An alert log is saved if there is a serious device

malfunction, for example, all device features are down.

– Critical — The third highest warning level. A critical log is saved if a critical device malfunction occurs,

for example, two device ports are not functioning, while the rest of the device ports remain functional.

– Error — A device error has occurred, for example, if a single port is offline.

– Warning — The lowest level of a device warning. The device is functioning, but an operational

problem has occurred.

– Notice — Provides device information.

– Informational — Provides device information.

– Debug — Provides debugging messages.

When a severity level is selected, all severity level choices above the selection are selected automatically.( So yes, choosing debug level will include everything.)

When you select a specific level, all of the levels above it are automatically selected. For example, if you select Error, the system automatically selects Error, Critical, Alert, and Emergency. If you deselect Error, all of the levels below (for example, Error, Warning, Notice, Informational, Debug) are deselected.

Page 135 starts the management of logs. It goes over the web based and CLI version.

http://support.dell.com/support/edocs/network/PC62xx/en/UCG/ucg_en.pdf

Hope this information helps.

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

I would recommend checking your firmware level and making sure it is up to date.

<ADMIN NOTE: Broken link has been removed from this post by Dell>

If I find anything else that may cause this I will chime back in.

Thanks.

Of course we are running the latest firmware (3.3.2.3), so I think this is a bug

Thanks for your help

Thilo