Spirent Test Center – Setting up basic

BGP sessions, advertising routes, and sending

traffic between the routes

____________________________________________________________________

 

To Print or View in Word format, click here

 

Content

 

Introduction

Components Used

Configuration Summary

Test Topology

Connect to the Spirent TestCenter chassis and setup two ports

Enable BGP protocol and advertise routes with Route Generator

Use Traffic Wizard to create traffic between the BGP routes

Check counters in real-time and after the test stops

____________________________________________________________________

 

Introduction

The purpose of this document is to provide the user step-by-step instructions to

configure BGP sessions, advertise routes, and send traffic to the advertised routes.

 

Components Used

  • DUT configured with BGP connected to two Ethernet Spirent ports
  • Spirent TestCenter 9U chassis with two Ethernet interfaces
  • Spirent TestCenter application software

 

Configuration Summary

  • Connect to the Spirent TestCenter chassis and setup two ports
  • Enable BGP protocol and advertise routes with the Route Generator
  • Use Traffic Wizard to create traffic between the BGP routes
  • Check counters in real-time and after the test stops

 

Test Topology

 

 

Connect to the Spirent TestCenter chassis and setup two ports

 

Step#1: Click Actions, Connect

 

 

Step#2: Click Active on the ports and hit Apply

 

NOTE: Apply button must be clicked after every config change

 

 

 

Step#3: If link does not come up, double check the Media Type and Auto Negotiation settings

 

 

Step#4: Right-click on any of the port LEDs and use the Link or Unlink option to check if you are connected to the right port on the DUT (useful feature if working remote from physical setup)

 

 

Step#6: Go to DUT and ping the Spirent port

 

Step#5: Go to the IP Config section, configure the IP address of the ports, and click Apply

 

 

 

Enable BGP protocol and advertise routes with Route Generator

 

Step#7: Go to the Protocols section and enable OSPF on both ports

 

 

Step#8: Go to BGP, Sessions and configure the Tester and SUT AS #. Doublecheck the IP Addresses

 

 

Step#9: Go to BGP, Routes. Change the following:                      

-          Total Networks 100

-          Distribution=Even

-          Prefix Length Start 32

 

 

Step#10: Click Range and set the Start IP .

Click OK

 

 

Step#11: Note the routes were automatically configured for each BGP session

 

 

Use Traffic Wizard to create traffic between the BGP routes

 

Step#12: Go to Streams and click on Traffc Wizard

 

Step#13: Select All BGP Routes on both sides and click on Next

 

 

Step#14: Click Finish

 

 

Step#15: Note the Streams that are configured

 

 

Step#16: View and modify the frame with the PDU editor by right-clicking on any Stream and selecting Edit Frame

 

 

Step#17: Modify the frame with the PDU editor (optional)

 

 

Step#18: Click the Start Test and set the Tx Load to 500 fps. Click Run

 

 

Check DUT for BGP neighbors and routes advertised

 

 

Check counters in real-time and after the test stops

 

Step#19: Select Port Rates and Port Counters from the drop-down menu and note the Signature Frames sent and received

 

 

Step#20: Enable per-stream stats by clicking on Result Collection and selecting All Streams. Click Ok

 

 

Step#21: Click Apply and select Streams from the drop-down menu

 

 

Step#22: Set unique loads for each stream by going to Transmit Ports, clicking in the Load section, and set the Mode to Per Stream. Click OK.

 

 

Step#23: Set unique frame size for each stream by going to Transmit Ports, clicking in the Frame Size section, and set the Mode to Per Stream. Click OK.

 

 

Step#24: Set the Frame Size and Rate for each stream and click Apply

 

 

Step#25: Select Streams from the drop-down menu and note the Tx Rate for each stream

 

NOTE: the % Loss is based on the run-time Tx/Rx rate and not the actual loss. The Lost Frames and % Loss will display the correct results after stopping the test

 

 

Step#26: Click the Stop Test button and wait for the hardware to send results to the GUI

 

NOTE: Always note the status of the GUI in the lower left-hand corner. The amount of time for the test to stop will vary depending on the size and complexity of the test

 

 

Step#27: After the test stops, select Detailed Stream Statistics from the drop-down menu and review the Lost Frames, % Loss, and Latency numbers