Controllerless Networks

Reply
Occasional Contributor I

cannot connect IAP 205s to Central

Hi Guys

 

I have multiple IAP205s (ArubaOS (MODEL: 205), Version 6.4.3.1-4.2.0.2) where I have successfully assigned the license and added them to correct Group, after which they fail to download config and are now sitting as 'not connected'. i have 3rd party firewal which is now configured to permit traffic via URL filtering to *.arubanetworks.com

The frustration is i also have multiple exact simiar devices that are connected and good

 

I have compared the 'show tech-support' output captured from both a connected and not connected IAP and discovered the not connected IAP appears to be stuck in an 'awc' loop as follows: -

 

Aug 3 11:40:18 awc[1834]: wsc: connect to server 52.10.81.96
Aug 3 11:40:18 awc[1834]: wsc: central connection exist, destroy it first.
Aug 3 11:40:18 awc[1834]: wsc: create a wss connection address 52.10.81.96, port 443
Aug 3 11:40:18 awc[1834]: wsc lib: Initial logging level 967
Aug 3 11:40:18 awc[1834]: wsc lib: Library version: 1.2
Aug 3 11:40:18 awc[1834]: wsc lib: Configured without extension support
Aug 3 11:40:18 awc[1834]: wsc lib: Started with daemon pid 0
Aug 3 11:40:18 awc[1834]: wsc lib: static allocation: 4444 + (12 x 1024 fds) = 16732 bytes
Aug 3 11:40:18 awc[1834]: wsc: callback_central(1275) LWS_CALLBACK_OPENSSL_LOAD_EXTRA_CLIENT_VERIFY_CERTS
Aug 3 11:40:18 awc[1834]: wsc lib: libwebsocket_client_connect: direct conn
Aug 3 11:40:18 awc[1834]: wsc lib: libwebsocket_client_connect_2
Aug 3 11:40:18 awc[1834]: wsc lib: libwebsocket_client_connect_2: address 52.10.81.96
Aug 3 11:40:18 awc[1834]: wsc: callback_central(1294) LWS_CALLBACK_ADD_POLL_FD, add fd 8 to dispatcher, fds fd 8.
Aug 3 11:40:18 awc[1834]: wsc lib: nonblocking connect retry
Aug 3 11:40:18 awc[1834]: wsc: callback_central(1328) LWS_CALLBACK_SET_MODE_POLL_FD POLLOUT, add fd 8 to dispatcher.
Aug 3 11:40:18 awc[1834]: wsc: Waiting for connect...
Aug 3 11:40:18 awc[1834]: wsc: wsc_service_wd_fd(1507), poll write, sevice fd 8
Aug 3 11:40:18 awc[1834]: wsc lib: libwebsocket_client_connect_2
Aug 3 11:40:18 awc[1834]: wsc lib: libwebsocket_client_connect_2: address 52.10.81.96
Aug 3 11:40:18 awc[1834]: wsc lib: connected
Aug 3 11:40:18 awc[1834]: wsc: callback_central(1328) LWS_CALLBACK_SET_MODE_POLL_FD POLLOUT, add fd 8 to dispatcher.
Aug 3 11:40:18 awc[1834]: wsc: wsc_service_wd_fd(1507), poll write, sevice fd 8
Aug 3 11:40:19 awc[1834]: wsc: LWS_CALLBACK_CLIENT_CONNECTION_ERROR
Aug 3 11:40:19 awc[1834]: wsc: connect status is 3, prapare to send to cli.
Aug 3 11:40:19 awc[1834]: wsc: send papi message to cli, appid 1, type 2, raw message len 9.
Aug 3 11:40:19 cli[1837]: wsc: parse_wsc_msg(1547) receive message type 2, message size 2
Aug 3 11:40:19 cli[1837]: wsc: [WSC_CENTRAL] State WSC_STATE_CONNECTING Event WSC_EVENT_CONNECT_RETRY Next state WSC_STATE_CONNECTING
Aug 3 11:40:19 cli[1837]: wsc: org server name 52.10.81.96, server name 52.10.81.96, len 11. proxy
Aug 3 11:40:19 cli[1837]: wsc: send papi message to awc, appid 1, type 1, raw message len 116. use_payloadfile=0
Aug 3 11:40:19 cli[1837]: wsc: cli_wsc_start_connect_retry_timer(328): start connect retry timer.
Aug 3 11:40:19 awc[1834]: wsc: callback_central(1308) LWS_CALLBACK_DEL_POLL_FD, remove fd 8 from dispatcher.
Aug 3 11:40:19 awc[1834]: wsc: receive message from cli, len 116
Aug 3 11:40:19 awc[1834]: wsc: receive message type 1, payload_type=1
Aug 3 11:40:19 awc[1834]: wsc: connect to server 52.10.81.96
Aug 3 11:40:19 awc[1834]: wsc: central connection exist, destroy it first.

 

and so on continusly ....................

 

Am I going mad or does the line 'central connection exist, destroy it first' indicate the backend server has an open connection with my IAP which must be closed before connectivity is established???

 

Thanks for any assistance!!!!!

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: