Monitoring, Management & Location Tracking

How to do a synthetic testing in AMP

Aruba Employee
Requirement:

AMP : 8.2.3

AirWave supports synthetic testing for the following Aruba access points running ArubaOS 6.5.0.0 or later:


 AP-220 Series
 AP-210 Series
 AP-200 Series


 



Solution:

By using Clarity Synthetic we can make an AP to act like user connections over Wi-Fi to find potential problems in your network.

 



Configuration:

Step 1: Adding the Clarity Engine :

We must add the Clarity Engine in AirWave. AirWave communicates with the Clarity Engine using the WebSocket Secure protocol over Port 60001.

1. In AMP we must navigate to Home > Clarity and open the link to Synthetic. Clarity redirects you to the Add a Clarity Engine page
2. In the Add Clarity Engine tab, click New as shown below:

To check the communication between Airwave and clarity engine, we can check the serverbackend.log in Clarity engine from /var/log/serverbackend.log.

#tail -f serverbackend.log

2016-12-14 19:27:42,878 - amsSyntheticClientBackend - INFO - opened:=>Connection Openend
Waiting for Redis to start ...
Redis-server started/running
Waiting for Gunicorn to start ...
Gunicorn started/running
2016-12-14 20:40:58,819 - amsSyntheticClientBackend - INFO - main:=>Starting => SyntheticClientBackend
2016-12-14 20:40:58,824 - amsSyntheticClientBackend - INFO - amsSyntheticClientBackendInit:=>Got Airwave parameter as wss://10.17.164.17:60001/clarity. Starting connection...
2016-12-14 20:40:59,390 - amsSyntheticClientBackend - INFO - opened:=>Connection Openend
2016-12-14 20:41:01,082 - amsSyntheticClientBackend - INFO - closed:=>Connection Closed

 

In Airwave we can validate the visualrf and clarity log to see the communication message. By navigating to cd /var/log/visualrf/clarity.log & /var/log/visualrf/visualrf.log from CLI:

#tail -f clarity.log
2016-12-20 19:42:28.377 WARN  ClarityStateServiceImpl - TestCount is 0
2016-12-20 19:43:58.852 WARN  ClarityStateServiceImpl - check status of testSuite at this time for f49f42be-4792-411a-3368-550c3ebc1aad status 2
2016-12-20 19:45:29.239 WARN  GetPendingResultsCount - Number of tests that are currently running/scheduled to run in the back-end are: 0
2016-12-20 19:45:29.593 WARN  GetPendingResultsCount - Number of tests that are currently running/scheduled to run in the back-end are: 0
2016-12-20 19:45:33.758 WARN  GetPendingResultsCount - Number of tests that are currently running/scheduled to run in the back-end are: 0
2016-12-20 19:46:34.245 INFO  FetchAllTestServerControl -

Fetching all Test Servers from backend
2016-12-20 19:46:34.247 INFO  FetchAllTestServerControl - All the test server ids are: [10.17.164.55]
2016-12-20 19:46:34.320 INFO  FetchAllTestServerControl

Fetching all Test Servers from backend
2016-12-20 19:46:34.321 INFO  FetchAllTestServerControl - All the test server ids are: [10.17.164.55]
2016-12-20 19:46:34.706 INFO  FetchAllProfilesControl

Step 2: We can use Clarity Synthetic to select the client and target APs:

Clarity Synthetic allows you to batch select any AP. When you select the client and target APs, Clarity Synthetic displays the names of the APs and its folders.

1. Click on Home > Clarity and click the Synthetic link.
2. Click on Schedule Tests.
3. Select the Client AP(s). We can select as many devices as you want from the AP list. Clarity Synthetic only lists devices that are up.
4. Select the Target AP(s). For manual selection, click Select Target AP(s), select one or more devices from the AP list, and then click Define Test Profile as shown below:

 




Verification

Once the test is intiated AMP will do a configuration push to the controller to change the AP mode to synthetic mode:

Tue Dec 20 19:42:00 2016:
>> ap clarity-synthetic ap-name AP-225 amsip-addr 10.17.164.55 forward-mode gre test-id f49f42be-4792-411a-3368-550c3ebc1aad mixed-mode band a

Tue Dec 20 19:42:00 2016:
>> exit

In controller we can execute the following command to confirm the ap mode:

(Aruba7030) #Show ap details ap-name AP-225 | include Mode
Mode                  Clarity-Synthetic  Configuration
Mode                     AP        Configuration

Once the test is completed AMP will do another configuration push to the controller to the change the AP mode:

ap clarity-synthetic ap-name <name> reset  - to reset AP back to AP mode

We can see the results in AMP web page once the test is completed as shown below:

 

 

Aso we can see the test results from the Clarity engine from cd /var/log/containersResults/ as shown below:

 {
    "BSSID": "AC:A3:1E:58:03:D0",
    "INITDATA": {
      "apForwardModeChanged": "FALSE",
      "apForwardingMode": "Campus",
      "greStatus": "SUCCESS",
      "mgmtEntityConfigChanged": "FALSE",
      "result": "Success",
      "startTime": "2016-12-20 14:51:40.113890 UTC",
      "webSocketStatus": "SUCCESS"
    },
    "SUMMARYDATA": [
      {
        "result": "Failed:Test WPA aborted for target BSSID AC:A3:1E:58:03:D0"
      }

Version history
Revision #:
2 of 2
Last update:
‎03-29-2017 05:15 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.