[c-nsp] MST and Uplinkfast
Andy Saykao
andy.saykao at staff.netspace.net.au
Thu Aug 27 03:06:00 EDT 2009
Hi David,
Thanks for the reply...
With MST deployed across our network now, the access layer switches take
20-30seconds before they start switching traffic via the redundant link.
Prior to this we were using PVST+ and with uplinkfast enabled on these
access layer switches, once the primary link failed, the redundant
linked kicked in straight away (drop one packet). Is MST suppose to
switch traffic almost instantly or is this 20-30sec delay a "normal"
thing???
Thanks.
Andy
-----Original Message-----
From: David Hughes [mailto:David at Hughes.com.au]
Sent: Thursday, 27 August 2009 4:49 PM
To: Andy Saykao
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] MST and Uplinkfast
The fact that Rapid STP is an active protocol (rather than the old
listen / learn / wait) implies that workarounds like uplinkfast are
nolonger required. MST uses RSTP as the STP within the instances and as
such gains all the benefits that rapid gives you.
David
...
On 27/08/2009, at 7:37 AM, Andy Saykao wrote:
> To me this statement seems rather ambigious - are they saying
> uplinkfast is disabled with MST or is it built into RPST and therefore
> MST will have that feature too???
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
Please notify the sender immediately by email if you have received this
email by mistake and delete this email from your system. Please note that
any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of the organisation.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The organisation accepts no liability for any
damage caused by any virus transmitted by this email.
More information about the cisco-nsp
mailing list