Controller Based WLANs

 View Only
last person joined: one year ago 

APs, Controllers, VIA

How to fix perf-test report connection timed out for tcp? 

Aug 14, 2014 07:09 PM

Question: How to fix perf-test report connection timed out for tcp?

 

Environment: Only AP-130 Series, AP-220 Series, and AP-105 access points connected to a 7200 Series or M3 controller running AOS 6.3 and above support this feature.

 

 

Below are the steps to run perf-test for tcp when controller runs as perf-test server and AP as client.

(Aruba) (config) # perf-test server start controller tcp window 256k
 
NOTE:Please make sure that CP whitelist was configured, permit TCP packets to forward. (TCP portocol number 6, perf-test port 5001)
     If you have done, please ignore this prompt
NOTE:Need to execute 'perf-test port open' because cpsec is enabled
 
 
(Aruba) #perf-test port open  
 
 
(Aruba) #perf-test client start ap ap-name ArubaAP host 172.16.0.254 tcp window 256k duration 10
 
 
(Aruba) #show perf-test reports controller
 
Command Warning:No perf-test reports on this Controller
 
In the datapath session table, we could see 'D' flag for the tcp port 5001.
 
(Aruba) # show datapath session table 192.168.0.13  | include 5001
 
192.168.0.13    172.16.0.254    6    63094 5001   0/0     0 0   0   tunnel 13   5    0         0          FDYC
 
 When show perf-test reports is executed the connection times out.

(Aruba) #show perf-test reports ap ap-name ArubaAP
 
Perf-test: Success
 
 Jul  3 16:12:15 2014
 
connect failed: Connection timed out

In order the reolve the connection timed out issue, we need add an firewall cp acl to allow tcp port 5001 as shown below:

(Aruba) (config) #firewall cp
(Aruba) (config-fw-cp) #ipv4 permit any proto 6 ports 5001 5001

After allowing tcp 5001, we could see perf-test reports successfully for tcp.

(Aruba)#show perf-test reports ap ap-name ArubaAP

Perf-test: Success


Jul 22 14:42:05 2014

------------------------------------------------------------

Client connecting to 100.0.0.1, TCP port 5001

TCP window size:  260 KByte (WARNING: requested  256 KByte)

------------------------------------------------------------

[  3] local 120.0.0.254 port 57435 connected with 100.0.0.1 port 5001

[ ID] Interval       Transfer     Bandwidth

[  3]  0.0- 1.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  1.0- 2.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  2.0- 3.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  3.0- 4.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  4.0- 5.0 sec  11.0 MBytes  92.3 Mbits/sec
[  3]  5.0- 6.0 sec  11.0 MBytes  92.3 Mbits/sec
[  3]  6.0- 7.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  7.0- 8.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  8.0- 9.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  9.0-10.0 sec  11.1 MBytes  93.3 Mbits/sec
[  3]  0.0-10.0 sec   111 MBytes  93.1 Mbits/sec


 Note: Adding firewall cp acl is applicable only for tcp and not for udp.

Statistics
0 Favorited
3 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.