6513 stp root bridge and Dell powerconnect 5316 issue

Hi everyone,
have this issue with root bridge on on a vlan being learnt incorrectly by itself from another vlan.
The topology is this
6513        vlan 10       interface f4/10   Dell 5316 interface g11   vlan 1
                vlan 20       interface f4/20                   interface g16   vlan 20
The 6513 vlan 10 priority 12228                 Dell configured with classic stp and priority 32768
                vlan 20 priority 8192
pvst+ used on ios 12.1 (i know really old, but going to be de-commissioned any way).
Now on the cisco switch a show spanning-tree vl 20 it is entered and reports its the root for this vlan, ok correct there.
But when this is done for vlan 10 it reports that the root brodge is via f4/10 with the priority and mac address of vlan 20.
Somehow this shows that vlan 10 is getting bpdu's via the Dell 5316 from vlan 20 . The blade server connectivity is fine.
Thanks for any advice
Cheers
TJ.

Hi Reza,
Inherited issue. The ports are set to access. The servers are regular Windows servers (2008).
I agree would have been a better configured setup done that way with an etherchanel.
Also I noted that the interfaces on the Dell are set to untagged.
Cheers
TJ.

Similar Messages

1300 Root-Bridge and Non-Root Bridge setup

I have two 1300s that I am trying to set up as Root Bridge and Non-Root Bridge, however, everytime i specify one of them as a Non-Root bridge, the radio0 interface becomes disabled. The only option that i am able to pick that enables the radio0 interface is "Access Point", which is what am trying to avoid it being.
Can anybody help me figure out how to go about this

A non-root's radio will show as disabled if it cannot find the root AP to associate to. Make sure you have "infrastructure-ssid" configured under the SSID on both the root and non-root bridges. Also depending on code versions you may have to configure the distance command under the radio interface on the root.

Root-Bridge and Non-Root Bridge Support

I was wondering if the ISR Routers (Cisco 1811w) support the root-bridge and non-root-bridge feature. If not is there another device apart from the 1310 and 1410 bridges that support this feature?
Thank You,
VT

Hi VT,
The ISR AP supports both of these roles;
Access Point Link Role Flexibility
Access Point Link Role Flexibility allows access point radios to operate in a combination of radio roles,
such as access point root, bridge root (with or without clients), bridge nonroot (with or without clients).
This provides a more flexible deployment scheme to support the various applications requirement. Note
that the ISR AP does not support access point repeater and WGB.
Wireless Non-Root Bridge
The wireless non-root bridge allows the access point radio to operate as the remote node in a point to
point or point to multi-point network.
Wireless Root Bridge
The wireless root bridge role provides support for both point-to-point or point to multi-point bridging.
http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn1800xj.html
Hope this helps!
Rob

Cisco 2950 and Dell Powerconnect 5224

I am trying to Cascade a cisco 2950 and dell powerconnect 5224. I am connecting port 32 on the 2950 and port 24 (gigport) on the dell. Any idea on how I can get the cascading to work? This is what I have on the Dell and the cisco.
Dell Powerconnect 5224:
interface ethernet 1/24
switchport allowed vlan add 1 untagged
switchport native vlan 1
switchport mode trunk
switchport allowed vlan add 1,10 tagged
Cisco 2950:
interface FastEthernet0/32
switchport access vlan 10
switchport mode trunk
Dell documentationon casdcading between powerconnect and catalyst 4000 talks about setting up GVRP on both the dell and cisco switches. However, 2950 doesn't have GVRP.
http://www.dell.com/downloads/global/products/pwcnt/en/app_note_4.pdf
Any ideas, tips. Thanks.

Try this instead:
Dell:
interface ethernet 1/24
switchport allowed vlan add 1 untagged
switchport native vlan 1
switchport mode trunk
switchport allowed vlan add 10 tagged
Cisco 2950:
interface FastEthernet0/32
switchport mode trunk
switchport trunk allow vlan 1,10
switchport nonegotiate
You don't need "switchport access vlan 10" on the Cisco because it's not in access mode, it's in trunk mode. And on the Dell you don't want vlan 1 to be tagged and untagged.
Good luck.

How to find out Secondary STP Root bridge in cisco switche network

Hi, i need to find out Root Primary and Root Secondary bridge in all my offices.
sh spanning-tree summary command can tell me which switch is root bridge primary, but how can i find secondary root easily with some simple command?
sh spanning-tree summary
Switch is in pvst mode
Root bridge for: VLAN0001-VLAN0002, VLAN0005, VLAN0008, VLAN0031

I'm not sure if there is a simple way of finding the bridge with the SECOND best priority.

ISCSI and Dell PowerConnect 6224

We have a Virtualization project in the early design stages utilizing VMWare and a iSCSI SAN environment.
We are a Cisco only data center at present, but one vendor quote has all Dell equipment included.
For switching they have specified the PowerConnect 6224 (24 Gbit ports).
A second vendor quote is all IBM equipment, but leaves out the network switching equipment (our choice).
I'd like to keep our data center a Cisco only environment. I need to understand what Catalyst switch(s) would be comparable
to the PowerConnect 6224. A 24 port switch was quoted. May need a pair for failover depending upon
Today we use a pair of Cisco Catalyst 3750G (24 port) L3 switches for our core distribution environment.
Any advice would be appreciated.
Thanks,
Joe

Joe Campbell:
Why do you need to keep it an all-Cisco shop?
My shop deployed the Dells and we loved them. Just set up and walk away.
The Dell PowerConnect 6200 and 8000 series switches are very competitive. The 6224's 24-gig ports operate at wire speed with a non-blocking backplane, plus a zero-loss throughput. They offer up to four 10G SFP+, XFP, 10G-Base-T and CX4 uplinks. They also offer stackability of up to 12 switches (576 ports), advenaced QoS and security features.
The Dell 6200s are also iSCSI optimized, which no Cisco switch offers.
Read the tolly Group's reviews.
http://www.dell.com/downloads/global/products/pwcnt/en/tolly_pwcnt6200_test.pdf
If you want to know which Cisco switch offers the same functionality, go to Cisco's website and match them. But be assured that the Cisco switch will be anywhere between 3 to 5 times the cost of the Dell 6200s.
HTH

Root bridge and Non rootbridge as backup link (point to Point)

I want to use 2 APs as backup link. I want to be sure that this wireless link is working fine as a backup.
In order to avoid loops, Should I set any specific configuration in both APs?

Follow the URl for the configuration of the Backup Controllers which may help you :
http://www.cisco.com/en/US/docs/wireless/controller/5.1/configuration/guide/c51lwap.html#wp1249029

Network Design - Root and Non root bridges

Hi,
We have a network set-up as the below image. Where the switches have STP enable to handle the muliple paths for the data to flow.
What I would like to know is should the 2 bridges plugged into the same switch e.g Switch A (Bridge A and Bridge B) both be root bridges and (Bridge C and Bridge D) both be non root.
Or should for example, Bridge A be a root and Bridge C a non root and Bridge B a non root and Bridge D the root?
Similarly with the rest of the other bridges E, F, G and H
Thanks

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
Ah, I think I understand. So the wireless bridges are "transparent" to the rest of the network. They just convert wired to wireless and back again.
If I have that right, we can ignore them and just consider your switches.
In that case, it appears you have two L2 loops, those formed by the dual paths between switches A and B and between switches C and D. From a topology standpoint, it doesn't seem to matter what switch you select as root and secondary root. However, as switches B and C are the interior switches, I would suggest those as your root and secondary root switches.

STP Loop after root bridge reload

10 3560 Switches with RSTP enabled and with default bridge priorities and with redundant links between.
One bridge is elected as RSTP root, redundant links are blocked. Setup is stable.
What happens if the root bridge is reloaded ?
Are there loops in the network after reload ?
br Fritz

Fritz
The short answer is no there should not be any loops if the root switch is reloaded because RSTP should elect a new root bridge and build a new loop free topology.
There will however obviously be an outage while the switches work out a new topology.
There will also be an outage when the reloaded switch comes back online because if it was root before because of it's lower bridge ID then it will become root again when it is fully up and running.
But you should not see any loops.
Note the word "should" because you can never be fully sure.
If you are proposing to do this on a live network you should always schedule an outage for this sort of thing because you never know what could happen.
Jon

Can one Root Bridge support multiple non-root bridges?

Hey gang,
I have a pretty simple question here I think
I have a wireless bridge currently setup to support a separate office building on our property about 200 yards away from the main building. The wireless bridge has been working great and was a much cheaper solution when compared to the cost of making a fiber drop to this building. The needs of our business have changed (go figure), to include a warehouse building also on the backside of the property. It's not feasible to run a cable between these two building either. So I need to create another wireless bridge to this back warehouse as well. My question is can I just use another non-root bridge to link to the root bridge already in place, or does each wireless bridge require one root bridge and one non-root bridge?
I have good LoS to both buildings from where the current root bridge is, so if two non-root bridges can talk to one root bridge I should be able to just an additional non-root bridge and be good to go. But if wireless bridges are meant to be a one to one setup, then I'll need to setup an additional root bridge to link to the new non-root bridge?
It seems like you should be able to have one root bridge link to multiple non-root bridges but I haven't been able to find any clear examples of this being done.
Thanks in advance for the help!

That was just too easy.
I copied the configuration from the working non-root bridge to my laptop. I changed out the ip address of the BVI interface. I uploaded the configuration to the new 1300 bridge. I plugged it in and pointed the yagi antenna in the general direction of the original root bridge and started pinging the new 1300. Success!
I'll use my spare 1300 to get service up and running in the warehouse by the end of the week and I'll just need to order one more 1300 to make sure I have spare on hand if needed.
Thanks again!

Two root bridge in same network

Dear Team,
As I checked, there are two root bridge in the same LAN.
We have 6500 which is manually configured as root bridge and this is showing root for all the vlans in the network. Once switch connected to 6500 through 4500 is showing root for the vlans that not assigned to any of the port. Please help to clear it.
Setup
Cisco 6500 -- Cisco 4500 -- Cisco3560 -- Cisco 3560
Cisco 6500
CORE_SW#show spanning-tree root detail
VLAN0001
Root ID Priority 24577
Address 0025.84d9.ac80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0002
Root ID Priority 24578
Address 0025.84d9.ac80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Cisco 3560 Second
Access#show spanning-tree root de
VLAN0001
Root ID Priority 24577
Address 0025.84d9.ac80
Cost 16
Port 28 (GigabitEthernet0/4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0002
Root ID Priority 32770
Address 000a.b8ff.be00
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Here, I have not assigned any port in vlan 2 and this is showing root bridge for vlan 2. In which cases such thing can happen?
Thank You,
Abhisar.

By default, Cisco switches run one spanning tree instance per VLAN and negotiate the topology with other connected switches. If your 3560 believes it is the root for VLAN 2 and there are no ports using VLAN 2, it will consider itself the to be the root because it hasn't been able to negotiate a topology for this VLAN with any other devices. This is normal. Once ports are connected to VLAN 2 and the 3560 can talk to the other switches, the spanning tree will be renegotiated and should behave as you expect.
If you want to have a single spanning tree topology for all VLANs and avoid this behaviour, consider moving to a single-instance MSTP configuration.

Non-root bridges associating with each other.

We have a point to multi-point bridge setup with 3 BR1310s. One is set to be a root bridge and the other two are set to be non-root bridges. From past experience (not to mention Cisco documentation) I would expect the 2 non-roots to associate to the root. What is happening is that one of the non-roots associates with the root and the other non-root associates with the first non-root. The good bit is that everything still works, the puzzling bit is why this is happening, the bridges are physically in a V pattern so there's no reason for the second non-root to behave as it is, even if we force it off the first non-root it just jumps right back in there again. Bridges are all running 12.3.4-JA.

Configurations of both non-root bridges attached. I've just found out that the customer has mounted the second non-root bridge in such a way that there is probably no line of site to the root bridge (failing to follow clear instructions!) which explains why we can't get it to associate with the root bridge but doesn't explain how it can associate with the other non-root. The only thing I can think of is that both are "non-root with clients" and the second bridge is being accepted as a client rather than a bridge.

1310 Root Bridge will not Authenticate with 350 Non Root Bridge

I've exhausted myself solving this issue.
I have a 1310 set as a root bridge using WEPS. I have a 350 set as a non root bridge/without clients, also using WEPS (they both use the same SSID)
The 350 will not authenticate to the 1310. After doing a Carrier Busy Test, it is clear the 350 see's the 1310 with signal strengh of 100 percent.
(I have a test lab setup in my office)
If I make the 350 the Root Bridge and the 1310 the Non Root, The 1310 will authenticate to the 350.
I hoping someone else has seen this problem and can enlighten me.
Thank you.

I have successfully configured a 1310 Bridge as a Root Bridge and a BR350 Bridge and a Non Root Bridge/with Clients. I also had to force the 1310 to operate at 11MB only.
As soon as I make the BR350 Bridge a Non Root Bridge/without Clients, the authentication is dropped between the two.
I was hoping I could transition to the 1310 one unit at a time since I have over a dozen 350's to replace.

1310 Root with two non-root bridges

I have a Cisco 1310 root bridge and a 1310 non-root bridge . it worked fine for a year, I then installed one more 1310 as a non-root bridge now I?m seeing both of my non-root bridges dropping offline more and more. I checked my first non-root bridge today and the radio is down and I can?t seem to bring it back up. I have recently upgraded the tar to see if that would fix the problem. This problem started when I added my second non-root bridge. Did I miss some setting or something

Make sure the spanning tree protocol is disabled on Vlan interfaces

AP1200 as Root Bridge: Accept wireless clients or not?

Cisco's docs precisely contradict themselves on this topic. In some places they state clearly that configuring an AP1200 as a root bridge means it will NOT accept connections from normal wireless clients. In other places they state just as clearly that in root bridge mode an AP1200 WILL accept connections from both non-root bridges and normal wireless clients.
Which is correct?

Yes, I discovered that after setting up several units and running some experiments. At first all I saw were the options offered in the "express setup" area. The root-bridge choice there says nothing about wireless clients, and the help screen it invokes says it won't work. But on the radio interface config screen the option you mention is offered and ITS help screen notes wireless clients will be accepted (as its name implies).
The telnet interface offers all the options as well.
I can confirm that it does work: In root-bridge with wireless client mode the unit will accept associations from non-root bridges, other AP1230's in WGB mode, and even non-Cisco clients.
The testing continues... thanks!

6513 stp root bridge and Dell powerconnect 5316 issue

Similar Messages

Maybe you are looking for