STP logging level

bmauro

Alright - first off I want to apologize for this question - but I've tried everything I can and can't find an answer.

I want to go through some STP labs, but I'm having the hardest time configuring the logging levels to see STP messages.

All the examples in the books so the messages in the following format : for example - 01:04:46: %SPANTREE_FAST-SP-7-PORT_FWD_UPLINK: VLAN0001 FastEthernet3/2 moved to Forwarding (UplinkFast).



I have my console and terminal set to debugging, and nothing. I would assume that setting the log to level 7 would capture everything.

The only way I can come close to these messages is turn on debug spann-tree events, which gets the job done, but now I just want to know what I'm over looking. All of this is being done through the console port.

***************************
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns)
Console logging: level debugging, 1016 messages logged
Monitor logging: level debugging, 2 messages logged
Logging to: vty1(2)
Buffer logging: level debugging, 941 messages logged
Exception Logging: size (4096 bytes)
File logging: disabled
Trap logging: level debugging, 257 message lines logged

kryolla

I think you need to turn it on by default it is not turned on

Rack1SW2(config)#spanning-tree logging

bmauro

Just checked - doesn't look like its a valid command on a 2950:

2950(config)#spanning-tree ?
backbonefast Enable BackboneFast Feature
etherchannel Spanning tree etherchannel specific configuration
extend Spanning Tree 802.1t extensions
loopguard Spanning tree loopguard options
mode Spanning tree operating mode
mst Multiple spanning tree configuration
pathcost Spanning tree pathcost options
portfast Spanning tree portfast options
uplinkfast Enable UplinkFast Feature
vlan VLAN Switch Spanning Tree

But it was a valid command on my 3750 - but it still wasn't displaing STP port state changes (ie, BLK->LIS->LRN)

kryolla

try this in interface level

Rack1SW1(config-if)#logging event ?
bundle-status BUNDLE/UNBUNDLE messages
link-status UPDOWN and CHANGE messages
nfas-status NFAS D-channel status messages
spanning-tree Spanning-tree Interface events
status Spanning-tree state change messages
subif-link-status Sub-interface UPDOWN and CHANGE messages
trunk-status TRUNK status messages

Rack1SW1(config-if)#logging event spann
Rack1SW1(config-if)#logging event spanning-tree ?
<cr>

Rack1SW1(config-if)#logging event spanning-tree

bmauro

kryolla - thanks for the help...but unfortunately I think I was chasing an imaginary rabbit.

The lab I was working was for uplinkfast, and after reading the chapter back and forth I found that besides

%SPANTREE_FAST-7-PORT_FWD_UPLINK: VLAN0001 FastEthernet0/2 moved to Forwarding (UplinkFast).

There weren't any %SPANTREE messages - I just assumed that normal STP operation would also trigger a log message, which is appears, it does not.

debug spanning-tree events seems to be the only game in town

If anyone has more info to correct me - pls let me know.

kryolla

I turned on logging spanning-tree global and interface and I do see logs for normal spanning tree events

Rack1SW2(config-if)#
*Mar 10 23:03:20.700: %SPANTREE-6-PORT_STATE: Port Fa0/4 instance 43 moving from
disabled to blocking
*Mar 10 23:03:20.700: %SPANTREE-6-PORT_STATE: Port Fa0/4 instance 43 moving from
blocking to listening
Rack1SW2(config-if)#
*Mar 10 23:03:21.196: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state t
o up
*Mar 10 23:03:22.196: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/4, changed state to up
Rack1SW2(config-if)#
*Mar 10 23:03:35.700: %SPANTREE-6-PORT_STATE: Port Fa0/4 instance 43 moving from
listening to learning
Rack1SW2(config-if)#
*Mar 10 23:03:50.700: %SPANTREE-6-PORT_STATE: Port Fa0/4 instance 43 moving from
learning to forwarding
Rack1SW2(config-if)#
*Mar 10 23:03:50.700: %SPANTREE-5-TOPOTRAP: Topology Change Trap for vlan 43
Rack1SW2(config-if)#

bmauro

I'll have to play around with this more tonight.

jason_lunde

I think I had this same problem the other day...try the global command
logging console

It worked for me trying to see spanning tree messages the other day through the console port...I was using debug commands like
debug spanning events

and nothing was coming to the screen when I would unplug a cable and ports would transition. Plugged in the logging console command and I had all the output I could handle. Hope this helps.

Jason

Nevermind...read your above posts better and now I see what you are saying...I will lab a bit tonight on my switches and see if I can find a bit out.