A brief overview of the Test parameters

Introduction

This section will give a brief explanation of some of the tabs in the GUI. This example project has already filled these in for you to make the test easy to run.






Port Tab

The Port Tab. 

Here you will create IPv4 and/or IPv6 addresses. These will be the transmitters/ receivers of the test traffic configured in the later steps. 

In this tab, you can configure the following:

  • Port Name
  • MAC address
  • IP Configuration (Static address/ DHCP)
  • IP address 
  • Gateway (IPv4)/ Router Address (IPv6)
  • Netmask (IPv4) Prefix Length (IPv6)
  • NAT (IPv4) or Firewall (IPv6) 
  • enable VLAN Stack
  • set MTU for that port

Frame Tab

Creates a data frame.

  • For this test, we will use the default frame size → 1024
  • Later, you can adapt the size of the frames as needed as well as manually add MAC and IP addresses.
  • This is not recommended at this stage in order to run a basic test.


Frame Blasting Template

Frame blasting flows create a repeating flow of frames with a size determined in the previous step (1024).

  • This frame blasting flow (UDP) is an easy way to simulate traffic.
  • The physical load is the speed of the throughput. The speed in this demonstration is set at 838.4 kbps
  • You can adapt this to match the speed you expect from your system by using the Edit button on the top middle section of the screen.
  • The frame rate and interval are automatically calculated based on your choice of the physical load.

 

Flow

The source and destination of the frame blast are chosen here.

  • The flow tab is used to finalize the traffic flow by choosing which port is the source and which is the destination.
  • If you are making a downstream measurement, the source would be the server and the destination would be the client.

 

Run the test

Up to this point, there has been no real communication or connection with the ByteBlower server. Once we run the test, the server comes into the picture.

  • We will initiate the test by running a 'scenario'. The scenario uses the flow that we have created and we then just need to choose the duration of the test. In this example we have chosen 10 seconds; this is sufficient for this basic test.
  • As you use ByteBlower more, you can easily adapt the duration and start time of the test.

Introduction

Once the test is complete, open the ByteBlower report to see how the test performed.

You should see that 100% of the frames were received.