From: Matt Sherman (matt.sherman2@gmail.com)
Date: Sun Jul 13 2008 - 20:36:08 ART
I was running dynamips ver 0.2.8-RC1 and had big problems with Spanning
Tree. Two bridges would both claim to be root for a given vlan. The
switches usually started up normally but then started experiencing problems.
My CPU utilization was low and memory wasn't maxed out either.
I upgraded to 0.2.8-RC2 and it seems to have fixed the problem. One of my
hypervisor instances would crash after a period of time and that cleared up
as well.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Rado
Vasilev
Sent: Friday, July 11, 2008 11:22 AM
To: Jason Madsen
Cc: Cisco certification
Subject: Re: Spanning Tree in Dynamips
Hi Jason,
I've seen spanning tree constantly flapping with a dynamips setup with 2
machines.
I'm using two machines and have spread the routers across those. The
issue back then is that i had one of the dynamips process bound to the
first machine's localhost interface.
As soon as i had it reconfigured to listen to the public IP, the
spanning tree stopped flapping.
Regards,
Rado
> Has anyone experienced instability using Dynamips with constant Spanning
> Tree changes e.g. list, lrn, blk, fwd...etc? I believe I'm seeing this
> because of the latency associated with running Dynamips on my computer,
but
> I'm wondering if that's the case or if there's something else inolved
> configuration-wise?
>
> here's what I'm seeing on the one device having issues (debug spann
> event output):
>
> *Mar 1 00:42:06.955: STP: VLAN1 Fa0/0 -> blocking
> R3#
> *Mar 1 00:42:30.011: STP: VLAN1 Fa0/0 -> listening
> R3#
> *Mar 1 00:42:31.927: STP: VLAN1 heard root 32768-cc02.1594.0000 on Fa0/0
> *Mar 1 00:42:31.931: current Root has 1600-cc00.1594.0000
> R3#
> *Mar 1 00:42:32.967: STP: VLAN1 Fa0/0 -> blocking
> R3#
> *Mar 1 00:42:52.987: STP: VLAN1 Fa0/0 -> listening
> *Mar 1 00:42:53.091: STP: VLAN1 heard root 32768-cc02.1594.0000 on Fa0/0
> *Mar 1 00:42:53.095: current Root has 1600-cc00.1594.0000
> *Mar 1 00:42:53.143: STP: VLAN1 Topology Change rcvd on Fa0/0
> *Mar 1 00:42:53.143: STP: VLAN1 sent Topology Change Notice on Fa0/1
> R3#
> *Mar 1 00:42:54.103: STP: VLAN1 Fa0/0 -> blocking
> R3#
> *Mar 1 00:43:15.123: STP: VLAN1 Fa0/0 -> listening
> *Mar 1 00:43:15.151: STP: VLAN1 heard root 32768-cc02.1594.0000 on Fa0/0
> *Mar 1 00:43:15.155: current Root has 1600-cc00.1594.0000
> *Mar 1 00:43:15.275: STP: VLAN1 Topology Change rcvd on Fa0/0
> *Mar 1 00:43:15.279: STP: VLAN1 sent Topology Change Notice on Fa0/1
> R3#
> *Mar 1 00:43:16.219: STP: VLAN1 Fa0/0 -> blocking
> R3#
> *Mar 1 00:43:37.203: STP: VLAN1 Fa0/0 -> listening
> *Mar 1 00:43:37.983: STP: VLAN1 heard root 32768-cc02.1594.0000 on Fa0/0
> *Mar 1 00:43:37.987: current Root has 1600-cc00.1594.0000
> *Mar 1 00:43:38.071: STP: VLAN1 Topology Change rcvd on Fa0/0
> *Mar 1 00:43:38.075: STP: VLAN1 sent Topology Change Notice on Fa0/1
> R3#
> *Mar 1 00:43:38.967: STP: VLAN1 Fa0/0 -> blocking
> R3#
> *Mar 1 00:44:01.159: STP: VLAN1 Fa0/0 -> listening
> *Mar 1 00:44:01.999: STP: VLAN1 heard root 32768-cc02.1594.0000 on Fa0/0
> *Mar 1 00:44:02.003: current Root has 1600-cc00.1594.0000
> *Mar 1 00:44:02.051: STP: VLAN1 Topology Change rcvd on Fa0/0
> *Mar 1 00:44:02.055: STP: VLAN1 sent Topology Change Notice on Fa0/1
> R3#
> *Mar 1 00:44:02.975: STP: VLAN1 Fa0/0 -> blocking
>
>
>
> Jason
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:54 ART