Looking for 200.10.10.5.229 Feedback

[daniel_m]

Hello community!

So is anyone here running 200.10.10.5.229 at home with great success?  I'm considering upgrading for the latest security fixes and to be on the "latest and greatest," but I am a bit worried about bringing too much "ruckus" to my home network in the form of incompatibilities due to too much IoT and other legacy wireless devices.

So, anyone here with a varied home network have "200.10.10.5.229" Just Work with no issues or have seen it improve things?

Cheers.

[daniel_m]

I'm the OP and decided to upgrade; I shouldn't have.  Like @veno77, my network breaks once a week with a heartbeat loss.  In looking at this further, it appears it might be PoE related.  Port 2 is the R710.

In the past I had issues with the R710 and manually configured the PoE Operating Mode for 802.3at to allow the R710 to have full power.  After the first heartbeat loss with 200.10, I removed this manual configuration, but the issue persists.  The R610 has the default configuration and does not appear to have an issue.

Logs from the controller:

Jun 15 14:47:45 Ruckus-Unleashed syslog: eventd_to_syslog():AP[R710@58:b6:33:3b:18:30] joins with uptime [307] s and last disconnected reason [Heartbeat Loss] 
Jun 15 14:48:02 R710 syslog: eventd_to_syslog():AP[R610@30:87:d9:03:8a:c0] joins with uptime [86] s and last disconnected reason [AP Restart : application reboot] 
Jun 15 14:48:04 R710 stamgr: stamgr_update_reboot_info():AP[30:87:d9:03:8a:c0] reboot detail:/usr/sbin/election  election: The unleashed network have another master and the priority is less than it, reboot.  
Jun 15 14:48:04 R710 syslog: eventd_to_syslog():AP[R610@30:87:d9:03:8a:c0] warm boot successfully,last reboot reason [application reboot].

Logs from my switch:

I 06/15/21 14:42:24 00077 ports: port 2 is now off-line
W 06/15/21 14:42:24 00562 ports: port 2 PD Over Current indication.
I 06/15/21 14:42:24 00565 ports: port 2 PD Removed.
W 06/15/21 14:42:26 00562 ports: port 2 PD Over Current indication.
I 06/15/21 14:42:28 00560 ports: port 2 PD Detected.
I 06/15/21 14:42:28 00561 ports: port 2 Applying Power to PD.
I 06/15/21 14:42:30 00076 ports: port 2 is now on-line
I 06/15/21 14:43:19 00077 ports: port 2 is now off-line
I 06/15/21 14:43:22 00076 ports: port 2 is now on-line
I 06/15/21 14:44:15 05824 ports: Port 3: PD stopped responding to LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will be retained.
I 06/15/21 14:46:27 00077 ports: port 3 is now off-line
I 06/15/21 14:46:31 00076 ports: port 3 is now on-line
I 06/15/21 14:46:31 05824 ports: Port 3: PD stopped responding to LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will be retained.
I 06/15/21 14:47:11 00077 ports: port 3 is now off-line
I 06/15/21 14:47:14 00076 ports: port 3 is now on-line

More info from the switch; it appears the R710 is not negotiating LLDP:

  Available: 195 W  Used: 26 W  Remaining: 169 W

 PoE    Pwr  Pwr      Pre-std Alloc Alloc  PSE Pwr PD Pwr  PoE Port    PLC PLC
 Port   Enab Priority Detect  Cfg   Actual Rsrvd   Draw    Status      Cls Type
 ------ ---- -------- ------- ----- ------ ------- ------- ----------- --- ----
 1      No   low      off     usage usage  0.0 W   0.0 W   Disabled     0   -
 2      Yes  low      off     usage usage  5.6 W   5.3 W   Delivering   4   2
 3      Yes  low      off     usage lldp   5.8 W   5.6 W   Delivering   4   2

I had no issue here with 200.9.