summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormrpa <mrpa@enea.se>2019-12-19 19:47:44 +0100
committermrpa <mrpa@enea.se>2019-12-19 19:54:16 +0100
commit36cc695647da47557370eed0506f1818452e54b0 (patch)
treecea81f2d85e407a77e1a545bd743a131f1b5f838
parent65ac4bdd13860cb1d61e7369abd2d312bd8b8e25 (diff)
downloadel_releases-nfv-access-36cc695647da47557370eed0506f1818452e54b0.tar.gz
Updated Evalkit with new content and fixed errors.
Change-Id: I355640157c1d0ef4926e53dcfddfad6ac99a4152
Diffstat
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml26
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml2
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/branch_to_branch_connection.xml1107
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml10
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml64
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml52
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml1452
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml23
-rw-r--r--doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml8
9 files changed, 1560 insertions, 1184 deletions
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml
index a952493..f89372a 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml
@@ -7,19 +7,29 @@
7 7
8 <itemizedlist> 8 <itemizedlist>
9 <listitem> 9 <listitem>
10 <para>Development host with Linux shell.</para> 10 <para>Development host with a Linux shell.</para>
11 </listitem> 11 </listitem>
12 12
13 <listitem> 13 <listitem>
14 <para>The <literal>genisoimage</literal> tool installed.</para> 14 <para>The <literal>Cloud-localds</literal> tool installed.</para>
15 </listitem> 15 </listitem>
16 </itemizedlist> 16 </itemizedlist>
17 17
18 <para>Please unpack the 18 <note><para>Contact the flexiWAN VNF provider to get access to their controller and a valid token.</para></note>
19 <filename>flexiwan/flexiwan-cloud-init-example.tar.gz</filename> and check
20 the README file for more details:<programlisting>tar -zxf flexiwant-cloud-init-example.tar.gz
21cd flexiwan/cloud-init-example/ </programlisting></para>
22 19
23 <para>To generate the cloud-init iso image run the following script: 20 <para>Unpack the <filename>flexiwan/flexiwan-cloud-init-example.tar.gz</filename> and check
24 <programlisting>create_cloudinit.sh</programlisting></para> 21 the README file for more details:
22
23 <programlisting>tar -zxf flexiwant-cloud-init-example.tar.gz
24cd flexiwan/cloud-init-example/</programlisting></para>
25
26 <para>To generate the cloud-init iso image:</para>
27
28 <programlisting>
29 > create_flexiwan_cloudinit.sh &lt;token&gt;
30 > create_flexiwan_cloudinit.sh
31 > $cat token.txt
32 </programlisting>
33
34 <para>The <filename>flexiWAN_cloudinit.iso</filename> file can be used to instantiate the flexiWAN VNF on NFV Access.</para>
25</appendix> \ No newline at end of file 35</appendix> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml
index cebae0c..f1826e9 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml
@@ -21,7 +21,7 @@
21 <xi:include href="prerequisites.xml" 21 <xi:include href="prerequisites.xml"
22 xmlns:xi="http://www.w3.org/2001/XInclude" /> 22 xmlns:xi="http://www.w3.org/2001/XInclude" />
23 23
24 <xi:include href="branch_to_branch_connection.xml" 24 <xi:include href="sdwan_arch.xml"
25 xmlns:xi="http://www.w3.org/2001/XInclude" /> 25 xmlns:xi="http://www.w3.org/2001/XInclude" />
26 26
27 <xi:include href="validating_setup.xml" 27 <xi:include href="validating_setup.xml"
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/branch_to_branch_connection.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/branch_to_branch_connection.xml
deleted file mode 100644
index 3dec671..0000000
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/branch_to_branch_connection.xml
+++ /dev/null
@@ -1,1107 +0,0 @@
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<chapter id="branch_to_branch_conn">
3 <title>Branch to Branch Connection</title>
4
5 <para>The setup detailed in this chapter covers the onboarding and
6 instantiation of two VNFs on a uCPE device and connecting the networks
7 between them<remark>Is this accurate?</remark>. The FlexiWAN and pfSense
8 VNFs are connected through a service chain in this case.</para>
9
10 <para>The FlexiWAN SD-WAN and the pfSense virtual router service chain
11 connection setup is shown graphically below.<figure>
12 <title>Branch to Branch Connection Overview</title>
13
14 <mediaobject>
15 <imageobject>
16 <imagedata align="center" contentwidth="600"
17 fileref="images/br_to_br_conn_setup.png" />
18 </imageobject>
19 </mediaobject>
20 </figure>This overview contains representations the
21 following:<itemizedlist>
22 <listitem>
23 <para>1 in-band mgmt port for device management.</para>
24 </listitem>
25
26 <listitem>
27 <para>1 in-band mgmt port for pfSense.</para>
28 </listitem>
29
30 <listitem>
31 <para>1 WAN interface for FlexiWAN.</para>
32 </listitem>
33
34 <listitem>
35 <para>1 LAN facing interface for pfSense.</para>
36 </listitem>
37
38 <listitem>
39 <para>1 WAN facing interface for pfSense.</para>
40 </listitem>
41
42 <listitem>
43 <para>1 service chain (SFC Bridged interface) to sit between the
44 FlexiWAN and pfSense VNFs.</para>
45 </listitem>
46 </itemizedlist></para>
47
48 <section id="ucpe_mg_evalkit221">
49 <title>The uCPE Manager</title>
50
51 <para>To begin, a device must be added within the uCPE Manager:</para>
52
53 <orderedlist>
54 <listitem>
55 <para>Log into the uCPE manager with the username and password
56 "admin".</para>
57 </listitem>
58
59 <listitem>
60 <para>Add a uCPE device into uCPE Manager: <literal>Devices -&gt;
61 Manage -&gt; Add</literal>.</para>
62
63 <para>Use the following values to fill the required fields:</para>
64
65 <table>
66 <title></title>
67
68 <tgroup cols="2">
69 <tbody>
70 <row>
71 <entry>Type</entry>
72
73 <entry>Enea universal CPE</entry>
74 </row>
75
76 <row>
77 <entry>Release</entry>
78
79 <entry>1.0</entry>
80 </row>
81
82 <row>
83 <entry>Name</entry>
84
85 <entry>Ucpe1</entry>
86 </row>
87
88 <row>
89 <entry>IP/DNS Address</entry>
90
91 <entry>Dynamic IP received by the device from the DHCP server
92 (E.g.: 172.24.12.74).</entry>
93 </row>
94
95 <row>
96 <entry>Description</entry>
97
98 <entry>ucpe device site 1</entry>
99 </row>
100
101 <row>
102 <entry>SSH</entry>
103
104 <entry>Port 830</entry>
105 </row>
106
107 <row>
108 <entry>SSH User Name</entry>
109
110 <entry>root</entry>
111 </row>
112
113 <row>
114 <entry>Password</entry>
115
116 <entry></entry>
117 </row>
118
119 <row>
120 <entry>OK</entry>
121
122 <entry><itemizedlist>
123 <listitem>
124 <para>Green status indicates connection with target was
125 established.</para>
126 </listitem>
127
128 <listitem>
129 <para>In order to add a device on the map: Right-Click
130 on the <literal>Map -&gt; Place Device -&gt;
131 ucpe1</literal></para>
132 </listitem>
133 </itemizedlist></entry>
134 </row>
135 </tbody>
136 </tgroup>
137 </table>
138 </listitem>
139 </orderedlist>
140 </section>
141
142 <section id="flexiwan_vnf">
143 <title>Onboarding the FlexiWAN VNF</title>
144
145 <para>After adding a device in the uCPE Manager, a VNF must be onboarded:
146 <literal>VNF -&gt; Descriptors -&gt; On-board -&gt; VM
147 Image</literal>.</para>
148
149 <para>Use the following values to fill the required fields:</para>
150
151 <table>
152 <tgroup cols="2">
153 <tbody>
154 <row>
155 <entry>VM image file</entry>
156
157 <entry>
158 <literal>flexiwan.qcow2</literal>
159 </entry>
160 </row>
161
162 <row>
163 <entry>Image format</entry>
164
165 <entry>QCOW2</entry>
166 </row>
167
168 <row>
169 <entry>VNF Type Name</entry>
170
171 <entry>flexiWAN</entry>
172 </row>
173
174 <row>
175 <entry>Description</entry>
176
177 <entry>Flexiwan VNF</entry>
178 </row>
179
180 <row>
181 <entry>Version</entry>
182
183 <entry>1.0</entry>
184 </row>
185
186 <row>
187 <entry>Memory in MB</entry>
188
189 <entry>4096 - More memory can be allocated if required.</entry>
190 </row>
191
192 <row>
193 <entry>Num of CPUs</entry>
194
195 <entry>2. More CPUs can be reserved if required and
196 available.</entry>
197 </row>
198
199 <row>
200 <entry>Interfaces to add:</entry>
201
202 <entry>wan and lan</entry>
203 </row>
204
205 <row>
206 <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>
207
208 <entry>ISO</entry>
209 </row>
210
211 <row>
212 <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>
213
214 <entry>cdrom</entry>
215 </row>
216
217 <row>
218 <entry>Onboard</entry>
219
220 <entry>Wait for the message: "VNF package onboarded successfully"
221 then close the pop-up.</entry>
222 </row>
223 </tbody>
224 </tgroup>
225 </table>
226 </section>
227
228 <section id="pfsense_vnf">
229 <title>Onboarding the pfSense VNF</title>
230
231 <para>After onboarding the first VNF, follow the same steps to add the
232 second: <literal>VNF -&gt; Descriptors -&gt; On-board -&gt; VM
233 Image</literal>.</para>
234
235 <para>Use the following values to fill the required fields:</para>
236
237 <table>
238 <tgroup cols="2">
239 <tbody>
240 <row>
241 <entry>VM image file</entry>
242
243 <entry>
244 <literal>pfSense.qcow2</literal>
245 </entry>
246 </row>
247
248 <row>
249 <entry>Image format</entry>
250
251 <entry>QCOW2</entry>
252 </row>
253
254 <row>
255 <entry>VNF Type Name</entry>
256
257 <entry>pfSense</entry>
258 </row>
259
260 <row>
261 <entry>Description</entry>
262
263 <entry>pfSense VNF</entry>
264 </row>
265
266 <row>
267 <entry>Version</entry>
268
269 <entry>1.0</entry>
270 </row>
271
272 <row>
273 <entry>Memory in MB</entry>
274
275 <entry>1024</entry>
276 </row>
277
278 <row>
279 <entry>Num of CPUs</entry>
280
281 <entry>1</entry>
282 </row>
283
284 <row>
285 <entry>Interfaces to add:</entry>
286
287 <entry>wan, lan and mgmt.</entry>
288 </row>
289
290 <row>
291 <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>
292
293 <entry>ISO</entry>
294 </row>
295
296 <row>
297 <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>
298
299 <entry>cdrom</entry>
300 </row>
301
302 <row>
303 <entry>Properties to add:</entry>
304
305 <entry>
306 <itemizedlist>
307 <listitem>
308 <para>Name: <literal>vnfMgmtIpAddress</literal>. Value:
309 10.0.0.3<superscript>1</superscript></para>
310 </listitem>
311
312 <listitem>
313 <para>Name: <literal>internalMgmtPort</literal>. Value:
314 443<superscript>2</superscript></para>
315 </listitem>
316
317 <listitem>
318 <para>Name: <literal>externalMgmtPort</literal>. Value:
319 60002<superscript>3</superscript></para>
320 </listitem>
321 </itemizedlist>
322 </entry>
323 </row>
324
325 <row>
326 <entry>Onboard</entry>
327
328 <entry>Wait for the message: "VNF package onboarded successfully"
329 then close the pop-up.</entry>
330 </row>
331 </tbody>
332 </tgroup>
333 </table>
334
335 <para>Please note the following:</para>
336
337 <itemizedlist>
338 <listitem>
339 <para><superscript>1</superscript>vnfMgmtIpAddress (10.0.0.3)
340 represents the IP address of the management interface of the Fortigate
341 VNF. Changing this value requires an update of the Fortigate
342 configuration to match with new IP address.</para>
343 </listitem>
344
345 <listitem>
346 <para><superscript>2</superscript>HTTPS access (443) can be changed to
347 another type of access. Please consult the official Fortigate
348 documentation for more details and make sure the Fortigate VNF is
349 configured to accept another type of connection before changing the
350 port number.</para>
351 </listitem>
352
353 <listitem>
354 <para><superscript>3</superscript>externalMgmtPort (60002) represents
355 the external port on which a user can access the VNF management
356 interface from a web browser. The user can select another port if
357 needed. There are no other changes required or components affected by
358 this change.</para>
359 </listitem>
360 </itemizedlist>
361 </section>
362
363 <section id="config_infrastruc_site1">
364 <title>Configuring the infrastructure for the uCPE device installed on
365 site1</title>
366
367 <orderedlist>
368 <listitem>
369 <para>Select the ucpe1 device: <literal>Configuration -&gt;
370 OpenVSwitch -&gt; Host Interfaces -&gt; Add</literal>.</para>
371
372 <para>Use the following values to fill the required fields:</para>
373
374 <itemizedlist>
375 <listitem>
376 <para><emphasis role="bold">Source</emphasis>:
377 <literal>enp4s0f1</literal>. <note>
378 <para>This is just an example interface. The user must select
379 the interface needed for use with the LAN connection.</para>
380 </note></para>
381 </listitem>
382
383 <listitem>
384 <para><emphasis role="bold">Type</emphasis>: dpdk
385 (standard).</para>
386 </listitem>
387
388 <listitem>
389 <para><emphasis role="bold">networking-type</emphasis>:
390 dpdk.</para>
391 </listitem>
392
393 <listitem>
394 <para><emphasis role="bold">dpdk-type</emphasis>: vfio-pci.</para>
395 </listitem>
396 </itemizedlist>
397
398 <para>Click <literal>Create</literal>, and the
399 <literal>enp4s0f1</literal> interface will be ready to use in a bridge
400 (LAN).</para>
401 </listitem>
402
403 <listitem>
404 <para>Select the ucpe1 device: <literal>Configuration -&gt;
405 OpenVSwitch -&gt; Bridges -&gt; Add</literal>.</para>
406
407 <para>Use the following values to fill the required fields for the
408 four bridges that need to be created:<itemizedlist>
409 <listitem>
410 <para><literal>ibm_br</literal>:</para>
411
412 <itemizedlist>
413 <listitem>
414 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
415 - do not change&gt;.</para>
416 </listitem>
417
418 <listitem>
419 <para><emphasis role="bold">Name</emphasis>:
420 <literal>ibm_br</literal>.</para>
421 </listitem>
422
423 <listitem>
424 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
425 <literal>inbandMgmt</literal>.</para>
426 </listitem>
427
428 <listitem>
429 <para><emphasis role="bold">mgmt-address</emphasis>: Provide
430 the IPv4 address of the uCPE Manager machine (E.g.
431 172.24.3.109).</para>
432 </listitem>
433
434 <listitem>
435 <para><emphasis role="bold">mgmt-port</emphasis>:
436 830.</para>
437 </listitem>
438 </itemizedlist>
439
440 <para>Click <literal>Create</literal>.</para>
441 </listitem>
442
443 <listitem>
444 <para><literal>vnf_mgmt_br</literal>:</para>
445
446 <itemizedlist>
447 <listitem>
448 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
449 - do not change&gt;.</para>
450 </listitem>
451
452 <listitem>
453 <para><emphasis role="bold">Name</emphasis>:
454 <literal>vnf_mgmt_br</literal>.</para>
455 </listitem>
456
457 <listitem>
458 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
459 <literal>vnfMgmt</literal>.</para>
460 </listitem>
461
462 <listitem>
463 <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
464 10.0.0.1</para>
465 </listitem>
466 </itemizedlist>
467
468 <para>Click <literal>Create</literal>.</para>
469 </listitem>
470
471 <listitem>
472 <para><literal>sfc_br</literal>:</para>
473
474 <itemizedlist>
475 <listitem>
476 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
477 - do not change&gt;.</para>
478 </listitem>
479
480 <listitem>
481 <para><emphasis role="bold">Name</emphasis>:
482 <literal>sfc_br</literal>.</para>
483 </listitem>
484
485 <listitem>
486 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
487 <literal>dataPlane</literal>.</para>
488 </listitem>
489
490 <listitem>
491 <para><emphasis role="bold">Sub-type</emphasis>:
492 integration.</para>
493 </listitem>
494 </itemizedlist>
495
496 <para>Click <literal>Create</literal>.</para>
497 </listitem>
498
499 <listitem>
500 <para><literal>lan_br</literal>:</para>
501
502 <itemizedlist>
503 <listitem>
504 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
505 - do not change&gt;.</para>
506 </listitem>
507
508 <listitem>
509 <para><emphasis role="bold">Name</emphasis>:
510 <literal>lan_br</literal>.</para>
511 </listitem>
512
513 <listitem>
514 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
515 <literal>dataPlane</literal>.</para>
516 </listitem>
517
518 <listitem>
519 <para><emphasis role="bold">Sub-type</emphasis>:
520 communication. Name: <literal>enp4s0f1</literal></para>
521 </listitem>
522 </itemizedlist>
523
524 <para>Click <literal>Create</literal>.</para>
525 </listitem>
526 </itemizedlist></para>
527 </listitem>
528
529 <listitem>
530 <para>Instantiate the FlexiWAN VNF by selecting the ucpe1 device, then
531 the VNF menu -&gt; <literal>Instances</literal> -&gt;
532 <literal>Add</literal>. </para>
533
534 <para>Use the following values to fill the required fields:</para>
535
536 <itemizedlist>
537 <listitem>
538 <para><emphasis role="bold">Name:</emphasis>
539 <literal>Flexiwan_ucpe1</literal>.</para>
540 </listitem>
541
542 <listitem>
543 <para><emphasis role="bold">VNF Type:</emphasis>
544 <literal>flexiWAN</literal>.</para>
545 </listitem>
546
547 <listitem>
548 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
549 </listitem>
550
551 <listitem>
552 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
553 </listitem>
554
555 <listitem>
556 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
557 </listitem>
558
559 <listitem>
560 <para><emphasis role="bold">Cloud Init File:</emphasis>
561 <filename>flexiWAN1_cloudinit.iso</filename>.</para>
562
563 <note>
564 <para>Example image provided. Please see the Appendix for
565 details on how to change the configuration and create a new
566 cloud-init iso image.</para>
567 </note>
568
569 <para>Click <literal>Domain Update Script</literal>.</para>
570 </listitem>
571
572 <listitem>
573 <para>Create the <literal>wan</literal> Interface: </para>
574
575 <para><emphasis role="bold">ID:</emphasis>
576 <literal>wan</literal>.</para>
577
578 <para><emphasis role="bold">Type:</emphasis>
579 <literal>dpdk</literal> tap.</para>
580
581 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
582 <literal>ibm_br</literal>.</para>
583
584 <para>Click <literal>Create</literal>.</para>
585 </listitem>
586
587 <listitem>
588 <para>Create the <literal>lan</literal> Interface: </para>
589
590 <para><emphasis role="bold">ID:</emphasis>
591 <literal>lan</literal>.</para>
592
593 <para><emphasis role="bold">Type:</emphasis>
594 <literal>dpdk</literal> tap.</para>
595
596 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
597 <literal>sfc_br</literal>.</para>
598
599 <para>Click <literal>Create</literal>.</para>
600 </listitem>
601 </itemizedlist>
602 </listitem>
603
604 <listitem>
605 <para>Instantiate the pfSense VNF by selecting the
606 <literal>me1100</literal> device, then the VNF menu -&gt;
607 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
608
609 <para>Use the following values to fill the required fields:</para>
610
611 <itemizedlist>
612 <listitem>
613 <para><emphasis role="bold">Name:</emphasis>
614 <literal>Pfsense_ucpe1</literal>.</para>
615 </listitem>
616
617 <listitem>
618 <para><emphasis role="bold">VNF Type:</emphasis>
619 <literal>pfSense</literal>.</para>
620 </listitem>
621
622 <listitem>
623 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
624 </listitem>
625
626 <listitem>
627 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
628 </listitem>
629
630 <listitem>
631 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
632 </listitem>
633
634 <listitem>
635 <para><emphasis role="bold">Cloud Init File:</emphasis>
636 <filename>pfsense_192_168_1_1.iso</filename>.</para>
637
638 <para>Click <literal>Domain Update Script</literal>.</para>
639 </listitem>
640
641 <listitem>
642 <para>Create the <literal>wan</literal> Interface:</para>
643
644 <para><emphasis role="bold">ID:</emphasis>
645 <literal>wan</literal>.</para>
646
647 <para><emphasis role="bold">Type:</emphasis>
648 <literal>dpdk</literal> tap.</para>
649
650 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
651 <literal>sfc_br</literal>.</para>
652
653 <para>Click <literal>Create</literal>.</para>
654 </listitem>
655
656 <listitem>
657 <para>Create the <literal>lan</literal> Interface:</para>
658
659 <para><emphasis role="bold">ID:</emphasis>
660 <literal>lan</literal>.</para>
661
662 <para><emphasis role="bold">Type:</emphasis>
663 <literal>dpdk</literal> tap.</para>
664
665 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
666 <literal>lan_br</literal>.</para>
667
668 <para>Click <literal>Create</literal>.</para>
669 </listitem>
670
671 <listitem>
672 <para>Create the <literal>mgmt</literal> Interface:</para>
673
674 <para><emphasis role="bold">ID:</emphasis>
675 <literal>mgmt</literal>.</para>
676
677 <para><emphasis role="bold">Type:</emphasis>
678 <literal>dpdk</literal> tap.</para>
679
680 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
681 <literal>vnf_mgmt_br</literal>.</para>
682
683 <para>Click <literal>Create</literal>.</para>
684 </listitem>
685 </itemizedlist>
686 </listitem>
687 </orderedlist>
688 </section>
689
690 <section id="config_infrastruc_site2">
691 <title>Configuring the infrastructure for the uCPE device installed on
692 site2</title>
693
694 <orderedlist>
695 <listitem>
696 <para>Select the ucpe2 device: <literal>Configuration -&gt;
697 OpenVSwitch -&gt; Host Interfaces -&gt; Add</literal>.</para>
698
699 <para>Use the following values to fill the required fields:</para>
700
701 <itemizedlist>
702 <listitem>
703 <para><emphasis role="bold">Source</emphasis>:
704 <literal>enp4s0f1</literal>. <note>
705 <para>This is just an example interface. The user must select
706 the interface needed for use with the LAN connection.</para>
707 </note></para>
708 </listitem>
709
710 <listitem>
711 <para><emphasis role="bold">Type</emphasis>: dpdk
712 (standard).</para>
713 </listitem>
714
715 <listitem>
716 <para><emphasis role="bold">networking-type</emphasis>:
717 dpdk.</para>
718 </listitem>
719
720 <listitem>
721 <para><emphasis role="bold">dpdk-type</emphasis>: vfio-pci.</para>
722 </listitem>
723 </itemizedlist>
724
725 <para>Click <literal>Create</literal>, and the
726 <literal>enp4s0f1</literal> interface will be ready to use in a bridge
727 (LAN).</para>
728 </listitem>
729
730 <listitem>
731 <para>Select the ucpe2 device: <literal>Configuration -&gt;
732 OpenVSwitch -&gt; Bridges -&gt; Add</literal>.</para>
733
734 <para>Use the following values to fill the required fields for the
735 four bridges that need to be created:<itemizedlist>
736 <listitem>
737 <para><literal>ibm_br</literal>:</para>
738
739 <itemizedlist>
740 <listitem>
741 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
742 - do not change&gt;.</para>
743 </listitem>
744
745 <listitem>
746 <para><emphasis role="bold">Name</emphasis>:
747 <literal>ibm_br</literal>.</para>
748 </listitem>
749
750 <listitem>
751 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
752 <literal>inbandMgmt</literal>.</para>
753 </listitem>
754
755 <listitem>
756 <para><emphasis role="bold">mgmt-address</emphasis>: Provide
757 the IPv4 address of the uCPE Manager machine (E.g.
758 172.24.3.109).</para>
759 </listitem>
760
761 <listitem>
762 <para><emphasis role="bold">mgmt-port</emphasis>:
763 830.</para>
764 </listitem>
765 </itemizedlist>
766
767 <para>Click <literal>Create</literal>.</para>
768 </listitem>
769
770 <listitem>
771 <para><literal>vnf_mgmt_br</literal>:</para>
772
773 <itemizedlist>
774 <listitem>
775 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
776 - do not change&gt;.</para>
777 </listitem>
778
779 <listitem>
780 <para><emphasis role="bold">Name</emphasis>:
781 <literal>vnf_mgmt_br</literal>.</para>
782 </listitem>
783
784 <listitem>
785 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
786 <literal>vnfMgmt</literal>.</para>
787 </listitem>
788
789 <listitem>
790 <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
791 10.0.0.1</para>
792 </listitem>
793 </itemizedlist>
794
795 <para>Click <literal>Create</literal>.</para>
796 </listitem>
797
798 <listitem>
799 <para><literal>sfc_br</literal>:</para>
800
801 <itemizedlist>
802 <listitem>
803 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
804 - do not change&gt;.</para>
805 </listitem>
806
807 <listitem>
808 <para><emphasis role="bold">Name</emphasis>:
809 <literal>sfc_br</literal>.</para>
810 </listitem>
811
812 <listitem>
813 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
814 <literal>dataPlane</literal>.</para>
815 </listitem>
816
817 <listitem>
818 <para><emphasis role="bold">Sub-type</emphasis>:
819 integration.</para>
820 </listitem>
821 </itemizedlist>
822
823 <para>Click <literal>Create</literal>.</para>
824 </listitem>
825
826 <listitem>
827 <para><literal>lan_br</literal>:</para>
828
829 <itemizedlist>
830 <listitem>
831 <para><emphasis role="bold">id</emphasis>: &lt;autogenerated
832 - do not change&gt;.</para>
833 </listitem>
834
835 <listitem>
836 <para><emphasis role="bold">Name</emphasis>:
837 <literal>lan_br</literal>.</para>
838 </listitem>
839
840 <listitem>
841 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
842 <literal>dataPlane</literal>.</para>
843 </listitem>
844
845 <listitem>
846 <para><emphasis role="bold">Sub-type</emphasis>:
847 communication. Name: <literal>enp4s0f1</literal></para>
848 </listitem>
849 </itemizedlist>
850
851 <para>Click <literal>Create</literal>.</para>
852 </listitem>
853 </itemizedlist></para>
854 </listitem>
855
856 <listitem>
857 <para>Instantiate the FlexiWAN VNF by selecting the ucpe2 device, then
858 the VNF menu -&gt; <literal>Instances</literal> -&gt;
859 <literal>Add</literal>.</para>
860
861 <para>Use the following values to fill the required fields:</para>
862
863 <itemizedlist>
864 <listitem>
865 <para><emphasis role="bold">Name:</emphasis>
866 <literal>Flexiwan_ucpe2</literal>.</para>
867 </listitem>
868
869 <listitem>
870 <para><emphasis role="bold">VNF Type:</emphasis>
871 <literal>flexiWAN</literal>.</para>
872 </listitem>
873
874 <listitem>
875 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
876 </listitem>
877
878 <listitem>
879 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
880 </listitem>
881
882 <listitem>
883 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
884 </listitem>
885
886 <listitem>
887 <para><emphasis role="bold">Cloud Init File:</emphasis>
888 <filename>flexiWAN2_cloudinit.iso</filename>.</para>
889
890 <note>
891 <para>Example image provided. Please see the Appendix for
892 details on how to change the configuration and create a new
893 cloud-init iso image.</para>
894 </note>
895
896 <para>Click <literal>Domain Update Script</literal>.</para>
897 </listitem>
898
899 <listitem>
900 <para>Create the <literal>wan</literal> Interface:</para>
901
902 <para><emphasis role="bold">ID:</emphasis>
903 <literal>wan</literal>.</para>
904
905 <para><emphasis role="bold">Type:</emphasis>
906 <literal>dpdk</literal> tap.</para>
907
908 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
909 <literal>ibm_br</literal>.</para>
910
911 <para>Click <literal>Create</literal>.</para>
912 </listitem>
913
914 <listitem>
915 <para>Create the <literal>lan</literal> Interface:</para>
916
917 <para><emphasis role="bold">ID:</emphasis>
918 <literal>lan</literal>.</para>
919
920 <para><emphasis role="bold">Type:</emphasis>
921 <literal>dpdk</literal> tap.</para>
922
923 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
924 <literal>sfc_br</literal>.</para>
925
926 <para>Click <literal>Create</literal>.</para>
927 </listitem>
928 </itemizedlist>
929 </listitem>
930
931 <listitem>
932 <para>Instantiate the pfSense VNF by selecting the
933 <literal>ucpe2</literal> device, then the VNF menu -&gt;
934 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
935
936 <para>Use the following values to fill the required fields:</para>
937
938 <itemizedlist>
939 <listitem>
940 <para><emphasis role="bold">Name:</emphasis>
941 <literal>Pfsense_ucpe2</literal>.</para>
942 </listitem>
943
944 <listitem>
945 <para><emphasis role="bold">VNF Type:</emphasis>
946 <literal>pfSense</literal>.</para>
947 </listitem>
948
949 <listitem>
950 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
951 </listitem>
952
953 <listitem>
954 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
955 </listitem>
956
957 <listitem>
958 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
959 </listitem>
960
961 <listitem>
962 <para><emphasis role="bold">Cloud Init File:</emphasis>
963 <filename>pfsense_192_168_2_1.iso</filename>.</para>
964
965 <para>Click <literal>Domain Update Script</literal>.</para>
966 </listitem>
967
968 <listitem>
969 <para>Create the <literal>wan</literal> Interface:</para>
970
971 <para><emphasis role="bold">ID:</emphasis>
972 <literal>wan</literal>.</para>
973
974 <para><emphasis role="bold">Type:</emphasis>
975 <literal>dpdk</literal> tap.</para>
976
977 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
978 <literal>sfc_br</literal>.</para>
979
980 <para>Click <literal>Create</literal>.</para>
981 </listitem>
982
983 <listitem>
984 <para>Create the <literal>lan</literal> Interface:</para>
985
986 <para><emphasis role="bold">ID:</emphasis>
987 <literal>lan</literal>.</para>
988
989 <para><emphasis role="bold">Type:</emphasis>
990 <literal>dpdk</literal> tap.</para>
991
992 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
993 <literal>lan_br</literal>.</para>
994
995 <para>Click <literal>Create</literal>.</para>
996 </listitem>
997
998 <listitem>
999 <para>Create the <literal>mgmt</literal> Interface:</para>
1000
1001 <para><emphasis role="bold">ID:</emphasis>
1002 <literal>mgmt</literal>.</para>
1003
1004 <para><emphasis role="bold">Type:</emphasis>
1005 <literal>dpdk</literal> tap.</para>
1006
1007 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1008 <literal>vnf_mgmt_br</literal>.</para>
1009
1010 <para>Click <literal>Create</literal>.</para>
1011 </listitem>
1012 </itemizedlist>
1013 </listitem>
1014 </orderedlist>
1015
1016 <figure>
1017 <title>Overview</title>
1018
1019 <mediaobject>
1020 <imageobject>
1021 <imagedata align="center" contentwidth="600"
1022 fileref="images/br_to_br_conn_overview.png" />
1023 </imageobject>
1024 </mediaobject>
1025 </figure>
1026 </section>
1027
1028 <section id="flexiwan_config">
1029 <title>Configuring FlexiWAN</title>
1030
1031 <para>Connect to <ulink
1032 url="https://app.flexiwan.com">https://app.flexiwan.com</ulink> and make
1033 sure you have an account and at least two valid device tokens. </para>
1034
1035 <para>Proceed to the Investory<remark>is this accurate?</remark> menu,
1036 click on <literal>Devices</literal>, the devices should already be present
1037 and need to be set. </para>
1038
1039 <para><emphasis role="bold">How to set a device</emphasis></para>
1040
1041 <orderedlist>
1042 <listitem>
1043 <para>Select each device and make sure to set the following
1044 values:</para>
1045
1046 <para><table>
1047 <tgroup cols="2">
1048 <tbody>
1049 <row>
1050 <entry>Target1(ucpe1)</entry>
1051
1052 <entry>Target1(ucpe2)</entry>
1053 </row>
1054
1055 <row>
1056 <entry>Device Name: target1</entry>
1057
1058 <entry>Device Name: target2</entry>
1059 </row>
1060
1061 <row>
1062 <entry>Description: Set IPv4 for the second interface
1063 (ens3): 10.0.1.1/24.</entry>
1064
1065 <entry>Description: Set IPv4 for the second interface
1066 (ens3): 10.0.2.1/24.</entry>
1067 </row>
1068
1069 <row>
1070 <entry>Set "Approved".</entry>
1071
1072 <entry>Set "Approved".</entry>
1073 </row>
1074
1075 <row>
1076 <entry>Click "Update Device".</entry>
1077
1078 <entry>Click "Update Device".</entry>
1079 </row>
1080 </tbody>
1081 </tgroup>
1082 </table></para>
1083 </listitem>
1084
1085 <listitem>
1086 <para>Select the option for each device to be put in the "running"
1087 state. </para>
1088 </listitem>
1089
1090 <listitem>
1091 <para>Wait for each "vRouter" to enter the running state.</para>
1092 </listitem>
1093
1094 <listitem>
1095 <para>Select the main top up checkbox in order to select all devices
1096 and hit "Create Tunnels". At this moment a direct connection should be
1097 available between those two targets.</para>
1098 </listitem>
1099 </orderedlist>
1100
1101 <note>
1102 <para>For the pfSense VNF there is no need for manual configuration. The
1103 configuration provided into the cloud init image is good enough to run
1104 the setup.</para>
1105 </note>
1106 </section>
1107</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml
index c294a77..4702cb0 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml
@@ -2,6 +2,12 @@
2<chapter id="intro_evalkit221"> 2<chapter id="intro_evalkit221">
3 <title>Introduction</title> 3 <title>Introduction</title>
4 4
5 <para>The NFV Access EvalKit offered by Enea contains software that can be
6 used to deploy an SD-WAN setup. The branch-to-branch setup uses two
7 opensource based VNFs: flexiWAN and pfSense. These VNFs are provided as
8 examples and the configuration used only works on the documented
9 setup.</para>
10
5 <para>Enea NFV Access for the universal Customer Premise Equipment (uCPE) is 11 <para>Enea NFV Access for the universal Customer Premise Equipment (uCPE) is
6 a virtualization and management platform, which allows end-users to 12 a virtualization and management platform, which allows end-users to
7 introduce, instantiate, and run third-party VNFs onto their systems.</para> 13 introduce, instantiate, and run third-party VNFs onto their systems.</para>
@@ -25,7 +31,7 @@
25 31
26 <para>The current Enea NFV Access solution provides a working and deployable 32 <para>The current Enea NFV Access solution provides a working and deployable
27 configuration as an example for branch-to-branch connection setup using the 33 configuration as an example for branch-to-branch connection setup using the
28 flexiWAN and pfSense VNFs service chained together on a uCPE device. </para> 34 flexiWAN and pfSense VNFs service chained together on a uCPE device.</para>
29 35
30 <para>This document will present all information required to replicate the 36 <para>This document will present all information required to replicate the
31 use cases described therein in the user's environment. The first part of 37 use cases described therein in the user's environment. The first part of
@@ -63,7 +69,7 @@
63 <para>The Automation Framework consists of a set of tooling and a 69 <para>The Automation Framework consists of a set of tooling and a
64 collection of Python based scripts that can be used to automate the 70 collection of Python based scripts that can be used to automate the
65 process of onboarding a VNF with all of the required configuration for 71 process of onboarding a VNF with all of the required configuration for
66 day zero deployment at scale. </para> 72 day zero deployment at scale.</para>
67 73
68 <para>This tooling calls the auto generated REST API that's exposed on 74 <para>This tooling calls the auto generated REST API that's exposed on
69 the uCPE Manager as a north bound interface.</para> 75 the uCPE Manager as a north bound interface.</para>
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml
index 1b348ee..943e1ef 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml
@@ -6,7 +6,7 @@
6 <title>Prerequisites</title> 6 <title>Prerequisites</title>
7 7
8 <table> 8 <table>
9 <title> Required Elements </title> 9 <title>Required Elements</title>
10 10
11 <tgroup cols="2"> 11 <tgroup cols="2">
12 <colspec align="left" /> 12 <colspec align="left" />
@@ -21,45 +21,39 @@
21 21
22 <tbody> 22 <tbody>
23 <row> 23 <row>
24 <entry>uCPE device<itemizedlist> 24 <entry>Two uCPE whitebox devices containing:<itemizedlist>
25 <listitem> 25 <listitem>
26 <para>Processor Xeon-D/atom-C3000</para> 26 <para>Processor: Intel xeon-D/atom-C3000 with min. 4
27 CPUs.</para>
27 </listitem> 28 </listitem>
28 29
29 <listitem> 30 <listitem>
30 <para>2 x network interfaces</para> 31 <para>Min. 2 network interfaces.</para>
31 </listitem> 32 </listitem>
32 33
33 <listitem> 34 <listitem>
34 <para>SSD storage</para> 35 <para>Min. 10 GB SATA storage.</para>
35 </listitem> 36 </listitem>
36 37
37 <listitem> 38 <listitem>
38 <para>8GB RAM</para> 39 <para>Min 8 GB RAM.</para>
39 </listitem> 40 </listitem>
40 </itemizedlist></entry> 41 </itemizedlist></entry>
41 42
42 <entry><itemizedlist> 43 <entry><itemizedlist>
43 <listitem> 44 <listitem>
44 <para>This is an example hardware configuration available in 45 <para>One network interface connected to WAN.</para>
45 the Enea Lab.</para>
46 </listitem> 46 </listitem>
47 47
48 <listitem> 48 <listitem>
49 <para>One of the SFP ports is connected to a network with 49 <para>One network interface to be used for LAN.</para>
50 DHCP server access (receiving a dynamic IP based on
51 MAC).</para>
52 </listitem> 50 </listitem>
53 51
54 <listitem> 52 <listitem>
55 <para>The device has network access to the uCPE 53 <para>NFV Access installed on both uCPE devices. Please see
56 Manager.</para> 54 Enea NFV Access Getting Started Manual, chapter "Enea NFV
57 </listitem> 55 Access Installer"<remark>make this into an olink</remark>
58 56 for more details.</para>
59 <listitem>
60 <para>NFV Access is installed on the device. Please see the
61 <emphasis>Enea NFV Access Getting Started</emphasis> Manual,
62 chapter "Enea NFV Access Installer" for more details.</para>
63 </listitem> 57 </listitem>
64 </itemizedlist></entry> 58 </itemizedlist></entry>
65 </row> 59 </row>
@@ -72,19 +66,20 @@
72 <para>The uCPE Manager is installed on this host or virtual 66 <para>The uCPE Manager is installed on this host or virtual
73 machine. Pease see the <emphasis>Enea NFV Access Getting 67 machine. Pease see the <emphasis>Enea NFV Access Getting
74 Started</emphasis> Manual, chapter "Getting Started with 68 Started</emphasis> Manual, chapter "Getting Started with
75 Enea uCPE Manager" for more details.</para> 69 Enea uCPE Manager" for more details <remark>make this into
70 an olink</remark>.</para>
76 </listitem> 71 </listitem>
77 72
78 <listitem> 73 <listitem>
79 <para>The uCPE Manager must have access to the me1100 74 <para>The uCPE Manager must have access to the uCPE
80 target.</para> 75 device.</para>
81 </listitem> 76 </listitem>
82 77
83 <listitem> 78 <listitem>
84 <para>A web browser will access the management interface of 79 <para>A web browser will access the management interface of
85 the VNFs. Management interfaces of the VNF can be accessed 80 the VNFs. Management interfaces of the VNF can be accessed
86 from any machine connected on the same network with the 81 from any machine connected on the same network with the uCPE
87 me1100 target.</para> 82 device.</para>
88 </listitem> 83 </listitem>
89 </itemizedlist></entry> 84 </itemizedlist></entry>
90 </row> 85 </row>
@@ -96,8 +91,23 @@
96 <section id="rel_struc_evalkit221"> 91 <section id="rel_struc_evalkit221">
97 <title>Release structure</title> 92 <title>Release structure</title>
98 93
99 <para></para> 94 <programlisting>|----enea-nfv-access-atom-c3000-20191210210825.hddimg
100 95|----ea-nfv-access-xeon-d-20191210210913.hddimg
101 <programlisting></programlisting> 96|----nfvaccess2.2.1_af-th.zip
97|----ucpeManager_1.0.1_b3-CentOS.tar.gz
98|----doc
99|----VNFs
100 |----EneaVNF
101 |----enea-nfv-access-vnf-qemux86-64.wic.qcow2
102 |----flexiWAN
103 |----flexiWAN_cloudinit.iso
104 |----flexiWAN.qcow2
105 |----flexiwant-cloud-init-example.tar.gz
106 |----pfSense
107 |----pfsense_192_168_1_1.iso
108 |----pfsense_192_168_2_1.iso
109 |----pfsense_config_192_168_1_1.xml
110 |----pfsense_config_192_168_2_1.xml
111 |----pfSense.qcow2</programlisting>
102 </section> 112 </section>
103</chapter> \ No newline at end of file 113</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml
index 455ac1f..02a29df 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml
@@ -2,40 +2,36 @@
2<chapter id="run_example_uc_auto_fm"> 2<chapter id="run_example_uc_auto_fm">
3 <title>Running Example Use-cases from the Automation Framework</title> 3 <title>Running Example Use-cases from the Automation Framework</title>
4 4
5 <section id="setup_ucpe1"> 5 <para>In order to run example use-cases from the Automation Framework,
6 <title>Setup on ucpe1</title> 6 offline configurations need to be added for both uCPE devices and for the
7 VNFs to be onboarded.</para>
7 8
8 <para><emphasis role="bold">How to Deploy fexiwan and pfsense VNFs on 9 <programlisting>&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 \
9 ucpe1</emphasis></para> 10-o ucpem -s test_EvalKit_addOfflineConfig_and_onBoardVNFs.json -d \
11"Set - offline config for uCPE1 and uCPE2"
10 12
11 <programlisting>&gt; cd automation_and_systemtest/automation_framework/unittestSuite 13#add device1
12&gt; python unittestSuite.py -u admin -p admin -H &lt;uCPE_Manager_IP&gt; \ 14&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \
13-n ucpe1 -s flexiwan_pfsense_ucpe1.json -d "ucpe1 Deployment"</programlisting> 15-s test_EvalKit_Deploy1.json -d "Add taget1 and instantiate VNFs"
14 16
15 <para><emphasis role="bold">Clean-up:</emphasis></para> 17#add device2
18&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \
19-s test_EvalKit_Deploy2.json -d "Add taget2 and instantiate VNFs"</programlisting>
16 20
17 <programlisting>&gt; python unittestSuite.py -u admin -p admin -H &lt;uCPE_Manager_IP&gt; \ 21 <para>Once done, the device configurations need to be cleaned up:</para>
18-n ucpe1 -s ucpe1Cleanup.json -d "ucpe1 Clean-up"</programlisting>
19 </section>
20 22
21 <section id="setup_ucpe2"> 23 <programlisting>&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \
22 <title>Setup on ucpe2</title> 24-s test_EvalKit_Cleanup1.json -d "Cleanup config on taget1"
23 25
24 <para><emphasis role="bold">How Deploy fexiwan and pfsense VNFs on 26&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \
25 ucpe2</emphasis></para> 27-s test_EvalKit_Cleanup2.json -d "Cleanup config on taget2"
26 28
27 <programlisting>&gt; cd automation_and_systemtest/automation_framework/unittestSuite 29&gt; python unittestSuite.py -u admin -p admin -H 172.24.3.109 -o ucpem -s \
28&gt; python unittestSuite.py -u admin -p admin -H &lt;uCPE_Manager_IP&gt; \ 30test_EvalKit_CleanupZTP_and_offboardVNFs.json -d \
29-n ucpe2 -s flexiwan_pfsense_ucpe2.json -d "ucpe2 Deployment"</programlisting> 31"Cleanup offline configuration and OffBoard VNFs"</programlisting>
30 32
31 <para><emphasis role="bold">Clean-up:</emphasis></para> 33 <note>
32 34 <para>Replace the &lt;uCPE_Manager_IP&gt; with the IP address of uCPE
33 <programlisting>&gt; python unittestSuite.py -u admin -p admin -H &lt;uCPE_Manager_IP&gt; \ 35 Manager machine.</para>
34-n ucpe1 -s ucpe1Cleanup.json -d "ucpe1 Clean-up"</programlisting> 36 </note>
35
36 <note>
37 <para>Please replace &lt;uCPE_Manager_IP&gt; with IP address of uCPE
38 Manager machine.</para>
39 </note>
40 </section>
41</chapter> \ No newline at end of file 37</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml
new file mode 100644
index 0000000..c5da1bc
--- /dev/null
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml
@@ -0,0 +1,1452 @@
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<chapter id="sdwan_arch_evalkit">
3 <title>SD-WAN architecture</title>
4
5 <para>Software-Defined Wide Area Networking (SD-WAN), provides the benefits
6 of software-defined networking (SDN) technology to traditionally
7 hardware-based networking. It is an overlay architecture providing a
8 networking foundation that is much easier to manage than legacy WANs,
9 essentially moving the control layer to the cloud and in the process,
10 centralizing and simplifying network management. This overlay design
11 abstracts software from hardware, enabling network virtualization and making
12 the network more elastic.</para>
13
14 <para>The setup detailed in this chapter looks to cover all the steps
15 required to create a connection between two branch offices. On each site a
16 uCPE device is installed and connected to a WAN network. NFV Access should
17 already be installed on each uCPE device, and with it the flexiWAN and
18 pfSense VNFs will be instantiated on each site.</para>
19
20 <para>The flexiWAN VNF will create the tunnel between the two branches while
21 the pfSense VNF (connected in the service chain), will cover the
22 communication with LAN on each branch. The setup will be configured from the
23 uCPE Manager GUI, accessible from any web browser if connected to the IP
24 address of uCPE Manager machine.</para>
25
26 <para>The default login credentials for both username and password are
27 admin/admin.</para>
28
29 <figure>
30 <title>Branch to Branch Connection Overview</title>
31
32 <mediaobject>
33 <imageobject>
34 <imagedata align="center" contentwidth="600"
35 fileref="images/br_to_br_conn_setup.png" />
36 </imageobject>
37 </mediaobject>
38 </figure>
39
40 <para>The figure above represents the uCPE configuration of one of the
41 branches. The second uCPE device (site2) will be configured in a similar
42 way, described in the following sections.</para>
43
44 <para>Since there is only one physical network interface connected to WAN,
45 the configuration allows for multiple types of traffic to pass over this
46 interface. The <literal>ibm_br</literal> bridge is the main bridge that
47 connects the physical network interface to the virtual
48 infrastructure.</para>
49
50 <para>The Data-Path represents the traffic that passes over the physical
51 interface between the in-band management bridge (<literal>ibm_br</literal>),
52 the flexiWAN VNF, the service chain bridge (<literal>sfc_br</literal>), the
53 pfSense VNF, and the <literal>lan_br</literal> bridge to finally reach the
54 LAN.</para>
55
56 <para>The VNF management interface for the pfSense VNF can be accessed from
57 WAN using a web browser. VNF management for flexiWAN is done from a
58 centralized management location where the user needs an account in order to
59 have access. Please contact the flexiWAN VNF provider before beginning to
60 set up the configuration.</para>
61
62 <para>For infrastructure configuration of each uCPE device Zero Touch
63 Provisioning (ZTP) will be used. This is a feature that allows the user to
64 create an offline configuration before starting and connecting a uCPE device
65 to the uCPE Manager. NFV Access allows a user to preconfigure interfaces and
66 bridges using ZTP so that, all that is left to do in order to have a full
67 setup running correctly after adding uCPE devices, is simply instantiation
68 of the VNFs on the designated devices.</para>
69
70 <section id="prelim_setup">
71 <title>Preliminary Setup</title>
72
73 <orderedlist>
74 <listitem>
75 <para>Connect each uCPE device to the network/Internet using one
76 physical interface as the designated WAN access interface.</para>
77
78 <note>
79 <para>The uCPE device must have Internet access beforehand.</para>
80 </note>
81 </listitem>
82
83 <listitem>
84 <para>Install NFV Access on the uCPE devices. See the <remark>make
85 this into an olink</remark> Enea NFV Access Getting Started manual,
86 chapter Installing Enea NFV Access, for more details.</para>
87 </listitem>
88
89 <listitem>
90 <para>Install the uCPE Manager on the CentOS host or VM. See the
91 <remark>make this into an olink</remark> Enea NFV Access Getting
92 Started manual, chapter Getting Started with Enea uCPE Manager, for
93 more details.</para>
94
95 <note>
96 <para>The uCPE Manager host machine must be connected to the network
97 so all uCPE devices can access the internet.</para>
98 </note>
99 </listitem>
100
101 <listitem>
102 <para>Connect to the uCPE Manager: <literal>https://&lt;uCPE Manager
103 IP&gt;</literal></para>
104 </listitem>
105 </orderedlist>
106 </section>
107
108 <section id="ucpe_mg_evalkit221">
109 <title>The uCPE Manager</title>
110
111 <para>Log into the uCPE manager with the username and password
112 "admin".</para>
113
114 <para>In this setup Zero Touch Provisioning (ZTP) will be used to
115 preconfigure the infrastructure in the uCPE Manager for each device. The
116 interface and bridge configurations are pushed onto each uCPE device when
117 connected.</para>
118
119 <para>Onboarding is the process of registering VNFs into the uCPE Manager
120 after devices are configured for the VNF(s) they will host and added into
121 the Manager. The flexiWAN and pfSense VNFs are used along with example
122 configuration data.</para>
123
124 <section id="onboard_flexiwan_vnf">
125 <title>Onboarding the FlexiWAN VNF</title>
126
127 <para>Add a VNF by accessing the <literal>VNF</literal> menu from the
128 top toolbar then <literal>Descriptors</literal> -&gt;
129 <literal>On-board</literal> -&gt; <literal>VM Image</literal>.</para>
130
131 <para>Use the following values to fill the required fields:</para>
132
133 <table>
134 <tgroup cols="2">
135 <tbody>
136 <row>
137 <entry>VM image file</entry>
138
139 <entry>
140 <literal>flexiWAN.qcow2</literal>
141 </entry>
142 </row>
143
144 <row>
145 <entry>Image format</entry>
146
147 <entry>QCOW2</entry>
148 </row>
149
150 <row>
151 <entry>VNF Type Name</entry>
152
153 <entry>flexiWAN</entry>
154 </row>
155
156 <row>
157 <entry>Description</entry>
158
159 <entry>Flexiwan VNF</entry>
160 </row>
161
162 <row>
163 <entry>Version</entry>
164
165 <entry>1.0</entry>
166 </row>
167
168 <row>
169 <entry>Memory in MB</entry>
170
171 <entry>4096. More memory can be allocated if required.</entry>
172 </row>
173
174 <row>
175 <entry>Num of CPUs</entry>
176
177 <entry>2. More CPUs can be reserved if required and
178 available.</entry>
179 </row>
180
181 <row>
182 <entry>Interfaces to add:</entry>
183
184 <entry>wan and lan</entry>
185 </row>
186
187 <row>
188 <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>
189
190 <entry>ISO</entry>
191 </row>
192
193 <row>
194 <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>
195
196 <entry>cdrom</entry>
197 </row>
198
199 <row>
200 <entry>Onboard</entry>
201
202 <entry>Wait for the message: "VNF package onboarded
203 successfully" then close the pop-up.</entry>
204 </row>
205 </tbody>
206 </tgroup>
207 </table>
208 </section>
209
210 <section id="onboard_pfsense_vnf">
211 <title>Onboarding the pfSense VNF</title>
212
213 <para>Add the other VNF by accessing the <literal>VNF</literal> menu
214 from the top toolbar once again, then <literal>Descriptors</literal>
215 -&gt; <literal>On-board</literal> -&gt; <literal>VM
216 Image</literal>.</para>
217
218 <para>Use the following values to fill the required fields:</para>
219
220 <table>
221 <tgroup cols="2">
222 <tbody>
223 <row>
224 <entry>VM image file</entry>
225
226 <entry>
227 <literal>pfSense.qcow2</literal>
228 </entry>
229 </row>
230
231 <row>
232 <entry>Image format</entry>
233
234 <entry>QCOW2</entry>
235 </row>
236
237 <row>
238 <entry>VNF Type Name</entry>
239
240 <entry>pfSense</entry>
241 </row>
242
243 <row>
244 <entry>Description</entry>
245
246 <entry>pfSense VNF</entry>
247 </row>
248
249 <row>
250 <entry>Version</entry>
251
252 <entry>1.0</entry>
253 </row>
254
255 <row>
256 <entry>Memory in MB</entry>
257
258 <entry>1024</entry>
259 </row>
260
261 <row>
262 <entry>Num of CPUs</entry>
263
264 <entry>1</entry>
265 </row>
266
267 <row>
268 <entry>Interfaces to add:</entry>
269
270 <entry>wan, lan and mgmt.</entry>
271 </row>
272
273 <row>
274 <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>
275
276 <entry>ISO</entry>
277 </row>
278
279 <row>
280 <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>
281
282 <entry>cdrom</entry>
283 </row>
284
285 <row>
286 <entry>Properties to add:</entry>
287
288 <entry>
289 <itemizedlist>
290 <listitem>
291 <para>Name: <literal>vnfMgmtIpAddress</literal>. Value:
292 10.0.0.3<superscript>1</superscript></para>
293 </listitem>
294
295 <listitem>
296 <para>Name: <literal>internalMgmtPort</literal>. Value:
297 443<superscript>2</superscript></para>
298 </listitem>
299
300 <listitem>
301 <para>Name: <literal>externalMgmtPort</literal>. Value:
302 60002<superscript>3</superscript></para>
303 </listitem>
304 </itemizedlist>
305 </entry>
306 </row>
307
308 <row>
309 <entry>Onboard</entry>
310
311 <entry>Wait for the message: "VNF package onboarded
312 successfully" then close the pop-up.</entry>
313 </row>
314 </tbody>
315 </tgroup>
316 </table>
317
318 <para>Please note the following:</para>
319
320 <itemizedlist>
321 <listitem>
322 <para><superscript>1</superscript>vnfMgmtIpAddress (10.0.0.3)
323 represents the IP address of the management interface of the pfSense
324 VNF. Changing this value requires an update of the pfSense
325 configuration to match the new IP address.</para>
326 </listitem>
327
328 <listitem>
329 <para><superscript>2</superscript>HTTPS access (443) can be changed
330 to another type of access. Please consult the official pfSense
331 documentation for more details and make sure the pfSense VNF is
332 configured to accept another type of connection before changing the
333 port number.</para>
334 </listitem>
335
336 <listitem>
337 <para><superscript>3</superscript>externalMgmtPort (60002)
338 represents the external port on which a user can access the VNF
339 management interface from a web browser. The user can select another
340 port if needed. There are no other changes required or components
341 affected by this change.</para>
342 </listitem>
343 </itemizedlist>
344 </section>
345
346 <section id="offline_config_ucpe_device1">
347 <title>Offline Configuration for uCPE device1</title>
348
349 <para>A Zero Touch Provisioning configuration for a device is done in
350 two steps from the uCPE Manager's GUI. The first step is to create a
351 data store and then to add the offline configuration for the device
352 infrastructure into that data store.</para>
353
354 <orderedlist>
355 <listitem>
356 <para><emphasis role="bold">Create the "device1" data
357 store</emphasis>: <literal>Applications</literal> -&gt;
358 <literal>Offline Config</literal> -&gt;
359 <literal>Add</literal>.</para>
360
361 <para>Use the following values to fill the required fields:</para>
362
363 <table>
364 <tgroup cols="2">
365 <colspec align="left" />
366
367 <tbody>
368 <row>
369 <entry>Name</entry>
370
371 <entry>
372 <literal>Device1</literal>
373 </entry>
374 </row>
375
376 <row>
377 <entry>Device Type</entry>
378
379 <entry>Enea universal CPE</entry>
380 </row>
381
382 <row>
383 <entry>Device Version</entry>
384
385 <entry>2.2.1</entry>
386 </row>
387
388 <row>
389 <entry>Config Set</entry>
390
391 <entry>uCPE Config</entry>
392 </row>
393
394 <row>
395 <entry>
396 <literal>deviceId</literal>
397 </entry>
398
399 <entry>The ID extracted from device1 after running
400 <filename>list_deviceID.sh</filename>.</entry>
401 </row>
402 </tbody>
403 </tgroup>
404 </table>
405
406 <para>Press the Create button.</para>
407 </listitem>
408
409 <listitem>
410 <para>Prepare the infrastructure configuration for device1 in the
411 data store: <literal>Applications</literal> -&gt; <literal>Offline
412 Config</literal> -&gt; &lt;select "device1" data store&gt; -&gt;
413 <literal>Config App...</literal>. This window layout is very similar
414 to the Configuration window of a device.</para>
415 </listitem>
416
417 <listitem>
418 <para>Disable the DPDK: <literal>DPDK</literal> -&gt;
419 <literal>Advanced Settings</literal> -&gt; uncheck <literal>Enable
420 DPDK</literal> to disable the DPDK and click "Create".</para>
421 </listitem>
422
423 <listitem>
424 <para><emphasis role="bold">Configure the host
425 interface(s):</emphasis> select the device -&gt;
426 <literal>Configuration</literal> -&gt;
427 <literal>OpenVSwitch</literal> -&gt; <literal>Host
428 Interfaces</literal> -&gt; <literal>Add</literal>.</para>
429
430 <para>Use the following values to fill the required fields:</para>
431
432 <itemizedlist>
433 <listitem>
434 <para><emphasis role="bold">Source</emphasis>:
435 <literal>enp7s0f1</literal>. <note>
436 <para>This is just an example interface. The user must
437 select the interface needed for use with the LAN
438 connection.</para>
439 </note></para>
440 </listitem>
441
442 <listitem>
443 <para><emphasis role="bold">Type</emphasis>: N/A.</para>
444 </listitem>
445
446 <listitem>
447 <para><emphasis role="bold">networking-type</emphasis>:
448 standard.</para>
449 </listitem>
450
451 <listitem>
452 <para><emphasis role="bold">dpdk-type</emphasis>: N/A.</para>
453 </listitem>
454 </itemizedlist>
455
456 <para>Click <literal>Create</literal>, and the
457 <literal>enp7s0f1</literal> interface will be ready to use in a
458 bridge (LAN).</para>
459 </listitem>
460
461 <listitem>
462 <para><emphasis role="bold">Configure the bridges</emphasis>: select
463 the device -&gt; <literal>Configuration</literal> -&gt;
464 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>
465 -&gt; <literal>Add</literal>.</para>
466
467 <para>Use the following values to fill the required fields for the
468 four bridges that need to be created: <itemizedlist>
469 <listitem>
470 <para><literal>ibm_br</literal>:</para>
471
472 <itemizedlist spacing="compact">
473 <listitem>
474 <para><emphasis role="bold">Name</emphasis>:
475 <literal>ibm_br</literal>.</para>
476 </listitem>
477
478 <listitem>
479 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
480 <literal>inbandMgmt</literal>.</para>
481 </listitem>
482
483 <listitem>
484 <para><emphasis role="bold">mgmt-address</emphasis>:
485 Provide the IPv4 address of the uCPE Manager machine (E.g.
486 172.24.3.109).</para>
487 </listitem>
488
489 <listitem>
490 <para><emphasis role="bold">mgmt-port</emphasis>:
491 830.</para>
492 </listitem>
493 </itemizedlist>
494
495 <para>Click <literal>Create</literal>.</para>
496 </listitem>
497
498 <listitem>
499 <para><literal>vnf_mgmt_br</literal>:</para>
500
501 <itemizedlist spacing="compact">
502 <listitem>
503 <para><emphasis role="bold">Name</emphasis>:
504 <literal>vnf_mgmt_br</literal>.</para>
505 </listitem>
506
507 <listitem>
508 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
509 <literal>vnfMgmt</literal>.</para>
510 </listitem>
511
512 <listitem>
513 <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
514 10.0.0.1</para>
515 </listitem>
516 </itemizedlist>
517
518 <para>Click <literal>Create</literal>.</para>
519 </listitem>
520
521 <listitem>
522 <para><literal>sfc_br</literal>:</para>
523
524 <itemizedlist spacing="compact">
525 <listitem>
526 <para><emphasis role="bold">Name</emphasis>:
527 <literal>sfc_br</literal>.</para>
528 </listitem>
529
530 <listitem>
531 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
532 <literal>dataPlane</literal>.</para>
533 </listitem>
534
535 <listitem>
536 <para><emphasis role="bold">Sub-type</emphasis>:
537 integration.</para>
538 </listitem>
539 </itemizedlist>
540
541 <para>Click <literal>Create</literal>.</para>
542 </listitem>
543
544 <listitem>
545 <para><literal>lan_br</literal>:</para>
546
547 <itemizedlist spacing="compact">
548 <listitem>
549 <para><emphasis role="bold">Name</emphasis>:
550 <literal>lan_br</literal>.</para>
551 </listitem>
552
553 <listitem>
554 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
555 <literal>dataPlane</literal>.</para>
556 </listitem>
557
558 <listitem>
559 <para><emphasis role="bold">Sub-type</emphasis>:
560 communication. Name: <literal>enp7s0f1</literal></para>
561 </listitem>
562 </itemizedlist>
563
564 <para>Click <literal>Create</literal>.</para>
565 </listitem>
566 </itemizedlist></para>
567 </listitem>
568 </orderedlist>
569 </section>
570
571 <section id="offline_config_ucpe_device2">
572 <title>Offline Configuration for uCPE device2</title>
573
574 <para>A Zero Touch Provisioning configuration for a device is done in
575 two steps from the uCPE Manager's GUI. The first step is to create a
576 data store and then to add the offline configuration for the device
577 infrastructure into that data store.</para>
578
579 <orderedlist>
580 <listitem>
581 <para><emphasis role="bold">Create the "device2" data
582 store</emphasis>: <literal>Applications</literal> -&gt;
583 <literal>Offline Config</literal> -&gt;
584 <literal>Add</literal>.</para>
585
586 <para>Use the following values to fill the required fields:</para>
587
588 <table>
589 <tgroup cols="2">
590 <colspec align="left" />
591
592 <tbody>
593 <row>
594 <entry>Name</entry>
595
596 <entry>
597 <literal>Device2</literal>
598 </entry>
599 </row>
600
601 <row>
602 <entry>Device Type</entry>
603
604 <entry>Enea universal CPE</entry>
605 </row>
606
607 <row>
608 <entry>Device Version</entry>
609
610 <entry>2.2.1</entry>
611 </row>
612
613 <row>
614 <entry>Config Set</entry>
615
616 <entry>uCPE Config</entry>
617 </row>
618
619 <row>
620 <entry>
621 <literal>deviceId</literal>
622 </entry>
623
624 <entry>The ID extracted from device2 after running
625 <filename>list_deviceID.sh</filename>.</entry>
626 </row>
627 </tbody>
628 </tgroup>
629 </table>
630
631 <para>Press the Create button.</para>
632 </listitem>
633
634 <listitem>
635 <para>Prepare the infrastructure configuration for device2 in the
636 data store: <literal>Applications</literal> -&gt; <literal>Offline
637 Config</literal> -&gt; &lt;select "device2" data store&gt; -&gt;
638 <literal>Config App...</literal>. This window layout is very similar
639 to the Configuration window of a device.</para>
640 </listitem>
641
642 <listitem>
643 <para>Disable the DPDK: <literal>DPDK</literal> -&gt;
644 <literal>Advanced Settings</literal> -&gt; uncheck <literal>Enable
645 DPDK</literal> to disable the DPDK and click "Create".</para>
646 </listitem>
647
648 <listitem>
649 <para><emphasis role="bold">Configure the host
650 interface(s):</emphasis> select the device -&gt;
651 <literal>Configuration</literal> -&gt;
652 <literal>OpenVSwitch</literal> -&gt; <literal>Host
653 Interfaces</literal> -&gt; <literal>Add</literal>.</para>
654
655 <para>Use the following values to fill the required fields:</para>
656
657 <itemizedlist>
658 <listitem>
659 <para><emphasis role="bold">Source</emphasis>:
660 <literal>eno4</literal>. <note>
661 <para>This is just an example interface. The user must
662 select the interface needed for use with the LAN
663 connection.</para>
664 </note></para>
665 </listitem>
666
667 <listitem>
668 <para><emphasis role="bold">Type</emphasis>: standard.</para>
669 </listitem>
670
671 <listitem>
672 <para><emphasis role="bold">networking-type</emphasis>:
673 standard.</para>
674 </listitem>
675
676 <listitem>
677 <para><emphasis role="bold">dpdk-type</emphasis>: N/A.</para>
678 </listitem>
679 </itemizedlist>
680
681 <para>Click <literal>Create</literal>, and the
682 <literal>eno4</literal> interface will be ready to use in a bridge
683 (LAN).</para>
684 </listitem>
685
686 <listitem>
687 <para><emphasis role="bold">Configure the bridges</emphasis>: select
688 the device -&gt; <literal>Configuration</literal> -&gt;
689 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>
690 -&gt; <literal>Add</literal>.</para>
691
692 <para>Use the following values to fill the required fields for the
693 four bridges that need to be created:</para>
694
695 <itemizedlist>
696 <listitem>
697 <para><literal>ibm_br</literal>:</para>
698
699 <itemizedlist spacing="compact">
700 <listitem>
701 <para><emphasis role="bold">Name</emphasis>:
702 <literal>ibm_br</literal>.</para>
703 </listitem>
704
705 <listitem>
706 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
707 <literal>inbandMgmt</literal>.</para>
708 </listitem>
709
710 <listitem>
711 <para><emphasis role="bold">mgmt-address</emphasis>: Provide
712 the IPv4 address of the uCPE Manager machine (E.g.
713 172.24.3.109).</para>
714 </listitem>
715
716 <listitem>
717 <para><emphasis role="bold">mgmt-port</emphasis>:
718 830.</para>
719 </listitem>
720 </itemizedlist>
721
722 <para>Click <literal>Create</literal>.</para>
723 </listitem>
724
725 <listitem>
726 <para><literal>vnf_mgmt_br</literal>:</para>
727
728 <itemizedlist spacing="compact">
729 <listitem>
730 <para><emphasis role="bold">Name</emphasis>:
731 <literal>vnf_mgmt_br</literal>.</para>
732 </listitem>
733
734 <listitem>
735 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
736 <literal>vnfMgmt</literal>.</para>
737 </listitem>
738
739 <listitem>
740 <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
741 10.0.0.1</para>
742 </listitem>
743 </itemizedlist>
744
745 <para>Click <literal>Create</literal>.</para>
746 </listitem>
747
748 <listitem>
749 <para><literal>sfc_br</literal>:</para>
750
751 <itemizedlist spacing="compact">
752 <listitem>
753 <para><emphasis role="bold">Name</emphasis>:
754 <literal>sfc_br</literal>.</para>
755 </listitem>
756
757 <listitem>
758 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
759 <literal>dataPlane</literal>.</para>
760 </listitem>
761
762 <listitem>
763 <para><emphasis role="bold">Sub-type</emphasis>:
764 integration.</para>
765 </listitem>
766 </itemizedlist>
767
768 <para>Click <literal>Create</literal>.</para>
769 </listitem>
770
771 <listitem>
772 <para><literal>lan_br</literal>:</para>
773
774 <itemizedlist spacing="compact">
775 <listitem>
776 <para><emphasis role="bold">Name</emphasis>:
777 <literal>lan_br</literal>.</para>
778 </listitem>
779
780 <listitem>
781 <para><emphasis role="bold">ovs-bridge-type</emphasis>:
782 <literal>dataPlane</literal>.</para>
783 </listitem>
784
785 <listitem>
786 <para><emphasis role="bold">Sub-type</emphasis>:
787 communication. Name: <literal>eno4</literal></para>
788 </listitem>
789 </itemizedlist>
790
791 <para>Click <literal>Create</literal>.</para>
792 </listitem>
793 </itemizedlist>
794 </listitem>
795 </orderedlist>
796 </section>
797
798 <section id="upload_offline_config">
799 <title>Uploading the offline Configuration</title>
800
801 <para>In this context and example setup, which uses ZTP, the offline
802 configuration can be uploaded and applied on a uCPE device only once. If
803 the setup needs to be rerun on a device where ZTP was already used,
804 please do the following:</para>
805
806 <orderedlist spacing="compact">
807 <listitem>
808 <para>Add the device manually from the uCPE manager GUI.</para>
809 </listitem>
810
811 <listitem>
812 <para>Clean the entire configuration on the device.</para>
813 </listitem>
814
815 <listitem>
816 <para>Reset the ZTP: <literal>device</literal> -&gt; Configure -&gt;
817 Host -&gt; initial-config-complete: false -&gt; Apply.</para>
818 </listitem>
819
820 <listitem>
821 <para>Delete the device from the uCPE Manager.</para>
822 </listitem>
823 </orderedlist>
824 </section>
825 </section>
826
827 <section id="add_ucpe1_mg">
828 <title>Adding the uCPE device1 into the uCPE Manager</title>
829
830 <para>Access the <literal>Devices</literal> menu, then
831 <literal>Manage</literal> -&gt; <literal>Add</literal>.</para>
832
833 <para>Use the following values to fill the required fields:</para>
834
835 <table>
836 <tgroup cols="2">
837 <colspec align="left" />
838
839 <tbody>
840 <row>
841 <entry>Type</entry>
842
843 <entry>Enea universal CPE</entry>
844 </row>
845
846 <row>
847 <entry>Release</entry>
848
849 <entry>1.0</entry>
850 </row>
851
852 <row>
853 <entry>Name</entry>
854
855 <entry>Ucpe1</entry>
856 </row>
857
858 <row>
859 <entry>IP/DNS Address</entry>
860
861 <entry>Dynamic IP received by the device from the DHCP server
862 (E.g. 172.24.12.74).</entry>
863 </row>
864
865 <row>
866 <entry>Description</entry>
867
868 <entry>ucpe device site 1</entry>
869 </row>
870
871 <row>
872 <entry>SSH Port</entry>
873
874 <entry>830</entry>
875 </row>
876
877 <row>
878 <entry>SSH User Name</entry>
879
880 <entry>root</entry>
881 </row>
882
883 <row>
884 <entry>Password</entry>
885
886 <entry />
887 </row>
888
889 <row>
890 <entry>Device ID</entry>
891
892 <entry>Extract the device ID from device1, by running
893 <literal>list_deviceID.sh</literal>.</entry>
894 </row>
895
896 <row>
897 <entry>OK</entry>
898
899 <entry>
900 <itemizedlist>
901 <listitem>
902 <para>Green status indicates connection with the device was
903 established.</para>
904 </listitem>
905
906 <listitem><para>To add the device on the map: Right-Click on
907 the Map -&gt; Place Device -&gt; ucpe1</para>.</listitem>
908 </itemizedlist>
909 </entry>
910 </row>
911 </tbody>
912 </tgroup>
913 </table>
914 </section>
915
916 <section id="add_ucpe2_mg">
917 <title>Adding the uCPE device2 into the uCPE Manager</title>
918
919 <para>Access the <literal>Devices</literal> menu, then
920 <literal>Manage</literal> -&gt; <literal>Add</literal>.</para>
921
922 <para>Use the following values to fill the required fields:</para>
923
924 <table>
925 <tgroup cols="2">
926 <colspec align="left" />
927
928 <tbody>
929 <row>
930 <entry>Type</entry>
931
932 <entry>Enea universal CPE</entry>
933 </row>
934
935 <row>
936 <entry>Release</entry>
937
938 <entry>1.0</entry>
939 </row>
940
941 <row>
942 <entry>Name</entry>
943
944 <entry>Ucpe2</entry>
945 </row>
946
947 <row>
948 <entry>IP/DNS Address</entry>
949
950 <entry>Dynamic IP received by the device from the DHCP server
951 (E.g. 172.24.12.74).</entry>
952 </row>
953
954 <row>
955 <entry>Description</entry>
956
957 <entry>ucpe device site 2</entry>
958 </row>
959
960 <row>
961 <entry>SSH Port</entry>
962
963 <entry>830</entry>
964 </row>
965
966 <row>
967 <entry>SSH User Name</entry>
968
969 <entry>root</entry>
970 </row>
971
972 <row>
973 <entry>Password</entry>
974
975 <entry />
976 </row>
977
978 <row>
979 <entry>Device ID</entry>
980
981 <entry>Extract the device ID from device2, by running
982 <literal>list_deviceID.sh</literal>.</entry>
983 </row>
984
985 <row>
986 <entry>OK</entry>
987
988 <entry>
989 <itemizedlist>
990 <listitem>
991 <para>Green status indicates connection with the device was
992 established.</para>
993 </listitem>
994
995 <listitem><para>To add the device on the map: Right-Click on
996 the Map -&gt; Place Device -&gt; ucpe2</para>.</listitem>
997 </itemizedlist>
998 </entry>
999 </row>
1000 </tbody>
1001 </tgroup>
1002 </table>
1003
1004 <para>After the two devices are added into the uCPE Manager all offline
1005 configuration data prepared for them is pushed automatically onto the
1006 devices. To check if a device is configured, add the device onto the map
1007 and select &lt;ucpe1&gt; -&gt; <literal>Configuration</literal> -&gt;
1008 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>.</para>
1009 </section>
1010
1011 <section id="flexiwan_inst_device1">
1012 <title>FlexiWAN VNF Instantiation on device1</title>
1013
1014 <para>Instantiate the FlexiWAN VNF by selecting the ucpe1 device, then the
1015 VNF menu -&gt; <literal>Instances</literal> -&gt;
1016 <literal>Add</literal>.</para>
1017
1018 <para>Use the following values to fill the required fields:</para>
1019
1020 <itemizedlist>
1021 <listitem>
1022 <para><emphasis role="bold">Name:</emphasis>
1023 <literal>Flexiwan_ucpe1</literal>.</para>
1024 </listitem>
1025
1026 <listitem>
1027 <para><emphasis role="bold">VNF Type:</emphasis>
1028 <literal>flexiWAN</literal>.</para>
1029 </listitem>
1030
1031 <listitem>
1032 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
1033 </listitem>
1034
1035 <listitem>
1036 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
1037 </listitem>
1038
1039 <listitem>
1040 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
1041 </listitem>
1042
1043 <listitem>
1044 <para><emphasis role="bold">Cloud Init File:</emphasis>
1045 <filename>flexiWAN_cloudinit.iso</filename>.</para>
1046
1047 <note>
1048 <para>Example image provided. Please see the Appendix for details on
1049 how to change the configuration and create a new cloud-init iso
1050 image.</para>
1051 </note>
1052
1053 <para>Click <literal>Domain Update Script</literal>.</para>
1054 </listitem>
1055
1056 <listitem>
1057 <para>Create the <literal>wan</literal> Interface:</para>
1058
1059 <para><emphasis role="bold">ID:</emphasis>
1060 <literal>wan</literal>.</para>
1061
1062 <para><emphasis role="bold">Type:</emphasis>
1063 <literal>tap</literal>.</para>
1064
1065 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1066 <literal>ibm_br</literal>.</para>
1067
1068 <para>Click <literal>Create</literal>.</para>
1069 </listitem>
1070
1071 <listitem>
1072 <para>Create the <literal>lan</literal> Interface:</para>
1073
1074 <para><emphasis role="bold">ID:</emphasis>
1075 <literal>lan</literal>.</para>
1076
1077 <para><emphasis role="bold">Type:</emphasis> <literal>dpdk</literal>
1078 tap.</para>
1079
1080 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1081 <literal>sfc_br</literal>.</para>
1082
1083 <para>Click <literal>Create</literal>.</para>
1084 </listitem>
1085 </itemizedlist>
1086 </section>
1087
1088 <section id="pfSense_inst_device1">
1089 <title>pfSense VNF Instantiation on device1</title>
1090
1091 <para>Instantiate the pfSense VNF by selecting the ucpe1 device, then the
1092 VNF menu -&gt; <literal>Instances</literal> -&gt;
1093 <literal>Add</literal>.</para>
1094
1095 <para>Use the following values to fill the required fields:</para>
1096
1097 <itemizedlist>
1098 <listitem>
1099 <para><emphasis role="bold">Name:</emphasis>
1100 <literal>Pfsense_ucpe1</literal>.</para>
1101 </listitem>
1102
1103 <listitem>
1104 <para><emphasis role="bold">VNF Type:</emphasis>
1105 <literal>pfSense</literal>.</para>
1106 </listitem>
1107
1108 <listitem>
1109 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
1110 </listitem>
1111
1112 <listitem>
1113 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
1114 </listitem>
1115
1116 <listitem>
1117 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
1118 </listitem>
1119
1120 <listitem>
1121 <para><emphasis role="bold">Cloud Init File:</emphasis>
1122 <filename>pfsense_192_168_1_1.iso</filename>.</para>
1123
1124 <para>Click <literal>Domain Update Script</literal>.</para>
1125 </listitem>
1126
1127 <listitem>
1128 <para>Create the <literal>wan</literal> Interface:</para>
1129
1130 <para><emphasis role="bold">ID:</emphasis>
1131 <literal>wan</literal>.</para>
1132
1133 <para><emphasis role="bold">Type:</emphasis>
1134 <literal>tap</literal>.</para>
1135
1136 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1137 <literal>sfc_br</literal>.</para>
1138
1139 <para>Click <literal>Create</literal>.</para>
1140 </listitem>
1141
1142 <listitem>
1143 <para>Create the <literal>lan</literal> Interface:</para>
1144
1145 <para><emphasis role="bold">ID:</emphasis>
1146 <literal>lan</literal>.</para>
1147
1148 <para><emphasis role="bold">Type:</emphasis>
1149 <literal>tap</literal>.</para>
1150
1151 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1152 <literal>lan_br</literal>.</para>
1153
1154 <para>Click <literal>Create</literal>.</para>
1155 </listitem>
1156
1157 <listitem>
1158 <para>Create the <literal>mgmt</literal> Interface:</para>
1159
1160 <para><emphasis role="bold">ID:</emphasis>
1161 <literal>mgmt</literal>.</para>
1162
1163 <para><emphasis role="bold">Type:</emphasis>
1164 <literal>tap</literal>.</para>
1165
1166 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1167 <literal>vnf_mgmt_br</literal>.</para>
1168
1169 <para>Click <literal>Create</literal>.</para>
1170 </listitem>
1171 </itemizedlist>
1172 </section>
1173
1174 <section id="flexiwan_inst_device2">
1175 <title>FlexiWAN VNF Instantiation on device2</title>
1176
1177 <para>Instantiate the FlexiWAN VNF by selecting the ucpe2 device, then the
1178 VNF menu -&gt; <literal>Instances</literal> -&gt;
1179 <literal>Add</literal>.</para>
1180
1181 <para>Use the following values to fill the required fields:</para>
1182
1183 <itemizedlist>
1184 <listitem>
1185 <para><emphasis role="bold">Name:</emphasis>
1186 <literal>Flexiwan_ucpe2</literal>.</para>
1187 </listitem>
1188
1189 <listitem>
1190 <para><emphasis role="bold">VNF Type:</emphasis>
1191 <literal>flexiWAN</literal>.</para>
1192 </listitem>
1193
1194 <listitem>
1195 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
1196 </listitem>
1197
1198 <listitem>
1199 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
1200 </listitem>
1201
1202 <listitem>
1203 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
1204 </listitem>
1205
1206 <listitem>
1207 <para><emphasis role="bold">Cloud Init File:</emphasis>
1208 <filename>flexiWAN_cloudinit.iso</filename>.</para>
1209
1210 <note>
1211 <para>Example image provided. Please see the Appendix for details on
1212 how to change the configuration and create a new cloud-init iso
1213 image.</para>
1214 </note>
1215
1216 <para>Click <literal>Domain Update Script</literal>.</para>
1217 </listitem>
1218
1219 <listitem>
1220 <para>Create the <literal>wan</literal> Interface:</para>
1221
1222 <para><emphasis role="bold">ID:</emphasis>
1223 <literal>wan</literal>.</para>
1224
1225 <para><emphasis role="bold">Type:</emphasis>
1226 <literal>tap</literal>.</para>
1227
1228 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1229 <literal>ibm_br</literal>.</para>
1230
1231 <para>Click <literal>Create</literal>.</para>
1232 </listitem>
1233
1234 <listitem>
1235 <para>Create the <literal>lan</literal> Interface:</para>
1236
1237 <para><emphasis role="bold">ID:</emphasis>
1238 <literal>lan</literal>.</para>
1239
1240 <para><emphasis role="bold">Type:</emphasis>
1241 <literal>tap</literal>.</para>
1242
1243 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1244 <literal>sfc_br</literal>.</para>
1245
1246 <para>Click <literal>Create</literal>.</para>
1247 </listitem>
1248 </itemizedlist>
1249 </section>
1250
1251 <section id="pfSense_inst_device2">
1252 <title>pfSense VNF Instantiation on device2</title>
1253
1254 <para>Instantiate the pfSense VNF by selecting the ucpe2 device, then the
1255 VNF menu -&gt; <literal>Instances</literal> -&gt;
1256 <literal>Add</literal>.</para>
1257
1258 <para>Use the following values to fill the required fields:</para>
1259
1260 <itemizedlist>
1261 <listitem>
1262 <para><emphasis role="bold">Name:</emphasis>
1263 <literal>Pfsense_ucpe2</literal>.</para>
1264 </listitem>
1265
1266 <listitem>
1267 <para><emphasis role="bold">VNF Type:</emphasis>
1268 <literal>pfSense</literal>.</para>
1269 </listitem>
1270
1271 <listitem>
1272 <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
1273 </listitem>
1274
1275 <listitem>
1276 <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
1277 </listitem>
1278
1279 <listitem>
1280 <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
1281 </listitem>
1282
1283 <listitem>
1284 <para><emphasis role="bold">Cloud Init File:</emphasis>
1285 <filename>pfsense_192_168_2_1.iso</filename>.</para>
1286
1287 <para>Click <literal>Domain Update Script</literal>.</para>
1288 </listitem>
1289
1290 <listitem>
1291 <para>Create the <literal>wan</literal> Interface:</para>
1292
1293 <para><emphasis role="bold">ID:</emphasis>
1294 <literal>wan</literal>.</para>
1295
1296 <para><emphasis role="bold">Type:</emphasis>
1297 <literal>tap</literal>.</para>
1298
1299 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1300 <literal>sfc_br</literal>.</para>
1301
1302 <para>Click <literal>Create</literal>.</para>
1303 </listitem>
1304
1305 <listitem>
1306 <para>Create the <literal>lan</literal> Interface:</para>
1307
1308 <para><emphasis role="bold">ID:</emphasis>
1309 <literal>lan</literal>.</para>
1310
1311 <para><emphasis role="bold">Type:</emphasis>
1312 <literal>tap</literal>.</para>
1313
1314 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1315 <literal>lan_br</literal>.</para>
1316
1317 <para>Click <literal>Create</literal>.</para>
1318 </listitem>
1319
1320 <listitem>
1321 <para>Create the <literal>mgmt</literal> Interface:</para>
1322
1323 <para><emphasis role="bold">ID:</emphasis>
1324 <literal>mgmt</literal>.</para>
1325
1326 <para><emphasis role="bold">Type:</emphasis>
1327 <literal>tap</literal>.</para>
1328
1329 <para><emphasis role="bold">IF Name:</emphasis> Bridge:
1330 <literal>vnf_mgmt_br</literal>.</para>
1331
1332 <para>Click <literal>Create</literal>.</para>
1333 </listitem>
1334 </itemizedlist>
1335
1336 <para>Once all VNFs are up and running, the setup is ready for final VNF
1337 configuration and testing.</para>
1338
1339 <figure>
1340 <title>SD-WAN branch-to-branch connection setup Overview</title>
1341
1342 <mediaobject>
1343 <imageobject>
1344 <imagedata align="center" contentwidth="600"
1345 fileref="images/br_to_br_conn_overview.png" />
1346 </imageobject>
1347 </mediaobject>
1348 </figure>
1349
1350 <para>In order to have the full setup working properly, a tunnel between
1351 two SD-WAN devices needs to be created. The FlexiWAN VNF provides the
1352 functionality to create the VPN tunnel.</para>
1353 </section>
1354
1355 <section id="flexiwan_config">
1356 <title>FlexiWAN configuration</title>
1357
1358 <para>Connect to <ulink
1359 url="https://app.flexiwan.com">https://app.flexiwan.com</ulink> and make
1360 sure you have an account and at least two valid device tokens. For more
1361 information please contact the flexiWAN VNF provider.</para>
1362
1363 <para>Proceed to the Inventory menu, click on <literal>Devices</literal>,
1364 the devices should already be present and need to be configured.</para>
1365
1366 <para><emphasis role="bold">How to configure a device</emphasis></para>
1367
1368 <orderedlist>
1369 <listitem>
1370 <para>Select each device and make sure to set the following
1371 values:</para>
1372
1373 <para><table>
1374 <tgroup cols="2">
1375 <tbody>
1376 <row>
1377 <entry>Device1(ucpe1)</entry>
1378
1379 <entry>Device2(ucpe2)</entry>
1380 </row>
1381
1382 <row>
1383 <entry>Device Name: Device1</entry>
1384
1385 <entry>Device Name: Device2</entry>
1386 </row>
1387
1388 <row>
1389 <entry>Description: Set IPv4 for the second interface
1390 (ens3): 10.0.1.1/24.</entry>
1391
1392 <entry>Description: Set IPv4 for the second interface
1393 (ens3): 10.0.2.1/24.</entry>
1394 </row>
1395
1396 <row>
1397 <entry>Set "Approved".</entry>
1398
1399 <entry>Set "Approved".</entry>
1400 </row>
1401
1402 <row>
1403 <entry>Click "Update Device".</entry>
1404
1405 <entry>Click "Update Device".</entry>
1406 </row>
1407 </tbody>
1408 </tgroup>
1409 </table></para>
1410
1411 <note>
1412 <para>uCPE devices can installed under the same local network, i.e.
1413 having the same public IP, or on different networks (different
1414 public IPs). If both devices are installed under same local network
1415 (same public IP), delete the public IP address from the device
1416 configuration before creating a tunnel: <ulink
1417 url="https://app.flexiwan.com">https://app.flexiwan.com</ulink>
1418 -&gt; <literal>Inventory</literal> -&gt; <literal>Devices</literal>
1419 -&gt; <literal>&lt;device&gt;</literal> -&gt; Public IP.</para>
1420 </note>
1421 </listitem>
1422
1423 <listitem>
1424 <para>Select the "&gt;" option for each device to be put in the
1425 "running" state.</para>
1426 </listitem>
1427
1428 <listitem>
1429 <para>Wait for each "vRouter" device to also enter the "running"
1430 state.</para>
1431 </listitem>
1432
1433 <listitem>
1434 <para>Select the main top up checkbox in order to select all devices
1435 and hit "Create Tunnels". At this moment a direct connection should be
1436 available between those two devices. You can check if the tunnel was
1437 created by selecting Inventory -&gt; Tunnels.</para>
1438 </listitem>
1439 </orderedlist>
1440 </section>
1441
1442 <section id="pfsense_config">
1443 <title>pfSense configuration</title>
1444
1445 <para>For the pfSense VNF there is no need for manual configuration. The
1446 configuration provided into the cloud init image is good enough to run the
1447 setup.</para>
1448
1449 <para>The management interface can be accessed from a web browser at:
1450 <literal>https://&lt;deviceIP&gt;:60002</literal></para>
1451 </section>
1452</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml
index 0261844..78bf5ed 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml
@@ -5,42 +5,42 @@
5 <para>In order to remove the setup created in the previous chapter all 5 <para>In order to remove the setup created in the previous chapter all
6 components need to be deleted in reverse order:</para> 6 components need to be deleted in reverse order:</para>
7 7
8 <orderedlist> 8 <orderedlist spacing="compact">
9 <listitem> 9 <listitem>
10 <para>Select the ucpe1 target, access the <emphasis>VNF</emphasis> menu 10 <para>Select the ucpe1 device, access the <emphasis>VNF</emphasis> menu
11 then <literal>Instances FlexiWAN and pfSense</literal> and press 11 then <literal>Instances FlexiWAN and pfSense</literal> and press
12 Delete.</para> 12 Delete.</para>
13 </listitem> 13 </listitem>
14 14
15 <listitem> 15 <listitem>
16 <para>Select the ucpe1 target, access the 16 <para>Select the ucpe1 device, access the
17 <emphasis>Configuration</emphasis> menu, then 17 <emphasis>Configuration</emphasis> menu, then
18 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>. Select 18 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>. Select
19 all bridges and press Delete.</para> 19 all bridges and press Delete.</para>
20 </listitem> 20 </listitem>
21 21
22 <listitem> 22 <listitem>
23 <para>Select the ucpe1 target, access the 23 <para>Select the ucpe1 device, access the
24 <emphasis>Configuration</emphasis> menu, then 24 <emphasis>Configuration</emphasis> menu, then
25 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces</literal>. 25 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces</literal>.
26 Select all interfaces and press Delete.</para> 26 Select all interfaces and press Delete.</para>
27 </listitem> 27 </listitem>
28 28
29 <listitem> 29 <listitem>
30 <para>Select the ucpe2 target, access the <emphasis>VNF</emphasis> menu 30 <para>Select the ucpe2 device, access the <emphasis>VNF</emphasis> menu
31 then <literal>Instances FlexiWAN and pfSense</literal> and press 31 then <literal>Instances FlexiWAN and pfSense</literal> and press
32 Delete.</para> 32 Delete.</para>
33 </listitem> 33 </listitem>
34 34
35 <listitem> 35 <listitem>
36 <para>Select the ucpe2 target, access the 36 <para>Select the ucpe2 device, access the
37 <emphasis>Configuration</emphasis> menu, then 37 <emphasis>Configuration</emphasis> menu, then
38 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>. Select 38 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>. Select
39 all bridges and press Delete.</para> 39 all bridges and press Delete.</para>
40 </listitem> 40 </listitem>
41 41
42 <listitem> 42 <listitem>
43 <para>Select the ucpe2 target, access the 43 <para>Select the ucpe2 device, access the
44 <emphasis>Configuration</emphasis> menu, then 44 <emphasis>Configuration</emphasis> menu, then
45 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces</literal>. 45 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces</literal>.
46 Select all interfaces and press Delete.</para> 46 Select all interfaces and press Delete.</para>
@@ -48,7 +48,14 @@
48 48
49 <listitem> 49 <listitem>
50 <para>Access the <emphasis>VNF</emphasis> menu, select 50 <para>Access the <emphasis>VNF</emphasis> menu, select
51 <literal>Descriptors</literal>. Select all bundles press Delete.</para> 51 <literal>Descriptors</literal>. Select each descriptor and off-board
52 them.</para>
53 </listitem>
54
55 <listitem>
56 <para>Access the <emphasis>Applications</emphasis> menu, select
57 <literal>Offline Config</literal>. Select both device configurations and
58 delete them.</para>
52 </listitem> 59 </listitem>
53 </orderedlist> 60 </orderedlist>
54</chapter> \ No newline at end of file 61</chapter> \ No newline at end of file
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml
index fa3b07e..85ea1f4 100644
--- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml
+++ b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml
@@ -13,7 +13,8 @@
13 13
14 <listitem> 14 <listitem>
15 <para>Connect to: <literal>https://&lt;publicIP&gt;:60002</literal> with 15 <para>Connect to: <literal>https://&lt;publicIP&gt;:60002</literal> with
16 the username: admin and the password: pfsense.<note> 16 the username: admin and the password: pfsense.
17 <note>
17 <para>Please make sure the WAN interface of each device has access 18 <para>Please make sure the WAN interface of each device has access
18 to the internet.</para> 19 to the internet.</para>
19 </note></para> 20 </note></para>
@@ -29,8 +30,9 @@
29 </listitem> 30 </listitem>
30 31
31 <listitem> 32 <listitem>
32 <para>Check for a dynamic IP. The pfSense LAN interface is configured 33 <para>Check for a dynamic IP. The pfSense LAN interface is configured with a DHCP server and should provide an IP 192.168.1/2.XXX:
33 with a DHCP server:<programlisting>&gt; dhclient eth1 34
35 <programlisting>&gt; dhclient eth1
34&gt; ping 192.168.2.1</programlisting></para> 36&gt; ping 192.168.2.1</programlisting></para>
35 </listitem> 37 </listitem>
36 </orderedlist> 38 </orderedlist>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-08 08:20:52 +0000