IxTutorials

Running UCSniff to Eavesdrop on IxLoad VOIP Emulation

noreply@blogger.com (Anonymous) — Thu, 22 Nov 2012 04:59:00 +0000

I've setup a VoIP emulation in IxLoad, where i enabled voice and video to simulate a video call. You can just use a VoIP template in IxLoad to setup then enabled both audio and video on the voip tabs. I've also used an Anue network emulator to toggle with the bandwidth to mess with the QoE of my test. One of the ports from my Ixia traffic generator is connected directly to one of the ports of the Anue NE and the other ports of my traffic gen and anue are connected to the switch. I have another laptop thats running Ucsniff (under ubuntu) which is also connected to the switch. The sniffer must be connected to the switch in order to do arp poisoning, else it will not work. Apply the IxLoad config to your test ports before running the UcSniff. If you try to run the UcSniff first it won't be able to see other hosts in the network and it will fail to load. Remember it's trying to do arp to get the IP and MAC addresses in the network. Once both are loaded you can then start your test. Now I included a network emulator to mess around with the QoE, you can enable the MOS scoring in IxLoad to provide you subjective tests scores and we'll be using the extracted video from the UcSniff to check the effects of the impaired network to the video.

After the test, I need to rename/copy the *.264 file to an .h264 for your to be able to play it in VLC or MPlayer. Sometimes it will not play well on those players so I need to convert them manually using mencoder. You can check AV muxing in UcSniff, then again, it doesn't work all the time. After i convert it to a proper video format, you can see that the video quality degrades once we toggle the bandwidth and became viewable again when i turned the NE off.

GGSN Test (Back-to-Back)

noreply@blogger.com (Anonymous) — Thu, 19 Apr 2012 05:55:00 +0000

This is a test in IxLoad where we emulate GTP-SGSN and GTP-GGSN. In this scenario, all GTP tunnels are being established during HTTP traffic.

In this scenario, All GTP tunnels are established first before the HTTP traffic starts.

Adding webGUI automation in IxNetwork using Sikuli

noreply@blogger.com (Anonymous) — Wed, 21 Dec 2011 00:19:00 +0000

Sikuli uses screenshot to do GUI automation. The first part of the video shows the script to invoke Chrome browser, go to a Dlink router emulator site and navigate through the setup. We'll run it first in Sikuli to make sure that the script is running perfectly then save the config.
Start the IxNetwork's Test Composer, from the composer, look for and choose "run process". From the run process, type in the path of the sikuli cli exe file plus an argument of -r (run) and the save script file.

i.e. c:\program files\sikuli x\sikuli-ide.exe -r test.sikuli

Now in Test Composer, just add a wait time or sleep time after the run process followed by whatever steps you have in your configuration.

Using SNMP in TestShell

noreply@blogger.com (Anonymous) — Mon, 19 Dec 2011 22:25:00 +0000

IxAutomate scripts running on TestShell

noreply@blogger.com (Anonymous) — Tue, 20 Sep 2011 09:58:00 +0000

This shows how to run IxAutomate using Qualisystems TestShell, all raw data are also generated in IxAutomate's default logfile paths. Since it run over a third party automation tool, it will not appear in IxA data miner.

Integrating IxNetwork 6.0 in Qualisystems TestShell

noreply@blogger.com (Anonymous) — Thu, 04 Aug 2011 06:57:00 +0000

Migrating Configs in IxNetwork

noreply@blogger.com (Anonymous) — Mon, 22 Nov 2010 08:40:00 +0000

L3VPN Demo with Stateless and Stateful Traffic

noreply@blogger.com (Anonymous) — Wed, 29 Sep 2010 06:10:00 +0000

This is to show you how easy it is to setup an L3VPN and run L2-3 traffic and application traffic simultaneously to deliver realism in network testing.

noreply@blogger.com (Anonymous) — Tue, 21 Sep 2010 02:22:00 +0000

Latency - latency in communications network is defined as the time it takes for a message to traverse the network from a transmitter to the receiver.

-www.ruggedcom.com

Cut-Through latency - is a type of timing measurement used for switches and other devices that operate using packet header information. The cut-through type measures the time interval between the first data bit out of the transmit port and the first data bit received by the receive port. The first data bit received on Ethernet links is the start of the MAC destination address field.

Store and forward latency - is a type of timing measurement used for routers and other devices that operate on the contents of the entire packet. The time interval between the last bit out of the transmit port and the first data bit received by the received port is measured. The last data bit out is usually the end of the FCS or CRC and the first data bit received is as described below for cut-through.

MEF frame Delay - is based on MEF 10.1 and RFC 3393 standards. They consist of the time interval starting when the first bit reaches the input port and ending when the last bit of the output frame is seen on the output port (first in, last out).

Forwarding Delay - is a last-in, last-out (LILO) measurement which is based on RFC 4689. The LILO method most closely simulates the way a network layer device actually processes an IP datagram. IP datagrams are not passed up and down the stack unless they are complete, and processing begins only once the last bit of the IP datagram has been received.

Delay Variation - The difference between the two consecutive frames in a flow with any lost packets being ignored.

DDoS How-to

noreply@blogger.com (Anonymous) — Mon, 20 Sep 2010 02:19:00 +0000

Record your screencast online

This is to show how to create a DDoS configuration in IxLoad plus adding the packet monitor that will identify packets in a DDoS attack that the DUT has failed to capture or stop.

IxDefend Demo

noreply@blogger.com (Anonymous) — Mon, 13 Sep 2010 09:28:00 +0000

Record your screencast online

I've used two web server applications here to showcase the robustness of the two apps. I'm running identical test cases (i.e. Testcase# 0 - 60). The first web server was able to pass all test cases giving it more robust to packet anomalies, while the second web server crashed at testcase# 53 which is an overflow attack. Check the video for more detailed results.

Case Study: Network Resiliency Test Using Stateful Traffic

noreply@blogger.com (Anonymous) — Wed, 14 Jul 2010 08:07:00 +0000

What is HTTP?
HTTP is a client-server protocol by which two machines can communicate over a TCP/IP connection. An HTTP server is a program that sits listening on a machine's port for HTTP requests. An HTTP client (we will be using the terms HTTP client and web client interchangeably) opens a TCP/IP connection to the server via a socket, transmits a request for a document, then waits for a reply from the server. Once the request-reply sequence is completed, the socket is closed. So the HTTP protocol is a transactional one. The lifetime of a connection corresponds to a single request-reply sequence. (a transaction) HTTP is the protocol used for document exchange in the World-Wide-Web. Everything that happens on the web, happens over HTTP transactions. TCP/IP networking and HTTP are the two essential components that make the web work.

How it works?
The Hypertext Transfer Protocol (HTTP) is actually quite simple. The web browser (or client) makes a request of a webpage to the server, and the webserver passes the page back to the browser. More cleverly, it also passes back any images, sounds or other media items back to the browser too.
The web browser is also particularly clever in the way it displays what it retrieves.

Various versions of HTTP
HTTP 1.0

Now Obsolete
Each transaction requires new TCP session
Server closes the session s
Slow

HTTP 1.1

Current
Multiple Transaction in a single TCP session
Client closes the sessions
Fast and better bandwidth management

HTTP 1.0 Packet Flow

HTTP 1.1 Packet Flow

Http 1.1 uses multiple transaction with in the same TCP connection. Here, we have 2 transactions with thesame TCP sessions.
Client closes the connection. Notice the FIN/ACK is being sent by webclient

Topology

Objective

To test resiliency of TCP session over the network when there is an induced network failure
Record resiliency values when HTTP timers are modified

Configuration Walkthrough
Emulating 2 hosts on either end of the network. Following are the traffic pattern;
30.0.0.2 ----HTTP Traffic ----> 40.0.0.2
30.0.0.6 ----Stateless Traffic ----> 40.0.0.6

network configuration

TCP configuration

Web client configuration 01

Web client configuration 02

Web client configuration 03

Web server configuration 01

Web server configuration 02

Web server configuration 03

Case Study 1: Standard Configuration

Run HTTP traffic with default values timers. i.e. HTTP client command timeout 60sec in line with Internet Explorer defaults
Flap the network between R1 and R2 to collect resiliency time

Note: Increase the HTTP keep-alive timeout interval on the Web server or the proxy server. There is no setting in Microsoft Internet Information Services (IIS) to control the keep-alive timeout other than the Windows registry KeepAliveTime value. But with some Web servers and some proxy servers, you can specify a connection expiration time. If you can specify a connection expiration time in the Web server or the proxy server, increase the keep-alive timeout interval. See your Web server documentation for the correct setting name and value. The default keep-alive timeout value for Internet Explorer is one minute (60 seconds). Therefore, you must use an HTTP keep-alive timeout interval on the Web server or the proxy server that is greater than one minute. http://support.microsoft.com/kb/831167
Baseline Results

Throughput reach 10mbps

Transactions, sessions objective reached

SYN and SYN/ACK = to 1

No frame loss on the stateless traffic

FLAP the Network!!!

TCP connection drop to ZERO as expected

Stateless traffic packet loss duration logs at about 6.5ms of packet loss

After the HTTP command timeout values = 60sec sessions comesback again

Conclusion
§

Network resiliency tests are more accurate using stateless traffic generation and capture the accurate value via Packet Loss Duration method.
Using Stateful TCP protocol is not the best way as the resiliency is dependant on many parameters like TCP timeouts and Application layer protocol time outs (In this case HTTP)
Although Stateful protocols can be tweaked to achieve closer resiliency values (in this case, Command Timeouts), they are not real world scenarios.
Ref: http://support.microsoft.com/kb/831167 for default Internet explorer time out values

Courtesy of Bala

Running IxChariot in Command Line

noreply@blogger.com (Anonymous) — Thu, 24 Jun 2010 03:15:00 +0000

This video shows how to run IxChariot over CLI. We have two commands that we could use runtst.exe and fmttst.exe.
runtst.exe executes any .tst files (i.e saved configurations from the console) we have several options but we'll just use -v (verbose mode). So the syntax will be:

runtst -v ### this outputs the run results in your cmd prompt
runtst -v ### this saves the result to a new test file, when you open the in the console, it shows the results with it.
runtst -v > file.txt ### this writes the output to a text file

fmttst -v ### writes the test file to a csv format.

All of the commands above can be written in a batch file and you can use the windows scheduler to run all your tests.

WebServer Testing with Authentication

noreply@blogger.com (Anonymous) — Thu, 01 Apr 2010 06:05:00 +0000

Capture your screen in seconds

Y.1731 Test

noreply@blogger.com (Anonymous) — Wed, 31 Mar 2010 09:56:00 +0000

Record your screencast online

This shows on how to test Y.1731 using 2 test ports, it also shows how to simulate AIS and learn CCM defect and no defect.

Video Multicast Test Using IxChariot

noreply@blogger.com (Anonymous) — Tue, 30 Mar 2010 09:39:00 +0000

Capture your screen in seconds

Creating L2/3 traffic using QuickFlow Groups (easy!!!)

noreply@blogger.com (Anonymous) — Mon, 15 Mar 2010 06:46:00 +0000

Capture your screen in seconds

You can easily create L2/3 traffic using QuickFlow Groups in just a few clicks and gives you the same stats as the one in basic or advanced wizards.

IxLoad's App-Replay [custom-ip]

noreply@blogger.com (Anonymous) — Wed, 10 Mar 2010 03:59:00 +0000

Record your screencast online

1. Add a network for both originate and terminate. Do not configure IP's yet.

2. Add the App-replay in the "traffic" pull down menu.

3. In the App-replay click "plus sign" icon and choose custom ip.
4. Disable loop iteration as shown in the picture and check "use ip from captured file"

5. Now check on the IP addresses used in the pcap (refer to the video) and edit the IP addresses in the network (originate and terminate) to have the same ip address as the captured file.

6. On the test objective you could use either the basic timeline or advanced which uses linear timeline.

Measuring Service Disruption Time using Packet Loss Duration

noreply@blogger.com (Anonymous) — Wed, 24 Feb 2010 07:08:00 +0000

Record your screencast online

QoS Marking in IxLoad

noreply@blogger.com (Anonymous) — Thu, 04 Feb 2010 04:18:00 +0000

Free online screencasting tool

Custom-IP in App-replay

noreply@blogger.com (Anonymous) — Thu, 04 Feb 2010 03:01:00 +0000

Capture your screen in seconds

Creating Layer 3 Traffic with QoS marks

noreply@blogger.com (Anonymous) — Tue, 26 Jan 2010 06:56:00 +0000

This is one way of creating layer 3 traffic in IxNetwork. I've configured IP addresses on the test ports, marked the same traffic item with three different ToS values. This method is useful in a routed environment, so you don't need to manually key in the destination MAC addresses in your traffic flows.

Latency Measurement Using IxExplorer

noreply@blogger.com (Anonymous) — Tue, 19 Jan 2010 08:03:00 +0000

Creating Layer 2 Traffic

noreply@blogger.com (Anonymous) — Thu, 07 Jan 2010 07:27:00 +0000

Web server Testing

noreply@blogger.com (Anonymous) — Mon, 04 Jan 2010 03:13:00 +0000

Capture your screen in seconds