summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/book.xml5
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml459
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml541
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml (renamed from doc/book-enea-nfv-access-example-usecases/doc/vnf_fortigate.xml)412
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/clav_VNF_demo_SR-IOV.pngbin27484 -> 18909 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/descriptor_button.pngbin86515 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/enea_vnf_demo_overview.pngbin8908 -> 8896 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/host_interface_creation.pngbin10719 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/iperf_client_inttype.pngbin11909 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/iperf_server_inttype.pngbin11060 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/onboarding_status.pngbin9684 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_tab.pngbin12709 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_two.pngbin19759 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_zero.pngbin19759 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/ovs_host_interface.pngbin18805 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/secondtar_hostinterface.pngbin10719 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/testPMD_VNF_PCI.pngbin19081 -> 11945 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/traffic_forward.pngbin20450 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/traffic_terminate.pngbin20490 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_dpdk_int_bind.pngbin6872 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_fortigate_onboard.pngbin7298 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/vnf_instance.pngbin23413 -> 0 bytes
-rwxr-xr-xdoc/book-enea-nfv-access-example-usecases/doc/images/vnf_instances.pngbin70774 -> 0 bytes
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml63
-rw-r--r--doc/book-enea-nfv-access-example-usecases/doc/introduction.xml18
25 files changed, 717 insertions, 781 deletions
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
index 22740d2..0f69570 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
@@ -14,6 +14,9 @@
14 14
15 <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml" 15 <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
16 xmlns:xi="http://www.w3.org/2001/XInclude" /> 16 xmlns:xi="http://www.w3.org/2001/XInclude" />
17
18 <xi:include href="introduction.xml"
19 xmlns:xi="http://www.w3.org/2001/XInclude" />
17 20
18 <xi:include href="clav_vnf_examples.xml" 21 <xi:include href="clav_vnf_examples.xml"
19 xmlns:xi="http://www.w3.org/2001/XInclude" /> 22 xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -21,7 +24,7 @@
21 <xi:include href="enea_vnf_examples.xml" 24 <xi:include href="enea_vnf_examples.xml"
22 xmlns:xi="http://www.w3.org/2001/XInclude" /> 25 xmlns:xi="http://www.w3.org/2001/XInclude" />
23 26
24 <xi:include href="vnf_fortigate.xml" 27 <xi:include href="forti_vnf_examples.xml"
25 xmlns:xi="http://www.w3.org/2001/XInclude" /> 28 xmlns:xi="http://www.w3.org/2001/XInclude" />
26 29
27 <xi:include href="inband_management.xml" 30 <xi:include href="inband_management.xml"
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 ac27ba8..a73c5e8 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
@@ -2,167 +2,179 @@
2<chapter id="clav_vnf_example"> 2<chapter id="clav_vnf_example">
3 <title>Clavister VNF Example Use-cases</title> 3 <title>Clavister VNF Example Use-cases</title>
4 4
5 <section id="clav_vnf"> 5 <section id="prere_clav_vnf">
6 <title>Clavister VNF</title> 6 <title>Prerequisites</title>
7
8 <para>In this use case, <literal>target_1</literal> will run the Clavister
9 VNF and an Open vSwitch bridge, while <literal>target_2</literal> will run
10 two iPerf VNFs.</para>
11
12 <figure>
13 <title>Clavister VNF Example Overview</title>
14
15 <mediaobject>
16 <imageobject>
17 <imagedata align="center" fileref="images/clavister_vnf_diagram.png"
18 scale="50" />
19 </imageobject>
20 </mediaobject>
21 </figure>
22
23 <para><emphasis role="bold">How to setup the target to run the Clavister
24 VNF and an Open vSwitch Bridge</emphasis></para>
25
26 <orderedlist>
27 <para><emphasis role="bold">Configure the Network on target_1 and
28 target_2:</emphasis></para>
29
30 <listitem>
31 <para>From the uCPE Manager select the target_1:
32 <literal>Configuration</literal> -&gt; <literal>OpenVSwitch</literal>
33 -&gt; H<literal>ost Interfaces</literal> -&gt;
34 <literal>Add</literal></para>
35 </listitem>
36 7
37 <listitem> 8 <para>The following files are needed for this example use case:</para>
38 <para>Select the network interface that will be used to connect to the
39 second target, configure it for DPDK, and click
40 <literal>Create</literal> to send the configuration to the
41 target:</para>
42
43 <figure>
44 <title>Host Interface Creation</title>
45
46 <mediaobject>
47 <imageobject>
48 <imagedata align="center"
49 fileref="images/host_interface_creation.png" />
50 </imageobject>
51 </mediaobject>
52 </figure>
53 </listitem>
54
55 <listitem>
56 <para>Create an Open vSwitch bridge (<literal>ovsbr0</literal>) with
57 one DPDK interface by selecting the <literal>Add</literal> button from
58 the <literal>Bridges</literal> tab.</para>
59 </listitem>
60
61 <listitem>
62 <para>Once the bridge creation popup appears, fill the fields and add
63 the physical interface:</para>
64
65 <figure>
66 <title>OVS bridge</title>
67
68 <mediaobject>
69 <imageobject>
70 <imagedata align="center" fileref="images/ovs_bridge_zero.png"
71 scale="80" />
72 </imageobject>
73 </mediaobject>
74 </figure>
75 </listitem>
76
77 <listitem>
78 <para>Repeat the steps above on the target_2, by also using one DPDK
79 interface and creating an OVS bridge.</para>
80 </listitem>
81 </orderedlist>
82
83 <orderedlist>
84 <para><emphasis role="bold">Instantiate the VNFs:</emphasis></para>
85
86 <para>Once the network configuration has been completed on both targets
87 instantiate the VNFs:</para>
88
89 <para><emphasis role="bold">A) Instantiate Clavister VNF on
90 target_1:</emphasis></para>
91 9
10 <itemizedlist>
92 <listitem> 11 <listitem>
93 <para>Select the target_1, then the VNF option from the top toolbar: 12 <para><literal>enea-nfv-access-vnf-qemux86-64.qcow2</literal>. This
94 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt; 13 image is provided with your release.</para>
95 <literal>Add</literal>.</para>
96 </listitem> 14 </listitem>
97 15
98 <listitem> 16 <listitem>
99 <para>Fill in the required information about the 17 <para><literal>clavister-cos-stream-&lt;version&gt;-virtual-x64-generic.qcow2</literal>.
100 <literal>Clavister</literal> VNF, (the default network configuration 18 This image is provided with your release.</para>
101 can be used):</para>
102
103 <figure>
104 <title>VNF Instance</title>
105
106 <mediaobject>
107 <imageobject>
108 <imagedata align="center" fileref="images/vnf_instance.png"
109 scale="80" />
110 </imageobject>
111 </mediaobject>
112 </figure>
113 </listitem>
114 </orderedlist>
115
116 <orderedlist>
117 <para><emphasis role="bold">B) Instantiate two iPerf VNFs (one as client
118 and one as server) on target_2: </emphasis></para>
119
120 <listitem>
121 <para>Instantiate two <literal>iPerf</literal> VNFs on target_2. One
122 will act as the server and the second as the client.</para>
123 </listitem> 19 </listitem>
124 20
125 <listitem> 21 <listitem>
126 <para>Select target_2, then the VNF option from the top toolbar: 22 <para>License for the Clavister VNF (needed as Cloud-Init content in the Cloud-Init tab).
127 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt; 23 This file is available through the VNF provider.</para>
128 <literal>Add</literal>.</para>
129 </listitem> 24 </listitem>
25 </itemizedlist>
26 </section>
130 27
131 <listitem> 28 <section id="clav_vnf">
132 <para>In the <literal>VNF Instance</literal> window, select the first 29 <title>Clavister VNF using Open vSwitch Bridge</title>
133 <literal>iPerf</literal> VNF from the dropdown menu, configure it to
134 act as a server by unchecking the <literal>Client mode IPerf</literal>
135 box, and click the <literal>Create</literal> button.</para>
136 </listitem>
137 30
138 <listitem> 31 <para>In this use-case, uCPE device 1 will run the Clavister VNF and an
139 <para>Select <literal>Add</literal>, enable the <literal>Client mode 32 Open vSwitch bridge, while uCPE device 2 will run two iPerf VNFs.</para>
140 IPerf</literal> checkbox and then click <literal>Create</literal> to
141 instantiate the second <literal>iPerf VNF</literal> as a client, and
142 to run it in client mode.</para>
143 </listitem>
144 33
145 <listitem> 34 <figure>
146 <para>In order to check that traffic is forwarded between the VNFs, 35 <title>Clavister VNF Example Overview</title>
147 connect to the iPerf VNF client console:</para>
148 36
149 <para>Connect to the target_2 by using: <literal>SSH</literal> -&gt; 37 <mediaobject>
150 <literal>user</literal> (root) -&gt;<literal>Connect</literal> and run 38 <imageobject>
151 the following:</para> 39 <imagedata align="center" fileref="images/clavister_vnf_diagram.png"
40 scale="50" />
41 </imageobject>
42 </mediaobject>
43 </figure>
152 44
153 <programlisting>virsh list 45 <section id="clav_vnf_setup_1">
154virsh console 46 <title>uCPE device Setup</title>
155root@qemux86-64:~# iperf3 -c 192.168.10.10</programlisting> 47
156 </listitem> 48 <para><emphasis role="bold">Configure Network interfaces on the uCPE devices:</emphasis></para>
157 </orderedlist> 49
50 <orderedlist>
51 <listitem>
52 <para>From the uCPE Manager select uCPE device 1, then access <literal>Configuration</literal>
53 -&gt; <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces</literal> -&gt;
54 <literal>Add.</literal></para>
55 </listitem>
56
57 <listitem>
58 <para>Select the network interface that will be used to connect to uCPE device 2.
59 Configure it for DPDK, and click <literal>Create</literal> to send the configuration
60 to that uCPE device.</para>
61 </listitem>
62
63 <listitem>
64 <para>Create an Open vSwitch bridge (<literal>ovsbr0</literal>) with
65 one DPDK interface, by selecting the <literal>Add</literal> button
66 from the <literal>Bridges</literal> tab.</para>
67 </listitem>
68
69 <listitem>
70 <para>Once the bridge creation popup appears, fill-in the required fields and add the
71 physical interface.</para>
72 </listitem>
73
74 <listitem>
75 <para>Repeat the steps above on uCPE device 2, using one DPDK interface and creating
76 another OVS bridge.</para>
77 </listitem>
78 </orderedlist>
79 </section>
80
81 <section id="onboard_vnf_clav">
82 <title>Onboard the VNFs</title>
83
84 <orderedlist>
85 <listitem>
86 <para>Select <literal>VNF</literal> -&gt; <literal>Descriptor</literal> -&gt;
87 <literal>On-board</literal>.</para>
88 </listitem>
89
90 <listitem>
91 <para>Select the <literal>VM Image</literal> radio button.</para>
92 </listitem>
93
94 <listitem>
95 <para>Provide the path to the qcow image by selecting <literal>Browse</literal>
96 from <literal>VM image file</literal> option.</para>
97 </listitem>
98
99 <listitem>
100 <para>Fill the required fields below and press <literal>Onboard</literal>:</para>
101
102 <itemizedlist spacing="compact">
103 <listitem>
104 <para><emphasis role="bold">Memory in MB</emphasis>: 1024</para>
105 </listitem>
106
107 <listitem>
108 <para><emphasis role="bold">Nr. of CPUs</emphasis>: 1</para>
109 </listitem>
110
111 <listitem>
112 <para><emphasis role="bold">Storage in GB</emphasis>: 10</para>
113 </listitem>
114 </itemizedlist>
115 </listitem>
116 </orderedlist>
117 </section>
118
119 <section id="instance_vnfs_clav">
120 <title>Instantiate the VNFs</title>
121
122 <para><emphasis role="bold">A) Instantiate the Clavister VNF on uCPE device 1:</emphasis></para>
123
124 <orderedlist>
125 <listitem>
126 <para>Select uCPE device 1, then from the top toolbar: <literal>VNF</literal> -&gt;
127 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
128 </listitem>
129
130 <listitem>
131 <para>Fill in the required information about the Clavister VNF, (the default network
132 configuration can be used) and select <literal>Create</literal>.</para>
133 </listitem>
134 </orderedlist>
135
136 <para><emphasis role="bold">B) Instantiate two Enea VNFs (one as the client and one as the
137 server) on uCPE device 2:</emphasis></para>
138
139 <orderedlist>
140 <listitem>
141 <para>Select uCPE device 2, then from the top toolbar: <literal>VNF</literal> -&gt;
142 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
143 </listitem>
144
145 <listitem>
146 <para>In the new <literal>VNF Instance</literal> window, select the Enea VNF from the
147 dropdown menu, configure it to act as a server by unchecking the <literal>Client mode
148 IPerf</literal> box, and then click <literal>Create</literal>.</para>
149 </listitem>
150
151 <listitem>
152 <para>Select <literal>Add</literal> once more, enable the <literal>Client mode
153 IPerf</literal> checkbox this time, and click <literal>Create</literal> to instantiate
154 the second <literal>iPerf VNF</literal> as a client, and to run it in client mode.</para>
155 </listitem>
156
157 <listitem>
158 <para>In order to check that traffic is forwarded between the two VNFs, connect to the
159 iPerf VNF client console: <literal>SSH</literal> -&gt; <literal>user</literal> (root)
160 -&gt; <literal>Connect</literal> and run the following:</para>
161
162 <programlisting>
163 virsh list
164 virsh console
165 root@qemux86-64:~# iperf3 -c 192.168.10.10
166 </programlisting>
167 </listitem>
168 </orderedlist>
169 </section>
158 </section> 170 </section>
159 171
160 <section id="clav_example_sriov"> 172 <section id="clav_example_sriov">
161 <title>Clavister VNF using SR-IOV</title> 173 <title>Clavister VNF using SR-IOV</title>
162 174
163 <para>In this use case, target 1 will run the iPerf server and iPerf 175 <para>In this use-case, uCPE device 1 will run the iPerf server and iPerf
164 client VNFs using SR-IOV and target 2 will run the Clavister VNF using 176 client VNFs using SR-IOV, while uCPE device 2 will run the Clavister VNF
165 SR-IOV with two virtual functions (vf1 and vf2):</para> 177 using SR-IOV with two virtual functions (vf1 and vf2):</para>
166 178
167 <figure> 179 <figure>
168 <title>Example Overview</title> 180 <title>Example Overview</title>
@@ -175,93 +187,80 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10</programlisting>
175 </mediaobject> 187 </mediaobject>
176 </figure> 188 </figure>
177 189
178 <orderedlist> 190 <section id="clav_vnf_setup_2">
179 <listitem> 191 <title>Example Setup</title>
180 <para>On target 2, create an SR-IOV configuration with 2 virtual 192
181 functions: <literal>Configuration</literal> -&gt; 193 <orderedlist>
182 <literal>OpenVSwitch</literal> -&gt; <literal>Host 194 <listitem>
183 Interfaces</literal> -&gt; <literal>Add</literal>:</para> 195 <para>On uCPE device 2, create an SR-IOV configuration with 2
184 196 virtual functions by selecting <literal>Configuration</literal>
185 <figure> 197 -&gt; <literal>OpenVSwitch</literal> -&gt; <literal>Host
186 <title>SR-IOV configuration with 2 virtual functions</title> 198 Interfaces</literal> -&gt; <literal>Add</literal>:</para>
187 199
188 <mediaobject> 200 <figure>
189 <imageobject> 201 <title>SR-IOV configuration with 2 virtual functions</title>
190 <imagedata align="center" 202
191 fileref="images/sriov_configuration.png" scale="80" /> 203 <mediaobject>
192 </imageobject> 204 <imageobject>
193 </mediaobject> 205 <imagedata align="center"
194 </figure> 206 fileref="images/sriov_configuration.png" scale="80" />
195 </listitem> 207 </imageobject>
196 208 </mediaobject>
197 <listitem> 209 </figure>
198 <para>Instantiate the Clavister VNF on target 2, by clicking 210 </listitem>
199 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt; 211
200 <literal>Add</literal>.</para> 212 <listitem>
201 213 <para>Instantiate the Clavister VNF on uCPE device 2: <literal>VNF</literal>
202 <para>Select <literal>SrIovAdapterPool</literal> as an Interface type 214 -&gt; <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
203 for both Interface1 type and 2 type, before clicking 215 </listitem>
204 <literal>Create</literal>:</para> 216
205 217 <listitem>
206 <figure> 218 <para>Select <literal>SrIovAdapterPool</literal> as an Interface
207 <title>Instantiating the Clavister VNF on target 2</title> 219 type for both Interface 1 type and 2 type, before clicking
208 220 <literal>Create</literal>.</para>
209 <mediaobject> 221
210 <imageobject> 222 <figure>
211 <imagedata align="center" fileref="images/srlov_adap_pool.png" 223 <title>Instantiating the Clavister VNF on uCPE device 2</title>
212 scale="70" /> 224
213 </imageobject> 225 <mediaobject>
214 </mediaobject> 226 <imageobject>
215 </figure> 227 <imagedata align="center" fileref="images/srlov_adap_pool.png"
216 </listitem> 228 scale="70" />
217 229 </imageobject>
218 <listitem> 230 </mediaobject>
219 <para>On target 1, create an SR-IOV interface as done in step 231 </figure>
220 1.</para> 232 </listitem>
221 </listitem> 233
222 234 <listitem>
223 <listitem> 235 <para>On uCPE device 1, create an SR-IOV interface as done in step
224 <para>Create the iPerf server on target 1. Select 236 1.</para>
225 <literal>SrIovAdapterPool</literal> as an Interface type:</para> 237 </listitem>
226 238
227 <figure> 239 <listitem>
228 <title>IPerf Server Interface Type</title> 240 <para>Create the iPerf server on uCPE device 1 and select
229 241 <literal>SrIovAdapterPool</literal> as an Interface type.</para>
230 <mediaobject> 242 </listitem>
231 <imageobject> 243
232 <imagedata align="center" 244 <listitem>
233 fileref="images/iperf_server_inttype.png" scale="70" /> 245 <para>Create the iPerf client on uCPE device 1. Select
234 </imageobject> 246 <literal>SrIovAdapterPool</literal> as an Interface type and tick
235 </mediaobject> 247 the <literal>Client mode IPerf</literal> checkbox.</para>
236 </figure> 248 </listitem>
237 </listitem> 249
238 250 <listitem>
239 <listitem> 251 <para>In order to check that traffic is forwarded between the VNFs,
240 <para>Create the iPerf client on target 1. Select 252 connect to the iPerf VNF client console by using:
241 <literal>SrIovAdapterPool</literal> as an Interface type and tick the 253 <literal>SSH</literal> -&gt; <literal>user</literal> (root)
242 <literal>Client mode IPer</literal> checkbox:</para> 254 -&gt;<literal>Connect</literal> and run the following
243 255 commands:
244 <figure> 256 <programlisting>
245 <title>IPerf Client Interface Type</title> 257 virsh list
246 258 virsh console
247 <mediaobject> 259 root@qemux86-64:~# iperf3 -c 192.168.10.10
248 <imageobject> 260 </programlisting>
249 <imagedata align="center" 261 </para>
250 fileref="images/iperf_client_inttype.png" scale="70" /> 262 </listitem>
251 </imageobject> 263 </orderedlist>
252 </mediaobject> 264 </section>
253 </figure>
254 </listitem>
255
256 <listitem>
257 <para>In order to check that traffic is forwarded between the VNFs,
258 connect to the iPerf VNF client console by using:
259 <literal>SSH</literal> -&gt; <literal>user</literal> (root)
260 -&gt;<literal>Connect</literal> and run the following
261 commands:<programlisting>virsh list
262virsh console
263root@qemux86-64:~# iperf3 -c 192.168.10.10</programlisting></para>
264 </listitem>
265 </orderedlist>
266 </section> 265 </section>
267</chapter> 266</chapter>
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml
index cfb9b72..f2d7910 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/enea_vnf_examples.xml
@@ -1,13 +1,23 @@
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="ISO-8859-1"?>
2<chapter id="enea_vnf_examples"> 2<chapter id="enea_vnf_examples">
3 <title>Enea VNF Example Use-cases</title> 3 <title>Enea VNF Example Use-cases</title>
4 4
5 <section id="prere_enea_vnf">
6 <title>Prerequisites</title>
7
8 <para>The following file(s) are needed for this example use-case:
9 <literal>enea-nfv-access-vnf-qemux86-64.qcow2</literal>. This image is
10 provided with your release.</para>
11 </section>
12
5 <section id="enea_vnf"> 13 <section id="enea_vnf">
6 <title>TestPMD VNF</title> 14 <title>TestPMD VNF</title>
7 15
8 <para>Use case description: pktgen[DPDK] - PHY1 - PHY2 - [DPDK]OVS - 16 <para>In this use-case, <literal>uCPE device 1</literal> will run pktgen
9 VM[DPDK]testpmd(forwarding) - OVS[DPDK] - VM[DPDK] 17 (the DPDK application) and <literal>uCPE device 2</literal> will onboard
10 testpmd(termination).</para> 18 and instantiate two VNFs. One VNF will run <literal>testpmd_fwd</literal>,
19 forwarding traffic, and the other will run <literal>testpmd_term</literal>
20 which will terminate traffic.</para>
11 21
12 <figure> 22 <figure>
13 <title>Enea VNF Example Overview</title> 23 <title>Enea VNF Example Overview</title>
@@ -20,285 +30,254 @@
20 </mediaobject> 30 </mediaobject>
21 </figure> 31 </figure>
22 32
23 <para><emphasis role="bold">How to setup the Enea VNF 33 <section id="enea_vnf_setup">
24 Example</emphasis></para> 34 <title>Example Setup</title>
25 35
26 <para><emphasis role="bold">Configure the Network on target_1 and 36 <para><emphasis role="bold">Configure the Network interface on uCPE
27 target_2:</emphasis></para> 37 devices 1 and 2:</emphasis></para>
28 38
29 <orderedlist> 39 <orderedlist>
30 <listitem> 40 <listitem>
31 <para>Bind the host interfaces to the DPDK by selecting the target 41 <para>Bind the host interfaces to the DPDK by selecting uCPE device 1
32 first, then accessing <literal>Configuration</literal> -&gt; 42 first, then accessing <literal>Configuration</literal> -&gt;
33 <literal>OpenVSwitch</literal> -&gt; <literal>Host 43 <literal>OpenVSwitch</literal> -&gt; <literal>Host
34 Interfaces</literal> -&gt; <literal>Add</literal>:</para> 44 Interfaces</literal> -&gt; <literal>Add</literal>.</para>
35 45 </listitem>
36 <figure> 46
37 <title>Adding OVS Host Interfaces</title> 47 <listitem>
38 48 <para>Select the network interface that will be used to connect to
39 <mediaobject> 49 the second uCPE device and configure it for the DPDK.</para>
40 <imageobject> 50 </listitem>
41 <imagedata align="center" 51
42 fileref="images/ovs_host_interface.png" scale="80" /> 52 <listitem>
43 </imageobject> 53 <para>Select the <literal>Create</literal> button to send the
44 </mediaobject> 54 configuration to uCPE device 1.</para>
45 </figure> 55 </listitem>
46 </listitem> 56
47 57 <listitem>
48 <listitem> 58 <para>Repeat these same steps on uCPE device 2.</para>
49 <para>Select the network interface that will be used to connect to the 59 </listitem>
50 second target and configure it for the DPDK:</para> 60 </orderedlist>
51 61
52 <figure> 62 <para><emphasis role="bold">Create an Open vSwitch bridge on uCPE device
53 <title>Configuring the host interface</title> 63 1:</emphasis></para>
54 64
55 <mediaobject> 65 <para>Create an Open vSwitch bridge (<literal>ovsbr0</literal>) on uCPE
56 <imageobject> 66 device 1, that uses one DPDK interface:</para>
57 <imagedata align="center" 67
58 fileref="images/secondtar_hostinterface.png" 68 <orderedlist>
59 scale="90" /> 69 <listitem><para>Click the <literal>Add</literal> button from the
60 </imageobject> 70 Bridges tab.</para>
61 </mediaobject> 71 </listitem>
62 </figure> 72
63 </listitem> 73 <listitem><para>Select uCPE device 1, then access
64 74 <literal>Configuration</literal> -&gt;<literal>OpenVSwitch</literal>
65 <listitem> 75 -&gt;<literal>Bridges</literal>.</para>
66 <para>Select the <literal>Create</literal> button to send the 76 </listitem>
67 configuration to the target.</para> 77 </orderedlist>
68 </listitem> 78
69 79 <para><emphasis role="bold">Onboard the Enea VNF:</emphasis></para>
70 <listitem> 80
71 <para>Repeat the same steps on the target_2.</para> 81 <orderedlist>
72 </listitem> 82 <listitem>
73 </orderedlist> 83 <para>Select <literal>VNF</literal> -&gt;<literal>Descriptor</literal>
74 84 -&gt; <literal>On-board</literal>.</para>
75 <para><emphasis role="bold">Create an OpenVSwitch bridge on 85 </listitem>
76 target_1:</emphasis></para> 86
77 87 <listitem>
78 <orderedlist> 88 <para>Select the <literal>VM Image</literal> radio button.</para>
79 <listitem> 89 </listitem>
80 <para>Create an OpenVSwitch bridge (<literal>ovsbr0</literal>) on 90
81 target_1 that uses one DPDK interface, by selecting the 91 <listitem>
82 <literal>Add</literal> button from the Bridges tab and then selecting 92 <para>Provide the path to the qcow image by selecting <literal>Browse
83 the target first, then accessing <literal>Configuration</literal> 93 </literal> from the <literal>VM image file</literal> option.</para>
84 -&gt; <literal>OpenVSwitch</literal>-&gt; 94 </listitem>
85 <literal>Bridges</literal>:</para> 95
86 96 <listitem>
87 <figure> 97 <para>Fill the required fields below and press <literal>Onboard</literal>:
88 <title>OVS Bridge Table</title> 98 </para>
89 99
90 <mediaobject> 100 <itemizedlist spacing="compact">
91 <imageobject> 101 <listitem>
92 <imagedata align="center" fileref="images/ovs_bridge_tab.png" 102 <para><emphasis role="bold">Memory in MB</emphasis>: 1024</para>
93 scale="75" /> 103 </listitem>
94 </imageobject> 104
95 </mediaobject> 105 <listitem>
96 </figure> 106 <para><emphasis role="bold">Nr. of CPUs</emphasis>: 1</para>
97 107 </listitem>
98 <figure> 108
99 <title>Adding the interface to the OVS Bridge</title> 109 <listitem>
100 110 <para><emphasis role="bold">Storage in GB</emphasis>: 10</para>
101 <mediaobject> 111 </listitem>
102 <imageobject> 112 </itemizedlist>
103 <imagedata align="center" fileref="images/ovs_bridge_two.png" 113 </listitem>
104 scale="90" /> 114 </orderedlist>
105 </imageobject> 115
106 </mediaobject> 116 <para><emphasis role="bold">Instantiate two VNFs on uCPE device 2:</emphasis></para>
107 </figure> 117
108 </listitem> 118 <orderedlist>
109 </orderedlist> 119 <listitem>
110 120 <para>Select uCPE device 2, then access <literal>VNF</literal> -&gt;
111 <para><emphasis role="bold">Onboard the TestPMD VNF on 121 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para>
112 target_2:</emphasis></para> 122 </listitem>
113 123
114 <para>Onboard the TestPMD VNF on target_2 by selecting the target, then accessing 124 <listitem>
115 <literal>VNF</literal> -&gt; <literal>Descriptor</literal> -&gt; <literal>Add</literal>.</para> 125 <para>Fill-in the required fields and click <literal>Create</literal>.</para>
116 126 </listitem>
117 <para><emphasis role="bold">Instantiate the TestPMD VNF on 127
118 target_2:</emphasis></para> 128 <listitem>
119 129 <para>Configure VNF 1 to forward traffic.</para>
120 <orderedlist> 130 </listitem>
121 <listitem> 131
122 <para>Instantiate TestPMD VNF (testpmd_fwd) on target_2 by selecting 132 <listitem>
123 the target first, then accessing <literal>VNF</literal> -&gt; 133 <para>Configure VNF 2 to terminate traffic.</para>
124 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para> 134 </listitem>
125 </listitem> 135
126 136 <listitem>
127 <listitem> 137 <para>Add Open vSwitch flows to control this traffic:</para>
128 <para>Instantiate TestPMD VNF (testpmd_term) on target_2 by selecting 138
129 the target first, then accessing <literal>VNF</literal> -&gt; 139 <figure>
130 <literal>Instances</literal> -&gt; <literal>Add</literal>.</para> 140 <title>Configuring the FWD flow</title>
131 </listitem> 141
132 142 <mediaobject>
133 <listitem> 143 <imageobject>
134 <para>Configure the VNF (testpmd_fwd) to forward trafic:</para> 144 <imagedata align="center" fileref="images/flow_fwd.png"
135 145 scale="90" />
136 <figure> 146 </imageobject>
137 <title>Configuring the VNF (testpmd_fwd)</title> 147 </mediaobject>
138 148 </figure>
139 <mediaobject> 149
140 <imageobject> 150 <figure>
141 <imagedata align="center" fileref="images/traffic_forward.png" 151 <title>Configuring the TERM flow</title>
142 scale="85" /> 152
143 </imageobject> 153 <mediaobject>
144 </mediaobject> 154 <imageobject>
145 </figure> 155 <imagedata align="center" fileref="images/flow_term.png"
146 </listitem> 156 scale="90" />
147 157 </imageobject>
148 <listitem> 158 </mediaobject>
149 <para>Configure the VNF (testpmd_term) to terminate traffic:</para> 159 </figure>
150 160 </listitem>
151 <figure> 161
152 <title>Configuring the termVNF</title> 162 <listitem>
153 163 <para>Start pktgen on uCPE device 1. Connect to the device by selecting
154 <mediaobject> 164 it first, then access <literal>SSH</literal> -&gt; <literal>user</literal>
155 <imageobject> 165 (root) and perform the following:</para>
156 <imagedata align="center" fileref="images/traffic_terminate.png" 166
157 scale="85" /> 167 <programlisting>
158 </imageobject> 168 cd /usr/share/apps/pktgen/
159 </mediaobject> 169 ./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:05:00.3 -- \
160 </figure> 170 -P -m "[1:2].0"
161 </listitem> 171 Pktgen:/&gt; start 0</programlisting>
162 172
163 <listitem> 173 <note>
164 <para>Add OpenVSwitch flows to control this traffic:</para> 174 <para>The PCI address &lt;0000:05:00.3&gt; used in this example
165 175 varies depending on the uCPE device. To determine the exact PCI
166 <figure> 176 address used, look in the uCPE device specific Network
167 <title>Configuring the FWD flow</title> 177 configuration.</para>
168 178 </note>
169 <mediaobject> 179 </listitem>
170 <imageobject> 180
171 <imagedata align="center" fileref="images/flow_fwd.png" 181 <listitem>
172 scale="90" /> 182 <para>Connect to the forwarder VNF in order to check the traffic
173 </imageobject> 183 statistics, by selecting the uCPE device first, then accessing
174 </mediaobject> 184 <literal>SSH</literal> -&gt; <literal>user</literal> (root):</para>
175 </figure> 185
176 186 <programlisting>
177 <figure> 187 Virsh list
178 <title>Configuring the TERM flow</title> 188 Virsh console 1
179 189 # Qemux86-64 login: root
180 <mediaobject> 190 tail -f /var/log/testpmd-out</programlisting>
181 <imageobject> 191
182 <imagedata align="center" fileref="images/flow_term.png" 192 <figure>
183 scale="90" /> 193 <title>Traffic Statistics</title>
184 </imageobject> 194
185 </mediaobject> 195 <mediaobject>
186 </figure> 196 <imageobject>
187 </listitem> 197 <imagedata align="center"
188 198 fileref="images/connection_information.png"
189 <listitem> 199 scale="70" />
190 <para>Start pktgen on target_1. Connect to the target by selecting the 200 </imageobject>
191 target first, then accessing <literal>SSH</literal> -&gt; 201 </mediaobject>
192 <literal>user</literal> (root) and perform the following:</para> 202 </figure>
193 203 </listitem>
194 <programlisting>cd /usr/share/apps/pktgen/ 204 </orderedlist>
195./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:05:00.3 -- \ 205 </section>
196 -P -m "[1:2].0" 206
197Pktgen:/&gt; start 0</programlisting> 207 <section condition="hidden" id="vnf_pci">
198 208 <title>TestPMD VNF using PCI passthrough</title>
199 <note> 209
200 <para>The PCI address &lt;0000:05:00.3&gt; used in this example 210 <para>In this use case, uCPE device 1 will run the Pktgen and uCPE
201 varies depending on the target. To determine the exact PCI address 211 device 2 will run the TestPMD VNF. Both will be using PCI
202 used, look in the target specific Network configuration.</para> 212 passthrough:</para>
203 </note> 213
204 </listitem> 214 <figure>
205 215 <title>TestPMD VNF using PCI passthrough Overview</title>
206 <listitem> 216
207 <para>Connect to the forwarder VNF in order to check the traffic 217 <mediaobject>
208 statistics by selecting the target first, then accessing 218 <imageobject>
209 <literal>SSH</literal> -&gt; <literal>user</literal> (root):</para> 219 <imagedata align="center" fileref="images/testPMD_VNF_PCI.png"
210 220 scale="65" />
211 <programlisting>Virsh list 221 </imageobject>
212Virsh console 1 222 </mediaobject>
213# Qemux86-64 login: root 223 </figure>
214tail -f /var/log/testpmd-out</programlisting> 224
215 225 <orderedlist>
216 <figure> 226 <listitem>
217 <title>Traffic Statistics</title> 227 <para>Make sure that neither uCPE device 1 nor uCPE device 2 have
218 228 any configured host interfaces by selcting uCPE device :
219 <mediaobject> 229 <literal>Configuration</literal> -&gt;
220 <imageobject> 230 <literal>OpenVSwitch</literal> -&gt; <literal>Host
221 <imagedata align="center" 231 Interfaces</literal>.</para>
222 fileref="images/connection_information.png" 232 </listitem>
223 scale="70" /> 233
224 </imageobject> 234 <listitem>
225 </mediaobject> 235 <para>On uCPE device 1 start the Pktgen VNF. Select
226 </figure> 236 <literal>PciPassthrough</literal> as the Interface type.</para>
227 </listitem> 237
228 </orderedlist> 238 <para>From the drop-down list, select the PCI interface
229 </section> 239 corresponding to the NIC which is connected to uCPE device 2:</para>
230 240
231 <section condition="hidden" id="vnf_pci"> 241 <figure>
232 <title>TestPMD VNF using PCI passthrough</title> 242 <title>Selecting the Pktgen VNF Interface</title>
233 243
234 <para>In this use case, target 1 will run the Pktgen and target 2 will run 244 <mediaobject>
235 the TestPMD VNF. Both will be using PCI passthrough:</para> 245 <imageobject>
236 246 <imagedata align="center"
237 <figure> 247 fileref="images/pciPass_interface.png" scale="70" />
238 <title>TestPMD VNF using PCI passthrough Overview</title> 248 </imageobject>
239 249 </mediaobject>
240 <mediaobject> 250 </figure>
241 <imageobject> 251 </listitem>
242 <imagedata align="center" fileref="images/testPMD_VNF_PCI.png" 252
243 scale="65" /> 253 <listitem>
244 </imageobject> 254 <para>On uCPE device 2, start the TestPmdForwarder VNF. Select
245 </mediaobject> 255 "PciPassthrough" as the Interface type. From the drop-down list,
246 </figure> 256 select the PCI interface corresponding to the NIC which is connected
247 257 to uCPE device 1:</para>
248 <orderedlist> 258
249 <listitem> 259 <figure>
250 <para>Make sure that neither target 1 nor target 2 have any configured 260 <title>Selecting the TestPmdForwarder VNF Interface</title>
251 host interfaces by selcting target: <literal>Configuration</literal> 261
252 -&gt; <literal>OpenVSwitch</literal> -&gt; <literal>Host 262 <mediaobject>
253 Interfaces</literal>.</para> 263 <imageobject>
254 </listitem> 264 <imagedata align="center"
255 265 fileref="images/testpmd_fwdvnf_int.png" scale="70" />
256 <listitem> 266 </imageobject>
257 <para>On target 1 start the Pktgen VNF. Select 267 </mediaobject>
258 <literal>PciPassthrough</literal> as the Interface type.</para> 268 </figure>
259 269 </listitem>
260 <para>From the drop-down list, select the PCI interface corresponding 270
261 to the NIC which is connected to target 2:</para> 271 <listitem>
262 272 <para>To check that traffic is being forwarded from uCPE device 2,
263 <figure> 273 SSH to the uCPE device and connect to the VNFs console:</para>
264 <title>Selecting the Pktgen VNF Interface</title> 274
265 275 <programlisting>Right click on uCPE device 2 and select SSH.
266 <mediaobject>
267 <imageobject>
268 <imagedata align="center" fileref="images/pciPass_interface.png"
269 scale="70" />
270 </imageobject>
271 </mediaobject>
272 </figure>
273 </listitem>
274
275 <listitem>
276 <para>On target 2, start the TestPmdForwarder VNF. Select
277 "PciPassthrough" as the Interface type. From the drop-down list,
278 select the PCI interface corresponding to the NIC which is connected
279 to target 1:</para>
280
281 <figure>
282 <title>Selecting the TestPmdForwarder VNF Interface</title>
283
284 <mediaobject>
285 <imageobject>
286 <imagedata align="center"
287 fileref="images/testpmd_fwdvnf_int.png" scale="70" />
288 </imageobject>
289 </mediaobject>
290 </figure>
291 </listitem>
292
293 <listitem>
294 <para>To check that traffic is being forwarded from target 2, SSH to
295 the target and connect to the VNFs console:</para>
296
297 <programlisting>Right click on target 2 and select SSH.
298Run: virsh list 276Run: virsh list
299Run: virsh console [VM NAME] 277Run: virsh console [VM NAME]
300Run: tail -f /opt/testpmd-out</programlisting> 278Run: tail -f /opt/testpmd-out</programlisting>
301 </listitem> 279 </listitem>
302 </orderedlist> 280 </orderedlist>
281 </section>
303 </section> 282 </section>
304</chapter> 283</chapter>
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
index 2bd0dc3..cc158fe 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_fortigate.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
@@ -32,11 +32,11 @@
32 Descriptor configurations may be needed to support other configurations 32 Descriptor configurations may be needed to support other configurations
33 required by the customer.</para> 33 required by the customer.</para>
34 34
35 <para>Enea can provide assistance to provide alternative VNF Descriptor 35 <para>Enea can offer assistance and provide alternative VNF Descriptor
36 configurations.</para> 36 configurations.</para>
37 37
38 <note> 38 <note>
39 <para>While the prepared FortiGate bundle is provided from Enea Portal, 39 <para>While the prepared FortiGate bundle is available through the Enea Portal,
40 additional content needs to be received from Fortinet directly. The 40 additional content needs to be received from Fortinet directly. The
41 FortiGate VNF license as well as any FortiGate specific documentation 41 FortiGate VNF license as well as any FortiGate specific documentation
42 shall be requested from the local Fortinet sales representatives in your 42 shall be requested from the local Fortinet sales representatives in your
@@ -72,30 +72,30 @@
72 72
73 <tbody> 73 <tbody>
74 <row> 74 <row>
75 <entry>Firewall</entry> 75 <entry align="left">Firewall</entry>
76 76
77 <entry>"All pass" mode</entry> 77 <entry align="left">"All pass" mode</entry>
78 </row> 78 </row>
79 79
80 <row> 80 <row>
81 <entry>WAN (Virtual Port1)</entry> 81 <entry align="left">WAN (Virtual Port1)</entry>
82 82
83 <entry><para>DHCP Client, dynamically assigned IP 83 <entry align="left"><para>DHCP Client, dynamically assigned IP
84 address.</para>FortiGate In-Band 84 address.</para><para>FortiGate In-Band
85 Management<superscript>1</superscript></entry> 85 Management<superscript>1</superscript>.</para></entry>
86 </row> 86 </row>
87 87
88 <row> 88 <row>
89 <entry>WAN (Virtual Port2)</entry> 89 <entry align="left">WAN (Virtual Port2)</entry>
90 90
91 <entry><para>IP address: 172.168.16.1</para>DHCP server (IP range 91 <entry align="left"><para>IP address: 172.168.16.1</para><para>DHCP server (IP range
92 172.168.16.1 - 172.168.16.255).</entry> 92 172.168.16.1 - 172.168.16.255).</para></entry>
93 </row> 93 </row>
94 94
95 <row> 95 <row>
96 <entry>WAN (Virtual Port3)</entry> 96 <entry align="left">WAN (Virtual Port3)</entry>
97 97
98 <entry>Ignored</entry> 98 <entry align="left">Ignored</entry>
99 </row> 99 </row>
100 </tbody> 100 </tbody>
101 </tgroup> 101 </tgroup>
@@ -104,8 +104,8 @@
104 <para><superscript>1</superscript>FortiGate In-Band Management is a 104 <para><superscript>1</superscript>FortiGate In-Band Management is a
105 feature for running FortiGate Management traffic over WAN.</para> 105 feature for running FortiGate Management traffic over WAN.</para>
106 106
107 <para>Instructions on how to alter the default configuration is provided 107 <para>Instructions on how to alter the default configuration are provided
108 in the Fortigate VNF management chapter.</para> 108 in the Fortigate VNF management chapter.<remark>where is this chapter located?</remark></para>
109 109
110 <para><emphasis role="bold">Lab Setup</emphasis></para> 110 <para><emphasis role="bold">Lab Setup</emphasis></para>
111 111
@@ -129,7 +129,7 @@
129 129
130 <tbody> 130 <tbody>
131 <row> 131 <row>
132 <entry>Lab Network</entry> 132 <entry align="left">Lab Network</entry>
133 133
134 <entrytbl cols="1"> 134 <entrytbl cols="1">
135 <tbody> 135 <tbody>
@@ -145,7 +145,7 @@
145 </row> 145 </row>
146 146
147 <row> 147 <row>
148 <entry>Setup of an Intel Whitebox target device</entry> 148 <entry align="left">Setup of an Intel Whitebox uCPE device</entry>
149 149
150 <entrytbl cols="1"> 150 <entrytbl cols="1">
151 <tbody> 151 <tbody>
@@ -174,7 +174,7 @@
174 </row> 174 </row>
175 175
176 <row> 176 <row>
177 <entry>ETH0 connected to Lab Network (for Enea uCPE Manager 177 <entry>ETH0 connected to the Lab Network (for Enea uCPE Manager
178 communications)</entry> 178 communications)</entry>
179 </row> 179 </row>
180 </tbody> 180 </tbody>
@@ -182,7 +182,7 @@
182 </row> 182 </row>
183 183
184 <row> 184 <row>
185 <entry>Setup of a Lab Machine</entry> 185 <entry align="left">Setup of a Lab Machine</entry>
186 186
187 <entrytbl cols="1"> 187 <entrytbl cols="1">
188 <tbody> 188 <tbody>
@@ -202,7 +202,7 @@
202 </row> 202 </row>
203 203
204 <row> 204 <row>
205 <entry>Setup of a Test Machine</entry> 205 <entry align="left">Setup of a Test Machine</entry>
206 206
207 <entrytbl cols="1"> 207 <entrytbl cols="1">
208 <tbody> 208 <tbody>
@@ -222,31 +222,31 @@
222 </row> 222 </row>
223 223
224 <row> 224 <row>
225 <entry>FortiGate VNF</entry> 225 <entry align="left">FortiGate VNF</entry>
226 226
227 <entrytbl cols="1"> 227 <entrytbl cols="1">
228 <tbody> 228 <tbody>
229 <row> 229 <row>
230 <entry>Downloaded the FortiGate VNF Bundle from Enea Portal 230 <entry>Download the FortiGate VNF Bundle from the Enea Portal
231 to the Lab Machine file system. Please see the Download 231 to the Lab Machine file system. Please see the Download
232 Chapter for more details.</entry> 232 Chapter for more details.</entry>
233 </row> 233 </row>
234 234
235 <row> 235 <row>
236 <entry>Downloaded FortiGate configuration examples from the 236 <entry>Download FortiGate configuration examples from the
237 Enea Portal to the Lab Machine file system. Please check the 237 Enea Portal to the Lab Machine file system. Please check the
238 Download Chapter for more details. Unpack the configuration 238 Download Chapter for more details. Unpack the configuration
239 examples on the Lab Machine.</entry> 239 examples on the Lab Machine.</entry>
240 </row> 240 </row>
241 241
242 <row> 242 <row>
243 <entry>Retrieve FortiGate VNF license from Fortinet and 243 <entry>Retrieve the FortiGate VNF license file from Fortinet and
244 store it on the Lab Machine file system. See FortiGate VNF 244 store it on the Lab Machine file system. See FortiGate VNF
245 for details.</entry> 245 for details.</entry>
246 </row> 246 </row>
247 247
248 <row> 248 <row>
249 <entry>Optionally retrieve FortiGate VNF documentation from 249 <entry>Optionally, retrieve FortiGate VNF documentation from
250 Fortinet. See FortiGate VNF for details.</entry> 250 Fortinet. See FortiGate VNF for details.</entry>
251 </row> 251 </row>
252 </tbody> 252 </tbody>
@@ -262,17 +262,21 @@
262 <mediaobject> 262 <mediaobject>
263 <imageobject> 263 <imageobject>
264 <imagedata align="center" fileref="images/intel_whitebox.png" 264 <imagedata align="center" fileref="images/intel_whitebox.png"
265 scale="35" /> 265 scale="45" />
266 </imageobject> 266 </imageobject>
267 </mediaobject> 267 </mediaobject>
268 </figure> 268 </figure>
269 </section>
270
271 <section id="exam_setup_forti">
272 <title>Example Setup</title>
269 273
270 <para><emphasis role="bold">uCPE Networking Setup</emphasis></para> 274 <para><emphasis role="bold">uCPE Networking Setup</emphasis></para>
271 275
272 <para>Before deploying the FortiGate Firewall, the Enea NFV Access 276 <para>Before deploying the FortiGate Firewall, the Enea NFV Access
273 platform has to be configured to the specific networking setup.</para> 277 platform has to be configured to the specific networking setup.</para>
274 278
275 <para>Since the firewall is using three External Network Interfaces, three 279 <para>Since the firewall uses three External Network Interfaces, three
276 bridges need to be configured. Each bridge provides the ability to connect 280 bridges need to be configured. Each bridge provides the ability to connect
277 a physical network interface to the virtual machines' virtual network 281 a physical network interface to the virtual machines' virtual network
278 interface. Each physical to virtual network interface connection is setup 282 interface. Each physical to virtual network interface connection is setup
@@ -292,19 +296,19 @@
292 <note> 296 <note>
293 <para>For more details about interface configuration, please see the 297 <para>For more details about interface configuration, please see the
294 Network Configuration section in the chapter on Configuration 298 Network Configuration section in the chapter on Configuration
295 Options.</para> 299 Options.<remark>where is this chapter and its section located exactly?</remark></para>
296 </note> 300 </note>
297 301
298 <orderedlist> 302 <orderedlist>
299 <listitem> 303 <listitem>
300 <para>Start the setup by preparing each interface for attachment to a 304 <para>Start the setup by preparing each interface for attachment to a
301 bridge. Bind the physical network interfaces to the DPDK by selecting 305 bridge. Bind the physical network interfaces to the DPDK by selecting
302 the target: <literal>Configuration</literal> -&gt; 306 the uCPE device, then accessing: <literal>Configuration</literal> -&gt;
303 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces 307 <literal>OpenVSwitch</literal> -&gt; <literal>Host Interfaces
304 </literal>-&gt; <literal>Add</literal>:</para> 308 </literal>-&gt; <literal>Add</literal>:</para>
305 309
306 <figure> 310 <figure>
307 <title>Binding the physical network interface</title> 311 <title>Binding a physical network interface</title>
308 312
309 <mediaobject> 313 <mediaobject>
310 <imageobject> 314 <imageobject>
@@ -330,15 +334,14 @@
330 </listitem> 334 </listitem>
331 335
332 <listitem> 336 <listitem>
333 <para>Create one OpenVSwitch bridge for each firewall network 337 <para>Create one Open vSwitch bridge for each firewall network
334 connection (WAN, LAN1 and LAN2), by selecting the 338 connection (WAN, LAN1 and LAN2), by selecting:
335 <literal>Add</literal> button from Bridges tab:
336 <literal>Configuration</literal> -&gt; 339 <literal>Configuration</literal> -&gt;
337 <literal>OpenvSwitch</literal>-&gt; <literal>Bridges</literal>. A 340 <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal> -&gt; <literal>Add</literal>.
338 popup like the following should appear:</para> 341 A popup like the following should appear:</para>
339 342
340 <figure> 343 <figure>
341 <title>Creating a bridge each Firewall Net. Connection</title> 344 <title>Creating a bridge for a Firewall Net. Connection</title>
342 345
343 <mediaobject> 346 <mediaobject>
344 <imageobject> 347 <imageobject>
@@ -359,77 +362,45 @@
359 <mediaobject> 362 <mediaobject>
360 <imageobject> 363 <imageobject>
361 <imagedata align="center" 364 <imagedata align="center"
362 fileref="images/configured_bridges.png" scale="65" /> 365 fileref="images/configured_bridges.png" scale="68" />
363 </imageobject> 366 </imageobject>
364 </mediaobject> 367 </mediaobject>
365 </figure> 368 </figure>
366 </listitem> 369 </listitem>
367 </orderedlist> 370 </orderedlist>
371 </section>
368 372
369 <para><emphasis role="bold">Onboarding the FortiGate VNF</emphasis></para> 373 <section id="onboarding_fortigate">
374 <title>Onboarding the FortiGate VNF</title>
370 375
371 <orderedlist> 376 <orderedlist>
372 <listitem> 377 <listitem>
373 <para>To on-board the Fortigate VNF click the <literal>VNF</literal> 378 <para>To onboard the Fortigate VNF select from the top toolbar
374 tab in the top toolbar: <literal>VNF</literal> -&gt; 379 <literal>VNF</literal> -&gt; <literal>Descriptors</literal> -&gt;
375 <literal>Descriptors</literal> -&gt; <literal>On-board </literal>-&gt; 380 <literal>On-board.</literal></para>
376 <literal>Browse</literal> options, and select the
377 <literal>Fortigate.zip</literal> file, before clicking
378 <literal>Send</literal>:</para>
379
380 <figure>
381 <title>Selecting Descriptors</title>
382
383 <mediaobject>
384 <imageobject>
385 <imagedata align="center" fileref="images/descriptor_button.png"
386 scale="45" />
387 </imageobject>
388 </mediaobject>
389 </figure>
390 </listitem> 381 </listitem>
391 382
392 <listitem> 383 <listitem>
393 <para>Wait for the <literal>Onboarding Status</literal> popup to 384 <para>Click <literal>Browse</literal> to view selections, and choose the
394 display the confirmation message (listed in green) and select 385 <literal>Fortigate.zip</literal> file, before clicking <literal>Send</literal>.</para>
395 <literal>OK</literal>:</para>
396
397 <figure>
398 <title>Onboarding the new VNF</title>
399
400 <mediaobject>
401 <imageobject>
402 <imagedata align="center" fileref="images/onboarding_status.png"
403 scale="80" />
404 </imageobject>
405 </mediaobject>
406 </figure>
407 </listitem> 386 </listitem>
408 </orderedlist> 387 </orderedlist>
388 </section>
409 389
410 <para><emphasis role="bold">Instantiate the FortiGate 390 <section id="instance_fortigate">
411 VNF</emphasis></para> 391 <title>Instantiating and Testing the FortiGate VNF</title>
392
393 <para><emphasis role="bold">Instantiate the FortiGate VNF</emphasis></para>
412 394
413 <orderedlist> 395 <orderedlist>
414 <listitem> 396 <listitem>
415 <para>Select the target, then from the top toolbar the select: 397 <para>Select the uCPE device, then from the top toolbar select
416 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt; 398 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt;
417 <literal>Add</literal>:</para> 399 <literal>Add</literal>.</para>
418
419 <figure>
420 <title>Adding Instances to Target</title>
421
422 <mediaobject>
423 <imageobject>
424 <imagedata align="center" fileref="images/vnf_instances.png"
425 scale="50" />
426 </imageobject>
427 </mediaobject>
428 </figure>
429 400
430 <para>Make sure you have downloaded valid license files for the 401 <para>Make sure you have downloaded valid license files for the
431 Fortigate VNF from Fortinet, and the configuration file provided by 402 Fortigate VNF from Fortinet, and the configuration file provided by
432 Enea as examples according to previous instructions.</para> 403 Enea as examples according to the previous instructions.</para>
433 404
434 <figure> 405 <figure>
435 <title>Example License and Configuration files</title> 406 <title>Example License and Configuration files</title>
@@ -437,7 +408,7 @@
437 <mediaobject> 408 <mediaobject>
438 <imageobject> 409 <imageobject>
439 <imagedata align="center" 410 <imagedata align="center"
440 fileref="images/fortigate_licenses.png" scale="75" /> 411 fileref="images/fortigate_licenses.png" scale="70" />
441 </imageobject> 412 </imageobject>
442 </mediaobject> 413 </mediaobject>
443 </figure> 414 </figure>
@@ -467,130 +438,129 @@
467 <row> 438 <row>
468 <entry align="left">Name</entry> 439 <entry align="left">Name</entry>
469 440
470 <entry>The name of the VM which will be created on the target 441 <entry align="left">Name of the VM which will be created on the uCPE
471 device.</entry> 442 device.</entry>
472 </row> 443 </row>
473 444
474 <row> 445 <row>
475 <entry align="left">VNF Type</entry> 446 <entry align="left">VNF Type</entry>
476 447
477 <entry>Name of the on-boarded VNF bundle.</entry> 448 <entry align="left">Name of the onboarded VNF bundle.</entry>
478 </row> 449 </row>
479 450
480 <row> 451 <row>
481 <entry align="left">VIM</entry> 452 <entry align="left">VIM</entry>
482 453
483 <entry>Name and IP address of the device where the VNF has to 454 <entry align="left">Name and IP address of the device where the VNF will
484 be instantiated.</entry> 455 be instantiated.</entry>
485 </row> 456 </row>
486 457
487 <row> 458 <row>
488 <entry align="left">License file</entry> 459 <entry align="left">License file</entry>
489 460
490 <entry>FortiGate license file provided by Fortinet.</entry> 461 <entry align="left">FortiGate license file provided by Fortinet.</entry>
491 </row> 462 </row>
492 463
493 <row> 464 <row>
494 <entry align="left">Configuration file</entry> 465 <entry align="left">Configuration file</entry>
495 466
496 <entry>Firewall example configuration file provided by Enea 467 <entry align="left">Firewall example configuration file provided by Enea
497 <filename>FGVM080000136187_20180828_0353_basic_fw.conf 468 (<filename>FGVM080000136187_20180828_0353_basic_fw.conf
498 </filename></entry> 469 </filename>).</entry>
499 </row> 470 </row>
500 471
501 <row> 472 <row>
502 <entry align="left">Port1 - WAN</entry> 473 <entry align="left">Port1 - WAN</entry>
503 474
504 <entry>Set as dpdk type and connect it to wanmgrbr 475 <entry align="left">Set the External Interface type to Dpdk and connect it to the
505 bridge.</entry> 476 <literal>wanmgrbr</literal> ovs bridge.</entry>
506 </row> 477 </row>
507 478
508 <row> 479 <row>
509 <entry align="left">Port2 - LAN1</entry> 480 <entry align="left">Port2 - LAN1</entry>
510 481
511 <entry>Set as dpdk type and connect it to lan1 bridge.</entry> 482 <entry align="left">Set the Incoming Interface type to Dpdk and connect it to the
483 <literal>lan1</literal> ovs bridge.</entry>
512 </row> 484 </row>
513 485
514 <row> 486 <row>
515 <entry align="left">Port3 - LAN2</entry> 487 <entry align="left">Port3 - LAN2</entry>
516 488
517 <entry>Set as dpdk type and connect it to lan2 bridge.</entry> 489 <entry align="left">Set the Outgoing Interface type to Dpdk and connect it to the
490 <literal>lan2</literal> ovs bridge.</entry>
518 </row> 491 </row>
519 </tbody> 492 </tbody>
520 </tgroup> 493 </tgroup>
521 </table> 494 </table>
522
523 <para>When the instantiation process is completed, the setup is ready
524 for testing.</para>
525 </listitem> 495 </listitem>
526 </orderedlist> 496 </orderedlist>
527 497
528 <para><emphasis role="bold">Test the FortiGate Firewall</emphasis></para> 498 <para><emphasis role="bold">Testing the FortiGate Firewall</emphasis></para>
529 499
530 <para>Connect the Test Machine on the LAN interface and access the 500 <para>Connect the Test Machine on the LAN interface<remark>which lan interface?</remark>
531 internet from the Test Machine to use the firewall on the target 501 and access the internet from the Test Machine to use the firewall on the uCPE device.</para>
532 device.</para>
533 502
534 <note> 503 <note>
535 <para>The connected Test Machine can be a laptop or a target that has 504 <para>The connected Test Machine can be a laptop or a uCPE device. It must have one
536 one interface configured to get an dynamic IP from a DHCP server. The 505 interface configured to get a dynamic IP from a DHCP server. The
537 <literal>dhclient &lt;interface&gt;</literal> command can be used to 506 <literal>dhclient &lt;interface&gt;</literal> command can be used to
538 request an IP address. The received IP must be in the 172.16.1.2 - 507 request an IP address. The received IP must be in the 172.16.1.2 -
539 172.16.1.255 range.</para> 508 172.16.1.255 range.</para>
540 </note> 509 </note>
541 510
542 <figure> 511 <figure>
543 <title>Testing Overview</title> 512 <title>Testing Setup Overview</title>
544 513
545 <mediaobject> 514 <mediaobject>
546 <imageobject> 515 <imageobject>
547 <imagedata align="center" fileref="images/testing_fortigate.png" 516 <imagedata align="center" fileref="images/testing_fortigate.png"
548 scale="50" /> 517 scale="60" />
549 </imageobject> 518 </imageobject>
550 </mediaobject> 519 </mediaobject>
551 </figure> 520 </figure>
552 521
553 <para>In the example above, the FortiGate VNF management interface is 522 <para>In the example above<remark>what example exactly, in the overview picture or?</remark>,
554 accessible through the WAN interface, the WAN IP address can be used from 523 the FortiGate VNF management interface is accessible through the WAN interface. The
555 a web browser on the Lab Machine to access the Fortigate VNF Management 524 WAN IP address can be used from a web browser on the Lab Machine to access the
556 Web UI. Please check the Fortigate VNF web management section for more 525 Fortigate VNF Management Web UI. Please check the Fortigate VNF web management section
557 information.</para> 526 for more information.<remark>Note to self: An olink is needed to this section in this book,
527 use fortigate_webmg as the ID.</remark></para>
558 528
559 <para>In another example, the firewall can be setup to use bridges as 529 <para>In another example, the firewall can be setup to use bridges as
560 connection points for the Fortigate VNF. It is possible to replace 530 connection points for the Fortigate VNF. It is possible to replace these
561 OVS-DPDK bridges with SR-IOV connection points. <remark>The previous 531 OVS-DPDK bridges with SR-IOV connection points. Please check the network
562 sentence in the original was very hard to understand, please confirm if 532 configuration chapter on how to configure an interface for SR-IOV.<remark>An olink
563 this is what you intended to say</remark> Please check the network 533 is needed but I can't add it without clarifying which chapter do you refer to?</remark></para>
564 configuration chapter on how to configure an interface for SR-IOV.</para>
565 534
566 <para>It was previously assumed that three physical interfaces are 535 <para>It was previously assumed that three physical interfaces are
567 available for VNF connection. In the case of a firewall setup it is 536 available for VNF connection. In the case of a firewall setup only two physical interfaces
568 possible to use only two physical interfaces for the data path (one for 537 are needed for the data path (one for WAN and one for LAN).</para><remark>Is this the meaning you
569 WAN and one for LAN). In the example below only two interfaces will be 538 intented to convey in this sentence?</remark>
570 configured as DPDK and two bridges are created, one for each type of 539
571 connection.</para> 540 <para>In the example below only two interfaces will be configured as DPDK, with two
572 541 bridges created, one for each type of connection.</para>
573 <para>At VNF instantiation instead of assigning distinct bridges for each 542
543 <para>Please note that at VNF instantiation instead of assigning distinct bridges for each
574 LAN interface, only one will be used for both LAN1 and LAN2, with no 544 LAN interface, only one will be used for both LAN1 and LAN2, with no
575 changes in WAN interface configuration. Please see the picture below for 545 changes in WAN interface configuration. Please see the picture below for the
576 final setup:</para> 546 final setup:</para>
577 547
578 <figure> 548 <figure>
579 <title>Two Interface Configuration</title> 549 <title>Two-Interface Configuration</title>
580 550
581 <mediaobject> 551 <mediaobject>
582 <imageobject> 552 <imageobject>
583 <imagedata align="center" fileref="images/two_inst_firewall.png" 553 <imagedata align="center" fileref="images/two_inst_firewall.png"
584 scale="45" /> 554 scale="65" />
585 </imageobject> 555 </imageobject>
586 </mediaobject> 556 </mediaobject>
587 </figure> 557 </figure>
588 </section> 558 </section>
589 559
590 <section id="fortigate_webmg"> 560 <section id="fortigate_webmg">
591 <title>FortiGate VNF web management</title> 561 <title>FortiGate VNF Web Management</title>
592 562
593 <para>In order to check the IP address assigned to Fortigate VNF you need 563 <para>In order to check the IP address assigned to the Fortigate VNF you need
594 to connect to the Fortigate CLI.</para> 564 to connect to the Fortigate CLI.</para>
595 565
596 <para><emphasis role="bold">Connecting to the Fortigate 566 <para><emphasis role="bold">Connecting to the Fortigate
@@ -615,15 +585,14 @@
615 </listitem> 585 </listitem>
616 586
617 <listitem> 587 <listitem>
618 <para>To access Fortigate CLI, use the credential 588 <para>To access Fortigate CLI, use <literal>admin</literal> as the user,
619 <literal>admin</literal> for the user, leaving the password blank, 589 leaving the password blank/empty, and press enter.</para>
620 then press enter.</para>
621 590
622 <para>Use the CLI command <literal>get system interface</literal> to 591 <para>Use the CLI command <literal>get system interface</literal> to
623 get the dynamic interfaces configuration.</para> 592 get the dynamic interfaces configuration.</para>
624 593
625 <figure> 594 <figure>
626 <title>Acessing and configuring Fortigate CLI</title> 595 <title>Accessing and configuring Fortigate CLI</title>
627 596
628 <mediaobject> 597 <mediaobject>
629 <imageobject> 598 <imageobject>
@@ -662,14 +631,14 @@
662 <mediaobject> 631 <mediaobject>
663 <imageobject> 632 <imageobject>
664 <imagedata align="center" 633 <imagedata align="center"
665 fileref="images/fortinet_interface.png" scale="30" /> 634 fileref="images/fortinet_interface.png" scale="33" />
666 </imageobject> 635 </imageobject>
667 </mediaobject> 636 </mediaobject>
668 </figure> 637 </figure>
669 </listitem> 638 </listitem>
670 639
671 <listitem> 640 <listitem>
672 <para>Optional, alter the default Fortinet example configuration 641 <para>Optionally, alter the default Fortinet example configuration
673 provided by Enea, through the following steps:</para> 642 provided by Enea, through the following steps:</para>
674 643
675 <orderedlist> 644 <orderedlist>
@@ -679,7 +648,7 @@
679 </listitem> 648 </listitem>
680 649
681 <listitem> 650 <listitem>
682 <para>Connect to the FortiGate VNF Web Management with a web 651 <para>Connect to the FortiGate VNF Web Management interface with a web
683 browser.</para> 652 browser.</para>
684 </listitem> 653 </listitem>
685 654
@@ -689,8 +658,7 @@
689 </listitem> 658 </listitem>
690 659
691 <listitem> 660 <listitem>
692 <para>Store the updated configuration in a file, by saving in the 661 <para>Store the updated configuration in a file, so it may be used at the
693 FortiGate VNF Web Management interface, so it may be used at the
694 next FortiGate VNF instantiation.</para> 662 next FortiGate VNF instantiation.</para>
695 </listitem> 663 </listitem>
696 </orderedlist> 664 </orderedlist>
@@ -706,13 +674,13 @@
706 <section id="fortigate_sdwan_vpn"> 674 <section id="fortigate_sdwan_vpn">
707 <title>FortiGate VNF as an SD-WAN VPN</title> 675 <title>FortiGate VNF as an SD-WAN VPN</title>
708 676
709 <para>The software-defined wide-area network (SD-WAN or SDWAN) is a 677 <para>The Software-Defined Wide-Area Network (SD-WAN or SDWAN) is a
710 specific application of software-defined networking (SDN) technology 678 specific application of software-defined networking (SDN) technology
711 applied to WAN connections. It connects enterprise networks, including 679 applied to WAN connections. It connects enterprise networks, including
712 branch offices and data centers, over large geographic distances.</para> 680 branch offices and data centers, over large geographic distances.</para>
713 681
714 <para>SD-WAN decouples the network from the management plane, detaching 682 <para>SD-WAN decouples the network from the management plane, detaching
715 the traffic management and monitoring functions from hardware. Most forms 683 traffic management and monitoring functions from hardware. Most forms
716 of SD-WAN technology create a virtual overlay that is transport-agnostic, 684 of SD-WAN technology create a virtual overlay that is transport-agnostic,
717 i.e. it abstracts underlying private or public WAN connections. With an 685 i.e. it abstracts underlying private or public WAN connections. With an
718 overlay SD-WAN, a vendor provides an edge device to the customer that 686 overlay SD-WAN, a vendor provides an edge device to the customer that
@@ -730,7 +698,8 @@
730 </note> 698 </note>
731 699
732 <table> 700 <table>
733 <title>FortiGate VNF Example Configuration - SD-WAN Target 1</title> 701 <title>FortiGate VNF Example Configuration - SD-WAN uCPE device
702 1</title>
734 703
735 <tgroup cols="2"> 704 <tgroup cols="2">
736 <colspec align="center" /> 705 <colspec align="center" />
@@ -745,26 +714,26 @@
745 714
746 <tbody> 715 <tbody>
747 <row> 716 <row>
748 <entry>SD-WAN</entry> 717 <entry align="left">SD-WAN</entry>
749 718
750 <entry>VPN connection between two branches (Target 1 and Target 719 <entry>VPN connection between two branches (uCPE device 1 and uCPE
751 2).</entry> 720 device 2).</entry>
752 </row> 721 </row>
753 722
754 <row> 723 <row>
755 <entry>VNFMgr (Virtual Port1)</entry> 724 <entry align="left">VNFMgr (Virtual Port1)</entry>
756 725
757 <entry>DHCP Client, dynamically assigned IP address.</entry> 726 <entry>DHCP Client, dynamically assigned IP address.</entry>
758 </row> 727 </row>
759 728
760 <row> 729 <row>
761 <entry>WAN (Virtual Port2)</entry> 730 <entry align="left">WAN (Virtual Port2)</entry>
762 731
763 <entry>IP address: 10.0.0.1</entry> 732 <entry>IP address: 10.0.0.1</entry>
764 </row> 733 </row>
765 734
766 <row> 735 <row>
767 <entry>LAN (Virtual Port3)</entry> 736 <entry align="left">LAN (Virtual Port3)</entry>
768 737
769 <entrytbl cols="1"> 738 <entrytbl cols="1">
770 <tbody> 739 <tbody>
@@ -784,7 +753,8 @@
784 </table> 753 </table>
785 754
786 <table> 755 <table>
787 <title>FortiGate VNF Example Configuration - SD-WAN Target 2</title> 756 <title>FortiGate VNF Example Configuration - SD-WAN uCPE device
757 2</title>
788 758
789 <tgroup cols="2"> 759 <tgroup cols="2">
790 <colspec align="center" /> 760 <colspec align="center" />
@@ -799,26 +769,26 @@
799 769
800 <tbody> 770 <tbody>
801 <row> 771 <row>
802 <entry>SD-WAN</entry> 772 <entry align="left">SD-WAN</entry>
803 773
804 <entry>VPN connection between two branches (Target 2 and Target 774 <entry>VPN connection between two branches (uCPE device 2 and uCPE
805 1).</entry> 775 device 1).</entry>
806 </row> 776 </row>
807 777
808 <row> 778 <row>
809 <entry>VNFMgr (Virtual Port1)</entry> 779 <entry align="left">VNFMgr (Virtual Port1)</entry>
810 780
811 <entry>DHCP Client, dynamically assigned IP address.</entry> 781 <entry>DHCP Client, dynamically assigned IP address.</entry>
812 </row> 782 </row>
813 783
814 <row> 784 <row>
815 <entry>WAN (Virtual Port2)</entry> 785 <entry align="left">WAN (Virtual Port2)</entry>
816 786
817 <entry>IP address: 10.0.0.2</entry> 787 <entry>IP address: 10.0.0.2</entry>
818 </row> 788 </row>
819 789
820 <row> 790 <row>
821 <entry>LAN (Virtual Port3)</entry> 791 <entry align="left">LAN (Virtual Port3)</entry>
822 792
823 <entrytbl cols="1"> 793 <entrytbl cols="1">
824 <tbody> 794 <tbody>
@@ -858,7 +828,7 @@
858 828
859 <tbody> 829 <tbody>
860 <row> 830 <row>
861 <entry>Lab Network</entry> 831 <entry align="left">Lab Network</entry>
862 832
863 <entrytbl cols="1"> 833 <entrytbl cols="1">
864 <tbody> 834 <tbody>
@@ -874,7 +844,7 @@
874 </row> 844 </row>
875 845
876 <row> 846 <row>
877 <entry>Two Intel Whitebox target devices</entry> 847 <entry align="left">Two Intel Whitebox uCPE devices</entry>
878 848
879 <entrytbl cols="1"> 849 <entrytbl cols="1">
880 <tbody> 850 <tbody>
@@ -913,7 +883,7 @@
913 </row> 883 </row>
914 884
915 <row> 885 <row>
916 <entry>One Lab Machine</entry> 886 <entry align="left">One Lab Machine</entry>
917 887
918 <entrytbl cols="1"> 888 <entrytbl cols="1">
919 <tbody> 889 <tbody>
@@ -933,7 +903,7 @@
933 </row> 903 </row>
934 904
935 <row> 905 <row>
936 <entry>Two Test Machines</entry> 906 <entry align="left">Two Test Machines</entry>
937 907
938 <entrytbl cols="1"> 908 <entrytbl cols="1">
939 <tbody> 909 <tbody>
@@ -953,18 +923,18 @@
953 </row> 923 </row>
954 924
955 <row> 925 <row>
956 <entry>FortiGate VNF</entry> 926 <entry align="left">FortiGate VNF</entry>
957 927
958 <entrytbl cols="1"> 928 <entrytbl cols="1">
959 <tbody> 929 <tbody>
960 <row> 930 <row>
961 <entry>Downloaded the FortiGate VNF Bundle from Enea Portal 931 <entry>FortiGate VNF Bundle downloaded from the Enea Portal
962 to the Lab Machine file system.</entry> 932 to the Lab Machine file system.</entry>
963 </row> 933 </row>
964 934
965 <row> 935 <row>
966 <entry>Downloaded FortiGate configuration examples from Enea 936 <entry>FortiGate configuration examples downloaded from the Enea
967 Portal to Lab Machine file system. Unpack the configuration 937 Portal to the Lab Machine file system. Unpack the configuration
968 examples specific for SD-WAN on the Lab Machine.</entry> 938 examples specific for SD-WAN on the Lab Machine.</entry>
969 </row> 939 </row>
970 940
@@ -990,7 +960,7 @@
990 <mediaobject> 960 <mediaobject>
991 <imageobject> 961 <imageobject>
992 <imagedata align="center" fileref="images/sdwan_vpn_overview_1.png" 962 <imagedata align="center" fileref="images/sdwan_vpn_overview_1.png"
993 scale="50" /> 963 scale="55" />
994 </imageobject> 964 </imageobject>
995 </mediaobject> 965 </mediaobject>
996 </figure> 966 </figure>
@@ -1002,7 +972,7 @@
1002 972
1003 <para>Since the SD-WAN VNF uses three External Network Interfaces, three 973 <para>Since the SD-WAN VNF uses three External Network Interfaces, three
1004 bridges need to be configured. Each bridge provides the ability to connect 974 bridges need to be configured. Each bridge provides the ability to connect
1005 a physical network interface to the virtual machine's virtual network 975 a physical network interface to the VM's virtual network
1006 interface. Each physical to virtual network interface connection is setup 976 interface. Each physical to virtual network interface connection is setup
1007 in two steps:</para> 977 in two steps:</para>
1008 978
@@ -1023,7 +993,7 @@
1023 993
1024 <orderedlist> 994 <orderedlist>
1025 <listitem> 995 <listitem>
1026 <para>Bind physical interface to DPDK by selecting the target_1: 996 <para>Bind a physical interface to the DPDK by selecting uCPE device 1 first, then:
1027 <literal>Configuration</literal> -&gt; <literal>OpenVSwitch</literal> 997 <literal>Configuration</literal> -&gt; <literal>OpenVSwitch</literal>
1028 -&gt; <literal>Host Interfaces</literal> -&gt; 998 -&gt; <literal>Host Interfaces</literal> -&gt;
1029 <literal>Add</literal>:</para> 999 <literal>Add</literal>:</para>
@@ -1039,8 +1009,8 @@
1039 </mediaobject> 1009 </mediaobject>
1040 </figure> 1010 </figure>
1041 1011
1042 <para>The result of binding these three interfaces should look like 1012 <para>Repeat this step for the other two interfaces. The result of a successful binding
1043 the following:</para> 1013 should look like the following:</para>
1044 1014
1045 <figure> 1015 <figure>
1046 <title>Results of Binding</title> 1016 <title>Results of Binding</title>
@@ -1055,15 +1025,13 @@
1055 </listitem> 1025 </listitem>
1056 1026
1057 <listitem> 1027 <listitem>
1058 <para>Create one OpenVSwitch bridge for each SD-WAN network connection 1028 <para>Create an Open vSwitch bridge for each SD-WAN network connection
1059 (VNF management, WAN and LAN) by selecting the <literal>Add</literal> 1029 (VNF management, WAN and LAN) by selecting the uCPE device then:
1060 button from the Bridges tab by selecting the target: 1030 <literal>Configuration</literal> -&gt; <literal>OpenvSwitch</literal> -&gt;
1061 <literal>Configuration</literal> -&gt; 1031 <literal>Bridges</literal> -&gt; <literal>Add</literal>. A popup will appear:</para>
1062 <literal>OpenvSwitch</literal>-&gt; <literal>Bridges</literal>. A
1063 popup like this should appear:</para>
1064 1032
1065 <figure> 1033 <figure>
1066 <title>Creating an OpenVSwitch bridge for an SD-WAN network 1034 <title>Creating an Open vSwitch bridge for an SD-WAN network
1067 connection</title> 1035 connection</title>
1068 1036
1069 <mediaobject> 1037 <mediaobject>
@@ -1080,7 +1048,7 @@
1080 be created:</para> 1048 be created:</para>
1081 1049
1082 <figure> 1050 <figure>
1083 <title>The three newly created Bridges</title> 1051 <title>OVS Bridges</title>
1084 1052
1085 <mediaobject> 1053 <mediaobject>
1086 <imageobject> 1054 <imageobject>
@@ -1092,22 +1060,21 @@
1092 </listitem> 1060 </listitem>
1093 </orderedlist> 1061 </orderedlist>
1094 1062
1095 <para>Once the interfaces and bridges are ready, only the on-boarding and 1063 <para>Once the interfaces and bridges are ready, onboard and instantiate the VNF.</para>
1096 instantiation of the VNF remains to be done.</para>
1097 1064
1098 <para><emphasis role="bold">Onboarding the FortiGate VNF</emphasis></para> 1065 <para><emphasis role="bold">Onboarding the FortiGate VNF</emphasis></para>
1099 1066
1100 <orderedlist> 1067 <orderedlist>
1101 <listitem> 1068 <listitem>
1102 <para>To on-board a VNF, select target on the map and click the 1069 <para>To onboard a VNF, select a uCPE device on the map and click the
1103 <literal>VNF</literal> button in the top toolbar. Then, click the 1070 <literal>VNF</literal> button in the top toolbar. Then, click the
1104 <literal>Descriptors</literal> -&gt; <literal>On-board</literal> -&gt; 1071 <literal>Descriptors</literal> -&gt; <literal>On-board</literal> -&gt;
1105 <literal>Browse</literal> options, and select the 1072 <literal>Browse</literal> options, and select the
1106 <filename>Fortigate.zip</filename> file, before clicking 1073 <filename>Fortigate.zip</filename> file, before pressing
1107 <literal>Send</literal>:</para> 1074 <literal>Send</literal>:</para>
1108 1075
1109 <figure> 1076 <figure>
1110 <title>On-boarding FortiGate VNF</title> 1077 <title>Onboarding FortiGate VNF</title>
1111 1078
1112 <mediaobject> 1079 <mediaobject>
1113 <imageobject> 1080 <imageobject>
@@ -1139,15 +1106,15 @@
1139 1106
1140 <para><emphasis role="bold">Instantiating the FortiGate 1107 <para><emphasis role="bold">Instantiating the FortiGate
1141 VNF</emphasis></para> 1108 VNF</emphasis></para>
1142 1109
1143 <para>The following steps describe how to instantiate the Fortigate 1110 <note><para>Download locally the valid license files for the Fortigate VNF from
1144 VNF.</para> 1111 Fortinet and the configuration file provided by Enea as examples.</para>
1112 </note>
1145 1113
1146 <orderedlist> 1114 <orderedlist>
1147 <listitem> 1115 <listitem>
1148 <para>Select the target, then from the top toolbar click on 1116 <para>Select a uCPE device on the map, then from the top toolbar click
1149 <literal>VNF</literal>-&gt; <literal>Instances</literal> -&gt; 1117 <literal>VNF</literal> -&gt; <literal>Instances</literal> -&gt; <literal>Add</literal>:</para>
1150 <literal>Add</literal> options:</para>
1151 1118
1152 <figure> 1119 <figure>
1153 <title>Adding an Instance</title> 1120 <title>Adding an Instance</title>
@@ -1155,24 +1122,18 @@
1155 <mediaobject> 1122 <mediaobject>
1156 <imageobject> 1123 <imageobject>
1157 <imagedata align="center" fileref="images/adding_instance.png" 1124 <imagedata align="center" fileref="images/adding_instance.png"
1158 scale="50" /> 1125 scale="52" />
1159 </imageobject> 1126 </imageobject>
1160 </mediaobject> 1127 </mediaobject>
1161 </figure> 1128 </figure>
1162
1163 <note>
1164 <para>Download locally the valid license files for the Fortigate VNF
1165 from Fortinet and the configuration file provided by Enea as
1166 examples.</para>
1167 </note>
1168 </listitem> 1129 </listitem>
1169 1130
1170 <listitem> 1131 <listitem>
1171 <para>Use the <literal>sdwan1</literal> example configuration file for 1132 <para>Use the <literal>sdwan1</literal> example configuration file for
1172 the first target:</para> 1133 uCPE device 1:</para>
1173 1134
1174 <figure> 1135 <figure>
1175 <title>Configuring target_1</title> 1136 <title>Configuring uCPE device 1</title>
1176 1137
1177 <mediaobject> 1138 <mediaobject>
1178 <imageobject> 1139 <imageobject>
@@ -1184,10 +1145,10 @@
1184 </listitem> 1145 </listitem>
1185 </orderedlist> 1146 </orderedlist>
1186 1147
1187 <para>Fortigate VNF instantiation requires the following settings:</para> 1148 <para>FortiGate VNF instantiation requires the following settings:</para>
1188 1149
1189 <table> 1150 <table>
1190 <title>Fortigate VNF Instantiation Requirements</title> 1151 <title>FortiGate VNF Instantiation Requirements</title>
1191 1152
1192 <tgroup cols="2"> 1153 <tgroup cols="2">
1193 <colspec align="left" colwidth="2*" /> 1154 <colspec align="left" colwidth="2*" />
@@ -1206,72 +1167,71 @@
1206 <row> 1167 <row>
1207 <entry>Name</entry> 1168 <entry>Name</entry>
1208 1169
1209 <entry>The name of the VM which will be created on target 1170 <entry>The name of the VM which will be created on the uCPE device.</entry>
1210 device.</entry>
1211 </row> 1171 </row>
1212 1172
1213 <row> 1173 <row>
1214 <entry>VNF Type</entry> 1174 <entry>VNF Type</entry>
1215 1175
1216 <entry>The name of the on-boarded VNF bundle.</entry> 1176 <entry>The name of the onboarded VNF bundle.</entry>
1217 </row> 1177 </row>
1218 1178
1219 <row> 1179 <row>
1220 <entry>VIM</entry> 1180 <entry>VIM</entry>
1221 1181
1222 <entry>Name and IP address of the device where the VNF has to be 1182 <entry>Name and IP address of the device where the VNF will be
1223 instantiated.</entry> 1183 instantiated.</entry>
1224 </row> 1184 </row>
1225 1185
1226 <row> 1186 <row>
1227 <entry>License file</entry> 1187 <entry>License file</entry>
1228 1188
1229 <entry>FortiGate license file provided by Fortinet.</entry> 1189 <entry>The FortiGate license file provided by Fortinet.</entry>
1230 </row> 1190 </row>
1231 1191
1232 <row> 1192 <row>
1233 <entry>Configuration file</entry> 1193 <entry>Configuration file(s)</entry>
1234 1194
1235 <entry>SD-WAN example configuration files provided by Enea: - 1195 <entry>SD-WAN example configuration files provided by Enea:
1236 FGVM080000136187_20180215_0708_sdwan1.conf - 1196 <literal>FGVM080000136187_20180215_0708_sdwan1.conf</literal>
1237 FGVM080000136188_20180215_0708_sdwan2.conf</entry> 1197 <literal>FGVM080000136188_20180215_0708_sdwan2.conf</literal></entry>
1238 </row> 1198 </row>
1239 1199
1240 <row> 1200 <row>
1241 <entry>Port1 - VNFMgr</entry> 1201 <entry>Port1 - VNFMgr</entry>
1242 1202
1243 <entry>Set as dpdk type and connect it to vnfmgrbr bridge.</entry> 1203 <entry>Set as Dpdk type and connect it to the <literal>vnfmgrbr</literal> bridge.</entry>
1244 </row> 1204 </row>
1245 1205
1246 <row> 1206 <row>
1247 <entry>Port2 - WAN</entry> 1207 <entry>Port2 - WAN</entry>
1248 1208
1249 <entry>Set as dpdk type and connect it to wanbr bridge.</entry> 1209 <entry>Set as Dpdk type and connect it to the <literal>wanbr</literal> bridge.</entry>
1250 </row> 1210 </row>
1251 1211
1252 <row> 1212 <row>
1253 <entry>Port3 - LAN</entry> 1213 <entry>Port3 - LAN</entry>
1254 1214
1255 <entry>Set as dpdk type and connect it to lanbr bridge.</entry> 1215 <entry>Set as Dpdk type and connect it to the <literal>lanbr</literal> bridge.</entry>
1256 </row> 1216 </row>
1257 </tbody> 1217 </tbody>
1258 </tgroup> 1218 </tgroup>
1259 </table> 1219 </table>
1260 1220
1261 <para>To complete the branch-to-branch setup, configure the peer target in 1221 <para>To complete the branch-to-branch setup, configure the peer uCPE
1262 the same way as <literal>target_1</literal>. Make sure to use the 1222 device in the same way as <literal>uCPE device 1</literal>. Make sure to
1263 <filename>FGVM080000136188_20180215_0708_sdwan2.conf</filename> 1223 use the <filename>FGVM080000136188_20180215_0708_sdwan2.conf</filename>
1264 configuration file for the second VNF instantiation.</para> 1224 configuration file for the second VNF instantiation.</para>
1265 1225
1266 <para><emphasis role="bold">Testing the FortiGate SD-WAN 1226 <para><emphasis role="bold">Testing the FortiGate SD-WAN
1267 VPN</emphasis></para> 1227 VPN</emphasis></para>
1268 1228
1269 <para>Once the full SD-WAN setup is in place a VPN connection needs to 1229 <para>Once the full SD-WAN setup is in place a VPN connection needs to be
1270 established between the two targets. The Test Machines can be connected to 1230 established between the two uCPE devices. The Test Machines can be
1271 the LAN interface on each target.</para> 1231 connected to the LAN interface on each uCPE device.</para>
1272 1232
1273 <para>The connected Test Machine can be a laptop or a target that has one 1233 <para>The connected Test Machine can be a laptop or a uCPE device that has
1274 interface configured to get dynamic IP from a DHCP server. The 1234 one interface configured to get a dynamic IP from a DHCP server. The
1275 <command>dhclient &lt;interface&gt;</command> command can be used to 1235 <command>dhclient &lt;interface&gt;</command> command can be used to
1276 request an IP address.</para> 1236 request an IP address.</para>
1277 1237
@@ -1287,13 +1247,13 @@
1287 <mediaobject> 1247 <mediaobject>
1288 <imageobject> 1248 <imageobject>
1289 <imagedata align="center" fileref="images/test_machines.png" 1249 <imagedata align="center" fileref="images/test_machines.png"
1290 scale="40" /> 1250 scale="45" />
1291 </imageobject> 1251 </imageobject>
1292 </mediaobject> 1252 </mediaobject>
1293 </figure> 1253 </figure>
1294 1254
1295 <para>Target 1 should be able to ping Test target 2 in this setup over the 1255 <para>uCPE device 1 should be able to ping Test uCPE device 2 in this
1296 WAN connection.</para> 1256 setup over the WAN connection.</para>
1297 1257
1298 <para>In the figure above and this example, the FortiGate VNF management 1258 <para>In the figure above and this example, the FortiGate VNF management
1299 interface is accessible through a dedicated Mgmt interface. The Mgmt IP 1259 interface is accessible through a dedicated Mgmt interface. The Mgmt IP
@@ -1302,8 +1262,8 @@
1302 1262
1303 <note> 1263 <note>
1304 <para>In this SD-WAN VPN setup example, bridges were used as connection 1264 <para>In this SD-WAN VPN setup example, bridges were used as connection
1305 points for Fortigate VNF. It is possible to replace OVS-DPDK bridges 1265 points for the Fortigate VNF. It is possible to replace OVS-DPDK bridges
1306 with SR-IOV connection points.</para> 1266 with SR-IOV connection points.</para>
1307 </note> 1267 </note>
1308 </section> 1268 </section>
1309</chapter> \ No newline at end of file 1269</chapter>
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/clav_VNF_demo_SR-IOV.png b/doc/book-enea-nfv-access-example-usecases/doc/images/clav_VNF_demo_SR-IOV.png
index cdfb4d3..03a618f 100755
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/clav_VNF_demo_SR-IOV.png
+++ b/doc/book-enea-nfv-access-example-usecases/doc/images/clav_VNF_demo_SR-IOV.png
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/descriptor_button.png b/doc/book-enea-nfv-access-example-usecases/doc/images/descriptor_button.png
deleted file mode 100755
index 72b59bc..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/descriptor_button.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/enea_vnf_demo_overview.png b/doc/book-enea-nfv-access-example-usecases/doc/images/enea_vnf_demo_overview.png
index a3a8a85..48b3a94 100755
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/enea_vnf_demo_overview.png
+++ b/doc/book-enea-nfv-access-example-usecases/doc/images/enea_vnf_demo_overview.png
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/host_interface_creation.png b/doc/book-enea-nfv-access-example-usecases/doc/images/host_interface_creation.png
deleted file mode 100755
index 6fabb9b..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/host_interface_creation.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_client_inttype.png b/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_client_inttype.png
deleted file mode 100755
index 486f9d9..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_client_inttype.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_server_inttype.png b/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_server_inttype.png
deleted file mode 100755
index 000e250..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/iperf_server_inttype.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/onboarding_status.png b/doc/book-enea-nfv-access-example-usecases/doc/images/onboarding_status.png
deleted file mode 100755
index 8adb954..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/onboarding_status.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_tab.png b/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_tab.png
deleted file mode 100755
index 9d096c9..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_tab.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_two.png b/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_two.png
deleted file mode 100755
index 3f4c427..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_two.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_zero.png b/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_zero.png
deleted file mode 100755
index 3f4c427..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_bridge_zero.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_host_interface.png b/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_host_interface.png
deleted file mode 100755
index 3ccdd66..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/ovs_host_interface.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/secondtar_hostinterface.png b/doc/book-enea-nfv-access-example-usecases/doc/images/secondtar_hostinterface.png
deleted file mode 100755
index 6fabb9b..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/secondtar_hostinterface.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/testPMD_VNF_PCI.png b/doc/book-enea-nfv-access-example-usecases/doc/images/testPMD_VNF_PCI.png
index 03f298f..5aeebbf 100755
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/testPMD_VNF_PCI.png
+++ b/doc/book-enea-nfv-access-example-usecases/doc/images/testPMD_VNF_PCI.png
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_forward.png b/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_forward.png
deleted file mode 100755
index 9c2ca82..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_forward.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_terminate.png b/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_terminate.png
deleted file mode 100755
index 9decd36..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/traffic_terminate.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_dpdk_int_bind.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_dpdk_int_bind.png
deleted file mode 100755
index ea1fef7..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_dpdk_int_bind.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_fortigate_onboard.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_fortigate_onboard.png
deleted file mode 100755
index 6fa40bd..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_ibm_fortigate_onboard.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instance.png b/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instance.png
deleted file mode 100755
index ecfee74..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instance.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instances.png b/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instances.png
deleted file mode 100755
index e07bd9e..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/vnf_instances.png
+++ /dev/null
Binary files differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml b/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml
index f28fc4e..3aea4f5 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/inband_management.xml
@@ -14,12 +14,12 @@
14 <mediaobject> 14 <mediaobject>
15 <imageobject> 15 <imageobject>
16 <imagedata align="center" fileref="images/uc_ibm_solution.png" 16 <imagedata align="center" fileref="images/uc_ibm_solution.png"
17 scale="50" /> 17 scale="55" />
18 </imageobject> 18 </imageobject>
19 </mediaobject> 19 </mediaobject>
20 </figure> 20 </figure>
21 21
22 <para>Setup uses the following network configuration:</para> 22 <para>This Setup uses the following network configuration:</para>
23 23
24 <itemizedlist> 24 <itemizedlist>
25 <listitem> 25 <listitem>
@@ -31,8 +31,8 @@
31 </listitem> 31 </listitem>
32 </itemizedlist> 32 </itemizedlist>
33 33
34 <para>For prerequisites and further details, please see <xref 34 <para>For prerequisites and further details, please see <xref linkend="inband_management" />
35 linkend="inband_management" /> and <xref linkend="vnf_fortigate" />.</para> 35 and <xref linkend="vnf_fortigate" /><remark>Are these references still valid?</remark>.</para>
36 36
37 <section id="mg_activation"> 37 <section id="mg_activation">
38 <title>In-band management activation for FortiGate VNF 38 <title>In-band management activation for FortiGate VNF
@@ -110,17 +110,6 @@
110 <literal>ovs-bridge-type</literal>.</para> 110 <literal>ovs-bridge-type</literal>.</para>
111 </listitem> 111 </listitem>
112 </itemizedlist> 112 </itemizedlist>
113
114 <figure>
115 <title>Bind LAN physical port to dpdk</title>
116
117 <mediaobject>
118 <imageobject>
119 <imagedata align="center"
120 fileref="images/uc_ibm_dpdk_int_bind.png" scale="75" />
121 </imageobject>
122 </mediaobject>
123 </figure>
124 </listitem> 113 </listitem>
125 114
126 <listitem> 115 <listitem>
@@ -128,17 +117,17 @@
128 117
129 <itemizedlist> 118 <itemizedlist>
130 <listitem> 119 <listitem>
131 <para>Select the <literal>Device.</literal></para> 120 <para>Select the <literal>Device</literal>.</para>
132 </listitem> 121 </listitem>
133 122
134 <listitem> 123 <listitem>
135 <para>In the Configuration menu select 124 <para>In the Configuration menu select
136 <literal>OpenVSwitch.</literal></para> 125 <literal>OpenVSwitch</literal>.</para>
137 </listitem> 126 </listitem>
138 127
139 <listitem> 128 <listitem>
140 <para>Open the <literal>Bridges</literal> menu and click 129 <para>Open the <literal>Bridges</literal> menu and click
141 <literal>Add.</literal></para> 130 <literal>Add</literal>.</para>
142 </listitem> 131 </listitem>
143 </itemizedlist> 132 </itemizedlist>
144 133
@@ -168,7 +157,7 @@
168 157
169 <note> 158 <note>
170 <para>The WAN port of the very first VNF instantiated on the device 159 <para>The WAN port of the very first VNF instantiated on the device
171 must be connected to the <literal>ibm-wan-br bridge</literal>. All 160 must be connected to the <literal>ibm-wan-br</literal>bridge. All
172 other VNFs must be connected in chain with the first VNF.</para> 161 other VNFs must be connected in chain with the first VNF.</para>
173 </note> 162 </note>
174 </listitem> 163 </listitem>
@@ -178,7 +167,7 @@
178 167
179 <itemizedlist> 168 <itemizedlist>
180 <listitem> 169 <listitem>
181 <para>Select the <literal>Device.</literal></para> 170 <para>Select the <literal>Device</literal>.</para>
182 </listitem> 171 </listitem>
183 172
184 <listitem> 173 <listitem>
@@ -195,18 +184,6 @@
195 pressing the <literal>Send</literal> button.</para> 184 pressing the <literal>Send</literal> button.</para>
196 </listitem> 185 </listitem>
197 </itemizedlist> 186 </itemizedlist>
198
199 <figure>
200 <title>Onboard Fortigate VNF</title>
201
202 <mediaobject>
203 <imageobject>
204 <imagedata align="center"
205 fileref="images/uc_ibm_fortigate_onboard.png"
206 scale="50" />
207 </imageobject>
208 </mediaobject>
209 </figure>
210 </listitem> 187 </listitem>
211 188
212 <listitem> 189 <listitem>
@@ -214,7 +191,7 @@
214 191
215 <itemizedlist> 192 <itemizedlist>
216 <listitem> 193 <listitem>
217 <para>Select the <literal>Device.</literal></para> 194 <para>Select the <literal>Device</literal>.</para>
218 </listitem> 195 </listitem>
219 196
220 <listitem> 197 <listitem>
@@ -224,7 +201,7 @@
224 <listitem> 201 <listitem>
225 <para>Choose the <literal>Instances</literal> option, select the 202 <para>Choose the <literal>Instances</literal> option, select the
226 VNF configuration you desire and press 203 VNF configuration you desire and press
227 <literal>Add.</literal></para> 204 <literal>Add</literal>.</para>
228 </listitem> 205 </listitem>
229 206
230 <listitem> 207 <listitem>
@@ -234,7 +211,7 @@
234 </itemizedlist> 211 </itemizedlist>
235 212
236 <figure> 213 <figure>
237 <title>Instantiate Fortigate VNF</title> 214 <title>Instantiate the FortiGate VNF</title>
238 215
239 <mediaobject> 216 <mediaobject>
240 <imageobject> 217 <imageobject>
@@ -249,7 +226,7 @@
249 226
250 <para>Once the VNF is instantiated, the setup is complete and ready for 227 <para>Once the VNF is instantiated, the setup is complete and ready for
251 testing. Connect the test machine to the LAN port. It will receive an IP 228 testing. Connect the test machine to the LAN port. It will receive an IP
252 address from the Fortigate VNF and be able to access the internet.</para> 229 address from the FortiGate VNF and be able to access the internet.</para>
253 </section> 230 </section>
254 231
255 <section id="test_fortvnf_inband"> 232 <section id="test_fortvnf_inband">
@@ -261,7 +238,7 @@
261 <mediaobject> 238 <mediaobject>
262 <imageobject> 239 <imageobject>
263 <imagedata align="center" fileref="images/uc_ibm_solution_test.png" 240 <imagedata align="center" fileref="images/uc_ibm_solution_test.png"
264 scale="50" /> 241 scale="52" />
265 </imageobject> 242 </imageobject>
266 </mediaobject> 243 </mediaobject>
267 </figure> 244 </figure>
@@ -271,11 +248,11 @@
271 248
272 <itemizedlist> 249 <itemizedlist>
273 <listitem> 250 <listitem>
274 <para>Device management traffic from uCPE Manager.</para> 251 <para>Device management traffic from the uCPE Manager.</para>
275 </listitem> 252 </listitem>
276 253
277 <listitem> 254 <listitem>
278 <para>Fortigate management interface traffic from a web 255 <para>FortiGate management interface traffic from a web
279 browser.</para> 256 browser.</para>
280 </listitem> 257 </listitem>
281 258
@@ -284,13 +261,13 @@
284 </listitem> 261 </listitem>
285 </itemizedlist> 262 </itemizedlist>
286 263
287 <para>Having access from the uCPE Manager to the device as shown above, 264 <para>If you have access from the uCPE Manager to the device as shown above, this
288 demonstrates that device management traffic passes through the in-band 265 demonstrates that device management traffic passes through the In-band
289 management WAN bridge successfully.</para> 266 management WAN bridge successfully.</para>
290 267
291 <para>To access the management interface of the VNF, connect from a web 268 <para>To access the management interface of the VNF, connect from a web
292 browser to the public IP address of the device e.g. 269 browser to the public IP address of the device e.g.
293 <literal>https://&lt;IP&gt;</literal>. From a Test machine connected on 270 <literal>https://&lt;IP&gt;</literal>. From a Test machine connected on
294 LAN port, try a test ping to the internet e.g. "ping 8.8.8.8".</para> 271 the LAN port, try a test ping to the internet e.g. "ping 8.8.8.8".</para>
295 </section> 272 </section>
296</chapter> \ No newline at end of file 273</chapter>
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
new file mode 100644
index 0000000..208cd0e
--- /dev/null
+++ b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
@@ -0,0 +1,18 @@
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<chapter id="intro">
3 <title>Introduction</title>
4
5 <para>This document describes several example use-cases concerning uCPE device
6 network interface configuration, onboarding and instantiation of certain VNFs,
7 VNF chaining, and In-band management.</para>
8
9 <note><para>Before running any example make sure the uCPE device(s) have been
10 added to the uCPE Manager and placed on the map.</para>
11 </note>
12
13 <para>For detailed information on how to add a device to the uCPE Manager, how
14 to configure the network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers,
15 or VNF configuration, please refer to the <xi:include href="../../s_docbuild/olinkdb/pardoc-common.xml"
16 xmlns:xi="http://www.w3.org/2001/XInclude"
17 xpointer="element(book_enea_nfv_access_getting_started/1)" /> Manual.</para>
18</chapter>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-10-26 19:55:13 +0000