IxNetwork Specialist September 2013-Jp

IxNetwork Specialist
6
6
0 01
1 Ag
our
a
Rd.
Cal
aba
sas
,
COURSE # 985-2002
CA
91
September302013
2
(Tol
l
Fre
e
US)
7.F
OR.
© IXIA 2013 September IXI
A
(Int
’l)
+1.
Copyright © 2013 Ixia. All rights reserved.
This publication may not be copied, in whole or in part, without Ixia’s consent.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in
subparagraph (c)(1)(II) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19.
Ixia, the Ixia logo, and all Ixia brand names and product names in this document are either trademarks or registered trademarks of Ixia in
the United States and/or other countries. All other trademarks belong to their respective owners.
This material is for informational purposes only and subject to change without notice. It describes Ixia’s present plans to develop and
make available to its customers certain products, features and functionality. Ixia is only obligated to provide those deliverables
specifically included in a written agreement between Ixia and the customer.
Corporate Headquarters Ixia Worldwide Headquarters Web site: www.ixiacom.com

26601 W. Agoura Rd. General: info@ixiacom.com
Calabasas, CA 91302 Investor Relations: ir@ixiacom.com
USA Training: training@ixiacom.com
(877) FOR IXIA (877-367-4942) Support: support@ixiacom.com
+1 (818) 871-1800 (International)
(FAX) +1 (818) 871-1805
sales@ixiacom.com
EMEA Ixia Europe Limited Support: eurosupport@ixiacom.com

Globeside Business Park Building One Unit +44 1869 356370 (Option 5)
A
Marlow, SL7 1 GJ
United Kingdom
+44 1869 356370
(FAX) +44 1869 356371
ixiaeurope@ixiacom.com
China Ixia China Support:support-china@ixiacom.com
Unit 1103, Raffles CityBeijing Office Tower, +86 400 610 6988
No. 1 Dongzhimen South Avenue
Dongcheng District
Beijing 100007
China
+86 10 57323900
saleschina@ixiacom.com
Japan Ixia KK Support: support@ixiacom.com
AioiSampo Shinjuku Building, 16th Floor 3- +1 (818) 871-1800
25-3 Yoyogi Shibuya-Ku
Tokyo, 151-0053
Japan
+81 3 5365 4690
(FAX) +81 3 3299 6263
ixiajapan@ixiacom.com
India Ixia India Support:support-india@ixiacom.com
7th Floor Umiya Bay +91 80 49396408
Cessna Business Park
Outer Ring Road
Bangalore - 560037
Karnataka,India
+91 80 49396400
ixiaindia@ixiacom.com
Ixia Professional Services Offerings
© IXIA 2013 September

Table of Contents
IxNetwork Introduction 1
Lab 1 – Working with Scenario Editor 17
Lab 2 – Port Management 46
Lab 3a – Engage Ospf Protocol Configuration 59
Lab 3b: BGP Protocol Configuration 73
Basic Traffic Wizard 89
Lab 4: Basic Traffic Wizard 112
Advanced Traffic Wizard 129
Lab 5: Additional Field tracking with the Advanced Traffic Wizard 151
Quick Flow Groups 173
Lab 6: Raw Traffic using Quick Flow Groups 186
Lab 7 – Configuring L3VPN with Scenario Editor 197
Lab 8 – Configuring IPv6 with Ospf v3 239
Lab 9 – Configuring Multicast with Scenario Editor 273
Lab 10a – Test Composer Pre-Lab 299
Lab 10b: Test Composer Scripting Lab 321

Lab 11: Macro Recorder Lab 337
Lab 12: Open Flow Lab 347
Lab 13 a: Setting up Ospfv2 before running RFC 2544 Test 371
Lab 13 b: Running RFC 2544 Test 391
Lab 14 a: Setting up Ospfv2 before Running Cloud Performance Test 407
Lab 14b: Configuring and running Cloud Performance Quick Test 425
APPENDIX 441
IxNetwork Specialist 1
IxNetwork Introduction
Overview
IxNetwork is a tool for testing routing, switching, authentication and access protocols. We will
cover the basic routing protocol configuration process and perform through a general workflow a
test for generating traffic over advertised routes using various methods of measuring and
evaluating the performance and operational integrity of a router, switch or system under test.
The emphasis of this course is on traffic generation and measurement. The subtleties of individual
protocol technologies and configuration are covered in separate courses available through Ixia as
lecture/lab or online e-learning courses.
© IXIA 2013 September IxNetwork Introduction

2 IxNetwork Specialist







Lab 1 – Working with Scenario Editor
Overview
The first step in using IxNetwork is to allocate ports, either real or virtual (offline) for subsequent
protocol and traffic configuration. We will use the Scenario Editor to connect to chassis and take
ports. Numerous options are available for setting additional L1 and L2 parameters to coincide with
the requirements of the test procedure and to correspond with the load modules in the Ixia chassis.
In this lab we will allocate the ports to be used with Scenario Editor and subsequently demonstrate
various ways to manage and manipulate the port status and parameters.
Lab Objectives
Students who complete this lab will be able to:
 Create a New Topology by connecting to Chassis and taking ports using the Scenario Editor.
 Configure the Ospf Protocol in the Classic Mode.
 Control the various L1 parameters of their ports.
 Save these parameters for subsequent invocations of IxNetwork.
Ospf Test Topology with Ixia Port Emulation
© IXIA 2013 September Working with Scenario Editor

Test Topology with Ixia Chassis

See Figure 1for the topology of this test. This topology diagram shows the physical wiring and
layout of the Ixia chassis, as well as the devices that are used for running the tests.
Figure 1: Port Management Topology

Description of Lab Procedure

This test procedure will consist of the following major steps as listed below.
A. Click on the Scenario Editor Icon and further Click on the “+” Sign next to
“New Topology”.
B. Connect to Chassis and take allocated Ports.
C. Use the Protocol Wizard to create an Ospf/IP Stack in the Classic Mode for a given topology.
D. Learn the various L1/L2 port options and other tweakables parameters for the ports
E. Set the stage for running the Protocol.
Procedure
1. Acquire your user number from your instructor before proceeding with this lab. Your
number will determine your PC, chassis ports and IP address assignments as indicated in
Appendix A.
2. If not done already, connect to your assigned PC and start IxNetwork on your desktop.
3. The First screen that will appear after successfully launching IxNetwork will be the four
quadrants with selection on “Overview” as shown. We do have the option of Clicking on the
first quadrant marked as “Click here to configure Ports” and proceed in the traditional way
to select the chassis and the ports. We will however choose to use the option of Scenario
Editor marked as “Scenario” to the Left in the Resource Tree to select the Chassis and Ports.

4. In order to start the configuration with the Scenario Editor, select “Scenario” in the Test
Configuration window. This will present a New Screen with a “+”sign next to “New
Topology” button. In order to start the configuration with the help of Scenario Editor, click
on the “+”sign next to “New Topology” as shown.
5. Following screen appears that has the option of adding Ports as “Add Ports” under the
heading of “Ixia Ports” as shown.
6. On the top side of the screen labeled “Protocol Wizard”, select the button to Add chassis
and ports by clicking on “ + Add Ports”. Following Screen will appear that will display that
has the following options –
a) “+ Add Chassis”
b) Recently Used Chassis
If the IP of the Chassis is not listed under the “Recently Used Chassis” then add the IP of the
Chassis provided by the Instructor by clicking on “+ Add Chassis” and press Enter.
If the IP of the Chassis provided by the Instructor is already listed under the “Recently
Used Chassis” option, then click on it to connect.

7. Wait for the chassis connection to be established which should display a green circle with
the IP mentioned next to it. This indicates that the Chassis is up. Also below the Chassis, all
the active ports would be displayed as shown as green indicating the status as up under
each card. At this point you would need to select the ports that have been assigned to you by
your Instructor. If you do not know your ports, kindly ask your Instructor for your user
number along with Card and Ports assigned to you for doing your further Labs.
8. Expand the Card(s) your ports are on, highlight your ports, and select the double arrow
button to add ports by clicking on “Add ports” and push them to the right under “Ports in
Configuration” as shown.
9. Wait for the ports to reset. After a couple of seconds the ports will return to green as shown
below giving details of Status, Name and Chassis/Card/Port. If you notice that the “Mapped
To” Tab is empty as the ports have not been appended and pushed to the right.
10. Select the Ports by highlighting them as shown and further click on “Append Ports” to send
the ports towards “Ports in New Topology” as shown. The Protocol Wizard now shows a
New Icon of “Protocols” that will be configured at some point later. Click on “Next”

11. At this point Ixia IxNetwork 7.0 introduces the two modes under “Protocols” Tab to select
the protocol type to be configured –
a) Classic Mode – Includes all the Legacy Protocols that you can configure.
b) Next Gen Mode - protocols that efficiently scales to very large port and protocol session
counts.
Next Gen Protocols - Introduction
The protocols migrated to the new framework are categorized as NextGen protocols. You can
create a compact protocol configuration for the NextGen protocols that efficiently scales to very
large port and protocol session counts.
Advantages of Next Gen Protocols over Legacy Protocols
Configuring protocols using the new framework has a number of benefits over configuring the
legacy way.
Improve Usability
 The NextGen Architecture improves usability in the following ways:
 Presents all protocols in a single tree, with consistent look and feel across all protocols.
 Provides new configuration concepts (device pools) which make it easier to configure
and manage complex scenarios.
 Presents configurations in a scalable, compact form, which is fast to create and edit and
easy to understand.
 Provides inline state feedback, so that the user can quickly understand what is going on
with the test.
Improve Functionality
 The NextGen Architecture improves functionality and inter-networking in the following

ways:
 Removes the barriers between the current Stack Manager and Routing/Bridging
protocols. Any protocol may use layer interfaces created by any other.
 Provides new configuration concepts (device pools) which model the connected
relationship and dependency between protocols that don’t share the same interface.
 Gives all protocols access to framework features, such as changes and actions on the fly
and learnt information.
Improve Scalability
 The NextGen Architecture improves scalability in the following ways:
 Models all protocols and configuration data using a new multi-value based properties
that can represent thousands of sessions in a single range and row in the GUI, yet
provide detail view and full read/write access to individual protocol sessions.
 Exposes the port group concept into IxNetwork, so that a single configuration may be
distributed across multiple ports.
 Removes some of the existing legacy code roadblocks to moving to a 64 bit operating
system.
Scenario Editor provides a single common framework containing Stack Manager, Routing-
Bridging, wireless, and all new NextGen protocols. It enables you to create a compact
protocol configuration that efficiently scales to very large port and protocol session counts.
By visually modeling the logical configuration of the protocols, you will have a much clearer
picture of the network test topology.
12. For this configuration we will be using the Classic Mode to configure Ospf. Select the
“Classic Mode” and further select “Ospf” as shown –

Ixia IxNetwork 7.0 has an option of configuring Ospf with Next Gen and can be used as an
option when the customer requirements include improved usability, improved functionality
and improved scalability. In our configuration we will configure Ospf in the Classic Mode.
13. Select “Ospf” and further select “New Wizard Run” and click on “Run Wizard” a shown
below
The Wizard will take you through a step by step process of configuring Ospf v2 by –
1. First Selecting Port/Ports

2. Selecting Number of Routers that you would like to emulate on each port.
3. Providing IP address of the emulated Routers and the Gateway Address
4. Choosing the Incrementing Factor (Per Port/Per Router)
5. Advertising Routes on these Emulated Routers.
6. Saving the above configuration with a Name.
14. Select the First Port by putting a check mark next to your first assigned port as shown and
further click on “Next”–

15. Enter the IP address (Tester IP Address), Gateway Address (Gateway IP Address) and
mainly add the “Number of Emulated Routers per Port” as per the
scenario/topology/User No. provided by the Instructor and click on “Next”.
16. Put a checkmark next to “Advertise Routes” and enter the “Number of Routes Per
Router” as 10 and enter your “First Route” as per the “Lab Parameter Table” provided at
the end of the Lab Manual as shown. Please make sure to change “Increment By”(Per
Router) parameter mask from 0.1.0.0 to 1.0.0.0 to avoid overlapping of routes between
Users.

17. Screen Number # 4 of 6 includes Network Range –

The optional ospf Wizard-Network Range dialog allows the user to create a matrix/grid of
Ixia-emulated Ospf (v2) networks. The size of this network range matrix is determined by
the number of rows and columns configured. For example, a network range with 10 rows
and 10 columns will contain 10 times 10 Ixia-emulated routers, connected horizontally and
vertically by Ospf Network Range links (subnets).
We can skip the 4 # 6 screen number as we are not going to create subnets behind the
emulated Routers in this Lab Exercise.
18. The OSPFv2 Advanced Interface Settings-Network Range TE dialog box allows you to
configure Traffic Engineering parameters for links to virtual Ospf topologies created with
the Ospf Network Range feature. We can also skip the 5 # 6 screen numbers as we are not
going to configure traffic engineering parameters in this Lab Exercise.
19. On Screen number 6# of 6 select the Radio button that says “Generate and Overwrite
Existing Configuration”, give a relevant name “Ospf_Port_1” and further click on “Finish”
to complete the configuration for Port1.
20. Following screen appears indicating the use of the Scenario Editor to configure properties
on the 1st Port. The screen shows the “Ospf” and Interface as a Stack and as a Part of a
Device Group identified with a name as “Device Group 2” in this case under “Topology 1”.
Note
The Ospf tab is in Gray and the Interfaces tab is in Green. This is mandatory and it indicates
that your configuration on the 3 Protocol Interfaces on Port 1 is correct and also indicates that
the Opsf Protocol is yet to be started.

Elements of a Scenario
Scenario presents all the protocols in a single tree with a consistent look and feel across all
protocols. It enables you to create a scalable compact configuration using the following:
Topology – An arrangement of the network elements used for configuring large scale, complex
routing/bridging network simulations. It is a collection of test ports and can contain multiple
Device Groups.
Device– A simulated network element, which can be a router, host, switch, and so on. A Device
can run multiple protocols and protocol stacks. Thus, when we configure a Device, we add or
remove protocols that we want to simulate.
Device Group – A group of n similar Devices per test port. Device Groups model devices that
run protocols and interact with the DUT. A Device Group count is the number of instances in the
group. A configuration can be scaled by modelling a group of n Devices per test port by
changing the multiplier.
Port Group – A set of similar ports, which share the same device group configuration. All ports
in a Port Group must have the same interface type. A Port Group may contain many Device
Groups. A Port may belong to one Port Group and a Device Group may belong to only one Port
Group. Device Groups are connected to a Port Group and the configuration replicated on each
port in the group.
Connectors – Connects the Device Groups to ports and other Device Groups. When Devices are
connected, the Group size is the product of the Device Group size property and the Group size of
the upstream device.
Multiplier – Increases the count of Devices in a Device Group.
Network Group – A Network Group represents a set of L3 networks (sub-netted or switched)

with optional information explaining the reachability to each of these networks. All Devices
connected to a Network Group must belong to one of the networks modelled by that Network
Group.
Protocol – A Protocol represents a set of protocol emulation sessions running in the context of a
Device Group.
21. In order to create a configuration on Port 2 click on the “+ New Topology” as shown –
22. Following screen appears, with Port 1 Mapped To Topology 1. Next we will attempt to
Map Port 2 with Topology 2.
23. In order to configure Port 2, select your Port 2 and further click on “Append Ports” as
shown and click on “Next”
24. There are two modes under “Protocols” Tab to select the protocol type to be configured –
c) Classic Mode
d) Next Gen Mode
25. For this configuration we will be again using the Classic Mode to configure Ospf. Select the
“Classic Mode” and further select “Ospf” as shown for Port 2 as well.

26. Select OSPF once again and note that there is already a configuration for Port 1 and the
selection by default is on “New Wizard Run”. Click on “Run Wizard” to start the
configuration for Port 2.
27. Select the Second Port by putting a check mark next to your first assigned port as shown
and further click on “Next”–

28. Enter the IP address (Tester IP Address), Gateway Address (Gateway IP Address) and
mainly add the “Number of Emulated Routers per Port” as per the scenario/topology
provided by the Instructor and click on “Next” for the Second Port as shown -
the end of the Lab Manual a shown. Please make sure to change the “Increment By”(Per
Users.
2. Skip Screen number 4# of 6 and Screen Number 5# of 6.

3. On Screen number 6# of 6 select the Radio button that says “Generate and Overwrite
Existing Configuration”, give a relevant name “Ospf_Port_2” and further click on “Finish”
to complete the configuration for Port2.
4. Following screen appears indicating the use of the Scenario Editor to configure properties
on the 1st Port. The screen shows the “Ospf” and Interface as a Stack and as a Part of a
Device Group identified with a name as “Device Group 4” in this case under “Topology 2”.
5. At this point we have both Configurations on Port 1 and Port 2 successfully completed. In
order to verify there are a few caveats that should be considered –
a) Color on Ospf tab should be gray (as seen above)
b) Color on Interface should be Green (as seen above)
c) Protocol Interfaces on both ports should not have any exclamation Marks. (as seen
below)-

d) Color of Opsf on the Resource tree should also be gray – (as seen below)
e) Color on Protocol Interfaces should be Green – (as seen above)

f) The Color on Ports should also be Green – (as seen below)
Before engaging the Protocol for the above configuration, we will take a deeper look into
the editing of L1/L2 properties of the ports. The next chapter includes Port Management
with a deep dive into Tweaking Port speed, Media Mode, Reboot CPU etc. The ribbon on
top, after selecting the ports highlights the properties of ports that can be changed. ( as
seen below) –
CONTINUED AT ENGAGE OSPF PROTOCOL CONFIGURATION IN PAGE 59

© IXIA 2013 September Port Management



Lab 2 – Port Management

The Port Manager screen provides a table displaying many of the L1 and chassis port
behavior parameters and they can be modified from this table as well. The large number of
parameters would make the table inconveniently wide. At the bottom of the display there
are two tabs labeled General and Ethernet which when selected will display a table with a
select subset of parameters. Select Ethernet tab to display those related parameters.
1. If you click in the “Speed Ethernet” cell, there is a drop-down menu. Uncheck “Auto
Negotiate” and you will then be able to select a specific speed and duplex. Click OK at the
bottom of this drop down window.
2. Note at the top of the screen, an Apply and Undo button are now selectable. The changes
you make here are not downloaded to the chassis until you select Apply. Until then, you can
Undo your changes one at a time, or reverse that and Redo your changes one at a time. Once
you select the Apply button, you will not be able to undo or redo anything that had been
done up to this point. Make sure that you select Undo to set back to Auto Negotiate!
3. You may create a customized table displaying only those parameters you are interested in.
At the lower left bottom of the table, select the tab to the right most. Holding the cursor
over this will result in a pop up balloon stating Create New page. Click on this tab to display
a dialog that will allow you to pick and choose fields for your newly created tab.

4. Your table starts out with 3 default columns to which you can add. Expand Ethernet on the
left, select all items and move them to the right side using the center arrow. From here,
expand the General entry and select Connection Status and move to the right. Then select
OK.
5. At the bottom you will see a new tab called New Grid. If you select it, your custom table will
display. Right click in the tab and select Rename from drop down menu.
6. Rename the grid to “My Grid”. Remember to use the checkmark on the right side of the
rename window to accept your changes.
7. If you wish to modify the column fields in an existing table, right click in the header row and
select Column Chooser. The chooser in the previous step will reappear allowing you to add,
remove, or reorder the columns.
8. Return to the General tab. Right click on your second port and select Simulate Link Down.
That port will now turn red.
9. Right click in the column called “Connection Status” and select the “Group By This Column”
option.
10. Although more useful when there are more ports to work with, you can see the table has
now divided up the grouping of ports based on the state described in a new title line.
11. If you want to go back to the default view, right click on the tabs at the bottom and select
“Restore Default”. Make sure to simulate link up for the second port so that both ports
show link up!

12. An alternative and more conventional way to configure L1 parameters is to click on the
“Edit L1 Properties” button at the top of the window.
13. This will bring up a Layer 1 Configuration screen from which you can select each port in
turn on the left and the tab for the L1 parameters on the right. Note that here, there is no
undo operation and selecting the OK button is the same as selecting Apply. Click Cancel to
return to the Port Manager Screen (see screen shot above).
14. Under the Name column, enter a more useful port name as Port 1 and Port 2.
15. Please do not Attempt Step 16 as it will reset you ports. This is just for Information
16. Select the first port by left clicking in the left most (numbered) column. Hold down the shift
key and select the second port. Both ports are now selected and highlighted. Right click
anywhere in the highlighted area and select Reboot CPU + Factory Default. When the green
circle returns for each port, the configuration will back in its original state which will be
required for subsequent lab exercises.
<END OF LAB2>

© IXIA 2013 September Ospf Protocol Configuration



Lab 3a – Engage Ospf Protocol Configuration
Overview
CONTINUED FROM WORKING WITH SCENARIO EDITOR FROM PAGE No.40
We will continue from Lab1 where we created a configuration using the Scenarios editor. The
protocol to be engaged first will be ospf. The Scenario Editor provides a fast and convenient way to
perform the initial configuration of complex protocols where manual configuration has a high
chance of error.

Lab 3a: OSPF Protocol Configuration

The Open Shortest Path First Protocol Version 2 is becoming the standard interior gateway protocol
(IGP) for large IP networks that contain complex topologies and high levels of path redundancy.
This protocol is designed to handle large routing tables efficiently and aggregate routes to reduce
routing table lookups. With network topology changes, it converges at a high speed, much faster
than RIP. Administratively determined metrics are assigned to all outbound interfaces allowing a
highly granular path selection to be made based on total path cost to the destination network.
IxNetwork will test the router by simulating a large number of routers and networks, generating
and advertising controlled link state advertisements and forwarding controlled traffic to determine
the effects and behavior of the router.
Objectives
The student will use the earlier created topology using Scenario Editor to run the protocols
Bidirectional traffic will be sent later to verify the routing table forwarding process.
The LSA’s will be manipulated to demonstrate how the DUT will receive and advertise them.
 Run the protocol and evaluate the operational state of the interfaces.
 Use the multiport grid feature to change values in the parameter tables.
Topology
Two ports on the Ixia will each emulate three OSPF neighboring area border routers. All routers
will advertise a range of 10 networks from neighboring areas into the backbone. All configuration
parameters are found in Table 2 in Appendix A.
Figure1. Logical Lab Topology

Lab Procedure
NOTE: This lab continues from Lab 1 where OSPF was configured with scenario
editor, without engaging it resulting in the following Topology.
1. Start by configuring parameters for “Topology1 Ospf” by clicking on the ospf Tab as shown
2. Verify protocol interface by issuing PING command to the DUT interface. Click on Protocol
Interfaces from under Protocol Configuration in the resource tree on left. Right click on
one of your ports in the middle pane and select “Ping” from the drop down menu. Use
either of the default gateway addresses you configured in the wizard. You may need to
retry this until it succeeds. If you see a red exclamation mark “!” in the Port Link Column,
there has been an ARP failure, typically the result of setting a wrong IP address. Rerun the
wizard configuration to correct errors if there are any.
3. You can send Ping by using the buttons at the top of the window on near the middle.

4. Or you can send Ping by right clicking on the ports themselves and selecting Ping from the
dropdown.
5. Next we are going to configure working with the Learned LSA’s. Go back to OSPF button on
the left. In the middle pane, make sure you click on the Routers tab at the top and Router
at the bottom. Scroll to the right and make sure the check box for Discard Learned LSA’s is
unchecked for at least one router. The effect of this will be shown later in this lab.
6. We are going to now configure our statistics so that we can see OSPF aggregated stats. Make
sure that you click on “Select Views” and put a cross-mark next to “OSPF Aggregated
Statistics” and “Ospf Aggregated State Counts” and “Tx-Rx Frame Rate Statistics”.
7. When done, click on “OK” close this window and the changes will be saved.

8. From here, go to “Stat Viewer Options” and find OSPF. Put a checkmark by both the
ports. Don’t forget to also select Tx/Rx Frame Rate Statistics.
9. Configure parameters for “Topology 2 Ospf “ by clicking on the OSPF Tab as shown
10. Now let’s start OSPF and see if it works! Start OSPF with the Start OSPF button at the top of
the window. If you don’t see this button, click on Protocol Configuration in the resource
tree on left. Remember to select “Start All” from the drop down or the protocol will not
start!
11. Now let’s see if it all worked.

12. Select the “OSPF Aggregated State Counts” Tab at the top of the stat window and confirm
that all neighbors have advanced to the “full” state. The pie charts should be slightly
different colors of green.
13. In the other tab you can see the numbers (no graphs). If you cannot see another tab, use the
arrow buttons on the top right hand side of the graph window.
NOTE: View the number of updates advertised. These are total packet counts
per port. If you scroll further to the right, the columns will provide payload
data with total counts of various LSA types in the packets overall.
14. In order to see the learned LSA’s, you need to expand your ports. To do this, click on OSPF
on the left side of window in the resource tree. Right click and use “Expand 2 levels”.
Expand this out until you see the “Learned LSA’s” option under the RID’s on your ports.
You might also click on the arrows to expand the levels. Make sure that the Protocol is
running. Click the “Refresh” button in the ribbon at top. Examine the Link state
advertisements that been advertised by the DUT and distinguish the type 1, 2 and 3 LSA’s.

15. For more information on any LSA that has been learned, double click on the row in the table
and a window will pop up to display the details of update message fields. Note that the
contents are relative to the area the receiving interface is in!
16. Click on “Learned LSAs” on the other port. Is there a pattern that prevents both ports from
generating conflicting router ids and networks?
17. Telnet to the DUT and display the LSDB and the IP routing table to display the impact of the
advertisements. Look for entries created by your emulated routers (the 2nd octet is your
assigned number!).
DUT Output
# sh ip ospf neighbor
# sh ip ospf database
# sh ip route
SAVE your configuration from the File menu as you will need this in future lab exercises!!
<END OF LAB 3a>

Lab 3b: BGP Protocol Configuration

The Border Gateway Protocol version 4 is the standard exterior gateway protocol (EGP) for ISP’s
and large enterprise networks that desire a close interaction with the Internet to control routing
through their domain. This protocol is designed to handle extremely large routing tables, aggregate
routes to reduce routing table lookups and do so with minimal loss of information to select the best
path to destination networks. With network topology changes, it converges at a moderate speed,
faster than RIP, but slower than OSPF. Since changes will have a wide impact across thousands of
routers, a dampening mechanism is used to reduce traffic loss in consideration of instabilities.
It is imperative that with a mixed vendor environment across autonomous systems,
interoperability is ensured, and high volumes of network traffic are handled in consideration of
network layer reachability changes as they propagate through the BGP routing domain.
In an ISP environment, typical BGP routers can be peered with a few dozen other routers. The Ixia
will test the router by simulating a large number of peer connections, generating and advertising a
controlled number of routes and forwarding controlled traffic to determine the effects and behavior
of the router.
Objectives
The student is required to create an AS topology for BGP consisting of three IBGP and three EBGP
peer connections per port as shown in the following diagram. Bidirectional traffic will be sent to
verify the routing table forwarding process.
The AS path and origin will be manipulated to demonstrate how the DUT will receive
and advertise these attributes and influence the DUT’s route selection process.
 Using the Scenario Editor, configure BGP on 2 ports.
01
 Diagnose, evaluate and observe the running protocol statistics and logs. Ago
ura
Roa
d
Cala
bas
as,
CA
913
02
[Toll
Free
US
1.
877.
FOR
.IXIA
)
© IXIA 2013 September BGP Protocol Configuration (Int’
l+
1.81
8.87
Topology
One port on the Ixia emulates three EBGP peer connections while a second port will emulate three
IBGP peer connections. All will advertise a range of 10 networks in a single update message so all
will share common attributes. All configuration parameters are found in Table 1 in Appendix A.
Figure 2. Logical Lab Topology
Figure 3. Physical Lab Topology

Lab Procedure
NOTE: Allocate your ports. You may selectively allocate a subset of ports for your
own testing purposes on the DUT. You may not allocate ports that have been
assigned to other testers. Your ownership is fully authenticated to your own
computer and login. Owner ship will be maintained until you explicitly relinquish
the ports or terminate IxNetwork.
1. Continue with the port assignment from Lab 1.
Note: Configuring BGP on the ports. For convenience and speed, it is highly
recommended that you use the Scenario Editor along with the Interface and
Traffic option in the Classic Mode for the initial configuration of the ports. You
may then proceed to make additional changes or additions with a high confidence
that there will be minimal chance of failure to provide a com plete or correct
configuration.
2. Make sure you are on the Home menu, and click on “Scenario”
Following screen will appear with the existing topology of Ospf. We can add an additional
protocol in the existing topology for BGP. Keep the cursor over “Device Group 2” and click
on “Add Protocol” to create a New Topology for iBGP on the first Port and EBGP on the
second port as shown –
© IXIA 2013 September BGP Protocol Configuration

3. Following Screen will appear. Select BGP by putting a cross-mark next to the checkbox as
shown. Click on “OK”.
4. One more Protocol should get added with BGP protocol for the iBGP Configuration under
“Topology 1” as shown -
5. Repeat the same step for “Topology 2” as shown and further click on ok. One more Protocol
should get added with BGP protocol for the EBGP Configuration under “Topology 2” as
shown -
6. Notice that the ospf protocol is not active and is in gray color and the BGP Protocol tab on
topology 1 and topology 2 is also gray in color. This indicates that the protocol is not
running.
7. Now, let us start by configuring the BGP Protocols under Topology1 and Topology 2 by
clicking on the left side of the screen under the resource tree as shown directly on the Grid –

8. Make sure that you are on the “Ports” tab and observe the field of “Number of “IPv4
Peers.”
9. Change the “Number of IPv4 Peers” for Port1 and Port 2 to “3” each as shown –
10. Also change the Tester AS# for IBGP from default value of 1 to 65001 for both the Ports.
(Before)
(After)
11. Click further on the “IPv4 Peers” Tab and observe the default values under Port1 and Port
2 for the following –
a) Port1 Enable and Port 2 Enable checkmark
b) Type Field
c) Interfaces Field
Refer the following image -
12. Change the Default Field to the following by

a) Assigning Interfaces to the unassigned interfaces as shown for all the 6 interfaces –

13. Change the BGP “Type” after this –
Before After
14. Now put a checkmark next to the “Enable Checkbox” as shown –
Before After
15. Keep the tab on IPv4 Tab and further under the Neighbor Sub-Tab and observe the default
values under the “DUT IP” Field as “0.0.0.0”. This field will be changed as per the IP
assigned to you based on your user Number as shown –
Before After
16. Continue to keep the cursor on IPv4 Tab and further under the Neighbor Sub Tab, scroll to
the right and observe the field of “Number of Route Ranges” as shown. Change the value to
“1” for each interface.
Before After
17. Keep the Tab on IPv4 but further click the sub-tab for “Advanced” and observe the default
values for “Local AS #”
a) Enable the “Enable 4 Byte As#” for Port 1 and Port 2 by putting checkmarks as shown -
18. Now change the default values for “Local AS#” to number as per the User Number assigned
to you by your instructor and put the checkmark next to “Enable 4 Byte AS#” as shown-

19. Further operation on the grid continues with the cursor on “IPv4 Peers” tab and “Learned
Routes Filters” Sub-Tab. Observe that the “Filter IPv4 Unicast” tab and the “Fetch the
Detailed IPv4 Unicast Info” sub-tab without the Checkmarks. This condition does not
allow routes to be learnt on the Ixia Protocol Interfaces. Therefore put the checkmark next
all the tabs to see all the attributes related to the Learned Routes, next to each route.
 Before
 After
20. In the “IPv4 Tab” look for the “Route Range” Tab on the Tabs placed on the top of the Tab
Window and observe the default values as shown –
 Before
 After(Route ranges assigned for User 1)
21. Make sure that you are able to view 3 Internal Peers and 3 External Peers under Port1 and
Port 2 a shown below. Also observe the “Learned Routes” field that will pick up advertised
routes on the respective protocol Interface as shown from other peers.
22. Create Statistics for BGP by clicking on the “Select Views” button as shown. Put a cross
mark on the box next to BGP and Click ok.

 Before
 After
23. Further click on “Stat Viewer” to enable graphical view
24. Start the protocol by clicking on the BGP Tab and further right clicking on the field
indicating “Start Protocols”
25. Confirm the state of “Established” on both the Ports as shown (Troubleshoot if the state of
Established is not reached).

26. Also Observe the Scenario Editor Screen with both IBGP and EBGP in Green Color and the
OSPF in Gray Color.
27. Click on learned Routes for the IBGP Peer and the EBGP Peer and click on the “Refresh” Tab
on top as shown.
28. Observe the Learned Routes for IBGP Peers and for the EBGP Peer as shown.
iBGP Learned Routes for one Peer
EBGP Learned Routes for one Peer

29. DUT Outputs – External Routes and Internal Routes.
<END OF LAB 3b>

Basic Traffic Wizard
Overview
After protocols are configured and running correctly, the basic traffic wizard can be used to take the
protocol information and quickly create traffic streams for testing data plane traffic. This module
will review the implementation of the basic traffic wizard to quickly create flow groups using
protocol configuration parameters.
© IXIA 2013 September Basic Traffic Wizard












Lab 4: Basic Traffic Wizard

The primary objective of testing is generating and measuring data plane traffic. With routing
protocols configured and running, the basic traffic wizard provides a quick and easy mechanism to
configure IxNetwork to generate traffic through the DUT appearing to originate and terminate
directly from the port interfaces or from the networks advertised by the routing protocols. The
traffic wizards will provide extensive control over the packet format from size and content to
bandwidth utilization including controlled bursting and packet count. The wizards will also allow
you to configure and measure traffic and drill down through those measurements from traffic item
to endpoint sets to flow groups to flows.
The basic traffic wizard is a subset of operations from the advanced traffic wizard which we will
cover in the next lab. Once a traffic item is created with the basic traffic wizard, subsequent
changes can be made to it but only through the advanced traffic wizard which will be invoked
explicitly when you attempt to edit a traffic item. Each traffic item, regardless when created from
the basic or advanced wizard will show up under the All Traffic Groups icon on the right side of the
screen.
Objectives
Using the protocol configuration from the previous lab exercise, we will run through the basic
traffic wizard to create flow groups and demonstrate the collection of statistics through the various
tables available.
The route metrics or attributes will be manipulated to demonstrate6 how the DUT will
6 selection process.
receive and advertise these attributes and influence the DUT’s route
0 01
 Create endpoint sets for bidirectional traffic pairs. 1 Ago
 Diagnose, evaluate and observe the running protocol statistics and logs. ura
Roa
d
Cala
bas
as,
CA
913
02
[Toll
Free
US
1.
877.
FOR
.IXIA
)
(Int’
l+
1.81
8.87
Topology
Each port on the Ixia will emulate three neighboring routers. While the routing protocol is running,
each router will advertise a single route range of 10 consecutive networks. All configuration

Lab Procedure
NOTE: If you have reset your ports either restore from your saved configuration
or rerun your wizard configurations. The protocol should be running correctly at
this point.
1. We are going to start by adding traffic to our test. At the top of the “Home” menu in the
ribbon, there is an option for this. Click on the bottom half of this button and from the drop-
down select “L2-3 Basic Traffic Wizard”.
2. The first screen is a summary of the remaining screens. You have the option of stepping
through each screen by clicking the Next or Previous button at the bottom of the screen, by
selecting the icon on the left to go directly to the screen of interest, or by concluding the
setup at any time by clicking on the Finish button at the bottom of the screen. If the basic
wizard is not providing all the control you want, you can switch to the advanced traffic
wizard at any time by clicking on the Advanced Wizard button. Click on Next to get started.

3. We will limit the number of flows and flow groups by committing to a one to one mesh for
both routes and route ranges. However, we will attempt to create more end point sets by
not selecting Bi-Directional and manually configure each direction as a separate end point
set. This will allow us to use to wizard to configure different parameters for each direction.
Name the traffic item Lab 4 and Click Next.
4. Stretch the window vertically to reach the top and bottom of the main window. Expand All
Ports and expand each individual port one level to show the protocol and interfaces, also
showing the number of individual choices below that level. Select the protocol on the first
port as the source and the protocol on the second port as the destination. Be sure not to
select the Interfaces. Clicking on a check box selects all choices below that level.

5. Click on the down arrow alongside Endpoint sets to add this combination as an endpoint
set. Then select the second port (just the protocol not the interfaces) as the source and the
first port (just the protocol not the interfaces) as the destination and add this to your
endpoint sets. Confirm that you now have 2 endpoint sets as shown. Click on Next.
Keep in mind that there will always be a default Endpoint Set at the bottom of the list that
you cannot get delete. Just ignore it.
Note: The down arrow will apply endpoint set configu ration changes to the
highlighted endpoint set!! Make sure the last set is selected when adding a
new endpoint set!
6. In the Frame setup screen, leave the default settings. Click on Next.

NOTE: In the flow tracking window, you have a choice of selecting multiple
fields to track on. You will also track on the traffic item along with any other
combination of frame fields or traffic characteristics. Statistical measurements
will be displayed per flow determined by all possible values of the item s selected
and (so far) choices determined by the protocol configuration.
7. Select Source/Destination Value Pair for tracking. This will match up the source IP
address with the destination IP address for statistical measurements. Tracking is also and
always done on the traffic item itself. Click on Next.
8. The final window will provide a summary of all configuration parameters chosen. Examine
it to confirm you have selected all choices correctly. Click on Finish.
9. The traffic item will build and then you will see its configuration in the grid view. You will
see 3 tabs across the top of the right hand window. These three tabs show different types of
information.

10. The Topology tab shows a graphical representation of what you built. If you click on any of
the configured fields on the right hand side, it will bring you back into the Advanced Traffic
Wizard to make changes.
11. Any attempt to edit the traffic item will bring up the Advanced Traffic wizard. This can be
done a few difference ways. One way is to go to the Flow Groups Tab and double click on
the Traffic Item. Another way is to go to the Topology Tab and click on any field on the right
hand side.
12. Now we are going to the Flow Groups Tab. If you click on one of your two flow groups, and
click on the top menu called “Configuration”, on the ribbon you will see a slider bar that you
can use to adjust the rate. If you cannot see the whole bar, there is an arrow on the far right
that you can use to scroll over. From here, change the rate on each flow to 40%.

13. We are finished configuring our traffic. We can now validate our settings prior to applying
them to ensure there are no errors or warnings for all traffic items. At the top of the
window, you can select “Traffic Actions”. Make sure you are in the Configuration menu!
Select the “Validate L2-3 Traffic” option from the drop down.
14. If everything checks out okay, we can apply the traffic to the Ixia ports and start
transmitting. To do this, select the “L2-3 Traffic Play Button“, in the ribbon of the Home
menu. If there is an exclamation point, it means the traffic has not been applied to the port.
This button will apply the traffic to the port and start it. However, there is a drop down at
the lower part of this button which allows you to apply the traffic and start sending in 2
separate steps.
15. Note that you can also start and stop the traffic on individual flows by using the Start/Stop
buttons in each row with your flow groups.
16. If you want to see your statistics, click on the traffic item called “Lab 4” in the left side of the
window. There will be a tab called “Traffic Statistics”. From here you will be able to select
those traffic views you wish to see. Make sure to check “Flow Statistics” if it isn’t already
selected. After you select what you are interested in, those views become tabs you can click
on to see. Remember that what you select from this window, a new Tab will appear in the
Stat View. Keep track of these tabs.

17. Examine Flow Statistics table and ensure there is no packet loss, however, while you are in
the middle of transmitting, there will be some loss while the stats are still being collected.
The tracking values are in columns with highlighted headers. If you click on the column
header, all rows will be sorted in either ascending or descending order on that column.
18. Select Tx-Rx Frame Rate Statistics (make sure it is enabled) tab to display the graph of
traffic for both ports. From here, you should see the graph for Tx-Rx Frame Rate Statistics
at the bottom of the window. Make sure you have your Flow Groups tab open in the top
window. From here, click on either of your flow groups and adjust the transmit rate. Note
the change in the Tx-Rx window at the bottom! You should see the graph dynamically
changing.

19. Stop the traffic by selecting the “Stop TX” button in the Home menu. Keep track of these
menus. In time it will become easier to remember where all the buttons are located.
Analysis
The tables and graphs allow you to start with general traffic statistics aggregated per traffic item
and “drill down” to more detailed measurements per port and per flow and distinguish between the
data plane and control plane traffic. Flows in the Flow Statistics table are distinguished based per
row on the values of the items being tracked.
In the next lab, we will drill down even further. These results will show up in the User Defined
Statistics table and they will be based on specific preferences.
<End of Lab 4>

Advanced Traffic Wizard
Overview
For complete control over the configuration of traffic streams and flow groups, we have the
advanced traffic wizard. The wizard is also called upon to edit traffic items created by the basic
wizard and can be invoked directly from the basic wizard if the need arises.
In this module, we will review the additional features and capabilities of the advanced traffic wizard
to create and measure date plane traffic.
© IXIA 2013 September Advanced Traffic Wizard











Lab 5: Additional Field tracking with the Advanced Traffic

Wizard
Overview
The advanced traffic wizard gives us many options to control various parameters of the data plane
traffic. Only one traffic item is created with each run of the wizard but the item breaks down into
configurable endpoint sets and flow groups. The endpoint sets are individually configurable within
the wizard only. The flow groups are completely manageable on their own.
There are many manageable fields with the advanced wizard and many different ways to manage
those entities. We will follow one path of doing so in this lab exercise but we will also look briefly at
the other ways of performing the same tasks.
Objectives
Using the protocol configuration from the previous lab exercise, we will run through the advanced
traffic wizard to create a new traffic item with flow groups and focus on QOS. The DUT has been
configured to perform traffic policing emulating a typical SLA. All traffic in excess of an established
CIR will have its priority remarked to 0. The expectation would be that some router further
downstream would mark 0 priority packets eligible to be dropped in anticipation of congestion.
TOS values of 2 and 5 only are being policed on the DUT. The CIR per port has been set to
40Mb/sec. Policed traffic in excess of 40Mb/sec will have TOS value remarked to 0.
 Create endpoint sets for unidirectional traffic pairs.
 Enable TOS values of 2 and 5 only for all endpoint sets.
 Enable for ingress and egress tracking on TOS.
 Set the traffic rate to exceed the CIR.
 Examine the traffic statistics and drill down to confirm that traffic policing is working as
configured.
 Determine the effects of traffic policing on varying rates of TOS values.
 Prove that the SLA conditions described above are being enforced.

Topology
Each Ixia port will emulate three neighboring routers. While the routing protocol is running, each
router will advertise a single route range of 10 consecutive networks. All configuration parameters
are found in Table 1 in Appendix A.

Lab Procedure
NOTE: If you have reset your ports, either restore your saved configuration or
rerun your wizard configur ations and restart the protocol. The protocol should
be running correctly at this point before you proceed.
1. You can launch the Advanced Traffic Wizard by clicking on the bottom part of the Add
Traffic button in the Home menu. There will be a drop down that allows you to select each
of the wizards. You can also click on “Traffic” from the left hand side resource tree and
click on “Add L2-3 Traffic Items” from the middle pane.

2. Note on the left side that you will have 8 screens to step through. As before, the first screen
will define the traffic item in terms of the endpoint sets.
3. Set the traffic name to Lab 5. As before, create two endpoint sets consisting of OSPF or BGP
traffic from the first to the second port, and again from the second port to the first port. We
could have done the equivalent by selecting bidirectional traffic but that would create only a
single endpoint set. Click on the green down arrow to add the new endpoint set. Click on
Next when you have both created.
Note: The remaining screens of the wizard are divided in two sections. The
upper section will allow you to apply parameters to any combination of
selected endpoint sets or simply all of them! If the endpoints hav e different
encapsulations, there will be 2 endpoints in a set. Observe carefully the radio
buttons at the top of this section:
4. For the remainder of the wizard configuration screens, parameters will apply to both
endpoint sets. With the All Encapsulations radio button selected, enter in the lower screen
two TOS values, 2<enter>and 5<enter>! You can either type the value in explicitly or
choose from the drop down menu that will appear when the line is selected. Click on Apply
to apply this to both endpoint sets.

5. Click on Next.
6. The “Flow Group Setup” window allows you to create various combinations of various
fields which are individually manageable based on their specific values on ingress. Select
IPv4: Precedence and Rx Port for flow groups. Click on Next.
7. In the Frame Setup window, choose 128 bytes or higher.
8. In the Rate Setup window, keep the line rate at 20%.Click on Next.

9. In the “Flow Tracking” window, select Track Flows by - IPv4: Precedence. Below this,
enable Egress Tracking and in the drop down menu for offset, select IPv4 TOS Precedence
(3 bits). Click on Next.
10. Skip the “Protocol Behaviors” screen and continue to the “View Flow Groups/Packets”
screen.
11. In the “Preview” window, select the button “View Flow Groups/Packets” and you should
see the flow groups (per Rx port × per TOS value= 2×2=4) appear in the upper window.
Select one of the flow groups and you will observe a packet sequence preview in the lower
window. Remember to adjust column width to allow proper viewing! Click on Next.
12. In the final “Validate” window, with the “Current Traffic Item” radio button selected, click
on the “Validate” button on the upper right and determine if there are errors or warnings.

13. With the ports in interleaved mode, it is possible to oversubscribe on a port where the sum
of the bandwidths of all flow groups exceeds 100% on a port. This, for example, would
result in an error. Select All Traffic Items and select Validate again. Note the results
which will likely show warnings! Click on Finish. Note, this will only happen if you have left
Lab 4 traffic item configured and then added the Lab 5 traffic item. If you already deleted
Lab 4, you will NOT see this. If you need to, go and delete the Lab 4 Traffic item from the
test. To do this, go to the L2-3 Traffic Items on left, highlight the Lab 3 Traffic item and right
click. From the drop, select “Delete selected items”.
14. Apply this L2 traffic and start the traffic.
15. Go create a stat view where you can select Data Plane Port Statistics. To do this,
remember that you have to click on the button that either says “Traffic Statistics” “BGP
Statistics” or “OSPF Statistics”. From here, make sure you select “Data Plane Port Statistics”.
This will become a new tab in your stat views.
16. Select Data Plane Port Statistics. Then select your Second port as shown.
17. From here, select the “Drill Down” button from the top of the window. From the Drill
Down menu, select “Ethernet: IPv4 TOS Precedence (3bits) at offset 120” as shown -
18. The drill down statistics will now display in the “User Defined Statistics” table. This is
another tab, and you may need to use the arrows on the right to see the other tabs.

19. To help analyze the metrics in this table, right click anywhere in the statistics side of this
table, and right click. From the Show option, select Show Footer. This will add a bar to the
bottom of the window. Hard to see, but it’s there.
20. Right click in the footer under the column for Rx Rate Mbps and select Sum. Note that the
value here approximates the line rate applied to the port speed. The breakdown of values is
such that the sum of QOS values 2 + 5 equals the CIR configured on the DUT for policing.
The excess is shown to have been remarked by the DUT to 0. No traffic had been
transmitted by the Ixia port with this TOS value. Any traffic appearing on the port with this
value had to be set by the DUT. Feel free to rearrange the columns in the table so the ones
you are most concerned with are on the left or are all together visible.

21. In the right corner of the User Defined Statistics window, click to button to “Undock” this
window. This will cause it to float. In the background, make sure you display all the flow
groups for Lab 5. You may need to move windows around to see both. One could be hidden
behind the other one.
22. Since we are observing egress tracking using the first port, select a flow group for one of the
TOS values with the TX Port as the second port or Rx Port as the first port. Move the rate
slider bar all the way to the right to saturate the line and note the effect of the metrics. The
total should go up to the full line rate but the amount of traffic with TOS values left
unchanged at 2 and 5 will adjust proportionately so the total still adds up to 40Mb and the
excess falls over into TOS value 0. Remember the slider bar will not allow you to
oversubscribe. Readjust the slider bar, varying it for both flow groups, to see how receive
statistics will change in response. Does the priority level in itself have any effect on TOS
remarking?
23. Another important aspect of tracking provides the ability to compare the ingress values
with the egress values to determine whether the conditions for modifying these values by
the DUT are being achieved. Hit the X in the upper right hand corner to close the floating
window and get back to the default statistics window. Select the Traffic Item Statistics Tab.
If you don’t see it, you might have to use the arrows on the far right hand side.

24. Make sure the row with Lab 5 is highlighted, and then click the “Drill Down” button at the
top of the window. Then select “Drill Down per IPv4: Precedence”. Make sure you are in
the “Data” tab.
25. In the “User Defined Statistics” table, you will see an aggregate of all traffic on both ports
per precedence value. You will see this:
26. Go back to “Traffic Item”. Click inside the cell and further right click and choose
“Ingress/Egress Statistics” and further scroll to “Ethernet: IPv4 TOS Precedence (3bits)
at offset 120” as shown –

27. Click on “Lab 5” and select it and further right click to choose “IPv4 Precedence”
28. The newly created table will show the TOS values from ingress to egress.
Let’s customize our view even further. First, highlight one of your cells and right click. From here,
select the “Customize” option from the drop down menu.

29. Select the phrase All Rx Ports (right about in the middle of the customize window). Another
drop down menu will appear with both ports selected. Deselect Port 1 only. Then click on
the OK button to apply this new profile to the screen. (Note: in the screen shot below, Port 1
is on the bottom)
30. Again, adjust column width for best viewing. You can do this by moving the Tx Rate and Rx
Rate to the left. You will now note that the User Defined Statistics displays only one port.
Do the statistical values verify that traffic policing is working?
31. The Ingress/Egress tracking view shown above validates that the Router’s QOS policy is
working as expected. The chart shows that we are transmitting two flows of traffic; the first
flow is marked as TOS value 2 and the second flow is marked as TOS value of 5. However,
on the Egress side of the Router, there are three different TOS settings 0, 2, and 5. The
policy is configured to remark any excess traffic above 40Mbps to TOS 0.
32. Stop the Traffic.
Analysis
We have demonstrated the use of the Advanced Traffic Wizard to set up a traffic item that uses both
ingress and egress tracking in this lab for IP TOS values. With traffic policing configured on the
DUT, we were able to use the Ixia to confirm that this operation is performing exactly as we would
expect. We have also been able to evaluate variations is flows for different rates of TOS values
being policed.
We have shown a real situation where we have been able to confirm that traffic policing via IP TOS
remarking is occurring as configured on the DUT and were further able to determine the impact of
the TOS level itself on throughput, latency, and policing.
We have drilled down from the Data Plane Statistics table. It is also possible to drill down from the
Traffic Item statistics table and the Flow groups.
< END OF LAB 5 >

Quick Flow Groups
Overview
The traffic wizard constrains us to choose endpoints for our traffic streams limited by the protocol
configuration. Host addresses will be assigned as the lowest value (.1) or run sequentially from .1
up. We can overcome these limitations by using a raw frame encapsulation for the endpoints which
will give us more control over the various header fields.
Quick Flow Groups allow us to create the near equivalent to streams with the flexibility of
IxExplorer including additional features such as ARP for IP interfaces and UDF’s (user defined
fields) without the drudgery of manipulating signatures and time stamps. All quick flow groups
constitute the equivalent of a single traffic item. Each flow group is strictly unidirectional. The flow
group is created from a designated transmit port and you add receive ports later. Ingress tracking,
if enabled, is limited to the flow group, i.e., the is only one flow per flow group.
Much like IxExplorer, flow groups, like streams, can be individually customized and duplicated.
Configuration is achieved directly through the parameter tables and through a flow group editor
which includes the packet editor.
© IXIA 2013 September Quick Flow Groups







Lab 6: Raw Traffic using Quick Flow Groups
Objectives
We will use the protocol configuration from the first lab exercise to provide DUT routing
information only. Our creation of flow groups will not use this information but we will rely on the
DUT being able to forward traffic to those advertised networks. This would be the equivalent of
creating raw traffic with the traffic wizard but without the need to for manual ARP resolution. We
will also include egress field tracking.
 Use quick flow groups to create flow groups across our assigned ports.
 Use the packet editor to customize the traffic in each flow group to direct it to a specific
range of hosts.
 Use the packet editor on each flow group to use a range of IP TOS values
Topology
Each port on the Ixia will emulate three neighboring routers. While the routing protocol is running,
each router will advertise a single route range of 10 consecutive networks. All configuration
01
Ago
ura
Roa
d
Cala
bas
Figure 6. Logical Lab Topology as,
CA
913
02
[Toll
Free
US
1.
877.
FOR
.IXIA
)
(Int’
l+
1.81
8.87
Lab Procedure
1. Continue with the protocol configuration from Lab 3a and leave the protocol running. Go
ahead and delete any traffic items you have already created. To do this, go to ”L2-3 Traffic
Items” in the resource tree on the left hand side of the GUI and click on it. From here,
highlight Lab 4 traffic item from middle pane and right click. Select “Delete selected
items” and hit “OK”.
NOTE: If you have reset your ports, either restore your saved configuration or
rerun your wizard configurations and restart the protocol. The protocol must
be running correctly at this point before you proceed.
2. Back in the Home menu, select Add Traffic and use the drop down to select “L2-3 Quick
Flow Group”.

3. Select just your first port. Each port will constitute a flow group based on the number
selected in the upper right. Leave this value as 1. Click on OK.
4. Each flow group is equivalent to a stream and the usual stream parameters can be
configured very much analogous to IxExplorer but with the added benefit of the packet
editor.
NOTE: There are many ways to configure the flow groups themselves. For
now, we will use the table (grid) approach to set as many parameters as the
table will allow. We will then bring up a more detaile d configuration screen to
set up additional items.
5. On the first port, where this is displayed as the Tx port, click in the cell for the Rx Port
(which should indicate None.) Select the down arrow to bring out a window where you will
select the other port. Click on OK.
6. The default is Ethernet II frame format. Select the top cell under Encapsulation; left click
to select the cell then click again on the down arrow to bring up an abbreviated view for the
Stack Diagram of the packet editor. Select IPv4 to append this to the stack.
7. You now have appended an IPv4 header to the frame. You may continue to append
additional headers. Add a UDP header to the frame as well. You can remove this layer by
clicking on the red X alongside the header. A more complex protocol stack can be saved and
reused at a later time by clicking on the floppy icon. We can also set IP and MAC addresses
here but we will defer this as the two ports must have different IP addresses. Click on OK.

8. By adding IP and UDP to the protocol stack, we can customize the title bar to better suit our
needs and continue using the grid to complete our configuration. Place the cursor in the
title bar and right click. Select Column Chooser.
9. You now have the column chooser which is available for all tables. Among the Visible
Columns, select and move (to the left) Preamble Size, CRC, Frame Payload and
Transmission as we are not concerned with these for this exercise. On the left side, expand
L3 and IPv4 and move to the right side IPv4Destination Address, Source Address, and
after expanding IP Priority and TOS, IP4: Precedence. Move these fields up to just after
Flow Group Name. We also want to set the TOS bits but this method will not allow us access
to fields smaller than a byte. Select OK when done.
10. Click under Dest MAC Mode and select ARP from the drop down menu. Make sure to move
your mouse cursor onto another column. Ex. Select the IPv4: Source field.
NOTE: We will forward traffic from and to specific hosts within a single
network among the advertised network ranges. Wederivethese values from
how we know the protocol has been configured. This is almost equivalent to
raw traffic. Many combinations are possible here.
11. Under IP Destination and Source address for the port, select the cell then select the down
arrow. Enter values shown below.X is your assigned user number.
12. Under IP: Precedence, click in the top cell and select from the drop down menu List. Enter
TOS values 2<enter> and 5<enter>. Click on OK.

13. In the 2nd tab across the top called “Quick Flow Group Options” make sure to enable both
Ingress and Egress Tracking (in that order.) For Egress Tracking, set the Offset drop
down menu to IPv4 TOS Precedence (3 bits.)
14. We are done configuring the Quick Flow Groups.

15. Now let’s go apply the traffic and start transmitting. Make sure you are in the Home tab and
first use the drop down under L2-3 Traffic to apply and then go back a 2nd time to start
transmit.
16. And then we can start the L2-3 Traffic.
17. Click on Traffic Item Statistics and note that all traffic for all flow groups created under
Quick Flow groups appears as a single item on one line. The stats are an aggregate for all
flow groups.

18. Deselect all of the statistic views except Data Plane Port Statistics and Flow Statistics.
Arrange these two tables horizontally by selecting the Views tab then selecting the second
arrangement from the left with a single window on top and 2 side by side on the bottom.
Note that they contain nearly the same information. For quick flow groups, you implicitly
create a flow group for each Tx port which thus equates each line in the Data Plane Port
stats.
19. Select the Flow Statistics table again. For the line that again represents the flow of traffic
from port 1 to port 2, right click in that line and in the pop out menu, select Ingress/Egress
Statistics Ethernet :IPv4 TOS Precedence.
20. Deselect the Flow Statistics table so only the User Define Stats table is displayed. This table
is implicitly reduced to display only the non-zero statistics for both ports. This can
significantly reduce the size of the table when egress tracking on a field that may be much
wider than 8 bits. Note also that as you scroll across, the Tx and Rx Port columns remain
visible. Columns can be rearranged by click and dragging them across to the desired
position.
Analysis
Quick Flow Groups allows us to circumvent the formalities of the traffic wizard and quickly create
simple flow groups based on the Tx port. All flow groups created under Quick Flow Groups appear
as a single traffic item as if created all together by the wizard and traffic item statistics displays an
aggregate count of all statistics for all these flow groups.
As before, each flow group has a limited amount of independence from other groups. Traffic can be
individually turned on or off or paused. The bandwidth rate and packet size can be dynamically
modified while traffic is running.
< End of Lab 6 >

Lab 7 – Configuring L3VPN with Scenario Editor
Overview
Lab Objectives
 Configure the L3VPN Protocol in the Classic Mode.
L3 VPN Test Topology with Ixia Port Emulation
© IXIA 2013 September L3 VPN


See Figure 1 for the topology of this test. This topology diagram shows the physical wiring and
Figure 7: Port Management Topology


a. Click on the Scenario Editor Icon and further Click on the “+” Sign next to “New
Topology”.
b. Connect to Chassis and take allocated Ports.
c. Use the Protocol Wizard to create an L3VPN Stack in the Classic Mode for a given topology.
d. Set the stage for running the Protocol.
Procedure
1. Acquire your user number from your instructor before proceeding with this lab. Your number
will determine your PC, chassis ports and IP address assignments as indicated in Appendix A.
first quadrant marked as “Click here to configure Ports” and proceed in the traditional way
to select the chassis and the ports. We will however choose to use the option of Scenario
Editor marked as “Scenario” to the Left in the Resource Tree to select the Chassis and Ports.

Configuration window. This will present a New Screen with a “+”sign next to “New Topology”
button. In order to start the configuration with the help of Scenario Editor click on the “+”sign
next to “New Topology” as shown.
5. Following screen appears that has the option of adding Ports as “Add Ports” under the
heading of “Ixia Ports” as shown.
6. On the top side of the screen labeled “Protocol Wizard”, select the button to Add chassis and
ports by clicking on “ + Add Ports”. Following Screen will appear that will display that has
the following options –
 “+ Add Chassis”
 Recently Used Chassis
If the IP of the Chassis provided by the Instructor is already listed under the “Recently Used
Chassis” option, then click on it to connect.

7. Wait for the chassis connection to be established which should display a green circle with the
IP mentioned next to it. This indicates that the Chassis is up. Also below the Chassis, all the
active ports would be displayed as shown as green indicating the status as up under each card.
At this point you would need to select the ports that have been assigned to you by your
Instructor. If you do not know your ports, kindly ask your Instructor for your user number
along with Card and Ports assigned to you for doing your further Labs.
8. Expand the Card(s) your ports are on, highlight your ports, and select the double arrow button
to add ports by clicking on “Add ports” and push them to the right under “Ports in
Configuration” as shown and further click on “Ok”.
below giving details of Status, Name and Chassis/Card/Port. If you notice that the “Mapped
To” Tab is empty it is because the ports have not been appended and pushed to the right.
10. Select the Ports by highlighting them as shown and further click on “Append Ports” to send
the ports towards “Ports in New Topology” as shown. The Protocol Wizard now shows a
New Icon of “Protocols” that will be configured at some point later. Click on “Next”.

11. At this point Ixia IxNetwork 7.0 introduces the two modes under “Protocols” Tab to select the
protocol type to be configured –
counts.
create a compact protocol configuration for the NextGen protocols that efficiently scales to
very large port and protocol session counts.
legacy way.
Improve Usability
The NextGen Architecture improves usability in the following ways:
easy to understand.
with the test.
The NextGen Architecture improves functionality and inter-networking in the following

ways:
Improve Scalability
The NextGen Architecture improves scalability in the following ways:
system.
12. For this configuration we will be using the Classic Mode to configure Ospf. Select the “Classic
Mode” and further select “L3 VPN/6VPE ” as shown –

13. Further select “New Wizard Run” and click on “Run Wizard” a shown below
14. The following screen appears where the checkmarks need to be appropriately put for the first
port emulating the “Provider Side” (PE-P-PE) and the second port emulating the “Customer
side” (PE – CE). As shown in the image below.
The Wizard will take you through a step by step process of configuring L3 VPN/6VPE by:
a) First Selecting Port/Ports
b) Selecting Number of Routers that you would like to emulate on each port.
c) Providing IP address of the emulated Routers and the Gateway Address
d) Choosing the Incrementing Factor (Per Port/Per Router)
e) Advertising Routes on these Emulated Routers.
f) Saving the above configuration with a Name.
Before:
After:

15. Make your selection by choosing the first port emulating the Provider Side by putting a
checkmark under the Provider Side as shown above.
16. Also make your selection by choosing the second port emulating the Customer Side by putting
a checkmark under the Customer Side as shown above.
17. After making both the selections in the same screen, click on “Next” and the following screen
appears as default screen.
18. At this point the instructor will guide you on how to navigate through the Screens with the
help of the “IP Assignment Sheet” provided to you, in the Appendix of the Lab Manual, based
on your User Number. Below please find the snapshot of IP Assignment Sheet for “User1”.
19. With the help of the “IP Assignment Sheet” enter the details as shown (User 1) –
20. Click Next to move to the Screen # 3 of 7.

21. With the help of the “IP Assignment Sheet” enter the details as shown (User 1)

23. Click on “Next” to move to Screen # 5 of 7.Following screen appears with the default
Parameters and IPs. Change this based on your User ID. The config shown here is for User 1.

25. Click on “Next” to move to Screen # 6 of 7.

26. The next screen shown will be Screen # 6 of 6 as we are not currently configuring the 6VPE –
IPv6 Protocol. Give a suitable name to your configuration and click on the “Finish Tab” to
conclude the configuration using the Scenario Editor Classic Mode Wizard.
27. Further Click on Scenario to confirm the topology as per your configuration (both on the
Resource Tree and in the Scenario Editor.
28. At this point you can see that the Interfaces are all in green color and the Protocols are in gray.
This indicates that the Interfaces are up and the protocols are not running. Before we start
running the protocols there are a couple of items that need to be fine-tuned. First we need to
create a Statistical view for all 3 protocols. (OSPF, BGP and LDP).
29. This has two steps to it as seen below. First Step is to click on “Select Views” and put a cross
mark next to each protocol as shown and further click on “Ok” as shown –
First Step:
30. Second Step is to click on Stat Viewer that is seen on the Ribbon on the top of the Screen -
Second Step:

31. Following Screen will appear and you need to put a check mark across the protocols (OSPF,
BGP and LDP) as shown below – and further click on “Close”.
Ospf Aggregated State Counts
BGP Aggregated State Counts
LDP Aggregated State Counts

32. Each of the protocol interfaces gives you an option for opening a Trace Window where
Debugging is possible for that protocol. In case of BGP it also gives you an additional option to
trouble-shoot states as “Open BGP Statistic” a shown below –
33. At this stage we are ready to start the protocol but there are few key parameters that need to
be further considered before starting the protocols.

34. First the “Discard Learned LSA” checkmarks from the Ospf Routers Sub Tab must be removed
as shown below
35. To do this click on the “OSPF” Tab in the “Resource Tree” and further click on “Routers” Sub-
Tab and remove the checkmarks from “Discard Learned LSAs”.
Before -
After –
36. Second the “Ospf Interface Type” should be made “point-to-point” as shown below -
To do this click on the “OSPF” Tab in the “Resource Tree” and further click on “Interfaces”
Sub-Tab and change the Network Type from “Broadcast” to “Point-Point”.
Before –
After –

37. Expand each one of the protocols Tab in the Resource Tree and explore the sub-tabs –
a) BGP Protocol Tab
b) LDP Protocol Tab
c) Ospf Protocol Tab

38. At this point the protocols are not running. There are different ways of starting the protocols.
39. First is starting the protocols in Global mode where all protocols start at the same time as
shown-
40. Second is at the individual Protocol Level –
41. Thirdly at the Protocol Level at the in the Ribbon on top of the screen –

42. We will now start the Protocol in a steps starting with OSPF first –
43. You will notice that the Ospf session on Port1 and Port2 have reached a state of “Full”.
44. Now start LDP –
45. You will notice that the LDP Basic Session has come up.
46. Now let us start iBGP Session –
47. You will notice that the BGP Session is also up.

Verify DUT Outputs

Command -
Output -
Command and Output -

Command and Output –
< End of DUT Output>

48. In order to see the “Learned VPN Routes” Click on the BGP Tab, Expand it until you see the
“Learned VPN Routes” and further refresh the screen clicking on the “Refresh” button seen on
the Ribbon on the top of the screen.
49. Verify that there are 20 VPN Routes on the screen as shown.
Traffic Generation
50. In order to send/receive traffic the first step involves in choosing the right option for the
traffic wizard. Click on Add Traffic as shown, use the pull down and select L2-3 Advanced
Traffic Wizard a shown below-
51. Following Screen appears (As Default) –

52. Below find the screen view after making changes to “Traffic Name” and changing the “Source
“to “L3VPN” and also expand the respective source and destination endpoints from where
you want to send and receive traffic.
53. Screen view after making changes by putting the relevant checkmarks (2).
54. Following Endpoint Set appears –
55. Click on “Next” to move to the next tab that is “Packet/Qos”. As in this Lab exercise we are
not adding any precedence/ ToS mark on the packet, we can skip this screen and click on
“Next “.
56. Following Screen appears where you define your Flow Group –

57. We will define our Flow Group based on the Rx Port, MPLS Label Value (1) so that we can drill
down on the same fields later once the Traffic Item is generated and transmission begins as
shown below –
58. Click on “Next” and change the Frame size to Fixed 128 bytes to accommodate additional
headers as shown below-
59. Click on “Next” to move to the next screen configuration, where you can specify the Rate at
which you would like to send the Traffic across the configured “Traffic Item”. Keep the “Line
Rate” as 50% as shown –
60. Click on “Next” to move to the next screen configuration, where you can specify the
parameters for Tracking as “Source/Dest Value Pair” and “MPLS: Label Value 1”.

61. Click on “Next” and Skip the “Protocol Behavior” Tab.
62. Further click on “Next” to take a Preview of your “Configuration” done so far.
63. Following Screen will appear to give you a preview of the configuration done so far with
details of Flow Groups/Packets.
64. The Last Step in the Traffic Configuration includes “Validating” the Traffic Item before it gets
created. This is done to confirm the Configuration, Packets, Flow Groups and Flows.

65. Click on Next to move to “Validation” as shown below and further click on “Validate”.
66. Now you can conclude the creation of Traffic Item by clicking on “Finish”.
67. Following Flow Group for the Traffic Item gets created –
68. Now we can start the traffic by clicking on the “Play button “as shown –
69. In order to see if there are any Loss in the Traffic, Toggle over to “Traffic Item Statistics” as
shown below –
70. Ideally there should be no loss or the Loss% across all flow groups should be Zero.

71. At this point we can drill down from the “Traffic Item” based on the 2 tracking criteria that
was defined earlier as –
a) Source/Dest Value Pair
b) MPLS: Label Value 1
Output for Drill Down based on Source/Dest Value Pair (User1) –

Output for Drill Down based on MPLS: Label Value (1)
< END of LAB 7>

Lab 8 – Configuring IPv6 with Ospf v3
Overview
protocol and traffic configuration. We will click on the quadrant that says add ports and connect to
chassis and take ports.
In this lab we will add the ports and further choose ospf v3 as the protocol to configure using IPv6.
Lab Objectives
 Create an IPv6 based topology and run Ospf over it.
 Fine tune the configuration.
 Run L2/L3 traffic over IPv6 endpoints.
Ospf v3 Test Topology with Ixia Port Emulation
© IXIA 2013 September IPv6 with Ospf v3


1. Click on the Scenario Editor Icon and further Click on the “+” Sign next to “New
Topology”.
2. Connect to Chassis and take allocated Ports.
3. Assign IPv6 Address to the Ports as per the ipv6 assignment sheet attached.
4. Advertise 10 Routes on each endpoint as per the ipv6 assignment sheet attached.
5. Run the Ospfv3 Protocol, verify and run traffic between the IPv6 endpoints.
Procedure
quadrants with selection on “Overview” as shown. We do have the option of Clicking on the first
quadrant marked as “Click here to configure Ports” and proceed in the traditional way to select
the chassis and the ports. We will however choose to use the option of Scenario Editor marked
as “Scenario” to the Left in the Resource Tree to select the Chassis and Ports.
5. Following screen appears that has the option of adding Ports as “Add Ports” under the heading
of “Ixia Ports” as shown.
ports by clicking on “ + Add Ports”. Following Screen will appear that will display that has the
following options –
c) “+ Add Chassis”
d) Recently Used Chassis

7. If the IP of the Chassis is not listed under the “Recently Used Chassis” then add the IP of the
8. Wait for the chassis connection to be established which should display a green circle with the IP
mentioned next to it. This indicates that the Chassis is up. Also below the Chassis, all the active
ports would be displayed as shown as green indicating the status as up under each card. At this
point you would need to select the ports that have been assigned to you by your Instructor. If
you do not know your ports, kindly ask your Instructor for your user number along with Card
and Ports assigned to you for doing your further Labs.
below giving details of Status, Name and Chassis/Card/Port. If you notice that the “Mapped To”
Tab is empty it is because the ports have not been appended and pushed to the right.

11. Select the Ports by highlighting them as shown and further click on “Append Ports” to send the
ports towards “Ports in New Topology” as shown. The Protocol Wizard now shows a New Icon
of “Protocols” that will be configured at some point later. Click on “Next”
12. A window will appear where the Ospf v3 needs to be configured. Select the “Classic” option as
shown and further select Ospf v3.

13. Further select “New Wizard Run” and click on “Run Wizard” a shown below –
port and the second port (one at a time as best practice) as shown in the next screenshot and
click on “Next”
Before:
After:

15. Following screen appears that needs to be filled with ipv6 Tester address as shown. Also for
this Lab you can need to keep the “Number of Emulated Routers Per Port” as 1. Note that the
“Gateway IP Address” is grayed out and needs to be filled later directly on the grid.
Before -
After -
16. Click on Next and put a checkmark next to Advertise and publish 10 routes as per the IP table
given to you including the Route Origin for ospfv3 as routes coming from another area.
17. Save the configuration using the option as shown below, with a relevant name –
18. And further click on “Finish” as shown –

19. This process completes the configuration of ospf v3 on Port 1 and can be confirmed by clicking
on the “Scenario” option as shown –
20. The “Interfaces” Tab is red in color as the appropriate gateway address has not been provided
so far. The Ospfv3 is greyed out as the protocol is yet to be started. Before we start to tweak the
above tabs we also configure the second port for an ospfv3 configuration.
21. Click on the “+ New Topology” and start the configuration on Port 2 as shown below -
22. Select the second port that has been assigned to you as per the IPv6 sheet and click on “Append
Ports” as shown below -
23. The second port should get appended to the New Topology as shown. Click on “Next”-
24. Following screen appears and this time again the Classic option is chosen along with OSPFv3.

25. Click on “Next” and run the wizard once again for Port 2 as shown -
26. Select your second port by putting a check-mark next to port 2 as shown –
Before -
After –
27. Click on “Next “and the following screen appears that needs to be filled with ipv6 Tester
address as shown. Also for this Lab you can need to keep the “Number of Emulated Routers
Per Port” as 1. Note that the “Gateway IP Address” is grayed out and needs to be filled later
directly on the grid.

28. Click on Next and put a checkmark next to Advertise and publish 10 routes as per the IP table
given to you including the Route Origin for ospfv3 as routes coming from another area and
further click on “Next”
29. Save the configuration using the option as shown below, with a relevant name –
30. And further click on “Finish” as shown –
31. This process completes the configuration of ospf v3 on Port 2 and can be confirmed by clicking
on the “Scenario” option as shown –
32. The “Interfaces” Tab is red in color as the appropriate gateway address has not been provided
so far. The Ospfv3 is greyed out as the protocol is yet to be started.
33. The appropriate gateway address needs to be provided to the ports as per the IP Table
provided to you by the instructor for both port 1 and port 2 as shown below –
34. The modifications for the IPv6 Gateway address will be done directly on the Grid as shown
below –
35. Click on the Tab indicating “Protocol Interfaces” and

36. The following screen will appear –
37. The exclamation mark next to the protocol interface indicates that there is an ARP failure. This
is obvious as the gateway address have so for not been provided in our configuration. Provide
the correct IPv6 Gateway address and further uncheck and check the “Enable” Tab for both the
Interfaces as shown –
Before
After
38. Now “Uncheck” and “Check” the Enable tab for a successful ARP resolution on your first port as
shown below –

39. If the gateway IP has been provided correctly then the exclamation mark should not be appear
after putting the check-mark back on the “Enable Tab” of Port 1. Repeat the same exercise for
Port 2.
40. The protocol will however be in grey as we have yet to start it.
Note: Important steps to do before starting the protocol –
a) The statistical view (Grid and Graphic) for Ospfv3 should be prepared – Refer to earlier
configurations.
b) Trace can be enabled on both interfaces (optionally). Refer to earlier configurations.
c) Change Ospfv3 Network Type from the Broadcast mode to point-to-point from the
“Interfaces Tab”. Refer to earlier configurations.
d) Remove the checkmarks from “Discard Learned LSAs” under the “Routers” Tab.
e) Verify the Learned LSA Tab as shown –
41. Click OSPFv3 tab and expand it to view the available options.
42. Also Note that the protocol is not running hence the “Refresh” tab is grayed out as shown –

43. Now we can start the protocol by clicking on the OSPF v3 tab and further clicking on “Start
Protocols” as shown –
44. Following Results should be seen in the Grid Mode –
45. Following Results should be seen in the Graphical Mode –

46. Verify the Learned LSAs by clicking on the “Learned LSAs” tab and further click on “Refresh”
for both the ports –
Port 1 -
Port - 2

Verify DUT Outputs

Traffic Configuration
47. The Traffic Configuration begins by selecting the “Traffic” Tab as shown –
48. Further select the “L2-3 Basic Traffic Wizard” by using the Drop-Down from the Add “L2-3
Traffic”

49. And click on it. This will start the Wizard for Traffic Configuration over the IPv6 Interfaces.
50. The Topology Parameters will be as follows:

 Name: User_1_IPv6_Traffic
 Type: IPv6
 Source/Dest: One-One
 Routes/Hosts: One-One

51. Select the Source and Destination traffic endpoints as shown below by choosing OSPFv3 Route
Ranges.
52. Expand to see your selection of endpoints –

53. After making the right selection click on the green drop down arrow to apply and update the
selected endpoints as shown below-
54. The endpoint configuration will look like this with 1 Source Endpoint to 1 Destination Endpoint.
Click on “Next”.

55. In the Frame Setup Tab choose the “Target Frame Size” as 256 and “and– “Line Rate” at 50%
and click on “Next”-
56. We can do flow tracking based on “Source/Destination Value Pair”. Click on “Next”.
57. The summary of your configuration should be seen. Click on finish to close the Configuration. At
this point the traffic item should be ready to be deployed as shown below -
58. The traffic item should be visible under the “Traffic Tab” in the Resource Tree.

59. Start the traffic making sure that the Control Plane that is OSPFv6 is up and running as shown
by clicking on the green color play button on the top of the screen in the ribbon.
60. We had done a tracking based on “Source/Destination value Pair” and now that can be
verified using a “Drill Down Option” by right clicking on “Traffic Item Statistics” as shown –
61. The Result is as shown –
<End of Lab 8 >

Lab 9 – Configuring Multicast with Scenario Editor
Overview
Lab Objectives
 Configure the Multicast in the Classic Mode.
Multicast Topology with Ixia Port Emulation
© IXIA 2013 September Multicast


Topology”.
3. Select the “Receiver Side” and the “Source Side” as per the instruction provided. (First Port
will be the “Receiver Side” and the Second Port will be the “Source Side”).
4. Assign IPs as per the IP Parameter Sheet Provided in the Appendix and Configure Multicast.
5. Configure Traffic and verify Multicast Traffic between the Source and Destination.
Procedure
first quadrant marked as “Click here to configure Ports” and proceed in the traditional way to
select the chassis and the ports. We will however choose to use the option of Scenario Editor
marked as “Scenario” to the Left in the Resource Tree to select the Chassis and Ports.

e) “+ Add Chassis”
f) Recently Used Chassis

ports towards “Ports in New Topology” as shown.
11. The Protocol Wizard now shows a New Icon of “Protocols” that will be configured at some
point later. Click on “Next” and for this configuration we will be using the Classic Mode to
configure Multicast. Select the “Classic Mode” and further select “Multicast” as shown –

port and the second port (both at the same time as best practice for Multicast) as shown in the
next screenshot. Select the “Receiver Side” and the “Source Side” as per the instruction
provided. (First Port will be the “Receiver Side” and the Second Port will be the “Source Side”)
and click on “Next”
Before -
After-
13. Following screen appears that is the default screen and need to be changed with IP address
provided as per the User No. (The below Table shows the values that user1 has to enter).
IP Address Sheet for Receivers Side (User 1)
Tester IP Address 192.168.8.2/24

DUT IP Address 192.168.8.1/24
Multicast Protocol IGMPv2
RP Address 21.20.20.2
Number of Emulated Users per Port 10
Starting Group Address 225.12.12.1/32
Group Address Count per Receiver 0.0.0.0
Before -

After –
14. Click on “Next” after entering the values as shown above for the respective User No. assigned to
you by the Instructor as per the IP Parameter sheet.
IP Address Sheet for Source Side (User 1)

Tester IP Address 192.168.9.2/24
DUT IP Address 192.168.9.1/24
IGP Protocol OSPF
Multicast Protocol PIM-SMv4
Number of Emulated PIM
Routers Per Port 1
Source Address Distribution Continuous Increment
Starting Source Address 23.20.20.2/32
Source Count per Router 1
Before:

After:
15. Save your configuration with a relevant name by choosing the option of “Generate and
Overwrite Existing Configuration”
16. Following Screen appears in the “Scenario Editor” with the Interfaces tab on both Port 1 and
Port 2 in Green Color. The other tabs (IGMP, PIM-SM and OSPF) are in grey because the protocol
is not started.
17. Click on Protocol Interfaces and verify the 10 Receivers on Port 1 and one Sender on Port 2.
18. Expand the IGMP Tab in the Resource Tree to the right of the screen and verify 10 Hosts on Port

19. Expand the Ospf Tab and further fine tune the protocol for functionality as per the topology by
removing the “Discard Learnt LSA’s” from the “Routers” Tab as shown -
20. Expand the PIM-SM/SSM-v4/v6 and verify the PIM-SM Interface IP on Port 2.
21. Also ensure that the Statistical view for Multicast are enabled by clicking on the “Select Views”
tab as shown below -
22. The DUT Configuration before running the protocols indicates no multicast activity on port 1
and port 2 –
23. Start all the protocols by clicking on the play button on the top of the ribbon as shown –

24. DUT Configurations after the Protocols are started indicate multicast activity on port 1 and port
Multicast Traffic
We can send traffic over the configured topology from Port 2 that is the Source towards Port 1 that
is the destination. The traffic will be sent from Port 2 configured and enabled with PIMSM towards
Port 1 that is configured and enabled to join the group and receive multicast traffic from Port 2. The
10 IGMP hosts configured on Port 1 will be receiving the traffic from Port 2. The first step in
configuring is to use the traffic wizard to configure endpoint and later send traffic.
For this Lab we will be using the “Advanced Traffic Wizard” to receive Multicast Traffic.
25. Click on “Traffic” and further select the “Advanced Traffic Wizard” as shown below –

Following Traffic Wizard opens up –
26. Enter the details for the following fields –

 Traffic Name – Mult_Traffic_U_1
 Type of Traffic – IPv4
 Traffic Mesh (Routes/Hosts) – Fully Meshed
27. Also choose the Source as an Interface 2 where PIM has been enabled by putting checkmarks–
28. And choose the Destination as the 10 IGMP hosts on interface 1 by putting checkmarks -

29. After selecting endpoints accurately click on the green apply button as shown to update the
selected end-points sets as shown-
Before -
After -
30. Now click on “Next” and skip the following options -

 Packet/Qos
 Flow Group
 Frame Setup
 Rate Setup (Optional)
31. At “Flow Tracking” enable tracking based on
32. Click on Preview – and further click on view flow group/packets -
33. Following Screen will appear showing the default flow group created –

34. Click on “Next “and following careen appears where the traffic item validation needs to be done
-
35. Click on validate and troubleshoot if you get any warnings or errors -
36. On successful validation click on “Finish” and the traffic item should be ready.
37. Following Traffic Item should get created without warning /errors –
38. Before starting the Traffic enable capture by clicking on the funnel as shown on the control
plane of Port 1 so that the IGMP hosts can be seen to form v2 join membership with the
multicast group address (User 1).
39. Now start the traffic by clicking on the play button for traffic and making sure that protocols are
running.

40. Click on the Capture Button as shown –
41. Start the Capture as shown by clicking on the Capture play button and further click on the
Packets in the Hosts tab –
42. The Ladder Diagram indicates traffic from source to the multicast group, where the IGMP
endpoint connects to the multicast group generating a V2 Membership Report.

DUT Configurations –
<End of Lab 9>

Lab 10a – Test Composer Pre-Lab
Overview
The first step in using IxNetwork is to allocate ports, for subsequent Ospf and Test Composer
configuration. We will click on the quadrant that says add ports and connect to chassis and take
ports.
In this lab we will add the ports and further choose the Automation tab to configure a script using
the IxNetwork tool called as Test Composer.
Lab Objectives
 Create an IPv4 based topology and run Ospf v2 over it. (Lab 3a)
 Fine tune the configuration.
 Run the “Test Composer Script” for Flapping the Ixia Ports. (Lab 5b)
Test Composer Topology with Ixia Port Emulation
© IXIA 2013 September Test Composer Pre-Lab



Topology”.
3. Use the Protocol Wizard to configure OSPFv2 Stack in the Classic Mode for a given topology.
4. Set the stage for running the Protocol.
Procedure

g) “+ Add Chassis”
h) Recently Used Chassis

Expand the Card(s) your ports are on, highlight your ports, and select the double arrow button
counts.
create a compact protocol configuration for the NextGen protocols that efficiently scales to very
large port and protocol session counts.


legacy way.
Improve Usability
easy to understand.
with the test.
The NextGen Architecture improves functionality and inter-networking in the following ways:
Improve Scalability
The NextGen Architecture improves scalability in the following ways:
system.
Mode” and further select “Ospf” as shown –
Ixia IxNetwork 7.0 has an option of configuring Ospf with Next Gen and can be used as an option
when the customer requirements include improved usability, improved functionality and
improved scalability. In our configuration we will configure Ospf in the Classic Mode.
12. Select “Ospf” and further select “New Wizard Run” and click on “Run Wizard” a shown below

14. Enter the IP address (Tester IP Address), Gateway Address (Gateway IP Address) and mainly
add the “Number of Emulated Routers per Port” as per the scenario/topology/User No.
provided by the Instructor and click on “Next”.

the end of the Lab Manual a shown. Please make sure to change “Increment By”(Per
Users.
15. Screen Number # 4 of 6 includes Network Range –

The optional ospf Wizard-Network Range dialog allows the user to create a matrix/grid of Ixia-
emulated Ospf (v2) networks. The size of this network range matrix is determined by the
number of rows and columns configured. For example, a network range with 10 rows and 10
columns will contain 10 times 10 Ixia-emulated routers, connected horizontally and vertically
by Ospf Network Range links (subnets). We can skip the 4 # 6 screen number as we are not
going to create subnets behind the emulated Routers in this Lab Exercise.
16. The OSPFv2 Advanced Interface Settings-Network Range TE dialog box allows you to configure
Traffic Engineering parameters for links to virtual Ospf topologies created with the Ospf
Network Range feature. We can also skip the 5 # 6 screen numbers as we are not going to
configure traffic engineering parameters in this Lab Exercise.
17. On Screen number 6# of 6 select the Radio button that says “Generate and Overwrite Existing
Configuration”, give a relevant name “Ospf_Port_1” and further click on “Finish” to complete
the configuration for Port1.
18. Following screen appears indicating the use of the Scenario Editor to configure properties on
the 1st Port. The screen shows the “Ospf” and Interface as a Stack and as a Part of a Device
Group identified with a name as “Device Group 2” in this case under “Topology 1”.
Note:
The Ospf tab is in Gray and the Interfaces tab is in Green. This is mandatory and it indicates
that your configuration on the 3 Protocol Interfaces on Port 1 is correct and also indicates that
the Opsf Protocol is yet to be started.

Elements of a Scenario
Scenario presents all the protocols in a single tree with a consistent look and feel across all
protocols. It enables you to create a scalable compact configuration using the following:
Topology – An arrangement of the network elements used for configuring large scale, complex
routing/bridging network simulations. It is a collection of test ports and can contain multiple
Device Groups.
Device– A simulated network element, which can be a router, host, switch, and so on. A Device
can run multiple protocols and protocol stacks. Thus, when we configure a Device, we add or
remove protocols that we want to simulate.
Device Group – A group of n similar Devices per test port. Device Groups model devices that
run protocols and interact with the DUT. A Device Group count is the number of instances in the
group. A configuration can be scaled by modelling a group of n Devices per test port by
changing the multiplier.
Port Group – A set of similar ports, which share the same device group configuration. All ports
in a Port Group must have the same interface type. A Port Group may contain many Device
Groups. A Port may belong to one Port Group and a Device Group may belong to only one Port
Group. Device Groups are connected to a Port Group and the configuration replicated on each
port in the group.
Connectors – Connects the Device Groups to ports and other Device Groups. When Devices are
connected, the Group size is the product of the Device Group size property and the Group size of
the upstream device.
Multiplier – Increases the count of Devices in a Device Group.
Network Group – A Network Group represents a set of L3 networks (sub-netted or switched)

with optional information explaining the reachability to each of these networks. All Devices
connected to a Network Group must belong to one of the networks modelled by that Network
Group.
Protocol – A Protocol represents a set of protocol emulation sessions running in the context of a
Device Group.
19. In order to create a configuration on Port 2 click on the “+ New Topology” as shown –
20. Following screen appears, with Port 1 Mapped To Topology 1. Next we will attempt to Map
Port 2 with Topology 2.
21. In order to configure Port 2, select your Port 2 and further click on “Append Ports” as shown
and click on “Next”
22. There are two modes under “Protocols” Tab to select the protocol type to be configured –
a) Classic Mode
b) Next Gen Mode

23. For this configuration we will be again using the Classic Mode to configure Ospf. Select the
“Classic Mode” and further select “Ospf” as shown for Port 2 as well.
24. Select OSPF once again and note that there is already a configuration for Port 1 and the
selection by default is on “New Wizard Run”. Click on “Run Wizard” to start the configuration
for Port 2.
25. Select the Second Port by putting a check mark next to your first assigned port as shown and

26. Enter the IP address (Tester IP Address), Gateway Address (Gateway IP Address) and mainly
add the “Number of Emulated Routers per Port” as per the scenario/topology provided by
the Instructor and click on “Next” for the Second Port as shown -
the end of the Lab Manual as shown below. Please make sure to change “Increment By”(Per
Users.
27. Skip Screen number 4# of 6 and Screen Number 5# of 6.

28. On Screen number 6# of 6 select the Radio button that says “Generate and Overwrite Existing
Configuration”, give a relevant name “Ospf_Port_2” and further click on “Finish” to complete
the configuration for Port2.
29. Following screen appears indicating the use of the Scenario Editor to configure properties on
the 1st Port. The screen shows the “Ospf” and Interface as a Stack and as a Part of a Device
Group identified with a name as “Device Group 4” in this case under “Topology 2”.
30. At this point we have both Configurations on Port 1 and Port 2 successfully completed. In order
to verify there are a few caveats that should be considered –
a) Color on Ospf tab should be gray (as seen in the preceding image)
b) Color on Interface should be Green (as seen in the preceding image)
Protocol Interfaces on both ports should not have any exclamation Marks. (as seen below)-
Color of Opsf on the Resource tree should also be gray – (as seen below)
Color on Protocol Interfaces should be Green – (as seen above)

The Color on Ports should also be Green – (as seen below)
<End of Lab 10 a>

Lab 10b: Test Composer Scripting Lab
Objective - Our script will be executing a flap on both the ports 10 times before stopping.
Now let us use the IxNetwork “Test Composer” to create a script to flap the ports.
Note - Before starting “Test Composer” stop OSPF.
Also adjust the position on your screen so that you are on the Ports Tab by clicking on it as shown
and make sure that both the ports are visible in green –
1. Click the Automation tab to start the Test Composer Configuration as shown below.
2. Note the various fields under the Automation Tab that also includes “Test Composer”.
© IXIA 2013 September Test Composer Scripting Lab

3. Following screen appears after a few seconds that indicates the starting point to begin the
procedure for script writing. Click on the “+”sign to start the process of writing the script and
the following screen appears
4. The first command will be an execute command by default.
5. In order to indicate what should get executed double click in the empty space next to the
“Execute” as shown
6. Following screen appears with a Pull Down Option –
7. Click on the Pull down and choose the option that is most appropriate to execute. In our case
the execution will begin with Choosing “Port”.
8. Highlight the “Port” option and further select the “Simulate Link Down” option as shown –

9. Further click on the Browse option and select the two ports that has been assigned to you as
shown –
The “Select options” tab highlights the 2 ports for which you will generate a Port Flap.
10. Select your ports by putting a check-mark next to Ports and click on ok as shown–

That would complete the first step in the Script as “Port Simulate Link Down” -
11. In order to insert the next line, right click on area next to 1 (Execute) and choose the “Insert
below” option as shown below -
One more “Execute” command gets added to the script as shown below.
As we would like to create a pause between the Link Down and Link up we need to replace the
second “Execute” command with a “Sleep” command.
12. In order to do this, click on the second “Execute” command as shown, use the pull down and
replace it with a sleep command as shown -

13. Now add Step 3 to your script by “Port Simulate Link Up” by inserting yet another “Execute”
Command as shown-
14. By default in “Test Composer” the next new command that is added replicates the previous one,
therefore a new “Sleep” command gets added. This needs to be replaced by an “Execute”
command as shown –
Following Screen appears with the “Execute” Command where you will add a “Simulate Port
Link Up” as shown –
15. In order to indicate what should get executed double click in the empty space next to the
“Execute” as shown


16. Now in order to execute the above script for an iteration of 10 times, we need to put this script
in a “For-End-For “Loop as shown -
Following screen appears after expanding the Script-

The For- End-For Loop will run for 10 (“Count to”) iterations starting from:
 Count From = 1,
 Step Size = 1,
 Loop Type = Counter,
 Assigned to Variable = index1
17. In Order to run the above script select the entire script by highlighting the “For” and using the
shift key to select all the remaining commands up to “EndFor” and then right click as shown
and further click on “Play selected steps” as shown –
Port status is down for 10 seconds
Port status is up after 10 seconds
This flapping will go on for 10 iterations with 4 execution steps for each iteration.
< End of Lab 10b >

Lab 11: Macro Recorder Lab
Overview
The objective of the Lab is to get Hands-on experience using the New Recording Feature to build a
Test Composer Script that is capable of modifying the configuration on the Fly with Macro
Recorder.
Lab Objectives
 Continue from the 10a) and make sure that Route Ranges from OSPF are disabled by
removing the checkmarks.
 Start the Recorder and enable the first route range and stop recording.
 Edit the recorded procedure and play it and observe the Output in GUI.
Macro Recorder automatically builds the commands for the user as they make changes to the
configuration. Once these commands are captured by the recorder, they can be manipulated and
replayed just like any other Test Composer commands.
© IXIA 2013 September Macro Recorder Lab

Procedure
1. You will be building off the previous Ospf v2 Lab. Make sure to delete the earlier Test
Composer configuration by selecting the entire script and right clicking to delete the steps as
shown.
The following window appears-
2. Also, Make sure that the 6 Route ranges in your first and second port are disabled as shown –
3. Now click on the “Start Recording” tab to begin recording.

4. We will now put the check mark on the First Route Range under Port 1.
5. At this point stop the recording by clicking on the “Stop Recording” button as shown.
This will automatically create a Config Set command inside the procedure as shown -
Our Config set will require editing to allow all route ranges to be enabled across Port 1
represented as [vport1] and also we would require one more Config set that would allow all
route ranges to be enabled across Port 2 represented as [vport2].
6. In order to duplicate the Config set, click the current Config set and right click on it
and copy
7. Copy and paste the earlier Configuration Set. This will create one more Configuration Set as
shown.

8. Next we will edit the script in the script preview window for both “Config Sets” by putting them
in For-end-For Loop. To do this, select the 2 Config Sets script with the shift key and further
right click to put them in a “For-end-For” Loop as shown below-
9. Also make the necessary change in the second “Configuration Set” for Port 2 by replacing
vport[1] to vport[2] a shown below-
10. Further Edit the router[1] field in both Config Sets by replacing the router[1] field in both
“Configuration Sets” to router[$index1] as shown –
Before:
After:
First Config set
Second Config set

This will allow the For-end-For Loop to execute 3 iterations for vport[1] and 3 iterations for
vport[2]. For each iteration, there will be a checkmark put for routeRange after the script is run.
1. vport[1] – Route range enabled – 200.1.1.0/24
4. vport[2] – Route range enabled - 203.1.1.0/24
11. In order to run the script we will not be selecting the script and playing them, instead we will
play the entire procedure from the IxNetwork GUI and watch the Route Ranges get enabled.
12. Use the Pull down for the Macro in the Home Tab and click on it to run as shown –
Before running the Macro
After running the Macro –

Execution Messages while running the Macro –
<End of Lab 11>

Lab 12: Open Flow Lab
Overview
Most modern day network architectures rely on a traditional and conventional hierarchical
organization, dependent on a tree-like structure of Ethernet switches and routers. Focusing solely
on client-server computing, the network architectures fail to meet the needs of today’s computing
trends. With the changes in traffic patterns for increased accessibility and connectivity, the rising
prominence of both private and public cloud services, and the immense parallel server processing
necessary for mega datasets, it is imperative that the demand for higher network capacity is
fulfilled.
By utilizing Software Defined Networking (SDN), it becomes possible to address these needs
using a more dynamic and flexible networking architecture. SDN moves away from traditional
architecture and into a revolutionary service delivery platform that can easily and readily address
the changes in industry. With SDN, the control plane is accessed and modified using open
protocols through software clients. By allowing third parties increased access to the control plane
via software, SDN provides enterprises and carriers unparalleled programmability and network
flexibility with rapid experimentation and optimization in order to address business needs.
© IXIA 2013 September Open Flow Lab

OpenFlow
OpenFlow is one such communication protocol that enables SDN. OpenFlow, the first standard
interface communications protocol designed specifically for SDN, decouples the control and data
planes so that software can determine the network packets passing through a network thereby
customizing the needs of applications and its users. With the centralization of the control plane, it is
possible to introduce and experiment with new capabilities in isolated slices of the network
without affecting the rest of the network. This major change in network architecture offers its users
a way to introduce new applications without the reliance upon individual device configuration and
vendor releases.
SDN via OpenFlow revolutionizes and expands the capabilities of networking architecture,
providing key benefits for the ever-changing market. With rapid innovation and experimentation
possible through software control, OpenFlow delivers the flexibility necessary to combat current
and future network problems. Additionally, not only is there an increased choice regarding new
applications but there is also an increased choice regarding vendor markets. The switch from a
hardware-based to a software-based networking architecture creates open multivendor markets as
the network operator can select different control and data plane vendors. The division of the
planes increases network reliability and security, creating the potential to lower both CAPEX and
OPEX costs while decreasing the complexity of networking hardware and network management.
OpenFlow is a protocol that allows a server to tell network switches where to send packets. In a
conventional network, each switch has proprietary software that tells it what to do. With
OpenFlow, the packet-moving decisions are centralized, so that the network can be programmed
independently of the individual switches and data center gear.
In a conventional switch, packet forwarding (the data path) and high-level routing (the control
path) occur on the same device. An OpenFlow switch separates the data path from the control
path. The data path portion resides on the switch itself; a separate controller makes high-level
routing decisions. The switch and controller communicate by means of the OpenFlow protocol.
This methodology, known as software-defined networking (SDN), allows for more effective use
of network resources than is possible with traditional networks. OpenFlow has gained favor in
applications such as VM (virtual machine) mobility, mission-critical networks, and next
generation IP-based mobile networks.
Test Execution
However, with every new and innovative networking strategy and solution comes the need to test
its efficiency. As today’s growing market increases its need for accessibility, connectivity, immense
server processing, and new application / services, testing the new network paradigm of SDN is
imperative in order for service providers to turn OpenFlow into a reality. With Ixia, equipment
manufacturers, service providers, enterprises, and government agencies can test SDN via OpenFlow
thereby addressing and answering the following key questions and concerns:
Is the network architecture properly and effectively functioning? What is the capability of
introducing a new software program or application? Can the network keep pace with new
technologies and standards while ensuring rapid innovation? Does the programming environment
allow the centralized network state to easily tune the network behavior, applications, and
services to user needs? Can the network ensure protocol conformance and optimal performance?
Is the network management cost effective while remaining secure and reliable?

Lab Objectives
 Create an Open flow environment between 2 Ixia Ports
 One Ixia Port emulating Controller and the other emulating an open flow Switch.
 Run the protocol and verify the Echo’s between the Controller and the Switch.
Open Flow Topology with Ixia Port Emulation

1. Launch IxNetwork and select ports as per the IP Assignment sheet provided to you by the
Instructor. Note this exercise involves taking 2 Ixia Ports connected Back-Back.
2. Connect to the Chassis as advised by the Instructor.

3. Take the ports as advised by your Instructor based on your User Number. The configuration
done below is for User 1and hence the first 2 Ports are used as shown below.
4. Make sure that the Ports are up by verifying Link Status and also the color on the ports should
turn green.
At this point the Protocol Interfaces Tab is grey in color. This is because we have yet to
configure IPs and Gateways for the selected Ports. Also, as we have not yet enabled the Protocol
(Open Flow). Hence there is no indication for the same in the Resource Tree.
5. Click on Protocol Interfaces Tab and you will observe that the Grids are also empty a shown
below-

6. Start the Configuration by Naming the Ports. The first Ixia port (Port1)will be acting like an
emulated “Controller” and the Second port (Port2) will be acting like an emulated “Switch”.
Rename the Ports accordingly.
7. In order to put the IP address and Gateway select the “Protocol Interfaces” Tab. Following
screen appears where you can enter the IP address and the Gateway address for Port 1 and as
the Ports are connected Back-Back , just reverse the IP and Gateway for Port 2 a shown below
and enable them. Make sure there are no red color exclamation marks .
8. The next step involves configuring the “Open Flow” Protocol. In order to do that Click on the
“Protocols” tab as shown below and select the Open Flow Protocol by putting a check mark
next to it for both the Ports as shown below.
Before:
After:

You will note in the resource tree that the “OpenFlow” Protocol appears but is grey in color as
the protocol is not running. Also both the Ports after expanding them show the sub-tabs, that
will be relevant when we start the protocol.
9. Click on the “OpenFlow” tab and observe the configured/configurable sub-tabs a shown.
The first sub-tab is the “Ports” Tab and describes the Number of Devices on each Port and also
the their Port Roles.
10. Click on the “Devices” tab as shown and the default Description is visible. Also note that there is
no Checkmark next to the “Enable” check-box. Change the Description as shown and also
enable both the Devices by putting a check-mark next to the enable check-box.
Before:
After:
11. Click on the “Interfaces” sub-tab and the default fields indicate that
a) Protocol Interface is Unassigned
b) Number of Channels is 0.
c) Periodic Echo is enabled.
d) Echo interval is same for both Controller and Switch. (10seconds)

12. Change the default parameters as follows –

a) Protocol interface is “Connected” (Use the pull down under the field).
b) Number of Channels for both is 1
c) Periodic Echo is “Enabled” for both Devices.
d) Echo interval for Switch is 25 seconds.
Before:
After:
13. Scroll to the right on the “Interfaces” tab as shown and note that the “Mode of Connection” for
both devices is passive. This needs to change as the Switch will be initiating the echo to the
Controller every 25 seconds and hence the Switch will have a mode of connection that needs to
be “Active” as shown below.
Before)
After:

14. Now in order to configure the parameters of the Open Flow Channel further click on the Sub-tab
and go to the “OF Channels” Tab and enter the “Remote IP” for both Devices based on the IP
that you have earlier assigned to the Devices based on your User No. and further enable them
by putting a check mark next to the “Enable” Check-box.
Before:
After:
15. Create a Statistical view for Open flow by clicking on “Select view” and putting checkmark on
“OpenFlow Controller Aggregated Statistics” as shown –
You will note that there is no activity on the Grid as the protocol has yet to be started as shown
below.

Also note that the Controller has not yet learned the info coming from the Switch as the protocol
is not running. This is because the “Refresh OF Channels” tab on the Ribbon on the Top is
greyed out. This is again because the Protocol is not running as shown below.
There is also a clear indication further to the right on your screen that indicates that the
Learned Info Records are all “Zero” as the protocol is not running.
16. Before starting the protocol we will enable Control Plane Capture on both the Ports as shown.
17. At this stage we are ready to start the protocol. Click on the “Protocol” Play button on the
ribbon or the “OpenFlow” play button to start the protocol as shown below.

Observe the “OpenFlow Controller Aggregated Statistics” and confirm the OF channel is up
and hello packets are being exchanged between the Switch and the Controller.
18. In order to see the Information learned by the Controller from the Switch, click on the “Learned
Information” under the “Controller” as shown and further click on “Refresh OF Channels”.
The OF info with the “Data Path ID” along with Local Port Number for Controller and
Remote Port Number for Switch should be visible.
19. Start the Capture that you had earlier set for the Control Plane only and you can see the Echo
and TCP packets being exchanged between the Controller and Switch a shown below.

20. The Ladder Diagram indicates Echo Request packets exchanged between Open Flow endpoints
as shown.
21. In order to view the Learned Info Records on the “Controller” click on the “Controller” tab and
note that in order to view statistics we need to select the rows and send trigger.
22. In order to see Statistics, select the entire row as shown below and further enable triggering.

23. The moment the “On Demand Messages” trigger is clicked, there will be a pop up where you
can specify the parameter for which you would like to send the Trigger. In this case we have
taken the parameter as Flow Stat. This can be done by putting a checkmark next to “Flow Stat”
as shown.
24. Click on ok after making the selection a shown above and further send the trigger by clicking on
the “On Demand Messages” as shown.
The Learned Info Records indicate 10 Default Flow Stats as seen below.
<End of Lab 12>

Lab 13a: Setting up Ospfv2 before running RFC 2544 Test
Overview
The first step before Launching “Quick Test” is to allocate ports, configure Ospf v2 first and
subsequent RFC 2544 Throughput and Latency configuration. We will click on the scenario Editor
Tab and configure the Ospf v2 as the Control Plane over which we will be sending the Traffic using
the RFC 2544 Quick Test Option in IxNetwork for specific Frame Sizes and generate a Quick Test
report.
Lab Objectives
 Set up an IPv4 based Ospf topology. (Lab 1)
 Run the ospfv2 configuration.(Lab 3a)
 Run the “Quick Test” for RFC 2544 Throughput/Latency Test and generate Report.
Ospf v2 Topology for executing RFC 2544 Throughput/Latency Test
© IXIA 2013 September Setting up Ospf V 2 before running RFC 2544



Topology”.
3. Use the Protocol Wizard to configure OSPFv2 Stack in the Classic Mode for a given topology.
4. Set the stage for running the Protocol.
Procedure
© IXIA 2013 September Setting up Ospf v 2 before running RFC 2544

i) “+ Add Chassis”
j) Recently Used Chassis

counts.
create a compact protocol configuration for the NextGen protocols that efficiently scales to
very large port and protocol session counts.


legacy way.
Improve Usability
easy to understand.
with the test.
The NextGen Architecture improves functionality and inter-networking in the following
ways:
Improve Scalability
The Next Gen Architecture improves scalability in the following ways:
system.
Mode” and further select “Ospf” as shown –
Ixia IxNetwork 7.0 has an option of configuring Ospf with Next Gen and can be used as an option
when the customer requirements include improved usability, improved functionality and
improved scalability. In our configuration we will configure Ospf in the Classic Mode.
13. Select “Ospf” and further select “New Wizard Run” and click on “Run Wizard” a shown below.

15. Make sure that the number of Emulated Routers on Port 1 is 1 as shown below.
16. Skip 3 of 6, 4 of 6 and 5 of 6 Screens and give a relevant name to the Config on Port1 and select
the appropriate Radio Button and further click on Finish.

17. Now enable Ospf on Port 2 by clicking on the “+ “sign next to “New Topology” as shown.
18. Click on Next and select Ospf as the protocol as shown below –
Following screen appears to the right of the screen as shown-
19. Select Port 2 as shown and click on Next.

20. Make sure that the number of Emulated Routers on Port 2 is 1 as shown below.
21. Skip 3 of 6, 4 of 6 and 5 of 6 select the appropriate Radio Button and further click on Finish.
The final Topology is as shown where the Protocol Interfaces on both the Ports should be up in
green color and the ospf tables in the topology should be in grey color as the protocol has not
yet been started.
Before starting the Ospf Protocol there are 2 parameters of the protocol that need to be
tweaked –
a) Ospf interface should be in a Point-Point Configuration
b) The checkmark next to discard Learned LSA’s should be removed as shown –
Before for step a:
After for step a:

Before for step b:
After for step b:

Also the property of the port should be set without “Flow Control” so that the pause frames
do not come in the way of the Throughput Test and cause low average throughput as shown -
Before:
After:
You will receive a message as shown below to commit the changes on the Port. Click on Apply as
shown -

22. We can start the Protocol by clicking on the Ospf Tab and right clicking to start the protocol.
23. Verify the Protocol is up a shown in the scenario editor and also on the Statistics –
<End of Lab 13 a>

Lab 13b: Running RFC 2544 Test
Overview
The first step before Launching “Quick Test” is to allocate ports, configure Ospf v2 first (Lab 13 a)
and subsequent RFC 2544 Throughput and Latency configuration.
We will click on the scenario Editor Tab and configure the Ospf v2 as the Control Plane over which
we will be sending the Traffic using the RFC 2544 Quick Test Option in IxNetwork for specific
Frame Sizes and generate a Quick Test report.
Lab Objectives
 Run the “Quick Test” for RFC 2544 Throughput / Latency Test
 Generate Report.
© IXIA 2013 September RFC 2544 Test

Topology for running the RFC 2544 Test

Lab Procedure
1. Click on the “Home” Tab and further click on the “+” sign on “Add Quick Test” to open the
“Quick Test” wizard to as shown-
2. Select the RFC 2544 Folder and expand it as shown below.

3. From the Expanded Tree select Throughput/Latency Option as shown below-

4. Click on the Ports Tab and verify that the Flow Control is turned off on both the Ports and
further click on “Next” as shown below.
5. In the Frame Data tab make sure the appropriate IP addresses and Gateway addresses are
entered along with the appropriate incrementing factors.
Before:

After:
6. Click on “Next” and enter the below mentioned parameters into the respective fields under
“Traffic”.
1. “Source/Dest” = One to One
2. “Bidirectional”
3. “Apply your Selection”
Before:
Before:
Before:

After:
After:
After:
7. Click on “Next” to move to the Traffic Options Tab as shown below and make the following
changes.
1. Put a check mark next to “Regenerate traffic at Run Time”.
2. Mode = Custom
3. Frame Size 128
Before:
After:

8. Further Click on “Next” – Following Screen Appears as default under “Test Parameters”.
9. Make the following Changes to the default parameters as shown.

1. Load Type = Step
2. Load Unit = % Line Rate
3. Initial Rate = 90
4. End Rate = 100
5. Step Rate = 10
6. Acceptable Frame Loss = 0 %
Before:
After:

10. Click on “Next” and give a relevant name to your configuration as shown.
Before:
After:
11. Verify in the Protocol Interface that the QT configuration has been added to the existing
Protocol Interfaces on Port1 and Port 2.
12. For starting the RFC 2544 Throughput Test, go to the “Home” menu and select the drop down
on your Quick Test as shown -

Monitoring the Results

Generating Quick Test Report from Data Miner
<End of Lab 13b >

Lab 14a: Setting up Ospfv2 before Running Cloud Performance

Test
Overview
Testing cloud solutions is complex for a several reasons. Cloud testing includes infrastructure tests
that could be evaluated using standard network test equipment. But cloud testing also includes the
virtual server space that standard testing tools cannot easily explore, not to mention the added
complexity of shared memory, CPU, network and storage resources. Ixia can support both type of
tests offering hardware to test the infrastructure, virtual Ixia tools to test within the virtual space,
and configuration assistance to put it all together.
Lab Objective
Measure the forwarding performance of a Data Center, Top of Rack Switch or Network using
simulated data center, North-South and East-West Profile.
© IXIA 2013 September Setting up Ospf v2 for Cloud Performance Test

Lab Procedure
1. The first step before Launching “Quick Test for Cloud Performance” is to allocate 6 ports per
User.
2. 2 Ports for North- South and 2 Ports for East- West will be used during the cloud
performance configuration from the 1st and 2nd Load Modules as advised by your instructor and
your defined User ID.
3. The remaining 2 Ports (Optional as they are Back-Back)) would represent background traffic
during the Test while configuring the “Quick Test” and would be taken from the 3rd Load
Module as advised by your instructor and your defined User ID.
4. You will start the configuration by clicking on the Protocol Configuration tab and configure the
Ospf v2 for the 1st 4 Ports.
5. Also you will configure 2 more ports to send/receive raw traffic using the advanced traffic
wizard with flow group defined from Line Card 3 per User (Back – Back) as a Background
Traffic while running the Cloud performance test.
6. Start the Ospf Protocol for the first 4 Ports and verify Full Sates for all 4 sessions.
7. Now Launch the Quick Test for Cloud Performance and configure parameters and run the
Test for a Pass/Fail Criteria and generate report in the Data Miner.
Topology for executing Cloud Perf Test

1. Start the IP Cloud Performance configuration by taking the user defined Ports as advised by
your instructor.
And the first 2 Ports from Card 03 as shown –

2. Configure Ospf Protocol on the first 4 Ports as shown -

Ospf on 1st Port -
3. Skip 3 # 6, 4 # 6 and 5 # 6 Screens and save the configuration on Port 1 as O1 by enabling

the radio button on “Generate and Overwrite Existing Configuration” as shown and click
on “Finish”.
4. Similarly configure Ospf for Port 2 as shown by launching the wizard again.

on “Finish”.


on “Finish”.


on “Finish”.
Now the Ospf Protocol has been configured on the four ports.
10. Close the Wizard by clicking on “Close”. Observe the Protocol Interfaces Tab
11. Let us now configure the IPs for Port 5 and Port 6 as shown. They are connected back to
back so the IPs needs to be mirrored a shown.
Also the property of the port should be set without “Flow Control” so that the pause frames
do not come in the way of the Throughput Test and cause low average throughput as shown
–
12. Click on Ports and further click on the Ethernet Sub-Tab and remove all the checkmarks
under “Enable Flow Control” as shown

Background Traffic Configuration (Optional)

13. Let us now create a flow group for sending the Background traffic by taking port number 5
and port number 6 and configuring a Raw Traffic Item with flow group enabled a shown
using the “Advanced Traffic Wizard”.
14. Also select the source and destination of the Raw Traffic between Port 5 and Port 6 a
shown -
15. Apply it and create an endpoint set as shown -
16. Skip Packet Qos and come to the Flow Group Option and select the option as “Src/Dest
Endpoint Pair” to create a flow that would be needed as a background traffic later.
17. Click on ‘Next” and under the Frame set up Tab choose the Frame size = 128 bytes.
18. Click on Next and under the Rate set up Tab choose the Line Rate = 10% and click “Next”

19. Under Flow Tracking select the option as “Source/Dest Endpoint Pair “as shown and click
on Next
20. Skip “Protocol Behavior” tab and take preview of your flow group as shown –
21. Click on Next to “Validate’ the Traffic Configuration.
22. On Successful validation we can now create the background flow based Traffic Item for our
Cloud Performance Test by clicking on “Finish” as shown –

23. Start the Ospf Protocol as shown on the first four Ports as shown–
24. Verify the states on all four Interfaces are “Full” as shown –
<End of Lab 14 a>

Lab 14b: Configuring and running Cloud Performance Quick Test
1. Start the Quick Test by clicking on the Add Quick Tests button on the Ribbon as shown.
2. Select Converged Data Center folder and expand it.
© IXIA 2013 September Running Cloud Performance Test

3. Select CloudPerf option as shown and click Next.
Following Quick Test Wizard screen appears –
4. Change the parameters such that the Port Role is remarked as

 Port 1= North
 Port 2= South
 Port 3= East
 Port 4= West
Port 5 and Port 6 will not be included into the Test as they would be used for Background traffic
and therefor the checkmarks will be removed next to them. Following screen appears after the
above changes are made.
5. Click on Next to move to “Frame Data”. Following Screen appears.

6. Enter the details of your first port IP address and increment the gateway and the Interface IP
using the correct address incrementing factor. For User 1 following changes need to be done as
the IPs are:
 20.3.1.2 (First IP on Port 1)
The Octet that needs to be incremented is the 3rd octet, therefore the incrementing factor for
the above will be 0.0.1.0.
Similarly for the gateway increment keep the checkmark next to “Increment Gateway IP
Address per Port” on.

After making changes following screen appears –
7. Click on “Next” to move to “Traffic”. At this point check if the “Protocol Interfaces” is green
and up for all the Interfaces. Now you need to configure the Traffic Profiles with the type of
Traffic that needs to be sent over the cloud between North-South and East-West.
On the Traffic Tab observe that as default no Profiles have been added. Our First Step is to add a
profile for North-South bound traffic and the later for East-West bound traffic. We will use the
following profiles.
1. North-South bound Traffic Profile = YouTube traffic
2. East-West bound Traffic Profile = HTTP Traffic.

8. Click on Add New” Profile and the following screen appears -
9. Enter the parameters as follows –

Before:
After:
10. To enable the created profile, click on the checkmark after making all your selections for the
profile.
This Profile was created for North and South.

11. We will create one more profile for East and West below by clicking on the “+”sign next to “Add
New” as shown.
12. Edit the Frame Size settings for both North- South Profile and East-West Profile as shown so
that the request and responses are more predictable for a specific mentioned frame size by
clicking on the drop down button and make the change as shown.

13. Click on “Next” to move to the next Tab in the “Cloud Perf Quick Test Wizard”.
14. Now that the 2 profiles have been created, the next step is to configure the “Background
Traffic” by putting a checkmark next to “Include” for the traffic item created earlier. This is
optional as it represents traffic of Multicast in nature that is may also be traversing the cloud. As
we have included 2 ports back to back and also configured a Traffic Item to represent this type
of traffic, it is optional to “Include” it or not. This is more so, as the traffic is not moving over
out DUT. In this Lab we will “Include” the “Background Traffic” as shown.
15. Click on “Next” and configure the only parameter that is to “Regenerate Traffic” before
starting as best practice in case you have made a lot of changes to the parameter for “Traffic
Options” by putting a checkmark as shown. Keep the remaining parameters at their default
values.
16. Click on “Next” and move to the next tab in the wizard.
17. In the “Test Parameters” window following fields appear. Some of which can be tweaked based
on the specific needs and specific test environment for running the Test. The parameters that
you will change are as follows-
 Load Type = Step
 Load Unit = % Line Rate
 Initial Rate = 90
 End Rate = 95
 Step Rate = 5
 Acceptable Frame Loss = 0 %
 Pass/Fail= Rate less than 70%
Before:
Before:

After:
After:
18. Click on “Next” and give a name to your Configuration and further click on “Finish” to conclude
your Cloud Performance Quick Test Wizard Configuration as shown-
19. Verify that the Protocol Interfaces and the Protocol are up and the Quick Test Traffic Item is not
in Red and is ready to be launched as shown-
20. Also make sure that there are no exclamation marks on the “Connected Interfaces” as shown-

21. In order to run the Cloud Perf Quick Test click on the “Home Tab” and further click on the play
button as shown-
22. Alternatively you could also click on the Quick Test Tab on the Resource Tree and click on the
play button to run the test as shown -
Test Results

Report Generation of the Test Conducted from “Data Miner”
< End of Lab 14 b>

APPENDIX
Port Assignment
XMV-16
User Port 1 Port 2
Card/Slot Port Card/Slot Port
1 1 1 1 2
2 1 3 1 4
3 1 5 1 6
4 1 7 1 8
5 1 9 1 10
6 1 11 1 12
7 1 13 1 14
8 1 15 1 16
9 2 1 2 2
10 2 3 2 4
11 2 5 2 6
12 2 7 2 8
13 2 9 2 10
14 2 11 2 12
15 2 13 2 14
16 2 15 2 16

OSPF Lab Parameter Table

TESTER (Ixia)
Gateway
User Port
Address/DUT IP First Network in
First IP Address
Route Range
1 Port 1 20.3.1.1 20.3.1.2/24 200.1.1 .0/24

Port 2 20.3.2.1 20.3.2.2/24 203.1.1 .0/24
2 Port 1 20.3.3.1 20.3.3.2/24 200.2.1 .0/24

Port 2 20.3.4.1 20.3.4.2/24 203.2.1 .0/24
3 Port 1 20.3.5.1 20.3.5.2/24 200.3.1 .0/24

Port 2 20.3.6.1 20.3.6.2/24 203.3.1 .0/24
4 Port 1 20.3.7.1 20.3.7.2/24 200.4.1.0/24

Port 2 20.3.8.1 20.3.8.2/24 203.4.1 .0/24
5 Port 1 20.3.9.1 20.3.9.2/24 200.5.1 .0/24

Port 2 20.3.10.1 20.3.10.2/24 203.5.1 .0/24
6 Port 1 20.3.11.1 20.3.11.2/24 200.6.1.0/24

Port 2 20.3.12.1 20.3.12.2/24 203.6.1 .0/24
7 Port 1 20.3.13.1 20.3.13.2/24 200.7.1 .0/24

Port 2 20.3.14.1 20.3.14.2/24 203.7.1 .0/24
8 Port 1 20.3.15.1 20.3.15.2/24 200.8.1.0/24

Port 2 20.3.16.1 20.3.16.2/24 203.8.1 .0/24
9 Port 1 20.3.17.1 20.3.17.2/24 200.9.1 .0/24

Port 2 20.3.18.1 20.3.18.2/24 203.9.1 .0/24
10 Port 1 20.3.19.1 20.3.19.2/24 200.10.1.0/24

Port 2 20.3.20.1 20.3.20.2/24 203.10.1.0/24
11 Port 1 20.3.21.1 20.3.21.2/24 200.11.1.0/24

Port 2 20.3.22.1 20.3.22.2/24 203.11.1.0/24
12 Port 1 20.3.23.1 20.3.23.2/24 200.12.1.0/24

Port 2 20.3.24.1 20.3.24.2/24 203.12.1.0/24
13 Port 1 20.3.25.1 20.3.25.2/24 200.13.1.0/24

Port 2 20.3.26.1 20.3.26.2/24 203.13.1.0/24
14 Port 1 20.3.27.1 20.3.27.2/24 200.14.1.0/24

Port 2 20.3.28.1 20.3.28.2/24 203.14.1.0/24
15 Port 1 20.3.29.1 20.3.29.2/24 200.15.1.0/24

Port 2 20.3.30.1 20.3.30.2/24 203.15.1.0/24
Port 1 20.3.31.1 20.3.31.2/24 200.16.1.0/24
16
Port 2 20.3.32.1 20.3.32.2/24 203.16.1.0/24
BGP Lab Parameter Table

TESTER (Ixia)
Gateway First
User Port
Address/DUT IP AS # First Network in
First IP Address
Route Range
1 Port 1 — IBGP 20.3.1.1 65001 20.3.1.2/24 1.1.1.1 to 3.3.3.3

Port 2 — EBGP 20.3.2.1 65011 20.3.2.2/24 4.4.4.4 to 6.6.6.6
2 Port 1 — IBGP 20.3.3.1 65001 20.3.3.2/24 7.7.7.7 to 9.9.9.9

Port 2 — EBGP 20.3.4.1 65021 20.3.4.2/24 10.10.10.10 to 12.12.12.12
3 Port 1 — IBGP 20.3.5.1 65001 20.3.5.2/24 13.13.13.13 to 15.15.15.15

Port 2 — EBGP 20.3.6.1 65031 20.3.6.2/24 16.16.16.16 to 18.18.18.18
4 Port 1 — IBGP 20.3.7.1 65001 20.3.7.2/24 19.19.19.19 to 21.21.21.21

Port 2 — EBGP 20.3.8.1 65041 20.3.8.2/24 22.22.22.22 to 24.24.24.24
5 Port 1 — IBGP 20.3.9.1 65001 20.3.9.2/24 25.25.25.25 to 27.27.27.27

Port 2 — EBGP 20.3.10.1 65051 20.3.10.2/24 28.28.28.28 to 30.30.30.30
6 Port 1 — IBGP 20.3.11.1 65001 20.3.11.2/24 31.31.31.31 to 33.33.33.33

Port 2 — EBGP 20.3.12.1 65061 20.3.12.2/24 34.34.34.34 to 36.36.36.36
7 Port 1 — IBGP 20.3.13.1 65001 20.3.13.2/24 37.37.37.37 to 39.39.39.39

Port 2 — EBGP 20.3.14.1 65071 20.3.14.2/24 40.40.40.40 to 42.42.42.42
8 Port 1 — IBGP 20.3.15.1 65001 20.3.15.2/24 43.43.43.43 to 45.45.45.45

Port 2 — EBGP 20.3.16.1 65081 20.3.16.2/24 46.46.46.46 to 48.48.48.48
9 Port 1 — IBGP 20.3.17.1 65001 20.3.17.2/24 49.49.49.49 to 51.51.51.51

Port 2 — EBGP 20.3.18.1 65091 20.3.18.2/24 52.52.52.52 to 54.54.54.54
10 Port 1 — IBGP 20.3.19.1 65001 20.3.19.2/24 55.55.55.55 to 57.57.57.57

Port 2 — EBGP 20.3.20.1 65101 20.3.20.2/24 58.58.58.58 to 60.60.60.60
11 Port 1 — IBGP 20.3.21 .1 65001 20.3.21.2/24 61.61.61.61 to 63.63.63.63

Port 2 — EBGP 20.3.22.1 65111 20.3.22.2/24 64.64.64.64 to 66.66.66.66
12 Port 1 — IBGP 20.3.23.1 65001 20.3.23.2/24 67.67.67.67 to 69.69.69.69

Port 2 — EBGP 20.3.24.1 65121 20.3.24.2/24 70.70.70.70 to 72.72.72.72
13 Port 1 — IBGP 20.3.25.1 65001 20.3.25.2/24 73.73.73.73 to 75.75.75.75

Port 2 — EBGP 20.3.26.1 65131 20.3.26.2/24 76.76.76.76 to 78.78.78.78
14 Port 1 — IBGP 20.3.27.1 65001 20.3.27.2/24 79.79.79.79 to 81.81.81.81

Port 2 — EBGP 20.3.28.1 65141 20.3.28.2/24 82.82.82.82 to 84.84.84.84
15 Port 1 — IBGP 20.3.29.1 65001 20.3.29.2/24 85.85.85.85to 87.87.87.87

Port 2 — EBGP 20.3.30.1 65151 20.3.30.2/24 88.88.88.88 to 90.90.90.90
Port 1 — IBGP 20.3.31.1 65001 20.3.31 .2/24 91.91.91.91 to 93.93.93.93
16
Port 2 — EBGP 20.3.32.1 65161 20.3.32.2/24 94.94.94.94 to 96.96.96.96

L3VPN
OSPFv3 Lab

OSPFv3 Lab
Multicast Lab

IxNetwork Specialist September 2013-Jp

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IxNetwork Specialist September 2013-Jp

Uploaded by

Copyright:

Available Formats

IxNetwork Specialist

Corporate Headquarters Ixia Worldwide Headquarters Web site: www.ixiacom.com

EMEA Ixia Europe Limited Support: eurosupport@ixiacom.com

© IXIA 2013 September

Lab 1 – Working with Scenario Editor 17

Lab 2 – Port Management 46

Lab 3a – Engage Ospf Protocol Configuration 59

Lab 3b: BGP Protocol Configuration 73

Basic Traffic Wizard 89

Lab 4: Basic Traffic Wizard 112

Advanced Traffic Wizard 129

Quick Flow Groups 173

Lab 6: Raw Traffic using Quick Flow Groups 186

Lab 7 – Configuring L3VPN with Scenario Editor 197

Lab 8 – Configuring IPv6 with Ospf v3 239

Lab 9 – Configuring Multicast with Scenario Editor 273

Lab 10a – Test Composer Pre-Lab 299

Lab 10b: Test Composer Scripting Lab 321

© IXIA 2013 September

Lab 12: Open Flow Lab 347

Lab 13 a: Setting up Ospfv2 before running RFC 2544 Test 371

Lab 13 b: Running RFC 2544 Test 391

Lab 14 a: Setting up Ospfv2 before Running Cloud Performance Test 407

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

© IXIA 2013 September IxNetwork Introduction

Lab 1 – Working with Scenario Editor

Ospf Test Topology with Ixia Port Emulation

© IXIA 2013 September Working with Scenario Editor

Test Topology with Ixia Chassis

Figure 1: Port Management Topology

Description of Lab Procedure

© IXIA 2013 September Working with Scenario Editor

© IXIA 2013 September Working with Scenario Editor

© IXIA 2013 September Working with Scenario Editor

 The NextGen Architecture improves usability in the following ways:

 The NextGen Architecture improves functionality and inter-networking in the following

 The NextGen Architecture improves scalability in the following ways:

© IXIA 2013 September Working with Scenario Editor

1. First Selecting Port/Ports

© IXIA 2013 September Working with Scenario Editor

© IXIA 2013 September Working with Scenario Editor

17. Screen Number # 4 of 6 includes Network Range –

© IXIA 2013 September Working with Scenario Editor

Multiplier – Increases the count of Devices in a Device Group.

Network Group – A Network Group represents a set of L3 networks (sub-netted or switched)

© IXIA 2013 September Working with Scenario Editor

© IXIA 2013 September Working with Scenario Editor

2. Skip Screen number 4# of 6 and Screen Number 5# of 6.

© IXIA 2013 September Working with Scenario Editor

© IXIA 2013 September Working with Scenario Editor

e) Color on Protocol Interfaces should be Green – (as seen above)

CONTINUED AT ENGAGE OSPF PROTOCOL CONFIGURATION IN PAGE 59

© IXIA 2013 September Port Management

© IXIA 2013 September Port Management

© IXIA 2013 September Port Management

Lab 2 – Port Management

© IXIA 2013 September Port Management

© IXIA 2013 September Port Management