Dell STP and Cisco Rapid-PVST+ interoperabillity
Referencing to this doc:
https://supportforums.cisco.com/docs/DOC-16177
which was very helpful, I noticed that I'm getting this error message:
%SW_MATM-4-MACFLAP_NOTIF: Host d067.e5cc.2e49 in vlan 1 is flapping between port Po11 and port Po12
I have Dell PC6248 connected to C3560 with two port channels. In fact, I have two Dell switches in a stack. As document describes, I configured MST on both switches and that resolved slow convergence of network, but above message now appears.
That MAC address is no host:
Cisco switch
Dell switch
Cisco switch:
Router_Switch#sh mac address-table
Mac Address Table
Vlan Mac Address Type Ports
All 0100.0ccc.cccc STATIC CPU
All 0100.0ccc.cccd STATIC CPU
All 0180.c200.0000 STATIC CPU
All 0180.c200.0001 STATIC CPU
All 0180.c200.0002 STATIC CPU
All 0180.c200.0003 STATIC CPU
All 0180.c200.0004 STATIC CPU
All 0180.c200.0005 STATIC CPU
All 0180.c200.0006 STATIC CPU
All 0180.c200.0007 STATIC CPU
All 0180.c200.0008 STATIC CPU
All 0180.c200.0009 STATIC CPU
All 0180.c200.000a STATIC CPU
All 0180.c200.000b STATIC CPU
All 0180.c200.000c STATIC CPU
All 0180.c200.000d STATIC CPU
All 0180.c200.000e STATIC CPU
All 0180.c200.000f STATIC CPU
All 0180.c200.0010 STATIC CPU
All ffff.ffff.ffff STATIC CPU
1 d067.e5cc.2e49 DYNAMIC Po11
255 d067.e5cc.2e47 DYNAMIC Po11
Total Mac Addresses for this criterion: 22
WSS_Dell_PC6248#show bridge address-table
Aging time is 300 Sec
Vlan Mac Address Port Type
1 04C5.A464.301F ch1 Dynamic
1 04C5.A464.3025 ch2 Dynamic
1 04C5.A464.3028 ch1 Dynamic
255 04C5.A464.3045 ch1 Dynamic
255 D067.E5CC.2E47 cpu Management
Total MAC Addresses in use:5
VLAN 255 is mgmt vlan. I didn't get that message before using mst.
Configuration of trunk ports on Dell:
interface port-channel 1
description 'TRUNK_3560_1'
switchport mode general
switchport general allowed vlan add 10,255 tagged
exit
What seems to be the problem here?
CISCO 3560:
Router_Switch#show spanning-tree mst 0
##### MST0 vlans mapped: 1-4094
Bridge address 04c5.a464.3000 priority 32768 (32768 sysid 0)
Root this switch for the CIST
Operational hello time 2 , forward delay 15, max age 20, txholdcount 6
Configured hello time 2 , forward delay 15, max age 20, max hops 20
Interface Role Sts Cost Prio.Nbr Type
Fa0/25 Desg FWD 200000 128.29 P2p
Po11 Desg FWD 100000 128.136 P2p
Po12 Desg FWD 100000 128.144 P2p
Router_Switch#show etherchannel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
11 Po11(SU) - Fa0/33(P) Fa0/35(P)
12 Po12(SU) - Fa0/27(P) Fa0/36(P)
DELL:
WSS_Dell_PC6248#show interfaces port-channel
Channel Ports Hash Algorithm Type
ch1 Active: 1/g48, 2/g48 3
ch2 Active: 1/g47, 2/g47 3
(output omited)
WSS_Dell_PC6248#show spanning-tree mst-configuration
Name: D0-67-E5-CC-2E-47
Revision: 0
Instance Vlan Mapped
0 1, 10, 20, 255
WSS_Dell_PC6248#show spanning-tree
Spanning tree Enabled BPDU flooding Disabled Portfast BPDU filtering Disabled mode mstp
CST Regional Root: A0:00:D0:67:E5:CC:2E:47
Regional Root Path Cost: 0
###### MST 0 Vlan Mapped: 1, 10, 20, 255
ROOT ID
Address 04:C5:A4:64:30:00
Path Cost 100000
Root Port ch2
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Bridge ID
Priority 40960
Address D0:67:E5:CC:2E:47
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec TxHoldCount 6 sec
(output omited)
1/g47 Enabled 128.47 0 FWD Disb No No
1/g48 Enabled 128.48 0 FWD Disb No No
(output omited)
ch1 Enabled 96.626 100000 DSC Altn No No
ch2 Enabled 96.627 100000 FWD Root No No
(output omited)
Similar Messages
-
Uplink between Stacked Dell 8132 and Cisco 1921 HSRP pair.
Hello,
I have three Dell 8132 switches stacked and we plan on connecting them to an HSRP pair of Cisco 1921 routers. What would be the best way to uplink these stacked switches to the 1921 pair?
I was thinking of creating vlan trunk from 2 of the 3 Dell switches, one trunk going to each router and enable HSRP on these trunks for the vlans I need to route. Would that be a good approach?
Attached is a basic network of what it would look like. Please suggest if this is a good way to accomplish this or if there is a more better and efficient way to do it?
ThanksJust to clarify I wasn't suggesting that you move all the routing to the Dell switches. If the routers are already doing some routing for you then you could simply connect the Dell switches with L3 uplinks.
But yes if you feel more comfortable using Cisco then use the routers.
I have never used an integrated switch module to be honest, I just used L3 switches and routers separately.
I suspect it would work as long as there was a backplane connection between the switch module and the router itself so you could route directly from the switch module to the router.
Can't say for sure whether there is or not as like I say I have never used them.
Which to use really comes down to how much bandwidth you need between vlans which only you know really. If you think using one interface and splitting it up may cause problems then you could look at a switch module.
Although it does seem a bit redundant purchasing a switch module when you have L3 switches already :-)
But I do understand what you mean about being a Cisco shop.
Jon -
Migrating from Rapid-PVST+ to MST
We wish to migrate our Rapid-PVST+ network of around 25 switches to MST but for reasons that we believe are valid we do not want to start with the core switches. We want to convert one part of our network first that is connected to the core with a single trunk link.
We are refering to this document: Understanding Multiple Spanning Tree Protocol (802.1s) and in particular the section headed 'Alternate Configuration (Not Recommended)'. We can accomodate the drawbacks of this scenario, and in any case it will only be a temporary setup unitl we complete the migration.
Under 'Invalid Configuration' it states that "If the PVST+ bridge is the root, this bridge must be the root for all VLANs (including the CST, which always runs on VLAN 1, regardless of the native VLAN, when the CST runs PVST+)". My question is if this is strictly correct (the border bridge MUST be the root for all the VLANs) or if the PVST+ sub-section as a whole must contain the root (e.g. the next PVST+ bridge in the topology would also be valid if its priority were high enough)?
DanielHi Daniel,
Let me start by explaining what is the problem with MSTP/PVST+ interoperation. Things to watch out for are direct consequences of the interoperation limitations so it is vital to understand what is going on.
When MSTP region is connected to an (R)PVST+ region, it tries to speak (R)PVST+ and process received (R)PVST+ BPDUs. This process is called PVST Simulation. However, there are major difficulties in this process: the (R)PVST+ uses per-VLAN semantics while MSTP runs instances with VLANs simply mapped onto them. The role and state of an MSTP boundary port is always determined by the IST ( = MSTI0) instance talking to the outside world, and is simply inherited by all instances running in the MSTP region. That means that if the port is discarding in IST, it is discarding in all instances (and hence all VLANs). If the port is forwarding in IST, it is forwarding in all instances (and hence all VLANs). The same goes for every role/state combination. This fact makes it impossible to do any per-VLAN semantics on an MSTP boundary port. Even if you tried to map incoming (R)PVST+ BPDUs into appropriate instances, you could arrive to an unsolvable situation where the port should be discarding for one VLAN and forwarding for another, although they are both mapped to the same MSTP instance.
These limitations are the guidelines according to which the PVST Simulation works. Because the MSTP boundary port should use only IST data when speaking to the outside world (that is how MSTP boundary port should operate according to IEEE specifications), PVST Simulation makes use of it: it takes the IST data and replicates it into PVST+ BPDUs sent out for all VLANs defined on the switch. In other words, an MSTP boundary port speaking to PVST+ region sends one PVST+ BPDU for each VLAN that is defined on the switch, using IST data as the contents of this BPDU. Essentially, this makes the entire MSTP region look like a single huge switch identically configured for each and every VLAN, with the configuration simply taken from the IST.
Doing this is easy. However, the opposite process is much more constraining: an MSTP boundary port tries to process every received PVST+ BPDU using the IST instance. This is where the troubles begin. If all received PVST+ BPDUs are supposed to allow stable and unambiguous determination of the MSTP boundary port role and state, they must be identical, i.e. the same Root Bridge ID, the same Sending Bridge ID, same Root Path Cost, same Sending Port ID, perhaps even the same timers in each received PVST+ BPDU (sorry for the "perhaps" word here - the PVST Simulation is practically undocumented and these are only my experiences - some areas are still white). Failure to meet this requirement, i.e. receiving two or more differing PVST+ BPDUs on an MSTP boundary port, results in PVST Simulation inconsistency and into permanent blocking of that port until the conflicting PVST+ BPDUs cease to be received.
Note that this requirement of receiving identical PVST+ BPDUs is impossible to achieve with current Catalyst switches: every recent Catalyst switch is using Extended System ID, i.e. it inserts the VLAN ID into the Bridge ID when creating a BPDU for a particular VLAN. Even if you configured the PVST+ region so that a single switch was the root bridge for all VLANs, its PVST+ BPDUs would still differ because each of them would carry a different Extended System ID in the RBID/SBID field.
The only way to prevent these problems is to make sure that the MSTP region is considered as the root switch for all VLANs. Because it is the IST whose data is visible outside the MSTP region, this can be accomplished by configuring the bridge priority on the IST root bridge so low that it beats all switches in the PVST+ region and thereby becomes the root bridge for all VLANs.
Now to your questions:
We are refering to this document: Understanding Multiple Spanning Tree Protocol (802.1s) and in particular the section headed 'Alternate Configuration (Not Recommended)'. We can accomodate the drawbacks of this scenario, and in any case it will only be a temporary setup unitl we complete the migration.
That document is a perfect reference. However, it does not describe the troubles related to the PVST Simulation because it does not take the Extended System ID into account. In fact, the scenario with the PVST+ region containing the root bridge for all VLANs is not possible to accomplish with current Catalyst switches. It is ironical that by striving for compatibility between MSTP and Cisco (R)PVST+, Cisco has actually created a situation where it is very easy to be incompatible. So in my opinion, you cannot accomodate for such a setup - you can not afford having a root switch in the PVST+ region because that would most probably lead to MSTP boundary ports being blocked due to PVST Simulation inconsistency.
I shall stress that these problems are created in particular by the PVST Simulation. Switches running pure IEEE STP/RSTP do not cause these problems because they run a single (R)STP instance for all VLANs. An MSTP boundary port can talk to a single external (R)STP always without problems - a single (R)STP can never produce two conflicting BPDUs. It is as easy as that. It is the overdone striving for compatibility with PVST+ BPDUs that is causing these troubles.
Under 'Invalid Configuration' it states that "If the PVST+ bridge is the root, this bridge must be the root for all VLANs (including the CST, which always runs on VLAN 1, regardless of the native VLAN, when the CST runs PVST+)". My question is if this is strictly correct (the border bridge MUST be the root for all the VLANs) or if the PVST+ sub-section as a whole must contain the root (e.g. the next PVST+ bridge in the topology would also be valid if its priority were high enough)?
It is not the border bridge exactly that must be the root bridge for all VLANs. As I explained earlier, the MSTP region talks to the outside world using IST data. If the MSTP region is to become a root bridge for all VLANs, then the IST root bridge priority must be the lowest among all PVST+ bridges. The IST root bridge itself can perfectly be an internal switch somewhere deep inside the MSTP region.
The same would be valid if the PVST+ region was to become the region containing the root bridge for all VLANs. This root bridge can be any switch inside the PVST+ region, not just a boundary switch. However, this would require, among other things, deactivating the Extended System ID which is not possible.
Please feel welcome to ask further!
Best regards,
Peter -
Spanning-tree modes: PVST vs RAPID-PVST
I am upgrading an old network and as I add switches, I would like them to run rapid-pvst, instead of just pvst which is what the older switches are running.
Last I checked (with a Cisco techie at Networkers 2006), it was OK to have trunked switches with different modes (pvst and rapid-pvst)... but now I'm hearing differently from a few other sources.
Can someone please verify if this is a concern and if so, how should one proceed?
Cheers...rapid-pvst+ can be migrated into your pvst+ environment.
rapid-pvst+ configured switches revert to pvst+ to provide interoperability.
cisco recommends configuring the rapid-pvst+ and pvst+ for different STP instances. the rapid-pvst+ root switch must be running rapid-pvst+ and the pvst+ root switch must be running pvst+; as well, the pvst+ switches should be at the edge of the network.
(this being said, upgrade your core first and move outward. keep your pvst+ root switch out of the core where rapid-pvst+ will be running)
please see the following link for more info:
http://www.cisco.com/en/US/products/hw/switches/ps5206/products_configuration_guide_chapter09186a00801ce264.html#wp1150840 -
Which spanning tree protocol is preferred PVST or rapid-PVST and why?
I have WS-C2960G-24TC-L and Cisco 3750G switches, I have option to configure PVST spanning tree or rapid-pvst. Please let me know which is better and why? also send me some document explaining both protocols in detail.
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
As Alex has noted, normally rapid-PVST should be preferred.
Depending on needs (and device support), MST might be better yet. -
Does it matter if you have lets say pvst on one or more switches on the same network and rapid pvst on other switches on the same network?
They're backwards compatible, but you'll lose the advantage of Rapid-pvst when connected to a pvst switch.
HTH,
John
*** Please rate all useful posts *** -
SBR and cisco routers/switches
HI all,
i have a juniper SBR and large no of cisco devices as RAS/NAS.
i would like to have level 1 team to have just read only profile .
and level 2 team to have read and write access . i guess to accomplish this on a non cisco aaa product ,
1) DO i need to downlaod cisco radius attribute dictonary file . if yes where is the downlaod link ?
2) As user profiles are basic one ., their should be a standard attribute which has this feature . in case this is true which ietf attribute i can use ?
3) what aer vsa ? does cisco vsa help me in accomplishing my goals with SBR?
4) if i get above answers i can move in right direction accompleshing the same with firewall vendor a , ssl vpn vendor b , wifi controller vendor c , dslamp vendor e ....
Any response will be much appreciated .I have a 3750X and an SG300 trunked together and they are both running RSTP.
I set my 3750X to rapid-pvst
I set my SG300 to rstp
A "show spanning" on both devices yields: "Spanning tree enabled protocol rstp".
Both seem to be communicating STP fine. -
Hi everyone, I've a question for you guys:
Please check this topology: http://www.cisco.com/warp/public/473/84d.gif
I've read that you must enable loop guard on every nondesignated port (root and alternate ports) to prevent unidirectional related loops. I understand the situation where switch C unblooks the AP port and cause a loop. But what if the link is not unidirectional, what if switch B has some problem and indeed switch C should forward traffic to the segment C-B? Is there a difference between the link going down (disconected)and just stop seeing BPDUs?
Also, why would anyone configure loop guard on a root port? If for example, SWC stops seeing BPDUs from SWA, what would loop guard do? put the port in a block state or it would recalculate its Root port (port to SWB) and put the port to SWA into a designated state (after not receiving BPDS from SWA)? I'm very confused, any help would be greatly apretiated.
Omar MontesThe assumption made by STP is that if a link is not able to transmit BPDU, it is down. So if there is bidirectional link failure, the case is natively handled by STP. If there is only unidirectional link failure, you could end up with a unidirectional loop (which is about as bad as a bidirectional loop;-))
Loopguard is relevant on each port that is supposed to continuously receive BPDU. If your root port stop receiving BPDU, STP will move it to designated and elect a new root port. This is ok if your old root port cannot receive and transmit traffic. However, if the link is unidirectional and the port does not get blocked by loopguard, you will have a loop through the old and the new root port (in one direction only, the old root port TX direction).
Configuring loopguard on a designated port will not cause any problem anyway, so in fact you can configure loopguard blindly on all the port.
The IEEE introduced a feature (the dispute mechanism) that works much better than loopguard in order to protect against unidirectional link failure. However, this mechanism requires an RSTP bpdu format. It is currently only implemented in MST on cisco switches (it will be soon available in rapid-pvst). No need to use loopguard with the latest MST code at least.
Regards,
Francois -
Trunking between Huawei S3900 and Cisco catalyst 3750
One of my edge Huawei S3700 switches is dead, I am going to replace it with a Cisco switch Catalyst 3750 series PoE-48 via a trunk link with GE fiber port on both ends, please see the diagram below.
trunk trunk
Core switchrouter<----------S3700<--------------->Cisco Catlyst 3750
I haven’t touch Cisco switch for many years, I would like to ask the following questions:
1.) Do I need to take any precaution before connecting this Cisco switch into my Huawei network? Only one link between S3700 and C3750, so I don't need worry anout STP? Do I need to worry about Default vlan regarding trunking port?
2.) I need to use different trucking protocol e.g. 802.1Q etc to interconnect these two switches (S3700-28TP-SI-AC and Catalyst 3750), please see the following configuration:
For C3750:
switchport trunk encapsulation dot1q
switchport trunk native vlan (What you want)
switchport trunk allowed vlan (VLANs required)
switchport mode trunk
spanning-tree portfast trunk
For S3700:
port link-type trunk
port trunk permit vlan all
Do you think the configurations above are right?
Do I need to manually enter Duplex and speed options ?
3.)If the configurations are not right, then what are the commands for trucking port/link should I use on the Cisco switch (it uses IOS software) and Huawei switch? Procedures of the commands would be really helpful !
Any information and help would be much appreciated.
Thanks
RegardsHello
3750 - basic config
================
See as you are using this switch as an host switch you need to make sure ip routing isn't enabled ( it isn't by default)
Also it looks like the s3700 Huawei switch is permitting all vlans and I assuming the default native vlan is 1 ( as is cisco) so no need to specify the native either.
If you are requiring the access ports on this new cisco 3750 to be in multiple vlans then usually cisco to cisco interconnect would ultise VTP for vlan propagation however this wont occur between the Huawei switch, so you will need to manually add the vlans on the switch also.
so to summarize below is a basic host switch config for 3750.
conf t
no ip routing
hostname XXXXXX
username xxxx privilege 15 secret xxxxxxx
service password-encryption
enable secret xxxxx
security passwords min-length xx
security authentication failure rate xx log
aaa new-model aaa authentication login default local
logging buffered 4096
no service udp-small-servers
no service tcp-small-servers
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
no ip domain-lookup
spanning-tree mode rapid-pvst
spanning-tree portfast bpduguard default
int vlan x ( this may or not be vlan 1 - its whatever the L3 vlan interface is on the core switch for management connectivity)
ip address x.x.x.x y.y.y.y.
exit
ip default-gateway x.x.x.x ( ip address of CORE SVI management interface)
vlan x,x,x,x ( add the L2 vlans to the switch as vtp would not be used between the Huawei switch)
exit
int gigx/x
Description Link to Huawei switch
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
no shut
( no need for spanning-tree portfast trunk- this is usually only for ESX host ports)
int rang fa0/1 -48
Description - Access-ports
switchport host
switchport access vlan x (wihout this defaults to vlan 1)
no shut
clock timezone gmt 0
ntp peer
ntp server x.x.x. prefer
res
Paul -
Behavior of running PVST+ & Rapid-PVST+ simultaneously?
Say you have a network w/ 10 switches.
9 of them run Rapid PVST, and one runs the legacy PVST.
Would the entire L2 network fall back to legacy PVST, or only the segment where the one switch that's not yet converted to Rapid?
This Cisco doc says: "
When any RSTP port receives legacy 802.1D BPDU, it falls back to legacy STP and the inherent fast convergence benefits of 802.1w are lost when it interacts with legacy bridges."
http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a00807b0670.shtml
However, it doesn't really say if the compatibility fall-back applies to just one segment, or the entire network.
Also, what's the best way to migrate from 802.1D to 802.1w?
Is it best to go bottom-up (start from access, distro, then core), or top-down?
I've been doing it bottom-up, but wanted to know if that's appropriate.
thx
KevinDisclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Also believing, like Peter, STP with rapid-STP impacts only the joint segment, I prefer STP root core toward edge conversions. This to get the rapid-STP benefit to the core first, and to be able to selectively chose what "branches" I convert next. I.e. I might not convert from core to edge one hop layer at a time, but might choose a partial "tree" from the core. -
Rapid-PVST+ Interacting with MSTP
Hi,
we want to implement MSTP at customer side. unfortunately there are some legacy switches who don't understand MSTP.
so we'll have to implement a "hybrid scenario" where the "core" speaks MSTP using instances and the access-switches are
using their "old" spanning tree protocol (talking with the Instance 0 of the MSTP).
now my question:
when the core is migrated to MSTP, is the IST Spanning Tree able to talk with legacy switches in a "rapid way"
(if the support it)?
i found a cisco document which deals with this topic, but i'm not completely sure that it answers my question....
Rapid-PVST+ Interacting with MSTP
An MSTP switch interacts with a Rapid-PVST+ switch in the same way that an MSTP switch interacts
with PVST+ switch. (See IST Interacting with PVST+.) The MSTP switch will send IST BPDUs in
802.1D format on all VLANs to the Rapid-PVST+ switch and IST will consider the port connected to
the Rapid-PVST+ switch to be at the boundary of the MST region.
Has anyone of you experience with such "hybird" MST/Rapid-PVST+ configurations?
thanks a lot for your answers &
kind regards,
BernhardHi Bernard,
In that scenario, as mentioned in the document, the MST region is going to send plain STP BPDUs to the rapid-PVST region. So basically, only STP will be run at the boundary between MST and rapid-PVST. In particular, there will be no proposal agreement possible on the vlans because MST only runs one instance (the CIST, instance 0), while rapid-pvst runs several instances (one per vlan). So the MST side does not have a per-vlan context that would allow it to answer the proposal from each individual PVST+ instance. To be honest with you, that could probably have been enhanced, but the interaction rapid-PVST/MST has never been a priority, as we hope that customers will be able to migrate the whole network to MST and only use this interaction as a temporary solution.
Regards,
Francois -
IE-2000-4TS-B or IE-2000-4TS-L1 support PVST+ or Rapid PVST+ ?
Hello. I need to know IE-2000-4TS-B or IE-2000-4TS-L1 support PVST+ or Rapid PVST+ ? This very important to me. In datasheet I can't find this information. I was try ask this in our - Russian CISCO support on last week but they are still don't answer me. I want know this as quickly as possible,else industrial network will be designed on MOXA switches with MSTP support (less preferably).
Hello,
Based on the switch configuration guide for 15.0(1)EY, both PVST+ and Rapid PVST+ are supported on the IE 2000:
The switch can use either the per-VLAN spanning-tree plus (PVST+) protocol based on the IEEE 802.1D standard and Cisco proprietary extensions, or the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol based on the IEEE 802.1w standard.
Source: http://www.cisco.com/c/en/us/td/docs/switches/lan/cisco_ie2000/software/release/15-0_1_ey/configuration/guide/scg-ie2000/swstp.html -
A small conundrum which I can't get my head around. can someone please help.
I have a meshed layer 2 network with multiple vlans in my server farm connecting to two core routers. All these devices are running in 802.1d Spanning Tree.
I want to migrate all these to 802.1w Rapid spanning Tree. However all the documentation I read suggets that when I reconfigure a switch to Rapid it will listen on its links to utilise the appropriate protocol (802.1w or 802.1d)in use by the connected switches.
As all my switches work in 802.1d mode as I migrate a switch it will be Rapid capable but will work in 802.1d mode because all the other switches are in this mode.
Changing an attached switch to rapid will result in that listening after the config change and it will only hear 802.1d from the other switches(whether they are rapid or not) because that is what is in use.
Eventually all but one of my switches will be rapid capable but they will all work in 802.1d mode. I'll then make the config change on this last switch, it will listen to waht is being talked (802.1d) and will then come up in that mode.
So all my switches are now rapid capable but are working in non-rapid 802.1d mode.
How do I make them use the 802.1w protocol ????
The config change doesn't take up or down the point to point links and I don't reboot after making the change. Hence from the documentation the port just listens and uses what is being sent from the other end which will be 802.1d!!!
I must be missing something or not understanding things correctly. Can someone please advise how the links become 802.1W
ThanksThanks for your help Gents.
I have managed to find a definitive answer to my question by much searching on the Cisco Website and comments made by yourselves.
The definitive answer is:
1. RSTP selectively sends 802.1D-configured BPDUs and topology change notification (TCN) BPDUs on a per-port basis.
2. When a port initializes, the migration-delay timer starts and RSTP BPDUs are transmitted. While the migration-delay timer is active, the bridge processes all BPDUs received on that port.
3. If the bridge receives an 802.1D BPDU after a ports migration-delay timer expires, the bridge assumes it is connected to an 802.1D bridge and starts using only 802.1D BPDUs.
4. When RSTP uses 802.1D BPDUs on a port and receives an RSTP BPDU after the migration-delay expires, RSTP restarts the migration-delay timer and begins using RSTP BPDUs on that port.
The upshot of all this is that when a switch is configured for rapid spanning tree (spanning-tree mode rapid-pvst), the switch initializes its ports. It will immediately start sending RSTP BPDUs. If the Switch on the other end of the link(s) understands RSTP BPDUs it will then start to send RSTP BPDUs. When the migration delay timer expires they will be talking to each other in Rapid spanning Tree mode.
Switch links that have non Rapid switches at the other end will come up in 802.1D mode.
The Switch will then have different links operating in different modes. In essence a hybrid Switch.
Consequently converting a large meshed switch network to Rapid spanning Tree is quite easy and simple. Just change switches one at a time and the links will automatically change to 802.1w where possible and will remain 802.1d where not. Eventually the entire network will progressively become 802.1w as more switches are reconfigured, until it is completely 802.1w
Simple -
Migration from rapid-pvst to mst
Hi, we need to migrate our switching network (2 6513 and 8 4507 all running ios, we are using more than 200 vlan) from rapid-pvst to mst (we are going to interconnect some non-cisco switch). Is there any suggestion about this migration? Thank you.
Since you're having more than 200 vlan's, this suggestion of migrating from PerVlan RSTP(PVRSTP) to Multiple Spanning Tree (MST) is a good one. Before that ensure whether your cisco ios version supports MST feature. I think your catalyst switches all will support MST. It has2 main advantages.
1.Load Balancing,
2.Less cpu burden.
The following document explains in detail about MST:
http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfc.shtml -
Using and Troubleshooting the Dell Webcam and Dell Webcam Central Software
Please read the information at...
Using and Troubleshooting the Dell Webcam and Dell Webcam Central Software
Locate the execute file (WebcamDell2.exe) buried in...
C:\Program Files (x86)\Dell Webcam\Dell Webcam Central
Right clicked on it, then left click properties, then clicked on the compatibility tab, then changed compatibility from windows XP to Windows Vista SP 2 (the latest one they had).
If your operating system was upgraded to Windows 7, did you install the drivers in the correct order? How to Download and Install Drivers in the Correct Order
Shutdown the computer. Unplug the computer from the wall. Now remove the battery. Press and hold the power button for 30 seconds. Put the
battery back in and start the computer. Did the webcam come back?
If no, start, control panel, devices and printers. Click on add device. Is the webcam listed there?
If you recently reinstalled the operating system, did you use the preferred method? Restoring Your Computer´s Software to the Factory Settings or Restoring Your Dell Computer to Original Factory Installation with Dell DataSafe Local Backup 2.0
Please use Internet Explorer(32-bit) when navigating to My Dell Downloads :: Login. Use the same email address and password you use here. Click on add system.
***Systems purchased befor April 1, 2010 might NOT register with Dell My Downloads***
If system does NOT register after 5 minutes, then contact Dell Tech Support.
If you have XP or a system that will not register, then try using this version of Dell Webcam Central. Once it's installed, then open it, click on the ? , check for software update
Open Dell Webcam Central. In the bottom right corner, make sure the webcam is on Capture mode.
RickHello Rick,
Thanks for trying to help.
Here is the info as requested:-
Host Name: DELLLAPTOP
OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: Trevor
Registered Organization: Microsoft
Product ID: ?????
Original Install Date: 07/07/2010, 11:46:05
System Boot Time: 24/10/2011, 12:06:27
System Manufacturer: Dell Inc.
System Model: Inspiron 1570
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 23 Stepping 10 GenuineIntel ~793 Mhz
BIOS Version: Dell Inc. A05, 23/03/2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume2
System Locale: en-gb;English (United Kingdom)
Input Locale: en-gb;English (United Kingdom)
Time Zone: (UTC) Dublin, Edinburgh, Lisbon, London
Total Physical Memory: 2,937 MB
Available Physical Memory: 1,399 MB
Virtual Memory: Max Size: 5,872 MB
Virtual Memory: Available: 4,244 MB
Virtual Memory: In Use: 1,628 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server: \\DELLLAPTOP
Hotfix(s): 71 Hotfix(s) Installed.
[01]: 982861
[02]: KB971033
[03]: KB2305420
[04]: KB2393802
[05]: KB2425227
[06]: KB2475792
[07]: KB2476490
[08]: KB2478662
[09]: KB2479628
[10]: KB2479943
[11]: KB2484033
[12]: KB2485376
[13]: KB2487426
[14]: KB2488113
[15]: KB2491683
[16]: KB2492386
[17]: KB2503658
[18]: KB2503665
[19]: KB2505438
[20]: KB2506014
[21]: KB2506212
[22]: KB2506223
[23]: KB2506928
[24]: KB2507618
[25]: KB2507938
[26]: KB2508272
[27]: KB2508429
[28]: KB2509553
[29]: KB2511250
[30]: KB2511455
[31]: KB2515325
[32]: KB2518869
[33]: KB2522422
[34]: KB2524375
[35]: KB2525694
[36]: KB2529073
[37]: KB2530548
[38]: KB2532531
[39]: KB2533552
[40]: KB2533623
[41]: KB2534366
[42]: KB2536275
[43]: KB2536276
[44]: KB2539635
[45]: KB2541014
[46]: KB2544893
[47]: KB2545698
[48]: KB2547666
[49]: KB2552343
[50]: KB2555917
[51]: KB2556532
[52]: KB2559049
[53]: KB2560656
[54]: KB2562937
[55]: KB2563227
[56]: KB2563894
[57]: KB2564958
[58]: KB2567053
[59]: KB2567680
[60]: KB2570791
[61]: KB2570947
[62]: KB2572077
[63]: KB2579686
[64]: KB2586448
[65]: KB2607712
[66]: KB2616676
[67]: KB958488
[68]: KB976002
[69]: KB976902
[70]: KB976932
[71]: KB982018
Network Card(s): 4 NIC(s) Installed.
[01]: Realtek PCIe GBE Family Controller
Connection Name: Local Area Connection
Status: Media disconnected
[02]: Intel(R) WiFi Link 5100 AGN
Connection Name: Wireless Network Connection
DHCP Enabled: Yes
DHCP Server: 192.168.1.254
IP address(es)
[01]: ????
[02]: ????
[03]: Microsoft Virtual WiFi Miniport Adapter
Connection Name: Wireless Network Connection 2
Status: Media disconnected
[04]: Cisco Systems VPN Adapter for 64-bit Windows
Connection Name: Local Area Connection 2
Status: Hardware not present
Hope that this will help.
Thanks again
Regards
Trevor
Maybe you are looking for
-
What is the diffrence between ' Contolfile ' and ' Standby Controlfile' ???
Hi Guru's, Can someone please help me out with the diffrences between a 'Control File' and 'Standby Controlfile'. Thanks in advance Regards, Girish
-
Cracking noise when starting up MacBook Pro
Hey guys, Today I noticed a strange problem concerning my MacBook Pro Retina mid 2012. When starting up, a strange crackling noise appears from I think around the left speaker. The noise appears before the white loading screen of OSX. After starting
-
The other line can't understand me when I talk on my iphone 5.
They say my voice is muffled. The only way they clearly hear me is if I put my mouth directly in front of the bottom of my phone. Then, I can't hear them. The phone does not catch my voice when I have it up to my ear speaking normally. It's not the w
-
I have a view which I create a new button. I'm using a JSONModel to bind data to the button like so: var btnCall = new sap.m.Button('btnCall' { text: "{PHONE}", press: [oController.onCall, oController]}); Not all records have a phone number, in
-
I accidently deleted my "Recently Added" feature in my playlist. How do I get it back?
How do I get my "Recently Added" tool back into my play list if I accidently deleted it?