Monitoring, Management & Location Tracking

Problem:

With Clarity Synthetic available with 8.2.3 version of Airwave one can perform synthetic tests to determine issues with client connection with Aruba APs. These tests can be performed from the Home-->Clarity-->Synthetic tests page as shown below.

Please refer to the Airwave Clarity Beta guide for more information on how to perform these tests.

One such test result can show up with the following error message:

Below is a snippet from the Clarity log within Airwave located at /var/log.

2016-12-25 03:06:15.324 WARN  SyntheticTestServiceStartup - Starting ClaritySynthetic App...

2016-12-25 03:06:15.596 WARN  SyntheticTestServiceStartup - Flushing clarity keys

2016-12-25 03:06:21.747 WARN  SyntheticTestServiceStartup - Clarity keys deleted from redis

2016-12-25 03:06:21.758 WARN  SyntheticTestServiceStartup - clarityDatabase dbfileName: clarity_database.xml

2016-12-25 03:06:25.217 WARN  SyntheticTestServiceStartup - Starting Core Services...

2016-12-25 03:06:25.378 INFO  SyntheticTestServiceStartup - waiting for the DatabaseService to bootstrap

2016-12-25 03:06:35.382 INFO  SyntheticTestServiceStartup - Starting ClaritySyntheticService (Websocket)...

2016-12-25 03:07:20.064 INFO  SyntheticTestServiceStartup - Starting ClaritySyntheticWebServer...

2016-12-25 03:07:20.088 INFO  SyntheticTestServiceStartup - Starting HeartbeatMonitoringService...

2016-12-25 03:07:20.093 WARN  SyntheticTestManagerImpl - Reset all APs

2016-12-25 03:07:20.396 INFO  ClaritySyntheticServiceImpl - Akka actor started [pool_size:3]

2016-12-25 03:07:20.396 WARN  ClaritySyntheticServiceImpl - Cert path=/usr/local/airwave/lib/java/airwave.jks secure port is 60001

2016-12-25 03:07:22.009 INFO  log - Logging initialized @68968ms

2016-12-25 03:07:22.932 WARN  ClarityWebServer - secure port -1

2016-12-25 03:07:22.937 INFO  Server - jetty-9.3.7.v20160115

2016-12-25 03:07:23.026 WARN  ClarityWebSocket - secure port 60001

2016-12-25 03:07:23.029 INFO  Server - jetty-9.3.7.v20160115

2016-12-25 03:07:26.097 INFO  ContextHandler - Started o.e.j.s.ServletContextHandler@9378676{/clarity,null,AVAILABLE}

2016-12-25 03:07:26.312 INFO  ServerConnector - Started ServerConnector@7ad58409{HTTP/1.1,[http/1.1]}{0.0.0.0:8081}

2016-12-25 03:07:26.475 INFO  Server - Started @73452ms

2016-12-25 03:07:26.475 INFO  ClaritySyntheticWebServiceImpl - Jetty WebServer started [port=8081]

2016-12-25 03:07:26.774 INFO  ContextHandler - Started o.e.j.s.ServletContextHandler@5c5c14cd{/,null,AVAILABLE}

2016-12-25 03:07:26.775 INFO  ServerConnector - Started ServerConnector@515f7902{HTTP/1.1,[http/1.1]}{0.0.0.0:60000}

2016-12-25 03:07:26.993 INFO  SslContextFactory - x509=X509@3bd8643a(1,h=[10.1.2.13],w=[]) for SslContextFactory@57b93fed(file:///usr/local/airwave/lib/java/airwave.jks,null)

2016-12-25 03:07:27.644 INFO  ServerConnector - Started ServerConnector@7bb233c9{SSL,[ssl, http/1.1]}{0.0.0.0:60001}

2016-12-25 03:07:27.669 INFO  Server - Started @74646ms

2016-12-25 03:07:27.669 INFO  ClaritySyntheticServiceImpl - Jetty WebSocket started [port:60000]

Fetching all Test Servers from backend

2016-12-25 03:09:30.694 INFO  FetchAllTestServerControl - All the test server ids are: []

jsonArray: [{"BSSID":"84:D4:7E:D6:B1:B0","SUMMARYDATA":[{"result":"Failed:Test WPA aborted for target BSSID 84:D4:7E:D6:B1:B0"}],"TESTID":"74ad1040-85fa-fb73-0e28-67d97dad580e","INITDATA":{"webSocketStatus":"FAILURE","apForwardModeChanged":"FALSE","apForwardingMode":"None","mgmtEntityConfigChanged":"FALSE","result":"Failed: Failed to establish gre & websocket connection with syntheticAP","startTime":"2017-01-12 15:24:26.844307 UTC","greStatus":"FAILURE"},"WPADATA":{"startTime":"2017-01-12 15:24:58.083167 UTC","wpaassociation":{"bssid":"84:d4:7e:d6:b1:b0","result":"Success","startTime":"2017-01-12 15:24:58.818505 UTC","time":120,"retryCount":1,"groupText":"Association"},"wpascan":{"result":"Success","startTime":"2017-01-12 15:24:58.085822 UTC","time":715,"retryCount":1,"BSSIDS":[{"scanResultCount":1,"BSSID":"84:d4:7e:d6:b1:b0"}],"groupText":"Scan"},"result":"Failed:Deauth received","wpa4wayhandshake":{"WPAKey4TxRetryCount":0,"WPAKey2TxRetryCount":0,"WPAKey3RXRetryCount":0,"groupText":"4 Way Handshake","startTime":"1970-01-01 00:00:00.000000 UTC","time":0,"retryCount":0,"WPAKey1RxRetryCount":0,"result":"Failed"},"clientMACAddress":"84:d4:7e:d6:b1:bf"}}]

2017-01-12 02:30:11.056 WARN  TestDataHandler - no failed RESULT

2017-01-12 02:30:11.056 WARN  TestDataHandler - no failed Result

2017-01-12 02:30:11.056 WARN  TestDataHandler - result contains failed - setting status to errorFailed: Failed to establish gre & websocket connection with syntheticAP

2017-01-12 02:30:11.056 INFO  TestDataHandler - bldrString is

"ERRORDATA":

[{"BSSID":"84:D4:7E:D6:B1:B0","SUMMARYDATA":[{"result":"Failed:Test WPA aborted for target BSSID 84:D4:7E:D6:B1:B0"}],"TESTID":"74ad1040-85fa-fb73-0e28-67d97dad580e","INITDATA":{"webSocketStatus":"FAILURE","apForwardModeChanged":"FALSE","apForwardingMode":"None","mgmtEntityConfigChanged":"FALSE","result":"Failed: Failed to establish gre & websocket connection with syntheticAP","startTime":"2017-01-12 15:24:26.844307 UTC","greStatus":"FAILURE"},"WPADATA":{"startTime":"2017-01-12 15:24:58.083167 UTC","wpaassociation":{"bssid":"84:d4:7e:d6:b1:b0","result":"Success","startTime":"2017-01-12 15:24:58.818505 UTC","time":120,"retryCount":1,"groupText":"Association"},"wpascan":{"result":"Success","startTime":"2017-01-12 15:24:58.085822 UTC","time":715,"retryCount":1,"BSSIDS":[{"scanResultCount":1,"BSSID":"84:d4:7e:d6:b1:b0"}],"groupText":"Scan"},"result":"Failed:Deauth received","wpa4wayhandshake":{"WPAKey4TxRetryCount":0,"WPAKey2TxRetryCount":0,"WPAKey3RXRetryCount":0,"groupText":"4 Way Handshake","startTime":"1970-01-01 00:00:00.000000 UTC","time":0,"retryCount":0,"WPAKey1RxRetryCount":0,"result":"Failed"},"clientMACAddress":"84:d4:7e:d6:b1:bf"}}]

}]

From the Clarity log we see that there is a failure with regards to the test information requested by Clarity for the specified parameters(SSID & Client).

The error message is due to NAT enabled in contorller for internet access in this case. Once NAT was disabled the test was successful as show in the image below.

The AP system profile used must not have NAT enabled for the Clarity synthetic test to be succesful. If NATed the information will be routed elsewhere and not reach the Clarity engine.