in case you are still interested:
( the lines with the really long hex numbers are the result of the debug
span tree )

R1#debug span tree
Spanning Tree BPDU debugging is on
R1#debug span ev
Spanning Tree event debugging is on
R1#

00:46:20: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:46:22: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:46:24: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

INSERT LOOP INTO NETWORK ( bridge two hubs )

00:46:26: ST: Ethernet0
0000000000800000107B7EEBD700000000800000107B7EEBD7800200
00140002000F00
00:46:26: ST: new root is 32768, 0010.7b7e.ebd7 on port Ethernet0, cost 100
00:46:26: ST: sent Topology Change Notice on Ethernet0
00:46:26: ST: Serial0 -> blocking
00:46:26: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:46:27: ST: Ethernet0
0000000081800000107B7EEBD700000000800000107B7EEBD7800200
00140002000F00
00:46:28: ST: Ethernet0
0000000001800000107B7EEBD700000000800000107B7EEBD7800200
00140002000F00
00:46:28: ST: Serial0
0000000001800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:46:30: ST: Ethernet0
0000000001800000107B7EEBD700000000800000107B7EEBD7800200
00140002000F00
00:46:30: ST: Serial0
0000000001800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:46:32: ST: Ethernet0
0000000001800000107B7EEBD700000000800000107B7EEBD7800200
00140002000F00
00:46:32: ST: Serial0
0000000001800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

REMOVE LOOP

00:47:12: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:14: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

00:47:14: ST: new root is 32768, 0010.7b7e.ebd7 on port Serial0, cost 647
00:47:14: ST: Serial0 -> listening

00:47:16: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:18: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

00:47:29: ST: Serial0 -> learning
00:47:30: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:32: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:34: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

00:47:44: ST: Serial0
0000000000800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00

00:47:44: ST: sent Topology Change Notice on Serial0
00:47:44: ST: Serial0 -> forwarding
00:47:45: ST: Serial0
0000000081800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:46: ST: Serial0
0000000001800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00
00:47:48: ST: Serial0
0000000001800000107B7EEBD700000000800000107B7EEBD780030000
140002000F00u
R1#
R1#

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Priscilla Oppenheimer
Sent: Friday, August 24, 2001 10:51 AM
To: [EMAIL PROTECTED]
Subject: RE: debug span on router acting as bridge [7:17165]


I wonder if "debug span tree" is the one that shows the packets?

Any chance you could try for me?? ;-] You would have to have bridging
enabled on a couple routers or a router connected to a switch.

I am interested in the output. I want to see the actual packet and document
the output, because the Cisco documentation is wrong. Not only does it not
mention the required argument, but it explains the output incorrectly. A
missing carriage return messed it up for them. (If there's a carriage
return after "ST: Ether4," then their explanation works. I see these sorts
of errors as an opportunity! ;-)

To see what I'm babbling about, check

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122de
bug/dbfser.htm#xtocid471525

THANKS

Priscilla

At 11:24 AM 8/24/01, Leigh Anne Chisholm wrote:
>RouterD#debug span
>debug span
>% Incomplete command.
>
>RouterD#debug span ?
>   events  Spanning tree topology events
>   tree    Spanning tree protocol data units
>
>RouterD#debug span events
>Spanning Tree event debugging is on
>RouterD#debug span tree ?
>
>
>RouterD#debug span tree
>Spanning Tree BPDU debugging is on
>RouterD#
>
>Do you need an example of what the debug output looks like?
>
>
>   -- Leigh Anne
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
>Priscilla Oppenheimer
>Sent: Friday, August 24, 2001 11:26 AM
>To: [EMAIL PROTECTED]
>Subject: debug span on router acting as bridge [7:17165]
>
>
>Does anyone have a router acting as a bridge in their lab network?
>
>Cisco documentation claims that there is a "debug span" command that shows
>BPDU frames in hex as they come in. Now, I think this is an awful idea,
>since they come in every 2 seconds, but for a project I'm working on I need
>to find out if the command really exists.
>
>My routers will not run IOS beyond 11.0. (Hey, they were free! ;-) They do
>not support "debug span." They only support "debug span events" which shows
>this:
>
>Albany#debug span events
>Spanning Tree event debugging is on
>Albany#
>ST: Topology Change rcvd on Ethernet0
>ST: Topology Change rcvd on Ethernet1
>ST: Topology Change rcvd on Ethernet0
>ST: Topology Change rcvd on Ethernet1
>
>I'm wondering 2 things:
>
>Does "debug span events" still exist? (It's not in the documentation.)
>
>Does "debug span" exist? (It is in the documentation but doesn't work on my
>routers.)
>
>Could anyone try it for me and send me output?
>
>By the way, if you don't have bridging working on your routers, it's really
>easy to configure:
>
>bridge 1 protocol ieee
>int e0
>bridge-group 1
>int e1
>bridge-group 1
>
>THANK-YOU!!!!!!
>
>Priscilla
>
>________________________
>
>Priscilla Oppenheimer
>http://www.priscilla.com
________________________

Priscilla Oppenheimer
http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=17287&t=17165
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to