Run TCP, UDP, and multicast traffic, using Iperf, between a windows pServer release and a Linux pSer

1. 
   
2. Using the PAN Manager, create a vSwitch using a pair mode rEth with a VLAN id and add it to your LPAN.
   
   
3. Install current Windows test release on a pServer with the newly created vSwitch.
   
4. Install latest RedHat or SuSE release on a pServer in the same frame with new vSwitch.
   
5. Copy Iperf-1.6.5 files onto both pServers.
   
6. Make current test release the publisher and the other release the subscriber.
   
7. Run Iperf to run network traffic in the following manner:
   
   • 
     
   • Use Iperf to run TCP traffic with window size 64K for 5 minutes with the following commands:
     
     • 
       
     • On subscriber: iperf -s -w 64K
     • On publisher: iperf -c {subscriber IP address} -w 64K -i 5 -t 300
   • Use Iperf to run UDP traffic with datagram sizes 128, 4K, and 32K for 5 minutes each with the following commands:
     
     • 
       
     • On subscriber: iperf -s -u -l {datagram size} -w 1M 
     • On publisher: iperf -c {subscriber IP address} -u -l {datagram size} -b 1G -w 1M -i 5 -t 300
   • Use Iperf to run multicast traffic with datagram sizes 1470 and 16K for 5 minutes each with the following commands:
     
     • 
       
     • On subscriber: iperf -s -u -B {multicast bind address--224.0.x.x} -w 1M
     • On publisher: iperf -c {multicast bind address same as above} -u -l {datagram size} -b 1G -w 1M -i 5 -t 300 -T 4
       
8. Switch publisher and subscriber roles and goto step 5.

 

Note: If you havean internal vEth on your Windows pServer Iperf sometimes will bind tothat even though you explicitly state that you want to use the externalIP.  To resolve this issue, disable the internal vEth by right-clickingMy Computer > Manage > Device Manager > Network Adapters anddisable the appropriate network adapter(s).

Also note:Sometimes Iperf will not bind the appropriate vEth to the multicastaddress.  In such instances use the wListen utility to force a certainIP address to bind to the multicast address.

 

Expected Results:

ForTCP traffic, you should see a connection established and there shouldbe little to no bandwidth loss between the publisher and subscriber.

 

For UDP traffic, you should see a connection established and datagram loss for each datagram size should be less than 1%.

 

For multicast traffic, you should see a connection established and datagram loss for each datagram size should be less than 1%.

 

 

<!--@page { size: 21cm 29.7cm; margin: 2cm }H3 { margin-bottom: 0.11cm }H3.western { font-family: "Arial", sans-serif; font-size: 13pt }H3.cjk { font-family: "DejaVu Sans"; font-size: 13pt }H3.ctl { font-family: "Arial", sans-serif; font-size: 13pt }P { margin-bottom: 0.21cm }-->

Examples:

 

1. iperfServer (receiver/subscriber)

 

• iperf1.7–s -u -l 1k –B 224.0.100.2 -w 1G–i 5-T 4 >iperf_multicast_server_log.txt

 

 

1. iperfClient (transmitter/publisher).

 

• iperf1.7–c 224.0.100.2 -u -l 1k –b 400M -w 1G -i 5 -t 600 –T 4 >iperf_multicast_client_log.txt

 

 

Where:

 

-s	Run iperf inServer mode
-c	Run iperf inclient mode, connecting to an iperf server running on a host
-u	Use UDP ratherthen TCP
-l	The length ofbuffers to read/write. Iperf works by writing an array of lengthbytes a number of times.
-w	Sets the socketbuffer size to the specified value
-B 224.0.100.2	Is the MulticastIP Ranges dedicated to QA testing
-b	The UDP bandwidthto send at
-i	Set the intervaltime in seconds between periodic bandwidth
-t	The time inseconds to transmit for
-T	Time to live forout-going Multicast packets
iperf_multicast_server_log.txt	Log file for theiperf Multicast Server
iperf_multicast_client_log.txt	Log file for theiperf Multicast Client

 

 

Results:

 

1.  

   1. Onthe pServer that is designated as the Iperf Server(receiver/subscriber),verify the following when the Server starts up:

 

• TheServer is listening on an UDP port

• Bindingto local address 224.0.100.2 (dedicated Multicast address range)

• Thesocket buffer size is set to 1G

 

Forexample

 

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

Serverlistening on UDP port 5001 =======

Bindingto local address 224.0.100.2 ========

Joiningmulticast group 224.0.100.2

Receiving1024 byte datagrams

UDPbuffer size: 4.00 MByte (WARNING: requested 1.00 GByte) ========

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

[ 3] local 224.0.100.2 port 5001 connected with 192.168.1.20 port32768

[ID] Interval Transfer Bandwidth Jitter Lost/TotalDatagrams

[ 3] 0.0-100.0 sec 4.77 GBytes 410 Mbits/sec 0.013 ms 12/4999622(0.00024%)

[ 3] 0.0-100.0 sec 2245 datagrams received out-of-order

 

 

1.  

   1. Onthe pServer that is running the iperf client(transmitter/publisher),verify the following when the Client starts and finishes:

 

• Verifythat iperf Client is connected to the 224.0.100.2 Multicast IPaddress.

• Verifythat read/write buffer size is set to 1K

• Verifythat the Time to livefor out-going Multicast packets is set to 4

• Verifythat the UDP bandwidth is set to 400M

• Verifythat the socket buffer size is set to 1G

• Verifythat the Interval number is increasing every 5 seconds and that thisnumber is something other than 0.0.

 

AutomationNote: Shortly after you execute the iperf1.7 command, the Interval

numbershould be a number other than “0.0”. If this number

remains“0.0” then the I/O has stopped. The perl script should

wait 5seconds before checking the status of the Interval number.

 

AutomationNote: Below is an example of what the output should look like on the

iperfClient when running the iperf test for 100 seconds.

 

 

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

Clientconnecting to 224.0.100.2,UDP port5001 =========

Sending1024 byte datagrams

Settingmulticast TTL to 4 =========

UDPbuffer size: 1.00 MByte (WARNING: requested 1.00GByte) =======

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

[ 3] local 192.168.1.20 port 32768 connected with 224.0.100.2 port5001

[ID] Interval Transfer Bandwidth

[ 3] -0.0- 5.0 sec 244 MBytes 410 Mbits/sec

[ 3] 5.0-10.0 sec 244 MBytes 410 Mbits/sec ======Trafficstart here

[ 3] 10.0-15.0 sec 244 MBytes 410 Mbits/sec

[ 3] 15.0-20.0 sec 244 MBytes 409 Mbits/sec

[ 3] 20.0-25.0 sec 244 MBytes 410 Mbits/sec

[ 3] 25.0-30.0 sec 244 MBytes 410 Mbits/sec

[ 3] 30.0-35.0 sec 244 MBytes 410 Mbits/sec

[ 3] 35.0-40.0 sec 244 MBytes 410 Mbits/sec

[ 3] 40.0-45.0 sec 244 MBytes 410 Mbits/sec

[ 3] 45.0-50.0 sec 244 MBytes 410 Mbits/sec

[ 3] 50.0-55.0 sec 244 MBytes 410 Mbits/sec ==== Interval# increases

[ 3] 55.0-60.0 sec 244 MBytes 410 Mbits/sec

[ 3] 60.0-65.0 sec 244 MBytes 410 Mbits/sec

[ 3] 65.0-70.0 sec 244 MBytes 410 Mbits/sec

[ 3] 70.0-75.0 sec 244 MBytes 410 Mbits/sec

[ 3] 75.0-80.0 sec 244 MBytes 410 Mbits/sec

[ 3] 80.0-85.0 sec 244 MBytes 410 Mbits/sec

[ 3] 85.0-90.0 sec 244 MBytes 410 Mbits/sec

[ 3] 90.0-95.0 sec 244 MBytes 410 Mbits/sec

[ 3] 95.0-100.0 sec 244 MBytes 410 Mbits/sec

[ID] Interval Transfer Bandwidth

[ 3] 0.0-100.0sec 4.77 GBytes 410 Mbits/sec =======Trafficstops here

[ 3] Sent 4999622 datagrams

 

 

1. 192.168.1.115 (guest) ----  192.168.1.116 (guest)

-- from192.168.1.115
[root@localhost ~]# ./iperf1.7 -s -i 5 > iperf_server_log &

[root@localhost ~]# ./iperf1.7 -c 192.168.1.116 -u -l 256 -b 400M -w 1G -i 5 -t 288000 > iperf_udp_cli_.txt &
 
-- from192.168.1.116
[root@localhost ~]# ./iperf1.7 -s -u -l 256 -w 1G > iperf_udp_srv.txt &

[root@localhost ~]# ./iperf1.7 -c 192.168.1.115 -i 5 -t 288000 > iperf_tcp_cli.txt &

 

2.192.168.16.7 (guest) ----  192.168.16.8(guest)
-- from 192.168.16.7
c:/Documents and Settings/Administrator/desktop> iperf.exe -s

c:/Documents and Settings/Administrator/desktop> iperf.exe -c 192.168.16.8  u -l 256 -b 400M -w 1G -i 5 -t 288000

-- from 192.168.16.8

c:/Documents and Settings/Administrator/desktop> iperf.exe -c 192.168.16.7 -i 5 -t 288000

c:/Documents and Settings/Administrator/desktop> iperf.exe -s -u -l 256 -w 1G