nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ruckus ICX 7150 with R510 AP seems unstable

unknown

I've had this installed now for about a year without issue, but in the last few months it seems to have destabilized. The R510 seems to occasionally switch off and reboot, and the switch will occasionally lose all communications with the rest of the network, requiring a hard reboot of the switch to get it to start communicating again. The AP is running PoE, but I've checked the PoE allowance, and there is power to spare, so I'm not over-taxing the PoE allotment, and Spanning-tree is on so it should eliminate loop-backs.

This is a sporadic problem, so it's hard to trouble shoot (it rarely fails when I have bunches of free-time, usually when I need to leave in 5 minutes, and I'm already late), so what can I do to further find the source of this problem?

Find more posts tagged with

Accepted answers

All comments

itdept_head_me

I'd check the fans in the switch.
look at the logs after reboot and if possible check the temps.

find out is it the switch or the R510,
it might be the R510 shorting the PPOE & locking up the switch, so really you need to separate them... even if it means thowing in another switch between them tempararaly.. even some cheap ass consumer stuff with a ppoe bridge.

I won't tell you the number of times locked up or stopped fans have thrown our kit out of wack

jijo_panangat

Hello,

'show logging' o/p on the switch will list down any unexpected events during the problem. That might give some clue if its on the switch.

Thanks
Jijo

unknown

First off, It's a 12 port 7150, which unless I'm mistaken are fanless? That doesn't invalidate the temperature thing.

Here's my logging report, you can see where I restarted it towards the end:
Jan 1 00:04:33:I:STP: VLAN 1 Port 1/1/12 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:04:31:I:STP: VLAN 1 Port 1/1/12 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:04:28:I:STP: VLAN 1 Port 1/1/12 STP State -> LISTENING (MakeFwding)
Jan 1 00:04:28:I:System: Interface ethernet 1/1/12, state up
Jan 1 00:04:25:I:System: Interface ethernet 1/1/12, state down
Jan 1 00:04:25:I:STP: VLAN 1 Port 1/1/12 STP State -> DISABLED (PortDown)
Jan 1 00:04:25:I:STP: VLAN 1 Port 1/1/12 STP State -> FORWARDING (PortDown)
Jan 1 00:04:08:I:SNMP: Auth. failure, intruder IP: 192.168.12.20
Jan 1 00:03:56:I:STP: VLAN 1 Port 1/1/6 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:03:54:I:STP: VLAN 1 Port 1/1/12 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:03:54:I:STP: VLAN 1 Port 1/1/6 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:03:52:I:STP: VLAN 1 Port 1/1/12 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:03:51:I:STP: VLAN 1 Port 1/1/6 STP State -> LISTENING (MakeFwding)
Jan 1 00:03:51:I:System: Interface ethernet 1/1/6, state up
Jan 1 00:03:50:I:System: Interface ethernet 1/1/6, state down
Jan 1 00:03:50:I:STP: VLAN 1 Port 1/1/6 STP State -> DISABLED (PortDown)
Jan 1 00:03:50:I:STP: VLAN 1 Port 1/1/6 STP State -> FORWARDING (PortDown)
Jan 1 00:03:49:I:STP: VLAN 1 Port 1/1/12 STP State -> LISTENING (MakeFwding)
Jan 1 00:03:49:I:System: Interface ethernet 1/1/12, state up
Jan 1 00:03:47:I:STP: VLAN 1 Port 1/1/6 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:03:45:I:STP: VLAN 1 Port 1/1/6 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:03:43:I:System: PoE: Power enabled on port 1/1/12.
Jan 1 00:03:43:I:STP: VLAN 1 Port 1/1/6 STP State -> LISTENING (MakeFwding)
Jan 1 00:03:43:I:System: Interface ethernet 1/1/6, state up
Jan 1 00:03:40:I:System: Interface ethernet 1/1/6, state down
Jan 1 00:03:40:I:STP: VLAN 1 Port 1/1/6 STP State -> DISABLED (PortDown)
Jan 1 00:03:40:I:STP: VLAN 1 Port 1/1/6 STP State -> FORWARDING (PortDown)
Jan 1 00:03:31:I:STP: VLAN 1 Port 1/1/6 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:03:29:I:STP: VLAN 1 Port 1/1/6 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:03:27:I:STP: VLAN 1 Port 1/1/6 STP State -> LISTENING (MakeFwding)
Jan 1 00:03:27:I:System: Interface ethernet 1/1/6, state up
Jan 1 00:03:20:I:System: PoE: Power enabled on port 1/1/6.
Jan 1 00:03:12:I:STP: VLAN 1 Port 1/1/1 Bridge TC Event (FwdDlyExpiry)
Jan 1 00:03:12:I:STP: VLAN 1 Port 1/1/1 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:02:59:I:STP: VLAN 1 Port 1/2/2 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:02:59:I:STP: VLAN 1 Port 1/1/11 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:02:59:I:STP: VLAN 1 Port 1/1/9 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:02:59:I:STP: VLAN 1 Port 1/1/4 STP State -> FORWARDING (FwdDlyExpiry)
Jan 1 00:02:57:I:STP: VLAN 1 Port 1/2/2 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:02:57:I:STP: VLAN 1 Port 1/1/11 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:02:57:I:STP: VLAN 1 Port 1/1/9 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:02:57:I:STP: VLAN 1 Port 1/1/4 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:02:57:I:STP: VLAN 1 Port 1/1/1 STP State -> LEARNING (FwdDlyExpiry)
Jan 1 00:02:55:I:STP: VLAN 1 Port 1/2/2 STP State -> LISTENING (MakeFwding)
Jan 1 00:02:55:I:System: Interface ethernet 1/2/2, state up
Jan 1 00:02:55:I:STP: VLAN 1 Port 1/1/11 STP State -> LISTENING (MakeFwding)
Jan 1 00:02:55:I:System: Interface ethernet 1/1/11, state up
Jan 1 00:02:55:I:STP: VLAN 1 Port 1/1/9 STP State -> LISTENING (MakeFwding)
Jan 1 00:02:55:I:System: Interface ethernet 1/1/9, state up
Jan 1 00:02:55:I:STP: VLAN 1 Port 1/1/4 STP State -> LISTENING (MakeFwding)
Jan 1 00:02:55:I:System: Interface ethernet 1/1/4, state up
Jan 1 00:02:55:I:STP: VLAN 1 Port 1/1/1 STP State -> LISTENING (MakeFwding)
Jan 1 00:02:55:I:System: Interface ethernet 1/1/1, state up
Jan 1 00:02:53:I:PKI: Trustpoint DEVICE_TRUSTPNT: Successfully loaded Manufacturing certificate file.
Jan 1 00:02:52:D:DHCPC: Stopped DHCP Client service
Jan 1 00:02:52:I:System: Stack unit 1 POE PS 1, Internal Power supply with 124000 mwatts capacity is up
Jan 1 00:02:51:I:System: Cold start
Jan 1 00:02:51:D:DHCPC: starting dhcp client service
Jan 1 00:02:51:A:DHCPC: No DHCP Servers found on any ports
Jan 1 00:02:51:D:DHCPC: Found static IP address 192.168.12.253 subnet mask 255.255.255.0 on port 1/1/1
Jan 1 00:02:51:I:Security: running-config was potentially changed by operator from console

unknown

Temp shows 136 F (58 C)

itdept_head_me

58 Deg. c i would say it might be ok if that is peak.

check the manufacturers data sheets, not for environmental specs, but log temps that are considered "normal"

Did you have any luck splitting it off thru another switch?
also maybe an NTP so your logs show real date & time info, incase that assists in tracking it down.

jijo_panangat

Hello,

Did you encounter any power outage or power fluctuations at the site ? We can perform a health check on the switch if a support case can be opened.

Thanks
Jijo

unknown

Caveman: I haven't actually done the physical labor of splitting off the AP From the switch yet, but I will get to that when I have a chance, but it may be a few days yet. I will try to get the NTP Set up, thanks for the suggestion.

Jijo: At current, I haven't seen any additional power fluctuations, but historically, after a reboot, it seems to hold stable for awhile, a few weeks before it starts to fluctuate. I'm just trying to keep my eyes on it and get as much in place for the next time it destabilizes so I can gather info. Then I'll likely open a case. I want to make sure it's not something I'm doing or introducing first (no offense, but I've not had great experiences with Ruckus Tech Support in the past, so I try not to involve them unless I absolutely have to).

itdept_head_me

yep.. watch the controller it might be like cisco... no battery backed RTC

Another option is to throw in a vm with "WAZUH" or "naigos" on, to act as log servers... & central NTP maybe a 10-15 minute job.

Sadly from what I have seen certaninly with the 1205
log serves won't work reliably with RUCKUS kit, their log design is rubbish.(im calling it this after filing a request back in 2014 & 2020 to get it fixed)

They allow sub processes of thier kit to report directly without proper device identification stamps.
so if you have a network of a more than 3 deviecs.... good luck of sorting & filtering their log output.
Every line is tagged differently.... , not way to reliably "tree" filter.....

on your other point ,
I've had real good exp. with Ruckus. tech. mind you that was before they got bought out,...
I just returned from retirement..., so lets see how it goes...
Dell sonicwall is far worse.. for outright blocking bugs. they just say "as design" & then close the tickets....

jijo_panangat

Alright, Pls let us know when you get a chance to collect more info.
Sorry to hear about the past experience, We'll ensure a better overall experience if you can give us another chance.

Thanks
Jijo