1 # Copyright (c) 2016 Cisco and/or its affiliates.
2 # Licensed under the Apache License, Version 2.0 (the "License");
3 # you may not use this file except in compliance with the License.
4 # You may obtain a copy of the License at:
6 # http://www.apache.org/licenses/LICENSE-2.0
8 # Unless required by applicable law or agreed to in writing, software
9 # distributed under the License is distributed on an "AS IS" BASIS,
10 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
11 # See the License for the specific language governing permissions and
12 # limitations under the License.
15 | ${ip_address}= | 192.168.0.4
16 | @{ip_addresses}= | 192.168.0.4 | 192.168.0.5 | 192.168.0.6 | 192.168.0.7
18 | ${interface}= | ${node['interfaces']['port1']['name']}
19 | ${bd_name}= | bd_lisp
20 | ${bd2_name}= | bd2_lisp
21 | &{bd_settings}= | flood=${True} | forward=${True} | learn=${True}
22 | ... | unknown-unicast-flood=${True} | arp-termination=${True}
25 | Resource | resources/libraries/robot/default.robot
26 | Resource | resources/libraries/robot/honeycomb/honeycomb.robot
27 | Resource | resources/libraries/robot/honeycomb/lisp.robot
28 | Resource | resources/libraries/robot/honeycomb/bridge_domain.robot
29 | Variables | resources/test_data/honeycomb/lisp.py
31 | Documentation | *Honeycomb Lisp test suite.*
33 | Suite Teardown | Run Keyword If Any Tests Failed
34 | ... | Restart Honeycomb and VPP | ${node}
36 | Force Tags | HC_FUNC
39 | TC01: Honeycomb enables LISP feature
40 | | [Documentation] | Check if Honeycomb can enable the Lisp feature.
42 | | Given Lisp Should Not Be Configured | ${node}
43 | | When Honeycomb enables LISP | ${node}
44 | | Then LISP state from Honeycomb should be | ${node} | ${state}
45 | | And LISP state from VAT should be | ${node} | ${state}
47 | TC02: Honeycomb adds locator set and locator
48 | | [Documentation] | Check if Honeycomb can configure a locator set.
50 | | Given LISP state from Honeycomb should be | ${node} | ${state}
51 | | When Honeycomb adds locator set | ${node} | ${interface} | ${locator_set}
52 | | Then Locator Set From Honeycomb Should Be
53 | | ... | ${node} | ${interface} | ${locator_set}
55 | TC03: Honeycomb configures Lisp - remote mapping - Bridge Domain
56 | | [Documentation] | Check if Honeycomb can configure a remote Lisp mapping\
57 | | ... | with a bridge domain.
59 | | Given LISP state from Honeycomb should be | ${node} | ${state}
60 | | And Honeycomb creates first l2 bridge domain
61 | | ... | ${node} | ${bd_name} | ${bd_settings}
62 | | When Honeycomb adds LISP mapping | ${node} | ${lisp_settings_remote_bd}
63 | | Then LISP mapping from Honeycomb should be
64 | | ... | ${node} | ${remote_bd_subtable}
65 | | And LISP mapping from VAT should be
66 | | ... | ${node} | ${vat_remote_bd}
68 | TC04: Honeycomb can remove Lisp mapping
69 | | [Documentation] | Check if Honeycomb can remove a configured Lisp mapping.
71 | | Given LISP mapping from Honeycomb should be
72 | | ... | ${node} | ${remote_bd_subtable}
73 | | And LISP mapping from VAT should be
74 | | ... | ${node} | ${vat_remote_bd}
75 | | When Honeycomb removes all lisp mappings | ${node}
76 | | Then LISP mappings from Honeycomb should not exist
78 | | And LISP mappings from VAT should not exist
81 | TC05: Honeycomb configures Lisp - remote mapping - VRF
82 | | [Documentation] | Check if Honeycomb can configure a remote Lisp mapping\
85 | | [Teardown] | Honeycomb removes all lisp mappings | ${node}
87 | | Given LISP mappings from Honeycomb should not exist
89 | | And LISP mappings from VAT should not exist
91 | | When Honeycomb adds LISP mapping | ${node} | ${lisp_settings_remote_vrf}
92 | | Then LISP mapping from Honeycomb should be
93 | | ... | ${node} | ${remote_vrf_subtable}
94 | | And LISP mapping from VAT should be | ${node} | ${vat_remote_vrf}
96 | TC06: Honeycomb configures Lisp - local mapping - Bridge Domain
97 | | [Documentation] | Check if Honeycomb can configure a local Lisp mapping\
98 | | ... | with a bridge domain.
100 | | [Teardown] | Honeycomb removes all lisp mappings | ${node}
102 | | Given Locator Set From Honeycomb Should Be
103 | | ... | ${node} | ${interface} | ${locator_set}
104 | | And LISP mappings from Honeycomb should not exist
106 | | And LISP mappings from VAT should not exist
108 | | And Honeycomb creates first l2 bridge domain
109 | | ... | ${node} | ${bd2_name} | ${bd_settings}
110 | | When Honeycomb adds LISP mapping | ${node} | ${lisp_settings_local_bd}
111 | | Then LISP mapping from Honeycomb should be | ${node} | ${local_bd_subtable}
112 | | And LISP mapping from VAT should be | ${node} | ${vat_local_bd}
114 | TC07: Honeycomb configures Lisp - local mapping - VRF
115 | | [Documentation] | Check if Honeycomb can configure a local Lisp mapping\
118 | | [Teardown] | Honeycomb removes all lisp mappings | ${node}
120 | | Given Locator Set From Honeycomb Should Be
121 | | ... | ${node} | ${interface} | ${locator_set}
122 | | And LISP mappings from Honeycomb should not exist
124 | | And LISP mappings from VAT should not exist
126 | | When Honeycomb adds LISP mapping | ${node} | ${lisp_settings_local_vrf}
127 | | Then LISP mapping from Honeycomb should be | ${node} | ${local_vrf_subtable}
128 | | And LISP mapping from VAT should be | ${node} | ${vat_local_vrf}
130 | TC08: Honeycomb configures Lisp mapping with adjacency
131 | | [Documentation] | Check if Honeycomb can configure local and remote Lisp\
132 | | ... | mappings with VRF, and configure adjacency.
134 | | [Teardown] | Honeycomb removes all lisp mappings | ${node}
136 | | Given Locator Set From Honeycomb Should Be
137 | | ... | ${node} | ${interface} | ${locator_set}
138 | | And Honeycomb creates first l2 bridge domain
139 | | ... | ${node} | ${bd2_name} | ${bd_settings}
140 | | And LISP mappings from Honeycomb should not exist
142 | | And LISP mappings from VAT should not exist
144 | | And Honeycomb adds LISP mapping | ${node} | ${lisp_settings_both_vrf}
145 | | When Honeycomb adds LISP adjacency | ${node} | ${7} | remote_map_vrf
146 | | ... | adj01 | ${vrf_adjacency}
147 | | Then Lisp mapping from Honeycomb should be
148 | | ... | ${node} | ${adj_subtable}
150 | TC09: Honeycomb configures Lisp Map Resolver
151 | | [Documentation] | Check if Honeycomb can configure a Lisp Map Resolver.
153 | | Given LISP state from Honeycomb should be | ${node} | ${state}
154 | | And LISP state from VAT should be | ${node} | ${state}
155 | | When Honeycomb adds Lisp Map Resolver | ${node} | ${ip_address}
156 | | Then Map Resolver from Honeycomb should be | ${node} | ${ip_address}
157 | | And Map Resolver from VAT should be | ${node} | ${ip_address}
159 | TC10: Honeycomb configures Lisp Map Server
160 | | [Documentation] | Check if Honeycomb can configure a Lisp Map Server.
162 | | Given LISP state from Honeycomb should be | ${node} | ${state}
163 | | And LISP state from VAT should be | ${node} | ${state}
164 | | When Honeycomb adds Lisp Map Server | ${node} | @{ip_addresses}
165 | | Then Map Server from Honeycomb should be | ${node} | @{ip_addresses}
166 | | And Map Server from VAT should be | ${node} | @{ip_addresses}
168 | TC11: Honeycomb configures Lisp PETR configuration
169 | | [Documentation] | Check if Honeycomb can configure Lisp
170 | | ... | PETR configuration.
172 | | Given LISP state from Honeycomb should be | ${node} | ${state}
173 | | And LISP state from VAT should be | ${node} | ${state}
174 | | When Honeycomb enables LISP PETR feature | ${node} | ${ip_address}
175 | | Then PETR configuration from Honeycomb should be | ${node} | ${ip_address}
176 | | And PETR configuration from VAT should be | ${node} | enabled
178 | TC12: Honeycomb configures Lisp RLOC Probing
179 | | [Documentation] | Check if Honeycomb can configure Lisp RLOC Probing.
181 | | Given LISP state from Honeycomb should be | ${node} | ${state}
182 | | And LISP state from VAT should be | ${node} | ${state}
183 | | When Honeycomb enables LISP RLOC feature | ${node}
184 | | Then RLOC Probing from Honeycomb should be | ${node} | ${True}
185 | | And RLOC Probing from VAT should be | ${node} | enabled
187 | TC13: Honeycomb configures Lisp Map Register
188 | | [Documentation] | Check if Honeycomb can configure a Lisp Map Register.
190 | | Given LISP state from Honeycomb should be | ${node} | ${state}
191 | | And LISP state from VAT should be | ${node} | ${state}
192 | | When Honeycomb adds Lisp Map Register | ${node} | ${True}
193 | | Then Map Register from Honeycomb should be | ${node} | ${True}
194 | | And Map Register from VAT should be | ${node} | enabled
196 | TC14: Honeycomb enabled Lisp PITR feature
197 | | [Documentation] | Check if Honeycomb can configure the Lisp PITR feature.
199 | | Given Locator Set From Honeycomb Should Be
200 | | ... | ${node} | ${interface} | ${locator_set}
201 | | When Honeycomb enables LISP PITR feature | ${node} | ${locator_set}
202 | | Then PITR config from Honeycomb should be | ${node} | ${locator_set}
203 | | And PITR config from VAT should be | ${node} | ${locator_set}
205 | TC15: Honeycomb can remove configuration of Lisp features
206 | | [Documentation] | Check if Honeycomb can disable all Lisp features.
208 | | Given Map resolver from Honeycomb should be | ${node} | ${ip_address}
209 | | And PITR config from Honeycomb should be | ${node} | ${locator_set}
210 | | When Honeycomb disables all LISP features | ${node}
211 | | Then Lisp Should Not Be Configured | ${node}
213 | TC16: Honeycomb configures Lisp Map Request Mode
214 | | [Documentation] | Check if Honeycomb can configure Lisp Map Request mode.
215 | | ... | Note: Map Request Mode cannot be removed once configured.
217 | | [Teardown] | Honeycomb disables LISP | ${node}
219 | | Given Honeycomb enables LISP | ${node}
220 | | When Honeycomb sets Lisp Map Request Mode | ${node} | ${True}
221 | | Then Map Request Mode from Honeycomb should be
222 | | ... | ${node} | source-destination
223 | | And Map Request Mode from VAT should be | ${node} | src-dst