OTG with Ixia L23 Hardware: back-to-back setup

Overview

This example demonstrates how the OTG API can be used to control Keysight/Ixia L23 Network Test Hardware. The same Keysight Elastic Network Generator ixia-c-controller that serves as the OTG API Endpoint for Ixia-c software test ports can be used with the hardware test ports. Such deployment model requires to use ixia-c-ixhw-server container image that provides an interface between the controller and the hardware test ports. See the diagram below that illustrates the components of such setup:

Prerequisites

• Access to Keysight Elastic Network Generator images. Read more in KENG.md

• Keysight Ixia Novus or AresOne Network Test Hardware with IxOS 9.20 or higher

• Linux host or VM with sudo permissions and Docker support. Here is an example of deploying an Ubuntu VM otg using multipass:

  multipass launch 22.04 -n otg -c4 -m8G -d32G
  multipass shell otg
  

• Docker

  sudo apt update && sudo apt install docker.io -y
  sudo usermod -aG docker $USER
  

• Python3 (version 3.9 or higher), PIP and VirtualEnv

  sudo apt install python3 python3-pip python3.10-venv -y
  

  * Go version 1.19 or later

  sudo snap install go --channel=1.19/stable --classic
  

• git and envsubst commands (typically installed by default)

  sudo apt install git gettext-base -y
  

Install components

1. Install docker-compose

   sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" \
   -o /usr/local/bin/docker-compose && \
   sudo chmod +x /usr/local/bin/docker-compose
   

2. Make sure /usr/local/bin is in your $PATH variable (by default this is not the case on CentOS 7)

   cmd=docker-compose
   dir=/usr/local/bin
   if ! command -v ${cmd} &> /dev/null && [ -x ${dir}/${cmd} ]; then
     echo "${cmd} exists in ${dir} but not in the PATH, updating PATH to:"
     PATH="/usr/local/bin:${PATH}"
     echo $PATH
   fi
   

3. Clone this repository

   git clone -b keng-eval --recursive https://github.com/open-traffic-generator/otg-examples.git
   cd otg-examples/hw/ixhw-b2b
   

Diagnostics

To collect diagnostics logs from all the components of the lab, run:

../../utils/collect-ixia-c-hw-logs.sh

It will create a logs-DATE.tar.gz file you can share with Keysight for troubleshooting.

TIP. Use make logs if you have make on your system

Deploy Keysight Elastic Network Generator

1. Launch the deployment

   sudo -E docker-compose up -d
   

2. To make sure all the containers are running, use

   sudo docker ps
   

   the list of containers should include:

   • ixhw-b2b_ixia-c-controller_1
   • ixhw-b2b_ixia-c-ixhw-server_1

3. Initialize environment variables with locations of Ixia L23 hardware ports. Replace ixos_ip_address, slot_number_X, port_number_X with values matching your equipment.

   export OTG_LOCATION_P1="ixos_ip_address;slot_number_1;port_number_1"
   export OTG_LOCATION_P2="ixos_ip_address;slot_number_2;port_number_2"
   

   For example, if IxOS management IP is 10.10.10.10 and you need to use ports 14 and 15 in the slot number 2:

   export OTG_LOCATION_P1="10.10.10.10;2;14"
   export OTG_LOCATION_P2="10.10.10.10;2;15"
   

Run OTG traffic flows with Python snappi library

1. Setup virtualenv for Python

   python3 -m venv venv
   source venv/bin/activate
   pip install -r requirements.txt
   

2. Run flows via snappi script, reporting port metrics

   ./snappi/otg-flows.py -m port
   

3. Run flows via snappi script, reporting port flow

   ./snappi/otg-flows.py -m flow
   

Cleanup

To stop the deployment, run:

sudo docker-compose down

OpenConfig Feature Profiles B2B test

Deploy Keysight Elastic Network Generator

1. Launch the deployment

   sudo -E docker-compose -p keng1 --file fp.compose.yml --file fp.compose.ports.yml up -d
   

2. To make sure all the containers are running, use

   sudo docker ps
   

   the list of containers should include:

   • ixhw-b2b_ixia-c-controller_1
   • ixhw-b2b_ixia-c-ixhw-server_1
   • ixhw-b2b_ixia-c-gnmi-server_1

3. Initialize environment variables with locations of Ixia L23 hardware ports. Replace ixos_ip_address, slot_number_X, port_number_X with values matching your equipment.

   export OTG_LOCATION_P1="ixos_ip_address;slot_number_1;port_number_1"
   export OTG_LOCATION_P2="ixos_ip_address;slot_number_2;port_number_2"
   

   For example, if IxOS management IP is 10.10.10.10 and you need to use ports 14 and 15 in the slot number 2:

   export OTG_LOCATION_P1="10.10.10.10;2;14"
   export OTG_LOCATION_P2="10.10.10.10;2;15"
   

4. Create an ONDATRA binding file otgb2b.binding by using otgb2b.template as a template and substituting OTG port locations using the environmental variables initialized in the previous step.

   cat otgb2b.template | envsubst > otgb2b.binding
   export OTGB2B_BINDING="$(pwd)/otgb2b.binding"
   

Run FeatureProfiles OTG HW back-2-back test

1. Clone FeatureProfiles fork from Open Traffic Generator org. The back-2-back test we're going to use is published under the static branch we need to clone:

   git clone -b static --depth 1 https://github.com/open-traffic-generator/featureprofiles.git fp-static
   

2. Run FeatureProfiles OTG HW B2B test

   cd fp-static/feature/experimental/otg_only
   go test -v otgb2b_test.go -testbed otgb2b.testbed -binding "${OTGB2B_BINDING}"
   cd ../../../..
   

Multi-seat deployment

If you need to support multiple concurrent seats (simultaneous tests) on the same VM, it is possible to launch several parallel instances of Keysight Elastic Network Generator.

1. What you need for that is to choose a set of different TCP ports that ixia-c-controller and ixia-c-gnmi-server would be mapped to on the host. As an example, see the file fp.compose.ports2.yml. You would also need start the deployment using a non-default project name, so that the second set of containers would run over a dedicated network.

   sudo -E docker-compose -p keng2 --file fp.compose.yml --file fp.compose.ports2.yml up -d
   

2. Now create a second ONDATRA binding file, for example otgb2b.binding2:

   cp otgb2b.binding otgb2b.binding2
   # change TCP ports for both otg and gnmi targets
   # change port name strings to use different IxHW ports
   vi otgb2b.binding2
   export OTGB2B_BINDING="$(pwd)/otgb2b.binding2"
   

Now you're ready to run the two parallel tests via the same VM using two different binding files.

Cleanup

To stop the deployment, run:

sudo docker-compose -p keng1 --file fp.compose.yml down
sudo docker-compose -p keng2 --file fp.compose.yml down