Rel-Info: add CR number for the known issues

Rename "CPE devices" to "CPE devices".

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

1 files changed, 12 insertions, 7 deletions

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 fdeef66..65c460d 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
@@ -16,7 +16,7 @@
     <para><emphasis role="bold">Enea uCPE Manager</emphasis></para>
 
     <listitem>
-      <para><remark>LXCR-9056</remark>Instantiating a VNF with a different
+      <para><remark>ELCCR-115</remark>Instantiating a VNF with a different
       number of interfaces than was specified during VNF onboarding causes an
       exception.</para>
     </listitem>
@@ -39,21 +39,26 @@
     </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>
+      <para><remark>ELEMCR-1725</remark>No disk space check is performed when
+       instantiating (i.e. downloading) a VNF to the uCPE 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>
+      <para><remark>ELCCR-107</remark>The Enea uCPE Manager will not detect that
+      a VNF is no longer running if the uCPE device is reinstalled with the Enea
+      NFV Access Run-Time platform and rebooted after the VNF has been instantiated.</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>
+      <para><remark>ELCCR-119</remark>No support is provided for multiple uCPE devices
+      behind a firewall or gateway connecting callhome to a uCPE Manager (running
+      outside the local network).</para>
     </listitem>
 
     <listitem>
-      <para>There is no keepalive mechanism in place for callhome.</para>
+      <para><remark>ELEMCR-1690</remark>There is no keepalive mechanism in place
+      for callhome.</para>
     </listitem>
 
   </itemizedlist>