summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-nfv-access-example-usecases
diff options
context:
space:
mode:
authorSona Sarmadi <sona.sarmadi@enea.com>2019-10-28 14:36:03 +0100
committerMartin Borg <martin.borg@enea.com>2019-10-28 15:56:34 +0100
commit6b685c3cc9bea959053aed08a894931701df8cbb (patch)
tree918d044bf73b942dad1ba84045dc1f85a74a00ed /doc/book-enea-nfv-access-example-usecases
parentda96e6664ca96bc1e8cf1329a816ad191c82f51c (diff)
downloadel_releases-nfv-access-6b685c3cc9bea959053aed08a894931701df8cbb.tar.gz
ExampleUseCases: fortigate VNF interfaces order
The Fortigate SD-WAN use case assumes that interfaces are added in the order listed below: • Port1 - VNF Mgr: Set the type to DPDK and connect it to the vnfmgrbr bridge. • Port2 - WAN: Set the type to DPDK and connect it to the wanbr bridge. • Port3 - LAN: Set the type to DPDK and connect it to the lanbr bridge. The example doesn't work if we add interfaces in other order. Change-Id: I151472bbc04d3c6cfe5375a932db5ee7ee831a6a Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>
Diffstat (limited to 'doc/book-enea-nfv-access-example-usecases')
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml77
1 files changed, 68 insertions, 9 deletions
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 fcb8c87..06b1701 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
@@ -32,13 +32,14 @@
32 <para>VNF image:</para> 32 <para>VNF image:</para>
33 33
34 <listitem> 34 <listitem>
35 <para>FortiGate VNF. Please contact Fortinet to get a VNF image and its license file.</para> 35 <para>FortiGate VNF. Please contact Fortinet to get a VNF image and
36 its license file.</para>
36 </listitem> 37 </listitem>
37 </itemizedlist> 38 </itemizedlist>
38 39
39 <itemizedlist> 40 <itemizedlist>
40 <para>VNF Configuration files, provided with your Enea 41 <para>VNF Configuration files, provided with your Enea NFV Access
41 NFV Access release:</para> 42 release:</para>
42 43
43 <listitem> 44 <listitem>
44 <para><filename>fortigate-basic-fw.conf</filename>.</para> 45 <para><filename>fortigate-basic-fw.conf</filename>.</para>
@@ -54,8 +55,8 @@
54 <title>FortiGate VNF as a Firewall</title> 55 <title>FortiGate VNF as a Firewall</title>
55 56
56 <para>Enea provides an example of a simple basic firewall configuration 57 <para>Enea provides an example of a simple basic firewall configuration
57 for the FortiGate VNF. FortiGate In-Band Management is a 58 for the FortiGate VNF. FortiGate In-Band Management is a feature used for
58 feature used for running FortiGate Management traffic over WAN.</para> 59 running FortiGate Management traffic over WAN.</para>
59 60
60 <para>Instructions on how to alter the default configuration are provided 61 <para>Instructions on how to alter the default configuration are provided
61 in section <olink targetdoc="book_enea_nfv_access_example_usecases" 62 in section <olink targetdoc="book_enea_nfv_access_example_usecases"
@@ -320,11 +321,69 @@
320 </listitem> 321 </listitem>
321 </itemizedlist> 322 </itemizedlist>
322 323
323 <para><emphasis role="bold">Onboarding the FortiGate 324 <para><emphasis role="bold">Onboarding the VNF</emphasis>:</para>
324 VNF</emphasis>:</para> 325
326 <para>Onboard the FortiGate VNF by filling the required fields with the
327 following values:</para>
328
329 <itemizedlist spacing="compact">
330 <listitem>
331 <para><emphasis role="bold">VM Image File</emphasis>: Provide the
332 path to the FortiGate VNF qcow2 image.</para>
333 </listitem>
334
335 <listitem>
336 <para><emphasis role="bold">Memory in MB</emphasis>: 1024</para>
337 </listitem>
338
339 <listitem>
340 <para><emphasis role="bold">Num of CPUs</emphasis>: 1</para>
341 </listitem>
342
343 <listitem>
344 <para><emphasis role="bold">Storage in GB</emphasis>: 20</para>
345 </listitem>
325 346
326 <para>See the onboarding parameters detailed in the previous use-case 347 <listitem>
327 above.</para> 348 <para><emphasis role="bold">Interfaces</emphasis>: Add 3 interfaces
349 in the same order as listed below:</para>
350
351 <itemizedlist spacing="compact">
352 <listitem>
353 <para><emphasis role="bold">vnfmgr</emphasis>: to connect it to
354 the <literal>vnfmgrbr</literal> bridge.</para>
355 </listitem>
356
357 <listitem>
358 <para><emphasis role="bold">wan:</emphasis> to connect it to the
359 <literal>wanbr</literal> bridge.</para>
360 </listitem>
361
362 <listitem>
363 <para><emphasis role="bold">lan:</emphasis> to connect it to the
364 <literal>lanbr</literal> bridge.</para>
365 </listitem>
366 </itemizedlist>
367 </listitem>
368
369 <listitem>
370 <para><emphasis role="bold">Cloud-init Datasource</emphasis>:
371 ConfigDrive</para>
372 </listitem>
373
374 <listitem>
375 <para><emphasis role="bold">Cloud-init Disk Type</emphasis>:
376 cdrom</para>
377 </listitem>
378
379 <listitem>
380 <para><emphasis role="bold">Cloud-init content file</emphasis>: Add
381 a license file entry.</para>
382 </listitem>
383 </itemizedlist>
384
385 <note><para>The order of the interfaces that need to be added must be exactly
386 as listed above or else onboarding and in turn instantiation will fail.</para></note>
328 387
329 <para><emphasis role="bold">Instantiating the FortiGate 388 <para><emphasis role="bold">Instantiating the FortiGate
330 VNF</emphasis>:</para> 389 VNF</emphasis>:</para>