[c-nsp] backup with STP

Cheung, Rick Rick.Cheung at nextelpartners.com
Wed Sep 28 09:54:19 EDT 2005


	Or run etherchannel and achieve fast convergence with less
complexity.



Thanks,
Rick Cheung

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Dan Martin
Sent: Wednesday, September 28, 2005 9:25 AM
To: cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] backup with STP

Spanning tree can take a minute or more to work its magic, depending.
Make sure that the failover happens fast enough for you.  If it doesn't
I think you're back to rapid spanning tree to lower the amount of time
it takes to fail over.

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Maxim Tuliuk
Sent: Wednesday, September 28, 2005 9:03 AM
To: David J. Hughes
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] backup with STP

I don't need stp instance per vlan, I need compatibily with old dot1q
switch that support the simplest stp (802.1d) - it get two links (with
group of dot1q vlans) and will switch on these ports using stp.
Does mst be compatible with old stp implementation?

On Wed, Sep 28, 2005 at 21:43 +1000, David J. Hughes wrote:
>
> The only words I would say about MST are - DON'T GO THERE.
>
> If your environment is capable of running Rapid PVST then it is
> certainly what you want to be running.  RPVST+ extends the PVST+ that
> you know and love to include rapid response to topology changes.  MST
> gives you a totally different set of semantics (and issues/problems)
to
> get your head around.  Remember you no longer have an STP instance per

> vlan.  The interaction with anything in your network that doesn't
speak
> MST can be troublesome and "interesting" to say the least.  RPVST+ is
> the end-game and MST was a bump in the road on the way.
>
>
> David
> ...
>
>
> On 28/09/2005, at 9:11 PM, Maxim Tuliuk wrote:
>
> >ok
> >could you say some words about mstp? is it better or worse than
> >rapid-pvst?
> >
> >On Tue, Sep 27, 2005 at  7:40 -0400, Dave Temkin wrote:
> >>Yes, rapid-pvst and regular STP are directly inter-compatible.  The
> >>rapid-pvst switch will run in regular STP mode for the ports
> >>connected to the client switch.
> >>
> >>--
> >>David Temkin
> >>
> >>On Tue, 27 Sep 2005, Maxim Tuliuk wrote:
> >>
> >>>Hello!
> >>>Our client connects to us using switch and two different fiber
links.
> >>>Client's switch supports Spanning Tree (802.1D) only, on my side -
> >>>catalyst 3550 (now: mode rapid-pvst).
> >>>Can I build L2 backup using stp?
> >>>
> >>
> >
> >--
> >Maxim Tuliuk
> >WWW: http://primats.org.ua/~mt/
> >ICQ: 21134222
> >
> >The bike is absolute freedom of moving
> >_______________________________________________
> >cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>

--
Maxim Tuliuk
WWW: http://primats.org.ua/~mt/
ICQ: 21134222

The bike is absolute freedom of moving
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

This message, including any attachments, contains confidential information intended for a specific
individual and purpose and is protected by law. If you are not the intended recipient, please contact
sender immediately by reply e-mail and destroy all copies.
You are hereby notified that any disclosure, copying, or distribution of this message, or the taking
of any action based on it, is strictly prohibited.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email
and any attachments for the presence of viruses. The sender accepts no liability for any damage
caused by any virus transmitted by this email. E-mail transmission cannot be guaranteed
to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors
or omissions in the contents of this message, which arise as a result of e-mail transmission.



More information about the cisco-nsp mailing list