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.

20. 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.

Module 4 Advanced Traffic Wizard

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.

22. 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 4. You may need to move windows around to see both. One could be hidden behind the other one.

Module 4 Advanced Traffic Wizard

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?

© IXIA 2012 FEBRUARY

24. 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.

25. Make sure the row with Lab 4 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.

Module 4 Advanced Traffic Wizard precedence value. You will see this:

27. From here, highlight the first row and then make sure your inside a cell. Right click and select “Ingress/Egress Statistics” from the drop down menu. This will create a new stat view.

© IXIA 2012 FEBRUARY

28. The newly created table will show the TOS values from ingress to egress.

29. 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.

Module 4 Advanced Traffic Wizard

30. 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)

© IXIA 2012 FEBRUARY

31. 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?

32. 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.

33. 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.

Module 5 – Quick Flow Groups

Module 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 2012 FEBRUARY