7.4.1. honeycomb¶
7.4.1.1. mgmt-cfg-acl-apihc-apivat-func¶
Honeycomb access control lists test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can create ACL classify table | Check if Honeycomb API can create an ACL table. | PASS |
| TC02: Honeycomb can remove ACL table | Check if Honeycomb API can delete an ACL table. | PASS |
| TC03: Honeycomb manages more than one ACL table | Check if Honeycomb API can create another ACL table. | PASS |
| TC04: Honeycomb can add ACL session to table | Check if Honeycomb API can add an ACL session to a table. | PASS |
| TC05: Honeycomb can remove ACL session | Check if Honeycomb API can remove an ACL session. | PASS |
| TC06: Honeycomb manages more than one ACL session on one table | Check if Honeycomb API can add another ACL session to a table. | PASS |
| TC07: Honeycomb enables ACL on interface | Check if Honeycomb API can enable ACL on an interface. | PASS |
| TC08: Honeycomb disables ACL on interface | Check if Honeycomb API can disable ACL on an interface. | PASS |
| TC09: Honeycomb can remove one out of multiple ACL tables | Check if Honeycomb API can delete an ACL table if more than one table exists. | PASS |
7.4.1.2. mgmt-cfg-dhcp-apihc-apivat-func¶
Honeycomb DHCP relay test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can configure DHCP relay entry | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-DHCP. [Cfg] (Using Honeycomb API) On DUT1 configure IP addresses neighbors and configure DHCP relay. [Ver] Send DHCP packets from TG interface to DUT. Receive all packets on the second TG interface and verify required fields. |
PASS |
| TC02: Honeycomb can remove DHCP relay entry | Remove DHCP relay configuration, and verify that it was removed. | PASS |
| TC03: Honeycomb can configure multiple DHCP relay servers. | Configure multiple DHCP relay servers and verify their configuration using operational data. | PASS |
| TC04: Honeycomb can configure DHCP relay entry with ipv6 | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-DHCPv6. [Cfg] (Using Honeycomb API) On DUT1 configure IP addresses neighbors and configure DHCP relay. [Ver] Send DHCPv6 packets from TG interface to DUT. Receive all packets on the second TG interface and verify required fields. |
PASS |
7.4.1.3. mgmt-cfg-int-apihcnc-func¶
Netconf test suite. Contains test cases that need to bypass REST API.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can create and delete interfaces | Repeatedly create and delete an interface through Netconf and check the reply for any errors. | PASS |
| TC02: Transaction revert test case 1 | Configure two conflicting VxLAN tunnels, then verify that neither tunnel exists. | PASS |
| TC03: Transaction revert test case 2 | Configure two conflicting TAP interfaces, then verify that neither interface exists. | PASS |
| TC04: Vlan subinterface creation | Configure a Vlan sub-interface under a physical interface. | PASS |
7.4.1.4. mgmt-cfg-int-subint-apihc-apivat-func¶
Honeycomb sub-interface management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb creates sub-interface | Check if Honeycomb creates a sub-interface. | PASS |
| TC02: Honeycomb sets interface and sub-interface up | Honeycomb changes the state of interface and of its sub-interface to up. | PASS |
| TC03: Honeycomb sets sub-interface down while its super-interface is up | Honeycomb sets the sub-interface down while its super-interface is up. It must be possible. | PASS |
| TC04: Honeycomb sets interface and sub-interface down | Honeycomb changes the state of interface down and then changes the state of its sub-interface down, in this order. | PASS |
| TC05: Honeycomb fails to set sub-interface up while its super-interface is down | Honeycomb tries to set the sub-interface up while its super-interface is down. It must not be possible. | PASS |
| TC06: Honeycomb fails to delete sub-interface | Check if Honeycomb can delete an existing sub-interface. | PASS |
| TC07: Honeycomb adds sub-interface to new bridge domain | Check if Honeycomb adds a sub-interface to bridge domain. | PASS |
| TC08: Honeycomb enables tag-rewrite pop 1 | Check if Honeycomb enables tag-rewrite and sets its parameters correctly. Case: pop 1. | PASS |
| TC09: Honeycomb enables tag-rewrite push | Check if Honeycomb enables tag-rewrite and sets its parameters correctly. Case: push. | PASS |
| TC10: Honeycomb enables tag-rewrite translate 1-2 | Check if Honeycomb enables tag-rewrite and sets its parameters correctly. Case: translate 1-2. | PASS |
| TC11: Honeycomb disables tag-rewrite | Check if Honeycomb disables the tag-rewrite. | PASS |
| TC12: Honeycomb enables tag-rewrite pop 1 again | Check if Honeycomb can enable tag-rewrite again, once it was disabled by Honeycomb. | PASS |
| TC13: Honeycomb modifies the tag-rewrite | Honeycomb sets the tag-rewrite: 1. pop 1, then 2. push, then 3. translate 1 - 2 Then Honeycomb disables the tag-rewrite. | PASS |
| TC14: Honeycomb fails to set wrong vlan-type in tag-rewrite | Check that Honeycomb does not accept wrong values of vlan-type in tag-rewrite. | PASS |
| TC15: Honeycomb configures sub-interface ipv4 address | Check if Honeycomb can configure an ipv4 address on the sub-interface. | PASS |
| TC16: Honeycomb removes sub-interface ipv4 address | Check if Honeycomb can remove configured ipv4 addresses from the sub-interface. | PASS |
| TC17: Honeycomb modifies existing sub-interface ipv4 address | Check if Honeycomb can modify an ipv4 address already configured on the sub-interface. | PASS |
| TC18: Honeycomb modifies sub-interface exact tag match | Check if Honeycomb can modify a sub-interface with exact tag match. | PASS |
| TC19: Honeycomb configures sub-interface ipv6 address | Check if Honeycomb can configure an ipv6 address on the sub-interface. | PASS |
| TC20: Honeycomb removes sub-interface ipv6 address | Check if Honeycomb can remove configured ipv6 addresses from the sub-interface. | PASS |
| TC21: Honeycomb modifies existing sub-interface ipv6 address | Check if Honeycomb can modify an ipv6 address already configured on the sub-interface. | PASS |
7.4.1.5. mgmt-cfg-intip4-intip6-apihc-apivat-func¶
Honeycomb interface management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb configures and reads interface state | Check if Honeycomb API can modify the admin state of VPP interfaces. | PASS |
| TC02: Honeycomb modifies interface IPv4 address with netmask | Check if Honeycomb API can configure interfaces for ipv4 with address and netmask provided. | PASS |
| TC03: Honeycomb removes IPv4 address from interface | Check if Honeycomb API can remove configured ipv4 addresses from interface. | PASS |
| TC04: Honeycomb modifies interface IPv4 address with prefix | Check if Honeycomb API can configure interfaces for ipv4 with address and prefix provided. | PASS |
| TC05: Honeycomb modifies IPv4 neighbor table | Check if Honeycomb API can add and remove ARP entries. | PASS |
| TC06: Honeycomb modifies interface configuration - IPv6 | Check if Honeycomb API can configure interfaces for ipv6. | PASS |
| TC07: Honeycomb modifies IPv6 neighbor table | Check if Honeycomb API can add and remove ARP entries. | PASS |
| TC08: Honeycomb modifies interface configuration - MTU | Check if Honeycomb API can configure interface MTU value. | PASS |
| TC09: Honeycomb modifies interface configuration - vrf | Check if Honeycomb API can configure interface vrf ID. | PASS |
| TC10: Honeycomb can configure multiple IP addresses on one interface | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-ICMP; Eth-IPv6-ICMPv6 [Cfg] (Using Honeycomb API) On DUT1 set two IPv4 addresses and two IPv6 addresses on first interfaces to TG and add ARP entries for each address. [Ver] Send ICMP packets from TG to DUT, using different sets of source and destination IP addresses. Receive an ICMP reply for every packet sent. |
PASS |
| TC11: Honeycomb fails to configure two IPv4 addresses from the same subnet | Check if Honeycomb can configure two IPv4 addresses in the same subnet onto a single interface. It should not be possible. | FAIL |
| TC12: Honeycomb fails to configure two IPv6 addresses from the same subnet | Check if Honeycomb can configure two IPv6 addresses in the same subnet onto a single interface. It should not be possible. | FAIL |
7.4.1.6. mgmt-cfg-inttap-apihc-apivat-func¶
Honeycomb TAP management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb configures TAP interface | Check if Honeycomb API can configure a TAP interface. | PASS |
| TC02: Honeycomb modifies existing TAP interface configuration | Check if Honeycomb API can re-configure and existing TAP interface with new settings. | PASS |
| TC03: Honeycomb removes TAP interface | Check if Honeycomb API can remove TAP interface. | PASS |
7.4.1.7. mgmt-cfg-intvhost-apihc-apivat-func¶
Honeycomb vhost-user interface management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb creates vhost-user interface - server | Check if Honeycomb creates a vhost-user interface, role: server. | PASS |
| TC02: Honeycomb modifies vhost-user interface - server | Check if Honeycomb can modify properties of existing vhost-user interface, role: server. | PASS |
| TC03: Honeycomb deletes vhost-user interface - server | Check if Honeycomb can delete an existing vhost-user interface, role: server. | PASS |
| TC04: Honeycomb creates vhost-user interface - client | Check if Honeycomb creates a vhost-user interface, role: client. | PASS |
| TC05: Honeycomb modifies vhost-user interface - client | Check if Honeycomb can modify properties of existing vhost-user interface, role: client. | PASS |
| TC06: Honeycomb deletes vhost-user interface - client | Check if Honeycomb can delete an existing vhost-user interface, role: client. | PASS |
| TC07: Honeycomb does not set vhost-user configuration on another interface type | Check if Honeycomb refuses to set vhost-user configuration for interface which is not v3po:vhost-user type. | PASS |
| TC08: Honeycomb does not set invalid vhost-user configuration | Check if Honeycomb refuses to set invalid parameters to vhost-user interface. | PASS |
7.4.1.8. mgmt-cfg-l2bd-apihc-apivat-func¶
Honeycomb bridge domain management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb sets up l2 bridge domain | Check if Honeycomb can create bridge domains on VPP node. | PASS |
| TC02: Honeycomb manages multiple bridge domains on node | Check if Honeycomb can manage multiple bridge domains on a single node. | PASS |
| TC03: Honeycomb removes bridge domains | Check if Honeycomb can remove bridge domains from a VPP node. | PASS |
| TC04: Honeycomb assigns interfaces to bridge domain | Check if Honeycomb can assign VPP interfaces to an existing bridge domain. | PASS |
| TC05: Honeycomb cannot remove bridge domain with an interface assigned | Check if Honeycomb can remove a bridge domain that has an interface assigned to it. Expect to fail with code 500. | PASS |
7.4.1.9. mgmt-cfg-l2fib-apihc-apivat-func¶
Honeycomb L2 FIB management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb adds L2 FIB entry (forward) | Honeycomb creates a bridge domain and assignes an interface to it. Then adds an L2 FIB entry (forward) to the bridge domain. | PASS |
| TC02: Honeycomb adds L2 FIB entry (static, forward) | Honeycomb adds an L2 FIB entry (static, forward) to the bridge domain. | PASS |
| TC03: Honeycomb adds L2 FIB entry (static, filter) | Honeycomb adds an L2 FIB entry (static, filter) to the bridge domain. | PASS |
| TC04: Honeycomb adds and removes L2 FIB entry (forward) | Honeycomb adds an L2 FIB entry (forward) to the bridge domain and then Honeycomb removes it from the bridge domain. | PASS |
| TC05: Honeycomb adds more than one L2 FIB entry | Honeycomb adds three L2 FIB entries to the bridge domain. | PASS |
| TC06: Honeycomb fails to set wrong L2 FIB entry | Honeycomb tries to add an L2 FIB entry with wrong parameters to the bridge domain. It must fail. | PASS |
| TC07: Honeycomb fails to modify existing L2 FIB entry | Honeycomb tries to modify an existing L2 FIB entry. It must fail. | PASS |
7.4.1.10. mgmt-cfg-lisp-apihc-apivat-func¶
Honeycomb Lisp test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb enables Lisp feature | Check if Honeycomb can enable the Lisp feature. | PASS |
| TC02: Honeycomb adds locator set and locator | Check if Honeycomb can configure a locator set. | PASS |
| TC03: Honeycomb configures Lisp - remote mapping - Bridge Domain | Check if Honeycomb can configure a remote Lisp mapping with a bridge domain. | PASS |
| TC04: Honeycomb can remove Lisp mapping | Check if Honeycomb can remove a configured Lisp mapping. | PASS |
| TC05: Honeycomb configures Lisp - remote mapping - VRF | Check if Honeycomb can configure a remote Lisp mapping with VRF. | PASS |
| TC06: Honeycomb configures Lisp - local mapping - Bridge Domain | Check if Honeycomb can configure a local Lisp mapping with a bridge domain. | PASS |
| TC07: Honeycomb configures Lisp - local mapping - VRF | Check if Honeycomb can configure a local Lisp mapping with VRF. | PASS |
| TC08: Honeycomb configures Lisp mapping with adjacency | Check if Honeycomb can configure local and remote Lisp mappings with VRF, and configure adjacency. | PASS |
| TC09: Honeycomb configures Lisp map resolver | Check if Honeycomb can configure a Lisp map resolver. | PASS |
| TC10: Honeycomb enabled Lisp PITR feature | Check if Honeycomb can configure the Lisp PITR feature. | PASS |
| TC11: Honeycomb can remove configuration of Lisp features | Check if Honeycomb can disable all Lisp features. | FAIL |
7.4.1.11. mgmt-cfg-pbb-apihc-apivat-func¶
Honeycomb provider backbone bridge test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb sets PBB sub-interface | Honeycomb creates a new PBB sub-interface. | PASS |
| TC02: Honeycomb modifies existing PBB sub-interface | Honeycomb modifies an existing PBB sub-interface. | PASS |
| TC03: Honeycomb deletes existing PBB sub-interface | Honeycomb deletes an existing PBB sub-interface. | PASS |
| TC04: Honeycomb fails to set wrong destination-address for new PBB sub-interface | Honeycomb fails to create a new PBB sub-interface with wrong value of parameter destination-address, type yang:mac-address. | PASS |
| TC05: Honeycomb fails to set wrong source-address for new PBB sub-interface | Honeycomb fails to create a new PBB sub-interface with wrong value of parameter source-address, type yang:mac-address. | PASS |
| TC06: Honeycomb fails to set wrong b-vlan-tag-vlan-id for new PBB sub-interface | Honeycomb fails to create a new PBB sub-interface with wrong value of parameter b-vlan-tag-vlan-id, type uint16, 12 bit range, range 1..4095. | PASS |
| TC07: Honeycomb fails to set wrong i-tag-isid for new PBB sub-interface | Honeycomb fails to create a new PBB sub-interface with wrong value of parameter i-tag-isid, type uint32, 24 bit range, range 1..16777215. | PASS |
| TC08: Honeycomb fails to create new PBB sub-interface without vlan tag | Honeycomb fails to create a new PBB sub-interface without parameter b-vlan-tag-vlan-id. | PASS |
7.4.1.12. mgmt-cfg-pluginacl-apihc-apivat-func¶
Honeycomb access control lists test suite for ACL plugin.
| Name | Documentation | Status |
|---|---|---|
| TC01: ACL MAC filtering through plugin-acl node - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure L2 MAC ACL on ingress interface. [Ver] Send simple TCP packets from one TG interface to the other, using different MACs. Receive all packets except those with MACs in the filtered ranges. |
PASS |
| TC02: ACL IPv4 filtering through plugin-acl node - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure L3 IPv4 ACL on ingress interface with src/dst IP and protocol number. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different IPv4 IPs. Receive all packets except those with IPs in the filtered ranges and UDP protocol payload. |
PASS |
| TC03: ACL IPv6 filtering through plugin-acl node - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure L3 IPv6 ACL on ingress interface with src/dst IP and protocol number. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different IPv6 IPs. Receive all packets except those with IPs in the filtered ranges and UDP protocol payload. |
FAIL |
| TC04: ACL port filtering through plugin-acl node - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and and configure L4 port ACL on ingress interface with src/dst port ranges. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different ports. Receive all packets except those with ports in the filtered ranges. |
PASS |
| TC05: ACL filtering with IPv4 address and TCP port in one rule - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure a mixed rule with src/dst IP, TCP protocol and port ranges. [Ver] Send simple TCP packets from one TG interface to the other, using IPs and ports. Receive all packets except those with both IPs and ports in the filtered ranges. |
PASS |
| TC06: ACL ICMP packet filtering - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-ICMP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure a ICMP protocol filtering by ICMP type and code. [Ver] Send ICMP packets from one TG interface to the other, using different codes and types. Receive all packets except those with types and codes in the filtered ranges. |
PASS |
| TC07: ACL ICMPv6 packet filtering - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-ICMP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG and configure a ICMPv6 protocol filtering by ICMPv6 type and code. [Ver] Send ICMPv6 packets from one TG interface to the other, using different codes and types. Receive all packets except those with the filtered type and code. |
FAIL |
| TC08: ACL reflexive IPv4 filtering through plugin-acl node - bridged | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 bridge both interfaces to TG, configure a ‘drop all’ ACL on ingress and reflexive ACL on egress. [Ver] Send a simple TCP packet to VPP interface 1 and do not receive it back. Then send the packet with reversed src/dst IP address to VPP interface 2 and receive it from interface 1(this should create a reflexive ‘permit’ rule) Finally, send the original packet again and receive it from interface 2. |
PASS |
| TC09: ACL IPv4 filtering through plugin-acl node - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv4 addresses on both interfaces to TG, add ARP entry and routes, and configure L3 IPv4 ACL on ingress interface with src/dst IP and protocol. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different IPv4 IPs. Receive all packets except those with IPs in the filtered ranges and UDP protocol payload. |
PASS |
| TC10: ACL IPv6 filtering through plugin-acl node - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv6 addresses on both interfaces to TG, add IP neighbor entry and routes, and configure L3 IPv6 ACL on ingress interface with src/dst IP and next-header. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different IPv6 IPs. Receive all packets except those with IPs in the filtered ranges and UDP protocol payload. |
FAIL |
| TC11: ACL port filtering through plugin-acl node - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv4 addresses on both interfaces to TG, add ARP entry and routes, and configure L4 port ACL on ingress interface with src/dst port ranges. [Ver] Send simple TCP and UDP packets from one TG interface to the other, using different ports. Receive all packets except those with ports in the filtered ranges. |
PASS |
| TC12: ACL filtering with IPv4 address and TCP port in one rule - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv4 addresses on both interfaces to TG, add ARP entry and routes and configure a mixed rule with src/dst IP, TCP protocol and port ranges. [Ver] Send simple TCP packets from one TG interface to the other, using IPs and ports. Receive all packets except those with both IPs and ports in the filtered ranges. |
PASS |
| TC13: ACL ICMP packet filtering - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv4 addresses on both interfaces to TG, add ARP entry and routes, and configure ICMP ACL on ingress interface with ICMP type and code. [Ver] Send ICMP packets from one TG interface to the other, using different codes and types. Receive all packets except those with the filtered type and code. |
PASS |
| TC14: ACL ICMPv6 packet filtering - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv6 addresses on both interfaces to TG, add ARP entry and routes, and configure ICMP ACL on ingress interface with ICMPv6 type and code. [Ver] Send ICMPv6 packets from one TG interface to the other, using different codes and types. Receive all packets except those with the filtered type and code. |
FAIL |
| TC15: ACL reflexive IPv4 filtering through plugin-acl node - routed | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-TCP. [Cfg] (Using Honeycomb API) On DUT1 set IPv4 addresses on both interfaces to TG, add ARP entries and routes, configure a ‘drop all’ ACL on ingress and reflexive ACL on egress. [Ver] Send a simple TCP packet to VPP interface 1 and do not receive it back. Then send the packet with reversed src/dst IP address to VPP interface 2 and receive it from interface 1(this should create a reflexive ‘permit’ rule) Finally, send the original packet again and receive it from interface 2. |
PASS |
7.4.1.13. mgmt-cfg-proxyarp-apihc-func¶
Honeycomb proxyARP management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can configure ipv4 proxyARP | Check if Honeycomb can configure the proxyARP feature. | PASS |
| TC02: Honeycomb can enable proxyarp on an interface | Check if Honeycomb can enable the proxyARP feature on an interface. | PASS |
| TC03: DUT sends ARP reply on behalf of another machine from the IP range | [Top] TG-DUT1. [Ref] RFC1027. [Cfg] On DUT1 configure interface IPv4 address and proxy ARP for IP range, using Honeycomb API. [Ver] Make TG send ARP request to DUT1 interface, verify if DUT1 sends correct ARP reply on behalf of machine whose IP is in the configured range. |
PASS |
7.4.1.14. mgmt-cfg-proxynd6-apihc-func¶
Honeycomb IPv6 neighbor discovery proxy test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can configure IPv6 ND proxy on an interface | Check if Honeycomb can configure the IPv6 ND proxy feature on an interface. | PASS |
| TC02: Honeycomb can disable IPv6 ND proxy on an interface | Check if Honeycomb can remove IPv6 ND proxy feature configuration from an interface. | PASS |
| TC03: Honeycomb can configure multiple IPv6 ND proxies on an interface | Check if Honeycomb can configure two ND proxies on one interface. | PASS |
| TC04: VPP proxies valid ICMPv6 Neighbor Discovery request | [Top] TG=DUT [Cfg] On DUT configure IPv6 addresses and neighbors, supress router advertisement and configure IPv6 Neighbor Discovery proxy. [Ver] Make TG send a neighbor solicitation packet to it’s other interface through DUT, verify DUT responds to the packet instead of forwarding it. Then exchange ICMPv6 Echo request/reply to verify connectivity between interfaces. [Ref] RFC 4389 |
PASS |
7.4.1.15. mgmt-cfg-routing-apihc-apivat-func¶
Honeycomb routing test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Single hop IPv4 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-ICMP. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure route with TG-if2 as next-hop. [Ver] Send ICMP packet from first TG interface to configured route destination. Receive packet on the second TG interface. |
PASS |
| TC02: Multi hop IPv4 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-ICMP. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure two routes through the second DUT interface. [Ver] Send 100 ICMP packets from first TG interface to configured route destination. Receive all packets on the second TG interface and verify that each destination MAC was used by exactly 50 packets. Receive packet on the second TG interface. |
PASS |
| TC03: Special hop - blackhole IPv4 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv4-ICMP. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure route with special rule blackhole. [Ver] Send ICMP packet from first TG interface to configured route destination. Make sure no packet is received on the second TG interface. |
PASS |
| TC04: Single hop IPv6 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-ICMPv6. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure route with TG-if2 as next-hop. [Ver] Send ICMP packet from first TG interface to configured route destination. Receive packet on the second TG interface. |
PASS |
| TC05: Multi hop IPv6 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-ICMPv6. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure two routes through the second DUT interface. [Ver] Send 100 ICMP packets from first TG interface to configured route destination. Receive all packets on the second TG interface and verify that each destination MAC was used by exactly 50 packets. Receive packet on the second TG interface. |
PASS |
| TC06: Special hop - blackhole IPv6 route | [Top] TG=DUT1=TG. [Enc] Eth-IPv6-ICMPv6. [Cfg] (Using Honeycomb API) On DUT1 add ARP entries to both TG interfaces and configure route with special rule blackhole. [Ver] Send ICMP packet from first TG interface to configured route destination. Make sure no packet is received on the second TG interface. |
PASS |
7.4.1.16. mgmt-cfg-slaac-apihc-func¶
Honeycomb SLAAC management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can configure SLAAC | Checks if Honeycomb can congigure SLAAC. | PASS |
| TC02: Honeycomb can disable SLAAC | Checks if Honeycomb can disable SLAAC. | PASS |
| TC03: Honeycomb can configure SLAAC with suppress link layer disabled | Checks if Honeycomb can congigure SLAAC. | PASS |
| TC04: Honeycomb can configure SLAAC with sending RA packets disabled | Checks if Honeycomb can configure SLAAC with given settings. | PASS |
| TC05: Honeycomb can configure SLAAC with min interval values | Checks if Honeycomb can configure SLAAC with given settings. | PASS |
| TC06: Honeycomb can configure SLAAC with max interval values | Checks if Honeycomb can configure SLAAC with given settings. | PASS |
| TC07: DUT retransmits RA on IPv6 enabled interface after a set interval | [Top] TG-DUT1-DUT2-TG. [Cfg] On DUT1 configure IPv6 interface on the link to TG. [Ver] Make TG wait for two IPv6 Router Advertisement packets to be sent by DUT1 and verify the received RA packets are correct. |
PASS |
7.4.1.17. mgmt-cfg-snat44-apihc-apivat-func¶
Honeycomb NAT test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb configures NAT entry | Honeycomb configures a static NAT entry. | PASS |
| TC02: Honeycomb removes NAT entry | Honeycomb removes a configured static NAT entry. | PASS |
| TC03: Honeycomb configures multiple NAT entries | Honeycomb configures two static NAT entries. | PASS |
| TC04: Honeycomb enables NAT on interface - inbound | Honeycomb configures NAT on an interface in inbound direction. | PASS |
| TC05: Honeycomb removes NAT interface configuration | Honeycomb removes NAT configuration from an interface. | PASS |
| TC06: Honeycomb enables NAT on interface - outbound | Honeycomb configures NAT on an interface in outbound direction. | PASS |
7.4.1.18. mgmt-cfg-spanrx-apihc-apivat-func¶
Honeycomb port mirroring test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb can configure SPAN on an interface receive | Honeycomb configures SPAN on interface and verifies against VPP SPAN dump in state receive. | PASS |
| TC02: Honeycomb can configure SPAN on an interface transmit | Honeycomb configures SPAN on interface and verifies against VPP SPAN dump in state transmit. | PASS |
| TC03: Honeycomb can configure SPAN on an interface both | Honeycomb configures SPAN on interface and verifies against VPP SPAN dump in state both. | PASS |
| TC04: Honeycomb can configure SPAN on two interfaces | Honeycomb configures SPAN on interface and verifies against VPP SPAN dump in state both. | PASS |
| TC05: Honeycomb can disable SPAN on interface | Honeycomb removes existing SPAN configuration on interface. | PASS |
| TC06: DUT mirrors IPv4 packets from one interface to another | [Top] TG=DUT1 [Cfg] (using Honeycomb) On DUT1 configure IPv4 address and set SPAN mirroring from one DUT interface to the other. [Ver] Make TG send an ARP packet to DUT through one interface, then receive a copy of sent packet and of DUT’s ARP reply on the second interface. |
PASS |
7.4.1.19. mgmt-cfg-vxlan-apihc-apivat-func¶
Honeycomb VxLAN management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb configures VxLAN tunnel | Check if Honeycomb API can configure VxLAN settings. | PASS |
| TC02: Honeycomb disables VxLAN tunnel | Check if Honeycomb API can reset VxLAN configuration. | PASS |
| TC03: Honeycomb can configure VXLAN tunnel after one has been disabled | Check if Honeycomb API can configure VxLAN settings again after previous settings have been removed. | PASS |
| TC04: Honeycomb does not set VxLAN configuration on another interface type | Check if Honeycomb API prevents setting VxLAN on incorrect interface. | PASS |
| TC05: Honeycomb does not set invalid VxLAN configuration | Check if Honeycomb API prevents setting incorrect VxLAN settings. | PASS |
| TC06: Honeycomb configures VxLAN tunnel with ipv6 | Check if Honeycomb API can configure VxLAN with ipv6 settings. | PASS |
7.4.1.20. mgmt-cfg-vxlangpe-apihc-apivat-func¶
Honeycomb VxLAN-GPE management test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb creates VxLAN GPE tunnel | Check if Honeycomb API can configure a VxLAN GPE tunnel. | PASS |
| TC02: Honeycomb removes VxLAN GPE tunnel | Check if Honeycomb API can remove VxLAN GPE tunnel. | PASS |
| TC03: Honeycomb sets wrong interface type while creating VxLAN GPE tunnel | Check if Honeycomb refuses to create a VxLAN GPE tunnel with a wrong interface type set. | PASS |
| TC04: Honeycomb sets wrong protocol while creating VxLAN GPE tunnel | Check if Honeycomb refuses to create a VxLAN GPE tunnel with a wrong next-protocol set. | PASS |
| TC05: Honeycomb sets VxLAN GPE tunnel on existing interface with wrong type | Check if Honeycomb refuses to create a VxLAN GPE tunnel on existing interface with wrong type. | PASS |
| TC06: Honeycomb creates VxLAN GPE tunnel with ipv6 | Check if Honeycomb API can configure a VxLAN GPE tunnel with IPv6 addresses. | PASS |
| TC07: Honeycomb creates a second VxLAN GPE tunnel with ipv6 | Check if Honeycomb API can configure another VxLAN GPE tunnel with IPv6 addresses. | PASS |
7.4.1.21. mgmt-notif-apihcnc-func¶
Honeycomb notifications test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb sends notification on interface state change | Check if Honeycomb sends a state-changed notification when the state of an interface is changed. | PASS |
| TC02: Honeycomb sends notification on interface deletion | Check if Honeycomb sends an interface-deleted notification when an interface is deleted. | PASS |
7.4.1.22. mgmt-statepersist-apihc-func¶
Honeycomb configuration persistence test suite.
| Name | Documentation | Status |
|---|---|---|
| TC01: Honeycomb persists configuration through restart of both Honeycomb and VPP | Checks if Honeycomb maintains configuration after both Honeycomb and VPP are restarted. | PASS |
| TC02: Honeycomb persists configuration through restart of Honeycomb | Checks if Honeycomb maintains configuration after it is restarted. | PASS |
| TC03: Honeycomb persists configuration through restart of VPP | Checks if Honeycomb updates VPP settings after VPP is restarted. | FAIL |
| TC04: Honeycomb reverts to defaults if persistence files are invalid | Checks if Honeycomb reverts to default configuration when persistence files are damaged or invalid. | PASS |