Virtual Topologies

CSIT HoneyComb functional tests are executed in VM-based virtual topologies created on demand using VIRL simulation platform contributed by Cisco. VIRL runs on physical baremetal servers hosted by LF FD.io project.

All tests are executed in two-node virtual test topology shown in the figure below.


SUT (System Under Test) is a VM running Ubuntu Linux (or Centos, depending on the test suite), TG (Traffic Generator) is another VM running Ubuntu Linux. SUT VMs run HoneyComb management agent and VPP in Linux user-mode as a combined DUT (Device Under Test). TG runs Scapy application as a packet Traffic Generator. Virtual connectivity between SUT and TG is provided using virtual NICs using VMs’ virtio drivers.

Functional Tests Coverage

CSIT-18.07 includes following HoneyComb functionality tested in virtual VM environment:

Functionality Description
  • CRD for low-level classifiers: table and session management, interface assignment.
  • Configure up to 2 classify tables.
  • Configure up to 2 classify sessions on one table.
  • Assign classify session to a physical interface.
  • Remove tables, sessions, interface assignments.
  • Test case count: 9.
  • CRD for high-level classifier.
  • MAC + IP address classification.
  • IPv4, IPv6 address classification.
  • TCP, UDP, ICMP, ICMPv6 protocol and next-header classification.
  • port number classification.
  • ICMP, ICMPv6 code and type classification.
  • Test case count: 15.
Basic interface management
  • CRUD for interface state.
  • ipv4/ipv6 address, ipv4 neighbor, MTU value.
  • Test case count: 14.
Border Gateway Protocol
  • CRUD and functional tests for BGP.
  • Configure peers and routes
  • Check interactions with another BGP peer.
  • Test case count: 13.
DHCP Relay
  • CRD for DHCP relay feature.
  • Configure DHCP Relays.
  • IPv4 and IPv6 variants.
  • Test case count: 4.
Honeycomb Infractructure
  • Configuration persistence.
  • Netconf notifications for interface events.
  • Netconf negative tests aimed at specific issues.
  • Netconf/Restconf northbound over IPv6.
  • Test case count: 12.
  • CRUD for L2 Bridge-Domain, interface assignment.
  • Create up to two bridge domains with all implemented functions turned on: flooding, unknown-unicast flooding, forwarding, learning, arp-termination.
  • Assign up to two physical interfaces to a single bridge domain.
  • Remove interface assignments, remove bridge domains.
  • Test case count: 5.
  • CRD for L2-FIB entries.
  • Create 4 FIB entries: one of each for filter/forward, static/dynamic combinations.
  • Remove FIB entries.
  • Test case count: 7.
  • CRD for Lisp: mapping, locator set, adjacency, mapresolver.
  • Toggle Lisp feature status.
  • Configure and delete Lisp mapping as local and remote.
  • Configure and delete Lisp adjacency mapping.
  • Configure and delete Lisp map resolver, proxy ITR.
  • Test case count: 18.
  • CRUD for LISP GPE mappings.
  • Toggle Lisp GPE feature status.
  • Configure Lisp GPE mappings.
  • Traffic test verifying encapsulation.
  • Test case count: 12.
  • CRD for NAT entries, interface assignment.
  • Configure and delete up to two NAT entries.
  • Assign NAT entries to a physical interface.
  • Test case count: 6.
  • CRD for NSH maps and entries, using NSH_SFC plugin.
  • Configure up to 2 NSH entries.
  • Configure up to 2 NSH maps.
  • Modify and delete NSH maps and entries.
  • Test case count: 8.
  • CRD for provider backbone bridge sub-interface.
  • Configure, modify and remove a PBB sub-interface over a physical interface.
  • Test case count: 8.
  • CRD for traffic policing feature.
  • Configure Policing rules.
  • Assign to interface.
  • Test case count: 6.
Port mirroring
  • CRD for SPAN port mirroring, interface assignment.
  • Configure SPAN port mirroring on a physical interface, mirroring.
  • up to 2 interfaces.
  • Remove SPAN configuration from interfaces.
  • Test case count: 14.
  • CRD for proxyARP feature.
  • Configure proxyARP.
  • Assign to interface.
  • Test case count: 3.
  • CRD for Neighbor Discovery Proxy.
  • Configure ProxyND6 feature on interface.
  • Test case count: 4.
  • CRD for routing.
  • Configure single-hop route.
  • Configure multi-hop routes.
  • Configure blackhole route.
  • IPv4 and IPv6 variants.
  • Test case count: 6.
  • CRD for Stateless Address AutoConfiguration.
  • Configure SLAAC feature on interfaces.
  • Test case count: 7.
  • CRUD for Vhost-user interfaces.
  • Create, modify and delete Vhost-user interface, as client and server.
  • Test case count: 8.
  • CRUD for VLAN sub-interface management.
  • Create VLAN sub-interface over a physical interface.
  • Toggle interface state separately for super-interface and sub-interface.
  • Configure IP address and bridge domain assignment on sub-interface.
  • Configure VLAN tag rewrite on sub-interface.
  • Test case count: 24.
  • CRD for VxLAN tunnels.
  • Create VxLAN interface.
  • Disable VxLAN interface.
  • Re-create a disabled VxLAN interface.
  • Test case count: 6.
  • CRD for VxLAN GPE tunnels.
  • Create VxLAN GPE interface.
  • Disable VxLAN interface.
  • Re-create a disabled VxLAN interface.
  • Test case count: 7.
  • CRUD for Tap interface management.
  • Create, modify and delete TAP interface.
  • Test case count: 3.

Total 219 Honeycomb functional tests in the CSIT-18.07.

Operational data in Honeycomb should mirror configuration data at all times. Because of this, test cases follow this general pattern:

  1. read operational data of the feature using restconf.
  2. read status of the feature using VPP API dump.
  3. modify configuration of the feature using restconf.
  4. verify changes to operational data using restconf.
  5. verify changes using VPP API dump, OR
  6. send a packet to VPP node and observe behaviour to verify configuration.

Test cases involving network interfaces utilize the first two interfaces on the DUT node.

Functional Tests Naming

CSIT-18.07 follows a common structured naming convention for all performance and system functional tests, introduced in CSIT-17.01.

The naming should be intuitive for majority of the tests. Complete description of CSIT test naming convention is provided on Test Naming.