Monitoring, Management & Location Tracking

 View Only
last person joined: one year ago 

Articles relating to existing and legacy HPE Aruba Networking products and solutions including AirWave, Meridian Apps, ALE, Central / HPE Aruba Networking Central, and UXI / HPE Aruba Networking User Experience Insight

Clarity Synthetic Firewall requirements 

Mar 26, 2017 03:23 PM

Q:

Is there any port to be allowed between the clarity synthetic engine and the controllers / APs, to be able to start the Clarity Synthetic test?



A:

Communication ports needed by Clarity Synthetic engine-

 

Airwave to controller  - it needs SSH access, port number 22.

Airwave to Clarity engine - TCP  port number 60001. It is currently hard coded.

Clarity engine to AP - Gre tunnel, TCP Port number 1723 

 

The GRE tunnel will be handling all traffic to perform the Clarity Synthetic test. Primarily the clarity engine telling the AP (which is simulating client behavior) what operations to conduct. So it's usually a json message with the test request containing which SSID (or specific BSSID) to connect to, which username/authentication to use, which band to attempt connecting on, destinations for dns/ping/pageload/traceroute, and whether or not to run iperf3 test. All passwords are encrypted in the communication.

 

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.