RUCKUS ICX 7150 24P SWITCH UNSTABLE, SWITCHING ON AND OFF PORTS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 09:56 AM
Hello guys,
First of all, i would appreciate any workaround that anyone could give me. I have a large Switch network for a LAN of a univerisity campus here. This network is mixed with switchs HP for the distribution layer and ICX7150 for the access layer, that provides ethernet connection for several Ruckus Access point.
Since day one, we introduce the ICX switchs to the network and configure the APs we have seen that there is an issue regarding the randomly disconnection of the APs, at first, we thought would be the AP configuration or the SZ100 controller. Eventually we discover that the issue could be some sort of problem with the switches, we tried to look up for any kind of trouble and we discovered that maybe could be a RSTP or STP error or phenomenon that could led to randomly switching on and off the ethernet ports, provoking that the APs disconect form the network and get a poorly wifi experiance
.
We suspect that this could be, and connect the APs directly to the HP distribution switches, and now the building where they are, is steady as should be.
But it could be certanily another thing.
What do you think guys?
thanks a lot!
First of all, i would appreciate any workaround that anyone could give me. I have a large Switch network for a LAN of a univerisity campus here. This network is mixed with switchs HP for the distribution layer and ICX7150 for the access layer, that provides ethernet connection for several Ruckus Access point.
Since day one, we introduce the ICX switchs to the network and configure the APs we have seen that there is an issue regarding the randomly disconnection of the APs, at first, we thought would be the AP configuration or the SZ100 controller. Eventually we discover that the issue could be some sort of problem with the switches, we tried to look up for any kind of trouble and we discovered that maybe could be a RSTP or STP error or phenomenon that could led to randomly switching on and off the ethernet ports, provoking that the APs disconect form the network and get a poorly wifi experiance
We suspect that this could be, and connect the APs directly to the HP distribution switches, and now the building where they are, is steady as should be.
But it could be certanily another thing.
What do you think guys?
thanks a lot!
8 REPLIES 8
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 10:39 AM
Maybe it is nothing more than a power problem. Causing the AP to continue to reboot and go through spanning tree again and again.
What firmware are you running on the 7150's???
I ask because with 08.0.70 builds, it auto installs the latest PoE+ firmware, too.
Additionally, do you have the proper network discovery protocol at the edge to detect the APs?
Are you using plain "inline power" (on be default in newer builds) or are you specifically putting the class?
Personally, I would upgrade to a recent build of the FastIron /IronWare OS ensuring you are running 2.1.0 Build 002 or later, and that you at least have lldp turned on with lldp run.
I would try plain, vanilla "inline power" without extra arguments, so the device should get whatever it asks for.
^^^^^^^^^^^^ This is what I would do first.
What firmware are you running on the 7150's???
I ask because with 08.0.70 builds, it auto installs the latest PoE+ firmware, too.
Additionally, do you have the proper network discovery protocol at the edge to detect the APs?
Are you using plain "inline power" (on be default in newer builds) or are you specifically putting the class?
Personally, I would upgrade to a recent build of the FastIron /IronWare OS ensuring you are running 2.1.0 Build 002 or later, and that you at least have lldp turned on with lldp run.
I would try plain, vanilla "inline power" without extra arguments, so the device should get whatever it asks for.
^^^^^^^^^^^^ This is what I would do first.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 12:04 PM
Thanks man, i'll give it a try!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 10:41 AM
P.S. This is what I am currently running though we intend to upgrade to the 08.0.80 branch soon. If you stick with the 08070 series, I am certain they have at least "C" out by now... and that would be more desirable than "B"
UNIT 1: compiled on Apr 3 2018 at 15:27:41 labeled as SPS08070b
(25605164 bytes) from Primary SPS08070b.bin
SW: Version 08.0.70bT211
Compressed Boot-Monitor Image size = 786944, Version:10.1.11T225 (mnz10111)
UNIT 1: compiled on Apr 3 2018 at 15:27:41 labeled as SPS08070b
(25605164 bytes) from Primary SPS08070b.bin
SW: Version 08.0.70bT211
Compressed Boot-Monitor Image size = 786944, Version:10.1.11T225 (mnz10111)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2018 01:46 AM
Please look at the syslogs prior to the problem for any potential trigger.

