09-27-2002 06:10 AM - edited 03-02-2019 01:41 AM
In CatOS one has very strict control over the level of logging for individual facilities. I like to have detailed information on Spanning Tree transitions, and as such we've set Spanning Tree logging at a highly detailed level on our CatOS boxes.
In IOS one doesn't have the same level of control, as logging is merely defined as a general level af trap (syslog) logging.
Anybody got any tricks on obtaining detailed Spanning Tree information on Cat6500 IOS apart from increasing the log level and piping it thru' syslog-ng?
09-27-2002 10:25 AM
You can do quite a few debugs on the SP side
Router#remote login switch
Trying Switch ...
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
Switch-sp#debu
Switch-sp#debug sp
Switch-sp#debug spanning-tree ?
all All Spanning Tree debugging messages
backbonefast BackboneFast events
bpdu Spanning tree BPDU
bpdu-opt Optimized BPDU handling
config Spanning tree config changes
etherchannel EtherChannel support
events Spanning tree topology events
exceptions Spanning tree exceptions
general Spanning tree general
mstp MSTP debug commands
pvst+ PVST+ events
root Spanning tree root events
snmp Spanning Tree SNMP handling
switch Switch Shim debug commands
uplinkfast UplinkFast events
Switch-sp#debug spanning-tree
09-27-2002 02:03 PM
I was thinking more in terms of daily logging.
Debugging is great when you're tracking a specific problem.
I want logging to track down the cause of past events, or provide insight into what happened when something failed.
Spanning Tree state info is invaluable when tracking layer 2 problems and their history.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: