AP shows as down when it is not actually down

Hello,

due to some routing changes etc. we now have several APs that cnMaestro reports as down but the APs are actually still up.  cnMaestro shows all the SMs as up as well.  If I reboot the APs cnMaestro will then show them as up but that's disruptive to service.  is there any way to "kick" the AP to get it to comminucate with cnMaestro again?

AP version: 15.1.3

cnMaestro version: 1.6.3-r15

attached is the device agent log from the AP.

12/21/2018 : 05:31:54 MDT : : Not received PONG for the last ping (1)
12/21/2018 : 05:35:38 MDT : : Not received PONG for the last ping (1)
12/21/2018 : 05:35:59 MDT : : Not received PONG for the last ping (2)
12/21/2018 : 05:36:27 MDT : : Not received PONG for the last ping (3)
12/21/2018 : 05:36:49 MDT : : Not received PONG for the last ping (4)
12/21/2018 : 05:37:14 MDT : : Not received PONG for the last ping (5)
12/21/2018 : 05:37:14 MDT : : Missed 5 consecutive PONGS, disconnecting with server
12/21/2018 : 05:37:23 MDT : : callback_websocket: LWS_CALLBACK_CLOSED
12/21/2018 : 05:37:23 MDT : : Attempting (re)connection in 5 seconds
12/21/2018 : 05:37:44 MDT : : Timeout in select() - Cancelling!
12/21/2018 : 05:37:44 MDT : : OpenConnection to 65.117.210.11:443 failed
12/21/2018 : 05:37:44 MDT : : Unable to discover cnMaestro URL (re-discover in 357 seconds)
12/21/2018 : 05:37:44 MDT : : Attempting (re)connection in 5 minutes
12/21/2018 : 05:57:36 MDT : : Not received PONG for the last ping (1)
12/21/2018 : 05:58:01 MDT : : Not received PONG for the last ping (2)
12/21/2018 : 05:58:24 MDT : : Not received PONG for the last ping (3)
12/21/2018 : 05:58:49 MDT : : Not received PONG for the last ping (4)
12/21/2018 : 05:59:06 MDT : : Not received PONG for the last ping (5)
12/21/2018 : 05:59:06 MDT : : Missed 5 consecutive PONGS, disconnecting with server
12/21/2018 : 05:59:19 MDT : : callback_websocket: LWS_CALLBACK_CLOSED
12/21/2018 : 05:59:19 MDT : : Attempting (re)connection in 5 seconds
12/21/2018 : 05:59:40 MDT : : Timeout in select() - Cancelling!
12/21/2018 : 05:59:40 MDT : : OpenConnection to 65.117.210.11:443 failed
12/21/2018 : 05:59:40 MDT : : Unable to discover cnMaestro URL (re-discover in 309 seconds)
12/21/2018 : 05:59:40 MDT : : Attempting (re)connection in 5 minutes
12/21/2018 : 06:32:00 MDT : : Not received PONG for the last ping (1)
12/21/2018 : 06:32:19 MDT : : Not received PONG for the last ping (2)
12/21/2018 : 06:35:35 MDT : : Not received PONG for the last ping (1)
12/21/2018 : 06:35:51 MDT : : Not received PONG for the last ping (2)
12/21/2018 : 06:36:17 MDT : : Not received PONG for the last ping (3)
12/21/2018 : 06:36:33 MDT : : Not received PONG for the last ping (4)
12/21/2018 : 06:36:51 MDT : : Not received PONG for the last ping (5)
12/21/2018 : 06:36:51 MDT : : Missed 5 consecutive PONGS, disconnecting with server

We've had this happen as well although it's pretty rare. Other then rebooting the AP, we haven't found a non-intrusive way to bring them back to life with cnMaestro.

You can try disabling/enabling the remote management setting on AP GUI, it will re-initialize the agent 

Rupam

i tried that.  it requires a reboot to enable/disable.

1 Like

I would love to know how to quietly /non disrutptively get them back alive on cnmaestro as well. This is super irritating. I have 5 AP's right now that are in limbo.