summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjaar <aroosa.jamshaid@enea.com>2020-01-20 14:55:30 +0100
committerMiruna Paun <mrpa@enea.se>2020-01-28 13:28:53 +0100
commitab617d889d170121bc3a055a2f1503d9cac65394 (patch)
treef56725c2d9f57992feda6a9774a471b3fca89b92
parent5e210a7422278efccd5a3caae727c8292c5850d0 (diff)
downloadel_releases-nfv-access-ab617d889d170121bc3a055a2f1503d9cac65394.tar.gz
Text changes in example use cases
Update of prerequisities for all example use cases. Update of memory requirement for VNF chaining example. Change-Id: I0aee42c2de3cb3ec8250db51eb1ffc6fc9dc48e2 Signed-off-by: jaar <aroosa.jamshaid@enea.com>
Diffstat
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml180
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml174
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml150
3 files changed, 286 insertions, 218 deletions
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
index 7d69d43..1da91fe 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
@@ -5,54 +5,6 @@
5 <para>The Clavister VNF is a telco-ready, carrier-grade virtual next 5 <para>The Clavister VNF is a telco-ready, carrier-grade virtual next
6 generation firewall.</para> 6 generation firewall.</para>
7 7
8 <section id="prere_clav_vnf">
9 <title>Prerequisites</title>
10
11 <para>System requirements for the uCPE devices:</para>
12
13 <itemizedlist>
14 <listitem>
15 <para>1 Network Interface</para>
16 </listitem>
17
18 <listitem>
19 <para>2 GB of RAM memory</para>
20 </listitem>
21 </itemizedlist>
22
23 <para>The following files are needed for this example use case:</para>
24
25 <itemizedlist>
26 <para>VNF images:</para>
27
28 <listitem>
29 <para>Enea Test VNF. Please contact Enea to get this image.</para>
30 </listitem>
31
32 <listitem>
33 <para>Clavister VNF. Please contact Clavister to get this
34 image.</para>
35 </listitem>
36 </itemizedlist>
37
38 <itemizedlist>
39 <para>VNF Configuration files, these files are provided with your Enea
40 NFV Access release:</para>
41
42 <listitem>
43 <para><filename>clavister-cloudinit.conf</filename>.</para>
44 </listitem>
45
46 <listitem>
47 <para><filename>enea-vnf-iperf-client.conf</filename>.</para>
48 </listitem>
49
50 <listitem>
51 <para><filename>enea-vnf-iperf-server.conf</filename>.</para>
52 </listitem>
53 </itemizedlist>
54 </section>
55
56 <section id="clav_vnf"> 8 <section id="clav_vnf">
57 <title>Clavister VNF using an Open vSwitch Bridge</title> 9 <title>Clavister VNF using an Open vSwitch Bridge</title>
58 10
@@ -61,20 +13,71 @@
61 applications. The uCPE devices are connected using OVS-DPDK 13 applications. The uCPE devices are connected using OVS-DPDK
62 bridges.</para> 14 bridges.</para>
63 15
64 <figure> 16 <section id="prere_clav_vnf">
65 <title>Clavister VNF using an Open vSwitch bridge</title> 17 <title>Prerequisites</title>
18
19 <para>Two uCPE devices will be required for this setup. The system
20 requirements for each uCPE device are:</para>
21
22 <itemizedlist>
23 <listitem>
24 <para>1 Network Interface</para>
25 </listitem>
26
27 <listitem>
28 <para>2 GB of RAM memory</para>
29 </listitem>
30 </itemizedlist>
31
32 <para>The following files are needed for this example use-case:</para>
66 33
67 <mediaobject> 34 <itemizedlist>
68 <imageobject> 35 <listitem>
69 <imagedata align="center" contentwidth="600" 36 <para>Enea Test VNF image. Please contact Enea to get this image.</para>
70 fileref="images/uc_clavister_bridge.png" /> 37 </listitem>
71 </imageobject> 38
72 </mediaobject> 39 <listitem>
73 </figure> 40 <para>Clavister VNF image. Please contact Clavister to get this
41 image.</para>
42 </listitem>
43
44 <listitem><para>VNF Configuration files. These files are provided with your Enea
45 NFV Access release:</para>
46
47 <itemizedlist spacing="compact">
48 <listitem><para><filename>clavister-cloudinit.conf</filename>.</para></listitem>
49 <listitem><para><filename>enea-vnf-iperf-client.conf</filename>.</para></listitem>
50 <listitem><para><filename>enea-vnf-iperf-server.conf</filename>.</para></listitem>
51 </itemizedlist>
52 </listitem>
53 </itemizedlist>
54 </section>
74 55
75 <section id="clav_vnf_setup_1"> 56 <section id="clav_vnf_setup_1">
76 <title>Use-case Setup</title> 57 <title>Use-case Setup</title>
77 58
59 <para>In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE
60 device 2 runs two Enea Test VNFs with iPerf client and server
61 applications. The uCPE devices are connected using OVS-DPDK
62 bridges.</para>
63
64 <figure>
65 <title>Clavister VNF using an Open vSwitch bridge</title>
66
67 <mediaobject>
68 <imageobject>
69 <imagedata align="center" contentwidth="600"
70 fileref="images/uc_clavister_bridge.png" />
71 </imageobject>
72 </mediaobject>
73 </figure>
74
75 <note>
76 <para>When connecting, the uCPE devices can use a back-to-back or a VPN connection.
77 An appropriate interface with the required capabilities needs to be chosen for
78 this purpose.</para>
79 </note>
80
78 <para><emphasis role="bold">Network Configuration:</emphasis></para> 81 <para><emphasis role="bold">Network Configuration:</emphasis></para>
79 82
80 <orderedlist> 83 <orderedlist>
@@ -301,24 +304,63 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10</programlisting>
301 <section id="clav_example_sriov"> 304 <section id="clav_example_sriov">
302 <title>Clavister VNF using SR-IOV</title> 305 <title>Clavister VNF using SR-IOV</title>
303 306
304 <para>The following use-case is essentially the same as the one detailed 307 <section id="prere_clav_vnf_sriov">
305 above, in this scenario however, the uCPE devices are connected using 308 <title>Prerequisites</title>
306 SR-IOV, with two virtual functions.</para> 309
310 <para>Two uCPE devices will be required for this setup. The system
311 requirements for each uCPE device are:</para>
307 312
308 <figure> 313 <itemizedlist>
309 <title>Clavister VNF using SR-IOV</title> 314 <listitem>
315 <para>1 Network Interface</para>
316 </listitem>
317
318 <listitem>
319 <para>2 GB of RAM memory</para>
320 </listitem>
321 </itemizedlist>
310 322
311 <mediaobject> 323 <para>The following files are needed for this example use-case:</para>
312 <imageobject> 324
313 <imagedata align="center" contentwidth="600" 325 <itemizedlist>
314 fileref="images/uc_clavister_sriov.png" /> 326 <listitem>
315 </imageobject> 327 <para>Enea Test VNF image. Please contact Enea to get this image.</para>
316 </mediaobject> 328 </listitem>
317 </figure> 329
330 <listitem>
331 <para>Clavister VNF image. Please contact Clavister to get this
332 image.</para>
333 </listitem>
334
335 <listitem><para>VNF Configuration files. These files are provided with your Enea
336 NFV Access release:</para>
337 <itemizedlist spacing="compact">
338 <listitem><para><filename>clavister-cloudinit.conf</filename>.</para></listitem>
339 <listitem><para><filename>enea-vnf-iperf-client.conf</filename>.</para></listitem>
340 <listitem><para><filename>enea-vnf-iperf-server.conf</filename>.</para></listitem>
341 </itemizedlist>
342 </listitem>
343 </itemizedlist>
344 </section>
318 345
319 <section id="clav_vnf_setup_2"> 346 <section id="clav_vnf_setup_2">
320 <title>Use-case Setup</title> 347 <title>Use-case Setup</title>
321 348
349 <para>The following use-case is essentially the same as the one detailed
350 above, in this scenario however, the uCPE devices are connected using
351 SR-IOV, with two virtual functions.</para>
352
353 <figure>
354 <title>Clavister VNF using SR-IOV</title>
355
356 <mediaobject>
357 <imageobject>
358 <imagedata align="center" contentwidth="600"
359 fileref="images/uc_clavister_sriov.png" />
360 </imageobject>
361 </mediaobject>
362 </figure>
363
322 <para><emphasis role="bold">Network Configuration:</emphasis></para> 364 <para><emphasis role="bold">Network Configuration:</emphasis></para>
323 365
324 <orderedlist> 366 <orderedlist>
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 1187b07..547cda4 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
@@ -7,50 +7,6 @@
7 appliances. The virtual appliances can be integrated in Firewall or SD-WAN 7 appliances. The virtual appliances can be integrated in Firewall or SD-WAN
8 solution development.</para> 8 solution development.</para>
9 9
10 <section id="forti_firewall_prereq">
11 <title>Prerequisites</title>
12
13 <para>System requirements for the uCPE device:</para>
14
15 <itemizedlist>
16 <listitem>
17 <para>4 x Network Interfaces</para>
18 </listitem>
19
20 <listitem>
21 <para>4 cores</para>
22 </listitem>
23
24 <listitem>
25 <para>4 GB of RAM memory</para>
26 </listitem>
27 </itemizedlist>
28
29 <para>The following files are needed for this example use case:</para>
30
31 <itemizedlist>
32 <para>VNF image:</para>
33
34 <listitem>
35 <para>FortiGate VNF. Please contact Fortinet to get a VNF image and
36 its license file.</para>
37 </listitem>
38 </itemizedlist>
39
40 <itemizedlist>
41 <para>VNF Configuration files, provided with your Enea NFV Access
42 release:</para>
43
44 <listitem>
45 <para><filename>fortigate-basic-fw.conf</filename>.</para>
46 </listitem>
47
48 <listitem>
49 <para><filename>fortigate-sdwan&lt;x&gt;.conf</filename>.</para>
50 </listitem>
51 </itemizedlist>
52 </section>
53
54 <section id="fortigate_firewall_uc_1"> 10 <section id="fortigate_firewall_uc_1">
55 <title>FortiGate VNF as a Firewall</title> 11 <title>FortiGate VNF as a Firewall</title>
56 12
@@ -66,20 +22,57 @@
66 xpointer="element(book_enea_nfv_access_example_usecases/1)" /></olink> 22 xpointer="element(book_enea_nfv_access_example_usecases/1)" /></olink>
67 Manual.</para> 23 Manual.</para>
68 24
69 <figure> 25 <section id="forti_firewall_prereq">
70 <title>Fortigate VNF as a Firewall</title> 26 <title>Prerequisites</title>
27
28 <para>System requirements for the uCPE device:</para>
29
30 <itemizedlist>
31 <listitem>
32 <para>4 x Network Interfaces</para>
33 </listitem>
34
35 <listitem>
36 <para>4 cores</para>
37 </listitem>
38
39 <listitem>
40 <para>4 GB of RAM memory</para>
41 </listitem>
42 </itemizedlist>
43
44 <para>The following files are needed for this example use-case:</para>
45
46 <itemizedlist>
47 <listitem>
48 <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and
49 its license file.</para>
50 </listitem>
71 51
72 <mediaobject> 52 <listitem><para>VNF Configuration files, provided with your Enea NFV Access
73 <imageobject> 53 release:</para>
74 <imagedata align="center" contentwidth="600" 54 <itemizedlist spacing="compact">
75 fileref="images/uc_fortigate_fw.png" /> 55 <listitem><para><filename>fortigate-basic-fw.conf</filename>.</para></listitem>
76 </imageobject> 56 <listitem><para><filename>fortigate-sdwan&lt;x&gt;.conf</filename>.</para></listitem>
77 </mediaobject> 57 </itemizedlist>
78 </figure> 58 </listitem>
59 </itemizedlist>
60 </section>
79 61
80 <section id="exam_setup_fortifirewall"> 62 <section id="exam_setup_fortifirewall">
81 <title>Use-case Setup</title> 63 <title>Use-case Setup</title>
82 64
65 <figure>
66 <title>Fortigate VNF as a Firewall</title>
67
68 <mediaobject>
69 <imageobject>
70 <imagedata align="center" contentwidth="600"
71 fileref="images/uc_fortigate_fw.png" />
72 </imageobject>
73 </mediaobject>
74 </figure>
75
83 <para><emphasis role="bold">Network Configuration</emphasis>:</para> 76 <para><emphasis role="bold">Network Configuration</emphasis>:</para>
84 77
85 <para>Since the firewall uses three External Network Interfaces, three 78 <para>Since the firewall uses three External Network Interfaces, three
@@ -234,6 +227,13 @@
234 <literal>Outgoing Interface</literal> type to 227 <literal>Outgoing Interface</literal> type to
235 <literal>DPDK</literal> and connect it to the 228 <literal>DPDK</literal> and connect it to the
236 <literal>lan2</literal> ovs bridge.</para> 229 <literal>lan2</literal> ovs bridge.</para>
230
231 <note>
232 <para>The names of the ports used during instantiation need to be
233 the same as the ones described above, as the same names will be used in
234 the configuration files provided for this example use-case.
235 </para>
236 </note>
237 </listitem> 237 </listitem>
238 </itemizedlist> 238 </itemizedlist>
239 </section> 239 </section>
@@ -279,20 +279,64 @@
279 <para>Example SD-WAN configurations for the FortiGate VNF are provided by 279 <para>Example SD-WAN configurations for the FortiGate VNF are provided by
280 Enea.</para> 280 Enea.</para>
281 281
282 <figure> 282 <section id="forti_sdwan_vpn_prereq">
283 <title>Fortigate VNF as an SD-WAN or a VPN</title> 283 <title>Prerequisites</title>
284
285 <para>Two uCPE devices will be needed for this setup. The system
286 requirements for each uCPE device are:</para>
287
288 <itemizedlist>
289 <listitem>
290 <para>4 x Network Interfaces</para>
291 </listitem>
292
293 <listitem>
294 <para>4 cores</para>
295 </listitem>
296
297 <listitem>
298 <para>4 GB of RAM memory</para>
299 </listitem>
300 </itemizedlist>
301
302 <para>The following files are needed for this example use-case:</para>
303
304 <itemizedlist>
305 <listitem>
306 <para>FortiGate VNF image. Please contact Fortinet to get a VNF image and
307 its license file.</para>
308 </listitem>
284 309
285 <mediaobject> 310 <listitem><para>VNF Configuration files, provided with your Enea NFV Access
286 <imageobject> 311 release:</para>
287 <imagedata align="center" contentwidth="600" 312 <itemizedlist spacing="compact">
288 fileref="images/uc_fortigate_sdwan.png" /> 313 <listitem><para><filename>fortigate-basic-fw.conf</filename>.</para></listitem>
289 </imageobject> 314 <listitem><para><filename>fortigate-sdwan&lt;x&gt;.conf</filename>.</para></listitem>
290 </mediaobject> 315 </itemizedlist>
291 </figure> 316 </listitem>
317 </itemizedlist>
318 </section>
292 319
293 <section id="forti_examsetup_uc2"> 320 <section id="forti_examsetup_uc2">
294 <title>Use-case Setup</title> 321 <title>Use-case Setup</title>
295 322
323 <figure>
324 <title>Fortigate VNF as an SD-WAN or a VPN</title>
325
326 <mediaobject>
327 <imageobject>
328 <imagedata align="center" contentwidth="600"
329 fileref="images/uc_fortigate_sdwan.png" />
330 </imageobject>
331 </mediaobject>
332 </figure>
333
334 <note>
335 <para>When connecting, the uCPE devices can use a back-to-back or a VPN connection.
336 An appropriate interface with the required capabilities needs to be chosen for
337 this purpose.</para>
338 </note>
339
296 <para><emphasis role="bold">Network Configuration:</emphasis></para> 340 <para><emphasis role="bold">Network Configuration:</emphasis></para>
297 341
298 <para>Since the SD-WAN VNF uses three External Network Interfaces, three 342 <para>Since the SD-WAN VNF uses three External Network Interfaces, three
@@ -466,6 +510,12 @@
466 <para>Instantiate the FortiGate VNF on uCPE device 1 using the 510 <para>Instantiate the FortiGate VNF on uCPE device 1 using the
467 <literal>sdwan1</literal> example configuration file.</para> 511 <literal>sdwan1</literal> example configuration file.</para>
468 512
513 <note>
514 <para>The names of the ports used during instantiation need to be the
515 same as the ones described above, as the same names will be used in
516 the configuration files provided for this example use-case.</para>
517 </note>
518
469 <para>To complete the branch-to-branch setup, configure <literal>uCPE 519 <para>To complete the branch-to-branch setup, configure <literal>uCPE
470 device 2</literal> in the same way as <literal>uCPE device 1</literal>. 520 device 2</literal> in the same way as <literal>uCPE device 1</literal>.
471 Make sure to use the <literal>sdwan2</literal> configuration file for 521 Make sure to use the <literal>sdwan2</literal> configuration file for
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 18bc226..83dd51e 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
@@ -11,83 +11,72 @@
11 <para>In the example setup the following commercial VNFs are used: Juniper 11 <para>In the example setup the following commercial VNFs are used: Juniper
12 vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.</para> 12 vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.</para>
13 13
14 <section id="preq_chaining">
15 <title>Prerequisites</title>
16
17 <para>System requirements for the uCPE device:</para>
18
19 <itemizedlist>
20 <listitem>
21 <para>3 x Network Interfaces</para>
22 </listitem>
23
24 <listitem>
25 <para>4 GB of RAM memory</para>
26 </listitem>
27 </itemizedlist>
28
29 <para>The following files are needed for this example use case:</para>
30
31 <itemizedlist>
32 <para>VNF images:</para>
33
34 <listitem>
35 <para>Fortigate VNF.</para>
36 </listitem>
37
38 <listitem>
39 <para>Juniper vSRX VNF.</para>
40 </listitem>
41 </itemizedlist>
42
43 <para>For VNF images and their license files, please contact the VNF
44 provider.</para>
45
46 <itemizedlist>
47 <para>VNF Configuration files, provided with your Enea NFV Access
48 Release:</para>
49
50 <listitem>
51 <para><filename>vSRX-domain-update-script</filename>.</para>
52 </listitem>
53
54 <listitem>
55 <para><filename>vSRX-Site&lt;x&gt;.conf</filename>.</para>
56 </listitem>
57
58 <listitem>
59 <para><filename>FortiFW-Site&lt;x&gt;.conf</filename>.</para>
60 </listitem>
61 </itemizedlist>
62 </section>
63
64 <section id="VNF_chain_intro"> 14 <section id="VNF_chain_intro">
65 <title>VNF Chaining with FortiGate</title> 15 <title>VNF Chaining with FortiGate</title>
66 16
67 <para>The setup requires two physical appliances (uCPEs), each of them 17 <section id="preq_chaining">
68 having three DPDK-compatible NICs and one interface available for uCPE 18 <title>Prerequisites</title>
69 management (i.e. connected to Enea uCPE Manager). On each uCPE, one of the
70 DPDK-compatible interfaces is connected back-to-back with one interface
71 from the other uCPE device. This link simulates a WAN/uplink
72 connection.</para>
73 19
74 <para>Optionally, one additional device (PC/laptop) can be connected on 20 <para>Two uCPE devices will be needed for this setup. The system
75 the LAN port of each branch to run LAN-to-LAN connectivity tests.</para> 21 requirements for each uCPE device are:</para>
76 22
77 <figure> 23 <itemizedlist>
78 <title>VNF Chaining with Fortigate</title> 24 <listitem>
25 <para>4 x Network Interfaces</para>
26 </listitem>
79 27
80 <mediaobject> 28 <listitem>
81 <imageobject> 29 <para>4 GB of RAM memory</para>
82 <imagedata align="center" contentwidth="600" 30 </listitem>
83 fileref="images/uc_vnf_chaining.png" /> 31 </itemizedlist>
84 </imageobject> 32
85 </mediaobject> 33 <note>
86 </figure> 34 <para>On each uCPE device, 3 interfaces need to be DPDK compliant and one
35 of these needs to be connected back-to-back to the other uCPE
36 device. This link simulates a WAN/uplink connection. Optionally,
37 one additional device (PC/laptop) can be connected on the LAN port
38 of each branch to run LAN-to-LAN connectivity tests.</para>
39 </note>
40
41 <para>The following files are needed for this example use-case:</para>
42
43 <note><para>To procure the VNF image files and their licenses, please contact each respective VNF
44 provider.</para></note>
45
46 <itemizedlist>
47 <listitem>
48 <para>Fortigate VNF image file.</para>
49 </listitem>
50
51 <listitem>
52 <para>Juniper vSRX VNF image file.</para>
53 </listitem>
54
55 <listitem><para>VNF Configuration files, provided with your Enea NFV Access
56 Release:</para>
57 <itemizedlist spacing="compact">
58 <listitem><para><filename>vSRX-domain-update-script</filename>.</para></listitem>
59 <listitem><para><filename>vSRX-Site&lt;x&gt;.conf</filename>.</para></listitem>
60 <listitem><para><filename>FortiFW-Site&lt;x&gt;.conf</filename>.</para></listitem>
61 </itemizedlist>
62 </listitem>
63 </itemizedlist>
64 </section>
87 65
88 <section id="exam_setup_chain"> 66 <section id="exam_setup_chain">
89 <title>Use-case Setup</title> 67 <title>Use-case Setup</title>
90 68
69 <figure>
70 <title>VNF Chaining with Fortigate</title>
71
72 <mediaobject>
73 <imageobject>
74 <imagedata align="center" contentwidth="600"
75 fileref="images/uc_vnf_chaining.png" />
76 </imageobject>
77 </mediaobject>
78 </figure>
79
91 <para><emphasis role="bold">Network Configuration</emphasis>:</para> 80 <para><emphasis role="bold">Network Configuration</emphasis>:</para>
92 81
93 <para>Both branches in the example have similar setups, therefore 82 <para>Both branches in the example have similar setups, therefore
@@ -139,7 +128,7 @@
139 <note> 128 <note>
140 <para>The networking setup (Steps 1-3) can be modeled using the 129 <para>The networking setup (Steps 1-3) can be modeled using the
141 Offline Configuration entry, so that it is automatically 130 Offline Configuration entry, so that it is automatically
142 provisioned on the uCPE, once it gets enrolled into the management 131 provisioned on the uCPE device, once it gets enrolled into the management
143 system (uCPE Manager).</para> 132 system (uCPE Manager).</para>
144 </note> 133 </note>
145 </listitem> 134 </listitem>
@@ -152,12 +141,12 @@
152 <para>Onboard Juniper vSRX using the VNF by filling the required 141 <para>Onboard Juniper vSRX using the VNF by filling the required
153 fields with the following values:</para> 142 fields with the following values:</para>
154 143
155 <itemizedlist> 144 <itemizedlist spacing="compact">
156 <listitem> 145 <listitem>
157 <para>The Flavor selected must have at least 2 CPUs and 4 GB RAM 146 <para>The Flavor selected must have at least 2 CPUs and 3 GB RAM
158 since vSRX is quite resource consuming.</para> 147 since vSRX is quite resource consuming.</para>
159 148
160 <para>Tested-inhouse with 4 vCPUs/ 6 GB RAM.</para> 149 <para>Tested in-house with 4 vCPUs/ 3 GB RAM.</para>
161 </listitem> 150 </listitem>
162 151
163 <listitem> 152 <listitem>
@@ -178,7 +167,7 @@
178 <itemizedlist> 167 <itemizedlist>
179 <listitem> 168 <listitem>
180 <para>The Flavor selected can be quite light in resource 169 <para>The Flavor selected can be quite light in resource
181 consumption, e.g. 1 CPU and 2 GB RAM.</para> 170 consumption, e.g. 1 CPU and 1 GB RAM.</para>
182 </listitem> 171 </listitem>
183 172
184 <listitem> 173 <listitem>
@@ -196,11 +185,6 @@
196 in the Cloud-Init tab files.</para> 185 in the Cloud-Init tab files.</para>
197 </listitem> 186 </listitem>
198 </itemizedlist> 187 </itemizedlist>
199
200 <note>
201 <para>Steps 4-5 are done only once, i.e. they will not be repeated
202 for Site 2.</para>
203 </note>
204 </listitem> 188 </listitem>
205 </orderedlist> 189 </orderedlist>
206 190
@@ -216,7 +200,7 @@
216 file.</para> 200 file.</para>
217 201
218 <note> 202 <note>
219 <para>Please follow the Juniper's documentation to create 203 <para>Please follow Juniper's documentation to create the
220 <filename>vSRX-Site1.iso</filename> file.</para> 204 <filename>vSRX-Site1.iso</filename> file.</para>
221 </note> 205 </note>
222 </listitem> 206 </listitem>
@@ -236,16 +220,12 @@
236 <para>Management interface added to 220 <para>Management interface added to
237 <literal>vnf_mgmt_br</literal>.</para> 221 <literal>vnf_mgmt_br</literal>.</para>
238 </listitem> 222 </listitem>
239 </itemizedlist>
240 223
241 <itemizedlist>
242 <listitem> 224 <listitem>
243 <para>WAN interface added to 225 <para>WAN interface added to
244 <literal>wan_br</literal>.</para> 226 <literal>wan_br</literal>.</para>
245 </listitem> 227 </listitem>
246 </itemizedlist>
247 228
248 <itemizedlist>
249 <listitem> 229 <listitem>
250 <para>LAN interface added to 230 <para>LAN interface added to
251 <literal>sfc_br</literal>.</para> 231 <literal>sfc_br</literal>.</para>
@@ -265,7 +245,7 @@
265 245
266 <itemizedlist> 246 <itemizedlist>
267 <listitem> 247 <listitem>
268 <para>Use <filename>FortiFW-Site1.conf</filename> as Cloud-Init 248 <para>Use <filename>FortiFW-Site1.conf</filename> as the Cloud-Init
269 file.</para> 249 file.</para>
270 </listitem> 250 </listitem>
271 251
@@ -282,16 +262,12 @@
282 <para>Management interface added to 262 <para>Management interface added to
283 <literal>vnf_mgmt_br</literal>.</para> 263 <literal>vnf_mgmt_br</literal>.</para>
284 </listitem> 264 </listitem>
285 </itemizedlist>
286 265
287 <itemizedlist>
288 <listitem> 266 <listitem>
289 <para>WAN interface added to 267 <para>WAN interface added to
290 <literal>sfc_br</literal>.</para> 268 <literal>sfc_br</literal>.</para>
291 </listitem> 269 </listitem>
292 </itemizedlist>
293 270
294 <itemizedlist>
295 <listitem> 271 <listitem>
296 <para>LAN interface added to 272 <para>LAN interface added to
297 <literal>lan_br</literal>.</para> 273 <literal>lan_br</literal>.</para>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-03 10:10:25 +0000