Monitoring, Management & Location Tracking

Ping test from Clarity Synthetic fails
Problem:

Within Clarity Synthetic it is possible to perform a ping test from the Home-->Clarity -->Synthetic tests page as shown below.

 

It is possible that the ping test can fail with the following error message.

 



Diagnostics:

From the controller CLI, using the audit trail command we can see why the ping test failed.

#show audit-trail 20

Jan 12 09:36:45  fpcli: USER:airwave@192.168.64.207 COMMAND:<encrypt disable > disallowed

Jan 12 10:13:59  fpcli: USER:airwave@192.168.64.207 COMMAND:<ap clarity-synthetic ap-name "CAP2" amsip-addr 192.168.64.208 forward-mode gre test-id "afb76cd7-b44a-40d5-ab96-ba9ac8cbeaa9" mixed-mode band a > disallowed

Jan 12 10:16:43  fpcli: USER:airwave@192.168.64.207 COMMAND:<no paging > -- command executed successfully

Jan 12 10:16:43  fpcli: USER:airwave@192.168.64.207 COMMAND:<ap clarity-synthetic ap-name "CAP2" reset > disallowed



Solution

It is clear from the message above that Airwave users are not allowed to send or receive information from AP it is monitoring. This happens when Airwave is added with a read-only user on the controller. The controller thinks that the added user does not have enough rights for the ping test to go through. Changing the user rights and placing the user as root user will fix the problem.

Once the user is added as root with full access the following messages can be seen on contorller CLI for audit trail command output and the ping test will also be successful.

Jan 12 10:16:43  fpcli: USER:airwave@192.168.64.207 COMMAND:<no paging > -- command executed successfully

Jan 12 11:20:46  fpcli: USER:airwave@192.168.64.207 COMMAND:<encrypt disable > -- command executed successfully

Jan 12 11:21:16  fpcli: USER:airwave@192.168.64.207 COMMAND:<ap clarity-synthetic ap-name "CAP2" amsip-addr 192.168.64.208 forward-mode gre test-id "74ad1040-85fa-fb73-0e28-67d97dad580e" mixed-mode band a > -- command executed successfully

Jan 12 11:22:13  fpcli: USER:airwave@192.168.64.207 COMMAND:<ap clarity-synthetic ap-name "CAP2" reset > -- command executed successfully

Version history
Revision #:
2 of 2
Last update:
‎03-29-2017 05:52 AM
Updated by:
 
Labels (1)
Contributors
Comments
rey90

The Command could be executed successfully in the audit log. But the GUI tells me the following error:

Failed: Failed to establish gre & websocket connection with syntheticAP

 

AOS: CTL 7005 6.5.1.4

Airwave: 8.2.3

Search Airheads
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.