Updating the DPDK version,

Rearranging and updating the known issues chapter.

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

2 files changed, 134 insertions, 132 deletions

diff --git a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
index a7e55e7..53d3849 100644
--- a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
@@ -4,38 +4,50 @@
 <chapter id="bugs-limitations">
   <title>Known Issues and Limitations in this Release</title>
 
-  <para>This chapter lists the known general issues and limitations that
-  affect the current release.</para>
+  <para><emphasis role="bold">Issues and limitations found in the Enea Edge
+  <xi:include href="../../eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaEdge_REL_VER/1)" /> release:</emphasis></para>
 
   <itemizedlist>
     <listitem>
-      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
-      USB storage devices.</para>
+      <para><remark>ELCCR-1688, ELCCR-1809</remark>It is possible to end up
+      with a corrupted VM image from the download operation. If that happens,
+      the VNF instantiation will fail. The corrupted image has to be manually
+      removed from <literal>/var/odm/vm_images/startup/</literal>.</para>
     </listitem>
 
     <listitem>
-      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
-      uCPE device has more than one HDD attached.</para>
+      <para><remark>ELCCR-1733</remark>Logging into the Enea Edge Management 
+        application over HTTP can fail, producing the error 
+        <literal>You have been automatically logged out</literal>. If this 
+        happens, the user should clear the <literal>JSESSIONID</literal> 
+        browser's cookie or close and restart the browser.</para>      
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-527</remark>Canceling a file upload in the Enea Edge
-      Management application will require the user to close and reopen the
-      upload window for the next upload to work.</para>
+      <para><remark>ELCCR-1753</remark>For tap interfaces, port numbers
+      assigned to VM bridge interfaces can change when the VMs are
+      restarted.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
-      is restored from a backup made on a release version older than Enea NFV
-      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+      <para><remark>LXCR-10922</remark>There is a very rare sporadic error on
+      the X553 SFP+ ethernet ports on Atom C3000 boards. This has been
+      verified on Supermicro A2SDi-TP8F boards. This sporadic error makes X553
+      ethernet ports unusable until a target cold reset is performed. When the
+      error occurs in Enea Edge Runtime 2.5.0, there will be a warning printed
+      into console by the ixgbe driver as follows: 
+        <programlisting>[ 11.361580] ixgbe 0000:0a:00.0: Warning firmware error detected FWSM: 0x8010801A</programlisting> 
+        The only currently known workaround for this issue is a cold reset.</para>
     </listitem>
+  </itemizedlist>
 
-    <listitem>
-      <para><remark>LXCR-10750</remark>In order to avoid an incorrect boot
-      order after a failed upgrade, the user should remove the upgrade image
-      before attempting again.</para>
-    </listitem>
+  <para><emphasis role="bold">Issues and limitations found in previous
+  releases of Enea Edge that still affect this current
+  release:</emphasis></para>
 
+  <itemizedlist>
     <listitem>
       <para><remark>ELCCR-474</remark>Deleting VNF instances with flows
       configured on the OVS bridges can be done only after removing the
@@ -43,59 +55,30 @@
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-527</remark>Canceling a file upload in the Enea Edge
+      Management application will require the user to close and reopen the
+      upload window for the next upload to work.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-572</remark>Sometimes when selecting and deleting
       more than one VNF instance simultaneously, an error message might be
       triggered, even if the delete operation succeeds.</para>
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
+      is restored from a backup made on a release version older than Enea NFV
+      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-847</remark>The Juniper vSRX VNF cannot be
       instantiated on the Xeon-D architectures due to missing CPU features in
       the VNF's domain XML. This impacts all example use cases where the
       Juniper VNF is used.</para>
     </listitem>
-
-    <listitem>
-      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
-      parameter on the VNF onboarding page is ignored. The default storage
-      size specified when creating the VM image is used when instantiating the
-      VM and when presenting VM information.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>LXCR-9853</remark>The WAN interface of a uCPE device needs
-      to be connected to a network with at least a router/gateway installed
-      for next-hop communication.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>LXCR-9992</remark>Depending on hardware capabilities,
-      there are certain limitations regarding the <literal>vfio-pci</literal>
-      and <literal>igb_uio</literal> drivers. While the Enea Edge Runtime uses
-      the <literal>vfio-pci</literal> driver by default, for certain hardware
-      configurations, <literal>igb_uio</literal> should be used instead, by
-      providing custom scripting. Please contact Enea for further
-      details.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>STCR-6224</remark>The Enea Edge Automation Framework and
-      Test Harness do not support multiple custom scripts uploaded to a uCPE
-      device at the same time.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
-      implemented in the Enea Edge Automation Framework and Test
-      Harness.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>USERDOCAP-628</remark>The Enea Edge Automation Framework
-      and Test Harness do not have support for product features implemented in
-      Enea Edge 2.4.0 or newer.</para>
-    </listitem>
-
+    
     <listitem>
       <para><remark>ELCCR-912</remark>When the Enea Edge Management
       application is installed on CentOS 7, prior to C7.1804 (kernel version
@@ -105,18 +88,24 @@
     </listitem>
 
     <listitem>
-      <para><remark>USERDOCAP-641</remark>Enea Edge does not have support for
-      IPv6 addresses on both uCPE devices and the Enea Edge Management
-      installation.</para>
+      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
+      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
+      not possible. Either switch to HTTP mode (for more details see <olink
+      targetdoc="book_enea_edge_getting_started"
+      targetptr="device_up_process">The uCPE device Upgrade Process in the
+      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
+      or install it manually.</para>
     </listitem>
 
     <listitem>
-      <para><remark>USERDOCAP-651</remark>Wireless AP configuration is
-      optimized for wireless modules that use the <literal>ath10k</literal>
-      driver. Using other wireless modules may result in undefined
-      behavior.</para>
+      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application
+      has an incorrect database configuration, when performing an
+      uninstallation, the Tomcat instance and Watchdog service will not be
+      stopped automatically. Instead, they must be killed explicitly.</para>
     </listitem>
-
+    
     <listitem>
       <para><remark>ELCCR-1565</remark>Before starting an Enea Edge Management
       upgrade, any owned Tomcat certificates should be manually copied into
@@ -125,88 +114,96 @@
       folder.</para>
     </listitem>
 
-    <listitem>
-      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application
-      has an incorrect database configuration, when performing an
-      uninstallation, the Tomcat instance and Watchdog service will not be
-      stopped automatically. Instead, they must be killed explicitly.</para>
+    <listitem condition="hidden">
+      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
+      navigation</emphasis>: When using links to open other PDFs, or jump to
+      another place in the same PDF, jumping back sometimes fails. This has
+      been observed when opening a PDF in Adobe Reader, inside a browser with
+      PDF add-on, as well as when the browser is configured to open PDF files
+      in an external PDF reader. As a workaround, open the HTML version of the
+      document.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
-      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
-      not possible. Either switch to HTTP mode (for more details see <olink
-      targetdoc="book_enea_edge_getting_started"
-      targetptr="device_up_process">The uCPE device Upgrade Process in the
-      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
-      xmlns:xi="http://www.w3.org/2001/XInclude"
-      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
-      or install it manually.</para>
+      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
+      uCPE device has more than one HDD attached.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1688, ELCCR-1809</remark>It is possible to end up
-      with a corrupted VM image from the download operation. If that happens,
-      the VNF instantiation will fail. The corrupted image has to be manually
-      removed from <literal>/var/odm/vm_images/startup/</literal>.</para>
+      <para><remark>LXCR-9853</remark>The WAN interface of a uCPE device needs
+      to be connected to a network with at least a router/gateway installed
+      for next-hop communication.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1925</remark>VNF filtering based on VIM does not
-      work.</para>
+      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
+      USB storage devices.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1733</remark>Logging into the Enea Edge Management 
-        application over HTTP can fail. If this happens, the user should clear 
-        the session cookie from the browser.</para>
+      <para><remark>LXCR-9992</remark>Depending on hardware capabilities,
+      there are certain limitations regarding the <literal>vfio-pci</literal>
+      and <literal>igb_uio</literal> drivers. While the Enea Edge Runtime uses
+      the <literal>vfio-pci</literal> driver by default, for certain hardware
+      configurations, <literal>igb_uio</literal> should be used instead, by
+      providing custom scripting. Please contact Enea for further
+      details.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1571</remark>Uploading a domain update script when
-      instantiating a VNF does not work. The modifications from the script are
-      not taken into account.</para>
+      <para><remark>LXCR-10750</remark>In order to avoid an incorrect boot
+      order after a failed upgrade, the user should remove the upgrade image
+      before attempting again.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1757</remark>The management WAN interface can be
-      overwritten from an offline config.</para>
-    </listitem>
+      <para><remark>STCR-6224</remark>The Enea Edge Automation Framework and
+      Test Harness do not support multiple custom scripts uploaded to a uCPE
+      device at the same time.</para>
+      
+      <note>
+        <para>This limitation does not apply to Enea Edge Automation. It only 
+          affects the Enea Edge Automation Framework and Test Harness.</para>
+      </note>
+    </listitem>    
 
     <listitem>
-      <para><remark>ELCCR-1845</remark>Enea Edge Telemetry does not work.</para>
+      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
+      implemented in the Enea Edge Automation Framework and Test
+      Harness.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1873</remark>Failover to a previous working image
-      when booting a faulty Enea Edge Runtime image does not work.</para>
-    </listitem>
+      <para><remark>USERDOCAP-628</remark>The Enea Edge Automation Framework
+      and Test Harness do not have support for product features implemented in
+      Enea Edge 2.4.0 or newer.</para>
 
-    <listitem>
-      <para><remark>ELCCR-1753</remark>For tap interfaces, port numbers
-      assigned to VM bridge interfaces can change when the VMs are
-      restarted.</para>
+      <note>
+        <para>This limitation does not apply to Enea Edge Automation. It only 
+          affects the Enea Edge Automation Framework and Test Harness. Please 
+          use the new Enea Edge Automation component if you want support for 
+          newer features.</para>
+      </note>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1758</remark>Socket Memory filed in DPDK settings
-      needs to be larger than 1 GB.</para>
+      <para><remark>USERDOCAP-641</remark>Enea Edge does not have support for
+      IPv6 addresses on both uCPE devices and the Enea Edge Management
+      installation.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1658</remark>VNFs that have been offboarded after a
-      backup is complete, cannot be restored by the NFVi backup
-      functionality.</para>
+      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
+      parameter on the VNF onboarding page is ignored. The default storage
+      size specified when creating the VM image is used when instantiating the
+      VM and when presenting VM information.</para>
     </listitem>
 
-    <listitem condition="hidden">
-      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
-      navigation</emphasis>: When using links to open other PDFs, or jump to
-      another place in the same PDF, jumping back sometimes fails. This has
-      been observed when opening a PDF in Adobe Reader, inside a browser with
-      PDF add-on, as well as when the browser is configured to open PDF files
-      in an external PDF reader. As a workaround, open the HTML version of the
-      document.</para>
+    <listitem>
+      <para><remark>USERDOCAP-651</remark>Wireless AP configuration is
+      optimized for wireless modules that use the <literal>ath10k</literal>
+      driver. Using other wireless modules may result in undefined
+      behavior.</para>
     </listitem>
   </itemizedlist>
 
diff --git a/doc/book-enea-edge-release-info/doc/main_changes.xml b/doc/book-enea-edge-release-info/doc/main_changes.xml
index b301cac..85a5e7e 100644
--- a/doc/book-enea-edge-release-info/doc/main_changes.xml
+++ b/doc/book-enea-edge-release-info/doc/main_changes.xml
@@ -26,8 +26,8 @@
       </listitem>
 
       <listitem>
-        <para>Support for a DNS servers list for WAN interfaces
-                with a static IP configuration. For more details please see <olink
+        <para>Support for a DNS servers list for WAN interfaces with a static
+        IP configuration. For more details please see <olink
         targetdoc="book_enea_edge_getting_started"
         targetptr="install_ena_device">Installing Enea Edge - uCPE Device
         Installation in the <xi:include
@@ -96,9 +96,9 @@
       </listitem>
 
       <listitem>
-        <para>The Enea Edge Management application will wait for 10 minutes 
-                instead of 5 for the Enea Edge Runtime upgrade operations to complete 
-                successfully, before reporting an error.</para>
+        <para>The Enea Edge Management application will wait for 10 minutes
+        instead of 5 for the Enea Edge Runtime upgrade operations to complete
+        successfully, before reporting an error.</para>
       </listitem>
 
       <listitem>
@@ -108,8 +108,9 @@
       </listitem>
 
       <listitem>
-        <para>Enea Edge Runtime key component upgrades include: <itemizedlist
-            spacing="compact">
+        <para>Enea Edge Runtime key component upgrades include:</para> 
+          
+          <itemizedlist spacing="compact">
             <listitem>
               <para>Linux kernel 5.10</para>
             </listitem>
@@ -127,14 +128,17 @@
             </listitem>
 
             <listitem>
-              <para>DPDK 20.11.0</para>
+              <para>DPDK 20.11.1</para>
             </listitem>
-          </itemizedlist></para>
-      </listitem>
-
-      <listitem>
-        <para>Python3 (v3.9.4) replaced Python2 support in Enea Edge
-        Runtime.</para>
+          
+            <listitem>
+              <para>Python 3.9.4, replacing Python2 support</para>
+            </listitem>          
+          </itemizedlist>
+        
+            <para>Further information about what open source versions are used 
+              in Enea Edge Runtime, can be found in the Enea Edge Runtime 
+              Open Source Report.</para>
       </listitem>
     </itemizedlist>
 
@@ -209,6 +213,7 @@
   <section id="relinfo-backward-compat">
     <title>Compatibility</title>
 
-    <para>This release does not contain any public API changes impacting backwards compatibility.</para>
+    <para>This release does not contain any public API changes impacting
+    backwards compatibility.</para>
   </section>
 </chapter>
\ No newline at end of file