Rel-Info: update known issues

Fixed incorrect info in VNF chaining section in the example-usecases doc

Change-Id: I632d2ce23ddd951729367de68ea651a8db5a26d9
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

2 files changed, 29 insertions, 9 deletions

diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
index 3de347d..412af4a 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
@@ -270,7 +270,7 @@
         </itemizedlist>
 
         <note>
-          <para>the login/password values for the Juniper VNF are
+          <para>The login/password values for the Fortigate VNF are
           <literal>admin/&lt;empty password&gt;</literal>,
           respectively.</para>
         </note>
@@ -292,8 +292,10 @@
     <para>Before testing LAN to LAN connectivity, preliminary tests of service
     can be run to ensure everything was set up properly.</para>
 
-    <para>For instance, by connecting to the vSRX CLI (any site), the user can
-    test IKE security associations:</para>
+    <para>Before testing LAN to LAN connectivity, one can run preliminary tests of service to ensure everything was
+set-up properly. For instance, by connecting to vSRX CLI (any site), one can test IKE security associations:</para>
+
+    <programlisting>root@Atom-C3000:~ # cli</programlisting>
 
     <programlisting>root@Atom-C3000&gt; show security ike security-associations
 Index   State  Initiator cookie  Responder cookie  Mode           Remote Address
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 8c3a554..b066821 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
@@ -17,8 +17,8 @@
 
     <listitem>
       <para><remark>LXCR-9056</remark>Instantiating a VNF with a different
-      number of interfaces than was specified during VNF onboarding causes
-      an exception.</para>
+      number of interfaces than was specified during VNF onboarding causes an
+      exception.</para>
     </listitem>
 
     <listitem>
@@ -28,14 +28,32 @@
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-99</remark>The uCPE Manager fails to onboard renamed VNF
-      bundles downloaded to the same repo.</para>
+      <para><remark>ELCCR-99</remark>The uCPE Manager fails to onboard renamed
+      VNF bundles downloaded to the same repo.</para>
     </listitem>
 
     <listitem>
       <para><remark>ELCCR-102</remark>Sometimes, during VNF instantiation,
-      even if the needed configuration file has been selected/uploaded, the uCPE
-      Manager UI is not updated with the appropriate file name.</para>
+      even if the needed configuration file has been selected/uploaded, the
+      uCPE Manager UI is not updated with the appropriate file name.</para>
+    </listitem>
+
+    <listitem>
+      <para>No disk space check is performed when instantiating (i.e. downloading) a VNF to the CPE device. If there is not enough disk space available, then a crash will occur.</para>
+    </listitem>
+
+    <listitem>
+      <para>The Enea uCPE Manager will not detect that a VNF is no longer
+      running if the CPE device is reinstalled with the Enea NFV Access
+      Run-Time platform and rebooted after the VNF has been instantiated.</para>
+    </listitem>
+
+    <listitem>
+      <para>If different interfaces are configured during Instantiation than were set up during Onboarding, an error occurs..</para>
+    </listitem>
+
+    <listitem>
+      <para>No support is provided for multiple CPE devices behind a firewall or gateway connecting callhome to a uCPE Manager (running outside the local network).</para>
     </listitem>
   </itemizedlist>