Test Methodology Journal Test Methodolo - Spirent Support

Test Methodology Journal Test MethodoloInternet Protocol Television (IPTV)June 2006

Table of Contents

Introduction 2

Capacity Testing 3

Number of Multicast Streams 16

Channel Change Behavior 26

Video Quality Test 30

Glossary 46

Appendix A 48 Appendix B 53

Spirent Communications Test Methodologies • IPTV Test Methodology Journal

2

Introduction Over the last several years, as voice revenues suffered from increased competition and the resulting commodity pricing, service providers have searched for new ways to drive revenue and attract and retain customers.

They have discovered that the most profitable way to drive new revenue is through the bundling of services. By becoming the sole provider of as many services as possible, service providers are able to generate additional revenues while also minimizing the loss of their customers to competitors.

To take advantage of this opportunity, service providers have been migrating their voice-only networks to infrastructures that would also enable advanced applications and content-rich services such as e-mail, video, gaming, etc… This combination of voice, video, and data services is more commonly known as “Triple Play”.

Internet Protocol Television (IPTV) is a broadcast television service offered over a traditional service provider IP-based network, and promises to be a key revenue driver in the Triple Play package.

To offer IPTV services at a quality level acceptable to most viewers, the service provider must have the ability to deliver at least 200 channels of high quality video without packet loss to thousands of households in hundreds of neighborhoods.

Unfortunately, the simple delivery of these channels is not enough. Users have become accustomed to a high level of video quality from their current cable or satellite service provider and will not tolerate distorted video or noticeable delays in changing channels in any new service. This requires high bandwidth and specialized features in the access portion of the network to support high quality IPTV simultaneously with other network based services such as voice, Voice over IP (VoIP), internet access and gaming.

The delivery of quick channel changes to up to four (4) set top boxes per household without over-subscribing the DSL lines or network with unwatched channels is an absolute requirement for successful deployment of IPTV services. Network equipment manufacturers (NEMs), component manufacturers, and service providers alike need sophisticated and comprehensive new testing tools to stress the features and capacity of their products or infrastructure to support IPTV services.

In this Test Methodology journal, several key tests will be described which enable the user to emulate IPTV services at varying subscriber loads, create different client profiles for different types of behavior, measure such key parameters as channel change times and video quality (V-Factor), and analyze detailed statistics about product or service performance.

Additional test methodologies can also be found at http://www.spirentcom.com/tmj/download/.

Best Wishes with your testing efforts.

Sincerely,

Spirent Communications


3

Capacity Testing

Associated Documentation • RFC 1242: Benchmarking Terminology for Network Interconnection Devices • RFC 2544: Benchmarking Methodology for Network Interconnect Devices

Objective This test validates workloads, ensuring proper functionality with minimal loads.

Overview This procedure ensures a candidate workload functions correctly. It also assists with discovery of connectivity issues, syntax errors and other problems before a high-load test is run. Use this validation as a first step before the upcoming test methodologies in this journal. This test provides the percentage of packet loss, the capacity of the Device Under Test (DUT) and an estimated value of Internet Protocol Television (IPTV) users the DUT is able to handle.

Setup


4

1. Configure the router to use at least two vlans. Traffic will be generated and sent in a meshed port

pairing from one vlan to another. This will help to determine the capacity and latency of the Device Under Test (DUT).

2. Launch the Spirent TestCenter Application and connect to the chassis.


5

3. In the navigation box, on the left, select Card Setup Port Setup.

4. Reserve the ports that are to be used, set the MAC Addresses for each port and change the Port

Speed from 100M to 1000M. If desired, create an Alias for the port.


6

5. In the navigation window select Card Setup IP Config.

6. Configure each port with the correct IP Address, Gateway and Prefix Length.


7

7. In the navigation window select Traffic Streams.

8. Click the Traffic Wizard button; this will open a new window to allow for easy configuration of the traffic steams.


8

9. Select All Ports for the Source and Destination to create a Mesh port pairing. Once completed, click Next.


9

10. The default values are fine; click the Finish button.

11. For each port a single stream should have been created.


10

12. The stream load is initially set to 10% of the capacity of the bandwidth. This needs to be increased to a value of 100%. Select Traffic Transmit Ports and change the Load value for the correct port to 100%. This can be done in two ways; either type the value directly into the box or click the “...” that appears when selecting the box and then enter in a Fixed value of 100.

13. For a more realistic test change frame sizes to random. Click inside the Frame Size Box and select the “…” that appears. This will open a new window. Select the Random radio button and then click OK.

14. Click the Results Collection button that appears on the tool bar.


11

15. In the Results Collection window select All Streams for both Display Charts and Display Counters and then click OK.

16. Select Flap Schedule from the navigation box and check the Enable Flapping box.


12

17. The test should run for 120 seconds. Select the Add Step button and in the Option section select the None radio button for the Final Step. The results should look like the below image.

18. Highlight Step 1 Mode: Blocking and then click the Add Event button. A new window will appear. In this new window select Stop Test and click finish.


13

19. Highlight the Time Interval 30 sec line in the Flap Schedule. Next, select the Edit Time button this will cause a new window to appear. Change the time Interval to 120 and click OK.

20. The results in the Flap Schedule window should look like the below image.

21. The test can now be started. Select the green triangle in the upper left of the menu bar. This will open up a new window.

22. The default values are okay; select the Run button to start running the test.


14

23. Once the test has started from the drop down menus in the results window select Port Counters and Streams. These will show the traffic being sent, received, and lost frames and the average latency while the test is being performed.

24. Once the test has completed change the left drop down menu to Port Counters and in the right drop down menu to Port Pair Results in the Results window.

25. In the Port Pair Results window locate % Loss. If this value is less than 2% the test has

successfully been completed. If this value is greater than or equal to 2% the Stream Load % needs to be decreased and the test needs to be rerun, go back to step 13 for how to do this.

26. In the Port Counter window locate the Rx Bytes for each port. With the total number of bytes that was received it is possible to calculate the actual transmission speed of the DUT. Using a simple formula will convert the total Rx Bytes to Mbps. The formula is as follows:

( ) ( )[ ] 812010242 ××÷RxBytes


15

27. The DUT used in creating this methodology had a packet loss value less than 0.5% and Rx Byte value of 13389886380 for both ports. Using the Rx Byte value in the formula supplied a value of 851.3 Mbps is return. Taking this value and then dividing it by 8, as each IPTV Stream can take up to 8 Mbps, will give a close value of the number of IPTV users that the DUT could handle.


16

Number of Multicast Streams

Associated Documentation • RFC 1112: Internet Group Management Protocol, Version 2 • RFC 3376: Internet Group Management Protocol, Version 3

Objective This test validates the number of Multicast streams the Device Under Test (DUT) is able to handle.

Overview A single multicast group will be created. This multicast group will then stream data to a number of hosts. The first iteration will only stream to a single host to verify multicast is correctly working on the DUT. Once this has been verified, the number of hosts is increased and the test is run again. A binary search is used to help determine the number of multicast steams the DUT is able to handle.

Setup


17

1. Configure the Device Under Test (DUT) to use at least two vlans. Also, configure the DUT to support Multicast. Multicast traffic will be generated and sent from one vlan to another. This will help to determine the approximate number of Multicast streams the DUT is able to handle.

2. Repeat steps 2 – 7 in the Capacity Test.

3. From the navigation windows select Card Setup Protocols.

4. Enable IGMP/MLD on both test ports.

5. From the navigation window select IGMP&MLD Groups.


18

6. Right click on the second port and select New Group.

7. A new group should be added, and the resulting window should appear like the image below. Only one group will be used in this initial test, so the default values are okay.


19

8. From the navigation window, select Traffic Streams.

9. Select the Traffic Wizard button. This will open up a new screen.

10. Select the Multicast Host as the Source and on the remaining port select Multicast Group as the Destination. Once this has been completed click Next.


20

11. The defaults in this screen should be okay. Press Finish to create the stream.

12. A single resulting stream should now be present.


21

13. The test can now be started. Select the green triangle in the upper left of the menu bar. This will open up a new window.

14. The default values are okay select the Run button to start running the test.

15. Check to make sure that traffic is actually being sent. To do this, in the results window select Port Counter from the left drop down menu. On the right drop down menu select IGMP Counters.

16. Open a console window to the DUT and verify that both vlans the multicast group is seen. If it is not seen on both vlans the DUT needs to be reconfigured.


22

17. This test can be stopped now. Press the red stop button at the top of the screen. If a warning

window opens, press OK and continue.

18. To determine the number of multicast streams the DUT is able to handle more multicast hosts will need to be created. From the navigation window select IGMP&MLD Hosts.


23

19. The number of hosts needs to be increased from 1 to 100. Select the first port and right click to open a menu. From this menu select Duplicate.

20. A new window will appear. Change the value from 1 to 99 this will create 99 new hosts. Once finished press OK.

21. Notice how each host has the same IP address. Each host needs to have its own unique IP, press the Apply Default Value button to make each Host IP unique.


24

22. From the navigation window select Traffic Streams.

23. Select the Traffic Wizard Button again.


25

24. Select All IGMP/MLD Hosts as the source port. As the Destination port select the Multicast Group under the second port. Make sure these are the only ones checked. If others are checked uncheck them and then press Next.

25. The default values in the new window are okay. Press Finish to continue and answer Yes to Deleting existing streams question. The traffic streams window should now contain 100 traffic streams. It should look similar to the below image.

26. Start this iteration of the test the same way the last one was started.

27. Verify on the DUT that 100 multicast streams are present. If the DUT is not dropping any multicast streams, and is able to handle the current number of streams, increase the number of multicast streams. Though, if the DUT is not able to handle the number of multicast streams, the number of streams must be decreased. Go back to Step 19 and repeat the test with a new amount of hosts. Do not repeat the test if the number of multicast streams would be greater than the available number of IPs.

28. The result from this test is the number of multicast streams the DUT is able to handle. This is an

important value as IPTV channels are streamed using multicast. Each device in the network must be able to handle the multicast demand put on it from the streaming of channels.


26

Channel Changing Behavior

Associated Documentation • RFC 1112: Internet Group Management Protocol, Version 2 • RFC 3376: Internet Group Management Protocol, Version 3 • ETSI TR 10129: Digital Video Broadcasting Guide Lines • IEEE 802.1Q: Virtual LANS

Objective Determine how the changing of channels affects the network.

Overview A TCL script is used that will join and leave different multicast groups. The TCL script will output the results in to a comma separated values (csv) file. This test will help determine how changing between different channels affects the network. As a channel can require up to 8 Mbps, changing channels puts a huge stress on the network as channel overlapping happens.

Setup


27

1. Configure the Device Under Test (DUT) as needed. Make sure the DUT supports 802.1q so that sub-vlans can be created on each port. Please reference Appendix A for a sample DUT configuration file. Make sure that when the Spirent TestCenter software was installed that automation and TCL were installed. The easiest way to determine if automation was installed is by checking for the STC_AUTOMATION_HOME environment variable.

2. Open up a command prompt and change to the directory where the scripts are located.

3. Run the script by issuing the command: tclsh84 <script name>. Once the script has started some output should be seen.

4. During the running of the test results will scroll by, these results are also being stored in a csv file. Once the test has completed open the file. The results file is located in a subdirectory called Results in the directory the script is located in.


28

5. When opening the csv file the first thing noticed is that it displays a summary of the test configuration.

6. The csv file contains a lot of information. The Statistics: IPTV Clients and the Statistics: IPTV Client

View Profile are the two tables of interest. The IPTV Client table will provide all the information about the multicast channel streams that are needed while the IPTV Client View Profile table provides latency values.

7. The important values in the IPTV Client table are the Channel Changes, Failed Joins, Duplicated Joins, and Avg Change Latency. If there are any Failed Joins rerun the test to double check the results. If it happens again, make sure multicast as been configured correctly on the DUT. If multicast has been correctly configured decrease the number of Channel Changes in the script and rerun the test.


29

8. In the IPTV Client View Profiles the Avg Change Latency, Avg Join Latency, Avg Leave Latency and Ave Overlap are the values of interest. As with all latency values, the lower these values are the better they are. The Change Latency is the time it takes to leave the current channel and join the new one. The Join latency is how long it takes to join the new channel, while the Leave Latency is the time it takes to leave the current channel. The Overlap is the time that both channels are being streamed to the viewer.

9. Once a successful run has been completed, increase the number of clients the script uses and the length of the test. Increasing the number of clients and length of the test will provide a truer real world scenario.

10. Other IPTV TCL scripts can also be used by following the same procedures as mentioned above.

Different TCL scripts will provide different results and values.


30

Video Quality Test

Associated Documentation

• ETSI TR 10129: Digital Video Broadcasting Guide Lines

Objective Determine the VFactor and Mean Opinion Score (MOS) scores of an Internet Protocol Television (IPTV) multicast video stream.

Overview With the future of television going towards IPTV it is necessary to determine if the current infrastructure could handle the load of IPTV. As each IPTV stream could be up to 8 Mbps this will put a very heavy load on different parts of the network. If just even 0.5% of packet loss occurs the image becomes distorted and not pleasant to view. This is why it is very important to determine the MOS and VFactor scores. To determine the MOS and VFactor scores the Spirent TestCenter chassis needs to have the VQM bundle installed for use on its ports. A multicast stream of video will be streamed on a private network with a port that has the VQM bundle installed. The Video Test System Controller (VTSC) will collect the data results from the test. A separate computer system will be needed to be able to view the results from the VTSC.

Setup


31

1. Place the VQM Bundle in C:\Program Files\Spirent Communications\Spirent TestCenter\Firmware

folder. 2. Start the Spirent Administration Application and connect to the Spirent TestCenter chassis that

will be used to perform this test.

3. Select the Firmware button that is located at the top of the Administration Application. You should see a listing of firmware that can be installed on the left hand side.

4. Select the vqm package from the Install Package list. Wait several seconds while it checks to see if the firmware is already installed on the cards in the chassis. Once this has completed select the Port Groups you wish to install the vqm firmware on.

5. As you probably wish to leave the psb firmware available for use on those Port Groups make sure the Remove old version is not selected and then click Install.


32

6. Once the status changes to Installed, select the Home button and then disconnect from the chassis. The Administration Application can be closed and exited now.

7. Open a web browser and connect to “http://<ip address of Spirent Video Test System>:8080/webcenter/” the user name is “root” and the password is “spirent”. Press the login button to login to the Spirent Video Test System and a new window should appear.

8. Select VQM Discover. This will allow you to enter the IP address of your Spirent TestCenter chassis and discover ports that have VQM.


33

9. Enter the IP address of the Spirent TestCenter chassis and press Start Discovery. If a message

appears about IP conflicts, press the yes button to continue with the discovery. In the Auto Discovery Event Messages box messages should appear saying a VQM has been discovered.

10. Once VQM ports have been discovered, select VQM Test Setup


34

11. A new window should be created, this new window will allow for the configuration and running of the Video Quality Test.


35

12. Select the New Scenario Button. A new window titled New Scenario Setup will appear. Fill in the Test Scenario field with a name for the test and give it a brief description in the Description field. Change the test Duration to 60 and as we wish to have results uploaded every 10 seconds Result uploads can stay at 10. Once completed select the Save Button.

13. The main configuration window should look similar to the image below.


36

14. In the Add New Application area of the window, fill in a meaningful Name and Description. The Type is not able to be changed as RTP is the only one available. Select Save & Add New Application.

15. Select Yes in the window that appears.

16. In the List of Applications for this Scenario the name of the Application should be visible. Changes need to be made to this Application. Select the Edit App button and a new window will appear.


37

17. Select the Add New Group button. In the new window which appears enter in a Group name and make sure Session Type is set to UDP_Multimedia then press Ok.

18. In the RTP Group List an entry should be created. Next, the multicast stream needs to be added. Select Add Channel.


38

19. Enter a Channel Name and change the Test Duration to 60 as the test will run for one hour. Change the sample period to 10. Also, if needed change the Listen Port to the port the multicast stream will be on.

20. In the lower part of the same window, use the drop down menu and select 224.1.1.1 and press the Add Multicast button. An entry is the List of Multicast Addresses will appear.

21. As the chance is that 224.1.1.1 is not the multicast IP you are using select the Edit Multicast button. Enter the correct Multicast IP and press the Ok button.


39

22. In the List of Multicast Addresses the IP address should change. Select the Save button, and the window should close saving all the changes.


40

23. Select the Save Application button. This window does not close automatically, once it has been saved close the window manually.

24. Once back to the original configuration window select the Save Scenario button.


41

25. Before the scenario can be started the multicast stream must first be started. Once the multicast stream has started the scenario can be run. Press the Start Scenario button to start.

26. When prompted about running the scenario press the Yes button.

27. A new window should appear. In this window you will notice the Test Status. Once the status has changed to UPDATED_DB results are able to be viewed.


42

28. On the main page, go to Results Manager VQM Results. This will open a new window that will allow you to browse all the results of each test.

29. One the left side, locate your currently running test. It will be located under the Scenario name, then the Application name, and finally the starting time of the test. Select the computer icon once it is visible.

30. In the frame that loads, select the Program Info link. This will cause a new frame below to load.

31. Locate the Pid for MPEG-2 Video and select this. This will cause a new window to open.

32. From this window you are able to view all the results. Using the drop down menu different results can be viewed. Also, you are able to view the results in 15 min increments.


43

33. To view the MOS score in graph format choose DEFAULT_MPEG2TS_AUDIO_GRAPH_template from the drop down menu.


44

34. Three different result windows are available for VFactor, the first one is DEFAULT_MPEG2TS_VFACTOR_GRAPH_template. The second and third are DEFAULT_Content_Related_Template and DEFAULT_Network_Related_Template respectively. These three charts and graphs will provide you with the VFactor rating, I, B and P Frame counts, and some network statistics.


45

35. This test can be rerun with using different parameters for the video quality. When adding the multicast stream, edit the tunable parameter set to change some of the quality values. Once saved, it can be used for different tests too.

36. The VFactor scale is a range from 0 to 5. A VFactor rating of 0 is the worst possible rating, while a VFactor rating of 5 is the best rating possible. The test run in creating this methodology had a VFactor of 4.9, as can been seen in the images in step #34, this is an excellent VFactor rating.


46

Glossary

B Frames (Bi-directional or Bi-predictive frames) One of the three types of major frames found in video compression designs. This frame requires a prior decoding of other frames in order to be decoded itself. This frame may contain both image data and motion picture displacements.

Dot1q

(IEEE 802.1Q) A way to allow multiple bridged networks to transparently share the same physical link without having leakage between networks.

DUT

(Device Under Test) A device such as a router or switch that is going to be tested under different scenarios to determine its performance.

I Frames

(Intra frames) One of the three types of major frames found in video compression designs. An I Frame is a frame that is coded without and reference to any other frames besides itself. This type of frame usually requires more bits then the others.

IGMP

(Internet Group Management Protocol) IGMP is used by IP hosts and multicast routers to establish group memberships. IGMP is a very integral part of the IP multicast specifications.

IPTV

(Internet Protocol Television) Digital television is delivered to subscribing customers using the Internet Protocol (IP) over a broadband connection. IPTV is often provided with Video on Demand (VoD) and can also include Triple Play.

MOS (Mean Opinion Score) A motion picture abbreviation which indicates that a film segment does not have a synchronous audio track.

MLD

(Multicast Listener Discovery) Used by IPv6 multicast hosts and routers to discover listeners of a specific multicast group. MLD is very similar to IGMP in IPv4.

Multicast A way to send information to multiple destinations from a single source in a very efficient way. A single message can be sent simultaneously to several computers from one. A range of IP address has been reserved for multicast, 224.x.x.x to 239.x.x.x.

P Frames

(Predicted frames) One of the three major types of frames found in video compression designs. P Frames requires previously decoding of frames in order to be decoded. P Frames may contain both image data and motion vector displacements or a combination of both. P Frames are also able to reference previous frames in decoding order.

VFactor

A measurement of video quality that looks at packet impairments, program clock and I, B, and P frames for a more accurate quality measurements and frame-based statistics.


47

VLAN (Virtual Local Area Network) A network of computers that act as if they are connected to the same wire, even though they may be connected to different parts of the LAN. Several VLANs are able to coexist on a single physical switch.

VoD

(Video on Demand) Allows users to select and watch video content over a network. VOD systems either stream or download the content.

Triple Play

An industry term used to describe three types of service; high-speed Internet, television and telephone.


48

Appendix A Below is a sample cisco configuration to help in the setup of the DUT.

Current configuration : 1714 bytes ! version 12.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname R1 ! ! ip subnet-zero ! ! ! ip multicast-routing ! ! ! ! ! ! ! ! ! !


49

! mta receive maximum-recipients 0 ! ! ! ! interface FastEthernet0/0 description MGT PORT ip address 110.1.0.1 255.255.255.0 ip pim sparse-mode no ip route-cache ip igmp version 3 no ip mroute-cache speed 100 full-duplex pppoe enable ! interface FastEthernet0/0.1000 encapsulation dot1Q ip address 1.0.0.1 255.255.255.0 ip pim sparse-mode no ip route-cache no ip mroute-cache ! interface FastEthernet0/1 no ip address shutdown duplex auto


50

speed auto ! interface FastEthernet1/0 ip address 111.1.0.1 255.255.255.0 ip pim sparse-mode no ip route-cache ip igmp version 3 no ip mroute-cache speed 100 full-duplex ! interface FastEthernet1/0.1100 encapsulation dot1Q 1100 ip address 1.1.0.1 255.255.255.0 ip pim sparse-mode no ip route-cache no ip mroute-cache ! interface FastEthernet1/0.1101 encapsulation dot1Q 1101 ip address 1.1.1.1 255.255.255.0 ip pim sparse-mode no ip route-cachelogin: no ip mroute-cache ! interface FastEthernet1/0.1102


51

encapsulation dot1Q 1102 ip address 1.1.2.1 255.255.255.0 ip pim sparse-modes no ip route-cache no ip mroute-cache ! interface FastEthernet1/0.1103 encapsulation dot1Q 1103 ip address 1.1.3.1 255.255.255.0 ip pim sparse-mode no ip route-cache.168.0.100 no ip mroute-cache ! interface FastEthernet1/1 172.16.1.243 no ip address shutdown ! ! ! ! call rsvp-sync ! ! mgcp profile default ! dial-peer cor custom !


52

! ! ! line con 0 line aux 0 line vty 0 4 privilege level 15 no login ! ! end


53

Appendix B

Below is the TCL used in creating this methodology.

# Spirent TestCenter Automation Script # Generated from IPTV Test Application # Source the SpirentTestCenter IPTV Test API source "$::env(STC_AUTOMATION_HOME)/samplescripts/IPTV/iptv_api.tcl" proc main {} { # Configure global test parameters stciptv::config -testName IPTV_TEST -testDuration 10 -protocolType MULTICAST_TYPE_IGMP_V2 -joinThreshold 300 -leaveThreshold 3000 -channelIPStart 239.0.0.1 -channelCount 64 -udpSrcPort 3357 -udpDstPort 3358 # Configure the multicast source ports stciptv::createPort -chassis 10.13.16.52 -slot 1 -port 4 -role IPTV_SOURCE_PORT -portName mcSourcePort0 -macAddr 0:0:2:0:0:5 -ipAddr 110.1.0.2 -gateway 110.1.0.1 -portMode PORT_MODE_COPPER -autoNegot AUTONEG_ENABLE -speed 100MBPS -duplex FULL_DUPLEX -flowControl FALSE # Configure the multicast client ports stciptv::createPort -chassis 10.13.16.52 -slot 1 -port 6 -role IPTV_CLIENT_PORT -portName mcClientPort0 -macAddr 0:0:2:0:0:7 -ipAddr 111.1.0.2 -gateway 111.1.0.1 -portMode PORT_MODE_COPPER -autoNegot AUTONEG_ENABLE -speed 100MBPS -duplex FULL_DUPLEX -flowControl FALSE # Create the channel profiles # Channel profiles reference created ports using the -portName option stciptv::createChannelProfile -profileName {Source 1} -portName mcSourcePort0 -count 64 -vlanEnable TRUE -vlanID 1000 -vlanIDStep 0 -vlanPri 0 -srcMacAddr 0:0:2:0:0:5 -srcIp 1.0.0.2 -srcIpPrefixLen 24 -srcIpIncEnable FALSE -tos 0 -load 0.25 -frameSize 1000 # Create the view profiles stciptv::createViewProfile -profileName NetSurfers0 -zapBehavior ZAP_ONLY -zapsBeforeView 1 -viewDuration 1000 -zapDirection UP -zapIntervalType LEAVE_TO_LEAVE -zapInterval 1000 -startDelay 1000 -leaveJoinDelay 300 -channelStart 1 -channelEnd 64 -channelStep 1 -initChannel 1 -initChannelStep 1 # Create the client profiles stciptv::createClientProfile -portList "mcClientPort0" -viewProfileList "NetSurfers0" -clientsPerPort 4 -vlanEnable TRUE -vlanID 1100 -vlanIDStep 1 -macAddr 0:10:95:2:0:1 -macAddrStep 0:0:0:0:0:1 -prefixLen 24 -ipAddr 1.1.0.2 -ipAddrStep 0.0.1.0 # Start the test stciptv::start stciptv::startCapture mcClientPort0 CAPT_TYPE_HW # Wait for the test to complete stciptv::waitForTestToComplete


54

stciptv::stopCapture mcClientPort0 # Stop the test stciptv::stop # Clear the IP TV test stciptv::reset } if [catch { main } msg] { puts "Error: $msg" puts "==========================================" puts "$::errorInfo" }

© 2005 Spirent Communications, Inc. All of the company names and/or brand names and/or product names referred to in thisdocument, in particular the name “Spirent” and its logo device, are either registered trademarks or trademarks pending registrationin accordance with relevant national laws. All rights reserved. Specifications subject to change without notice.

P/N 79-000126 Rev A, 9/05

Spirent Communications is a worldwide provider ofintegrated performance analysis and service assurancesystems for next-generation network technologies. Our solutions accelerate the profitable developmentand deployment of network equipment and services byemulating real-world conditions in the lab and assuringend-to-end performance of large-scale networks.

Spirent performance analysis solutions includeinstruments and systems that measure and analyze the performance of network equipment, particularlythe devices that route voice and data messages to theirdestination. Our service assurance solutions includeremote test, fault and performance management systemsthat let network service providers quickly identifynetwork faults and monitor real-time performance.

Spirent’s integrated performance analysis and serviceassurance solutions enable our customers to morerapidly develop and certify new devices, lowering thecost of widespread deployment and operation of newnetworking services.

Spirent Communications is a wholly ownedsubsidiary of Spirent plc, an internationalnetwork technology company.

Spirent Communications26750 Agoura RoadCalabasas, CA 91302 USATel: +1 [email protected]

Sales and InformationAmericasTel: +1 [email protected]

Europe, Middle East, AfricaTel: +33 1 [email protected]

Asia PacificTel: [email protected]

www.spirentcom.comwww.spirentcom.com/tmj

Test Methodology Journal Test Methodolo - Spirent Support

Documents

Transcript of Test Methodology Journal Test Methodolo - Spirent Support