IP Traffic Generator User Guide
IP Traffic Generator User Guide
User Guide
The content of this User Guide is provided for informational use only. It is subject to change without
notice, and must not be used as a commitment by ZTI Communications.
ZTI Communications could not be liable for any direct or indirect damages caused by the software
or User guide imperfection.
The elaboration of this guide has been made to be as accurate as possible. We hope that you will
find all the information required to use our software in a convenient way. Failing to do so, do not
hesitate to contact us at support@[Link].
Except when allowed by license agreement between ZTI Communications and User, no part of this
guide or the software may be reproduced, transmitted in any form or by any means.
To contact us:
ZTI Communications
1 rue Ampère
22300 LANNION
France
Copyrights
Copyright ZTI Communications 2015. All rights The software described in this manual is protected by a License
reserved. An Orange licensed product. Agreement and may only be used in accordance with the terms of this
agreement.
No part of this manual may be copied, reproduced, translated or recorded by any mean without prior written consent from
ZTI Communications. All products and company names mentioned in this document are trademarks or registered
trademarks of their respective owners.
This is an agreement between you (legal entity or physical person) and ZTI Communications.
COPYRIGHT
The enclosed Software and documentation (here after called the Products) remains the property of ZTI
Communications. French copyright laws and international treaties protect the products. ZTI Communications grants
you the right to use the products according to the following:
SOFTWARE PROTECTION
IP Traffic – Test & Measure with its add-ons is licensed on a workstation basis. You will need to purchase a separate
license for each machine that you install it on. Each licensed copy of the software installed on a workstation has:
- a unique Site Code that requires the corresponding unique Site Key to be entered
- or a unique USB Software Protection Key to be plugged
to run the software.
LIMITED WARRANTY
The software is supplied without any express or implied warranty regarding the performances or results obtained by the
use of the Products.
ZTI Communications warrants that the software media (i.e. CD-ROM) will be free of material defects for a ninety (90)
days period following purchase. The limited warranty applies to the media and not the information contained on it. If the
media does not comply with this limited warranty, the only remedy is the replacement of the media software. In no event,
ZTI Communications will be liable for any kind of direct or indirect damages caused by the Products.
COURT OF LAW
French laws will govern this agreement.
The court of Saint-Brieuc (France) shall finally settle all disputes arising out of or in connection with this Agreement.
Table of Contents
PART 0 Preface
All modern versions of Microsoft Windows are supported - from XP to Windows 8 with 32-bit or
64-bit environment, including Windows XP, Windows Server 2003, Windows Vista, Windows
Server 2008, Windows Seven and Windows 8, Windows 10 and Server 2012.
Pentium processor with 512 MB memory
1024 x 768 display
25 MB free hard disk space
0.3 References
[IPV6-XP] [Link]
[RFC1889] “RTP: A Transport Protocol for Real-Time Application” explaining the jitter
calculation.
Interface Generic term used to reference a NIC (LAN adapter), a connected RAS
connection (ISDN, ADSL, Modem) or a tunneling path.
Tooltip A tooltip is a popup window displayed when you move the mouse over a sensitive
area. IP Traffic - Test & Measure displays the tooltip during 5 seconds.
Automation Automation is an add-on scripting tool used to pilot automatically IP Traffic - Test
& Measure.
ZTI Communications Technical Support can assist you with all your technical problems from
installation to troubleshooting. Before contacting our Technical Support, please read the relevant
sections of the product documentation and the “Read Me First” file.
Before contacting our technical support, make sure you record the following information:
Product name and version.
Demo version or licensed product.
System configuration.
Problem details: settings, error messages...
If the problem is persistent, give the details of how to create the problem.
PART 1 Overview
1.1 General Description
IP Traffic - Test & Measure is a connection and data generation tool for IP networks. Data flows
use TCP (Transmission Control Protocol), UDP (User Datagram Protocol) or ICMP (Internet
Control Message Protocol) protocols, which are used by mailing exchanges, file transfers, ping
programs and World Wide Web transmissions.
Various testing configurations can be implemented using more than two PCs. IP Traffic - Test &
Measure establishes TCP, UDP or ICMP connections between PCs through IP networks.
IP Traffic - Test & Measure is an IP software testing tool using the Microsoft Windows TCP/IP
stack (Winsock2 interface). So, IP Traffic - Test & Measure is independent of any transmission or
telecom link and can use any transmission link managed by the Windows operating system: LAN
(Ethernet, Token-ring, hyperlan...), WLAN, WAN (modem, ISDN, ATM, ADSL, FTTx, satellite
link...), remote access, mobile or cellular networks.
IP IP Traffic – Test & Measure can be used to get high accuracy measurements by using optional
hardware providing a very precise time reference thanks to both the Time Devices synchronized by
GNSS receivers GPS devices or Network Time Servers).
IP Traffic - Test & Measure is composed of four modules: ‘IP Generator’, ‘IP Answering’,
‘Traffic Sniffer’ and ‘Traffic Observer’.
IP Generator IP Answering
IP Answering IP Generator
Up to 16 connections
Caption Traffic
Echoed traffic
‘Traffic Sniffer’ is able to capture traffic files at the driver level (under the TCP/IP stack) in
order to calculate traffic statistics and to add a timestamp to the IP packets and to put them into
a file. The ‘IP Generator’ module can replay these traffic files.
IP Traffic - Test & Measure can be used to capture IP traffic with the ‘Traffic Sniffer’: for
example, the IP flows between a mobile and an application server (web, video telephony...) can
be captured and saved in a file. IP packets are time-stamped, to replay IP traffic with the same
timing as for the capture. The user can then use an internal IP Traffic - Test & Measure
algorithm in order to obtain two traffic files (traffic client file and traffic server file). These traffic
files can be used by the IP Traffic - Test & Measure generator as source traffic.
‘Traffic Observer’ is a powerful graphic tool to display and visualize traffic statistics of IP
connections. Statistics are displayed in real time [on-line mode] or by using an off-line mode
[user can replay traffic files by using a 'video recorder' mode (play, pause, stop) with index
management].
‘Traffic Observer’ online mode displays real time statistics for the ‘IP Generator’ or the ‘IP
Answering’ modules.
‘Traffic Observer’ offline mode provides QoS statistics as ‘Packet Erasure Rate’ and ‘Packet
Transit Delay’.
IP Traffic - Test & Measure can be operated with two main modes:
The normal mode: the user can access all commands and functionalities
The remote control mode: the user can’t access locally commands of IP Traffic - Test &
Measure. It’s mainly used for control by a remote IP Traffic - Test & Measure system. It’s
very useful for example to use an IP Traffic - Test & Measure system as a server that the
user can operate remotely.
The design of the IP Traffic - Test & Measure man machine interface offers a main window
allowing easy access to all functionalities and commands. Counters and indicators give an
overview of the overall traffic activities.
1.2 Architecture
To get a good accuracy to timestamp IP packets, additional time devices are available as
described in the following paragraph.
When no additional hardware is used the ‘Traffic Sniffer’ uses the PC internal clock to timestamp
sent and received IP packets. Because the PC internal clock can’t provide an absolute time
reference and needs to be synchronized with all the PCs internal clocks used by IP Traffic - Test
& Measure, ZTI Communications recommends an additional time device to allow a precise
calculation of the propagation delays through IP networks.
z050 Timing & Navigation Module: GPS USB Dongle with PPS (Pulse
Per Second usable for timing applications via serial port emulation).
Based on the Trimble technology (Trimble OEM), this sensitive GPS
receiver acquires autonomously GPS satellite signals and quickly
generates reliable position in extremely challenging environments and
even under poor signal conditions. It is recommended to use an outdoor
antenna for best results.
z150 Series: GNSS Multi Receivers Platform for Timing & Navigation
(Static or mobile application) in robust aluminum enclosure.
3 models available:
* Model P200 (GPS): 1 port RS232 + 1PPS-out
* Model P300 (GPS): 1 port RS232 + 1 port USB + 1PPS-out
* Model P400 (GPS, GLONASS, GALILEO, COMPASS): 1 port RS232
+ 1 port USB + 1PPS-out
Operating temperature range: -30°C (-22°F) to +85°C (185°F).
Designed to provide an accurate pps (pulse per second) signal to use in
measurement and industrial applications, this GPS/Glonass/Galileo
timing module is designed to be used in indoor or outdoor static
applications, requiring accurate time stamp reference information. It
delivers accurate pps signal, even in very poor signal level
environments (indoor, urban canyons and obscured environments) or
when only 1 satellite is visible and being tracked..
As an example, z250 NTP Time Server has been designed around the
Trimble® BD910 GNSS receiver module, originally for applications
requiring high accuracy from multiple GNSS constellations in a very
small enclosure. Mobile platforms can now embed proven Trimble RTK
technology using a very compact enclosure 108.5 x 84 x 30mm form
factor. z250 supports the L1 frequency from the GPS, GLONASS,
Galileo, and Compass constellations. Customers benefit from the
Ethernet connectivity available from RJ45 connection, allowing high
speed data transfer and configuration via standard web browsers. USB
and RS-232 are directly available from the enclosure..
Accuracy for
Configuration Absolute Time reference
Measurement
Undefined
IP Traffic – Test & Measure None or user defined.
(PC clock used)
YES, provided by the time device
IP Traffic – Test & Measure + z150 Series unit (Serial synchronized by the GNSS
5 milliseconds
or USB port) chipset (GPS, GLONASS, etc.).
Absolute reference.
YES, provided by the time device
IP Traffic – Test & Measure + z050 (USB GPS dongle) synchronized by GPS. Absolute 1 millisecond
reference.
IP Traffic – Test & Measure + NTP Time Server (e.g. YES, provided by the NTP Time
z250) Server synchronized by GNSS
1 millisecond
chipset (GPS, GLONASS, etc.).
(one unit for multiple PCs running IP Traffic – T&M) Absolute reference.
The ‘IP Answering’ module receives traffic (up to 16 simultaneous connections), and operates
for each connection following different working modes: ‘Absorber’, ‘Absorber file’, ‘Echoer’,
‘Echoer file’ ‘Generator’ or ‘Disable’.
We will consider hereafter that the local machine is used for generating IP traffic and the
remote one is used for IP answering.
Connection # n
Local IP Generator Remote IP Answering
(Absorber mode)
Connection # m
Remote IP Answering
Local IP Generator
(Absorber File mode)
Connection # p
Remote IP Answering
Local IP Generator
(Generator mode)
Connection # q
Remote IP Answering
Local IP Generator
(Echoer mode)
Connection # r
Remote IP Answering
Local IP Generator (Echoer File mode)
Statistics: different statistics parameters are displayed by the IP Answering module for each
connection:
Sent throughput
Received throughput
Sent packet throughput
Received packet throughput
Sent data volume
Received data volume (volume of data sent by the remote)
Sent packets
Received packets (packets sent by the remote)
Data volume to send
Remaining volume (of data to send)
Seq. numb errors (sequence numbering errors)
Data not echoed
Jitter
These statistics can be saved in a CSV file defined by the user.
Sent and received IP packets are time-stamped by the ‘Traffic Sniffer’ and then saved in a file to
generate capture traffic files.
The user can define IP filters to capture IP traffic in a file.
From one traffic file captured by the ‘Traffic Sniffer’, an analysis algorithm produces two data files
as shown below (because a traffic file contains IP packets sent and received):
Analysis algorithm
Then it is possible to use a data file generated in order to replay traffic via the 'IP Generator'
module:
The ‘Traffic Observer’ online mode displays real time statistics for the ‘IP Generator’ or the ‘IP
Answering’ modules.
The ‘Traffic Observer’ offline mode provides QoS statistics as ‘Packet Erasure Rate’ and ‘Packet
Transit Delay’. But some QoS statistics as the packet Transit Delay need to have time-stamped
packets from the local and the remote systems.
The off-line (batch mode) statistics are obtained using the two traffic files, File A and File B,
produced by the local and remote ‘Traffic Sniffer’ containing the sniffed traffic. Then, the ‘Traffic
Observer’ uses these files in order to calculate off-line statistics.
Export statistics in a CSV file with filters defined by user (the GPS location is also exported
in this CSV file).
Reset statistics
Help window
IP Traffic - Test & Measure performs the RFC 2544 with 2 differences:
1) It doesn't support the automatic recognition of the throughput.
2) Consequently, it doesn't generate the resulting graph for the automatic recognition of the
throughput.
IP Traffic - Test & Measure performs latency calculation for each packet, and then calculates
the average value, where RFC2544 expects the latency calculation for ONE packet in the flow of
120 seconds long (then calculate the average for 20 tests).
The RFC 2544 latency can be calculated using a script that gets 1 value returned from IP Traffic
- Test & Measure for each test of 120 seconds long.
Multicast feature
IP Traffic - Test & Measure is able to generate and receive Unicast and Multicast IP
traffic (IPv4 and IPv6). The multicast feature is used for UDP protocol only.
IP Traffic - Test & Measure is able to generate and receive Broadcast IP traffic (IPv4
only). The broadcast feature is used for UDP protocol only.
IP version selection
Please note that IP Traffic - Test & Measure supports IPv6 for Windows XP and later versions.
IPv6 is not installed by default under Windows XP and Server 2003: it should be added on the
network interface you want to use.
IP Traffic - Test & Measure supports the IPv6 numerical address format (128 bits long) as well as
canonical addresses. The IPv6 multicast is available with IP Traffic - Test & Measure in
accordance to RFC 2373 where a multicast IPv6 address starts with FF. With IPv6 the maximum
size of the packet to avoid fragmentation is 1440 bytes whereas it is 1460 bytes in TCP with IPv4.
Interface selection
The interface selection of a LAN card (NIC), a virtual NIC such as an IP tunneling protocol or a
remote access is useful to control the data traffic hardware route.
IP Traffic - Test & Measure is able to generate and receive Unicast, Multicast or Broadcast IP
traffic on a selected interface, giving the user a deeper control where data are exchanged and
makes multiple routes definition easily.
We have noticed that some operating systems may choose automatically the best network
interface to use when several NICs are plugged on the same network when it comes to
network interface selection. In that case, data can be sent on one interface and received on
another one.
A command is used to set parameters and/or activate a function of IP Traffic - Test & Measure.
For example the Set and Start connection(s) command helps to set parameters for IP connections
and to start the traffic on these connections. With such command you specify the IP address, port
number, protocol, packet size, inter packet delay, duration, etc. and you start the traffic generation
for these connections.
An instruction is used by the Automation Tool to create an internal process. For example, the Wait
Date/Time instruction suspends the scenario execution up to the specified date and time before to
continue.
By using the Automation Tool for IP Traffic - Test & Measure you can:
Set automatically the parameters of the IP Traffic - Test & Measure software,
Start and stop IP connections based on timers,
Execute the scheduled operations in accordance with your own timing,
Make repetitive tests operations automatically,
Simplify the tests reproduction,
And more…
To upgrade the software from the versions 1.3, 2.0 up 2.7 to the version 2.8, please refer to
paragraphs below.
The contexts created with versions 2.0 and higher are reused automatically. When saved, they
become the new 2.8 context file format.
The scenarios created with older versions are reused automatically. When saved, they become
the new 1.7 scenario file format.
* To run IP Traffic - Test & Measure your computer screen resolution must be at least
1024 X 768 and the DPI setting should be set up with the “Normal size (96 DPI)” value.
* To install IP Traffic - Test & Measure for Windows XP, Server 2003 or 2008, Vista,
Seven or 8, you must log on with the administrator rights.
We recommend that you shutdown first your anti-virus application before installing IP
Traffic - Test & Measure. Please note that you should mask the task bar in a
1024x768 screen resolution, so you get an optimal view of the software interface.
The installation procedure is a standard installation program for Windows that needs Administrator
rights.
Then run Setup_IPTrafficBundle.exe from this temporary directory to launch the setup.
First, insert the IP Traffic - Test & Measure CD-ROM in your CD-ROM drive.
Click on “Start”, “Execute” or “Run…” and type
CD unit>: \ Setup_IPTrafficBundle.exe
Follow the instructions until reaching the IP Traffic – T&M package selection window.
The setup procedure detects and installs automatically the 32-bit or 64-bit version
depending of your target operating system.
To use the IP Traffic - Test & Measure software, there are 3 license schemes:
Package #1: the IP Traffic - Test & Measure Trial package allows you to use IP
Traffic - Test & Measure during 15 days after the first run. When the trial period
has expired, the license should be purchased.
Package #2: the IP Traffic - Test & Measure Software Protection Key package
has been designed for users owning a Software License key and for the users of
the previous versions of IP Traffic - Test & Measure. It keeps your current
installation and files, without additional requirement.
Package #3: the IP Traffic - Test & Measure USB Software Protection Key
package requires a USB key with the IP Traffic - Test & Measure license. The
USB key is provided with IP Traffic - Test & Measure from version 2.5. This
package allows the installation of IP Traffic - Test & Measure on several PCs but
the only PC able to run IP Traffic - Test & Measure is the one having the USB key
plugged in.
As previous users, you may be interested to move to a USB Software Protection Key:
please contact your distributor or ZTI Communications to get more details about the
license migration program (see 4.3 IP Traffic - Test & Measure & USB Software
Protection Key for more details).
This software is licensed on a per workstation basis. This means that you need to get a
separate license for each machine you will run it on. The license may be a software key
(for previous users) or the USB Software Protection Key. Each licensed copy of the
software gets a USB Software Protection key (except for customers with Electronic
Software Delivery) that can be moved from one machine to another one.
The USB Software Protection Key contains only the license information.
The software is available on a separate CD-ROM.
Depending on your needs, please find here below the package most suitable for you.
This paragraph is dedicated to the users owning a previous version of IP Traffic - Test & Measure.
… and I want to upgrade and use the USB Software Protection Key I bought
In that case, choose the Package #3 “Customers with Software Protection using a USB Key”.
Plug the USB Software Protection Key before launching IP Traffic - Test & Measure.
… and I will receive the CD-ROM & USB Software Protection Key in a few days
In that case, choose the Package #2 “Customers with a Software Protection Key”.
You will get a fully functional but time-limited Software Protection Key.
The IP Traffic - Test & Measure installation procedure installs the following files on your hard
disk:
[Link]: program file
IP Traffic - Test & Measure User Guide: PDF file (use the free version of Adobe® Acrobat®
Reader® software available on [Link]).
Aut_IPTraff.exe: program file (Automation tool)
Automation Tool for IP Traffic - Test & Measure User Guide: PDF file
IP Traffic license help file (with the Software Protection Key package only)
Automation scenario samples and other files required by the software
Samples of sniffed traffic files
[Link]: program file installed with the USB Software Protection package only
[Link] : allows running IP Traffic as administrator (for Windows Vista only)
[Link]: a text file that contains information about the versions and the Registry
parameters.
All files created by IP Traffic - Test & Measure are saved in the folder where
IP Traffic - Test & Measure has been installed.
The installation procedure automatically installs the packet capture driver named ‘[Link]‘ on
your system in the ‘IP Traffic’ installation directory.
If the RPC mechanism is disabled, a message will ask automatically for the system reboot
at the end of the installation. This is mandatory to allow the dialog between the Automation
Tool and IP Traffic - Test & Measure.
With the Package #2 “Customers with a Software Protection Key”, install the software on the target
computer and refer to the paragraph “4.2.2 Software Protection Key Transfers” to know how to
transfer the software license.
You are now able to use IP Traffic - Test & Measure during the next 15 days.
When you press the OK button, IP Traffic - Test & Measure will stop running.
To continue to use the software please contact your local distributor or ZTI Communications to get
a permanent license.
If you want to configure your Software Protection Key before the time-limited period end, press
Enter just after launching the IP Traffic - Test & Measure when the following message is
displayed:
At the end of the trial period when you launch IP Traffic - Test & Measure, the same
license configuration window appears, but saying “Program not authorized” instead of
showing the remaining days of use.
To get the Site Key and obtain a permanent license, please send an email to contact@zti-
[Link] with the following information:
a. The Site Code (you can copy and paste the Site Code displayed in the license
window)
b. The name of the software: IP Traffic - Test & Measure
c. The OS used
d. Your details
e. The purchase order's number and date of purchase
We will then email you the Site Key. You can now close the license's window.
After you have received the email with the Site Key, open the license configuration window again
by pressing the Enter key as explained before. Copy the Site Key in and then click "Validate". After
validation of the Site Key, you will get the following message:
Important: one Site Code is associated with one Site Key, and only one. A Site Code is
unique for each PC installed. For security reasons, as soon as you validate a Site Key
(trial or unlimited), the Software License program generates a new Site Code
automatically.
For any question or further information, please contact our technical support:
Email: support@[Link]
Phone:+33 2 9613 4003
When you launch IP Traffic - Test & Measure with a Software Protection Key
related to a permanent license, you will see the following window:
A Software Protection Key transfer is not a duplication of any type. Please contact ZTI
Communications or your authorized distributor for site Software Protection Key information
and for several Software Protection Keys purchase.
Software Protection Keys can be transferred using one of the following methods:
Direct transfer: move the Software Protection Key to another directory of the same PC or
between two PCs linked to the same network.
Transfer by media: move the Software Protection Key from a source PC to a target PC by
using a USB key or an external hard disk.
Direct Transfer: move the Software Protection Key from one local directory to
another
This transfer mechanism must be used to move a Software Protection Key in two cases:
- From a source to a target directory of the same PC
- From a source to a target directory of networked PCs
First, copy the program (copy the IP Traffic - Test & Measure folder) to the target directory.
For example from “C:\Program Files\IP Traffic” to “C:\Temp\IP Traffic”
Then run the program from its original directory (from “C:\Program Files\IP Traffic”). When the
Software Protection Key configuration window appears, press Enter and select “License >
Transfer to directory …” in the License menu as shown below:
Provide the path name of the target program (for example C:\Temp\IP Traffic \[Link])
The Software Protection Key is now transferred to the new directory.
To transfer the Software Protection Key from the source PC (PC #1) to the target PC (PC #2),
proceed as described in the following order:
2) Run the software on PC #2 and kill the time-limited license in order to get an unauthorized
license on this PC.
If the "Transfer in from another computer …" item of the license menu is disabled,
you must kill the time-limited license.
When the license configuration window appears, press Enter and select “License > Kill license”
in the license menu.
Click 'OK' and the license configuration window displays now "Program not authorized":
3) Select “License > Transfer in from another computer …” in the License menu:
5) Go to the source PC (PC #1) and insert the media (USB key or external hard disk). Then start
the program on PC #1. When the license configuration window appears, press Enter and select
“License > Transfer out to another computer …” as shown below:
Input the media path (USB key) and then press "Next >".
When the license is put on the media, you get the “Program not authorized” message:
You can check that the license is not available anymore on the source PC since the IP
Traffic - Test & Measure software license is on a workstation basis. Contact us to get
information on a Site Software Protection Key (contact@[Link]).
4.3 IP Traffic - Test & Measure & USB Software Protection Key
The USB Software Protection Key is the most flexible way to transfer your license to any other PC.
Plug it in the computer you want to use IP Traffic - Test & Measure on.
If you are a user of a previous version of IP Traffic - Test & Measure (version 2.4 and under)
change for more flexibility to a USB Software Protection Key by contacting ZTI Communications
Sales Offices (sales@[Link]) and get some information about how to exchange
your software key to a USB Software Protection key.
To uninstall IP Traffic - Test & Measure select “Uninstall IP Traffic - Test & Measure” in the “Start
> Programs > IP Traffic - Test & Measure” menu.
Anti-virus or firewall applications may disrupt IP Traffic - Test & Measure when sending
or receiving data.
Please set up your security software before using IP Traffic - Test & Measure
(see PART 7 and 0).
New users can use this help as an introduction to IP Traffic - Test & Measure and generate or
receive traffic with the IPv4 protocol in a few clicks.
Just after launching IP Traffic - Test & Measure, the Getting Started Window is displayed:
Depending on your choice to use 1 or 2 PCs, the plan below shows the steps:
Step 1
Use 1 or 2 PCs
Then press the "Start IP Generator and IP Answering" button to continue. The "IP Generator –
Traffic + Statistics" tab of IP Traffic - Test & Measure will display the two first active connections
as shown on the following window:
If you select the option: I use two PCs, read the following instructions.
IP Traffic - Test & Measure must be installed on the two PCs.
Then choose if you want to generate or receive the traffic on this PC.
If you select "Use the IP Generator" the following window will appear:
After pressing the "Start the IP Answering" button, a warning message will appear:
Press "OK" and the "IP Answering – Parameters + Statistics" tab of IP Traffic - Test & Measure is
displayed on PC #2.
Then go to PC #1 and start the IP Traffic - Test & Measure IP Generator. The "IP Generator–
Traffic + Statistics" tab of IP Traffic - Test & Measure displays now the two first active
connections.
For Vista and after, you must have the administrator rights to be able to use the DSCP field.
To launch IP Traffic with the administrator rights, right-click on the IP Traffic - Test &
Measure shortcut as shown above and choose “Run as administrator”.
After a few seconds and depending on your license, you will get one of the following license
windows:
With some Windows O.S., the window below may appear. This window allows configuring the
Windows Firewall settings for IP Traffic - Test & Measure.
Click on the “Unblock” button to add IP Traffic - Test & Measure into the authorized programs list.
Anti-virus or firewall applications may disrupt IP Traffic - Test & Measure from sending
or receiving data. Please set up your security software before using IP Traffic - Test &
Measure.
Windows Firewall may also disrupt the IP Traffic - Test & Measure performances. To get
best performances, you should disable Windows Firewall.
To use a NTP Server under Window Vista, the ICMP exchange must be allowed. Please
refer to the paragraph 8.3 “How to authorize ICMPv4 and ICMPv6 traffic under Windows
Vista.”
Some anti-virus configurations can stop IP Traffic - Test & Measure working because of their
security settings. For commercial anti-virus, please refer to the related documentation to authorize
IP Traffic - Test & Measure to work.
Step1: Open a command prompt window. You should be logged on an account giving the
administrator rights to be able to modify the firewall configuration.
Make sure that "C:\Program Files\IP Traffic\" is the installation directory of IP Traffic - Test &
Measure. A message of confirmation is returned by netsh if the command is succeeded. If the path
you have specified is invalid, netsh returns an error message close to the following message: The
system cannot find the file specified. In that case, please renew Step 2.
Unlike under Windows Vista and after, the firewall allows the incoming echo replies. You
don't need to add a rule to be able to receive ICMPv4/ICMPv6 "echo reply" messages.
This command line allows IGMP protocol used by the IPv4 multicast connections.
8.2 How to authorize UDP and TCP connections under Windows Vista and
after
Windows Firewall on Windows Vista and after blocks incoming and outgoing network connections
except for the authorized programs. By default, all outgoing connections are allowed. But to
authorize IP Traffic - Test & Measure receiving incoming connections, you must add it in the
exceptions list of Windows Firewall by proceeding as follows:
Step 1: Open a command prompt window with the administrator rights. The administrator rights
are mandatory to set up the firewall configuration. Open the "All Programs / Accessories" folder
and right-click on the "Command Prompt" icon as shown on the figure below and choose "Run as
administrator". A command prompt window is opened.
Make sure that "C:\Program Files\IP Traffic\” is the installation directory of IP Traffic - Test &
Measure. A message of confirmation is returned by netsh if the command is succeeded. If the path
you have specified is invalid, netsh returns an error message close to the following message: The
system cannot find the file specified. In that case, please renew Step 2.
With Windows Vista, the firewall blocks the incoming echo replies. You must add a rule to
be able to receive ICMPv4/ICMPv6 "echo reply" messages. Please refer to the
paragraphs here after.
This command line allows IGMP protocol used by the IPv4 multicast connections.
To use a NTP Server under Window Vista and after, the ICMP exchange must be
allowed. Please refer to the paragraph 8.3 “How to authorize ICMPv4 and ICMPv6 traffic
under Windows Vista.”
8.3 How to authorize ICMPv4 and ICMPv6 traffic under Windows Vista and
after
Windows Firewall on Windows Vista blocks incoming ICMPv4 and ICMPv6 "echo reply" messages.
To be able to receive these messages, you must add two new rules by proceeding as follows:
Step 1: Open a command prompt window with the administrator rights. The administrator rights
are mandatory to do the firewall configuration. Open the "All Programs / Accessories" folder and
right-click on the "Command Prompt" icon as shown on the figure below and choose "Run as
administrator". A command prompt window is opened.
Step 2: To create the rule for ICMPv4 echo reply messages, type the command line below and
press "Enter".
%> netsh advfirewall firewall add rule name="Echo Reply ICMPv4 (used by IP Traffic - Test & Measure)"
dir=in action=allow profile=any localip=any remoteip=any protocol=icmpv4:0,0 interfacetype=any
A message of confirmation is returned by netsh if the command is succeeded.
Step 3: To create the rule for ICMPv6 echo reply messages, type the command line below and
press "Enter".
%> netsh advfirewall firewall add rule name="Echo Reply ICMPv6 (used by IP Traffic - Test & Measure)"
dir=in action=allow profile=any localip=any remoteip=any protocol=icmpv6:129,0 interfacetype=any
A message of confirmation is returned by netsh if the command is succeeded.
ICMP exchanges must be allowed to enable the use of the z300 Time Device.
The IP Traffic - Test & Measure main window is composed of four parts:
1 Menu bar: File, Edit, Configuration, Tools, File downloading, Automation Tool, Help, Operating
mode.
2 Tabs area: this main area displays the five tabs. To see a tab, click on the tab title you want to
display.
3 Time Reference display: this area shows the status of the time device(s) used as Time
Reference by IP Traffic - Test & Measure.
4 Activity display: ‘Activity’ parameter, ‘IP Generator Activity’, ‘IP Answering Activity’ and
‘Sniffer Activity’.
5 General commands: for remote control or local operations.
Menu bar, Time Reference display, activity display and global commands are always visible
whatever the tab displayed.
9.2 Display General Rules of the IP Traffic - Test & Measure GUI
The fields of the IP Traffic - Test & Measure software interface can be filled following four
situations:
Fields generated further to user action and displayed as information use only
These fields are filled automatically by IP Traffic - Test & Measure further to use enter or
parameters selection. They are displayed as reminder and will be modified by another user action.
These fields are recognizable by black writing on gray background.
Fields turned out of reach further to user action
User actions and parameters selection may turn some IP Traffic - Test & Measure GUI fields and
action buttons out of reach. Usually all the out of reach fields are grayed.
Fields can become out of reach in several cases, for example:
- As soon as a connection is running, it is impossible to change its parameters. You must stop
the connection in order to change the parameters of the connection.
- When a testing mode (unitary or automatic) is selected, it is impossible to change parameters
of the unselected testing mode.
If you enter a non valid value in a field, the connection could be disabled or actions button in the
configuration’s window could become out of reach.
Throughput computing
The IP Traffic - Test & Measure displayed throughputs correspond to payload data on
the sampling period (defined in the IP Traffic - Test & Measure configuration menu) and
bring back to a bits/second number. The displayed throughput is an “application”
throughput. At some instant, it could be different from the physical network throughput
because data can be split and buffered at various system levels.
9.3.3 Duration units
Display Meaning
31ms 31 milliseconds
1s 1 second
1mn32s 1 minute 32 seconds
1h24mn 1 hour 24 minutes
>24h Time superior to 24 hours
Unit changing
To change, a volume value in KB to a volume value in MB, IP Traffic - Test & Measure
divides the first value per 1024. Ex: 1000 KB = 0.98 MB. The same rule is applied with
throughput values. In order to have a throughput in Mb/s coming from a throughput in
Kb/s, IP Traffic - Test & Measure divides the first value per 1024. Ex: 2048 Kb/s = 2.00
Mb/s.
File/New
This command opens a new default context in IP Traffic - Test & Measure. Before opening a new
default context, running connections must be stopped. The default values of a new context are
presented in PART 13 Appendix.
File/Open
“Open” command allows reading a context file (.ctx file), which contains a previously saved
configuration. Before opening a context, running connections must be stopped.
Note:
Context file contains configuration parameters and a copy of the laws defined by the user.
Reading of a context file will delete currently used laws and replace them by the laws saved in
the context file.
File/Save
“Save” option allows saving the entire configuration parameters and parameters of the laws
defined in the opened context file.
File/Save as
This option allows saving all the configuration parameters and the parameters of the laws defined
in a context file (.ctx file), which name is requested in a standard enter dialog box.
File/Recent Contexts
This option allows charging the 4 most recent used context files (.ctx file).
File/Exit
This command stops IP Traffic - Test & Measure. To stop IP Traffic - Test & Measure, all active
connections (‘IP Generator’ and ‘IP Answering’) shall be stopped. A message box will ask you to
save or not changes made to parameters in a context file.
Active tab: “IP Generator – Parameters” Active tab: “IP Answering – Parameters +
Statistics”
By selecting this item, the 'IP Address' field from connection #01 is copied out for all connections
from #02 to #16.
By selecting one option, the 'Protocol' field for the connections #01 to #16 is set to TCP or UDP.
By selecting one option, the 'Protocol' field for the connections #01 to #16 is set to TCP or UDP.
By selecting this item, the IP Address field from connection #01 is copied out for all connections
from #02 to #16.
General parameters
This command allows configuring parameters applied to graphical display, timeouts for echoed
connections and the size of buffers used by IP Traffic - Test & Measure. When selected, the
following window is pop up:
Overwrite
If you choose this mode, each time you start a statistics export process or the traffic capture, IP
Traffic overwrites the file you have defined if it exists.
Rename
By choosing this mode, IP Traffic adds a suffix to the file name, if the file still exists. The suffix
follows the format: mmddyyyy_hhmmss
Example: For a file name IPGenerator_Statistics, the resulting file name generated by IP
Traffic will be IPGenerator_Statistics_01242004_193020.
AutoComplete
The AutoComplete option is a help mechanism to input values for the user. It lists possible entries
that match user entries typed before. The AutoComplete mechanism with IP Traffic - Test &
Measure is available for IP address entries in the “IP Generator – Parameters” and “IP Answering
– Parameters + Statistics” tabs.
The AutoComplete parameters dialog is used to enable/disable and to clear all historical records.
Up to 30 entries can be kept in the historical record. When a 31st entry is typed, the 1st entry is
deleted: the historical record is handled like a FIFO list.
The Clear History button removes user entries from historical records leaving two predefined
entries:
NO_ADDRESS: this is the default IP Address of the Traffic Generator - a void address,
used to disable the connection.
ANY_ADDRESS: this is the default IP Address of the Answering, used to accept any
incoming connection.
When AutoComplete is disabled, the historical record doesn’t continue to be filled. User entries
available - before AutoComplete deactivation - remain when AutoComplete is activated again.
Note: the historical record is associated to the IP Traffic - Test & Measure session. For
confidential reasons, the historical record is not kept between sessions and is lost at the end of the
IP Traffic - Test & Measure session.
Note: The IP address entries contained in a context are automatically added to the historical record
when loading it
Thanks to this menu, you can select the Time Device you want to use. Select “None” (no time
device used) or one of the Time Device Reference. Get more details on those Time Devices at
paragraph “1.3 Use a hardware time device to get high precision measurements”.
GNSS Receiver
This command allows configuring parameters applying to the GNSS Receiver connected to the PC
via a serial link.
GNSS Receiver legend in the main window: colored icons giving information on the state of the
GNSS Receiver (see the colored light on the lower left of the IP Traffic - Test & Measure main
window)
Green color: the GNSS Receiver provides synchronization and position information (3D).
For this status, the GPS system is synchronized with at least three satellites.
Red color: no information is available from the GNSS Receiver: either the time device is not
operational (no time device plugged or no power by example), or there is not enough
satellites seen by the GPS to get precise timing information and position. In this case,
change the position of the antenna of the GNSS Receiver and wait for a few minutes to see
the result.
Satellite information: for each satellite recognized by the GPS, the satellite number and the
signal level are displayed.
When GPS position is available: the GPS position (latitude, longitude and altitude) can be
added to data packets at a user-defined rate. IP Traffic - Test & Measure, stores this additional
information in a specific record of the Traffic sniffed file and it is not included in the data
packets. By saving the GPS position, IP Traffic is able to provide the location of the computers
when they receive or send packets. (see Statistics Display = Packet Statistics).
In the “GPS parameters” window, a Help button gives information about ‘How GPS works’ and how
to use it.
At the top of this window, you can follow the synchronization status. Three statuses exist:
- No Synchronization running
- Synchronizing
- Synchronized
When IP Traffic - Test & Measure is synchronized, you get the uncertainty value. In the other
cases, the uncertainty value is N/A (Not Applicable).
This part explains also the legend shown in the main window. If the red light is on, there is no NTP
Time server available or the synchronization is pending. If the green light is on, IP Traffic - Test &
Measure is synchronized with the NTP Time Server.
The General Parameters tab allows specifying the IP Address of the NTP Time Server plugged on
the network. By clicking on the button “Connect to the NTP Time Server”, you activate the dialog
with the NTP Time Server. In that case, the status presented in the last paragraph changes from
“No Synchronization running” to “Synchronizing”. Moreover, since the dialog is initiated, you can
access to the other tabs, “Information Messages” and “Advanced”.
By using the “Clear Logs” button, you can delete all previous messages. By using the “Save Logs”
button, you can save into a file all the current messages displayed in the list box.
Advanced tab
The “Advanced” tab allows having the access to embedded HTML interface of the NTP Time
Server (zx00 NTP Server only). This interface allows the parameters configuration and gives
information about the satellite visibility, the GPS status …
By clicking on the “Embedded Administration Interface”, a browser window is opened asking for a
login and password. To be able to access to the interface, enter the following information:
Login: user
Password: heol
Once you click on the OK button, you have access to the HTML interface. Please refer to the z300
documentation to get more details on the way to configure it.
File downloading
This command allows downloading a file from one IP Traffic - Test & Measure machine to another
one. In order to avoid confusion, “Local” and “Remote” terms are used to indicate the machines for
this command.
File Downloading is mainly used when a receiving connection is operating in Absorber File working
mode. It is aimed at repatriating the absorbed file from IP Answering to IP Generator, as shown in
the following scheme (any file from the remote machine can be downloaded).
When clicking on the file downloading command, the following window appears:
2
3
4
5
Warning message displayed on the remote machine from which file is downloaded
Remote IP address is the IP address or host name of the machine from which you want to
download the file. Can be an IPv4 or an IPv6 address.
Port number is the port number for the file downloading process (it must be the same for
remote and local machines).
This tool allows converting the Sniffed Traffic files by IP Traffic - Test & Measure format to
Ethereal standard format. By realizing this operation, the result file (dmp) can be opened by a
Network Analyzer software such as Ethereal or Network Instruments Observer. This tool can
convert capture traffic files containing IPv4 and IPv6 packets.
Help
Help command displays help on IP Traffic - Test & Measure. Pressing the F1 key can also
activate help. To display the IP Traffic - Test & Measure Help, Acrobat Reader should be
installed. If Acrobat reader is not installed, a warning message is displayed.
You can download the latest version from [Link] or use the version of Acrobat
Reader provided with the “IP Traffic – Test & Measure» CD ROM.
IP Traffic - Test & Measure doesn’t support other PDF readers than Acrobat Reader.
Forewarnings menu
This menu is aimed to inform you of IP Traffic - Test & Measure special behaviors due to system
limits.
IP Traffic - Test & Measure leans on Microsoft Winsock 2 Interface to generate and receive TCP
or UDP traffic. Therefore, IP Traffic - Test & Measure behavior, as any Winsock 2 application, is
dependent on Winsock 2 Interface, Microsoft TCP Stack and operating system working modes.
UDP connections
When several UDP connections are running and according to traffic level and system loading, IP
Traffic - Test & Measure can have strange behavior due to TCP stack limits and working mode.
Packet losses
UDP connection from Local IP Generator to Remote IP Answering - the working mode of the
Remote IP Answering is absorber.
n≥m
UDP connection
n sent packets m received packets
IP Generator IP Answering (echoer mode)
q received packets (echoed) p sent packets (echoed)
n≥m
q≤p
m=p
UDP connection from Local IP Generator to Remote IP Answering - the working mode of the
Remote IP Answering is echoer.
In this case, the number of received packets (m) will be equal to the number of echoed packet (p)
in the 'IP Answering' part. Nevertheless, the number of received packets (q) in the 'IP Generator'
part could be inferior to the number of packets (p) sent by the Remote 'IP Answering' in echoer
mode.
Local mode
By selecting this mode, all IP Traffic - Test & Measure functionalities and commands are
available.
When the remote control mode is selected, a message is displayed at the bottom of the IP Traffic -
Test & Measure main window as described below, and all button commands and tabs are
inhibited.
The “Traffic Observer” tab is displayed and you can see the connections activity if any.
To quit this mode, select the item menu “Normal” of the Operating mode menu. A message is then
displayed. Press OK to return in normal operating mode.
A remote IP Traffic - Test & Measure system can operate with another IP Traffic - Test &
Measure system in remote control mode by using commands at the bottom of the IP Traffic - Test
& Measure main window (left part):
First, you define the remote context file to load on the remote IP Traffic - Test & Measure
machine, and define the remote IP address or host name (IPv4 or IPv6) and the port number.
Note: the remote IP Traffic - Test & Measure machine must be set before in the ‘Remote’ mode
(by using the ‘Remote’ item of the ‘Operating mode’ menu).
When the “Run all processes” button is pressed, a TCP connection is established with the remote
system in order to supervise the link between the two systems. Then the context filename
previously defined is sent to the remote. The remote system loads this file context and then
executes the “Run all processes”. This specific TCP connection between local and remote is
stopped when you press the “Stop” button of the ‘Remote operations” on the local system.
10.4 Main window: the Time Reference display and the activity display
IP Traffic - Test & Measure displays four information areas:
IP Traffic - Test & Measure offers two command blocks at the bottom of the main window:
On the left: commands for Remote control of an IP Traffic - Test & Measure system
For remote control, you must first specify the following parameters:
Remote file context: filename of the IP Traffic - Test & Measure context to load located on
the remote
The remote IP address or host name (IPv4 or IPv6)
The associated Port number
Then you control the remote IP Traffic - Test & Measure system with these commands:
Run all processes: the ‘IP Generator’ and ‘IP Answering’ modules of the remote system
are started. Moreover, if the option is selected, this button can handle the Traffic Sniffer and
the statistics export process of the Traffic Observer.
Stop: the ‘IP Generator’ and ‘IP Answering’ modules of the remote system are stopped.
Note:
The previous commands are used to control a remote IP Traffic - Test & Measure system.
The remote system must be switched before in ‘Remote control mode’ by using the “Operating
mode” menu (and you must specify on this remote system the same port number as the one
defined previously for the local system).
On the right: Local Operation
The user can launch four main functionalities independently: IP Traffic Generator (“Run All
Connections’), IP Answering (“Start receiving traffic”), Traffic Sniffer (“Start”) and Export
statistics of the Traffic Observer tab (“Start”). For the Traffic Sniffer and the Traffic Observer
tabs, read the note below.
The command button “Start All Local Processes” is used to activate simultaneously these
functions. The command button “Stop All Local Processes Stop” stops all active functions.
Note:
User must first define if the start commands for the ‘Traffic Sniffer’ and the export of statistics in
the ‘Traffic Observer’ tab are included in the “Run all processes” command. See the check
boxes in the ‘Traffic Sniffer’ (Enable automatic start and stop in local operation) in the
paragraph 10.9.2 Capture sniffed traffic into a file and in the parameters button of ‘Export
statistics’ in the ‘Traffic Observer’ (Enable automatic export in local operation) in the paragraph
10.10 The ‘Traffic Observer’ tab.
Select the network interface, source IP address and source port number
(1) The network interface selection is optional with IPv4. It is used to constrain connections to
be established using a specific interface.
By default:
The IP version is automatically selected by IP Traffic - Test & Measure regarding
the destination address or host name specified on the “IP Generator - Parameters”
tab (see below).
The IP stack resolves the interface selection to send packets to the remote.
The IP stack uses the destination IP address to select the correct interface. The IP
address and the netmask related to each interface are checked against the remote
IP address to reach. When an interface that matches the remote IP address is
found, it is used. To understand how the IP stack selects the interface, you may
enter ‘route print’ console command to list the interface order, the IP address and
the network address mask.
You can select one interface from the list of the connected interfaces. IP Traffic - Test
& Measure will only use the selected interface to translate IP address and to make a
connection. You must select the interface compatible with the remote IP address you
want to reach. When the IP address translation failed, the current connection
parameters area is updated as follows:
Interface types are restricted: only Ethernet and PPP are listed.
A PPP interface should be in a ‘connected’ state to belong to the interface list.
We have noticed that some operating systems may choose automatically the best network
interface to use when several NICs are plugged on the same network when it comes to
network interface selection. In that case, data can be sent on one interface and received on
another one.
(3) Select IP address is available when multiple IP addresses are attached to the network
interface. This interface configuration is also known as ‘multihomed’ interface. The
selection of a Source IP address is generally not required: IP Traffic - Test & Measure
uses the default IP address of the interface to establish connections.
It may be useful when routing priority or policy is defined.
Select IP address is not available if the default interface ‘Interface chosen by the system’ is
selected.
(4) Specification of the local source port number is disabled by default. In this case, the
system automatically chooses the source port number for any connection generating traffic.
In order to respect the rules of a firewall for example, the source port number can be user
defined.
(5) Current parameters of this connection area are an abstract for the connection. It
summarizes the IP address, the numerical IP address format, the IP version and the
interface selection.
The source port used is dynamically updated with the user selection.
IP addresses are static. The IP address translation process occurs after you click on
OK.
When you click on the OK button if the interface selected or IP version has changed, the
IP address translation is automatically started. It may be time consuming.
Because the IP address translation mechanism is time consuming, you should be carefully when
using IP canonical addresses. The time consumption depends on the DNS answer speed, the
number of DNS configured and the network load when the DNS request is sent.
If network environment changes – e.g. a new DNS has been defined - you should press the Enter
key in the ‘IP Address or Host Name’ field to force IP Traffic - Test & Measure to restart the
translation mechanism for this connection.
When the IP address translation failed, the IP address is written in red on a white
background. This connection cannot be started: the “Run” button in the ‘IP Generator –
Traffic + Statistics’ tab is grayed.
If no IP version has been selected, the IP address translation mechanism chooses the
good IP version regarding the IP version returned by the resolution process. If for
example, a canonical name represents at the same time an IPv4 and an IPv6
addresses, the IP Address Translation mechanism chooses the IPv4 address. If you
want to use the IPv6 address, you should select IPv6 version (see Select the network
interface, source IP address and source port number).
In order to facilitate the input of these parameters, a copy/paste mechanism for all parameters of a
connection is available. This mechanism is not available when the canonical IP address cannot be
translated into numerical format.
Duplication of connection’s parameters doesn’t copy the interface information. When you copy a
connection to another one, the IP address translation mechanism is started.
Step 1: first, input parameters for a
connection (for example, connection #01)
(Copy mode)
Note: this copy/paste function allows copying parameters from one connection (source) to another
one (target). Repeat this process for others connections if needed.
When the mouse is located on the ‘IP Address or Host Name’ text area for example, the text color
changes to white. Then click left your mouse to display the associated menu.
Floating menu for the ‘IP Address or Host Name’ label
With this function, you can duplicate the IP address or the Host name from the first connection to
the others fifteen connections.
Floating menu for the ‘Protocol’ label
10.6.2 Configure the Unitary Mode for TCP and/or UDP connections
When the “Parameters #n” button is pressed, the following window is displayed.
Mathematical law
In the unitary mode, the offered mathematical law is a data volume to send law. Volume will modify
on the duration of the connection.
IP Traffic - Test & Measure unitary mode offers four mathematical laws related to data volume:
Uniform law
Exponential law
Pareto’s law
Gauss law
These laws are presented in details in the PART 13 Appendix.
In the “Law: data volume to send “sub-area, a list box allows selecting an existing law. The main
features (type of mathematical law and values range) of the selected law are reminded below the
list box.
You can add, modify or delete laws by pressing the “Edit” button. Then a new window is displayed:
Note: Laws created from this window will also be available for the Automatic mode.
Packets Generator
When the Packet Generator data source is selected, IP Traffic - Test & Measure generates n IP
packets for this connection. Packet contents can also be configured.
Packets number
You specify the number of packets to send in the “Packets generator” sub-area. The number of
packets to send is limited to 99,999,999. Zero value means infinite (Zero is the default value).
Packet contents
A content is one hex byte. Accepted values are all combinations from 00 to FF. If a no valid value
is entered, it will be automatically replaced by FF.
You can configure packet contents as follows:
Fix: each packet has the same content.
Random: IP Traffic - Test & Measure computes random packet content included in
a range (min to max).
Alternate: you define two values. IP Traffic - Test & Measure uses the first value
(value #1) for odd packets and the second value (value #2) for even packets.
Increasing/Decreasing: the content of each packet varies in a range from the
minimal to the maximal value; each packet content following is incremented by the
step value (0 is an invalid value). When the maximal value is reached, the packet
content decreases by the step value, until the minimal value is reached.
Note:
When ‘Packets generator’ data source is selected, the ‘Volume to send’ and the ‘Remaining
volume’ statistics cannot be computed. In the statistics fields of the tab 2 “IP Generator -
Traffic + Statistics”, “N/A” will be displayed in “Sent” and “Remain” columns.
File to send
With this selection, IP Traffic - Test & Measure sends the content of the file defined in “Filename”
sub-area. The “Browse” button is made to ease the “file to send” selection.
With the two input fields “Loop counter” and “Idle time between each loop (sec.)”, you can
specify how many times this file must be sent and the idle time (expressed in seconds) before
sending the file again. Notice that the remote IP Answering should be configured accordingly to
accept an idle time greater than the ‘Idle time between each loop value’.
Data Size
This parameter defines the size of transmitted packets.
The maximum accepted value is 65 535 for TCP connections and 65507 for UDP connections. 0
(null) is not a valid value. By default, the entered value is 1460.
Data size can be configured as follows:
Fix: each packet has the same size. The last packet may have an inferior size to fit
the data volume to send when a mathematical law or file to send data source is
selected.
Random: IP Traffic - Test & Measure computes a random data size included in a
range for each packet to send.
Alternate: IP Traffic - Test & Measure uses the first value for odd packets and the
second value for even packets.
Increasing/Decreasing: the size of each packet varies in a range from the minimal to
the maximal value, each size is incremented by step value (0 is an invalid value).
When the maximal value is reached, the data size decreases step by step until the
minimal value.
Note:
The TCP or UDP Data Size is the data payload, not including headers (MAC, IP and protocol
headers). It is not the frame size e.g. Ethernet frame size.
When UDP is used, the Data Size, greater than the MTU, generates IP fragmentation.
If TCP is used, the TCP protocol can aggregate packets with a size smaller than the MTU. To
avoid aggregation, you should configure IP Traffic – Test & Measure with a TCP No Delay option
set (see 13.3 Configuration parameters saved in the Registry database for more details).
In addition, if the time code option is selected, the real TCP or UDP Data Size adds the size of the
time code option. (see 0 Time code option).
Mode 2: Using the External data source generator (allowing to use an user file
or DLL)
If you select the external data source generator, the following area is active:
Two external data sources (file or DLL) are selectable, and you specify which filename to use:
User file: this external data file is provided by the user (see 13.5 External File for the ‘IP
Generator’ module). It contains different parameters: data, Data Size, Inter Packet Delay...
User DLL: IP Traffic - Test & Measure invokes the user DLL each time data is needed to send
(see 13.6 External DLL for the ‘IP Generator’ module for more information)
Note: when the ‘User file’ parameter is selected two parameters can be defined allowing sending
the same file many times:
- Loop counter,
- Idle time (expressed in seconds) between each loop.
Options
When this option is selected, IP Traffic - Test & Measure will add RTT (Round Trip Time)
information to packets. The RTT header format (in the little endian notation) is:
4 bytes magic number
4 bytes sequence number
4 bytes time when sent
2 bytes length (without the RTT header)
This information is used in conjunction with connections running in the echoer mode on the
Remote IP Answering module. The Local ‘IP Generator’ module analyzes each echoed packet.
When the RTT header is found, the RTT and the ‘sequencing errors’ values are computed and
displayed in statistics.
For the remote IP Answering module, the RTT information is checked to update ‘sequencing
errors’ statistics only.
You can input a DSCP value (by default, DSCP = 00) used for each
packet sent on the IP connection.
The Differentiated Services Code Point is a selector for router’s per-hop behaviors. Because it is a
selector, there is no implication that a numerically greater DSCP implies a better network service.
The RFC 2474 redefined the Type of Service Byte to be:
7 6 5 4 3 2 1 0
Differentiated Services Code Point ECT CE
The ECT and CE fields don't refer to the DiffServ quality of service. They are spare bits in the IP
Header used by the Explicit Congestion Notification (see RFC 3168 for more details).
This leads the notion of “class”, each class being a group of the DSCPs with the same Precedence
value. Values within a class offer similar network services but with slight differences (different
levels of service such as “gold”, “silver” and “bronze”).
From the initial definition of the RFC 2474, RFC 2697 added the “assured forwarding” service and
RFC 2598 defined the “expedited forwarding” service. The DSCP values are defined as following:
How to allow the use of the DSCP field on Windows XP and Server 2003
Using Registry Editor inaccurately can cause serious problems that may require you to
reinstall your operating system. Microsoft cannot guarantee that problems resulting from
the incorrect use of Registry Editor can be solved. Note that you should back up the
registry before editing it. If you are running Windows XP or Server 2003 you should also
update your Emergency Repair Disk (ERD). For information about how to edit the registry,
view the "Changing Keys and Values" Help topic in Registry Editor ([Link]) or the
"Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in
[Link].
Step1: Start Registry Editor ([Link]). Go to the following key on Local Machine:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\
Step 2: On the Edit menu, click Add Value, and then type DisableUserTOSSetting. Click
REG_DWORD in the Data Type box, and then click OK. Enter 0 in the prompt box. Quit Registry
Editor, and then restart the computer.
The user can input the TTL/Hop Limit value (hexadecimal) used for
each packet sent on the connection.
Default value = 00
With this feature, you save in a file all incoming data traffic on the considered connection. The
remote ‘IP Answering’ module must be set before in “Echoer” or “Echoer file” mode.
If the internal traffic generator is used and a file has been specified:
then it would be possible to compare the two files: sent data and received data on this connection.
By using the ICMP protocol, only the unitary mode can be used. You are still allowed to use TCP
and/or UDP on other connections.
By pressing the “Parameters #n” button, the window below is displayed:
For the “IP Generator – Traffic + Statistics” tab, six statistics are available when using ICMP Echo
Request:
Tx packets: this value represents the number of ICMP Echo Request packets sent.
Rx packets: this value is the number of ICMP Echo Reply packets received.
Mean RTT: this value shows the average Round Trip Time.
Min RTT: this value is the minimum Round Trip Time calculated
Max RTT: this value is the maximum Round Trip Time calculated
Seq. Num. Errors: this value represents the number of replies that IP Traffic - Test
& Measure does not receive.
By clicking on the “[P]“ button, the following window is displayed, allowing configuring the
automatic mode parameters:
Note: the Automatic Testing Mode can not be used if ICMP connections are selected
Note:
Up to the used OS (Windows XP, Server 2003 or Vista), WinSock 2 Interface could present
number-limits of the incoming simultaneous calls. Consequence for IP Traffic - Test & Measure is
the presence of “connection failed”, particularly when connections frequency is very near (inferior
to 150 ms), and when the data volume to transmit is very small, which implies to make many
connections. These connection failures do not disturb IP Traffic - Test & Measure. To reduce
these failures, increase the frequency of connection or the data volume.
Data size
In the automatic mode, entering a value (in bytes) in «Mathematical laws parameters» window
configures the Data Size.
The Data Size is limited to 65,535 bytes for TCP connections and to 65507 bytes for UDP
connections.
When you click on the command button “[P]”, the following window is
displayed.
First, select a ‘Data traffic file to replay’ and then press the “Analyze the data traffic file” button. At
the end of the process, an indication is displayed: “100.00% of xxx MB” (where xxx is the file size).
Note: the Replay Sniffed Traffic Mode can not be used if ICMP connections are enabled.
After the analysis of the data traffic file, all IP connections found in the sniffed traffic file are then
displayed in the “(A) Result of analysis (list of data sniffed connections)” object.
Connections that have already been defined in the current IP Generator module are displayed in
the “(B) Connection(s) already defined in IP Traffic“ object.
Then you must link one ‘data sniffed connection’ to one ‘defined connection’ by pressing the “Link”
button. If needed, one association can be removed by pressing the “Delete the selected link”
button.
Once the needed links have been defined, press OK. IP Traffic - Test & Measure is ready to
replay traffic on actually defined connections of the ‘IP Generator’ by using data of connections
from the ‘data traffic file to replay’ specified by the different links made by the user.
Note: the “.dtr” file contains only one-way packets. More details about how creating “.dtr” files are
available in the paragraph 10.9.3 Run analysis algorithm (Step 3).
The "N/A" (Not Applicable) mention can be displayed instead of a value in the cell of the statistics
table if the parameter cannot be calculated.
Note: the warning message isn't erased if the "Clear on Stop" option is selected.
Transmitting statistics
Tx Packets (2)
Tx Packets (Tx = Transmit) is the number of packets that IP Traffic - Test &
Measure has sent since the connection started.
Tx Pkts Tx Pkts Throughput (Tx = Transmit) is the mean number of packets that IP Traffic
Throughput (1) (2) - Test & Measure is sending per second. This value is only available with UDP
connections.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Tx Throughput (1) Tx Throughput (Tx = Transmit) is the mean throughput of data sent.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Tx Volume (1) Tx Volume (Tx = Transmit) is the number of bytes that IP Traffic - Test &
Measure has sent since the connection started.
Receiving statistics
Rx Packets(2) Rx Packets (Rx = Receive) is the number of packets that IP Traffic - Test &
Measure has received since the connection is started.
Rx Pkts Rx Pkts Throughput (Rx = Receive) is the mean number of packets that IP
Throughput (1) (2) Traffic - Test & Measure is receiving per second. This value is only available
with UDP connections.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Rx Throughput (1) Rx Throughput (Rx = Receive) is the mean throughput of data received.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Rx Volume (1) Rx Volume (Rx = Receive) is the number of bytes that IP Traffic - Test &
Measure has received since the connection is started.
Other statistics
Jitter (1) Jitter is the mean variation of delays on packets received. This value is only available
when Timecode option is selected (for the local 'IP Generator'). This value corresponds
to either the mean one-way variation (remote 'IP Answering' = Generator mode) or the
mean two-ways variation (remote 'IP Answering' = Echoer mode).
Remaining 'Remaining Volume' is the number of bytes that IP Traffic - Test & Measure has
Volume (1) still not sent. This information is only available for two Traffic Generator types:
Mathematical Law and File to Send.
Mean RTT 'Mean RTT' is the Round Trip Time of a packet that was sent by IP Traffic - Test &
Measure. This value is calculated if the Timecode option is selected for the local 'IP
Generator' and if the remote 'IP Answering' works in the Echoer mode.
Min RTT "Min RTT" is the minimum value of the Round Trip Time calculated by IP Traffic -
Test & Measure. For more information, please see the "Mean RTT" column
information.
Max RTT "Max RTT" is the maximum value of the Round Trip Time calculated by IP Traffic -
Test & Measure. For more information, please see the "Mean RTT" column
information
Seq. Numb. 'Seq. Numb. Errors' (Sequence Number Errors) is the sum of the Out Of Sequence
Errors(2) packets number (OOS) and the number of lost packets. This value is only available if
the Timecode option is selected (for the local 'IP Generator') and if the working mode
of the remote 'IP Answering' is Generator or Echoer.
Volume To 'Volume To Send' is the number of bytes that IP Traffic - Test & Measure should
Send (1) send. This information is only available for two Traffic Generator types: Mathematical
law and File to Send.
(1)
These statistics are not available with ICMP
(2)
These statistics are not available with TCP
A RTT summary for all connections is also available. This summary displays the minimum,
maximum and mean RTT values of all connections (for connections having RTT (Timecode) option
selected (see 0 Time code option for more information) ).
When you press the “Stop all connections” button, statistics remain displayed in black writing on
gray background.
If a connection cannot be activated (in case of invalid parameters), the statistics fields are empty
on gray background.
To export all or part of statistics into a CSV file, click on the 'Parameters' button when enabled
(i.e. when no connection of the IP Generator is active):
When no parameters are defined, the state is:
Export is disabled
Note: do not specify the same filename to save statistics for the 'IP Generator' and the 'IP
Answering' parts. If you do so, a warning message is displayed.
Note: The maximum number of columns handled by Excel is 255. If the number of statistics and
connections you have selected exceeds this limit of Excel, you have to restrict to the most
important statistics that you need, or to reduce the number of connections.
The statistics file is updated with the same refresh period than the statistics displayed.
A special mark is added to keep special TCP and UDP events e.g. Start and End of sending traffic.
When you reset statistics, the displayed values and the exported values are reset.
Statistics are saved into the CSV file as soon as one connection of the IP Generator is started and
the 'Export is running' state is displayed:
When all the connections are stopped, then the export process is automatically suspended and the
following idle state is displayed:
To export all or part of statistics displayed (in other words, there is the possibility of saving also the
statistics which are not displayed) in a file, you can use the parameters connection and statistics
dialog.
The RTT summary is exported even if the selected connections don’t use the RTT option.
Tx Pkts
Tx Throughput Tx Volume
IP Generator RTT Summary: RTT Summary: RTT Summary: State Throughput
Connection #xx Connection #xx
Date/Time Mean RTT (ms) Min RTT (ms) Max RTT (ms) Connection #xx Connection #xx
(Kb/s) (KB)
(Pkts/s)
Next lines:
MM/DD/YYYY TCP or UDP or
mmm mmm mmm [Link] [Link] mmm
HH:MM:[Link] ICMP
Tx Rx Tx Rx
Mean RTT Mean RTT
State Connection Throughput Throughput Throughput Throughput
IP Generator Date/Time Connection State Connection #02 Connection
#01 Connection Connection Connection Connection
#01 (ms) #02 (ms)
#01 (Kb/s) #01 (Kb/s) #02 (Kb/s) #02 (Kb/s)
The delimiter mark used between each field is the comma character (in conformance with the CSV
file format). In this example, the lines containing the END flag have a synthesis of all statistics
exported. The throughputs showed are the mean throughputs calculated from the START flag time
to the END flag time.
The unitary testing session can be started from the “Unitary mode“
area in Tab 2 “IP Generator - Traffic + Statistics”. From this area, you
can start or stop connections in unitary testing separately or all
together.
To run an unitary mode session:
1. In Tab 2 “ IP Generator - Traffic + Statistics”:
If the IP Generator connections are active, stop all running
connections by pressing the “Stop All connections” button.
10.8.2 Listening To …
In this area, you configure each receiving connection with the following parameters corresponding
to the connected sender from which connections are received. You configure the parameters IP
Traffic - Test & Measure uses to listen to incoming connections. These parameters are:
The black arrow has two purposes:
Network interface selection
To display a summary of the connection's parameters
To select the network interface and the IP version for a
connection.
The port number is limited to 65,535. By default, the port
Port
number is 2009.
The same port number can be used by two connections using either IPv4 or IPv6 YES YES
The same port number can be used by connections using different NICs YES YES*
The same port number can be used by connections using the same multihomed
YES YES*
NIC but by selecting different IP Addresses
* If a UDP connection uses the "default interface", this connection is used in favor of the
connection using an interface.
Network interface types are restricted: only Ethernet and PPP are listed.
A PPP interface should be in ‘connected’ state to belong to the interface list.
We have noticed that some operating systems may choose automatically the best network
interface to use when several NICs are plugged on the same network when it comes to
network interface selection. In that case, data can be sent on one interface and received on
another one.
(2) The IP version selection is available:
with Windows XP (or later)
If IPv6 features are installed on the target machine. Please refer to the Windows XP or
Windows Server 2003 documentation to install the IPv6 stack. On Windows Vista, the
IPv6 stack is installed by default.
You can allow IP Traffic - Test & Measure to choose automatically the good IP version
regarding the address or host name resolution result. If a canonical name corresponds
at the same time to an IPv4 and IPv6 addresses, IP Traffic - Test & Measure chooses
the IPv4 address. In that case, to use the IPv6 address, you should select the use of
IPv6 only (Use IPv6 only).
If you have selected an IP version, the IP address translation (see ) uses the current
selected IP version to get the IP address numerical form.
(3) Select IP address is available when multiple IP addresses are attached to the network
interface. This interface configuration is also known as ‘multihomed’ interface. The selection
of a Source IP address is generally not required: IP Traffic - Test & Measure uses the
default IP address of the interface to establish connections.
It may be useful when routing priority or policy is defined. Example of an IP address
selection for a multihomed interface:
Select IP address is not available if the default interface ‘Interface chosen by the system’ is
selected.
(4) Specification of the local source port number is disabled in the receiver Interface
configuration because the source port number and the destination port number are
generated by the remote as the originator of the connection.
(5) Current parameters of this connection area are an abstract for the connection. It
summarizes the IP address, the numerical IP address format, the IP version and the
interface selection.
The source port used is dynamically updated with the user selection.
The IP addresses are static. The IP address translation process occurs after you click
on OK.
The IP version field is dynamically updated with the user selection.
The current interface is dynamically updated with the user selection.
When you click on the OK button, if the interface selected or IP version has changed,
the IP address translation is automatically started. It may be time consuming.
When the mouse is located on the ‘Port’ text area for example, the text color changes to
white. Then click left your mouse to display the associated menu.
Set the port number increasingly or decreasingly for every UDP connection, based on the
port number of the first UDP connection.
Set the port number increasingly or decreasingly for every connection, based on the port
number of the first connection without taking account the protocol in use.
With a TCP connection, the incoming connection is rejected if IP Traffic - Test & Measure can’t
correlate this IP Address or host name with the source IP Address of the incoming packet.
With a UDP connection, the incoming packets are received but if IP Traffic - Test & Measure
can’t correlate this IP Address or host name with the source IP Address of the incoming packets,
IP Traffic - Test & Measure doesn’t take them into account in the statistics.
Click on the left mouse button to display the short menu as above. With this function, the IP
Address field from connection #01 is copied out to all connections from #02 to #16.
If the network environment changes – e.g. a new DNS has been defined - you should press the
Enter key in the ‘IP Address or Host Name’ field to force IP Traffic - Test & Measure to restart the
translation mechanism for this connection.
When the IP address translation failed, the IP address is written in red on a white
background. This connection cannot be started.
IP Traffic - Test & Measure offers five different active working modes for the IP Answering part:
’Absorber’, ’Absorber File’, ’Echoer’, ’Echoer file’ or Generator’. A ’Disable’ (or inactive) mode
is also available.
Absorber mode
With this working mode, IP Traffic - Test & Measure absorbs data on this connection.
Connection # n
Remote IP answering (absorber mode)
Local IP generator
(no specific treatment for each received IP packet)
Echoer mode
When a receiving connection is operating in echoer mode, the received data are sent back to the
‘IP Generator’ module.
Connection # p Remote IP answering (echoer mode)
Local IP generator (each received IP packet on the connection is
sent to the transmitter)
With UDP protocol, the ‘Echoer’ mode is available if a connected ‘IP Generator’ address is
specified only.
Remind:
Echoed data can be saved in a file by the local ‘IP Generator’ module via the tab 1 “IP
Generator - Parameters”.
Generator mode
This mode is displayed as “Generator” in the combo-box mode.
Properties of the IP flow 1 are defined at the local ‘IP Generator’ level and each IP packet received
by the remote ‘IP Answering’ module is used to compute statistics only.
When you select the “Generator” mode for a connection (#1 in the example above), a “Param.”
Button is displayed in order to specify the traffic parameters generated by the remote ‘IP
Answering’ module (i.e. IP flow 2). When you press the “Param.” button, an “IP Traffic –
Parameters in unitary mode” window is displayed (the same as IP Generator – configure unitary
testing mode). So you can input parameters for this IP flow 2 as you like (for example, generate
10000 packets with an average throughput of 250 Kb/s).
For a TCP connection, IP flow 2 is generated as soon as the TCP connection will be established
between the local ‘IP Generator’ and the remote ‘IP Answering’ modules. The IP flow 2 is stopped
when the FIN or RESET flag is received or when the user stops the IP Answering. The IP flow 2 is
also stopped when no data are received during TCPINACTIVITY seconds. (see 13.3 Configuration
parameters saved in the Registry database)
For an UDP connection, IP flow 2 is generated as soon as the remote ‘IP Answering’ module will
receive the first UDP packet. The IP flow 2 is stopped when the RESET flag is received or when
the user stops the IP Answering. The IP flow 2 is also stopped when no data are received during
UDPINACTIVITY seconds. (see 13.3 Configuration parameters saved in the Registry database)
Disable mode
When this mode is selected for a connection, IP Traffic - Test & Measure does not use this
connection. The disabled connections are grayed when you start receiving traffic. Statistics fields
of disabled connections are filled in with the following message: “Connection disabled”. There is no
statistics in the file for these connections.
First, select a ‘Data traffic file to replay’ and then press the “Analyze the data traffic file” button. At
the end of the process, an indication is displayed: “100.00% of xxx Kb” (where xxx is the file size).
After the analysis of the data traffic file, all IP connections found in the sniffed traffic file are then
displayed in the “(A) Result of analysis (list of data sniffed connections)” object.
Connections that have already been defined by the user in the current IP Answering module are
displayed in the “(B) Connection(s) already defined in IP Traffic“ object.
You must then link one ‘data sniffed connection’ to one ‘defined connection’ by pressing the “Link”
button. If needed, one association can be removed by pressing the “Delete the selected link”
button.
Once that the needed links have been defined, then press OK. IP Traffic - Test & Measure will
replay traffic on actually defined connections of the ‘IP Answering’ module by using data of
connections from the ‘data traffic file to replay’ specified by the different links you have made.
The connections that are not used to replay the traffic can be used but with the absorber Receiving
Working Mode only.
Transmitting statistics
Tx Packets(1) Tx Packets (Tx = Transmit) is the number of packets that IP Traffic - Test &
Measure has sent since the connection is started.
Tx Pkts Tx Pkts Throughput (Tx = Transmit) is the mean number of packets that IP Traffic
Throughput(1) - Test & Measure is sending per second. This value is only available with UDP
connections.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Tx Throughput Tx Throughput (Tx = Transmit) is the mean throughput of data sent.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Tx Volume Tx Volume (Tx = Transmit) is the number of bytes that IP Traffic - Test &
Measure has sent since the connection is started.
Receiving statistics
Rx Packets (1) Rx Packets (Rx = Receive) is the number of packets that IP Traffic - Test &
Measure has received since the connection is started.
Rx Pkts Rx Pkts Throughput (Rx = Receive) is the mean number of packets that IP Traffic -
Throughput(1) Test & Measure is receiving per second. This value is only available with UDP
connections.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Rx Throughput Rx Throughput (Rx = Receive) is the mean throughput of data received.
The calculation of this value is based on the sampling period defined by the
throughput sampling period in the 'Configuration/General Parameters' menu.
Rx Volume Rx Volume (Rx = Receive) is the number of bytes that IP Traffic - Test & Measure
has received since the connection is started.
Other statistics
Data Not Echoed 'Data Not Echoed' is the number of bytes that the 'IP Answering' part couldn't echo.
This value is only available if the 'IP Answering' part works in the Echoer mode.
Jitter Jitter is the mean variation of delays on packets received. This value is only
available when Timecode option is selected (on the remote IP Generator). This
value corresponds to the mean one-way variation only.
Remaining 'Remaining Volume' is the number of bytes that IP Traffic - Test & Measure has
Volume still not sent. This information is only available for two Traffic Generator types:
Mathematical Law and File to Send.
Seq. Numb. 'Seq. Numb. Errors' (Sequence Number Errors) is the sum of the Out Of Sequence
Errors(1) packets number (OOS) and the number of lost packets. This value is only available
if the Timecode option is selected (for the remote 'IP Generator') and if the working
mode of the local 'IP Answering' is Generator or Echoer.
Volume To Send 'Volume To Send' is the number of bytes that IP Traffic - Test & Measure should
send. This information is only available for two Traffic Generator types:
Mathematical law and File to Send.
(1)
These statistics are not available with TCP
Then a new window allows defining parameters for the export process:
Enable or disable the export process,
The filename (.csv extension) of the export file,
The identification of the needed connections,
The parameters to export (up to 13).
Note:
Do not specify the same filename to save statistics for the 'IP Generator' and the 'IP Answering'
parts. If you do so, a warning message is displayed.
Note: The maximum number of columns handled by Excel is 255. If the number of statistics and
connections you have selected exceeds this limit of Excel, you have to restrict to the most
important statistics that you need, or to reduce the number of connections.
The statistics file is updated at the same rate than the statistics are displayed.
A special mark is added to keep special TCP and UDP events e.g. Begin and End of sending
traffic.
When you reset statistics, the displayed values and the exported values are reset.
Statistics are saved into the file as soon as the 'Start Receiving Traffic' button of the IP Answering
has been pressed and the 'Export is running' state is displayed:
When the 'Stop Receiving Traffic' button of the IP Answering has been pressed, then the export
process is automatically suspended and the following idle state is displayed:
Tx Pkts Rx Pkts
State Tx Throughput Tx Volume Tx Packets Rx Throughput
IP Answering Throughput Throughput
Connection Connection #xx Connection Connection #xx Connection #xx
Date/Time Connection #xx Connection
#xx (Kb/s) #xx (KB) (Pkts) (Kb/s)
(Pkts/s) #xx (Pkts/s)
Next lines:
MM/DD/YYYY TCP or UDP
[Link] [Link] mmm mmm [Link] [Link]
HH:MM:[Link] or ICMP
TCP END It indicates the corresponding connection has stopped. The numerical
values are the latest values computed by IP Traffic - Test & Measure.
When this mark is included in the IP Answering traces, the error message
returned by IP Traffic - Test & Measure is placed after the “INFO” mark.
Idle connections
When the connection is idle, no numerical values are set. The fields are empty.
Conventions
“Volume to send” and “Remaining Volume” are filled with the “N/A” symbol when the generator is
not configured with “File to send”.
“Seq. Num. Errors” and “Jitter” are filled with the “N/A” symbol until one “RTT” header is found in
the received data by the 'IP Generator' part.
“Tx Pkts Throughput” and “Rx Pkts Throughput” are filled with the “N/A” symbol when the protocol
used for the concerned connection is not UDP.
Tx Rx Rx Pkts Tx Rx Rx Pkts
State State
Throughput Throughput Throughput Throughput Throughput Throughput
IP Answering Date/Time Connection Connection
Connection Connection Connection Connection Connection Connection
#01 #02
#01 (Kb/s) #01 (Kb/s) #01 (Pkts/s) #02 (Kb/s) #02 (Kb/s) #02 (Pkts/s)
The delimiter mark used between each field is the comma character (respecting the CSV format).
Note: IP Traffic - Test & Measure allows configuring the mode to capture the data. Please refer
the DriverFilterMode entry in the registry presented in Appendix paragraph “13.3.1 General
configuration parameters”.
You can define up to 20 ‘filters’ composed of five parameters: Source IP address, Destination IP
address, Source Port number, Destination Port number and Protocol.
The command buttons “Add filter”, “Edit filter” and “Delete filter” allow adding, editing and removing
the user-defined filters. By clicking on “Add filter”, the window below appears:
Note:
Each parameter is optional. It is not necessary to specify a value. In this case, this parameter is
not used to filter packets.
Warning:
You can input different filters, but IP Traffic - Test & Measure doesn’t control the functional
coherence between the filters.
To edit a filter, select it in the list box and then press the ‘Edit filter’ button.
To delete a filter, select it in the list box and then press the ‘Delete filter’ button.
By clicking on the “Select Adapters” button, the window below opens. By default, if your machine
contains more than one network card, IP Traffic Sniffer driver pools all of the network cards and
captures all packets. This polling capacity can be greedy for resource. If it is not necessary, up to
one network card could be specified.
Note:
When loading a context, if the interface in this context saved can not be found, IP Traffic - Test &
Measure selects the first interface available to replace the one saved.
10.9.2 Capture sniffed traffic into a file (Step 2)
Once that capture parameters have been defined in the previous area, you must define a capture
file. The command buttons “Start” and “Stop” allow starting and stopping the traffic capture.
During the capture process, information is displayed in the “Traffic overview during capture” object
(statistics if available).
“Save only the headers of the captured packets (Data are not saved)” check box: if checked,
only the packet headers are saved (thus significantly reducing the size of the capture file) but you
will be not able to use this file for the step 3.
“Automatic refresh mode” check box: allows refreshing display in the “Traffic overview during
capture” object.
“Enable automatic start and stop in ‘Local operation’ check box: if checked, the “Start all
processes” button of the “Local operation” will launch automatically the ‘Traffic Sniffer’.
You specify a capture traffic file name in the “Input traffic file” object and two output files.
Note:
The “Input traffic file” must contain data (see Step 2). The Step 3 can’t use the files containing
only headers.
This file contains IP frames with different IP source addresses and IP source destinations.
The goal is to find in the input traffic file the communication entities (IP Generator and IP
Answering) and to produce two traffic files to replay. An internal IP Traffic - Test & Measure
algorithm analyzes IP frames from the Input traffic file and produces the two traffic files named
“Output data traffic file1 to replay after processing” and “Output data traffic file2 to replay
after processing”. The extension of these files must be “.dtr” (data to replay). This is an owner
format used only by the IP Generator and IP Answering parts. This algorithm reassembles the
fragmented packets before dispatching them in the two files. It is able to handle up to 50 fragments
to reassemble a packet.
When you press the “Start” button, the following window is displayed:
You should select connections to consider (addresses + protocol and ports) and then press the
“Process with selection” button.
After processing, the object “Synthesis after processing“ displays statistics information about
generated files and connections.
Note:
Values and statistics displayed in this tab are calculated at the ‘time’ point of reference (see IP
Traffic - Test & Measure architecture in paragraph “11.2.1 Reference points to compute the
statistics”) i.e. under the TCP/IP protocol stack.
10.10.1 IP Traffic - Test & Measure: On-line and Off-line modes for statistics
When IP Traffic - Test & Measure is operating (‘IP Generator’ is active and/or ‘IP Answering’ is
active), this mode is named on-line. On-line statistics are displayed in the following tabs:
- ‘IP Generator – Traffic + statistics’: statistics area,
- ‘IP Answering – Parameters + statistics’: statistics area,
- ‘Traffic Observer’: statistics area, but all parameters are not displayed: PER (Packet Erasure
Rate) and Packet transit delay need remote information to be computed.
By using the “Traffic Sniffer” tab, a capture traffic file can be defined (see “10.9.2 Capture sniffed
traffic into a file (Step 2)”) to save traffic that would be used in the off-line mode. Both file formats
(With Data or Headers only) can be used for Off-line calculation.
On-Line mode
You can switch between the off-line and on-line mode by using the Yes / No radio button.
Off-Line mode
Off-line mode is defined as a state where all IP Traffic - Test & Measure activity is stopped (‘IP
Generator’, ‘IP Answering’ and ‘Traffic Sniffer’ are stopped). In this mode, only the “Traffic
Observer” tab is available. All other tabs are inhibited.
In order to analyze traffic files and obtain all statistics, the user must first download a traffic file
from the remote. IP Traffic - Test & Measure uses two traffic files to do off-line statistics analysis:
a ‘local’ traffic file (generated by the ‘Traffic Sniffer’) and a downloaded ‘remote’ traffic file
(generated by the remote ‘Traffic Sniffer’).
Note:
A red color for objects or command buttons in the 'Traffic Observer' tab means that these items are
only available in the off-line mode.
You can define different scale factors for the Transmit (Tx) and the Receive (Rx) graphs, and one
value for the time scale.
The “Play >”, “Play >>” and “Stop” buttons are enabled once that traffic files have been analyzed
via the “Process files…” button (see further in this paragraph).
The “Play >” or “Play >>” buttons
are replaced by “>” and “>>” after
the user has pressed “Pause” for
the first time.
“Next >”: the current position in the traffic file to analyze is set to the next display index set by
the user.
“Add”: adds a display index at the current position.
“XX/YY”: displays the actual XX index number (YY is the total number of indexes set by the
user).
“Remove”: removes the current displayed index.
“Remove all”: removes all displayed indexes.
The “Export statistics” area allows exporting in a CSV file the
statistics values calculated by IP Traffic - Test & Measure with
the filter parameters defined by the user.
You define first the export filters and filename by using the
command button “Parameters”. The export filters allow
selecting: connection(s) and parameter(s). The statistics export
file is a CSV file.
The command buttons “Start” and “Stop” allow starting and
stopping the export statistics process in the user-defined file.
Filename
The statistics are saved in the specified CSV file accordingly to parameters described below.
Connections to export:
Include total statistics
If checked, the following parameters are saved in the file for the ‘IP Generator’ and the ‘IP
Answering’ modules (see the file format explained in the next paragraph).
[Total Throughput Tx] [Total Throughput Rx] [Total Inter packet delay Tx] [Total Inter packet delay
Rx] [Total PER Tx] [Total PER Rx] [Total Transit delay Tx] [Total Transit delay Rx]
where the term total is used as the sum of values for connections selected by user. Tx is used as
Transmit and Rx as Receive.
‘All’ or ‘None’
These buttons select all the connections or none.
Connections subset
Select the needed connections in order to save statistics for these connections.
Parameters to export:
Select the parameter you want to save as statistics.
Enable automatic export in ‘Local operation’ check box
If checked, the “Run all processes” button of the “Local operation” will launch automatically the
export of statistics in the file according to parameters defined in the above window.
Note: Only up to 255 columns can be exported in the statistics file. It’s impossible to select all
statistics for all connections. A warning message is display if this limit is reached.
Note:
It is recommended to define carefully the parameters to use; otherwise, the number of columns in
the file can be high (and an application like Excel may have problems to import this file).
The ‘Include total statistics’ generate 16 columns per line (8 columns for the 'IP Generator' and '8
columns' for the IP Answering)
When you select the 4 parameters to export (IP Throughput, Inter packet delay, PER quality and
packet transit delay), that generates 16 columns to export for each connection (2 columns Rx and
Tx per parameter = 8 columns for the 'IP Generator' and 8 columns for the 'IP Answering'). When
16 connections are selected, that generates 16 x 16 = 256 columns.
The columns 3 and 4 refer to the 'IP Generator' part and columns 5 and 6 to the 'IP Answering'
part.
In order to proceed, you must input a local sniffed traffic file in (A) and a remote sniffed traffic file in
(B).
The “(A) < --- > (B)” button inverts the (A) and (B) filenames.
Note:
(A) will be used as reference to find the packet synchronization between these two files and to
compute the statistics (for example, lost packets and the transit delay).
Once files have been selected, then you can press the “Start Analysis” button and a new window is
displayed:
- Step 1: scanning of the selected files in order to display the TCP and UDP connections
found.
- Step 3: once the synchronization has been found in the step 2, you can now start the
analysis in order to play these traffic files via the Traffic Observer off-line mode and
compute the “Packet Statistics”.
To proceed, you must first do the Step 1 by pressing the “Start Scan” button. This scan allows
display of couples of IP addresses found in these files and for each couple the number of
connections and packets.
An example is given below by using two traffic files provided with the IP Traffic - Test & Measure
software: These sniffed traffic files have been generated with the following configuration:
PC # A PC # B
[Link] [Link]
1 UDP connection
Port = 2011
IP Network
with impairments
Port = 2010
IP Traffic 1 TCP connection IP Traffic
« Sniffer » « Sniffer »
Step 1
For each file, a descriptive is given with the following description when the scan is complete:
where:
<Couple of IP addresses> = Source IP address Destination IP address
<Number of packets> = number of packets found in the file for this couple of addresses
<Number of connections> = number of connections found in the file for this couple of
addresses
So, you can examine easily the (A) and (B) file overviews in order to choose for analysis a specific
couple of IP addresses or connection(s) for a couple of IP addresses.
For (B), two additional buttons are available ‘Collapse’ and ‘Expand’.
As a sniffed traffic file may content a huge number of connections with for example IP address
translation between the two files, you can examine the overview of these two files and decide
which couple of IP addresses to consider or select one or more connections for a couple of IP
addresses.
The selection can only be made on (A) which is used as reference.
Once selection is made, then the Step 2 is enabled.
Step 2
The Step 2 is aimed to find the synchronization between the two files by using up to 6 criteria:
- Source IP address
- Source Port Number
- Destination IP address
- Destination Port Number
- Identification number (corresponding to the Identification field of the IP header)
- Hash Code (MD5 Algorithm), available on the captured traffic files generated since the
version 2.4.0 of IP Traffic - Test & Measure. This Hash Code is based on the IP data
payload.
The Hash Code is very useful to identify the packets captured for example on mobile or
satellite networks. In this case, packets can go through a NAT. So the IP addresses and the
IP Identifier may be replaced. If the port numbers are changed too, the Hash Code can’t be
used anymore to identify the packets.
Synchronization
found:
Synchronization
not found:
If the synchronization is not found, you should modify the search criteria and then retry.
Remark: for example, if the receiving IP traffic system is behind a gateway that translates the
source IP addresses, don’t use the ‘Source IP address’ criterion.
When the synchronization is found (for example the packet #2 of the file (A) has been found in the
file (B) as packet #2 for the search criteria defined), the Step 3 is enabled.
Note:
if needed you can modify the search criteria or change the selection made in step 1. In this case,
you have to re-start the synchronization process
How does it work?
For packet #i in the file (A), a search is made in the file (B) by applying the user defined criteria
defined. The search uses a depth parameter (DEPTHFORPACKETANALYSIS) in order to limit
the processing time. If success, the synchronization is found and computing is stopped, else the
following packet #i+1 is considered for the next search up to the end of file (A) if necessary. If no
synchronization is found, the search is restarted but made, for each packet #i, in the whole file (B).
Step 3
You can now run the Step 3 by pressing the “Start Analysis” button n order to calculate the packet
statistics (number of lost packets, transit delay for each packet and total statistics).
As soon as processing is started, the number of packets analyzed is displayed with the percentage
already done.
How does it work?
For packet #i in the file (A), the search is made in the file (B) by applying the user defined criteria
defined in the Step 2. As the packet #i can be received fragmented or desequenced, the search
uses a depth parameter (DEPTHFORPACKETANALYSIS) in order to limit the processing time.
This process is applied to all packets contained in the two files in order to find the lost packets and
to calculate the transit delay between the two endpoints (A) and (B).
A packet is considered LOST in a source file if the search in the target file has failed on a
depth relative to the previous packet found in the target file.
Warning:
Once you have changed the value, you have to quit and re-start the IP Traffic - Test & Measure
software in order IP Traffic - Test & Measure takes into account the new value.
At the end of process, the number of packets analyzed is given and a synthesis is displayed:
- Couple of IP addresses selected
- Number of packets found corresponding to the search criteria defined in the Step 2
- Number of UDP connections found
- Number of TDP connections found
- Replay traffic duration (useful if you want to play these sniffed traffic files via the Traffic
Observer)
Note:
In this example, 25,022 packets have been analyzed (in fact 12,514 for file (A) and 12,514 for file
(B)) and 12,514 packets match the search criteria.
You can then press OK to quit this window and come back to the previous window as shown
below:
In this window, the synthesis is reminded. You can now press OK to quit the Off-line analysis.
More information on the ‘Packet Statistics’ object is explained further in this chapter.
Note:
If the captures have been realized without Time Device and zClock system, the values showed in
the “delay” column are close to the definition of the jitter. Why? The first packet found in the both
files allows realizing the synchronization. IP Traffic - Test & Measure compares the two
timestamps to calculate the delta time between the transmitting and the receiving of the packet.
Then, this delta time is added or suppressed to each transit delay calculated for each packet. That
is why the result is close to a variation of the transit delay and so close to the jitter notion.
You can select six statistics displays via the “Statistics Display”
object:
- Values
- 4 graphs:
IP Throughput
Inter Packet Delay
PER (Packet Erasure Rate) quality
Packet Transit Delay
- Packet Statistics
Before, you must select the 'IP Generator' or the 'IP Answering' part
via:
Note: switching between “IP Generator” and “IP Answering” can be done at any
time.
For each connection (from 1 to 16), the following 6 parameters (and for each parameter, Tx =
Transmit and Rx = Receive) are displayed in 3 distinct areas:
Area 1 - IP address, Port number and protocol
Area 2 - Four parameters (available on-line and off-line):
IP throughput snapshot (immediate value),
IP throughput average,
UDP or TCP throughput,
On the right area of the graphic display: ‘Statistical law to display’ and ‘Other parameters’
Notes:
PER (Packet Erasure Rate) quality and Packet Transit Delay are only available with the off-line
mode.
Time base scale for additional parameter to display is identical to the time base scale of the current
parameter.
x i
Average m: m i 1
n
n
x
2
i
Standard deviation : v (with variance v defined as: v i 1
m2 )
n
Confidence distance: 95.45 % of the values are between m 2 and m 2 .
=====>
When you change values during processing, the graphic is automatically updated with the new
values.
Status: 2 states: LOST(*) or Sent (meaning that the packet has been sent and received).
Note:
You can navigate from one LOST packet to another one in the (A) or (B) file by double-clicking the
left button of your mouse.
Transit in ms (accuracy): time expressed in milliseconds for the packet transit delay and
precision of the measure in brackets. Three values can be displayed for the accuracy:
- (?) The question-mask means that the software cannot define the accuracy of the
measurement because time stamping of packets in the source and the target files has not been
done with an absolute time reference (use of one of the Time Device i.e. z100, z200 or z300)
and a precise clock. This case is encountered in particular when the PC clock has been used
to timestamp the sent or received packets.
- (±5) More or less five means that the accuracy is less than or equal to 5 milliseconds. This
accuracy is obtained via the use of the z100/z200 GPS Time Device delivering an absolute
time reference.
- (±1) More or less one means that the accuracy is less than or equal to 1 millisecond. This
accuracy is obtained via the use of:
o the z100/z200 GPS Time Device delivering an absolute time reference and via the
zClock product delivering a very precise clock.
o the z300 NTP Time Server delivering an absolute time reference.
Ports: xxxx-yyyy with xxxx = source port number and yyyy= destination port number
IP size (protocol): IP size is the size of the IP packet (including the IP header) and (protocol) is
the protocol used (TCP or UDP).
Note:
If the sniffed traffic files contain GPS location, the location is exported into the statistics file. Two
columns are created. The first one is the GPS location of the computer when it sends the packet
and the second one is the GPS location when the other computer receives the packet.
Note:
The column "Transit Delay" available for the list of packets and for the synthesis means:
- a transit delay if the PCs have been synchronized using one of the Time Device i.e. z100, z200 or
z300
- or a transit delay variation in the other cases. In this case, the first delay is not available: it is the
reference time to calculate the delta time between both PCs. IP Traffic adds/subtracts the delta
time to the other delays calculated. The result value is a transit delay variation in millisecond.
However, it isn't a jitter in the sense that the delay variation refers to the first packet of the list
where the jitter refers to the previous packet.
Four examples are shown more precisely in the PART 14 “Examples of sniffed traffic files” at the
end of this user guide.
The statistics can be calculated on-line (real time mode) or off-line (differed time).
The off-line mode requires the analysis of two sniffed traffic files (the local traffic file and the remote
traffic file sent back on the local machine) and allows calculating parameters such as the PER
quality (Packet Erasure Rate) and the packet transit delay.
A sniffed traffic file is captured by the “Traffic Sniffer” module (with filters customizable by the user)
which stores on hard disk and timestamps all the IP frames sent and received.
Tx Throughput
Rx Throughput
Tx Packets Throughput
Rx Packets Throughput
Tx Packets
Rx Packets
Tx Volume
Rx Volume
Jitter
Volume to send
Remaining volume
Seq. numb errors (sequence numbering errors)
Mean RTT (Round Trip Time)
Min RTT
Max RTT
RTT summary (Minimum, Maximum and Mean RTT based on all RTT values calculated)
Tx Throughput
Rx Throughput
Tx Packets Throughput
Rx Packets Throughput
Tx Packets
Rx Packets
Tx Volume
Rx Volume
Jitter
Volume to send
Remaining volume
Seq. numb errors (sequence numbering errors)
Data not echoed
(1)
The Volume is the number of bytes sent to or received from the Winsock API by IP Traffic - Test &
Measure. The Winsock API doesn’t include the MAC neither the IP nor the protocols (TCP, UDP, etc.)
headers. This means for example, when using an Ethernet frame size of 70 bytes long containing a UDP
packet, the relevant IP Traffic - Test & Measure packet volume is: 70 (Ethernet frame size) – 14 (MAC) – 20
(IP) – 8 (UDP) = 28 bytes taken into account in the volume by IP Traffic - Test & Measure.
(2)
The sent volume increases as soon as the Winsock API accepts the request to send from IP Traffic - Test
& Measure.
Refresh time: this parameter defines the frequency to update the man machine interface. The
different statistical values are updated all the xx seconds (for all tabs) where xx is the value defined
by the user.
This parameter is also used to update the display of the following items:
the Time Device state (if selected)
the ‘zClock’ state (if selected)
the Uncertainty value (if zClock or a Time Device selected)
the ‘Activity’ counter
‘File size’ and ‘’Time before disk limit’ for the 'Traffic Sniffer' activity
the Statistics Export Processes (on IP Generator and IP Answering Parts)
Throughput sampling period: this parameter specifies the last traffic seconds to use in order to
calculate the throughput. More this value is high and more the average is smoothed. This
parameter is also used to calculate the IP throughput average parameter of the ‘Traffic Observer’.
Notes
Every second, the following processes are realized:
+ Calculation of the CPU load (‘Activity’ counter),
+ Calculation of the statistics for activity (‘IP Generator Activity’ and ‘IP Answering Activity’ displayed at the
bottom of the IP Traffic - Test & Measure main window).
Every 5 seconds, update of ‘Activity Sniffer’ is made (see ‘Traffic Sniffer’ - Traffic overview during capture).
These values of 1 and 5 seconds are not customizable and are fixed in the current version of the software.
Cumulative
The statistics defined in this category are cumulative statistics. They are reset when a new
connection or a new analysis is launched.
11.4.2 IP Traffic - IP Generator statistics
Calculation method Sampling Cumulative
Tx Throughput X
Rx Throughput X
Tx Packets Throughput X
Rx Packets Throughput X
Jitter X
Tx Packets X
Rx Packets X
Tx Volume X
Rx Volume X
Mean RTT (cumulative average) X
Min RTT X
Max RTT X
Sequence Error Number X
Mean RTT (summary) X
RTT Min (summary) X
RTT Max (summary) X
Tx+Rx Throughput (Activity) X
Table 1 - IP Traffic - Test & Measure - IP Generator calculation method
Mean RTT (Round Trip Time) = average of the differences between the sending times and the
receiving times (the multimedia timers of the OS are used, giving an accuracy of 1 ms – Microsoft
information). This value is available only if the packets include the Timecode information. For each
received packet, the process to find the Timecode information is applied. If the RTT identifier is
found, IP Traffic compares the "time when sent" of the last received packet with the arrival time of
this packet. The difference gives a RTT value.
To calculate this parameter, the remote must be configured in echoer mode for the connection.
RTT information
The information necessary to calculate the RTT parameter is included in each data packet, at
the beginning of the data.
Format of the RTT header (in little endian notation) is structured as follows:
4 bytes magic number (always 0x54 0x87 0x54 0x41)
4 bytes sequence number
4 bytes time when sent
2 bytes length (without the RTT header)
Min RTT = minimum value of the differences between the sending times and the receiving times
(the multimedia timers of the OS are used, giving an accuracy of 1 ms – Microsoft information) for
one connection. This is the minimum RTT value since the connection beginning.
Max RTT = maximum value of the differences between the sending times and the receiving times
(the multimedia timers of the OS are used, giving an accuracy of 1 ms – Microsoft information) for
one connection. This is the maximum RTT value since the connection beginning.
RTT Summary = minimum, maximum and average of the differences between the sending times
and the receiving times (the multimedia timers of the OS are used, giving an accuracy of 1 ms –
Microsoft information) but for all connections. The average is calculated on all RTT values of all
connections that are using the Timecode option. In others words, the average is not an average of
the Mean RTT of each connection.
Remark
The “IP Generator” builds data packets according to parameters defined by the user (contents, size
and inter packet delay). The data packets are then provided to the Winsock 2 interface to be sent
by the TCP/IP stack with the selected protocol (TCP or UDP). The volume of data sent or received
does not include the encapsulated data added by the TCP/IP stack.
The statistics in this tab are calculated at the ‘Applicative’ point of reference.
Triggers update
Each time a value is allocated to a pixel, the comparison is made with the trigger values. Then the
min or max trigger value is updated if the value exceeds the threshold.
Packet transit delay = instantaneous delay for the transfer of packets. It’s the average of the
transfer delays for all packets exchanged between two IP Traffic - Test & Measure machines. The
transfer delay (named ‘transit delay’) for a packet is the difference of time between the time when
the packet has been sent and the time when the packet has been received.
Both times – sent and received time - are stored in the record of the capture file made by the
‘Traffic Sniffer’.
x i
Average m: m i 1
n
n
x
2
i
Standard deviation : v (with variance v defined as: v i 1
m2 )
n
Confidence distance : 95.45 % of the values are between m 2 and m 2 .
Notes:
- n is the minimum between the number of calculated pixels and the number of displayed
pixels.
- the confidence distance is calculated only at the time of display.
12.2 Start IP Traffic - Test & Measure and open a context file
The context file contains all parameters of IP Traffic - Test & Measure. These parameters can be
saved in this file and reloaded later.
The command line parameter to start the IP Traffic - Test & Measure and load a context
file: -START
Syntax: -START:filename
Where filename may be:
C:\temp\Scenario4_ContextFile_PC#[Link] or
“C:\Program Files\IP Traffic\Scenario4_ContextFile_PC#[Link]”. The “ symbol is
necessary to use spaces in filenames or directories.
Example:
IPTraff –START: “C:\Program Files\IP Traffic\Scenario4_ContextFile_PC#[Link]”
Syntax: -STOP
Example:
IPTraff –STOP
Under Windows Vista, you must have the administrator rights to be able to execute the
“[Link] –STOP” command.
PART 13 Appendix
13.1 Description of the Mathematical Laws used by IP Traffic - Test &
Measure
IP Traffic - Test & Measure is based on the use of random number generation laws to determine
the starting time connection and data volume to send, and for the Inter Packet Delay in the ‘IP
Generator’ module. Four mathematical laws are offered. Uniform, Exponential and Gauss laws are
used for starting time connection and data volume. Pareto’s law is only used for data volume. The
mathematical laws are used:
For the unitary mode when the mathematical law data source is selected. In this case, only data
volume laws are available.
For the automatic mode: starting time connection generation and data volumes laws are
required parameters.
Hereafter is a detailed description of each mathematical law.
13.1.1 Uniform Law
Presentation:
The Uniform law has two parameters: and . It generates a random number included uniformly
between and . If is equal to , the generated number is always = .
With the Uniform law, the units used are millisecond for the starting time connection generation
laws and byte for the data volume to send laws.
Mathematical function:
Uniform law on ( , ) range
f ( x) 1 /( ) if x
f ( x) 0 else
Uniform law - example of generated values for 1000000 draws for this law with: 0 and
100 .
The factor 1000000 is because the figure intents to show the actual behavior of the random
generator. To do that, we draw 1000000 times a random value and count the actual frequencies.
The theoretical (= calculated values) curve and actual (= generated values) curve are displayed
below.
1
Pareto Law - example of generated values for 1000000a x with: a 10 and 1 .
(x)
2
e 2
1 2
2
45 000.00
40 000.00
Gauss law (linear scale)
35 000.00
30 000.00
Frequencies
25 000.00
20 000.00
Generated values
15 000.00
Calculated values
10 000.00
5 000.00
0.00
13
17
21
25
29
33
37
41
45
49
53
57
61
65
69
73
77
81
85
89
93
97
1
Values
Default value
Key name Type Description
(dec)
0x00000000 No traces.
DEBUGLEVEL REG_DWORD 0 0x00000001 Add errors in the trace.
0x00000002 Important information for the Support.
0x00000010 Add verbose information used by the ZTI
Communications Support.
0x00000080 Save debug information into a file
specified by the DEBUGFILENAME key.
0x00000100 Add the current time to each trace
message.
0x00000400 Add intermediate value computed during
the statistics process providing
information to the Observer Tab.
0x00001000 Detail the operation of the Sniffer
Analyzer when splitting a captured file
into data files replay.
0x00004000 Provide information for the GPS.
0x00010000 Detail operations of the Replay mode
0x00020000 Detail operations for the Off-line mode.
0x00080000 Specific flag for statistics generated at the
'IP Generator' and 'IP Answering' levels.
DEBUGFILENAME REG_SZ [Link] Filename to save the traces.
Parameter used in the search algorithm of the 'Traffic
DEPTHFORPACKETANALYSIS REG_DWORD 500
Observer' to calculate the packets statistics.
For UDP connections, timer (expressed in seconds) used
UDPINACTIVITY REG_DWORD 10 in the Generator mode to identify a connection has
stopped (10 seconds by default).
For TCP connections, timer (expressed in seconds) to
detect the 'IP Generator' has stopped the connection (10
TCPINACTIVITY REG_DWORD 10
seconds by default). “IP Traffic” closes the TCP
connection.
Maximal period (expressed in milliseconds) allocated to
SENDTIMEOUT REG_DWORD 500
send/receive data (default is 500 milliseconds).
TCPCONNECTRETRYCOUNTER REG_DWORD 0x1 Number of retry to establish a TCP connection
0x0: Nagle algorithm enabled
TCPNODELAY REG_DWORD 0x0
Other value: Nagle algorithm disabled
Buffer size (expressed in bytes) used by "IP Traffic" to
get TCP data from the Winsock2 interface. It is not the
TCPRECEIVERPACKETSIZE REG_DWORD 8192 MTU. If the size is big then the performances are better
because Winsock 2 is called less often. Max value =
65,535
When the file downloading is active, this timer
REG_DWORD 5 (expressed in seconds) is used to detect the sender has
FILETRANSFERINACTIVITY
stopped the connection (5 seconds by default). “IP
Traffic” closes the file transfer connection when the timer
is reached.
Maximum size of a packet used during a file transfer.
FILETRANSFERPACKETSIZE REG_DWORD 1460 (Expressed in bytes. Default value = 1460. Max value =
65,535).
This is the port number used by the RPC server to dialog
RPCPORT REG_DWORD 1001
with the Automation Tool.
Full path name to Aut_IPTraff .exe (“Automation Tool for
AUTOMATION PATH REG_SZ x
IP Traffic’” binary file.
Full path name to the IP Traffic - Test & Measure binary
IPTRAFFICPATH REG_SZ x
file.
Save in the registry the time reference used by the
USELOCALTIME REG_DWORD x
Automation Tool
Mode use by the traffic sniffer to capture the data on the
link. Here are the two main values:
DRIVERFILTERMODE REG_DWORD 32
0x00000020 NDIS_PACKET_TYPE_PROMISCUOUS
0x00000080 NDIS_PACKET_TYPE_ALL_LOCAL
IP Answering parameters
IP address ANY_ADDRESS
Port number 2009
Protocol TCP
Receiving working mode Absorber
Replay mode Disabled
Configuration
TCP stack parameters
Display parameters
Refresh time 2s
Throughput sampling period 5s
Connection parameters
AutoComplete parameter
Time Reference
z300 parameter
zClock parameter
File transfer
Operating Mode
Mode Local
Remote Control
Traffic Sniffer
Capture parameters
User-filters None
Type of filter used All TCP and UDP packets
Adapters selected All adapters found when
launching the software
Filename None
Save only headers No
Automatic refresh mode No
Enable automatic start No
and stop
Traffic Observer
Mode Generator
Statistics display Values
Graphical units
Section [DATA] : data size, delay (in milliseconds) before sending of next packet
Example of external data file [generation of random characters comprised between 32(decimal
value) and 48 (decimal value)]
;
; Sample DataFile for «IP Traffic» generator
;
; Section [HEADER] defines the content
; 1, char = fix character
; 2, cmin, cmax = random character
; 3, c1, c2 = alternate character
; 4, FileName = Content is based on a file
;
[HEADER]
2, 32, 48
[DATA]
100, 20
200, 10
300, 30
400, 40
500, 5
600, 50
700, 60
800, 70
10, 80
20, 10
30, 20
40, 30
50, 50
60, 60
70, 100
80, 200
Coding of characters:
character between quotes, e.g. ‘Z’
decimal value, e.g. 32
hexadecimal value, e.g. X32
BOOL CALLBACK TrafficInit( int CnxID, unsigned long IPAddr, unsigned char protocol, unsigned
port)
To init a new connection identified by par CnxID.
Parameters:
CnxID Connection identifier
IPAddr Remote IP address
Protocol Protocol to use (UDP or TCP)
Port Port number
Return codes:
True The DLL is ready to provide data to the IP Generator.
False The DLL can’t provide data. The complementary error code is handled by the
DLL and the DLL must warn the user directly.
Remark:
When a connection must use an external DLL, the IP Generator module verifies that the DLL is
present (via LoadLibrary). Then it looks for the 3 required entry points. TrafficInit() is called when a
connection is established with the remote.
13.6.2 PacketDelay
Parameters:
CnxID Connection identifier
pulDelay Address for delay expressed in milliseconds
Return codes:
True The DLL has provided the delay for the next packet. If this delay equals 0, the
IP Generator calls immediately PacketData().
False The DLL has not provided a delay. The IP Generator stops the connection.
Remark:
The PacketDelay() function is used to get the delay before a new packet contents.
13.6.3 PacketData
BOOL CALLBACK PacketData( int CnxID, unsigned short usBufferSize, unsigned char *pBuffer,
unsigned short *pusUsedSize)
Parameters:
CnxID Connection identifier
usBufferSize Max size of the buffer (pBuffer)
pBuffer Address of data to send
pusUsedSize Address of the data size to send. If size equals 0, a new delay is asked.
To avoid a ‘deadlock’, it is not authorized to provide more than 2 data packets with a
zero size.
Return codes:
True The DLL has provided data to send immediately.
False The DLL has not provided data. The IP Generator stops the connection.
Remark:
Before calling the PacketData() function, the buffer pointed by pBuffer is initialized with zeros. The
used length is initialized with zeros. The maximum size is 1460 in the sample.
13.7 IP Traffic - Test & Measure features versus OS, protocols and IP
versions.
The array below shows the IP Traffic - Test & Measure features based on the Windows versions,
on the protocols and on the IP versions. The cross in a cell indicates when the feature is available.
The test configuration used to generate three first traffic files is defined as below:
PC # A PC # B
[Link] [Link]
1 UDP connection
Port = 2011
IP Network
with impairments
Port = 2010
IP Traffic 1 TCP connection IP Traffic
« Sniffer » « Sniffer »
In the Step 1 the couple of IP addresses [Link] [Link] is selected. Then the
synchronization between these two files is found for the step 2. After running the step 3, the
synthesis is displayed showing 1 TCP and 1 UDP connections.
By using the “Packet Statistics” option, the following results are displayed.
In this example, 3 UDP packets have been lost and the transit delay has an average of 178 ms for
the UDP connection. 3 TCP packets sent by the PC #B have been lost and the average for the
transit delay is 8 ms. Note also that 3 TCP packets sent by the PC #B have been retransmitted.
Note:
The ‘Transit …’ column contains the symbols (?) to indicate that the accuracy for measurement
cannot be defined (no common clock reference between the PCs and the PC clock is used for
packet time stamping by the IP Traffic Sniffer when capturing the packets).
By using the “Packet Statistics” option, the following results are displayed.
In this example, 5 UDP packets have been lost and the transit delay has an average of 184 ms for
the UDP connection. 4 TCP packets sent by the PC #B have been lost and the average for the
transit delay is 1 ms. Note also that 4 TCP packets sent by the PC #B have been retransmitted.
Note: the ‘Transit …” column indicates the symbols (± 5) in order to precise that the accuracy for
measurement is less than or equal to 5 ms (due to use of the z100 Time Device that delivers a
precise time reference used for packet time stamping by the IP Traffic Sniffer when capturing the
packets).
Example 3: use of the z100 Time Device and the zClock module
In this example, 6 UDP packets have been lost and the transit delay has an average of 186 ms for
the UDP connection. 4 TCP packets sent by the PC #B have been lost and the average for the
transit delay is 1 ms. Note also that 4 TCP packets sent by the PC #B have been retransmitted.
Note: the ‘Transit …” column indicates the symbols (± 1) in order to precise that the accuracy for
measurement is less than or equal to 1 ms (due to use of the z100 Time Device that delivers a
precise time reference and the zClock module used for packet time stamping by the 'Traffic Sniffer'
when capturing the packets).