Skip to main content
jason_hilt's profile

Wed, Feb 3, 2021 2:32 PM

Uplink goes down when AP plugged into switch

New to Ruckus switches.

Have an ICX 7650 with one uplink to an Extreme switch.  ICX is managed by a SZ100.  When I plug in a Ruckus R650 to a port on the ICX switch, 1 gig or 2.5 gig port, the uplink port goes down.  Show Interface says port 1/2/1 is blocking but gives no indication of why it changed to blocking.  Only way I can get the uplink port to enable is if I reboot the switch. 

If I plug in a laptop into a port on the ICX everything works correctly.  We have one default vlan and four tagged vlans on the switch ports and 5 tagged vlans on the uplink.

I have no idea why plugging in an AP takes the uplink port down.  This is happening on 2 different 7650 switches and am assuming it will happen to all of them.  

Any ideas on what configuration needs to be done so the uplink port won't go into blocking?

Here's part of the show int for 1/2/1 when it's being blocked.

Hardware is 10GigabitEthernet, address is c0c5.2073.3531 (bia c0c5.2073.3531)
  Configured speed 10Gbit, actual unknown, configured duplex fdx, actual unknown
  Configured mdi mode AUTO, actual unknown
  Tagged member of 5 L2 VLANs, port state is BLOCKING
  BPDU guard is Disabled, ROOT protect is Disabled, Designated protect is Disabl
  Link Error Dampening is Disabled
  STP configured to ON, priority is level0, mac-learning is enabled
  MACsec is Disabled
  Flow Control is config enabled, oper enabled, negotiation disabled
  Mirror disabled, Monitor disabled

Responses

20 Messages

 • 

300 Points

a month ago

So I deleted the configs in the Smartzone for the switch and remade the 5 vlans we need and assigned them to the ports.  Factory reset the switch and reconnected it to the Smartzone to download the configuration.  Same thing.  Plug in an access point and the main uplink goes down.  Only way to get the link to come backup is to reboot the switch. 

Uplink (Port 1/2/1)  vlans are all tagged 128,232,236,240, and 2801.  No default vlan assigned in Smartzone group config.  After the switch was connected, the switch config now shows vlan 1 as the default vlan assigned to ports 1/2/1-1/2/4 and STP is turned on for all vlans, although it wasn't turned on in the Group config.

Any ideas?

Official Rep

 • 

174 Messages

 • 

2.7K Points

a month ago

Hi Jason,

This looks like spanning tree blocking the redundant ports to avoid a potential loop.

Pls verify the stp configuration on the ports to ensure they are set right.

https://docs.commscope.com/bundle/fastiron-08090-l2guide/page/GUID-B82095D0-61B4-428D-92B2-EEE62A39AF12-homepage.html 

20 Messages

 • 

300 Points

There are no redundant uplink ports.  Port 1/2/1 is the only uplink to the next switch. It only carries the wifi vlans, no management vlan.

Could the management port, which only has one vlan and is not on Port 1/2/1, be causing the issue?  There are no other ports being used when I plug in the AP.  STP is on right now for all normal ports and uplink.  What should it be?  I have tried with it off and on all ports and the uplink still goes down.

I have worked with Cisco and Extreme switches and never had this issue.  Is there something with Ruckus switches that's different in how they handle STP?

3 Messages

 • 

30 Points

Hi Jason, what kind of software are you running. We had a similar issue with ICX and R550, the latest ICX 8.0.95 version in combination with 5.2.1 build 1038 was made the ports flap

We downgraded the switch firmware to 8.0.90j

20 Messages

 • 

300 Points

Switch is on 08.0.95aT231

SZ controller is on 5.2.1.0.515

3 Messages

 • 

30 Points

What is the AP firmware ?

20 Messages

 • 

300 Points

Controller shows it as 5.2.1.0.698, same as all the other APs we have.

Any idea how to enable the uplink port after I remove the AP that causes it to go down?  Right now my only option is to reboot the switch.

289 Messages

 • 

4K Points

a month ago

Also, I have seen incompatibility in STP between different vendors and Enterasys (now owned by Extreme) -- connecting with Alcatel and Cisco in some configurations resulted in blocked ports.

You have to check what exact configuration of STP is on both switches -- is it STP, RSTP, plain or per VLAN, MSTP, etc, and what are exact settings for each protocol for each VLAN on uplink interface on both sides.

But as problem happens  when connecting AP, I would anyway start from disabling mesh, if it is enabled.

(edited)

20 Messages

 • 

300 Points

Mesh is disabled on all APs

Just checked and we are not running STP on the Extreme switches, guess it's disabled by default.  We don't use any redundant links, just LAGs.  Extreme uses MLAG.

Should I just disable STP on the Ruckus switches?  They will only be connected to APs.
I am still at a loss why the uplink port is getting shutdown when an AP is plugged in when there is no loop and the only other port being used is the Management port on it's own vlan.  So it's only the AP port and the uplink ports being used.

(edited)

20 Messages

 • 

300 Points

So I disabled STP on all the vlans on the SZ controller at the group level and switch level.  Couldn't disable it on Vlan 1 as it's the default vlan that we don't use.

On the switch through the CLI, disabled STP globally as it still showed ON in the interface.  Disabled STP directly on the uplink interface 1/2/1.  It now shows off.  Enabled PoE on port 1/1/26 for the AP.......and the uplink port 1/2/1 goes down immediately.  From the log:
Feb 10 11:12:03:I:System: Interface ethernet 1/1/26, state up
Feb 10 11:11:58:I:System: Interface ethernet 1/1/26, state down
Feb 10 11:11:39:I:System: Interface ethernet 1/1/26, state up
Feb 10 11:11:34:I:System: Interface ethernet 1/1/26, state down
Feb 10 11:11:32:I:System: Interface ethernet 1/1/26, state up
Feb 10 11:11:26:I:System: Interface ethernet 1/2/1, state down
Feb 10 11:11:25:I:System: PoE: Power enabled on port 1/1/26.

I am at a total loss of WHY 1/2/1 goes down immediately and WHY I can not get port 1/2/1 to even come back up without having to reboot the whole switch.

Really frustrated with these Ruckus switches at this point.  Never had issues like this with Cisco or Extreme.

3 Messages

 • 

30 Points

If you put the AP on standalone software, for example 114.0.0.0.6565, do you still have the same behaviour ?

https://support.ruckuswireless.com/software/2767-ruckus-solo-access-point-114-0-0-0-6565-ga-software-release-r650

Are you sure you don't have loops in the network ? Did you enable loop-detection maybe ?

20 Messages

 • 

300 Points

No loops.  Switch is a new install that I did.  One uplink to the ruckus.  One link on the management port and the AP is all that's connected to the Ruckus switch.

Plugging in a laptop works just fine.  Uplink stays up, get an IP and can surf the internet.

What would putting the AP in standalone mode do?  AP doesn't even have time to talk to the controller before the uplink goes down.

289 Messages

 • 

4K Points

Hello,

frustration isn't in place. You try to connect 2 different vendors swtcthes together but don't look on STP configuration. MLAG use doesn't mean some form of STP isn't enabled.

Most vendors use different defaults for STP, and such problems are not uncommon when BPDU are not properly understood. Actually, I have seen such problems mainly with Cisco and different brands (because of non-standard PVSTN default used by Cisco) and with Enterasys/Extreme for similar reason. To avoid this, when connecting 2 different brands of switches, you must set compatible STP (STP or MSTP) configuration on both switches, as all switches support standard protocols.

Most probably port is coming down, because some conflicting data are received.

I actually had similar situation when connecting Extreme switch in default config to ALE switch network  by just 1 port put all network down. It was big business center, and nobody new that one of tenants was connecting his switch to network port, just all building network went down at some moments. Admin couldn't understand what is the reason of problem at all, we had to  analyze logs in detail to find location of fault - use of incompatible STP protocols.

(edited)

20 Messages

 • 

300 Points

15 days ago

So figured out the issue, somewhat.  It's a bug in the 95 and 92 versions of the OS software.  The Ruckus tech was totally miffed on what the issue was and had no other advice than to try a downgrade.  I downgraded to 90h and everything works great, with and without STP configured to defaults.  Can unplug/plugin uplinks and APs with no issues now.

Now to downgrade 36 switches that are already installed.