diff options
author | Dan Andresan <Dan.Andresan@enea.com> | 2020-01-22 17:17:56 +0100 |
---|---|---|
committer | Miruna Paun <mrpa@enea.se> | 2020-01-27 15:00:26 +0100 |
commit | b896260295d6eef7cd015b6110ca89673d242048 (patch) | |
tree | 2fb35eab698e442735b6a9173170e5aa9dbf5ea8 | |
parent | 5990a8ac312856e122d7148492fff284dabbfcca (diff) | |
download | el_releases-nfv-access-b896260295d6eef7cd015b6110ca89673d242048.tar.gz |
BookExampleUseCases: add 128T Router
Added 128T VNF Setup as standalone VNF and as service chain with
Fortigate.
The documentation matches 2.2.1 release by:
- renaming dpdkWan to inbandMgmt
- renaming canonical without interfaces to dataPlane - integration
- renaming canonical with interfaces to dataPlane - communication
Change-Id: I1ba7c89eab5a085bd7621eeb23b2cf07f702c681
Signed-off-by: Dan Andresan <Dan.Andresan@enea.com>
-rw-r--r-- | .gitreview | 5 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml | 716 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml | 63 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml | 326 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml | 7 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml | 52 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml | 213 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/book.xml | 21 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png | bin | 0 -> 73441 bytes | |||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png | bin | 0 -> 52066 bytes | |||
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml | 1065 |
11 files changed, 2468 insertions, 0 deletions
diff --git a/.gitreview b/.gitreview new file mode 100644 index 0000000..30e070b --- /dev/null +++ b/.gitreview | |||
@@ -0,0 +1,5 @@ | |||
1 | [gerrit] | ||
2 | host=gerrit.enea.se | ||
3 | port=29418 | ||
4 | project=linux/el_releases-nfv-access | ||
5 | defaultbranch=rocko | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml new file mode 100644 index 0000000..9af1a89 --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml | |||
@@ -0,0 +1,716 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <chapter id="vnf_router_cust_uc"> | ||
3 | <title>128T VNF Router Example Use-case</title> | ||
4 | |||
5 | <para>The 128T Networking Platform (128T) natively provides network-based | ||
6 | security, control, and insight across data centers, wide-area networks | ||
7 | (WAN), and edge locations for enterprises, service providers, and cloud | ||
8 | companies alike.</para> | ||
9 | |||
10 | <section id="preq_128_router"> | ||
11 | <title>Prerequisites</title> | ||
12 | |||
13 | <para>The following are needed for this example use case:</para> | ||
14 | |||
15 | <itemizedlist spacing="compact"> | ||
16 | <listitem> | ||
17 | <para>1 in band management port for device management.</para> | ||
18 | </listitem> | ||
19 | |||
20 | <listitem> | ||
21 | <para>1 in band management port for 128T VNF.</para> | ||
22 | </listitem> | ||
23 | |||
24 | <listitem> | ||
25 | <para>1 WAN interface for 128T.</para> | ||
26 | </listitem> | ||
27 | |||
28 | <listitem> | ||
29 | <para>1 LAN interface for 128T.</para> | ||
30 | </listitem> | ||
31 | </itemizedlist> | ||
32 | </section> | ||
33 | |||
34 | <section id="vnf_router_cust"> | ||
35 | <title>128T VNF Router</title> | ||
36 | |||
37 | <figure> | ||
38 | <title>128T VNF Router Setup Overview</title> | ||
39 | |||
40 | <mediaobject> | ||
41 | <imageobject> | ||
42 | <imagedata contentwidth="600" fileref="images/trgt.png" /> | ||
43 | </imageobject> | ||
44 | </mediaobject> | ||
45 | </figure> | ||
46 | |||
47 | <section id="uc_setup_cust_router"> | ||
48 | <title>Use-case Setup</title> | ||
49 | |||
50 | <para><emphasis role="bold">Configuring Network Interfaces on uCPE | ||
51 | devices:</emphasis><orderedlist spacing="compact"> | ||
52 | <listitem> | ||
53 | <para>Log into the uCPE Manager with both username and password | ||
54 | values: <literal>admin</literal>.</para> | ||
55 | </listitem> | ||
56 | |||
57 | <listitem> | ||
58 | <para>Add the trgt uCPE device into the uCPE Manager: | ||
59 | <literal>Devices -> Manage -> Add</literal>.</para> | ||
60 | |||
61 | <para>Fill in the required fields with the following data:</para> | ||
62 | |||
63 | <table> | ||
64 | <title>Device Details</title> | ||
65 | |||
66 | <tgroup cols="2"> | ||
67 | <colspec align="left" /> | ||
68 | |||
69 | <colspec colwidth="2*" /> | ||
70 | |||
71 | <colspec colwidth="5*" /> | ||
72 | |||
73 | <thead> | ||
74 | <row> | ||
75 | <entry align="center">Field</entry> | ||
76 | |||
77 | <entry align="center">Value</entry> | ||
78 | </row> | ||
79 | </thead> | ||
80 | |||
81 | <tbody> | ||
82 | <row> | ||
83 | <entry>Type</entry> | ||
84 | |||
85 | <entry>Enea universal CPE</entry> | ||
86 | </row> | ||
87 | |||
88 | <row> | ||
89 | <entry>Release</entry> | ||
90 | |||
91 | <entry>1.0</entry> | ||
92 | </row> | ||
93 | |||
94 | <row> | ||
95 | <entry>Name</entry> | ||
96 | |||
97 | <entry>trgt</entry> | ||
98 | </row> | ||
99 | |||
100 | <row> | ||
101 | <entry>IP/DNS Address</entry> | ||
102 | |||
103 | <entry>Dynamic IP received by device from DHCP server | ||
104 | (E.g.: 172.24.12.74).</entry> | ||
105 | </row> | ||
106 | |||
107 | <row> | ||
108 | <entry>Description</entry> | ||
109 | |||
110 | <entry>Target 1</entry> | ||
111 | </row> | ||
112 | |||
113 | <row> | ||
114 | <entry>SSH Port</entry> | ||
115 | |||
116 | <entry>830</entry> | ||
117 | </row> | ||
118 | |||
119 | <row> | ||
120 | <entry>SSH User Name</entry> | ||
121 | |||
122 | <entry>root</entry> | ||
123 | </row> | ||
124 | |||
125 | <row> | ||
126 | <entry>Password</entry> | ||
127 | |||
128 | <entry>null</entry> | ||
129 | </row> | ||
130 | |||
131 | <row> | ||
132 | <entry>OK</entry> | ||
133 | |||
134 | <entry>Green status indicates connection with uCPE device | ||
135 | was established.</entry> | ||
136 | </row> | ||
137 | </tbody> | ||
138 | </tgroup> | ||
139 | </table> | ||
140 | </listitem> | ||
141 | |||
142 | <listitem> | ||
143 | <para>In order to add the device on the map: Right-Click on | ||
144 | <literal>Map -> Place Device -> trgt</literal>.</para> | ||
145 | </listitem> | ||
146 | |||
147 | <listitem> | ||
148 | <para>Configure the virtualization infrastructure for 128T VNF by | ||
149 | creating three OVS bridges and a host interface.</para> | ||
150 | |||
151 | <para>Select the trgt device then: <literal>Configuration -> | ||
152 | OpenVSwitch -> Bridges -> Add</literal>. Fill in the | ||
153 | required fields for each bridge with the following data from each | ||
154 | table:</para> | ||
155 | |||
156 | <table> | ||
157 | <title>ibm_br Bridge Details</title> | ||
158 | |||
159 | <tgroup cols="2"> | ||
160 | <colspec align="left" /> | ||
161 | |||
162 | <colspec colwidth="2*" /> | ||
163 | |||
164 | <colspec colwidth="5*" /> | ||
165 | |||
166 | <thead> | ||
167 | <row> | ||
168 | <entry align="center">Field</entry> | ||
169 | |||
170 | <entry align="center">Value</entry> | ||
171 | </row> | ||
172 | </thead> | ||
173 | |||
174 | <tbody> | ||
175 | <row> | ||
176 | <entry>id</entry> | ||
177 | |||
178 | <entry><autogenerated - do not change></entry> | ||
179 | </row> | ||
180 | |||
181 | <row> | ||
182 | <entry>Name</entry> | ||
183 | |||
184 | <entry><literal>ibm_br</literal></entry> | ||
185 | </row> | ||
186 | |||
187 | <row> | ||
188 | <entry>ovs-bridge-type</entry> | ||
189 | |||
190 | <entry>inbandMgmt</entry> | ||
191 | </row> | ||
192 | |||
193 | <row> | ||
194 | <entry>mgmt-address</entry> | ||
195 | |||
196 | <entry>Provide the IP address of the uCPE Manager machine | ||
197 | (E.g. 172.24.3.109).</entry> | ||
198 | </row> | ||
199 | |||
200 | <row> | ||
201 | <entry>mgmt-port</entry> | ||
202 | |||
203 | <entry>830</entry> | ||
204 | </row> | ||
205 | |||
206 | <row> | ||
207 | <entry>Create</entry> | ||
208 | |||
209 | <entry><para>The system will automatically select the | ||
210 | physical interface that has access to the uCPE | ||
211 | Manager.</para></entry> | ||
212 | </row> | ||
213 | </tbody> | ||
214 | </tgroup> | ||
215 | </table> | ||
216 | |||
217 | <table> | ||
218 | <title>vnf_mgmt_br Bridge Details</title> | ||
219 | |||
220 | <tgroup cols="2"> | ||
221 | <colspec align="left" /> | ||
222 | |||
223 | <colspec colwidth="2*" /> | ||
224 | |||
225 | <colspec colwidth="5*" /> | ||
226 | |||
227 | <thead> | ||
228 | <row> | ||
229 | <entry align="center">Field</entry> | ||
230 | |||
231 | <entry align="center">Value</entry> | ||
232 | </row> | ||
233 | </thead> | ||
234 | |||
235 | <tbody> | ||
236 | <row> | ||
237 | <entry>id</entry> | ||
238 | |||
239 | <entry><autogenerated - do not change></entry> | ||
240 | </row> | ||
241 | |||
242 | <row> | ||
243 | <entry>Name</entry> | ||
244 | |||
245 | <entry><literal>vnf_mgmt_br</literal></entry> | ||
246 | </row> | ||
247 | |||
248 | <row> | ||
249 | <entry>ovs-bridge-type</entry> | ||
250 | |||
251 | <entry>vnfMgmt</entry> | ||
252 | </row> | ||
253 | |||
254 | <row> | ||
255 | <entry>vnf-mgmt-address</entry> | ||
256 | |||
257 | <entry>10.0.0.1</entry> | ||
258 | </row> | ||
259 | |||
260 | <row> | ||
261 | <entry>Create</entry> | ||
262 | |||
263 | <entry></entry> | ||
264 | </row> | ||
265 | </tbody> | ||
266 | </tgroup> | ||
267 | </table> | ||
268 | |||
269 | <table> | ||
270 | <title>lan_br Bridge Details</title> | ||
271 | |||
272 | <tgroup cols="2"> | ||
273 | <colspec align="left" /> | ||
274 | |||
275 | <colspec colwidth="2*" /> | ||
276 | |||
277 | <colspec colwidth="5*" /> | ||
278 | |||
279 | <thead> | ||
280 | <row> | ||
281 | <entry align="center">Field</entry> | ||
282 | |||
283 | <entry align="center">Value</entry> | ||
284 | </row> | ||
285 | </thead> | ||
286 | |||
287 | <tbody> | ||
288 | <row> | ||
289 | <entry>id</entry> | ||
290 | |||
291 | <entry><autogenerated - do not change></entry> | ||
292 | </row> | ||
293 | |||
294 | <row> | ||
295 | <entry>Name</entry> | ||
296 | |||
297 | <entry><literal>lan_br</literal></entry> | ||
298 | </row> | ||
299 | |||
300 | <row> | ||
301 | <entry>ovs-bridge-type</entry> | ||
302 | |||
303 | <entry>dataPlane</entry> | ||
304 | </row> | ||
305 | |||
306 | <row> | ||
307 | <entry>sub-type</entry> | ||
308 | |||
309 | <entry>communication</entry> | ||
310 | </row> | ||
311 | |||
312 | <row> | ||
313 | <entry>+</entry> | ||
314 | |||
315 | <entry>Name: enp4s0f1 OK</entry> | ||
316 | </row> | ||
317 | |||
318 | <row> | ||
319 | <entry>Create</entry> | ||
320 | |||
321 | <entry></entry> | ||
322 | </row> | ||
323 | </tbody> | ||
324 | </tgroup> | ||
325 | </table> | ||
326 | |||
327 | <para>Add the Host Interface by selecting the trgt device, then | ||
328 | <literal>Configuration -> OpenVSwitch -> Host Interfaces | ||
329 | -> Add</literal>. </para> | ||
330 | |||
331 | <para></para> | ||
332 | |||
333 | <para>Fill in the required fields with the following data:</para> | ||
334 | |||
335 | <table> | ||
336 | <title>Host Interface Details</title> | ||
337 | |||
338 | <tgroup cols="2"> | ||
339 | <colspec align="left" /> | ||
340 | |||
341 | <colspec colwidth="2*" /> | ||
342 | |||
343 | <colspec colwidth="5*" /> | ||
344 | |||
345 | <thead> | ||
346 | <row> | ||
347 | <entry align="center">Field</entry> | ||
348 | |||
349 | <entry align="center">Value</entry> | ||
350 | </row> | ||
351 | </thead> | ||
352 | |||
353 | <tbody> | ||
354 | <row> | ||
355 | <entry>Source</entry> | ||
356 | |||
357 | <entry><literal>enp4s0f1</literal>. The only interface | ||
358 | available for LAN connection.</entry> | ||
359 | </row> | ||
360 | |||
361 | <row> | ||
362 | <entry>type</entry> | ||
363 | |||
364 | <entry>dpdk</entry> | ||
365 | </row> | ||
366 | |||
367 | <row> | ||
368 | <entry>networking-type</entry> | ||
369 | |||
370 | <entry>dpdk</entry> | ||
371 | </row> | ||
372 | |||
373 | <row> | ||
374 | <entry>dpdk-type</entry> | ||
375 | |||
376 | <entry>vfio-pci</entry> | ||
377 | </row> | ||
378 | |||
379 | <row> | ||
380 | <entry>Create</entry> | ||
381 | |||
382 | <entry><interface enp4s0f1 ready to be used in a LAN | ||
383 | bridge.></entry> | ||
384 | </row> | ||
385 | </tbody> | ||
386 | </tgroup> | ||
387 | </table> | ||
388 | </listitem> | ||
389 | </orderedlist></para> | ||
390 | |||
391 | <para><emphasis role="bold">Onboarding the VNFs:</emphasis></para> | ||
392 | |||
393 | <para>Onboard the VM Image through <literal>VNF -> Descriptors -> | ||
394 | On-board -> VM Image</literal>, and fill in the required fields with | ||
395 | the following values:</para> | ||
396 | |||
397 | <table> | ||
398 | <title>VM Image Details</title> | ||
399 | |||
400 | <tgroup cols="2"> | ||
401 | <colspec align="left" /> | ||
402 | |||
403 | <colspec colwidth="2*" /> | ||
404 | |||
405 | <colspec colwidth="5*" /> | ||
406 | |||
407 | <thead> | ||
408 | <row> | ||
409 | <entry align="center">Field</entry> | ||
410 | |||
411 | <entry align="center">Value</entry> | ||
412 | </row> | ||
413 | </thead> | ||
414 | |||
415 | <tbody> | ||
416 | <row> | ||
417 | <entry>VM image file</entry> | ||
418 | |||
419 | <entry><literal>centos_128t_with_ci.qcow2</literal></entry> | ||
420 | </row> | ||
421 | |||
422 | <row> | ||
423 | <entry>Image format</entry> | ||
424 | |||
425 | <entry>QCOW2</entry> | ||
426 | </row> | ||
427 | |||
428 | <row> | ||
429 | <entry>VNF Type Name</entry> | ||
430 | |||
431 | <entry>128T</entry> | ||
432 | </row> | ||
433 | |||
434 | <row> | ||
435 | <entry>Description</entry> | ||
436 | |||
437 | <entry>128T Router</entry> | ||
438 | </row> | ||
439 | |||
440 | <row> | ||
441 | <entry>Version</entry> | ||
442 | |||
443 | <entry>1.0</entry> | ||
444 | </row> | ||
445 | |||
446 | <row> | ||
447 | <entry>Memory in MB</entry> | ||
448 | |||
449 | <entry>8192. More memory can be allocated if required | ||
450 | (<28672).</entry> | ||
451 | </row> | ||
452 | |||
453 | <row> | ||
454 | <entry>Num. of CPUs</entry> | ||
455 | |||
456 | <entry>2. More CPUs can be reserved if required | ||
457 | (<15).</entry> | ||
458 | </row> | ||
459 | |||
460 | <row> | ||
461 | <entry>Interfaces -> +</entry> | ||
462 | |||
463 | <entry>Name: mgmt</entry> | ||
464 | </row> | ||
465 | |||
466 | <row> | ||
467 | <entry>Interfaces -> +</entry> | ||
468 | |||
469 | <entry>Name: wan</entry> | ||
470 | </row> | ||
471 | |||
472 | <row> | ||
473 | <entry>Interfaces -> +</entry> | ||
474 | |||
475 | <entry>Name: lan</entry> | ||
476 | </row> | ||
477 | |||
478 | <row> | ||
479 | <entry>Cloud Init -> Cloud-Init Datasource</entry> | ||
480 | |||
481 | <entry>ISO</entry> | ||
482 | </row> | ||
483 | |||
484 | <row> | ||
485 | <entry>Cloud Init -> Cloud-Init Disk Type</entry> | ||
486 | |||
487 | <entry>cdrom</entry> | ||
488 | </row> | ||
489 | |||
490 | <row> | ||
491 | <entry>Properties -> +</entry> | ||
492 | |||
493 | <entry>Name: vnfMgmtIpAddress. Value: 10.0.0.2</entry> | ||
494 | </row> | ||
495 | |||
496 | <row> | ||
497 | <entry>Properties -> +</entry> | ||
498 | |||
499 | <entry>Name: internalMgmtPort. Value: 443</entry> | ||
500 | </row> | ||
501 | |||
502 | <row> | ||
503 | <entry>Properties -> +</entry> | ||
504 | |||
505 | <entry>Name: externalMgmtPort. Value: 60001</entry> | ||
506 | </row> | ||
507 | |||
508 | <row> | ||
509 | <entry>Onboard</entry> | ||
510 | |||
511 | <entry><Wait for message: VNF package onboarded | ||
512 | successfully></entry> | ||
513 | </row> | ||
514 | |||
515 | <row> | ||
516 | <entry>Close</entry> | ||
517 | |||
518 | <entry></entry> | ||
519 | </row> | ||
520 | </tbody> | ||
521 | </tgroup> | ||
522 | </table> | ||
523 | |||
524 | <note> | ||
525 | <itemizedlist> | ||
526 | <listitem> | ||
527 | <para>HTTPS access (443) can be changed with another type of | ||
528 | access. Please consult official 128T documentation and make sure | ||
529 | the 128T VNF is configured to accept another type of connection | ||
530 | before changing the port number.</para> | ||
531 | </listitem> | ||
532 | |||
533 | <listitem> | ||
534 | <para><literal>externalMgmtPort</literal> (60001) represents the | ||
535 | external port on which the user can access the VNF management | ||
536 | interface via HTTPS. Another port can be selected if needed. There | ||
537 | are no other changes required or components affected by this | ||
538 | change.</para> | ||
539 | </listitem> | ||
540 | |||
541 | <listitem> | ||
542 | <para><literal>vnfMgmtIpAddress</literal> (10.0.0.2) represents | ||
543 | the IP address of the management interface of the 128T VNF. | ||
544 | Changing this value requires an update to the 128T configuration | ||
545 | to match the new IP address.</para> | ||
546 | </listitem> | ||
547 | </itemizedlist> | ||
548 | </note> | ||
549 | |||
550 | <para><emphasis role="bold">Instantiating the VNFs:</emphasis></para> | ||
551 | |||
552 | <para>Instantiate the 128T VNF by selecting the trgt device, then | ||
553 | <literal>VNF -> Instances -> Add</literal>.</para> | ||
554 | |||
555 | <para>Fill in the required fields with the following values:</para> | ||
556 | |||
557 | <table> | ||
558 | <title>128T VNF Instantiation</title> | ||
559 | |||
560 | <tgroup cols="2"> | ||
561 | <colspec align="left" /> | ||
562 | |||
563 | <colspec colwidth="2*" /> | ||
564 | |||
565 | <colspec colwidth="5*" /> | ||
566 | |||
567 | <thead> | ||
568 | <row> | ||
569 | <entry align="center">Field</entry> | ||
570 | |||
571 | <entry align="center">Value</entry> | ||
572 | </row> | ||
573 | </thead> | ||
574 | |||
575 | <tbody> | ||
576 | <row> | ||
577 | <entry>Name</entry> | ||
578 | |||
579 | <entry>128T_trgt_1</entry> | ||
580 | </row> | ||
581 | |||
582 | <row> | ||
583 | <entry>VNF Type</entry> | ||
584 | |||
585 | <entry>128T</entry> | ||
586 | </row> | ||
587 | |||
588 | <row> | ||
589 | <entry>VNFD Version</entry> | ||
590 | |||
591 | <entry>1.0</entry> | ||
592 | </row> | ||
593 | |||
594 | <row> | ||
595 | <entry>Flavour</entry> | ||
596 | |||
597 | <entry>Canonical</entry> | ||
598 | </row> | ||
599 | |||
600 | <row> | ||
601 | <entry>uCPE Device</entry> | ||
602 | |||
603 | <entry>trgt</entry> | ||
604 | </row> | ||
605 | |||
606 | <row> | ||
607 | <entry>Cloud Init File</entry> | ||
608 | |||
609 | <entry><literal>centos_128t_internet_ci.iso</literal></entry> | ||
610 | </row> | ||
611 | |||
612 | <row> | ||
613 | <entry>Domain Update Script</entry> | ||
614 | |||
615 | <entry></entry> | ||
616 | </row> | ||
617 | |||
618 | <row> | ||
619 | <entry>Interfaces</entry> | ||
620 | |||
621 | <entry></entry> | ||
622 | </row> | ||
623 | |||
624 | <row> | ||
625 | <entry>ID</entry> | ||
626 | |||
627 | <entry>IF Name</entry> | ||
628 | </row> | ||
629 | |||
630 | <row> | ||
631 | <entry>mgmt (dpdk)</entry> | ||
632 | |||
633 | <entry>Bridge: vnf_mgmt_br</entry> | ||
634 | </row> | ||
635 | |||
636 | <row> | ||
637 | <entry>wan (dpdk)</entry> | ||
638 | |||
639 | <entry>Bridge: ibm_br</entry> | ||
640 | </row> | ||
641 | |||
642 | <row> | ||
643 | <entry>lan (dpdk)</entry> | ||
644 | |||
645 | <entry>Bridge: lan_br</entry> | ||
646 | </row> | ||
647 | |||
648 | <row> | ||
649 | <entry>Create</entry> | ||
650 | |||
651 | <entry></entry> | ||
652 | </row> | ||
653 | </tbody> | ||
654 | </tgroup> | ||
655 | </table> | ||
656 | </section> | ||
657 | |||
658 | <section id="uc_test_cust_router"> | ||
659 | <title>Testing the Use-case</title> | ||
660 | |||
661 | <para>In order to access the web interface of the 128T VNF, open a | ||
662 | browser from a machine connected on the same network with the WAN port | ||
663 | of the trgt uCPE device and browse to: | ||
664 | <literal>https://<public_trgt_WAN_IP>:60001</literal>. Log in | ||
665 | using the following credentials:</para> | ||
666 | |||
667 | <itemizedlist> | ||
668 | <listitem> | ||
669 | <para>Username: admin</para> | ||
670 | </listitem> | ||
671 | |||
672 | <listitem> | ||
673 | <para>Password: 128Tadmin</para> | ||
674 | </listitem> | ||
675 | </itemizedlist> | ||
676 | |||
677 | <para>In order to validate the data path, connect a test machine to the | ||
678 | LAN physical port, assign the static IP and a route:<programlisting>> ifconfig eth3 192.168.64.2 netmask 255.255.255.0 | ||
679 | > ip route add default via 192.168.64.1 dev eth3 | ||
680 | > ping 8.8.8.8</programlisting>For data path validation, it may be required | ||
681 | to generate a new cloud-init image to match your network configuration. | ||
682 | Please check Appendix A: How to create 128T cloud-init iso image (day-0 | ||
683 | configuration), for more details.</para> | ||
684 | </section> | ||
685 | |||
686 | <section id="cleanup_custone"> | ||
687 | <title>Use-case Clean-up</title> | ||
688 | |||
689 | <para>In order to remove the setup created previously all components | ||
690 | need to be deleted in reverse order:</para> | ||
691 | |||
692 | <orderedlist> | ||
693 | <listitem> | ||
694 | <para>Select the trgt uCPE device -> VNF -> Instances -> | ||
695 | 128T -> Delete.</para> | ||
696 | </listitem> | ||
697 | |||
698 | <listitem> | ||
699 | <para>Select the trgt uCPE device -> Configuration -> | ||
700 | OpenVSwitch -> Bridges. Select all bridges -> Delete.</para> | ||
701 | </listitem> | ||
702 | |||
703 | <listitem> | ||
704 | <para>Select the trgt uCPE device -> Configuration -> | ||
705 | OpenVSwitch -> Host Interfaces. Select all interfaces -> | ||
706 | Delete.</para> | ||
707 | </listitem> | ||
708 | |||
709 | <listitem> | ||
710 | <para>VNF -> Descriptors, select all bundles -> | ||
711 | Offboard.</para> | ||
712 | </listitem> | ||
713 | </orderedlist> | ||
714 | </section> | ||
715 | </section> | ||
716 | </chapter> | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml new file mode 100644 index 0000000..df262af --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml | |||
@@ -0,0 +1,63 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <appendix id="appendix_one_cust"> | ||
3 | <title>How to create a 128T cloud-init iso image (day-0 | ||
4 | configuration)</title> | ||
5 | |||
6 | <para><emphasis role="bold">Prerequisites:</emphasis><itemizedlist> | ||
7 | <listitem> | ||
8 | <para>Development host with Linux shell.</para> | ||
9 | </listitem> | ||
10 | |||
11 | <listitem> | ||
12 | <para><literal>genisoimage</literal> tool installed.</para> | ||
13 | </listitem> | ||
14 | </itemizedlist></para> | ||
15 | |||
16 | <para>Unpack the <filename>128T/128t-cloud-init-example.tar.gz</filename> | ||
17 | archive and check the README file for more details:</para> | ||
18 | |||
19 | <programlisting>>tar -zxf 128t-cloud-init-example.tar.gz | ||
20 | >cd 128T/cloud-init-example/ | ||
21 | >ls ./ | ||
22 | README | ||
23 | user-data | ||
24 | meta-data | ||
25 | t128-running.xml</programlisting> | ||
26 | |||
27 | <para>To generate the cloud-init iso image:</para> | ||
28 | |||
29 | <programlisting>>genisoimage -output centos_128t_ci.iso -volid cidata -joliet \ | ||
30 | -rock user-data meta-data t128-running.xml </programlisting> | ||
31 | |||
32 | <para><emphasis role="bold">Notes: </emphasis><itemizedlist> | ||
33 | <listitem> | ||
34 | <para><literal>user-data</literal> and <literal>meta-data</literal> | ||
35 | files must be kept unchanged.</para> | ||
36 | </listitem> | ||
37 | |||
38 | <listitem> | ||
39 | <para>To update the 128T configuration change the | ||
40 | <literal>t128-runing.xml</literal> file.</para> | ||
41 | </listitem> | ||
42 | |||
43 | <listitem> | ||
44 | <para>XML is the same file downloaded from 128T web access: | ||
45 | <literal>configuration -> Import and Export Configuration -> | ||
46 | Export Configuration -> Download Configuration</literal>. The | ||
47 | configuration can be updated from a web interface, downloaded onto the | ||
48 | development host and used in generating a new cloud-init iso | ||
49 | image.</para> | ||
50 | </listitem> | ||
51 | </itemizedlist></para> | ||
52 | |||
53 | <para>By default, <literal>t128-running.xml</literal> is configured to pass | ||
54 | all traffic from the LAN to the WAN interface. There is only one change | ||
55 | required for the 128T VNF to work on the user's network:</para> | ||
56 | |||
57 | <programlisting><rt:next-hop>172.24.15.254</rt:next-hop></programlisting> | ||
58 | |||
59 | <para>Please change <172.24.15.254> with the IP address of your | ||
60 | Gateway in the <filename>t128-running.xml</filename> file and generate a new | ||
61 | iso image as described above. For more details about configuring the 128T | ||
62 | VNF please contact 128 Technologies.</para> | ||
63 | </appendix> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml new file mode 100644 index 0000000..b0a90b2 --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml | |||
@@ -0,0 +1,326 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <appendix id="appendix_two_cust"> | ||
3 | <title>How to create the 128T image for NFV Access</title> | ||
4 | |||
5 | <para>The following steps were used by Enea to generate the 128T qcow2 image | ||
6 | used as the VNF image on NFV Access.</para> | ||
7 | |||
8 | <note> | ||
9 | <para>Follow the <filename>128tISO-Install.pdf</filename> document and | ||
10 | keep in mind a Virtual Machine was used instead of a physical host.</para> | ||
11 | </note> | ||
12 | |||
13 | <para><emphasis role="bold">Prerequisites:</emphasis><itemizedlist> | ||
14 | <listitem> | ||
15 | <para><filename>128T-3.2.7-1.el7.centos.x86_64.iso</filename> provided | ||
16 | by 128 Technologies.</para> | ||
17 | </listitem> | ||
18 | |||
19 | <listitem> | ||
20 | <para>A Linux development host with internet access.</para> | ||
21 | </listitem> | ||
22 | |||
23 | <listitem> | ||
24 | <para>A least one of the TAP interfaces connected to a bridge with | ||
25 | Internet access.</para> | ||
26 | </listitem> | ||
27 | </itemizedlist><emphasis role="bold">How to create the 128T image for NFV | ||
28 | Access:</emphasis><orderedlist> | ||
29 | <listitem> | ||
30 | <programlisting>>qemu-img create -f qcow2 128t.qcow2 128G | ||
31 | >qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \ | ||
32 | -M q35 -nographic bios /usr/share/qemu/bios.bin -boot order=d,menu=on \ | ||
33 | cdrom 128T-3.2.7-1.el7.centos.x86_64.iso \ | ||
34 | hdb 128t.qcow2 \ | ||
35 | device e1000,netdev=net1,mac=52:52:01:02:03:01 \ | ||
36 | netdev tap,id=net1,ifname=tap1,script=no,downscript=no</programlisting> | ||
37 | </listitem> | ||
38 | |||
39 | <listitem> | ||
40 | <para>Press the <ENTER> key to begin the installation | ||
41 | process.</para> | ||
42 | </listitem> | ||
43 | |||
44 | <listitem> | ||
45 | <para>Wait for the distribution and the 128T to install:</para> | ||
46 | |||
47 | <programlisting>------------------------------ | ||
48 | 128T Packages Installed | ||
49 | |||
50 | Please Remove Install Media, | ||
51 | |||
52 | then enter <Yes> to reboot and | ||
53 | continue install process | ||
54 | |||
55 | <Yes> <No> | ||
56 | ------------------------------</programlisting> | ||
57 | |||
58 | <para>Press Yes.</para> | ||
59 | </listitem> | ||
60 | |||
61 | <listitem> | ||
62 | <para>Wait to reboot and press <literal>CTR+ a+c</literal> to enter | ||
63 | the qemu monitor:</para> | ||
64 | |||
65 | <programlisting>(qemu) quit</programlisting> | ||
66 | </listitem> | ||
67 | |||
68 | <listitem> | ||
69 | <para>Start qemu only with the qcow2 image attached, no installer | ||
70 | image required:</para> | ||
71 | |||
72 | <programlisting>>qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \ | ||
73 | -M q35 -nographic bios /usr/share/qemu/bios.bin \ | ||
74 | -boot order=c,menu=on \ | ||
75 | -hda 128t.qcow2 \ | ||
76 | -device e1000,netdev=net1,mac=52:52:01:02:03:01 \ | ||
77 | -netdev tap,id=net1,ifname=tap1,script=no,downscript=no | ||
78 | |||
79 | ------------------------------------------------------------------------------ | ||
80 | Booting from Hard Disk... | ||
81 | . | ||
82 | |||
83 | * CentOS Linux (3.10.0-514.2.2.el7.x86_64) 7 (Core) | ||
84 | CentOS Linux (0-rescue-4e73a369e89e466a888c9c77655a1d65) 7 (Core) | ||
85 | |||
86 | |||
87 | Use the ^ and v keys to change the selection. | ||
88 | Press 'e' to edit the selected item, or 'c' for a command prompt. | ||
89 | ------------------------------------------------------------------------------</programlisting> | ||
90 | |||
91 | <para>Select the first option.</para> | ||
92 | </listitem> | ||
93 | |||
94 | <listitem> | ||
95 | <programlisting>|-------------------128T Installer-------------------| | ||
96 | | | | ||
97 | | Configure Linux Networking | | ||
98 | | | | ||
99 | | Before 128T SetUp? | | ||
100 | | | | ||
101 | | | | ||
102 | | < Yes > < No > | | ||
103 | |----------------------------------------------------|</programlisting> | ||
104 | |||
105 | <para>Select NO.</para> | ||
106 | </listitem> | ||
107 | |||
108 | <listitem> | ||
109 | <para><programlisting>|----------------------------------------------------| | ||
110 | | Please select a role for this node: | | ||
111 | | |----------------------------------------------| | | ||
112 | | | (*) Router | | | ||
113 | | | ( ) Conductor | | | ||
114 | | |----------------------------------------------| | | ||
115 | | | | ||
116 | |----------------------------------------------------| | ||
117 | | < OK > < Back > | | ||
118 | |----------------------------------------------------|</programlisting>Select | ||
119 | Router and OK.</para> | ||
120 | </listitem> | ||
121 | |||
122 | <listitem> | ||
123 | <programlisting>|-------------------Conductor Info-------------------| | ||
124 | | | | ||
125 | | |----------------------------------------------| | | ||
126 | | |1st Conductor Address | | | ||
127 | | |Conductor Address | | | ||
128 | | |----------------------------------------------| | | ||
129 | | | | ||
130 | |----------------------------------------------------| | ||
131 | | < OK > < Skip > < Back > < Help > | | ||
132 | |----------------------------------------------------|</programlisting> | ||
133 | |||
134 | <para>Select SKIP.</para> | ||
135 | </listitem> | ||
136 | |||
137 | <listitem> | ||
138 | <para><programlisting>|----------------------HA Setup----------------------| | ||
139 | | What kind of Router node is this? | | ||
140 | | |----------------------------------------------| | | ||
141 | | |(*) Standalone No HA peer | | | ||
142 | | |( ) 1st HA Node HA peer is not set up | | | ||
143 | | |( ) 2nd HA Node HA peer is already set up | | | ||
144 | | |----------------------------------------------| | | ||
145 | | | | ||
146 | | | | ||
147 | |----------------------------------------------------| | ||
148 | | < OK > < Back > | | ||
149 | |----------------------------------------------------|</programlisting>Select | ||
150 | Standalone and OK.</para> | ||
151 | </listitem> | ||
152 | |||
153 | <listitem> | ||
154 | <programlisting>|---------------------Node Info----------------------| | ||
155 | | |----------------------------------------------| | | ||
156 | | | Node Role Router | | | ||
157 | | | Node Name 128tNode | | | ||
158 | | | Router Name 128tRouter | | | ||
159 | | |----------------------------------------------| | | ||
160 | | | | ||
161 | |----------------------------------------------------| | ||
162 | | < OK > < Advanced > < Back > < Help > | | ||
163 | |----------------------------------------------------|</programlisting> | ||
164 | |||
165 | <para>Enter a name for the router and node, press OK.</para> | ||
166 | </listitem> | ||
167 | |||
168 | <listitem> | ||
169 | <programlisting>|-------------------Password Setup-------------------| | ||
170 | | Enter the new password for the 128T 'admin' | | ||
171 | | user: | | ||
172 | | |----------------------------------------------| | | ||
173 | | | 128Tadmin | | | ||
174 | | |----------------------------------------------| | | ||
175 | | | | | ||
176 | |----------------------------------------------------| | ||
177 | | < OK > < Back > | | ||
178 | |----------------------------------------------------|</programlisting> | ||
179 | |||
180 | <para>Enter the password for web access: <literal>128Tadmin</literal> | ||
181 | and confirm the password.</para> | ||
182 | </listitem> | ||
183 | |||
184 | <listitem> | ||
185 | <programlisting>|--------------------------Anonymous Data Collection--------------------------| | ||
186 | | The 128T Networking Platform comes packaged with a software process | | ||
187 | |("Roadrunner") that is used to proactively monitor the health and liveliness | | ||
188 | |of the 128T Router and associated components. This watchdog process collects | | ||
189 | |anonymous information from the router and sends it to 128 Technology for | | ||
190 | |storage and analysis. This information helps inform 128 Technology about | | ||
191 | |software usage, to aid in the support and improvement of the 128 Technology | | ||
192 | |Networking Platform. | | ||
193 | | | | ||
194 | |Disabling this feature will prevent the sending of anonymous usage data to | | ||
195 | |128 Technology. | | ||
196 | | | | ||
197 | | | | ||
198 | | < Accept > < Back > < Disable > | | ||
199 | |-----------------------------------------------------------------------------|</programlisting> | ||
200 | |||
201 | <para>Select Accept.</para> | ||
202 | </listitem> | ||
203 | |||
204 | <listitem> | ||
205 | <programlisting>|-----128T Statistics Table Creator-----| | ||
206 | | Created table for metric 760/827 | | ||
207 | | Created table for metric 770/827 | | ||
208 | | Created table for metric 780/827 | | ||
209 | | Created table for metric 790/827 | | ||
210 | | Created table for metric 800/827 | | ||
211 | | Created table for metric 810/827 | | ||
212 | | Created table for metric 820/827 | | ||
213 | | Finished pre-creating stats tables | | ||
214 | | Creating tables for audit events | | ||
215 | | Finished creating audit event tables | | ||
216 | | Completed in 27.001386642456055 s | | ||
217 | | Shutting down local Cassandra node | | ||
218 | |---------------------------------------| | ||
219 | | < OK > | | ||
220 | |---------------------------------------|</programlisting> | ||
221 | |||
222 | <para>Select OK.</para> | ||
223 | </listitem> | ||
224 | |||
225 | <listitem> | ||
226 | <programlisting>|--------128T Installer Status----------| | ||
227 | | | | ||
228 | | Install SUCCESS | | ||
229 | | | | ||
230 | | Start 128T Router | | ||
231 | | before proceeding to | | ||
232 | | login prompt? | | ||
233 | |---------------------------------------| | ||
234 | | < Yes > < No > | | ||
235 | |---------------------------------------|</programlisting> | ||
236 | |||
237 | <para>Select: Yes</para> | ||
238 | </listitem> | ||
239 | |||
240 | <listitem> | ||
241 | <programlisting>localhost login: root | ||
242 | Password:</programlisting> | ||
243 | |||
244 | <para>The following user accounts and passwords are created during the | ||
245 | ISO installation process:</para> | ||
246 | |||
247 | <table> | ||
248 | <title>Accounts Created</title> | ||
249 | |||
250 | <tgroup cols="2"> | ||
251 | <colspec align="left" /> | ||
252 | |||
253 | <thead> | ||
254 | <row> | ||
255 | <entry align="center">User</entry> | ||
256 | |||
257 | <entry align="center">Password</entry> | ||
258 | </row> | ||
259 | </thead> | ||
260 | |||
261 | <tbody> | ||
262 | <row> | ||
263 | <entry>root</entry> | ||
264 | |||
265 | <entry>128tRoutes</entry> | ||
266 | </row> | ||
267 | |||
268 | <row> | ||
269 | <entry>t128</entry> | ||
270 | |||
271 | <entry>128tRoutes</entry> | ||
272 | </row> | ||
273 | </tbody> | ||
274 | </tgroup> | ||
275 | </table> | ||
276 | </listitem> | ||
277 | |||
278 | <listitem> | ||
279 | <para>GUI login via HTTPS is enabled by default on port 443</para> | ||
280 | |||
281 | <programlisting>[root@localhost ~]# dhclient enp0s2 | ||
282 | [root@localhost ~]# echo "nameserver 8.8.8.8" >>/etc/resolv.conf | ||
283 | [root@localhost ~]# yum -y install cloud-init | ||
284 | [root@localhost ~]# reboot</programlisting> | ||
285 | </listitem> | ||
286 | |||
287 | <listitem> | ||
288 | <para>Wait to reboot and press CTR+ a+c to enter in qemu | ||
289 | monitor.</para> | ||
290 | |||
291 | <programlisting>(qemu) quit | ||
292 | > qemu-img info 128t.qcow2 | ||
293 | image: 128t.qcow2 | ||
294 | file format: qcow2 | ||
295 | virtual size: 128G (137438953472 bytes) | ||
296 | disk size: 5.4G | ||
297 | cluster_size: 65536 | ||
298 | Format specific information: | ||
299 | compat: 1.1 | ||
300 | lazy refcounts: false | ||
301 | refcount bits: 16 | ||
302 | corrupt: false</programlisting> | ||
303 | </listitem> | ||
304 | |||
305 | <listitem> | ||
306 | <para>Compress the generated <filename>128t.qcow2</filename> image to | ||
307 | decrease the size of VNF image:</para> | ||
308 | |||
309 | <programlisting>qemu-img convert -O qcow2 -c 128t.qcow2 centos_128t_compressed.qcow2 | ||
310 | |||
311 | > qemu-img info centos_128t_compressed.qcow2 | ||
312 | image: centos_128t_compressed.qcow2 | ||
313 | file format: qcow2 | ||
314 | virtual size: 128G (137438953472 bytes) | ||
315 | disk size: 1.2G | ||
316 | cluster_size: 65536 | ||
317 | Format specific information: | ||
318 | compat: 1.1 | ||
319 | lazy refcounts: false | ||
320 | refcount bits: 16 | ||
321 | corrupt: false | ||
322 | |||
323 | centos_128t_compressed.qcow2 - Resulted image can be used in NFV Access.</programlisting> | ||
324 | </listitem> | ||
325 | </orderedlist></para> | ||
326 | </appendix> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml new file mode 100644 index 0000000..e8bd5ce --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml | |||
@@ -0,0 +1,7 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <appendix id="appendix_three_cust"> | ||
3 | <title>How to configure Fortigate VNF (day-0 configuration)</title> | ||
4 | |||
5 | <para>Please check the README file from Fortigate folder for more | ||
6 | details.</para> | ||
7 | </appendix> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml new file mode 100644 index 0000000..42e6a5e --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml | |||
@@ -0,0 +1,52 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <appendix id="appendix_four_cust"> | ||
3 | <title>Running Enea Automation Framework tests</title> | ||
4 | |||
5 | <para>The most relevant information from the Automation Framework and Test | ||
6 | Harness structure:</para> | ||
7 | |||
8 | <programlisting>|---automation_framework | ||
9 | | |---unittestSuite | ||
10 | | | |---128tCleanup.json - Use case 1 - clean up - test. | ||
11 | | | |---128tDeploy.json - Use case 1 - test. | ||
12 | | | |---128t_FG_SFCCleanup.json - Use case 2 - clean up - test. | ||
13 | | | |---128t_FG_SFCDeploy.json - Use case 2 - test. | ||
14 | | | |---config | ||
15 | | | | |---cust | ||
16 | - Folder containing the configuration files used by tests. | ||
17 | | | |---unittestLoader.py | ||
18 | | | |---unittestSuite.py | ||
19 | |---lab_config | ||
20 | | |---trgt-1 | ||
21 | | | |---enp4s0f0_0000_04_00_0.json | ||
22 | | | |---enp4s0f1_0000_04_00_1.json | ||
23 | | | |---ibm_br.json - In-band management definition. | ||
24 | | | |---lan_br_enp4s0f1.json - Lan bridge definition. | ||
25 | | | |---trgt-1.json | ||
26 | - Target definition - make sure to update the "address". | ||
27 | | | |---sfc_br.json - Service chain bridge definition. | ||
28 | | | |---vnf_mgmt_br.json - VNF management bridge definition. | ||
29 | |---vnf_config | ||
30 | | |---128t | ||
31 | | | |---128tInstance.json - 128T instantiation - used in use case 1. | ||
32 | | | |---128t.json - 128T onboarding. | ||
33 | | | |---128tSFCInstance.json - 128T instantiation - used in use case 2. | ||
34 | | | |---centos_128t_internet_ci.iso - 128T cloud init (day-0) iso image. | ||
35 | | |---fortigate | ||
36 | | | |---fg_basic_fw.conf - Fortigate day-0 configuration. | ||
37 | | | |---fortigateInstance.json - Fortigate instantiantion. | ||
38 | | | |---fortigate.json - Fortigate onboarding. | ||
39 | | | |---fortigateLicense.lic | ||
40 | - Fortigate license - replace it with a valid License file. | ||
41 | |---vnf_image | ||
42 | | |---centos_128t_with_ci.qcow2 - 128T qcow2 image. | ||
43 | | |---fortios.qcow2 - Fortigate qcow2 image.</programlisting> | ||
44 | |||
45 | <para>Make sure to update the relevant configuration file for your setup. | ||
46 | The essential files to consider are the target configuration | ||
47 | (<filename>trgt-1.json</filename>), the license for the Fortigate VNF, and | ||
48 | the 128T cloud-init iso image matching your network.</para> | ||
49 | |||
50 | <para>To run a test:<programlisting>> cd automation_and_systemtest/automation_framework/unittestSuite | ||
51 | > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 -s</programlisting></para> | ||
52 | </appendix> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml new file mode 100644 index 0000000..6e30d4e --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml | |||
@@ -0,0 +1,213 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <appendix id="appendix_five_cust"> | ||
3 | <title>Example Tests Results using the Automation Framework</title> | ||
4 | |||
5 | <programlisting>Test Host: | ||
6 | Use Case1 - 128T | ||
7 | > cd automation_and_systemtest/automation_framework/unittestSuite | ||
8 | > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ | ||
9 | -s 128tDeploy.json -d "128T Deployment" | ||
10 | |||
11 | Running 128T Deployment... | ||
12 | |||
13 | test 001: Add VCPE Agent from trgt-1 device (__main__.UnittestSuite) ... | ||
14 | 2019-08-13 12:49:58,091 - INFO: Add uCPE device | ||
15 | 2019-08-13 12:49:58,342 - INFO: Done | ||
16 | ok | ||
17 | test 002: Wait VCPE Agent device be up (__main__.UnittestSuite) ... | ||
18 | 2019-08-13 12:49:58,358 - INFO: Wait uCPE device | ||
19 | 2019-08-13 12:50:03,470 - INFO: Done | ||
20 | ok | ||
21 | test 003: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... | ||
22 | 2019-08-13 12:50:03,486 - INFO: Bind NIC | ||
23 | 2019-08-13 12:50:03,901 - INFO: Done | ||
24 | ok | ||
25 | test 004: Creating ibm bridge (__main__.UnittestSuite) ... | ||
26 | 2019-08-13 12:50:03,920 - INFO: New OVS network bridge | ||
27 | 2019-08-13 12:50:17,465 - INFO: Done | ||
28 | ok | ||
29 | test 005: Creating VNF Management bridge (__main__.UnittestSuite) ... | ||
30 | 2019-08-13 12:50:17,481 - INFO: New OVS network bridge | ||
31 | 2019-08-13 12:50:17,626 - INFO: Done | ||
32 | ok | ||
33 | test 006: Creating LAN bridge and attaching enp4s0f1 interface to the bridge \ | ||
34 | (__main__.UnittestSuite) ... | ||
35 | 2019-08-13 12:50:17,643 - INFO: New OVS network bridge | ||
36 | 2019-08-13 12:50:18,313 - INFO: Done | ||
37 | ok | ||
38 | test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... | ||
39 | 2019-08-13 12:50:18,332 - INFO: Onboard wizard | ||
40 | 2019-08-13 12:52:52,909 - INFO: Done | ||
41 | ok | ||
42 | test 008: Instantiate 128T VNF (__main__.UnittestSuite) ... | ||
43 | 2019-08-13 12:52:52,924 - INFO: Instantiate VNF | ||
44 | 2019-08-13 12:54:06,219 - INFO: Done | ||
45 | ok | ||
46 | |||
47 | ---------------------------------------------------------------------- | ||
48 | Ran 8 tests in 248.144s | ||
49 | |||
50 | OK | ||
51 | |||
52 | |||
53 | Clean-up use-case1 | ||
54 | > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ | ||
55 | -s 128tCleanup.json -d "128T Clean-up" | ||
56 | |||
57 | Running 128T Clean-up... | ||
58 | |||
59 | test 001: Destroying 128T VNF (__main__.UnittestSuite) ... | ||
60 | 2019-08-13 13:03:02,704 - INFO: Destroy VNF | ||
61 | 2019-08-13 13:03:03,619 - INFO: Done | ||
62 | ok | ||
63 | test 002: Deleting network bridge LAN (__main__.UnittestSuite) ... | ||
64 | 2019-08-13 13:03:03,635 - INFO: Delete OVS network bridge | ||
65 | 2019-08-13 13:03:13,857 - INFO: Done | ||
66 | ok | ||
67 | test 003: Deleting VNF management bridge (__main__.UnittestSuite) ... | ||
68 | 2019-08-13 13:03:13,877 - INFO: Delete OVS network bridge | ||
69 | 2019-08-13 13:03:24,027 - INFO: Done | ||
70 | ok | ||
71 | test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... | ||
72 | 2019-08-13 13:03:24,049 - INFO: Delete OVS network bridge | ||
73 | 2019-08-13 13:03:48,815 - INFO: Done | ||
74 | ok | ||
75 | test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... | ||
76 | 2019-08-13 13:03:48,835 - INFO: Unbind NIC | ||
77 | 2019-08-13 13:03:50,274 - INFO: Done | ||
78 | ok | ||
79 | test 006: Offboarding 128t VNF (__main__.UnittestSuite) ... | ||
80 | 2019-08-13 13:03:50,294 - INFO: Offboard VNF | ||
81 | 2019-08-13 13:03:50,844 - INFO: Done | ||
82 | ok | ||
83 | test 007: Remove VCPE Agent trgt-1 device (__main__.UnittestSuite) ... | ||
84 | 2019-08-13 13:03:50,858 - INFO: Remove uCPE device | ||
85 | 2019-08-13 13:03:50,998 - INFO: Done | ||
86 | ok | ||
87 | |||
88 | ---------------------------------------------------------------------- | ||
89 | Ran 7 tests in 48.308s | ||
90 | |||
91 | OK | ||
92 | |||
93 | |||
94 | Use-case2 | ||
95 | > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ | ||
96 | -s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment" | ||
97 | Running 128T - Fortigate SFC Deployment... | ||
98 | |||
99 | test 001: Add VCPE Agent from trgt-1 device (__main__.UnittestSuite) ... | ||
100 | 2019-08-13 13:09:16,146 - INFO: Add uCPE device | ||
101 | 2019-08-13 13:09:16,272 - INFO: Done | ||
102 | ok | ||
103 | test 002: Wait VCPE Agent device be up (__main__.UnittestSuite) ... | ||
104 | 2019-08-13 13:09:16,287 - INFO: Wait uCPE device | ||
105 | 2019-08-13 13:09:23,421 - INFO: Done | ||
106 | ok | ||
107 | test 003: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ... | ||
108 | 2019-08-13 13:09:23,445 - INFO: Bind NIC | ||
109 | 2019-08-13 13:09:24,226 - INFO: Done | ||
110 | ok | ||
111 | test 004: Creating ibm bridge (__main__.UnittestSuite) ... | ||
112 | 2019-08-13 13:09:24,245 - INFO: New OVS network bridge | ||
113 | 2019-08-13 13:09:34,720 - INFO: Done | ||
114 | ok | ||
115 | test 005: Creating VNF Management bridge (__main__.UnittestSuite) ... | ||
116 | 2019-08-13 13:09:34,741 - INFO: New OVS network bridge | ||
117 | 2019-08-13 13:09:34,885 - INFO: Done | ||
118 | ok | ||
119 | test 006: Creating LAN bridge and attaching enp4s0f1 interface to the bridge \ | ||
120 | (__main__.UnittestSuite) ... | ||
121 | 2019-08-13 13:09:34,903 - INFO: New OVS network bridge | ||
122 | 2019-08-13 13:09:35,566 - INFO: Done | ||
123 | ok | ||
124 | test 007: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ... | ||
125 | 2019-08-13 13:09:35,587 - INFO: New OVS network bridge | ||
126 | 2019-08-13 13:09:35,667 - INFO: Done | ||
127 | ok | ||
128 | test 008: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ... | ||
129 | 2019-08-13 13:09:35,684 - INFO: Onboard wizard | ||
130 | 2019-08-13 13:12:11,845 - INFO: Done | ||
131 | ok | ||
132 | test 009: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ... | ||
133 | 2019-08-13 13:12:11,861 - INFO: Onboard wizard | ||
134 | 2019-08-13 13:12:16,157 - INFO: Done | ||
135 | ok | ||
136 | test 010: Instantiate 128T VNF (__main__.UnittestSuite) ... | ||
137 | 2019-08-13 13:12:16,175 - INFO: Instantiate VNF | ||
138 | 2019-08-13 13:13:31,681 - INFO: Done | ||
139 | ok | ||
140 | test 011: Instantiate Fortigate VNF (__main__.UnittestSuite) ... | ||
141 | 2019-08-13 13:13:31,738 - INFO: Instantiate VNF | ||
142 | 2019-08-13 13:13:35,985 - INFO: Done | ||
143 | ok | ||
144 | |||
145 | ---------------------------------------------------------------------- | ||
146 | Ran 11 tests in 259.854s | ||
147 | |||
148 | OK | ||
149 | |||
150 | # Access 128T management interface | ||
151 | https://172.24.12.154:60001 | ||
152 | user: admin | ||
153 | password: 128Tadmin | ||
154 | |||
155 | # Access Fortigate management interface | ||
156 | https://172.24.12.154:60002 | ||
157 | user: admin | ||
158 | password: | ||
159 | |||
160 | |||
161 | |||
162 | Use case2 clean-up | ||
163 | > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n trgt-1 \ | ||
164 | -s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC CleanUp" | ||
165 | |||
166 | Running 128T - Fortigate SFC CleanUp... | ||
167 | |||
168 | test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ... | ||
169 | 2019-08-13 13:51:30,204 - INFO: Destroy VNF | ||
170 | 2019-08-13 13:51:31,781 - INFO: Done | ||
171 | ok | ||
172 | test 002: Destroying 128T VNF (__main__.UnittestSuite) ... | ||
173 | 2019-08-13 13:51:31,822 - INFO: Destroy VNF | ||
174 | 2019-08-13 13:51:32,729 - INFO: Done | ||
175 | ok | ||
176 | test 003: Deleting network bridge SFC (__main__.UnittestSuite) ... | ||
177 | 2019-08-13 13:51:32,756 - INFO: Delete OVS network bridge | ||
178 | 2019-08-13 13:51:42,863 - INFO: Done | ||
179 | ok | ||
180 | test 004: Deleting network bridge LAN (__main__.UnittestSuite) ... | ||
181 | 2019-08-13 13:51:42,878 - INFO: Delete OVS network bridge | ||
182 | 2019-08-13 13:51:53,087 - INFO: Done | ||
183 | ok | ||
184 | test 005: Deleting VNF management bridge (__main__.UnittestSuite) ... | ||
185 | 2019-08-13 13:51:53,103 - INFO: Delete OVS network bridge | ||
186 | 2019-08-13 13:52:03,251 - INFO: Done | ||
187 | ok | ||
188 | test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ... | ||
189 | 2019-08-13 13:52:03,269 - INFO: Delete OVS network bridge | ||
190 | 2019-08-13 13:52:29,868 - INFO: Done | ||
191 | ok | ||
192 | test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ... | ||
193 | 2019-08-13 13:52:29,885 - INFO: Unbind NIC | ||
194 | 2019-08-13 13:52:31,415 - INFO: Done | ||
195 | ok | ||
196 | test 008: Offboarding 128t VNF (__main__.UnittestSuite) ... | ||
197 | 2019-08-13 13:52:31,435 - INFO: Offboard VNF | ||
198 | 2019-08-13 13:52:32,009 - INFO: Done | ||
199 | ok | ||
200 | test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ... | ||
201 | 2019-08-13 13:52:32,023 - INFO: Offboard VNF | ||
202 | 2019-08-13 13:52:32,157 - INFO: Done | ||
203 | ok | ||
204 | test 010: Remove VCPE Agent trgt-1 device (__main__.UnittestSuite) ... | ||
205 | 2019-08-13 13:52:32,170 - INFO: Remove uCPE device | ||
206 | 2019-08-13 13:52:32,294 - INFO: Done | ||
207 | ok | ||
208 | |||
209 | ---------------------------------------------------------------------- | ||
210 | Ran 10 tests in 62.104s | ||
211 | |||
212 | OK</programlisting> | ||
213 | </appendix> \ No newline at end of file | ||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml index fb9db8d..e3e6adc 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml | |||
@@ -27,6 +27,27 @@ | |||
27 | <xi:include href="forti_vnf_examples.xml" | 27 | <xi:include href="forti_vnf_examples.xml" |
28 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | 28 | xmlns:xi="http://www.w3.org/2001/XInclude" /> |
29 | 29 | ||
30 | <xi:include href="128t_vnf_router.xml" | ||
31 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
32 | |||
30 | <xi:include href="vnf_chaining.xml" | 33 | <xi:include href="vnf_chaining.xml" |
31 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | 34 | xmlns:xi="http://www.w3.org/2001/XInclude" /> |
35 | |||
36 | <xi:include href="service_chaining_128t_fortigate.xml" | ||
37 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
38 | |||
39 | <xi:include href="appendix_1.xml" | ||
40 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
41 | |||
42 | <xi:include href="appendix_2.xml" | ||
43 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
44 | |||
45 | <xi:include href="appendix_3.xml" | ||
46 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
47 | |||
48 | <xi:include href="appendix_4.xml" | ||
49 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
50 | |||
51 | <xi:include href="appendix_5.xml" | ||
52 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
32 | </book> | 53 | </book> |
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png new file mode 100644 index 0000000..2c1c908 --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png new file mode 100644 index 0000000..3956c9d --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml new file mode 100644 index 0000000..15329e7 --- /dev/null +++ b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml | |||
@@ -0,0 +1,1065 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <chapter id="service_chaining_128t_fortigate"> | ||
3 | <title>Service Chaining 128T - Fortigate Example Use-case</title> | ||
4 | |||
5 | <para>The term service chaining or service function chaining (SFC) is used | ||
6 | to describe the definition and instantiation of an ordered list of instances | ||
7 | of such service functions and the subsequent "steering" of traffic flows | ||
8 | through those service functions. The set of enabled service function chains | ||
9 | reflects operator service offerings and is designed in conjunction with | ||
10 | application delivery and service and network policy.</para> | ||
11 | |||
12 | <section id="prereq_serv_chain_cust"> | ||
13 | <title>Prerequisites</title> | ||
14 | |||
15 | <para>The 128T router and the Fortinet firewall in a service chain require | ||
16 | the following prequisites for this example use case:</para> | ||
17 | |||
18 | <itemizedlist spacing="compact"> | ||
19 | <listitem> | ||
20 | <para>1 in band management port for device management.</para> | ||
21 | </listitem> | ||
22 | |||
23 | <listitem> | ||
24 | <para>1 in band management port for the 128T router.</para> | ||
25 | </listitem> | ||
26 | |||
27 | <listitem> | ||
28 | <para>1 in band management port for Fortinet.</para> | ||
29 | </listitem> | ||
30 | |||
31 | <listitem> | ||
32 | <para>1 WAN interface for Fortinet.</para> | ||
33 | </listitem> | ||
34 | |||
35 | <listitem> | ||
36 | <para>1 LAN facing interface for Fortinet.</para> | ||
37 | </listitem> | ||
38 | |||
39 | <listitem> | ||
40 | <para>1 WAN facing interface for the 128T router.</para> | ||
41 | </listitem> | ||
42 | |||
43 | <listitem> | ||
44 | <para>1 service chain (SFC Bridged interface) to sit between the | ||
45 | Firewall and vRouter.</para> | ||
46 | </listitem> | ||
47 | </itemizedlist> | ||
48 | </section> | ||
49 | |||
50 | <section id="ser_chain_uc"> | ||
51 | <title>Service Chaining 128T - Fortigate</title> | ||
52 | |||
53 | <figure> | ||
54 | <title>Service Chaining 128T - Fortigate Setup Overview</title> | ||
55 | |||
56 | <mediaobject> | ||
57 | <imageobject> | ||
58 | <imagedata contentwidth="600" | ||
59 | fileref="images/trgt_servicechain.png" /> | ||
60 | </imageobject> | ||
61 | </mediaobject> | ||
62 | </figure> | ||
63 | |||
64 | <section> | ||
65 | <title>Use-case Setup</title> | ||
66 | |||
67 | <para><emphasis role="bold">Configuring Network Interfaces on uCPE | ||
68 | devices:</emphasis><orderedlist> | ||
69 | <listitem> | ||
70 | <para>Log into the uCPE Manager with both username and password | ||
71 | values: <literal>admin</literal>.</para> | ||
72 | </listitem> | ||
73 | |||
74 | <listitem> | ||
75 | <para>Add the trgt uCPE device into the uCPE Manager: | ||
76 | <literal>Devices -> Manage -> Add</literal>.</para> | ||
77 | |||
78 | <para>Fill in the required fields with the following data:</para> | ||
79 | |||
80 | <table> | ||
81 | <title>Device Details</title> | ||
82 | |||
83 | <tgroup cols="2"> | ||
84 | <colspec align="left" /> | ||
85 | |||
86 | <colspec colwidth="2*" /> | ||
87 | |||
88 | <colspec colwidth="5*" /> | ||
89 | |||
90 | <thead> | ||
91 | <row> | ||
92 | <entry align="center">Field</entry> | ||
93 | |||
94 | <entry align="center">Value</entry> | ||
95 | </row> | ||
96 | </thead> | ||
97 | |||
98 | <tbody> | ||
99 | <row> | ||
100 | <entry>Type</entry> | ||
101 | |||
102 | <entry>Enea universal CPE</entry> | ||
103 | </row> | ||
104 | |||
105 | <row> | ||
106 | <entry>Release</entry> | ||
107 | |||
108 | <entry>1.0</entry> | ||
109 | </row> | ||
110 | |||
111 | <row> | ||
112 | <entry>Name</entry> | ||
113 | |||
114 | <entry>trgt</entry> | ||
115 | </row> | ||
116 | |||
117 | <row> | ||
118 | <entry>IP/DNS Address</entry> | ||
119 | |||
120 | <entry>Dynamic IP received by device from DHCP server | ||
121 | (E.g.: 172.24.12.74).</entry> | ||
122 | </row> | ||
123 | |||
124 | <row> | ||
125 | <entry>Description</entry> | ||
126 | |||
127 | <entry>Target 1</entry> | ||
128 | </row> | ||
129 | |||
130 | <row> | ||
131 | <entry>SSH Port</entry> | ||
132 | |||
133 | <entry>830</entry> | ||
134 | </row> | ||
135 | |||
136 | <row> | ||
137 | <entry>SSH User Name</entry> | ||
138 | |||
139 | <entry>root</entry> | ||
140 | </row> | ||
141 | |||
142 | <row> | ||
143 | <entry>Password</entry> | ||
144 | |||
145 | <entry>null</entry> | ||
146 | </row> | ||
147 | |||
148 | <row> | ||
149 | <entry>OK</entry> | ||
150 | |||
151 | <entry>Green status indicates connection with uCPE device | ||
152 | was established.</entry> | ||
153 | </row> | ||
154 | </tbody> | ||
155 | </tgroup> | ||
156 | </table> | ||
157 | </listitem> | ||
158 | |||
159 | <listitem> | ||
160 | <para>In order to add the device on the map: Right-Click on | ||
161 | <literal>Map -> Place Device -> trgt</literal>.</para> | ||
162 | </listitem> | ||
163 | |||
164 | <listitem> | ||
165 | <para>Configure the infrastructure for the 128T and Fortigate VNFs | ||
166 | in the service chain by creating four OVS bridges and a host | ||
167 | interface.</para> | ||
168 | |||
169 | <para>Add the Host Interface by selecting the trgt device, then | ||
170 | <literal>Configuration -> OpenVSwitch -> Host Interfaces | ||
171 | -> Add</literal>.</para> | ||
172 | |||
173 | <para>Fill in the required fields with the following data:</para> | ||
174 | |||
175 | <table> | ||
176 | <title>Host Interface Details</title> | ||
177 | |||
178 | <tgroup cols="2"> | ||
179 | <colspec align="left" /> | ||
180 | |||
181 | <colspec colwidth="2*" /> | ||
182 | |||
183 | <colspec colwidth="5*" /> | ||
184 | |||
185 | <thead> | ||
186 | <row> | ||
187 | <entry align="center">Field</entry> | ||
188 | |||
189 | <entry align="center">Value</entry> | ||
190 | </row> | ||
191 | </thead> | ||
192 | |||
193 | <tbody> | ||
194 | <row> | ||
195 | <entry>Source</entry> | ||
196 | |||
197 | <entry><literal>enp4s0f1</literal>. The only interface | ||
198 | available for LAN connection.</entry> | ||
199 | </row> | ||
200 | |||
201 | <row> | ||
202 | <entry>type</entry> | ||
203 | |||
204 | <entry>dpdk</entry> | ||
205 | </row> | ||
206 | |||
207 | <row> | ||
208 | <entry>networking-type</entry> | ||
209 | |||
210 | <entry>dpdk</entry> | ||
211 | </row> | ||
212 | |||
213 | <row> | ||
214 | <entry>dpdk-type</entry> | ||
215 | |||
216 | <entry>vfio-pci</entry> | ||
217 | </row> | ||
218 | |||
219 | <row> | ||
220 | <entry>Create</entry> | ||
221 | |||
222 | <entry><interface enp4s0f1 ready to be used in a LAN | ||
223 | bridge.></entry> | ||
224 | </row> | ||
225 | </tbody> | ||
226 | </tgroup> | ||
227 | </table> | ||
228 | |||
229 | <para>Add the OVS bridges by selecting the trgt device then: | ||
230 | <literal>Configuration -> OpenVSwitch -> Bridges -> | ||
231 | Add</literal>.</para> | ||
232 | |||
233 | <para>Fill in the required fields for each bridge with the | ||
234 | following data from each table:</para> | ||
235 | |||
236 | <table> | ||
237 | <title>ibm_br Bridge Details</title> | ||
238 | |||
239 | <tgroup cols="2"> | ||
240 | <colspec align="left" /> | ||
241 | |||
242 | <colspec colwidth="2*" /> | ||
243 | |||
244 | <colspec colwidth="5*" /> | ||
245 | |||
246 | <thead> | ||
247 | <row> | ||
248 | <entry align="center">Field</entry> | ||
249 | |||
250 | <entry align="center">Value</entry> | ||
251 | </row> | ||
252 | </thead> | ||
253 | |||
254 | <tbody> | ||
255 | <row> | ||
256 | <entry>id</entry> | ||
257 | |||
258 | <entry><autogenerated - do not change></entry> | ||
259 | </row> | ||
260 | |||
261 | <row> | ||
262 | <entry>Name</entry> | ||
263 | |||
264 | <entry><literal>ibm_br</literal></entry> | ||
265 | </row> | ||
266 | |||
267 | <row> | ||
268 | <entry>ovs-bridge-type</entry> | ||
269 | |||
270 | <entry>inbandMgmt</entry> | ||
271 | </row> | ||
272 | |||
273 | <row> | ||
274 | <entry>mgmt-address</entry> | ||
275 | |||
276 | <entry>Provide the IP address of the uCPE Manager machine | ||
277 | (E.g. 172.24.3.109).</entry> | ||
278 | </row> | ||
279 | |||
280 | <row> | ||
281 | <entry>mgmt-port</entry> | ||
282 | |||
283 | <entry>830</entry> | ||
284 | </row> | ||
285 | |||
286 | <row> | ||
287 | <entry>Create</entry> | ||
288 | |||
289 | <entry></entry> | ||
290 | </row> | ||
291 | </tbody> | ||
292 | </tgroup> | ||
293 | </table> | ||
294 | |||
295 | <table> | ||
296 | <title>vnf_mgmt_br Bridge Details</title> | ||
297 | |||
298 | <tgroup cols="2"> | ||
299 | <colspec align="left" /> | ||
300 | |||
301 | <colspec colwidth="2*" /> | ||
302 | |||
303 | <colspec colwidth="5*" /> | ||
304 | |||
305 | <thead> | ||
306 | <row> | ||
307 | <entry align="center">Field</entry> | ||
308 | |||
309 | <entry align="center">Value</entry> | ||
310 | </row> | ||
311 | </thead> | ||
312 | |||
313 | <tbody> | ||
314 | <row> | ||
315 | <entry>id</entry> | ||
316 | |||
317 | <entry><autogenerated - do not change></entry> | ||
318 | </row> | ||
319 | |||
320 | <row> | ||
321 | <entry>Name</entry> | ||
322 | |||
323 | <entry><literal>vnf_mgmt_br</literal></entry> | ||
324 | </row> | ||
325 | |||
326 | <row> | ||
327 | <entry>ovs-bridge-type</entry> | ||
328 | |||
329 | <entry>vnfMgmt</entry> | ||
330 | </row> | ||
331 | |||
332 | <row> | ||
333 | <entry>vnf-mgmt-address</entry> | ||
334 | |||
335 | <entry>10.0.0.1</entry> | ||
336 | </row> | ||
337 | |||
338 | <row> | ||
339 | <entry>Create</entry> | ||
340 | |||
341 | <entry></entry> | ||
342 | </row> | ||
343 | </tbody> | ||
344 | </tgroup> | ||
345 | </table> | ||
346 | |||
347 | <table> | ||
348 | <title>lan_br Bridge Details</title> | ||
349 | |||
350 | <tgroup cols="2"> | ||
351 | <colspec align="left" /> | ||
352 | |||
353 | <colspec colwidth="2*" /> | ||
354 | |||
355 | <colspec colwidth="5*" /> | ||
356 | |||
357 | <thead> | ||
358 | <row> | ||
359 | <entry align="center">Field</entry> | ||
360 | |||
361 | <entry align="center">Value</entry> | ||
362 | </row> | ||
363 | </thead> | ||
364 | |||
365 | <tbody> | ||
366 | <row> | ||
367 | <entry>id</entry> | ||
368 | |||
369 | <entry><autogenerated - do not change></entry> | ||
370 | </row> | ||
371 | |||
372 | <row> | ||
373 | <entry>Name</entry> | ||
374 | |||
375 | <entry><literal>lan_br</literal></entry> | ||
376 | </row> | ||
377 | |||
378 | <row> | ||
379 | <entry>ovs-bridge-type</entry> | ||
380 | |||
381 | <entry>dataPlane</entry> | ||
382 | </row> | ||
383 | |||
384 | <row> | ||
385 | <entry>sub-type</entry> | ||
386 | |||
387 | <entry>communication</entry> | ||
388 | </row> | ||
389 | |||
390 | <row> | ||
391 | <entry>+</entry> | ||
392 | |||
393 | <entry>Name: enp4s0f1 OK</entry> | ||
394 | </row> | ||
395 | |||
396 | <row> | ||
397 | <entry>Create</entry> | ||
398 | |||
399 | <entry></entry> | ||
400 | </row> | ||
401 | </tbody> | ||
402 | </tgroup> | ||
403 | </table> | ||
404 | |||
405 | <table> | ||
406 | <title>sfc_br Bridge Details</title> | ||
407 | |||
408 | <tgroup cols="2"> | ||
409 | <colspec align="left" /> | ||
410 | |||
411 | <colspec colwidth="2*" /> | ||
412 | |||
413 | <colspec colwidth="5*" /> | ||
414 | |||
415 | <thead> | ||
416 | <row> | ||
417 | <entry align="center">Field</entry> | ||
418 | |||
419 | <entry align="center">Value</entry> | ||
420 | </row> | ||
421 | </thead> | ||
422 | |||
423 | <tbody> | ||
424 | <row> | ||
425 | <entry>id</entry> | ||
426 | |||
427 | <entry><autogenerated - do not change></entry> | ||
428 | </row> | ||
429 | |||
430 | <row> | ||
431 | <entry>Name</entry> | ||
432 | |||
433 | <entry><literal>sfc_br</literal></entry> | ||
434 | </row> | ||
435 | |||
436 | <row> | ||
437 | <entry>ovs-bridge-type</entry> | ||
438 | |||
439 | <entry>dataPlane</entry> | ||
440 | </row> | ||
441 | |||
442 | <row> | ||
443 | <entry>sub-type</entry> | ||
444 | |||
445 | <entry>integration</entry> | ||
446 | </row> | ||
447 | |||
448 | <row> | ||
449 | <entry>Create</entry> | ||
450 | |||
451 | <entry></entry> | ||
452 | </row> | ||
453 | </tbody> | ||
454 | </tgroup> | ||
455 | </table> | ||
456 | </listitem> | ||
457 | </orderedlist></para> | ||
458 | |||
459 | <para><emphasis role="bold">Onboarding the VNFs:</emphasis></para> | ||
460 | |||
461 | <para>Onboard the 128T VNF VM Image through <literal>VNF -> | ||
462 | Descriptors -> On-board -> VM Image</literal>, and fill in the | ||
463 | required fields with the following values:</para> | ||
464 | |||
465 | <table> | ||
466 | <title>128T VM Image Details</title> | ||
467 | |||
468 | <tgroup cols="2"> | ||
469 | <colspec align="left" /> | ||
470 | |||
471 | <colspec colwidth="2*" /> | ||
472 | |||
473 | <colspec colwidth="5*" /> | ||
474 | |||
475 | <thead> | ||
476 | <row> | ||
477 | <entry align="center">Field</entry> | ||
478 | |||
479 | <entry align="center">Value</entry> | ||
480 | </row> | ||
481 | </thead> | ||
482 | |||
483 | <tbody> | ||
484 | <row> | ||
485 | <entry>VM image file</entry> | ||
486 | |||
487 | <entry><literal>centos_128t_with_ci.qcow2</literal></entry> | ||
488 | </row> | ||
489 | |||
490 | <row> | ||
491 | <entry>Image format</entry> | ||
492 | |||
493 | <entry>QCOW2</entry> | ||
494 | </row> | ||
495 | |||
496 | <row> | ||
497 | <entry>VNF Type Name</entry> | ||
498 | |||
499 | <entry>128T</entry> | ||
500 | </row> | ||
501 | |||
502 | <row> | ||
503 | <entry>Description</entry> | ||
504 | |||
505 | <entry>128T Router</entry> | ||
506 | </row> | ||
507 | |||
508 | <row> | ||
509 | <entry>Version</entry> | ||
510 | |||
511 | <entry>1.0</entry> | ||
512 | </row> | ||
513 | |||
514 | <row> | ||
515 | <entry>Memory in MB</entry> | ||
516 | |||
517 | <entry>8192. More memory can be allocated if required | ||
518 | (<28672).</entry> | ||
519 | </row> | ||
520 | |||
521 | <row> | ||
522 | <entry>Num. of CPUs</entry> | ||
523 | |||
524 | <entry>2. More CPUs can be reserved if required | ||
525 | (<15).</entry> | ||
526 | </row> | ||
527 | |||
528 | <row> | ||
529 | <entry>Interfaces -> +</entry> | ||
530 | |||
531 | <entry>Name: mgmt</entry> | ||
532 | </row> | ||
533 | |||
534 | <row> | ||
535 | <entry>Interfaces -> +</entry> | ||
536 | |||
537 | <entry>Name: wan</entry> | ||
538 | </row> | ||
539 | |||
540 | <row> | ||
541 | <entry>Interfaces -> +</entry> | ||
542 | |||
543 | <entry>Name: lan</entry> | ||
544 | </row> | ||
545 | |||
546 | <row> | ||
547 | <entry>Cloud Init -> Cloud-Init Datasource</entry> | ||
548 | |||
549 | <entry>ISO</entry> | ||
550 | </row> | ||
551 | |||
552 | <row> | ||
553 | <entry>Cloud Init -> Cloud-Init Disk Type</entry> | ||
554 | |||
555 | <entry>cdrom</entry> | ||
556 | </row> | ||
557 | |||
558 | <row> | ||
559 | <entry>Properties -> +</entry> | ||
560 | |||
561 | <entry>Name: vnfMgmtIpAddress. Value: 10.0.0.2</entry> | ||
562 | </row> | ||
563 | |||
564 | <row> | ||
565 | <entry>Properties -> +</entry> | ||
566 | |||
567 | <entry>Name: internalMgmtPort. Value: 443</entry> | ||
568 | </row> | ||
569 | |||
570 | <row> | ||
571 | <entry>Properties -> +</entry> | ||
572 | |||
573 | <entry>Name: externalMgmtPort. Value: 60001</entry> | ||
574 | </row> | ||
575 | |||
576 | <row> | ||
577 | <entry>Onboard</entry> | ||
578 | |||
579 | <entry><Wait for message: VNF package onboarded | ||
580 | successfully></entry> | ||
581 | </row> | ||
582 | |||
583 | <row> | ||
584 | <entry>Close</entry> | ||
585 | |||
586 | <entry></entry> | ||
587 | </row> | ||
588 | </tbody> | ||
589 | </tgroup> | ||
590 | </table> | ||
591 | |||
592 | <note> | ||
593 | <itemizedlist> | ||
594 | <listitem> | ||
595 | <para>HTTPS access (443) can be changed to another type of access. | ||
596 | Please consult official 128T documentation and make sure the 128T | ||
597 | VNF is configured to accept another type of connection before | ||
598 | changing the port number.</para> | ||
599 | </listitem> | ||
600 | |||
601 | <listitem> | ||
602 | <para><literal>externalMgmtPort(60001)</literal> represents the | ||
603 | external port on which the user can access the VNF management | ||
604 | interface from the web browser via HTTPS. The user can select | ||
605 | another port if needed. There are no other changes required or | ||
606 | components affected by this change.</para> | ||
607 | </listitem> | ||
608 | |||
609 | <listitem> | ||
610 | <para><literal>vnfMgmtIpAddress</literal> (10.0.0.2) represents | ||
611 | the IP address of the management interface of the 128T VNF. | ||
612 | Changing this value requires an update to the 128T configuration | ||
613 | to match the new IP address.</para> | ||
614 | </listitem> | ||
615 | </itemizedlist> | ||
616 | </note> | ||
617 | |||
618 | <para>Onboard the Fortigate VNF VM Image through <literal>VNF -> | ||
619 | Descriptors -> On-board -> VM Image</literal>, and fill in the | ||
620 | required fields with the following values:</para> | ||
621 | |||
622 | <table> | ||
623 | <title>Fortigate VM Image Details</title> | ||
624 | |||
625 | <tgroup cols="2"> | ||
626 | <colspec align="left" /> | ||
627 | |||
628 | <colspec colwidth="2*" /> | ||
629 | |||
630 | <colspec colwidth="5*" /> | ||
631 | |||
632 | <thead> | ||
633 | <row> | ||
634 | <entry align="center">Field</entry> | ||
635 | |||
636 | <entry align="center">Value</entry> | ||
637 | </row> | ||
638 | </thead> | ||
639 | |||
640 | <tbody> | ||
641 | <row> | ||
642 | <entry>VM image file</entry> | ||
643 | |||
644 | <entry><literal>fortios.qcow2</literal>. Please make sure to | ||
645 | contact Fortigate for an official Fortigate KVM image.</entry> | ||
646 | </row> | ||
647 | |||
648 | <row> | ||
649 | <entry>Image format</entry> | ||
650 | |||
651 | <entry>QCOW2</entry> | ||
652 | </row> | ||
653 | |||
654 | <row> | ||
655 | <entry>VNF Type Name</entry> | ||
656 | |||
657 | <entry>Fortigate</entry> | ||
658 | </row> | ||
659 | |||
660 | <row> | ||
661 | <entry>Description</entry> | ||
662 | |||
663 | <entry>Fortigate VNF</entry> | ||
664 | </row> | ||
665 | |||
666 | <row> | ||
667 | <entry>Version</entry> | ||
668 | |||
669 | <entry>1.0</entry> | ||
670 | </row> | ||
671 | |||
672 | <row> | ||
673 | <entry>Memory in MB</entry> | ||
674 | |||
675 | <entry>1024. More memory can be allocated if required | ||
676 | (<28672).</entry> | ||
677 | </row> | ||
678 | |||
679 | <row> | ||
680 | <entry>Num. of CPUs</entry> | ||
681 | |||
682 | <entry>1. More CPUs can be reserved if required | ||
683 | (<15).</entry> | ||
684 | </row> | ||
685 | |||
686 | <row> | ||
687 | <entry>Interfaces -> +</entry> | ||
688 | |||
689 | <entry>Name: mgmt</entry> | ||
690 | </row> | ||
691 | |||
692 | <row> | ||
693 | <entry>Interfaces -> +</entry> | ||
694 | |||
695 | <entry>Name: wan</entry> | ||
696 | </row> | ||
697 | |||
698 | <row> | ||
699 | <entry>Interfaces -> +</entry> | ||
700 | |||
701 | <entry>Name: lan</entry> | ||
702 | </row> | ||
703 | |||
704 | <row> | ||
705 | <entry>Cloud Init -> Cloud-Init Datasource</entry> | ||
706 | |||
707 | <entry>ConfigDrive</entry> | ||
708 | </row> | ||
709 | |||
710 | <row> | ||
711 | <entry>Cloud Init -> Cloud-Init Disk Type</entry> | ||
712 | |||
713 | <entry>cdrom</entry> | ||
714 | </row> | ||
715 | |||
716 | <row> | ||
717 | <entry>Cloud Init -> +</entry> | ||
718 | |||
719 | <entry>Path: license</entry> | ||
720 | </row> | ||
721 | |||
722 | <row> | ||
723 | <entry>Properties -> +</entry> | ||
724 | |||
725 | <entry>Name: vnfMgmtIpAddress. Value: 10.0.0.3</entry> | ||
726 | </row> | ||
727 | |||
728 | <row> | ||
729 | <entry>Properties -> +</entry> | ||
730 | |||
731 | <entry>Name: internalMgmtPort. Value: 443</entry> | ||
732 | </row> | ||
733 | |||
734 | <row> | ||
735 | <entry>Properties -> +</entry> | ||
736 | |||
737 | <entry>Name: externalMgmtPort. Value: 60002</entry> | ||
738 | </row> | ||
739 | |||
740 | <row> | ||
741 | <entry>Onboard</entry> | ||
742 | |||
743 | <entry><Wait for message: VNF package onboarded | ||
744 | successfully></entry> | ||
745 | </row> | ||
746 | |||
747 | <row> | ||
748 | <entry>Close</entry> | ||
749 | |||
750 | <entry></entry> | ||
751 | </row> | ||
752 | </tbody> | ||
753 | </tgroup> | ||
754 | </table> | ||
755 | |||
756 | <note> | ||
757 | <itemizedlist> | ||
758 | <listitem> | ||
759 | <para>HTTPS access (443) can be changed to another type of access. | ||
760 | Please consult official Fortigate documentation and make sure the | ||
761 | Fortigate VNF is configured to accept another type of connection | ||
762 | before changing the port number.</para> | ||
763 | </listitem> | ||
764 | |||
765 | <listitem> | ||
766 | <para><literal>externalMgmtPort</literal> (60002) represents the | ||
767 | external port on which the user can access the VNF management | ||
768 | interface from the web browser via HTTPS. The user can select | ||
769 | another port if needed. There are no other changes required or | ||
770 | components affected by this change.</para> | ||
771 | </listitem> | ||
772 | |||
773 | <listitem> | ||
774 | <para><literal>vnfMgmtIpAddress</literal> (10.0.0.3) represents | ||
775 | the IP address of the management interface of the Fortigate VNF. | ||
776 | Changing this value requires an update to the Fortigate | ||
777 | configuration to match with new IP address.</para> | ||
778 | </listitem> | ||
779 | </itemizedlist> | ||
780 | </note> | ||
781 | |||
782 | <para><emphasis role="bold">Instantiating the VNFs:</emphasis></para> | ||
783 | |||
784 | <para>Instantiate the 128T VNF by selecting the trgt device, then | ||
785 | <literal>VNF -> Instances -> Add</literal>.</para> | ||
786 | |||
787 | <para>Fill in the required fields with the following values:</para> | ||
788 | |||
789 | <table> | ||
790 | <title>128T VNF Instantiation</title> | ||
791 | |||
792 | <tgroup cols="2"> | ||
793 | <colspec align="left" /> | ||
794 | |||
795 | <colspec colwidth="2*" /> | ||
796 | |||
797 | <colspec colwidth="5*" /> | ||
798 | |||
799 | <thead> | ||
800 | <row> | ||
801 | <entry align="center">Field</entry> | ||
802 | |||
803 | <entry align="center">Value</entry> | ||
804 | </row> | ||
805 | </thead> | ||
806 | |||
807 | <tbody> | ||
808 | <row> | ||
809 | <entry>Name</entry> | ||
810 | |||
811 | <entry>128T_trgt_1</entry> | ||
812 | </row> | ||
813 | |||
814 | <row> | ||
815 | <entry>VNF Type</entry> | ||
816 | |||
817 | <entry>128T</entry> | ||
818 | </row> | ||
819 | |||
820 | <row> | ||
821 | <entry>VNFD Version</entry> | ||
822 | |||
823 | <entry>1.0</entry> | ||
824 | </row> | ||
825 | |||
826 | <row> | ||
827 | <entry>Flavour</entry> | ||
828 | |||
829 | <entry>Canonical</entry> | ||
830 | </row> | ||
831 | |||
832 | <row> | ||
833 | <entry>uCPE Device</entry> | ||
834 | |||
835 | <entry>trgt</entry> | ||
836 | </row> | ||
837 | |||
838 | <row> | ||
839 | <entry>Cloud Init File</entry> | ||
840 | |||
841 | <entry><literal>centos_128t_internet_ci.iso</literal>. Example | ||
842 | image provided. Please see Appendix A for details on how to | ||
843 | change the configuration and create a new cloud-init iso | ||
844 | image.</entry> | ||
845 | </row> | ||
846 | |||
847 | <row> | ||
848 | <entry>Domain Update Script</entry> | ||
849 | |||
850 | <entry></entry> | ||
851 | </row> | ||
852 | |||
853 | <row> | ||
854 | <entry>Interfaces</entry> | ||
855 | |||
856 | <entry></entry> | ||
857 | </row> | ||
858 | |||
859 | <row> | ||
860 | <entry>ID</entry> | ||
861 | |||
862 | <entry>IF Name</entry> | ||
863 | </row> | ||
864 | |||
865 | <row> | ||
866 | <entry>mgmt (dpdk)</entry> | ||
867 | |||
868 | <entry>Bridge: vnf_mgmt_br</entry> | ||
869 | </row> | ||
870 | |||
871 | <row> | ||
872 | <entry>wan (dpdk)</entry> | ||
873 | |||
874 | <entry>Bridge: ibm_br</entry> | ||
875 | </row> | ||
876 | |||
877 | <row> | ||
878 | <entry>lan (dpdk)</entry> | ||
879 | |||
880 | <entry>Bridge: sfc_br</entry> | ||
881 | </row> | ||
882 | |||
883 | <row> | ||
884 | <entry>Create</entry> | ||
885 | |||
886 | <entry></entry> | ||
887 | </row> | ||
888 | </tbody> | ||
889 | </tgroup> | ||
890 | </table> | ||
891 | |||
892 | <para>Instantiate the Fortigate VNF by selecting the trgt device, then | ||
893 | <literal>VNF -> Instances -> Add</literal>.</para> | ||
894 | |||
895 | <para>Fill in the required fields with the following values:</para> | ||
896 | |||
897 | <table> | ||
898 | <title>Fortigate VNF Instantiation</title> | ||
899 | |||
900 | <tgroup cols="2"> | ||
901 | <colspec align="left" /> | ||
902 | |||
903 | <colspec colwidth="2*" /> | ||
904 | |||
905 | <colspec colwidth="5*" /> | ||
906 | |||
907 | <thead> | ||
908 | <row> | ||
909 | <entry align="center">Field</entry> | ||
910 | |||
911 | <entry align="center">Value</entry> | ||
912 | </row> | ||
913 | </thead> | ||
914 | |||
915 | <tbody> | ||
916 | <row> | ||
917 | <entry>Name</entry> | ||
918 | |||
919 | <entry>fg_trgt_1</entry> | ||
920 | </row> | ||
921 | |||
922 | <row> | ||
923 | <entry>VNF Type</entry> | ||
924 | |||
925 | <entry>Fortigate</entry> | ||
926 | </row> | ||
927 | |||
928 | <row> | ||
929 | <entry>VNFD Version</entry> | ||
930 | |||
931 | <entry>1.0</entry> | ||
932 | </row> | ||
933 | |||
934 | <row> | ||
935 | <entry>Flavour</entry> | ||
936 | |||
937 | <entry>Canonical</entry> | ||
938 | </row> | ||
939 | |||
940 | <row> | ||
941 | <entry>uCPE Device</entry> | ||
942 | |||
943 | <entry>trgt</entry> | ||
944 | </row> | ||
945 | |||
946 | <row> | ||
947 | <entry>Cloud Init File</entry> | ||
948 | |||
949 | <entry><literal>fg_cust_basic_fw.conf</literal></entry> | ||
950 | </row> | ||
951 | |||
952 | <row> | ||
953 | <entry>License File</entry> | ||
954 | |||
955 | <entry><literal>FGVM08TM00001.lic</literal>. Please make sure to | ||
956 | use a valid license file (.lic) received from Fortinet.</entry> | ||
957 | </row> | ||
958 | |||
959 | <row> | ||
960 | <entry>Domain Update Script</entry> | ||
961 | |||
962 | <entry></entry> | ||
963 | </row> | ||
964 | |||
965 | <row> | ||
966 | <entry>Interfaces</entry> | ||
967 | |||
968 | <entry></entry> | ||
969 | </row> | ||
970 | |||
971 | <row> | ||
972 | <entry>ID</entry> | ||
973 | |||
974 | <entry>IF Name</entry> | ||
975 | </row> | ||
976 | |||
977 | <row> | ||
978 | <entry>mgmt (dpdk)</entry> | ||
979 | |||
980 | <entry>Bridge: vnf_mgmt_br</entry> | ||
981 | </row> | ||
982 | |||
983 | <row> | ||
984 | <entry>wan (dpdk)</entry> | ||
985 | |||
986 | <entry>Bridge: sfc_br</entry> | ||
987 | </row> | ||
988 | |||
989 | <row> | ||
990 | <entry>lan (dpdk)</entry> | ||
991 | |||
992 | <entry>Bridge: lan_br</entry> | ||
993 | </row> | ||
994 | |||
995 | <row> | ||
996 | <entry>Create</entry> | ||
997 | |||
998 | <entry></entry> | ||
999 | </row> | ||
1000 | </tbody> | ||
1001 | </tgroup> | ||
1002 | </table> | ||
1003 | </section> | ||
1004 | |||
1005 | <section> | ||
1006 | <title>Testing the Use-case</title> | ||
1007 | |||
1008 | <para>In order to access the web interfaces of the 128T VNF, open a | ||
1009 | browser on a machine connected on the same network with the WAN port of | ||
1010 | the target and connect to: | ||
1011 | <literal>https://<publicIP>:60001</literal> using the username: | ||
1012 | admin and the password: 128Tadmin.</para> | ||
1013 | |||
1014 | <para>In order to access the web interfaces of the Fortigate VNF, open a | ||
1015 | browser on a machine connected on the same network with the WAN port of | ||
1016 | the target and connect to: | ||
1017 | <literal>https://<publicIP>:60002</literal> using the username: | ||
1018 | admin, and leaving the password blank.</para> | ||
1019 | |||
1020 | <note> | ||
1021 | <para>Make sure the WAN interface of the trgt device has access to | ||
1022 | the internet. The Fortigate VNF requires internet access to validate | ||
1023 | the license.</para> | ||
1024 | </note> | ||
1025 | |||
1026 | <para>In order to validate the data path connect a test machine to the | ||
1027 | LAN physical port and check for a dynamic IP (the Fortigate LAN | ||
1028 | interface is configured with a DHCP server):<programlisting>> dhclient eth1 | ||
1029 | > ping 8.8.8.8</programlisting>For data path validation, a new cloud-init | ||
1030 | image may need to be generated for the 128T VNF to match your network | ||
1031 | configuration. Please check Appendix A "How to create 128T cloud-init | ||
1032 | iso image (day-0 configuration)" for details.</para> | ||
1033 | </section> | ||
1034 | |||
1035 | <section> | ||
1036 | <title>Use-case Clean-up</title> | ||
1037 | |||
1038 | <para>In order to remove the setup created in previously, all components | ||
1039 | need to be deleted in reverse order:</para> | ||
1040 | |||
1041 | <orderedlist> | ||
1042 | <listitem> | ||
1043 | <para>Select the trgt uCPE device -> VNF -> Instances. | ||
1044 | Select the 128T and Fortigate VNFs -> Delete.</para> | ||
1045 | </listitem> | ||
1046 | |||
1047 | <listitem> | ||
1048 | <para>Select the trgt uCPE device -> Configuration -> | ||
1049 | OpenVSwitch -> Bridges. Select all bridges -> Delete.</para> | ||
1050 | </listitem> | ||
1051 | |||
1052 | <listitem> | ||
1053 | <para>Select the trgt uCPE device -> Configuration -> | ||
1054 | OpenVSwitch -> Host Interfaces. Select all interfaces -> | ||
1055 | Delete.</para> | ||
1056 | </listitem> | ||
1057 | |||
1058 | <listitem> | ||
1059 | <para>VNF -> Descriptors. Select all bundles -> | ||
1060 | Offboard.</para> | ||
1061 | </listitem> | ||
1062 | </orderedlist> | ||
1063 | </section> | ||
1064 | </section> | ||
1065 | </chapter> | ||