cancel
Showing results for 
Search instead for 
Did you mean: 

Heartbeat Loss

mjschultz90
New Contributor

Hello!

I am experiencing heartbeat loss on both APs at the exact same time about 12 hours apart but sometimes sooner, then they come back online a minute or two later at the same time. 

This setup was working just fine for about three years before experiencing these issues. There may have been a power outage around the time it started happening but not sure. It does seem to have started happening after I updated the firmware from 200.12 to 200.14

Images below - I also have logs if that is helpful. 

May 24 22:11:25 Ruckus-Unleashed syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [151] s and last disconnected reason [AP Restart : power cycle]
May 24 22:11:26 Ruckus-Unleashed syslog: eventd_to_syslog():AP[4c:b1:cd:28:c4:f0] joins with uptime [151] s and last disconnected reason [AP Restart : power cycle]
May 24 22:11:26 Ruckus-Unleashed syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] cold boot successfully
May 24 22:11:28 RuckusAP syslog: eventd_to_syslog():AP[4c:b1:cd:28:c4:f0] warm boot successfully,last reboot reason [power cycle].
May 24 22:12:31 RuckusAP syslog: eventd_to_syslog():Radio [2.4G] of AP[4c:b1:cd:2a:4e:90] is ON
May 24 22:12:31 RuckusAP syslog: eventd_to_syslog():Radio [5G] of AP[4c:b1:cd:2a:4e:90] is ON
May 24 22:12:32 RuckusAP syslog: eventd_to_syslog():Radio [2.4G] of AP[4c:b1:cd:28:c4:f0] is ON
May 24 22:12:32 RuckusAP syslog: eventd_to_syslog():Radio [5G] of AP[4c:b1:cd:28:c4:f0] is ON
May 25 10:12:13 RuckusAP syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [43398] s and last disconnected reason [Heartbeat Loss]
May 25 10:12:15 RuckusAP syslog: eventd_to_syslog():AP[4c:b1:cd:28:c4:f0] joins with uptime [43400] s and last disconnected reason [Heartbeat Loss]
May 25 22:12:34 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [86619] s and last disconnected reason [Heartbeat Loss]
May 25 22:12:39 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [86623] s and last disconnected reason [Heartbeat Loss]
May 26 10:12:30 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [129815] s and last disconnected reason [Heartbeat Loss]
May 26 10:12:54 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [129838] s and last disconnected reason [Heartbeat Loss]
May 26 22:12:50 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [173034] s and last disconnected reason [Heartbeat Loss]
May 26 22:12:53 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [173038] s and last disconnected reason [Heartbeat Loss]
May 27 10:12:44 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [216228] s and last disconnected reason [Heartbeat Loss]
May 27 10:12:46 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [216229] s and last disconnected reason [Heartbeat Loss]
May 27 22:12:59 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [259442] s and last disconnected reason [Heartbeat Loss]
May 27 22:13:06 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [259449] s and last disconnected reason [Heartbeat Loss]
May 28 10:13:04 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [302646] s and last disconnected reason [Heartbeat Loss]
May 28 10:13:18 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [302660] s and last disconnected reason [Heartbeat Loss]
May 28 22:13:27 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [345869] s and last disconnected reason [Heartbeat Loss]
May 28 22:13:30 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [345871] s and last disconnected reason [Heartbeat Loss]
May 29 10:13:30 RuckusAP 1 syslog: eventd_to_syslog():AP[4c:b1:cd:2a:4e:90] joins with uptime [389071] s and last disconnected reason [Heartbeat Loss]
May 29 10:13:47 RuckusAP 1 syslog: eventd_to_syslog():AP[RuckusAP 1@4c:b1:cd:28:c4:f0] joins with uptime [389089] s and last disconnected reason [Heartbeat Loss]

-----------------

6 REPLIES 6

mjschultz90
New Contributor

Using Unleashed setup. 

 

AP1.jpgSwitch.jpgAP2.jpg

Hi @mjschultz90 

Greetings!!!

Thank you for contacting RUCKUS Lennar Home Community.

Hope you are doing well!!!

Thank you for the detailed information you shared.

As per the case description, I could understand that your RUCKUS setup is not working with a heartbeat loss error.

I would suggest you create a new WLAN/SSID and create a separate 5G network from your Unleashed Access Point to avoid any Wireless interference with 2.4. Please refer to the below link and screenshot. Please refer to the below links to create and new WLAN/SSID.

Creating a New Wireless WLAN (SSID):

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/Creating-a-New-Wireless-WLAN...

Video:

https://www.youtube.com/watch?v=eSl_8rs1QnU

Please let me know if you have any queries in this regard.

Thank you again for your patience.

 

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

AnitaL
New Contributor

Happening to me too! Any solutions?

Hi @AnitaL 

Greetings!!!

Thank you for contacting RUCKUS Lennar Home Community.

Hope you are doing well

As this case is raised by @mjschultz90 

To avoid confusion with posts, you can create your own post with the problem you're facing and a detailed description of the network issue and what you've done so that we can guide you properly.

Thank you again for understanding.

 

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.