Showing results for 
Search instead for 
Did you mean: 

Is consistence heartbeat lost normal?

New Contributor II

I have to monitor a group of R310 indoor AP remotely. It been few days that the log on VSZ show heartbeat lost. 
Is there any way that I can make this log not appear. Not not showing the log but make the problem cause the log to appear solve.

Also on few days back, few AP show 15 to 20 constant heartbeat lost in a day and in short time period. Making the AP down and user can't connect to the network. Is this normal or there something I should be cautious for?

Image_ images_messages_61a042673cf5db55dc754fb0_7b3df9e444cb6e2db01b0a98bfb67e25_Annotation20211126100302-8e94ec65-fd96-403b-afe0-b6f986ded32c-1770521009.png


Hi @nur_faizatul_nadiah_bt_anuar 

The heartbeat lost between an AP/SZ indicates connectivity issue in between. For such issue's you would need to initiate packet capture on AP eth and SZ eth to identify where packet is dropping or having issue. I would suggest to open a Ruckus TAC case to identify where the connectivity is getting lost. If all the AP's are connecting to SZ over WAN we can also try increasing the AP/SZ Heartbeat timer from default 30 sec to 300.

To open a case please reach out to us :

Below are the events that take place for HB lost:

1. If SZ fails to receive 2 consecutive heartbeats from an AP, SZ will generate a heartbeat lost event. Default settings dictates that this happens after 60 seconds have elapsed without receiving heatbeats.
2. SZ will continue to generate heartbeat lost events up to a period of 300 seconds (5 minutes) of consecutive lost heartbeats.
3. If 300 seconds elapses without hearing a heartbeat, SZ will generate an 'apConnectionLost' event and report the AP as Offline in the GUI. This means 10 heartbeats must be missed before the AP is reported as Offline.

Best Regards