Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARP17: Wrong Connection Established counts #79

Open
SSam009 opened this issue Aug 30, 2018 · 7 comments
Open

WARP17: Wrong Connection Established counts #79

SSam009 opened this issue Aug 30, 2018 · 7 comments
Assignees

Comments

@SSam009
Copy link

SSam009 commented Aug 30, 2018

WARP17 tests ui showing the very high number of Established connections on Server (Port1) when compared to Client ( Port 0) .

@SSam009
Copy link
Author

SSam009 commented Aug 30, 2018

warp17connections

@SSam009
Copy link
Author

SSam009 commented Aug 30, 2018

The above screenshot is just after the test started, Port 1 started with 3 million connections. It is very high compared to port0 connections (150K ).

@dceara
Copy link
Collaborator

dceara commented Aug 31, 2018

@SSam009 can you please share the config file you used and also the cmd line to start Warp17?

Is there a DUT in between? Does it act as TCP proxy for the sessions?

What version of Warp17 are you running?

Thanks,
Dumitru

@SSam009
Copy link
Author

SSam009 commented Aug 31, 2018

@dceara I am using latest code (dev-common) . There is a DUT between the interfaces of the same host, I don't think it acts as TCP Proxy.
WARP LOADGEN HOST NIC1 <----> Switch <----> WARP LOADGEN HOST NIC2

@dceara
Copy link
Collaborator

dceara commented Aug 31, 2018

@SSam009 can you also please share your full config? Was this working with v1.8?

@SSam009
Copy link
Author

SSam009 commented Sep 11, 2018

@dceara
we are using RHEL 7.5, I am not able to compile v1.8 on rhel7.5
here is test config

#PORT 0 - client port
#PORT 1 - server port

add tests l3_intf port 0 ip 100.64.18.3 mask 255.255.255.0
add tests l3_gw port 0 gw 100.64.18.2

add tests client tcp port 0 test-case-id 0 src 130.1.255.10 130.1.255.255 sport 1000 20000 dest 131.0.0.1 131.0.0.5 dport 80 80

set tests timeouts port 0 test-case-id 0 init 0
set tests timeouts port 0 test-case-id 0 uptime 30
set tests timeouts port 0 test-case-id 0 downtime 5

set tests rate port 0 test-case-id 0 open infinite
set tests rate port 0 test-case-id 0 send infinite
set tests rate port 0 test-case-id 0 close infinite

set tests criteria port 0 test-case-id 0 run-time 3600
set tests client http port 0 test-case-id 0 GET google.com /index.html req-size 20

Server configuration

add tests l3_intf port 1 ip 100.64.18.5 mask 255.255.255.0
add tests l3_gw port 1 gw 100.64.18.4

add tests server tcp port 1 test-case-id 0 src 131.0.0.1 131.0.0.5 sport 80 80
set tests server http port 1 test-case-id 0 200-OK resp-size 20

start tests port 1
start tests port 0
show tests ui

@davvore33
Copy link
Collaborator

davvore33 commented Sep 18, 2018

I've tried on my setup with your configuration and I didn't see this problem, can you please post the command line you use to launch warp17 as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants