summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndreas Wellving <andreas.wellving@enea.com>2021-08-23 16:01:06 +0200
committerMiruna Paun <mrpa@enea.se>2021-08-24 09:37:16 +0100
commit01a40353d65ff7b73d507270d4c76d50886207de (patch)
tree729a616abaa039cf0bdd48f8e0f0d12e87d8bc35
parentaaedc7e34cb66a60cde56d8258680e7f8f37b05b (diff)
downloadnfv-access-documentation-01a40353d65ff7b73d507270d4c76d50886207de.tar.gz
getting-started: Mention postinstall timeoutEnea_Edge_2.5.0_RC3
Change-Id: I6cf6d6a8e1e795bd464d845ac1024ad381a3ccb6 Signed-off-by: Andreas Wellving <andreas.wellving@enea.com>
-rw-r--r--doc/book-enea-edge-getting-started/doc/installation_guide.xml11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
index 32a39c0..dbf4c54 100644
--- a/doc/book-enea-edge-getting-started/doc/installation_guide.xml
+++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
@@ -97,8 +97,8 @@
97 97
98 <para>When hosting an entire solution including one or several network 98 <para>When hosting an entire solution including one or several network
99 services, the hardware must also have the resources to host one or 99 services, the hardware must also have the resources to host one or
100 more VNFs. During a typical evaluation, a dual VNF service on the Enea 100 more VNFs. A dual VNF service on the Enea
101 Edge Runtime needs a CPU with 4-8 cores and at least 8 GB RAM. The 101 Edge Runtime typically needs a CPU with 4-8 cores and at least 8 GB RAM. The
102 supported Intel CPUs of Enea Edge are documented in the <xi:include 102 supported Intel CPUs of Enea Edge are documented in the <xi:include
103 href="../../s_docbuild/olinkdb/pardoc-common.xml" 103 href="../../s_docbuild/olinkdb/pardoc-common.xml"
104 xmlns:xi="http://www.w3.org/2001/XInclude" 104 xmlns:xi="http://www.w3.org/2001/XInclude"
@@ -1177,8 +1177,9 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
1177 (disconnected) in the Enea Edge Management application. The uCPE device 1177 (disconnected) in the Enea Edge Management application. The uCPE device
1178 configuration can be corrected by removing the WAN cable(s), 1178 configuration can be corrected by removing the WAN cable(s),
1179 reconnecting the laptop to the LAN interface of the uCPE device and 1179 reconnecting the laptop to the LAN interface of the uCPE device and
1180 rebooting it. At this point, the Web-installer can be accessed from the 1180 rebooting it. After a timeout of a few minutes,
1181 laptop as described in <olink targetdoc="book_enea_edge_getting_started" 1181 the Web-installer can be accessed from the laptop as described in
1182 <olink targetdoc="book_enea_edge_getting_started"
1182 targetptr="install_ena_device">Installing Enea Edge - uCPE Device 1183 targetptr="install_ena_device">Installing Enea Edge - uCPE Device
1183 installation in the <xi:include 1184 installation in the <xi:include
1184 href="../../s_docbuild/olinkdb/pardoc-names.xml" 1185 href="../../s_docbuild/olinkdb/pardoc-names.xml"
@@ -1292,4 +1293,4 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
1292 </note> 1293 </note>
1293 </section> 1294 </section>
1294 </section> 1295 </section>
1295</chapter> \ No newline at end of file 1296</chapter>