diff options
Diffstat (limited to 'tests/vpp/func')
| -rw-r--r-- | tests/vpp/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot | 161 | ||||
| -rw-r--r-- | tests/vpp/func/honeycomb/mgmt-cfg-lispgpe-apihc-apivat-func.robot | 240 |
2 files changed, 355 insertions, 46 deletions
diff --git a/tests/vpp/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot b/tests/vpp/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot index ac5af9ab83..fa2506cba4 100644 --- a/tests/vpp/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot +++ b/tests/vpp/func/honeycomb/mgmt-cfg-lisp-apihc-apivat-func.robot @@ -22,11 +22,15 @@ | ... | unknown-unicast-flood=${True} | arp-termination=${True} *** Settings *** +| Library | resources.libraries.python.Trace.Trace | Resource | resources/libraries/robot/shared/default.robot +| Resource | resources/libraries/robot/shared/testing_path.robot +| Resource | resources/libraries/robot/shared/traffic.robot | Resource | resources/libraries/robot/honeycomb/honeycomb.robot +| Resource | resources/libraries/robot/honeycomb/interfaces.robot | Resource | resources/libraries/robot/honeycomb/lisp.robot | Resource | resources/libraries/robot/honeycomb/bridge_domain.robot -| Variables | resources/test_data/honeycomb/lisp.py +| Variables | resources/test_data/honeycomb/lisp/lisp.py | ... | Documentation | *Honeycomb Lisp test suite.* | ... @@ -38,9 +42,9 @@ *** Test Cases *** | TC01: Honeycomb enables LISP feature -| | [Documentation] | Check if Honeycomb can enable the Lisp feature. +| | [Documentation] | Check if Honeycomb can enable the LISP feature. | | ... -| | Given Lisp Should Not Be Configured | ${node} +| | Given LISP Should Not Be Configured | ${node} | | When Honeycomb enables LISP | ${node} | | Then LISP state from Honeycomb should be | ${node} | ${state} | | And LISP state from VAT should be | ${node} | ${state} @@ -53,8 +57,8 @@ | | Then Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} -| TC03: Honeycomb configures Lisp - remote mapping - Bridge Domain -| | [Documentation] | Check if Honeycomb can configure a remote Lisp mapping\ +| TC03: Honeycomb configures LISP - remote mapping - Bridge Domain +| | [Documentation] | Check if Honeycomb can configure a remote LISP mapping\ | | ... | with a bridge domain. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} @@ -66,24 +70,24 @@ | | And LISP mapping from VAT should be | | ... | ${node} | ${vat_remote_bd} -| TC04: Honeycomb can remove Lisp mapping -| | [Documentation] | Check if Honeycomb can remove a configured Lisp mapping. +| TC04: Honeycomb can remove LISP mapping +| | [Documentation] | Check if Honeycomb can remove a configured LISP mapping. | | ... | | Given LISP mapping from Honeycomb should be | | ... | ${node} | ${remote_bd_subtable} | | And LISP mapping from VAT should be | | ... | ${node} | ${vat_remote_bd} -| | When Honeycomb removes all lisp mappings | ${node} +| | When Honeycomb removes all LISP mappings | ${node} | | Then LISP mappings from Honeycomb should not exist | | ... | ${node} | | And LISP mappings from VAT should not exist | | ... | ${node} -| TC05: Honeycomb configures Lisp - remote mapping - VRF -| | [Documentation] | Check if Honeycomb can configure a remote Lisp mapping\ +| TC05: Honeycomb configures LISP - remote mapping - VRF +| | [Documentation] | Check if Honeycomb can configure a remote LISP mapping\ | | ... | with VRF. | | ... -| | [Teardown] | Honeycomb removes all lisp mappings | ${node} +| | [Teardown] | Honeycomb removes all LISP mappings | ${node} | | ... | | Given LISP mappings from Honeycomb should not exist | | ... | ${node} @@ -94,11 +98,11 @@ | | ... | ${node} | ${remote_vrf_subtable} | | And LISP mapping from VAT should be | ${node} | ${vat_remote_vrf} -| TC06: Honeycomb configures Lisp - local mapping - Bridge Domain -| | [Documentation] | Check if Honeycomb can configure a local Lisp mapping\ +| TC06: Honeycomb configures LISP - local mapping - Bridge Domain +| | [Documentation] | Check if Honeycomb can configure a local LISP mapping\ | | ... | with a bridge domain. | | ... -| | [Teardown] | Honeycomb removes all lisp mappings | ${node} +| | [Teardown] | Honeycomb removes all LISP mappings | ${node} | | ... | | Given Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} @@ -112,11 +116,11 @@ | | Then LISP mapping from Honeycomb should be | ${node} | ${local_bd_subtable} | | And LISP mapping from VAT should be | ${node} | ${vat_local_bd} -| TC07: Honeycomb configures Lisp - local mapping - VRF -| | [Documentation] | Check if Honeycomb can configure a local Lisp mapping\ +| TC07: Honeycomb configures LISP - local mapping - VRF +| | [Documentation] | Check if Honeycomb can configure a local LISP mapping\ | | ... | with VRF. | | ... -| | [Teardown] | Honeycomb removes all lisp mappings | ${node} +| | [Teardown] | Honeycomb removes all LISP mappings | ${node} | | ... | | Given Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} @@ -128,16 +132,14 @@ | | Then LISP mapping from Honeycomb should be | ${node} | ${local_vrf_subtable} | | And LISP mapping from VAT should be | ${node} | ${vat_local_vrf} -| TC08: Honeycomb configures Lisp mapping with adjacency -| | [Documentation] | Check if Honeycomb can configure local and remote Lisp\ +| TC08: Honeycomb configures LISP mapping with adjacency +| | [Documentation] | Check if Honeycomb can configure local and remote LISP\ | | ... | mappings with VRF, and configure adjacency. | | ... -| | [Teardown] | Honeycomb removes all lisp mappings | ${node} +| | [Teardown] | Honeycomb removes all LISP mappings | ${node} | | ... | | Given Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} -| | And Honeycomb creates first l2 bridge domain -| | ... | ${node} | ${bd2_name} | ${bd_settings} | | And LISP mappings from Honeycomb should not exist | | ... | ${node} | | And LISP mappings from VAT should not exist @@ -145,29 +147,29 @@ | | And Honeycomb adds LISP mapping | ${node} | ${lisp_settings_both_vrf} | | When Honeycomb adds LISP adjacency | ${node} | ${7} | remote_map_vrf | | ... | adj01 | ${vrf_adjacency} -| | Then Lisp mapping from Honeycomb should be +| | Then LISP mapping from Honeycomb should be | | ... | ${node} | ${adj_subtable} -| TC09: Honeycomb configures Lisp Map Resolver -| | [Documentation] | Check if Honeycomb can configure a Lisp Map Resolver. +| TC09: Honeycomb configures LISP Map Resolver +| | [Documentation] | Check if Honeycomb can configure a LISP Map Resolver. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} | | And LISP state from VAT should be | ${node} | ${state} -| | When Honeycomb adds Lisp Map Resolver | ${node} | ${ip_address} +| | When Honeycomb adds LISP Map Resolver | ${node} | ${ip_address} | | Then Map Resolver from Honeycomb should be | ${node} | ${ip_address} | | And Map Resolver from VAT should be | ${node} | ${ip_address} -| TC10: Honeycomb configures Lisp Map Server -| | [Documentation] | Check if Honeycomb can configure a Lisp Map Server. +| TC10: Honeycomb configures LISP Map Server +| | [Documentation] | Check if Honeycomb can configure a LISP Map Server. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} | | And LISP state from VAT should be | ${node} | ${state} -| | When Honeycomb adds Lisp Map Server | ${node} | @{ip_addresses} +| | When Honeycomb adds LISP Map Server | ${node} | @{ip_addresses} | | Then Map Server from Honeycomb should be | ${node} | @{ip_addresses} | | And Map Server from VAT should be | ${node} | @{ip_addresses} -| TC11: Honeycomb configures Lisp PETR configuration -| | [Documentation] | Check if Honeycomb can configure Lisp +| TC11: Honeycomb configures LISP PETR configuration +| | [Documentation] | Check if Honeycomb can configure LISP | | ... | PETR configuration. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} @@ -176,8 +178,8 @@ | | Then PETR configuration from Honeycomb should be | ${node} | ${ip_address} | | And PETR configuration from VAT should be | ${node} | enabled -| TC12: Honeycomb configures Lisp RLOC Probing -| | [Documentation] | Check if Honeycomb can configure Lisp RLOC Probing. +| TC12: Honeycomb configures LISP RLOC Probing +| | [Documentation] | Check if Honeycomb can configure LISP RLOC Probing. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} | | And LISP state from VAT should be | ${node} | ${state} @@ -185,17 +187,17 @@ | | Then RLOC Probing from Honeycomb should be | ${node} | ${True} | | And RLOC Probing from VAT should be | ${node} | enabled -| TC13: Honeycomb configures Lisp Map Register -| | [Documentation] | Check if Honeycomb can configure a Lisp Map Register. +| TC13: Honeycomb configures LISP Map Register +| | [Documentation] | Check if Honeycomb can configure a LISP Map Register. | | ... | | Given LISP state from Honeycomb should be | ${node} | ${state} | | And LISP state from VAT should be | ${node} | ${state} -| | When Honeycomb adds Lisp Map Register | ${node} | ${True} +| | When Honeycomb adds LISP Map Register | ${node} | ${True} | | Then Map Register from Honeycomb should be | ${node} | ${True} | | And Map Register from VAT should be | ${node} | enabled -| TC14: Honeycomb enabled Lisp PITR feature -| | [Documentation] | Check if Honeycomb can configure the Lisp PITR feature. +| TC14: Honeycomb enabled LISP PITR feature +| | [Documentation] | Check if Honeycomb can configure the LISP PITR feature. | | ... | | Given Locator Set From Honeycomb Should Be | | ... | ${node} | ${interface} | ${locator_set} @@ -203,22 +205,89 @@ | | Then PITR config from Honeycomb should be | ${node} | ${locator_set} | | And PITR config from VAT should be | ${node} | ${locator_set} -| TC15: Honeycomb can remove configuration of Lisp features -| | [Documentation] | Check if Honeycomb can disable all Lisp features. +| TC15: Honeycomb can remove configuration of LISP features +| | [Documentation] | Check if Honeycomb can disable all LISP features. | | ... -| | Given Map resolver from Honeycomb should be | ${node} | ${ip_address} +| | Given Map Resolver from Honeycomb should be | ${node} | ${ip_address} | | And PITR config from Honeycomb should be | ${node} | ${locator_set} +| | And Map Register from Honeycomb should be | ${node} | ${True} | | When Honeycomb disables all LISP features | ${node} -| | Then Lisp Should Not Be Configured | ${node} +| | Then LISP Should Not Be Configured | ${node} + +| TC16: Honeycomb can configure LISP for traffic test - IPv4 +| | [Documentation] +| | ... | [Top] TG-DUT1-TG. +| | ... | [Enc] Eth-IPv4-LISP. +| | ... | [Cfg] On DUT1 configure IPv4 LISP static adjacencies with TG. +| | ... | [Ver] Make TG send ICMPv4 Echo Req between its interfaces through\ +| | ... | DUT1 and verify LISP encapsulation of received packet. +| | ... | [Ref] RFC6830. +| | ... +| | [Teardown] | LISP Functional Traffic Test Teardown +| | Given Configure path in 2-node circular topology +| | ... | ${nodes['TG']} | ${nodes['DUT1']} | ${nodes['TG']} +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if1} | up +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if2} | up +| | And Honeycomb sets interface IPv4 address with prefix | ${dut_node} +| | ... | ${dut_to_tg_if1} | ${dut_to_tg_if1_ip4} | ${prefix_len4} +| | And Honeycomb sets interface IPv4 address with prefix | ${dut_node} +| | ... | ${dut_to_tg_if2} | ${dut_to_tg_if2_ip4} | ${prefix_len4} +| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if1} +| | ... | ${src_ip4} | ${tg_to_dut_if1_mac} +| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if2} +| | ... | ${tg_to_dut_if2_ip4} | ${tg_to_dut_if2_mac} +| | When Honeycomb enables LISP | ${node} +| | And Honeycomb adds locator set | ${node} | ${dut_to_tg_if2} | ${locator_set} +| | And Honeycomb adds LISP mapping | ${node} | ${lisp_traffic_ip4} +| | Then send packet and verify LISP encap +| | ... | ${tg_node} | ${src_ip4} | ${dst_ip4} +| | ... | ${tg_to_dut_if1} | ${tg_to_dut_if1_mac} | ${dut_to_tg_if1_mac} +| | ... | ${tg_to_dut_if2} | ${dut_to_tg_if2_mac} | ${tg_to_dut_if2_mac} +| | ... | ${src_rloc4} | ${dst_rloc4} + +| TC17: Honeycomb can configure LISP for traffic test - IPv6 +| | [Documentation] +| | ... | [Top] TG-DUT1-TG. +| | ... | [Enc] Eth-IPv6-LISP. +| | ... | [Cfg] On DUT1 configure IPv6 LISP static adjacencies with TG. +| | ... | [Ver] Make TG send ICMPv6 Echo Req between its interfaces through\ +| | ... | DUT1 and verify LISP encapsulation of received packet. +| | ... | [Ref] RFC6830. +| | ... +| | [Teardown] | LISP Functional Traffic Test Teardown +| | Given Configure path in 2-node circular topology +| | ... | ${nodes['TG']} | ${nodes['DUT1']} | ${nodes['TG']} +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if1} | up +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if2} | up +| | And Honeycomb sets interface IPv6 address | ${dut_node} +| | ... | ${dut_to_tg_if1} | ${dut_to_tg_if1_ip6} | ${prefix_len6} +| | And Honeycomb sets interface IPv6 address | ${dut_node} +| | ... | ${dut_to_tg_if2} | ${dut_to_tg_if2_ip6} | ${prefix_len6} +| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if1} +| | ... | ${src_ip6} | ${tg_to_dut_if1_mac} +| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if2} +| | ... | ${tg_to_dut_if2_ip6} | ${tg_to_dut_if2_mac} +| | When Honeycomb enables LISP | ${node} +| | And Honeycomb adds locator set | ${node} | ${dut_to_tg_if2} | ${locator_set} +| | And Honeycomb adds LISP mapping | ${node} | ${lisp_traffic_ip6} +| | Then send packet and verify LISP encap +| | ... | ${tg_node} | ${src_ip6} | ${dst_ip6} +| | ... | ${tg_to_dut_if1} | ${tg_to_dut_if1_mac} | ${dut_to_tg_if1_mac} +| | ... | ${tg_to_dut_if2} | ${dut_to_tg_if2_mac} | ${tg_to_dut_if2_mac} +| | ... | ${src_rloc6} | ${dst_rloc6} -| TC16: Honeycomb configures Lisp Map Request Mode -| | [Documentation] | Check if Honeycomb can configure Lisp Map Request mode. +| TC18: Honeycomb configures LISP Map Request Mode +| | [Documentation] | Check if Honeycomb can configure LISP Map Request mode. | | ... | Note: Map Request Mode cannot be removed once configured. | | ... | | [Teardown] | Honeycomb disables LISP | ${node} | | ... -| | Given Honeycomb enables LISP | ${node} -| | When Honeycomb sets Lisp Map Request Mode | ${node} | ${True} +| | Given Honeycomb Enables LISP | ${node} +| | When Honeycomb sets LISP Map Request Mode | ${node} | ${True} | | Then Map Request Mode from Honeycomb should be | | ... | ${node} | source-destination | | And Map Request Mode from VAT should be | ${node} | src-dst diff --git a/tests/vpp/func/honeycomb/mgmt-cfg-lispgpe-apihc-apivat-func.robot b/tests/vpp/func/honeycomb/mgmt-cfg-lispgpe-apihc-apivat-func.robot new file mode 100644 index 0000000000..072d475417 --- /dev/null +++ b/tests/vpp/func/honeycomb/mgmt-cfg-lispgpe-apihc-apivat-func.robot @@ -0,0 +1,240 @@ +# Copyright (c) 2017 Cisco and/or its affiliates. +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at: +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +*** Variables*** +| ${interface}= | ${node['interfaces']['port1']['name']} + +*** Settings *** +| Library | resources.libraries.python.Trace.Trace +| Resource | resources/libraries/robot/shared/default.robot +| Resource | resources/libraries/robot/shared/testing_path.robot +| Resource | resources/libraries/robot/shared/traffic.robot +| Resource | resources/libraries/robot/honeycomb/honeycomb.robot +| Resource | resources/libraries/robot/honeycomb/interfaces.robot +| Resource | resources/libraries/robot/honeycomb/lisp_gpe.robot +| Variables | resources/test_data/honeycomb/lisp/lisp_gpe.py +| ... +| Documentation | *Honeycomb LISP GPE test suite.* +| ... +| Suite Setup | Set Up Honeycomb Functional Test Suite | ${node} +| ... +| Suite Teardown | Tear Down Honeycomb Functional Test Suite | ${node} +| ... +| Force Tags | HC_FUNC + +*** Test Cases *** +| TC01: Honeycomb enables LISP GPE feature +| | [Documentation] | Check if Honeycomb can enable the LISP GPE feature. +| | ... +| | [Tags] | HC_FUNC | test +| | Given LISP GPE Should Not Be Configured | ${node} +| | When Honeycomb enables LISP GPE | ${node} +| | Then LISP GPE state from Honeycomb should be | ${node} | enabled +| | And LISP GPE state from VAT should be | ${node} | enabled + +| TC02: Honeycomb disable LISP GPE feature +| | [Documentation] | Check if Honeycomb can enable the LISP GPE feature. +| | ... +| | [Tags] | HC_FUNC +| | [Teardown] | Honeycomb enables LISP GPE | ${node} +| | Given LISP GPE state from Honeycomb should be | ${node} | enabled +| | And LISP GPE state from VAT should be | ${node} | enabled +| | When Honeycomb disables LISP GPE | ${node} +| | Then LISP GPE state from Honeycomb should be | ${node} | disabled +| | And LISP GPE state from VAT should be | ${node} | disabled + +| TC03: Honeycomb configures LISP GPE mapping - negative, IPv4 +| | [Documentation] | Check if Honeycomb can configure a LISP mapping\ +| | ... | with VRF. +| | ... +| | [Tags] | HC_FUNC +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4} + +| TC04: Honeycomb can remove LISP GPE mapping +| | [Documentation] | Check if Honeycomb can remove a configured LISP GPE\ +| | ... | mapping. +| | ... +| | [Tags] | HC_FUNC +| | Given LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4} +| | When Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4['id']} +| | Then LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} + +| TC05: Honeycomb configures LISP GPE mapping - positive, IPv4 +| | [Documentation] | Check if Honeycomb can configure a LISP mapping\ +| | ... | with VRF. +| | ... +# | | [Tags] | HC_FUNC +# Disabled due to VPP-915 - configuring positive entry crashes VPP +| | [Teardown] | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${positive_mapping_ip4['id']} +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${positive_mapping_ip4} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${positive_mapping_ip4} + +| TC06: Honeycomb configures LISP GPE mapping - negative, IPv6 +| | [Documentation] | Check if Honeycomb can configure a LISP mapping\ +| | ... | with VRF. +| | ... +| | [Tags] | HC_FUNC +| | [Teardown] | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip6['id']} +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip6} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip6} + +| TC07: Honeycomb configures LISP GPE mapping - positive, IPv6 +| | [Documentation] | Check if Honeycomb can configure a LISP mapping\ +| | ... | with VRF. +| | ... +# | | [Tags] | HC_FUNC +# Disabled due to VPP-915 - configuring positive entry crashes VPP +| | [Teardown] | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${positive_mapping_ip6['id']} +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${positive_mapping_ip6} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${positive_mapping_ip6} + +| TC08: Honeycomb can modify existing LISP GPE mappping +| | [Documentation] | Check if Honeycomb can modify and existing LISP GPE\ +| | ... | mapping. +| | ... +| | [Tags] | HC_FUNC +| | [Teardown] | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4_edit['id']} +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4} +| | When Honeycomb adds first LISP GPE mapping | ${node} +| | ... | ${negative_mapping_ip4_edit} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4_edit} + +| TC09: Honeycomb can configure multiple LISP GPE mapppings +| | [Documentation] | Check if Honeycomb can configure multiple LISP GPE\ +| | ... | mappings at the same time. +| | ... +| | [Tags] | HC_FUNC +| | [Teardown] | Run Keywords +| | ... | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4['id']} +| | ... | AND | Honeycomb removes LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4_2['id']} +| | Given LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | When Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4} +| | And Honeycomb adds LISP GPE mapping | ${node} | ${negative_mapping_ip4_2} +| | Then LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4} +| | And LISP GPE mapping from Honeycomb should be +| | ... | ${node} | ${negative_mapping_ip4_2} + +| TC10: Honeycomb can disable all LISP GPE features +| | [Documentation] | Check if Honeycomb can disable all LISP GPE features. +| | ... +| | [Tags] | HC_FUNC +| | Given Honeycomb adds first LISP GPE mapping +| | ... | ${node} | ${negative_mapping_ip4} +| | When Honeycomb disables all LISP GPE features | ${node} +| | Then LISP GPE mappings from Honeycomb should not exist +| | ... | ${node} +| | And LISP GPE state from Honeycomb should be | ${node} | disabled +| | And LISP GPE state from VAT should be | ${node} | disabled + +| TC11: Honeycomb can configure LISP GPE for traffic test - IPv4 +| | [Documentation] +| | ... | [Top] TG-DUT1-TG. +| | ... | [Enc] Eth-IPv4-LISPGPE-IPv4-ICMPv4 +| | ... | [Cfg] Configure IPv4 LISP static adjacencies on DUT1. +| | ... | [Ver] Case: ip4-lispgpe-ip4 - phy2lisp +| | ... | Make TG send ICMPv4 Echo Req between its interfaces through DUT1\ +| | ... | LISP GPE tunnel verify LISP encapsulation of received packet. +| | ... | [Ref] RFC6830. +| | ... +| | [Tags] | test +| | [Teardown] | LISPGPE functional traffic test teardown +| | Given Configure path in 2-node circular topology +| | ... | ${nodes['TG']} | ${nodes['DUT1']} | ${nodes['TG']} +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if1} | up +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if2} | up +| | And Honeycomb sets interface IPv4 address with prefix | ${dut_node} +| | ... | ${dut_to_tg_if1} | ${dut_to_tg_if1_ip4} | ${prefix_len4} +| | And Honeycomb sets interface IPv4 address with prefix | ${dut_node} +| | ... | ${dut_to_tg_if2} | ${dut_to_tg_if2_ip4} | ${prefix_len4} +| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if1} +| | ... | ${src_ip4} | ${tg_to_dut_if1_mac} +| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if2} +| | ... | ${tg_to_dut_if2_ip4} | ${tg_to_dut_if2_mac} +| | When Honeycomb enables LISP GPE | ${node} +| | And Honeycomb adds LISP GPE mapping | ${node} | ${lisp_traffic_ip4} +| | Then send packet and verify LISP GPE encap +| | ... | ${tg_node} | ${src_ip4} | ${dst_ip4} +| | ... | ${tg_to_dut_if1} | ${tg_to_dut_if1_mac} | ${dut_to_tg_if1_mac} +| | ... | ${tg_to_dut_if2} | ${dut_to_tg_if2_mac} | ${tg_to_dut_if2_mac} +| | ... | ${src_rloc4} | ${dst_rloc4} + +| TC12: Honeycomb can configure LISP GPE for traffic test - IPv6 +| | [Documentation] +| | ... | [Top] TG-DUT1-TG. +| | ... | [Enc] Eth-IPv6-LISPGPE-IPv6-ICMPv6 +| | ... | [Cfg] Configure IPv6 LISP static adjacencies on DUT1. +| | ... | [Ver] Case: ip6-lispgpe-ip6 - phy2lisp +| | ... | Make TG send ICMPv6 Echo Req between its interfaces through DUT1\ +| | ... | LISP GPE tunnel verify LISP encapsulation of received packet. +| | ... | [Ref] RFC6830. +| | ... +| | [Tags] | test +| | [Teardown] | LISPGPE functional traffic test teardown +| | Given Configure path in 2-node circular topology +| | ... | ${nodes['TG']} | ${nodes['DUT1']} | ${nodes['TG']} +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if1} | up +| | And Honeycomb configures interface state +| | ... | ${dut_node} | ${dut_to_tg_if2} | up +| | And Honeycomb sets interface IPv6 address | ${dut_node} +| | ... | ${dut_to_tg_if1} | ${dut_to_tg_if1_ip6} | ${prefix_len6} +| | And Honeycomb sets interface IPv6 address | ${dut_node} +| | ... | ${dut_to_tg_if2} | ${dut_to_tg_if2_ip6} | ${prefix_len6} +| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if1} +| | ... | ${src_ip6} | ${tg_to_dut_if1_mac} +| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if2} +| | ... | ${tg_to_dut_if2_ip6} | ${tg_to_dut_if2_mac} +| | When Honeycomb enables LISP GPE | ${node} +| | And Honeycomb adds LISP GPE mapping | ${node} | ${lisp_traffic_ip6} +| | Then send packet and verify LISP GPE encap +| | ... | ${tg_node} | ${src_ip6} | ${dst_ip6} +| | ... | ${tg_to_dut_if1} | ${tg_to_dut_if1_mac} | ${dut_to_tg_if1_mac} +| | ... | ${tg_to_dut_if2} | ${dut_to_tg_if2_mac} | ${tg_to_dut_if2_mac} +| | ... | ${src_rloc6} | ${dst_rloc6} |