diff options
author | mrpa <miruna.paun@enea.com> | 2020-04-02 14:31:07 +0200 |
---|---|---|
committer | mrpa <miruna.paun@enea.com> | 2020-04-02 14:40:14 +0200 |
commit | 821db501147d91236856695a2f5570e060a13420 (patch) | |
tree | 1761350ae0d59cccd922f5d38f97449fde3fc6c2 /doc | |
parent | 5382d8afd11bb4ffca6801135187af9474b92c28 (diff) | |
download | el_releases-nfv-access-821db501147d91236856695a2f5570e060a13420.tar.gz |
Fixing overlapping footer issues
in eg. usescase manual.
Change-Id: Iee8b37dfd725c060695f0511e84c267dbd82336d
Signed-off-by: mrpa <miruna.paun@enea.com>
Diffstat (limited to 'doc')
4 files changed, 167 insertions, 133 deletions
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 index ceae04f..9b63248 100644 --- 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 | |||
@@ -48,7 +48,7 @@ | |||
48 | <title>Use-case Setup</title> | 48 | <title>Use-case Setup</title> |
49 | 49 | ||
50 | <para><emphasis role="bold">Configuring Network Interfaces on uCPE | 50 | <para><emphasis role="bold">Configuring Network Interfaces on uCPE |
51 | devices:</emphasis><orderedlist spacing="compact"> | 51 | devices:</emphasis><orderedlist> |
52 | <listitem> | 52 | <listitem> |
53 | <para>Log into the uCPE Manager with both username and password | 53 | <para>Log into the uCPE Manager with both username and password |
54 | values: <literal>admin</literal>.</para> | 54 | values: <literal>admin</literal>.</para> |
@@ -130,9 +130,10 @@ | |||
130 | <row> | 130 | <row> |
131 | <entry>Device ID</entry> | 131 | <entry>Device ID</entry> |
132 | 132 | ||
133 | <entry>Also configured during installation of the device (E.g.: Target-15).</entry> | 133 | <entry>Also configured during installation of the device |
134 | (E.g.: Target-15).</entry> | ||
134 | </row> | 135 | </row> |
135 | 136 | ||
136 | <row> | 137 | <row> |
137 | <entry>OK</entry> | 138 | <entry>OK</entry> |
138 | 139 | ||
@@ -151,14 +152,12 @@ | |||
151 | 152 | ||
152 | <listitem> | 153 | <listitem> |
153 | <para>Configure the virtualization infrastructure for 128T VNF by | 154 | <para>Configure the virtualization infrastructure for 128T VNF by |
154 | creating three OVS bridges and a host interface.</para> | 155 | creating three OVS bridges and a host interface:</para> |
155 | 156 | ||
156 | <para>Add the Host Interface by selecting the trgt device, then | 157 | <para>Add the Host Interface by selecting the trgt device, then |
157 | <literal>Configuration -> External Interfaces -> Configuration | 158 | <literal>Configuration -> External Interfaces -> |
158 | -> Add</literal>.</para> | 159 | Configuration -> Add</literal>, and fill in the required fields |
159 | 160 | with the following data:</para> | |
160 | <para>Fill in the required fields with the following | ||
161 | data:</para> | ||
162 | 161 | ||
163 | <table> | 162 | <table> |
164 | <title>Host Interface Details</title> | 163 | <title>Host Interface Details</title> |
@@ -207,11 +206,10 @@ | |||
207 | </tbody> | 206 | </tbody> |
208 | </tgroup> | 207 | </tgroup> |
209 | </table> | 208 | </table> |
210 | 209 | ||
211 | <para>Select the trgt device then: <literal>Configuration -> | 210 | <para>Select the trgt device then: <literal>Configuration -> |
212 | OpenVSwitch -> Bridges -> Add</literal>.</para> | 211 | OpenVSwitch -> Bridges -> Add</literal>, and fill in the |
213 | 212 | required fields for each bridge with the following data from each | |
214 | <para>Fill in the required fields for each bridge with the following data from each | ||
215 | table:</para> | 213 | table:</para> |
216 | 214 | ||
217 | <table> | 215 | <table> |
@@ -313,7 +311,7 @@ | |||
313 | </tbody> | 311 | </tbody> |
314 | </tgroup> | 312 | </tgroup> |
315 | </table> | 313 | </table> |
316 | 314 | ||
317 | <table> | 315 | <table> |
318 | <title>lan_br Bridge Details</title> | 316 | <title>lan_br Bridge Details</title> |
319 | 317 | ||
@@ -687,8 +685,8 @@ | |||
687 | </listitem> | 685 | </listitem> |
688 | 686 | ||
689 | <listitem> | 687 | <listitem> |
690 | <para>Select the trgt uCPE device -> Configuration -> | 688 | <para>Select the trgt uCPE device -> Configuration -> External |
691 | External Interfaces -> Configuration. Select all interfaces -> | 689 | Interfaces -> Configuration. Select all interfaces -> |
692 | Delete.</para> | 690 | Delete.</para> |
693 | </listitem> | 691 | </listitem> |
694 | 692 | ||
@@ -699,4 +697,4 @@ | |||
699 | </orderedlist> | 697 | </orderedlist> |
700 | </section> | 698 | </section> |
701 | </section> | 699 | </section> |
702 | </chapter> | 700 | </chapter> \ No newline at end of file |
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml index a56fc0a..b5e7803 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml | |||
@@ -27,7 +27,7 @@ | |||
27 | 27 | ||
28 | <para>System requirements for the uCPE device:</para> | 28 | <para>System requirements for the uCPE device:</para> |
29 | 29 | ||
30 | <itemizedlist> | 30 | <itemizedlist spacing="compact"> |
31 | <listitem> | 31 | <listitem> |
32 | <para>4 x Network Interfaces</para> | 32 | <para>4 x Network Interfaces</para> |
33 | </listitem> | 33 | </listitem> |
@@ -43,16 +43,17 @@ | |||
43 | 43 | ||
44 | <para>The following file(s) are needed for this example use-case:</para> | 44 | <para>The following file(s) are needed for this example use-case:</para> |
45 | 45 | ||
46 | <itemizedlist> | 46 | <itemizedlist spacing="compact"> |
47 | <listitem> | 47 | <listitem> |
48 | <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and | 48 | <para>FortiGate VNF image. Please contact Fortinet to get a VNF |
49 | its license file.</para> | 49 | image and its license file.</para> |
50 | </listitem> | 50 | </listitem> |
51 | 51 | ||
52 | <listitem><para>VNF Configuration file(s), provided with your Enea NFV Access | 52 | <listitem> |
53 | release: <filename>fortigate-basic-fw.conf</filename>.</para> | 53 | <para>VNF Configuration file(s), provided with your Enea NFV Access |
54 | release: <filename>fortigate-basic-fw.conf</filename>.</para> | ||
54 | </listitem> | 55 | </listitem> |
55 | </itemizedlist> | 56 | </itemizedlist> |
56 | </section> | 57 | </section> |
57 | 58 | ||
58 | <section id="exam_setup_fortifirewall"> | 59 | <section id="exam_setup_fortifirewall"> |
@@ -72,9 +73,11 @@ | |||
72 | <para><emphasis role="bold">Network Configuration</emphasis>:</para> | 73 | <para><emphasis role="bold">Network Configuration</emphasis>:</para> |
73 | 74 | ||
74 | <para>Since the firewall uses three External Network Interfaces, three | 75 | <para>Since the firewall uses three External Network Interfaces, three |
75 | bridges need to be configured. Each bridge provides the ability to connect a physical network interface to the virtual network interface of a VM.</para> | 76 | bridges need to be configured. Each bridge provides the ability to |
77 | connect a physical network interface to the virtual network interface of | ||
78 | a VM.</para> | ||
76 | 79 | ||
77 | <para><emphasis role="bold">Setup of the uCPE device:</emphasis></para> | 80 | <para><emphasis role="bold">Setup of the uCPE device:</emphasis></para> |
78 | 81 | ||
79 | <orderedlist> | 82 | <orderedlist> |
80 | <listitem> | 83 | <listitem> |
@@ -90,7 +93,8 @@ | |||
90 | </listitem> | 93 | </listitem> |
91 | 94 | ||
92 | <listitem> | 95 | <listitem> |
93 | <para>Connect ETH0 to the Lab Network (for Enea uCPE Manager communications).</para> | 96 | <para>Connect ETH0 to the Lab Network (for Enea uCPE Manager |
97 | communications).</para> | ||
94 | </listitem> | 98 | </listitem> |
95 | 99 | ||
96 | <listitem> | 100 | <listitem> |
@@ -103,23 +107,22 @@ | |||
103 | <para>Create three OVS bridges, one for each DPDK network interface | 107 | <para>Create three OVS bridges, one for each DPDK network interface |
104 | (WAN, LAN1 and LAN2).</para> | 108 | (WAN, LAN1 and LAN2).</para> |
105 | 109 | ||
106 | <para>Alternatively, the firewall can be setup to use bridges as | 110 | <para>Alternatively, the firewall can be setup to use bridges as |
107 | connection points for the FortiGate VNF, by replacing the OVS-DPDK | 111 | connection points for the FortiGate VNF, by replacing the OVS-DPDK |
108 | bridges with SR-IOV connection points.</para> | 112 | bridges with SR-IOV connection points.</para> |
109 | |||
110 | <para>Please note that while previously three physical interfaces were | ||
111 | presumed necessary for VNF connection, in the case of a firewall setup | ||
112 | only two physical interfaces are required for the data path (one for WAN | ||
113 | and one for LAN).</para> | ||
114 | 113 | ||
115 | <para>Only two interfaces will be configured as DPDK, with two bridges | 114 | <para>Please note that while previously three physical interfaces |
116 | created, one for each type of connection.</para> | 115 | were presumed necessary for VNF connection, in the case of a |
116 | firewall setup only two physical interfaces are required for the | ||
117 | data path (one for WAN and one for LAN). Only two interfaces will be | ||
118 | configured as DPDK, with two bridges created, one for each type of | ||
119 | connection.</para> | ||
117 | 120 | ||
118 | <note> | 121 | <note> |
119 | <para>At VNF instantiation instead of assigning distinct bridges for | 122 | <para>At VNF instantiation instead of assigning distinct bridges |
120 | each LAN interface, only one will be used for both LAN1 and LAN2, with | 123 | for each LAN interface, only one will be used for both LAN1 and |
121 | no changes in WAN interface configuration.</para> | 124 | LAN2, with no changes in WAN interface configuration.</para> |
122 | </note> | 125 | </note> |
123 | </listitem> | 126 | </listitem> |
124 | </orderedlist> | 127 | </orderedlist> |
125 | 128 | ||
@@ -147,8 +150,8 @@ | |||
147 | </listitem> | 150 | </listitem> |
148 | 151 | ||
149 | <listitem> | 152 | <listitem> |
150 | <para><emphasis role="bold">Interfaces</emphasis>: Add 3 | 153 | <para><emphasis role="bold">Interfaces</emphasis>: Add 3 interfaces |
151 | interfaces (wan, lan1 and lan2).</para> | 154 | (wan, lan1 and lan2).</para> |
152 | </listitem> | 155 | </listitem> |
153 | 156 | ||
154 | <listitem> | 157 | <listitem> |
@@ -221,9 +224,9 @@ | |||
221 | 224 | ||
222 | <note> | 225 | <note> |
223 | <para>The names of the ports used during instantiation need to be | 226 | <para>The names of the ports used during instantiation need to be |
224 | the same as the ones described above, as the same names will be used in | 227 | the same as the ones described above, as the same names will be |
225 | the configuration files provided for this example use-case. | 228 | used in the configuration files provided for this example |
226 | </para> | 229 | use-case.</para> |
227 | </note> | 230 | </note> |
228 | </listitem> | 231 | </listitem> |
229 | </itemizedlist> | 232 | </itemizedlist> |
@@ -276,7 +279,7 @@ | |||
276 | <para>Two uCPE devices will be needed for this setup. The system | 279 | <para>Two uCPE devices will be needed for this setup. The system |
277 | requirements for each uCPE device are:</para> | 280 | requirements for each uCPE device are:</para> |
278 | 281 | ||
279 | <itemizedlist> | 282 | <itemizedlist spacing="compact"> |
280 | <listitem> | 283 | <listitem> |
281 | <para>4 x Network Interfaces</para> | 284 | <para>4 x Network Interfaces</para> |
282 | </listitem> | 285 | </listitem> |
@@ -292,15 +295,17 @@ | |||
292 | 295 | ||
293 | <para>The following files are needed for this example use-case:</para> | 296 | <para>The following files are needed for this example use-case:</para> |
294 | 297 | ||
295 | <itemizedlist> | 298 | <itemizedlist spacing="compact"> |
296 | <listitem> | 299 | <listitem> |
297 | <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and | 300 | <para>FortiGate VNF image. Please contact Fortinet to get a VNF |
298 | its license file.</para> | 301 | image and its license file.</para> |
299 | </listitem> | 302 | </listitem> |
300 | 303 | ||
301 | <listitem><para>VNF Configuration file(s), provided with your Enea NFV Access | 304 | <listitem> |
302 | release: <filename>fortigate-sdwan<x>.conf</filename>.</para></listitem> | 305 | <para>VNF Configuration file(s), provided with your Enea NFV Access |
303 | </itemizedlist> | 306 | release: <filename>fortigate-sdwan<x>.conf</filename>.</para> |
307 | </listitem> | ||
308 | </itemizedlist> | ||
304 | </section> | 309 | </section> |
305 | 310 | ||
306 | <section id="forti_examsetup_uc2"> | 311 | <section id="forti_examsetup_uc2"> |
@@ -316,12 +321,12 @@ | |||
316 | </imageobject> | 321 | </imageobject> |
317 | </mediaobject> | 322 | </mediaobject> |
318 | </figure> | 323 | </figure> |
319 | 324 | ||
320 | <note> | 325 | <note> |
321 | <para>When connecting, the uCPE devices can use a back-to-back or a VPN connection. | 326 | <para>When connecting, the uCPE devices can use a back-to-back or a |
322 | An appropriate interface with the required capabilities needs to be chosen for | 327 | VPN connection. An appropriate interface with the required |
323 | this purpose.</para> | 328 | capabilities needs to be chosen for this purpose.</para> |
324 | </note> | 329 | </note> |
325 | 330 | ||
326 | <para><emphasis role="bold">Network Configuration:</emphasis></para> | 331 | <para><emphasis role="bold">Network Configuration:</emphasis></para> |
327 | 332 | ||
@@ -333,23 +338,28 @@ | |||
333 | <para>Each VNF instance will have a virtual interface for VNF | 338 | <para>Each VNF instance will have a virtual interface for VNF |
334 | management, for the WAN network and for LAN communication.</para> | 339 | management, for the WAN network and for LAN communication.</para> |
335 | 340 | ||
336 | <para><emphasis role="bold">Setup of an Intel Whitebox uCPE device</emphasis>:</para> | 341 | <para><emphasis role="bold">Setup of an Intel Whitebox uCPE |
342 | device</emphasis>:</para> | ||
337 | 343 | ||
338 | <orderedlist> | 344 | <orderedlist> |
339 | <listitem> | 345 | <listitem> |
340 | <para>Connect the <literal>VNFMgr</literal> interfaces to the Lab Network for VNF management access.</para> | 346 | <para>Connect the <literal>VNFMgr</literal> interfaces to the Lab |
347 | Network for VNF management access.</para> | ||
341 | </listitem> | 348 | </listitem> |
342 | 349 | ||
343 | <listitem> | 350 | <listitem> |
344 | <para>Directly connect the <literal>WAN</literal> interfaces back to back (using a cable) or connected via VPN.</para> | 351 | <para>Directly connect the <literal>WAN</literal> interfaces back to |
352 | back (using a cable) or connected via VPN.</para> | ||
345 | </listitem> | 353 | </listitem> |
346 | 354 | ||
347 | <listitem> | 355 | <listitem> |
348 | <para>Connect the <literal>LAN</literal> interfaces to the Test Machine.</para> | 356 | <para>Connect the <literal>LAN</literal> interfaces to the Test |
357 | Machine.</para> | ||
349 | </listitem> | 358 | </listitem> |
350 | 359 | ||
351 | <listitem> | 360 | <listitem> |
352 | <para>Connect the <literal>ETH0</literal> interfaces to the Lab Network (for Enea uCPE Manager communications).</para> | 361 | <para>Connect the <literal>ETH0</literal> interfaces to the Lab |
362 | Network (for Enea uCPE Manager communications).</para> | ||
353 | </listitem> | 363 | </listitem> |
354 | 364 | ||
355 | <listitem> | 365 | <listitem> |
@@ -434,9 +444,11 @@ | |||
434 | will fail.</para> | 444 | will fail.</para> |
435 | </note> | 445 | </note> |
436 | 446 | ||
437 | <para><emphasis role="bold">Instantiating the FortiGate VNF</emphasis>:</para> | 447 | <para><emphasis role="bold">Instantiating the FortiGate |
448 | VNF</emphasis>:</para> | ||
438 | 449 | ||
439 | <para>Instantiate the FortiGate VNF by filling the required fields with the following values:</para> | 450 | <para>Instantiate the FortiGate VNF by filling the required fields with |
451 | the following values:</para> | ||
440 | 452 | ||
441 | <itemizedlist spacing="compact"> | 453 | <itemizedlist spacing="compact"> |
442 | <listitem> | 454 | <listitem> |
@@ -462,8 +474,9 @@ | |||
462 | <listitem> | 474 | <listitem> |
463 | <para><emphasis role="bold">Configuration file</emphasis>: The | 475 | <para><emphasis role="bold">Configuration file</emphasis>: The |
464 | SD-WAN example configuration files provided by Enea: | 476 | SD-WAN example configuration files provided by Enea: |
465 | <literal>fortigate-sdwan1.conf</literal> for the FortiGate VNF on uCPE device 1 and | 477 | <literal>fortigate-sdwan1.conf</literal> for the FortiGate VNF on |
466 | <literal>fortigate-sdwan2.conf</literal> for the FortiGate VNF on uCPE device 2.</para> | 478 | uCPE device 1 and <literal>fortigate-sdwan2.conf</literal> for the |
479 | FortiGate VNF on uCPE device 2.</para> | ||
467 | </listitem> | 480 | </listitem> |
468 | 481 | ||
469 | <listitem> | 482 | <listitem> |
@@ -494,10 +507,10 @@ | |||
494 | the second VNF instantiation.</para> | 507 | the second VNF instantiation.</para> |
495 | 508 | ||
496 | <note> | 509 | <note> |
497 | <para>The names of the ports used during instantiation need to be the | 510 | <para>The names of the ports used during instantiation need to be the |
498 | same as the ones described above, as the same names will be used in | 511 | same as the ones described above, as the same names will be used in |
499 | the configuration files provided for this example use-case.</para> | 512 | the configuration files provided for this example use-case.</para> |
500 | </note> | 513 | </note> |
501 | </section> | 514 | </section> |
502 | 515 | ||
503 | <section id="forti_test_uc2"> | 516 | <section id="forti_test_uc2"> |
@@ -518,8 +531,11 @@ | |||
518 | Machine-2.</para> | 531 | Machine-2.</para> |
519 | </note> | 532 | </note> |
520 | 533 | ||
521 | <para>The Test Machine connected to <literal>uCPE device 1</literal> should be able to ping the Test Machine connected to <literal>uCPE device 2</literal> in this setup, over the WAN connection. The FortiGate VNF management interface can be accessed from a web | 534 | <para>The Test Machine connected to <literal>uCPE device 1</literal> |
522 | browser on the Lab Machine. For more details please see <olink | 535 | should be able to ping the Test Machine connected to <literal>uCPE |
536 | device 2</literal> in this setup, over the WAN connection. The FortiGate | ||
537 | VNF management interface can be accessed from a web browser on the Lab | ||
538 | Machine. For more details please see <olink | ||
523 | targetdoc="book_enea_nfv_access_example_usecases" | 539 | targetdoc="book_enea_nfv_access_example_usecases" |
524 | targetptr="fortigate_webmg">FortiGate VNF Web Management, <xi:include | 540 | targetptr="fortigate_webmg">FortiGate VNF Web Management, <xi:include |
525 | href="../../s_docbuild/olinkdb/pardoc-names.xml" | 541 | href="../../s_docbuild/olinkdb/pardoc-names.xml" |
@@ -587,7 +603,10 @@ virsh console <id of FortiGate VNF></programlisting> | |||
587 | <orderedlist> | 603 | <orderedlist> |
588 | <listitem> | 604 | <listitem> |
589 | <para>Deploy the FortiGate Firewall in its default | 605 | <para>Deploy the FortiGate Firewall in its default |
590 | settings.</para><remark>Maybe more info about how to do it should be added here.</remark> | 606 | settings.</para> |
607 | |||
608 | <remark>Maybe more info about how to do it should be added | ||
609 | here.</remark> | ||
591 | </listitem> | 610 | </listitem> |
592 | 611 | ||
593 | <listitem> | 612 | <listitem> |
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 index 2c256a1..4719399 100644 --- 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 | |||
@@ -55,8 +55,7 @@ | |||
55 | 55 | ||
56 | <mediaobject> | 56 | <mediaobject> |
57 | <imageobject> | 57 | <imageobject> |
58 | <imagedata contentwidth="600" | 58 | <imagedata contentwidth="600" fileref="images/trgt_servicechain.png" /> |
59 | fileref="images/trgt_servicechain.png" /> | ||
60 | </imageobject> | 59 | </imageobject> |
61 | </mediaobject> | 60 | </mediaobject> |
62 | </figure> | 61 | </figure> |
@@ -73,9 +72,8 @@ | |||
73 | 72 | ||
74 | <listitem> | 73 | <listitem> |
75 | <para>Add the trgt uCPE device into the uCPE Manager: | 74 | <para>Add the trgt uCPE device into the uCPE Manager: |
76 | <literal>Devices -> Manage -> Add</literal>.</para> | 75 | <literal>Devices -> Manage -> Add</literal>, and fill in the |
77 | 76 | required fields with the following data:</para> | |
78 | <para>Fill in the required fields with the following data:</para> | ||
79 | 77 | ||
80 | <table> | 78 | <table> |
81 | <title>Device Details</title> | 79 | <title>Device Details</title> |
@@ -143,13 +141,14 @@ | |||
143 | 141 | ||
144 | <entry>null</entry> | 142 | <entry>null</entry> |
145 | </row> | 143 | </row> |
146 | 144 | ||
147 | <row> | 145 | <row> |
148 | <entry>Device ID</entry> | 146 | <entry>Device ID</entry> |
149 | 147 | ||
150 | <entry>Also configured during installation of the device (E.g.: Target-15).</entry> | 148 | <entry>Also configured during installation of the device |
149 | (E.g.: Target-15).</entry> | ||
151 | </row> | 150 | </row> |
152 | 151 | ||
153 | <row> | 152 | <row> |
154 | <entry>OK</entry> | 153 | <entry>OK</entry> |
155 | 154 | ||
@@ -173,9 +172,8 @@ | |||
173 | 172 | ||
174 | <para>Add the Host Interface by selecting the trgt device, then | 173 | <para>Add the Host Interface by selecting the trgt device, then |
175 | <literal>Configuration -> External Interfaces -> | 174 | <literal>Configuration -> External Interfaces -> |
176 | Configuration -> Add</literal>.</para> | 175 | Configuration -> Add</literal>, and fill in the required fields |
177 | 176 | with the following data:</para> | |
178 | <para>Fill in the required fields with the following data:</para> | ||
179 | 177 | ||
180 | <table> | 178 | <table> |
181 | <title>Host Interface Details</title> | 179 | <title>Host Interface Details</title> |
@@ -262,13 +260,13 @@ | |||
262 | 260 | ||
263 | <entry><literal>ibm_br</literal></entry> | 261 | <entry><literal>ibm_br</literal></entry> |
264 | </row> | 262 | </row> |
265 | 263 | ||
266 | <row> | 264 | <row> |
267 | <entry>ovs-bridge-type</entry> | 265 | <entry>ovs-bridge-type</entry> |
268 | 266 | ||
269 | <entry>inbandMgmt</entry> | 267 | <entry>inbandMgmt</entry> |
270 | </row> | 268 | </row> |
271 | 269 | ||
272 | <row> | 270 | <row> |
273 | <entry>Create</entry> | 271 | <entry>Create</entry> |
274 | 272 | ||
@@ -1004,9 +1002,9 @@ | |||
1004 | admin, and leaving the password blank.</para> | 1002 | admin, and leaving the password blank.</para> |
1005 | 1003 | ||
1006 | <note> | 1004 | <note> |
1007 | <para>Make sure the WAN interface of the trgt device has access to | 1005 | <para>Make sure the WAN interface of the trgt device has access to the |
1008 | the internet. The Fortigate VNF requires internet access to validate | 1006 | internet. The Fortigate VNF requires internet access to validate the |
1009 | the license.</para> | 1007 | license.</para> |
1010 | </note> | 1008 | </note> |
1011 | 1009 | ||
1012 | <para>In order to validate the data path connect a test machine to the | 1010 | <para>In order to validate the data path connect a test machine to the |
@@ -1026,8 +1024,8 @@ | |||
1026 | 1024 | ||
1027 | <orderedlist> | 1025 | <orderedlist> |
1028 | <listitem> | 1026 | <listitem> |
1029 | <para>Select the trgt uCPE device -> VNF -> Instances. | 1027 | <para>Select the trgt uCPE device -> VNF -> Instances. Select |
1030 | Select the 128T and Fortigate VNFs -> Delete.</para> | 1028 | the 128T and Fortigate VNFs -> Delete.</para> |
1031 | </listitem> | 1029 | </listitem> |
1032 | 1030 | ||
1033 | <listitem> | 1031 | <listitem> |
@@ -1036,8 +1034,8 @@ | |||
1036 | </listitem> | 1034 | </listitem> |
1037 | 1035 | ||
1038 | <listitem> | 1036 | <listitem> |
1039 | <para>Select the trgt uCPE device -> Configuration -> | 1037 | <para>Select the trgt uCPE device -> Configuration -> External |
1040 | External Interfaces -> Configuration. Select all interfaces -> | 1038 | Interfaces -> Configuration. Select all interfaces -> |
1041 | Delete.</para> | 1039 | Delete.</para> |
1042 | </listitem> | 1040 | </listitem> |
1043 | 1041 | ||
@@ -1048,4 +1046,4 @@ | |||
1048 | </orderedlist> | 1046 | </orderedlist> |
1049 | </section> | 1047 | </section> |
1050 | </section> | 1048 | </section> |
1051 | </chapter> | 1049 | </chapter> \ No newline at end of file |
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml index b003629..b8b0d5e 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml | |||
@@ -29,19 +29,21 @@ | |||
29 | <para>4 GB of RAM memory</para> | 29 | <para>4 GB of RAM memory</para> |
30 | </listitem> | 30 | </listitem> |
31 | </itemizedlist> | 31 | </itemizedlist> |
32 | 32 | ||
33 | <note> | 33 | <note> |
34 | <para>On each uCPE device, 3 interfaces need to be DPDK compliant and one | 34 | <para>On each uCPE device, 3 interfaces need to be DPDK compliant and |
35 | of these needs to be connected back-to-back to the other uCPE | 35 | one of these needs to be connected back-to-back to the other uCPE |
36 | device. This link simulates a WAN/uplink connection. Optionally, | 36 | device. This link simulates a WAN/uplink connection. Optionally, one |
37 | one additional device (PC/laptop) can be connected on the LAN port | 37 | additional device (PC/laptop) can be connected on the LAN port of each |
38 | of each branch to run LAN-to-LAN connectivity tests.</para> | 38 | branch to run LAN-to-LAN connectivity tests.</para> |
39 | </note> | 39 | </note> |
40 | 40 | ||
41 | <para>The following files are needed for this example use-case:</para> | 41 | <para>The following files are needed for this example use-case:</para> |
42 | 42 | ||
43 | <note><para>To procure the VNF image files and their licenses, please contact each respective VNF | 43 | <note> |
44 | provider.</para></note> | 44 | <para>To procure the VNF image files and their licenses, please |
45 | contact each respective VNF provider.</para> | ||
46 | </note> | ||
45 | 47 | ||
46 | <itemizedlist> | 48 | <itemizedlist> |
47 | <listitem> | 49 | <listitem> |
@@ -51,15 +53,26 @@ | |||
51 | <listitem> | 53 | <listitem> |
52 | <para>Juniper vSRX VNF image file.</para> | 54 | <para>Juniper vSRX VNF image file.</para> |
53 | </listitem> | 55 | </listitem> |
54 | 56 | ||
55 | <listitem><para>VNF Configuration files, provided with your Enea NFV Access Release:</para> | 57 | <listitem> |
58 | <para>VNF Configuration files, provided with your Enea NFV Access | ||
59 | Release:</para> | ||
60 | |||
56 | <itemizedlist spacing="compact"> | 61 | <itemizedlist spacing="compact"> |
57 | <listitem><para><filename>vSRX-domain-update-script</filename>.</para></listitem> | 62 | <listitem> |
58 | <listitem><para><filename>vSRX-Site<x>.iso</filename>.</para></listitem> | 63 | <para><filename>vSRX-domain-update-script</filename>.</para> |
59 | <listitem><para><filename>FortiFW-Site<x>.conf</filename>.</para></listitem> | 64 | </listitem> |
60 | </itemizedlist> | 65 | |
66 | <listitem> | ||
67 | <para><filename>vSRX-Site<x>.iso</filename>.</para> | ||
68 | </listitem> | ||
69 | |||
70 | <listitem> | ||
71 | <para><filename>FortiFW-Site<x>.conf</filename>.</para> | ||
72 | </listitem> | ||
73 | </itemizedlist> | ||
61 | </listitem> | 74 | </listitem> |
62 | </itemizedlist> | 75 | </itemizedlist> |
63 | </section> | 76 | </section> |
64 | 77 | ||
65 | <section id="exam_setup_chain"> | 78 | <section id="exam_setup_chain"> |
@@ -74,7 +87,9 @@ | |||
74 | fileref="images/uc_vnf_chaining.png" /> | 87 | fileref="images/uc_vnf_chaining.png" /> |
75 | </imageobject> | 88 | </imageobject> |
76 | </mediaobject> | 89 | </mediaobject> |
77 | </figure><remark>No info about vnf_mgmt_br?</remark> | 90 | </figure> |
91 | |||
92 | <remark>No info about vnf_mgmt_br?</remark> | ||
78 | 93 | ||
79 | <para><emphasis role="bold">Network Configuration</emphasis>:</para> | 94 | <para><emphasis role="bold">Network Configuration</emphasis>:</para> |
80 | 95 | ||
@@ -127,8 +142,8 @@ | |||
127 | <note> | 142 | <note> |
128 | <para>The networking setup (Steps 1-3) can be modeled using the | 143 | <para>The networking setup (Steps 1-3) can be modeled using the |
129 | Offline Configuration entry, so that it is automatically | 144 | Offline Configuration entry, so that it is automatically |
130 | provisioned on the uCPE device, once it gets enrolled into the management | 145 | provisioned on the uCPE device, once it gets enrolled into the |
131 | system (uCPE Manager).</para> | 146 | management system (uCPE Manager).</para> |
132 | </note> | 147 | </note> |
133 | </listitem> | 148 | </listitem> |
134 | </orderedlist> | 149 | </orderedlist> |
@@ -142,8 +157,8 @@ | |||
142 | 157 | ||
143 | <itemizedlist spacing="compact"> | 158 | <itemizedlist spacing="compact"> |
144 | <listitem> | 159 | <listitem> |
145 | <para>The Flavor selected must have at least 2 vCPUs and 4 GB RAM since vSRX is | 160 | <para>The Flavor selected must have at least 2 vCPUs and 4 GB |
146 | quite resource consuming.</para> | 161 | RAM since vSRX is quite resource consuming.</para> |
147 | 162 | ||
148 | <para>Tested in-house with 4 vCPUs/ 6 GB RAM.</para> | 163 | <para>Tested in-house with 4 vCPUs/ 6 GB RAM.</para> |
149 | </listitem> | 164 | </listitem> |
@@ -154,19 +169,21 @@ | |||
154 | </listitem> | 169 | </listitem> |
155 | 170 | ||
156 | <listitem> | 171 | <listitem> |
157 | <para>Select <literal>ISO</literal> as the Cloud-Init Datasource in the Cloud-Init | 172 | <para>Select <literal>ISO</literal> as the Cloud-Init Datasource |
158 | tab.</para> | 173 | in the Cloud-Init tab.</para> |
159 | </listitem> | 174 | </listitem> |
175 | |||
160 | <listitem> | 176 | <listitem> |
161 | <para>Select <literal>cdrom</literal> as the Cloud-Init Disk Type in the Cloud-Init | 177 | <para>Select <literal>cdrom</literal> as the Cloud-Init Disk |
162 | tab.</para></listitem> | 178 | Type in the Cloud-Init tab.</para> |
179 | </listitem> | ||
163 | </itemizedlist> | 180 | </itemizedlist> |
164 | </listitem> | 181 | </listitem> |
165 | 182 | ||
166 | <listitem> | 183 | <listitem> |
167 | <para>Onboard Fortigate FW using the VNF Onboarding Wizard:</para> | 184 | <para>Onboard Fortigate FW using the VNF Onboarding Wizard:</para> |
168 | 185 | ||
169 | <itemizedlist> | 186 | <itemizedlist spacing="compact"> |
170 | <listitem> | 187 | <listitem> |
171 | <para>The Flavor selected can be quite light in resource | 188 | <para>The Flavor selected can be quite light in resource |
172 | consumption, e.g. 1 CPU and 1 GB RAM.</para> | 189 | consumption, e.g. 1 CPU and 1 GB RAM.</para> |
@@ -178,12 +195,14 @@ | |||
178 | </listitem> | 195 | </listitem> |
179 | 196 | ||
180 | <listitem> | 197 | <listitem> |
181 | <para>Select <literal>ConfigDrive</literal> as the Cloud-Init Datasource in the | 198 | <para>Select <literal>ConfigDrive</literal> as the Cloud-Init |
182 | Cloud-Init tab.</para> | 199 | Datasource in the Cloud-Init tab.</para> |
183 | </listitem> | 200 | </listitem> |
184 | 201 | ||
185 | <listitem><para>Select <literal>cdrom</literal> as the Cloud-Init Disk | 202 | <listitem> |
186 | Type in the Cloud-Init tab.</para></listitem> | 203 | <para>Select <literal>cdrom</literal> as the Cloud-Init Disk |
204 | Type in the Cloud-Init tab.</para> | ||
205 | </listitem> | ||
187 | 206 | ||
188 | <listitem> | 207 | <listitem> |
189 | <para>Add <literal>license</literal> as the Cloud-Init content | 208 | <para>Add <literal>license</literal> as the Cloud-Init content |
@@ -250,8 +269,8 @@ | |||
250 | 269 | ||
251 | <itemizedlist> | 270 | <itemizedlist> |
252 | <listitem> | 271 | <listitem> |
253 | <para>Use <filename>FortiFW-Site1.conf</filename> as the Cloud-Init | 272 | <para>Use <filename>FortiFW-Site1.conf</filename> as the |
254 | file.</para> | 273 | Cloud-Init file.</para> |
255 | </listitem> | 274 | </listitem> |
256 | 275 | ||
257 | <listitem> | 276 | <listitem> |
@@ -262,7 +281,7 @@ | |||
262 | <listitem> | 281 | <listitem> |
263 | <para>Add virtual interfaces:</para> | 282 | <para>Add virtual interfaces:</para> |
264 | 283 | ||
265 | <itemizedlist> | 284 | <itemizedlist spacing="compact"> |
266 | <listitem> | 285 | <listitem> |
267 | <para>Management interface added to | 286 | <para>Management interface added to |
268 | <literal>vnf_mgmt_br</literal>.</para> | 287 | <literal>vnf_mgmt_br</literal>.</para> |
@@ -290,8 +309,8 @@ | |||
290 | </orderedlist> | 309 | </orderedlist> |
291 | 310 | ||
292 | <para>At this point the service will be up and running on Site1. Repeat | 311 | <para>At this point the service will be up and running on Site1. Repeat |
293 | the steps to instantiate a VNF for Site2, by changing the configuration files | 312 | the steps to instantiate a VNF for Site2, by changing the configuration |
294 | accordingly.</para> | 313 | files accordingly.</para> |
295 | 314 | ||
296 | <para>After the service is deployed on both branches, the VPN tunnel is | 315 | <para>After the service is deployed on both branches, the VPN tunnel is |
297 | established and LAN to LAN visibility can be verified by connecting one | 316 | established and LAN to LAN visibility can be verified by connecting one |