DRAFT AT&T Iperf Mobile Application User Guide (aka Iperf commands 2.0.5....pdf

8/11/2019 DRAFT AT&T Iperf Mobile Application User Guide (aka Iperf commands 2.0.5....pdf

1/7

Useful misc. iperf commands: iperf -v (displays the iperf client software version); iperf -h (displays the iperf help screen)

UDP UL iperf -c -i1 -b -t

TCP UL iperf -c -i1 -tUDP DL iperf -c -i1 -e -a

TCP DL iperf -c -i1 -a

UDP UL iperf -c -i1 -b -t

TCP UL iperf -c -i1 -t

UDP DL iperf -c -i1 -e -a

TCP DL iperf -c -i1 -a

Sample iperf client command parameter options with load balancing across servers (recommended)

Sample iperf client command parameter options withoutload balancing across servers

1See the latest version of the "AT&T Iperf Mobility Test Tool Enhancement and Fixes" document for optional command line parameters and other details.

1See the latest version of the "AT&T Iperf Mobility Test Tool Enhancement and Fixes" document for optional command line parameters and other details.

Note: Commands using two IP addresses are made to support "load sharing" across NTC server pairs . If a test is to be performed to a specific server, use a single IP address.

https://solar.edc.cingular.net/livelink/livelink?func=ll&objId=16760855&objAction=browse&sort=name

Updated October 8, 2014- compatible with iperf windows client 2.0.5.30

(2) The iperf commands listed below require iperf client version2.0.5.30or newer. (Some optional command line parameters are not supported on older client versions.)

(3) Please upgrade your client to version2.0.5.30 immediately, unless required to remain on an older client version for compatibility with third party applications.

(4) Please read the available iperf reference materials for details about the upgrades included in iperf version2.0.5.30. For those with SOLAR access, the latest documents are available at the URL below.

(1) PLEASE READ ALL PAGES WITHIN THIS DOCUMENT FOR IMPORTANT UPDATES.

Printed: 10/8/2014


2/7


3/7


4/7


5/7


6/7

[408] 10.0-11.0 sec 492 KBytes 4.03 Mbits/sec

[408] 0.0-11.2 sec 5.44 MBytes 4.06 Mbits/sec

Process exiting(4308)!

C:\iperf>iperf -c 172.16.254.242:172.16.254.243-i1 -a10

AT&T IPerf 2.0.5.30-wt 10/01/2013 (WIN32 threads)

Instantiated with options -c 172.16.254.242:172.16.254.243 -i1 -a10

UTC - Sat Jul 19 20:12:19 2014

TCP download client.

Computer name FredAllen-PC.

[412] Client 10.32.85.187 port 49302 connected with Server172.16.254.242port 5002

TCP window size: 512 KBytes

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

[412] Server name vnnperftp01.

[412] Time between TCP connect and first byte arrival (TTFB): 0.180 seconds

[ ID] Interval Transfer Bandwidth

[412] 0.0- 1.0 sec 510 KBytes 4.18 Mbits/sec




[412] 4.0- 5.0 sec 1.05 MBytes 8.77 Mbits/sec

[412] 5.0- 6.0 sec 1.07 MBytes 9.01 Mbits/sec






[412] 0.0-11.1 sec 9.31 MBytes 7.01 Mbits/sec

Process exiting(5036)!

OVERVIEW: AT&Ts internal network iperf servers are intended primarily for performance testing. Aligned with that purpose, their IP addresses are typically not routed across the AT&T network. As a result, LTE testers must be awa

path (PGW location) to determine which of the iperf servers will be reachable for that session.

This document describes techniques LTE testers may use to determine their LTE bearer path (PDN Gateway) and related iperf servers. (All LTE testers should use standard APNs, such as "broadband", "phone" or "pta", unless use of a te

a temporary solution to work around network issues.)


7/7

NTC Location Proxy name if Calico zone Proxy Name if NEO zoneAKRON, OH (AKR) akrmsp akrnz

ALLEN, TX (ALN) alnmsp alnnz

ALPHARETTA, GA (ALP) alpmsp alpnz

ARLINGTON, VA (ART) Not applicable: ART does not have Calico artnz

BOTHELL, WA (BTH) bthmsp bthnz

CHICAGO, IL (CHC) Not applicable: CHC does not have Calico chcnz

CONCORD, CA (CNC) cncmsp cncnz

GAINESVILLE, FL (GSV) Not applicable: GSV does not have Calico gsvnz

HOUSTON, TX (HST) Not applicable: HST does not have Calico hstnz

NEW YORK, NY (NYC) nycmsp nycnz

SCHAUMBERG, IL (SCH) schmsp Not applicable: SCH does not have NEO

VAN NUYS, CA (VNN) Not applicable: VNN does not have Calico vnnnz

This method works for virtually all SIMs (regardless of SIM provisioning related to network data compression via the Multi Services Proxy (MSP). If this method does not detect a proxy, an alternate method, or support from AT&T, wil b

example, testers using an Enterprise APN, routing through a NEO zone, may not pass through an MSP.)

* A tester can confirm their bearer path by attaching on LTE and browsing to www.WhatIsMyProxy.comand looking at the first few letters of the detected proxy name indicating the NTC acronym and zone type (Calico or Neo), as expl

BEARER PATH DETERMINATION:

For ALL testing to the AT&T performance servers (hosting iperf and ftp applications), the tester's device should have no other network connections other than the device's LTE connection. Ensure that all other network connections (such

WiFi) are disconnected and/or disabled. Maintaining multiple connections will typically cause a variety of intermittent problems, since the device's operating system will determine which network connection to use for the iperf test traffic

Iperf servers are available in each National Technical Center (NTC), as listed within this document.

Printed: 10/8/2014

DRAFT AT&T Iperf Mobile Application User Guide (aka Iperf commands 2.0.5....pdf

Documents

Transcript of DRAFT AT&T Iperf Mobile Application User Guide (aka Iperf commands 2.0.5....pdf