Issue with debug messages on SW
When I use debug commands they are not showing. I am having to use "show log" in order to see them. I thought the idea was for them to appear straight away following a change? I have logging sync enabled and the traps set to the default levels. I didn't touch them.
I don't think i'm even getting up/down or change lmessages unless I check show log. I have tried all commands and none are working.
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 21 flushes, 0 overruns)
Console logging: level debugging, 18245 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 15586 messages logged
Exception Logging: size (4096 bytes)
File logging: disabled
Trap logging: level informational, 27 message lines logged
Is it because of the Monitor logging?
Thanks
I don't think i'm even getting up/down or change lmessages unless I check show log. I have tried all commands and none are working.
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 21 flushes, 0 overruns)
Console logging: level debugging, 18245 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 15586 messages logged
Exception Logging: size (4096 bytes)
File logging: disabled
Trap logging: level informational, 27 message lines logged
Is it because of the Monitor logging?
Thanks
Comments
-
Epidot Member Posts: 11 ■□□□□□□□□□I think I might need "logging event link-status global". I will try
[edit] this command doesn't even exist on my SW.
[edit} fixed it. no idea how. -
Epidot Member Posts: 11 ■□□□□□□□□□Please can someone explain this to me.
one of my switches now shows me all messages and has the below
yslog logging: enabled (0 messages dropped, 0 messages rate-limited, 82 flushes, 0 overruns)
Console logging: level debugging, 74188 messages logged
Monitor logging: level debugging, 62809 messages logged
Logging to: vty1(62809)
Buffer logging: level debugging, 62823 messages logged
Exception Logging: size (4096 bytes)
File logging: disabled
Trap logging: level informational, 24 message lines logged
My other switch does not show messages and is missing that logging to VTY line.
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 361 flushes, 0 overruns)
Console logging: level debugging, 188700 messages logged
Monitor logging: level debugging, 4 messages logged
Buffer logging: level debugging, 145942 messages logged
Exception Logging: size (4096 bytes)
File logging: disabled
Trap logging: level informational, 36 message lines logged -
Epidot Member Posts: 11 ■□□□□□□□□□Okay nevermind. I see that terminal monitor enables instant messages and sets the "Logging to VTY" line. and logging monitor sets the level.
The problem I had was that I have only one cable connected to my PC so the telnet session was going into SW1 only. Terminal monitoring would be enabled on this SW and messages would show. Each time I telnet to another SW the connection has to go through SW1. This is causing the monitor VTY line to dissapear and messages will not show on SW 2,3 or 4. So I'm having to re enable Terminal Monitor ever time I reconnect to the other Switches as the Monitor VTY line keeps dissapearing. bit of a pain..
I guess I can connect a cable to each of the Switches to solve this.