Final edits 2.2.3 part 3.

Change-Id: I28eefc6092ebba6d77700a05ecbd12f0bcc00ae6
Signed-off-by: mrpa <miruna.paun@enea.com>

6 files changed, 32 insertions, 52 deletions

diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
index d58f101..7ba8a7b 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
@@ -39,27 +39,13 @@
       </listitem>
 
       <listitem>
-        <para>cloud-init iso image. Please check <olink
-        targetdoc="book_enea_nfv_access_example_usecases"
-        targetptr="appendix_one_cust">Appendix A: How to create a 128T
-        cloud-init iso image (day-0 configuration) in the <xi:include
-        href="../../s_docbuild/olinkdb/pardoc-names.xml"
-        xmlns:xi="http://www.w3.org/2001/XInclude"
-        xpointer="element(book_enea_nfv_access_example_usecases/1)" /></olink>
-        Manual for more details.</para>
+        <para>cloud-init iso image.</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <para>For data path validation, it may be required to generate a new
-      cloud-init image to match your network configuration. Please check
-      <olink targetdoc="book_enea_nfv_access_example_usecases"
-      targetptr="appendix_one_cust">Appendix A: How to create 128T cloud-init
-      iso image (day-0 configuration) in the <xi:include
-      href="../../s_docbuild/olinkdb/pardoc-names.xml"
-      xmlns:xi="http://www.w3.org/2001/XInclude"
-      xpointer="element(book_enea_nfv_access_example_usecases/1)" /></olink>
-      Manual for more details.</para>
+      cloud-init image to match your network configuration.</para>
     </note>
   </section>
 
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
index 2097435..ea99e4f 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
@@ -42,16 +42,16 @@
 
   <para>The FortiGate and 128T VNF images need to be copied into the
   <literal>vnf_image</literal> directory. The names should be the same as
-  those described in Appendix D.</para>
+  those described in the previous appendix.</para>
 
   <para>The FortiGate valid license file needs to be copied into the
   <literal>vnf_config/fortigate/</literal> directory. The name should be the
-  same as that described in Appendix D.</para>
+  same as that described in the previous appendix.</para>
 
   <para>The cloud init files that match the network, need to be copied into
   the <literal>vnf_config/fortigate/</literal> and the
   <literal>vnf_config/128t/</literal> directories respectively. The names
-  should be the same as those described in Appendix D.</para>
+  should be the same as those described in the previous appendix.</para>
 
   <section id="ap_d_uc1">
     <title>Use-case 1: 128T VNF Router Example Use-case</title>
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 05fd522..eb8b0c8 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
@@ -36,15 +36,6 @@
   <xi:include href="service_chaining_128t_fortigate.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
 
-  <xi:include href="appendix_1.xml"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-  <xi:include href="appendix_2.xml"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-  <xi:include href="appendix_3.xml"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
-
   <xi:include href="appendix_4.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
 
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
index 456ab50..fc3559b 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
@@ -6,20 +6,22 @@
   configuration, onboarding and instantiation of certain VNFs, VNF chaining,
   etc.</para>
 
+  <para>Before running any example use case make sure the uCPE device(s) have
+  been added to the uCPE Manager and placed on the map. For detailed
+  information on how to add a device to the uCPE Manager, how to configure the
+  network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF
+  configuration, please refer to the <xi:include
+  href="../../s_docbuild/olinkdb/pardoc-common.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(book_enea_nfv_access_getting_started/1)" /> Manual.</para>
+
   <note>
-    <para>Before running any example use case make sure the uCPE device(s) have been
-    added to the uCPE Manager and placed on the map.</para>
+    <para>Examples presented in this document use 3rd-party VNFs, which are
+    not provided by Enea. To procure and use these VNF image files and license
+    files, please contact the VNF provider. </para>
 
-    <para>For detailed information on how to add a device to the uCPE Manager,
-    how to configure the network interfaces to use DPDK, PCI-passthrough or
-    SR-IOV drivers, or VNF configuration, please refer to the <xi:include
-    href="../../s_docbuild/olinkdb/pardoc-common.xml"
-    xmlns:xi="http://www.w3.org/2001/XInclude"
-    xpointer="element(book_enea_nfv_access_getting_started/1)" />
-    Manual.</para>
+    <para>Request the VNF prerequisites from the VNF vendors, or alternatively
+    obtain the prerequisites based on instructions from each VNF vendor
+    respectively.</para>
   </note>
-  
-  <para>Examples presented in this document use 3rd-party VNFs, which
-  are not provided by Enea. To procure and use these VNF image files and license files,
-  where applicable, please contact the VNF provider.</para>
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
index 43c3fce..1f3a6ce 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
@@ -57,14 +57,7 @@
       </listitem>
 
       <listitem>
-        <para>Cloud-init iso image. Please check <olink
-        targetdoc="book_enea_nfv_access_example_usecases"
-        targetptr="appendix_one_cust">Appendix A: How to create a 128T
-        cloud-init iso image (day-0 configuration) in the <xi:include
-        href="../../s_docbuild/olinkdb/pardoc-names.xml"
-        xmlns:xi="http://www.w3.org/2001/XInclude"
-        xpointer="element(book_enea_nfv_access_example_usecases/1)" /></olink>
-        Manual for more details.</para>
+        <para>Cloud-init iso image.</para>
       </listitem>
     </itemizedlist>
 
@@ -1035,8 +1028,7 @@
       interface is configured with a DHCP server):<programlisting>&gt; dhclient eth1
 &gt; ping 8.8.8.8</programlisting>For data path validation, a new cloud-init
       image may need to be generated for the 128T VNF to match your network
-      configuration. Please check Appendix A "How to create 128T cloud-init
-      iso image (day-0 configuration)" for details.</para>
+      configuration.</para>
     </section>
 
     <section>
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index cdea2be..0980783 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -129,6 +129,15 @@
       <literal>igb_uio</literal>. However, the limitation stated above still
       applies so all the interfaces must be assigned to
       <literal>vfio-pci</literal>.</para>
+
+      <para>When an in-band management bridge is configured with DPDK enabled,
+      the <literal>igb_uio</literal> driver is used. If the in-band management
+      interface is assigned to a VM, and there are other interfaces assigned
+      to the VM that use the <literal>vfio-pci</literal> driver (this includes
+      SR-IOV interfaces and PCI passthrough interfaces), then the VM must be
+      stopped before restarting the vCPE service on the device
+      (<command>systemctl restart vcpe</command>). Rebooting the device does
+      not have this restriction.</para>
     </listitem>
 
     <listitem>