From 240f4c7b75d836dd6135ff2763cf46ac4a9d8ee9 Mon Sep 17 00:00:00 2001 From: mrpa Date: Thu, 3 Dec 2020 12:11:45 +0100 Subject: Final text edits to the getting started. Change-Id: I6669f7f381adffb235d77487ade1b8263ac09db4 Signed-off-by: mrpa --- .../doc/advanced_configurations.xml | 2 +- .../doc/images/prep_deploy.png | Bin 322979 -> 141376 bytes .../doc/images/prep_execution.png | Bin 312054 -> 132829 bytes .../doc/installation_guide.xml | 28 +++++++++++++-------- .../doc/introduction.xml | 4 +-- 5 files changed, 20 insertions(+), 14 deletions(-) diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml index 8925498..c03f657 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml @@ -64,7 +64,7 @@ CSM support and Dual Boot must be enabled in BIOS (i.e. PXE booting in legacy mode), while the final Enea NFV Access image will boot in UEFI mode. Doing a mass deployment using legacy PXE booting - usually means that SecureBoot is disabled, SecureBoot will need to + usually means that Secure Boot is disabled, Secure Boot will need to be enabled afterwards. diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png index e75275e..67b96a9 100755 Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png and b/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png differ diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png index 2917cd6..f589495 100755 Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png and b/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png differ diff --git a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml index 9e0ccb8..acd53b4 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml @@ -172,13 +172,13 @@ sudo systemctl mask -now firewalld Use the following command sequence to enable the required ports for deployment of the Enea uCPE Manager: - sudo firewall-cmd --permanent --add-service=80/tcp -sudo firewall-cmd --permanent --add-service=443/tcp -sudo firewall-cmd --permanent --add-service=54327/udp -sudo firewall-cmd --permanent --add-service=5701-5708/tcp -sudo firewall-cmd --permanent --add-service=4334/tcp -sudo firewall-cmd --permanent --add-service=2021-2040/tcp -sudo firewall-cmd --permanent --add-service=7000-7010/tcp + sudo firewall-cmd --permanent --add-port=80/tcp +sudo firewall-cmd --permanent --add-port=443/tcp +sudo firewall-cmd --permanent --add-port=54327/udp +sudo firewall-cmd --permanent --add-port=5701-5708/tcp +sudo firewall-cmd --permanent --add-port=4334/tcp +sudo firewall-cmd --permanent --add-port=2021-2040/tcp +sudo firewall-cmd --permanent --add-port=7000-7010/tcp sudo firewall-cmd --reload @@ -261,7 +261,7 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar

yum remove postgres\* -rm -f /var/lib/pgsql +rm -rf /var/lib/pgsql rm -f /etc/postgres-reg.ini userdel postgres @@ -620,7 +620,7 @@ SystemBackup_MMMDD_YYYY_HHMM_SS.zip Run Time Platform To install the Enea NFV Access Run Time Platform, create a - bootable USB stick with the image you intend to install. + bootable USB stick with the image you intend to install. In the example below, step by step instructions are provided for the CentOS 7 distribution. It's possible with the appropriate tools to @@ -774,6 +774,12 @@ of=/dev/sdb bs=4M conv=fsync stage, user should remove the USB stick and LAN cable and shutdown the uCPE device. It will be started after necessary configurations are done on the Enea uCPE Manager, as described below. + + + If the USB stick was booted in UEFI mode, an UEFI boot entry is + automatically created and the system will start booting from the + hard drive without further user configuration. +
@@ -879,7 +885,7 @@ of=/dev/sdb bs=4M conv=fsync establish a management connection, the user will add uCPE device information in the Enea uCPE Manager. This is accomplished by selecting Devices -> Manage -> - Add. + Add. The relevant parameters are: @@ -943,7 +949,7 @@ of=/dev/sdb bs=4M conv=fsync misconfiguration), the uCPE device status will be seen as RED (disconnected) in Enea uCPE Manager. Please check the accuracy of the information provided when the uCPE device was registered in the Enea - uCPE Manager. + uCPE Manager. The uCPE device configuration can be amended. In order to do that, please remove the WAN cable(s), reconnect the laptop to the LAN diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml index c303902..d403abf 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml @@ -32,7 +32,7 @@ - The Enea NFV Access Run-Time Platform, which acts as the host + The Enea NFV Access Run Time Platform, which acts as the host for Virtualized Network Functions (VNFs) and provides management over NETCONF. @@ -60,7 +60,7 @@
Enea NFV Access Run Time Platform - Enea NFV Access Runtime Platform is a lightweight, + Enea NFV Access Run Time Platform is a lightweight, multi-architecture virtualization platform built on de-facto standards in an SDN/NFV ecosystem. It is designed for a high networking performance with minimal hardware footprint, by only providing relevant -- cgit v1.2.3-54-g00ecf