29 files changed, 5397 insertions, 0 deletions

diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
new file mode 100644
index 0000000..70a9978
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -0,0 +1,1042 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="advanced_conf">
+  <title>Advanced Configurations</title>
+
+  <para>This chapter describes possible configurations for advanced features
+  such as the Hugepage Reservation Service customization, UEFI Secure Boot and
+  Bare Metal Provisioning.</para>
+
+  <section id="bare_meta_prov">
+    <title>Bare Metal Provisioning</title>
+
+    <para>Bare Metal Provisioning can be used for automated deployment of the
+    Enea Edge Runtime on a large number of uCPE devices. The uCPE devices may
+    have no previous operating system installed, or are reinstalled without
+    preserving any existing data. Enea Edge Bare Metal Provisioning is based
+    on standardized Pre-Boot Execution environment (PXE) booting.</para>
+
+    <para>The Bare Metal Provisioning process begins by PXE booting an Enea
+    Edge installer <literal>initramfs</literal> image. The installer downloads
+    a configuration file, as well as the Enea Edge Runtime image and then
+    proceeds to install the system by dividing the disk into 2 partitions: a
+    GPT partition containing the GRUB boot loader and a second partition
+    containing the Enea Edge Runtime root filesystem. When the installation is
+    complete, the uCPE device is automatically rebooted into Enea Edge
+    Runtime.</para>
+
+    <note>
+      <para>The <literal>.hddimg</literal>, <literal>initramfs</literal>, and
+      <literal>bzImage</literal> files are available in the
+      <filename>Enea_Edge_Runtime_&lt;processor&gt;_&lt;version&gt;-&lt;build_number&gt;.tar.gz</filename>
+      file you downloaded with your release.</para>
+    </note>
+
+    <section id="bare_meta_prov_prereq">
+      <title>Prerequisites</title>
+
+      <itemizedlist>
+        <listitem>
+          <para>The uCPE devices to be installed are connected in a working
+          PXE network boot environment. The PXE server can be set up using any
+          Linux distribution that includes TFTP and DHCP software packages.
+          Refer to the documentation for your distribution for setup
+          instructions.</para>
+        </listitem>
+
+        <listitem>
+          <para>An HTTP server must be available and accessible from the uCPE
+          devices in the provisioning network. Note that the installer will
+          use the same interface that the uCPE device is PXE-booted from, to
+          obtain an IP address using DHCP and access the HTTP server.</para>
+        </listitem>
+
+        <listitem>
+          <para>The uCPE devices are preconfigured in BIOS to boot from the
+          hard drive where the Enea Edge Runtime will be installed.</para>
+        </listitem>
+
+        <listitem>
+          <para>CSM support and Dual Boot must be enabled in BIOS (i.e. PXE
+          booting in legacy mode), while the final Enea Edge Runtime image
+          will boot in UEFI mode. Doing a mass deployment using legacy PXE
+          booting usually means that Secure Boot is disabled, Secure Boot will
+          need to be enabled afterwards.</para>
+        </listitem>
+
+        <listitem>
+          <para>A remote management tool such as <literal>ipmitool</literal>
+          (or a vendor-specific tool) is available for use to set the next
+          boot option to PXE and reboot the uCPE devices in order to begin the
+          installation.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="bare_meta_prov_server">
+      <title>Server Configuration</title>
+
+      <para>The following images provided with your Enea Edge release need to
+      be made available on the PXE and HTTP servers:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Copy the Enea Edge installer <literal>initramfs</literal>
+          image and kernel <literal>bzImage</literal> for your uCPE device
+          architecture to the TFTP directory on the PXE server (e.g
+          <literal>/var/lib/tftpboot</literal>).</para>
+        </listitem>
+
+        <listitem>
+          <para>Compress the Enea Edge Runtime <literal>.hddimg</literal>
+          image for the uCPE device architecture using <literal>gzip</literal>
+          and copy the resulting <literal>hddimg.gz</literal> file to the HTTP
+          server.</para>
+        </listitem>
+      </orderedlist>
+
+      <section id="bare_meta_prov_install_config">
+        <title>Installation Configuration File</title>
+
+        <para>An installation configuration file needs to be prepared on the
+        HTTP server. The format of the configuration file is a list of
+        "<literal>name = value</literal>" pairs and the available parameters
+        are described below.</para>
+
+        <para>Mandatory parameter(s):</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><literal>image_url</literal>. The HTTP server URL used for
+            downloading the Enea Edge Runtime image.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>Optional parameters:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><literal>install_drive</literal>. The name of the drive
+            where the Enea Edge Runtime will be installed (e.g
+            <literal>/dev/sda</literal>). If not set, the installer will use
+            the largest detected (non-USB) drive on the uCPE device.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>prompt_user</literal>. If the parameter is set to
+            "yes", the installer will ask for confirmation before formatting
+            and partitioning the drive. The default behaviour is to proceed
+            automatically without any user interaction.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>Installation Configuration File Example:</para>
+
+        <programlisting>image_url = http://192.168.1.100/enea-nfv-access-xeon-d.hddimg.gz
+install_drive = /dev/sda</programlisting>
+
+        <note>
+          <para>The installation configuration file needs to use the Linux
+          end-of-line format (\n), not the Windows format (\r\n).</para>
+        </note>
+      </section>
+
+      <section id="bare_meta_prov_pxe">
+        <title>PXE Configuration</title>
+
+        <para>A PXE entry for the Enea Edge installation needs to be added as
+        the default boot selection in the pxelinux configuration file (e.g
+        <literal>/var/lib/tftpboot/pxelinux.cfg/default</literal>). The PXE
+        entry should have the following settings:</para>
+
+        <programlisting>default nfv_access
+label nfv_access
+menu label ^NFV_ACCESS_INSTALLER
+kernel &lt;Path to kernel&gt;
+append root=/dev/ram0 initrd=&lt;Path to initramfs&gt; LABEL=pxe-installer \
+   INSTALL_CFG=http://&lt;Server IP&gt;/&lt;Path to install config file&gt; \
+   console=ttyS0,115200 earlyprintk=ttyS0,115200
+ipappend 2</programlisting>
+      </section>
+    </section>
+
+    <section id="bare_meta_prov_inst">
+      <title>Starting the Installation</title>
+
+      <para>To initiate the installation, set the boot device (for next boot
+      only) to PXE and reboot the uCPE devices. How to do this depends on the
+      remote management capabilities of the uCPE devices and may require
+      vendor-specific tools.</para>
+
+      <para>Example initiation using <literal>ipmitool</literal>:</para>
+
+      <programlisting>ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; chassis bootdev pxe
+ipmitool -U &lt;user&gt; -P &lt;password&gt; -H &lt;uCPE device IPMI IP address&gt; power reset   </programlisting>
+
+      <para>The uCPE devices should be configured in BIOS to boot from the
+      installation drive first in order to automatically start the Enea Edge
+      Runtime when the installation is finished.</para>
+    </section>
+  </section>
+
+  <section id="uefi_secure_boot">
+    <title>UEFI Secure Boot</title>
+
+    <para>Secure Boot was designed to enhance security in the pre-boot
+    environment. It prevents malicious software and applications from being
+    loaded during the system start-up process.</para>
+
+    <para>The basic principle of UEFI Secure Boot is that it requires all
+    artifacts involved in the boot process (bootloaders, kernel, initramfs) to
+    be signed using a set of private keys. On a Secure Boot enabled uCPE
+    device these artifacts are checked against a set of public certificates
+    which correspond to these keys. If there are any mismatches the boot
+    process will fail at the stage(s) they are detected.</para>
+
+    <para>For more information about Secure Boot please refer to <ulink
+    url="https://www.uefi.org/sites/default/files/resources/UEFI_Secure_Boot_in_Modern_Computer_Security_Solutions_2013.pdf">Secure
+    Boot in Modern Computer Security Solutions</ulink>.</para>
+
+    <section id="secure_boot_keys">
+      <title>Enabling UEFI Secure Boot</title>
+
+      <para>All Enea Edge image artifacts delivered with the release are
+      signed using the Enea UEFI Secure boot private keys. These artifacts can
+      be used on a uCPE device that doesn't have Secure Boot enabled. To use
+      the Secure Boot feature, however, the user must make the Enea UEFI
+      Secure Boot public certificates available on the uCPE device before
+      enabling the feature in BIOS. This process is called
+      "Provisioning".</para>
+
+      <section id="manual_key_provisioning">
+        <title>Provisioning the Enea UEFI Secure Boot Certificates</title>
+
+        <para>The UEFI firmware is normally shipped with factory preloaded
+        certificates. If these do not already include Certificates from Enea,
+        they will need to be appended or replaced with the Enea
+        Certificates.</para>
+
+        <para><emphasis role="bold">UEFI Secure Boot certificates provided
+        with your release:</emphasis></para>
+
+        <itemizedlist>
+          <listitem>
+            <para><literal>Platform Key (PK)</literal>: this key protects the
+            next key from uncontrolled modification. Once this key is
+            enrolled, Secure Boot enters into <literal>User Mode</literal>.
+            The drivers and loaders signed with the <literal>Platform
+            Key</literal> can then be loaded by the firmware.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>Key Exchange key (KEK)</literal>: this key allows
+            other certificates which have a connection to the private portion
+            of the <literal>Platform Key</literal> to be used.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>Authorized Signature (DB)</literal>: contains the
+            <literal>trusted keys</literal> used for authenticating any
+            drivers or applications executed in the UEFI environment.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>The Enea UEFI Secure Boot certificates are installed together
+        with the Enea Edge Runtime onto the hard drive. They can be found on
+        the EFI partition (usually the first partition of the drive) under
+        <literal>/uefi_sb_keys</literal>.</para>
+
+        <para>These certificates need to be manually enrolled in BIOS. The
+        exact details on how to proceed may vary depending the version of the
+        UEFI firmware.</para>
+
+        <para>The UEFI firmware is normally shipped with factory preloaded
+        certificates. If these do not already include Certificates from Enea,
+        they will need to be appended or replaced with the Enea
+        Certificates.</para>
+      </section>
+
+      <section id="enable_secure_boot">
+        <title>Enabling Secure Boot in BIOS</title>
+
+        <para>Once the certificates are enrolled, Secure Boot needs to be
+        enabled in BIOS and the device rebooted.</para>
+      </section>
+    </section>
+  </section>
+
+  <section id="hugepage_reservation">
+    <title>Hugepage Reservation Service</title>
+
+    <para>Huge page memory support is a mechanism that allows the Linux kernel
+    to support larger page sizes than the default page unit (4KB). Huge pages
+    are contiguous blocks of memory that come in 2MB or 1GB sizes. By using
+    huge page allocations, less memory is used for page tables and the
+    Translation Lookaside Buffer (TLB) miss rate is significantly reduced.
+    Enea Edge Runtime uses huge page backed memory in KVM guests in order to
+    improve performance.</para>
+
+    <para>Enea Edge Runtime implements an automatic hugepage allocation
+    service that is triggered at each startup. The service is skipped if
+    hugepages have been allocated in the kernel boot command line.</para>
+
+    <para>There are two strategies outlined for hugepage allocation:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>If a system has an amount of memory up to 8GB, the allocation
+        algorithm will reserve up to 30% (no more than 2GB), for the OS and
+        the rest as 2MB hugepages.</para>
+      </listitem>
+
+      <listitem>
+        <para>If a system has an amount of memory that's higher than 8GB, the
+        allocation algorithm will reserve all but 2GB of memory as 1GB
+        hugepages, leaving the rest (2GB) to be used by the OS.</para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <para>This is a best effort reservation after kernel boot, so the
+      results may vary accordingly.</para>
+    </note>
+
+    <section id="hugepage_customizing_auto">
+      <title>Customizing Automatic Hugepage Reservation</title>
+
+      <para>Configuration of Hugepage reservation is done in
+      <literal>/etc/enea-nfv-access/hugepages.cfg</literal>.</para>
+
+      <para><emphasis role="bold">Parameters used by the automatic algorithm:
+      </emphasis></para>
+
+      <itemizedlist spacing="compact">
+        <listitem>
+          <para><literal>hugepage_setup</literal>: Enables the automatic
+          configuration algorithm. It has only one value,
+          <literal>auto</literal>. For manual configuration comment or remove
+          this parameter. Use the other parameter descriptions as a
+          template/example.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>threshold_to_use_1g</literal>: Decides the threshold
+          which instructs the algorithm to use 1GB hugepages. If a system's
+          memory is higher than <literal>threshold_to_use_1g</literal>, then
+          the algorithm will use 1GB hugepages, otherwise it will use 2MB
+          hugepages.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>percent_os_alloc</literal>: Decides how much memory
+          to try to reserve for userspace applications. The algorithm will try
+          to reserve at least the value of <literal>percent_os_alloc</literal>
+          of the total system memory for userspace applications.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>maximum_os_alloc_mb</literal>: Maximum amount of
+          memory to allocate for userspace applications. If
+          <literal>percent_os_alloc</literal> of the total system memory
+          exceeds <literal>maximum_os_alloc_mb</literal> then the maximum
+          allocated memory for userspace applications is
+          <literal>maximum_os_alloc_mb</literal>.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Example of automatic Hugepage
+      Configuration:</emphasis></para>
+
+      <programlisting>hugepage_setup = auto
+threshold_to_use_1g = 8192
+percent_os_alloc = 30
+maximum_os_alloc_mb = 2048</programlisting>
+
+      <para>The following possible allocations can result (based on total
+      system memory available):</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>2GB of memory: approximately 30% will be allocated for the OS
+          and the rest will be allocated as 2MB hugepages.</para>
+        </listitem>
+
+        <listitem>
+          <para>4GB of memory: approximately 30% will be allocated for the OS
+          and the rest will be allocated as 2MB hugepages.</para>
+        </listitem>
+
+        <listitem>
+          <para>16GB of memory: approximately 2GB will be allocated for the OS
+          and the rest as 1GB hugepages.</para>
+        </listitem>
+      </itemizedlist>
+
+      <note>
+        <para>The memory allocated for the kernel and hugepages might vary
+        slightly depending on how much memory is available.</para>
+      </note>
+    </section>
+
+    <section id="hugepage_customizing_man">
+      <title>Customizing Manual Hugepage Reservation</title>
+
+      <para>The automatic algorithm can be disabled and hugepages in turn,
+      configured manually. To do this, comment the line which defines
+      <literal>hugepage_setup</literal> as <literal>auto</literal> and
+      configure memory for each CPU socket in the following manner:</para>
+
+      <programlisting>&lt;NUMA node&gt;.&lt;hugepage size&gt; = &lt;number of pages&gt;</programlisting>
+
+      <para>Where <literal>&lt;NUMA node&gt;</literal> refers to a node which
+      is part of the system's NUMA topology, <literal>&lt;hugepage
+      size&gt;</literal> decides what type of hugepages should be set and
+      <literal>&lt;number of hugepages&gt;</literal> is how many hugepages of
+      <literal>&lt;hugepage size&gt;</literal> should be allocated.</para>
+
+      <para>To list the available system nodes, run:</para>
+
+      <programlisting>ls -d /sys/devices/system/node/node* </programlisting>
+
+      <para>To list available hugepage sizes, per node, run:</para>
+
+      <programlisting>ls -d /sys/devices/system/node/node*/hugepages/hugepages-*</programlisting>
+
+      <para>Example of Manual Hugepage Configuration, configuring the system
+      to allocate three 1GB hugepages and 512 of 2MB hugepages on node:</para>
+
+      <programlisting>node0.2048kB = 512
+node0.1048576kB = 3 </programlisting>
+
+      <note>
+        <para>Make sure there are no hugepages reserved in the kernel boot
+        command line, these will override any manual configuration done in the
+        service.</para>
+      </note>
+    </section>
+  </section>
+
+  <section id="high_availability_ig">
+    <title>Installing the Enea Edge Management in High Availability
+    Mode</title>
+
+    <para>The following describes the setup needed for running the Enea Edge
+    Management in High Availabilty (HA) mode, with a MariaDB database cluster.
+    A setup example is illustrated in the diagram below.</para>
+
+    <figure>
+      <title>The High Availability setup</title>
+
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" contentwidth="600"
+                     fileref="images/high_av_setup.png" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <para>The setup consists of two sub-clusters, placed in different
+    geographical locations, each consisting of three MariaDB servers. In this
+    example, two of the machines are running only MariaDB, while the rest are
+    hosting a MariaDB server and an Enea Edge Management instance. The entire
+    network is hidden behind a firewall that performs NAT. While in protection
+    (cluster) mode, the Enea Edge Management instances promote a Virtual IP
+    (VIP) that represents the IP address of the entire cluster. The firewall
+    in this case will allocate a public IP for the outside world that will be
+    translated into the VIP. Also in this example, the traffic towards the
+    cluster from outside the firewall is done through HTTPS, which will be
+    translated to HTTP inside the private network.</para>
+
+    <note>
+      <para>By default, communication to the Enea Edge Management is done with
+      HTTPS. To enable HTTP, go to <emphasis role="bold">System</emphasis>,
+      <emphasis role="bold">Configuration</emphasis>, click on the <emphasis
+      role="bold">Web Access</emphasis> tab and check the <emphasis
+      role="bold">Enable HTTP</emphasis> checkbox.</para>
+    </note>
+
+    <section id="ha_reqs">
+      <title>Requirements for High Availability</title>
+
+      <para>The following hardware is needed for deploying the base
+      configuration:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Machines running the Enea Edge Management and MariaDB:</para>
+
+          <itemizedlist spacing="compact">
+            <listitem>
+              <para>4 CPU cores</para>
+            </listitem>
+
+            <listitem>
+              <para>12 - 16 GB memory</para>
+            </listitem>
+
+            <listitem>
+              <para>256 - 512 GB hard disk</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Machines running only MariaDB:</para>
+
+          <itemizedlist spacing="compact">
+            <listitem>
+              <para>2 CPU cores</para>
+            </listitem>
+
+            <listitem>
+              <para>8 GB memory</para>
+            </listitem>
+
+            <listitem>
+              <para>256 - 512 GB hard disk</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="firewall_rules">
+      <title>Firewall Rules</title>
+
+      <para>Please refer to <olink
+      targetdoc="book_enea_nfv_access_getting_started"
+      targetptr="firewall_config">Firewall Configuration in the <xi:include
+      href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+      Manual. In addition, the following configuration is needed:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Disable <literal>SELINUX</literal> on all database servers by
+          editing <literal>/etc/sysconfig/selinux</literal> and changing the
+          following:</para>
+
+          <programlisting>SELINUX=disabled
+SELINUXTYPE=targeted</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Reboot the server:</para>
+
+          <programlisting>[root@localhost ~]# sudo shutdown -r now</programlisting>
+        </listitem>
+      </orderedlist>
+
+      <para>The following ports should be opened in the local firewall (not
+      the one doing NAT), for each Enea Edge Management machine:</para>
+
+      <table>
+        <title>Ports for Enea Edge Management Machines</title>
+
+        <tgroup cols="2">
+          <colspec align="left" />
+
+          <thead>
+            <row>
+              <entry align="center">Port (Protocol)</entry>
+
+              <entry align="center">Usage</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>80 (TCP)</entry>
+
+              <entry>HTTP</entry>
+            </row>
+
+            <row>
+              <entry>443 (TCP)</entry>
+
+              <entry>HTTPS</entry>
+            </row>
+
+            <row>
+              <entry>54327 (UDP)</entry>
+
+              <entry>Cluster multicasting (Hazelcast)</entry>
+            </row>
+
+            <row>
+              <entry>5701 - 5708 (TCP)</entry>
+
+              <entry>Hazelcast communications</entry>
+            </row>
+
+            <row>
+              <entry>4334 (TCP)</entry>
+
+              <entry>NETCONF call-home</entry>
+            </row>
+
+            <row>
+              <entry>7000 - 7009 (TCP)</entry>
+
+              <entry>Reverse SSH connection pool</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <para>For MariaDB, the following ports must be opened (on each MariaDB
+      server, including the ones hosting the Enea Edge Management):</para>
+
+      <table>
+        <title>Ports for MariaDB Machines</title>
+
+        <tgroup cols="2">
+          <colspec align="left" />
+
+          <thead>
+            <row>
+              <entry align="center">Port (Protocol)</entry>
+
+              <entry align="center">Usage</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>3306 (TCP)</entry>
+
+              <entry>Client connections</entry>
+            </row>
+
+            <row>
+              <entry>4567 (UDP/TCP)</entry>
+
+              <entry>Galera cluster replication with multicasting</entry>
+            </row>
+
+            <row>
+              <entry>4568 (TCP)</entry>
+
+              <entry>Incremental state transfer</entry>
+            </row>
+
+            <row>
+              <entry>4444 (TCP)</entry>
+
+              <entry>State snapshot transfer</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <para>The following ports should be accessible externally and translated
+      to the Virtual IP side as shown below:</para>
+
+      <table>
+        <title>Ports for Virtual IP</title>
+
+        <tgroup cols="3">
+          <colspec align="left" />
+
+          <thead>
+            <row>
+              <entry align="center">External Port (Protocol)</entry>
+
+              <entry align="center">Usage</entry>
+
+              <entry align="center">Local Port (Protocol)</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>443 (TCP)</entry>
+
+              <entry>HTTPS to/back HTTP</entry>
+
+              <entry>80 (TCP)</entry>
+            </row>
+
+            <row>
+              <entry>4334 (TCP)</entry>
+
+              <entry>NETCONF call-home</entry>
+
+              <entry>4334 (TCP)</entry>
+            </row>
+
+            <row>
+              <entry>7000 - 7009 (TCP)</entry>
+
+              <entry>Reverse SSH connection pool</entry>
+
+              <entry>7000 - 7009 (TCP)</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
+
+    <section id="ha_installation">
+      <title>Installing High Availability</title>
+
+      <para>The Enea Edge Management can be installed in High Availability
+      mode with a MariaDB database cluster by performing the following steps.
+      The mandatory Java configuration is also detailed.</para>
+
+      <section id="ha_mariadb">
+        <title>Installing and configuring the MariaDB cluster</title>
+
+        <para>Install the latest MariaDB packages on all servers.</para>
+
+        <note>
+          <para>The setup was tested using MariaDB 10.5.8, built for CentOS
+          7.</para>
+        </note>
+
+        <para><emphasis role="bold">How to install MariaDB</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>Install the MariaDB official yum repository. Create a file
+            named <literal>mariadb.repo</literal> in
+            <literal>/etc/yum.repos.d/</literal> with the following
+            content:<programlisting># MariaDB 10.5 CentOS repository list - created 2021-02-16 08:46 UTC
+# http://downloads.mariadb.org/mariadb/repositories/
+[mariadb]
+name = MariaDB
+baseurl = http://yum.mariadb.org/10.5/centos7-amd64
+gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
+gpgcheck=1
+</programlisting></para>
+
+            <note>
+              <para>For more information about setting the repository, consult
+              <ulink
+              url="https://downloads.mariadb.org/mariadb/repositories/#mirror=nxtHost">Downloads
+              - Setting up MariaDB Repositories</ulink>.</para>
+            </note>
+          </listitem>
+
+          <listitem>
+            <para>Make sure the following packages are installed:</para>
+
+            <programlisting>MariaDB-compat-10.5.8-1.el7.centos.x86_64
+MariaDB-common-10.5.8-1.el7.centos.x86_64
+MariaDB-server-10.5.8-1.el7.centos.x86_64
+MariaDB-client-10.5.8-1.el7.centos.x86_64
+galera-4-26.4.6-1.el7.centos.x86_64</programlisting>
+
+            <para>These provide the MariaDB server, client and the Galera
+            <literal>wsrep</literal> provider library.</para>
+          </listitem>
+
+          <listitem>
+            <para>Copy the <literal>wsrep</literal> template:</para>
+
+            <programlisting>[root@localhost ~]# cp /usr/share/mysql/wsrep.cnf /etc/my.cnf.d
+            </programlisting>
+          </listitem>
+
+          <listitem>
+            <para>Change the following configuration in
+            <filename>/etc/my.cnf.d/wsrep.cnf</filename>:</para>
+
+            <programlisting># Full path to wsrep provider library or 'none'
+<emphasis role="bold">wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so</emphasis>
+
+# Provider specific configuration options
+#wsrep_provider_options=
+
+# Logical cluster name. Should be the same for all nodes.
+<emphasis role="bold">wsrep_cluster_name="ucpemanager"</emphasis>
+
+# Group communication system handle
+<emphasis role="bold">wsrep_cluster_address="gcomm://192.168.10.11,192.168.10.12,..,192.168.10.16"</emphasis>
+
+# Human-readable node name (non-unique). Hostname by default.
+<emphasis role="bold">wsrep_node_name=Node1</emphasis> # current node's name. set node name for each server in \
+the cluster
+
+# Base replication &lt;address|hostname&gt;[:port] of the node.
+# The values supplied will be used as defaults for state transfer receiving,
+# listening ports and so on. Default: address of the first network interface.\
+<emphasis role="bold">wsrep_node_address=192.168.10.11</emphasis> 
+#current node's interface IP . must be set for each node in the cluster</programlisting>
+
+            <note>
+              <para>Steps 2, 3 and 4 must be performed for each MariaDB node
+              in the cluster.</para>
+            </note>
+          </listitem>
+
+          <listitem>
+            <para>Bootstrap the first node in the cluster (referred to as
+            <literal>Node1</literal> in this example), by running:</para>
+
+            <programlisting>[root@localhost ~]# galera_new_cluster</programlisting>
+
+            <para>This script passes the
+            <literal>--wsrep-new-cluster</literal> to
+            <literal>mysqld</literal> which tells the node that there is no
+            pre-existing cluster to connect to. The node will create a new
+            UUID to identify the new cluster.</para>
+
+            <note>
+              <para>Do not execute this script when connecting to an existing
+              cluster. It will create a new UUID to identify the cluster
+              again, and the node won't reconnect to the old cluster.</para>
+            </note>
+          </listitem>
+
+          <listitem>
+            <para>Go to <literal>Node1</literal> and start the service:</para>
+
+            <programlisting>[root@localhost ~]# systemctl start mariadb</programlisting>
+
+            <para>Subsequently, start the service on the other servers.</para>
+          </listitem>
+
+          <listitem>
+            <para>Verify that the nodes have entered the cluster:</para>
+
+            <programlisting>[root@localhost ~]# mysql --host=localhost --user=root -p
+MariaDB [(none)]&gt; show status like 'wsrep_cluster_conf_%';
++-----------------------+-------+
+| Variable_name         | Value |
++-----------------------+-------+
+| wsrep_cluster_conf_id | 3     |
++-----------------------+-------+
+1 row in set (0.001 sec)</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>Run the initial configuration script (only once, on one of
+            the machines in the cluster):</para>
+
+            <programlisting>[root@localhost ~]# mysql_secure_installation
+
+Switch to unix_socket authentication [Y/n] <emphasis role="bold">Y</emphasis>
+Enabled successfully!
+Reloading privilege tables..
+ ... Success!
+&hellip;
+Change the root password? [Y/n] <emphasis role="bold">Y</emphasis>
+New password: 
+Re-enter new password: 
+Password updated successfully!
+Reloading privilege tables..
+ ... Success!
+&hellip;
+Remove anonymous users? [Y/n] <emphasis role="bold">Y</emphasis>
+ ... Success!
+&hellip;
+Disallow root login remotely? [Y/n] <emphasis role="bold">Y</emphasis>
+ ... Success!
+&hellip;
+Remove test database and access to it? [Y/n] <emphasis role="bold">Y (optional)</emphasis>
+ - Dropping test database...
+ ... Success!
+ - Removing privileges on test database...
+ ... Success!
+Reload privilege tables now? [Y/n] <emphasis role="bold">Y</emphasis>
+ ... Success!
+
+Cleaning up...
+
+All done!  If you've completed all of the above steps, your MariaDB
+installation should now be secure.
+
+Thanks for using MariaDB!</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>Create the initial database and grant access to it:</para>
+
+            <programlisting>[root@localhost application]# mysql --host=localhost --user=root -p
+MariaDB [(none)]&gt; CREATE DATABASE ucpemanager CHARACTER SET='utf8' \
+COLLATE='utf8_bin';
+Query OK, 1 row affected (0.004 sec)
+
+MariaDB [(none)]&gt; GRANT ALL PRIVILEGES ON ucpemanager.* \
+TO 'enea'@'%' IDENTIFIED BY 'somepassword' WITH GRANT OPTION;</programlisting>
+          </listitem>
+        </orderedlist>
+      </section>
+
+      <section id="ha_java_sdk_install">
+        <title>Installing the Java SDK</title>
+
+        <para>Please refer to <olink
+        targetdoc="book_enea_nfv_access_getting_started"
+        targetptr="openjdk_postgresql_config">Configuring OpenJDK and
+        PostgreSQL in the <xi:include
+        href="../../s_docbuild/olinkdb/pardoc-names.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+        Manual, for details on how to install and configure Java
+        OpenJDK.</para>
+
+        <para>Make sure the <literal>JAVA_HOME</literal> variable points to
+        the OpenJDK 11 installation:</para>
+
+        <programlisting>[root@localhost ~]# echo $JAVA_HOME
+/usr/lib/jvm/java-11-openjdk-11.0.10.0.9-0.el7_9.x86_64
+</programlisting>
+      </section>
+
+      <section id="ha_ucpe_mg">
+        <title>Installing the Enea Edge Management in High Availabilty
+        mode</title>
+
+        <para>These steps must be taken on each of the CentOS 7 machines that
+        will host the Enea Edge Management. The Enea Edge Management will be
+        installed and the setup for the external database cluster will be
+        prepared.</para>
+
+        <para>As the root user, go to the distribution folder of the Enea Edge
+        Management, and run:</para>
+
+        <programlisting>[root@localhost distro]#./install.sh /opt/ \
+Enea_NFV_Access_uCPEManager_2.3.0-build23.tar.gz
+This will install uCPEManager into /opt/ucpemanager folder.
+Select the following options, while asked by the installation script:
+Are you using the embedded PostgreSQL database? [Y/N]: <emphasis role="bold">N</emphasis>
+External database selected, getting user information ...
+Press 1 for PostgreSQL, 2 for MariaDB, 3 for SQL Server, 4 for Oracle and 5 \
+for MySQL: <emphasis role="bold">2</emphasis>
+Specify database server name(s) or IP Address(es): \
+<emphasis role="bold">192.168.10.11,192.168.10.12,&hellip;,192.168.10.16 *(see note)</emphasis>
+Specify database ID (or name) [ucpemanager]: 
+Specify database server port [3306]: 
+Specify database user name [root]: enea
+Specify database password [root]: somepassword
+Specify database startup thread pool size [1]: 
+Creating database configuration file \
+/opt//ucpemanager/application/config/databaseConfig.xml ...
+Done .
+&hellip;
+Installing ucpemanager service ..
+Specify service username [ucpemanager]: 
+Specify service password [ucpemanager]: somepassword
+&hellip;
+Specify the IP address of the local interface: <emphasis role="bold">192.168.10.11</emphasis>
+Is this server part of a cluster? [Y/N]: <emphasis role="bold">Y</emphasis>
+Specify the name of the cluster [ucpemanager]: 
+Specify the shared (virtual) cluster IP address: <emphasis role="bold">192.168.10.10</emphasis>
+Specify the netmask for the cluster IP address [255.255.255.0]: 
+HA Configuration files modified successfully.
+Configuration complete.</programlisting>
+
+        <note>
+          <para>For each Enea Edge Management installation, place the local
+          interface IP first in the list of IPs. This will optimize database
+          communication, since the Enea Edge Management uses the list of IPs
+          sequentially, therefore using the internal loopback interface for
+          communicating with the database.</para>
+        </note>
+
+        <para>Once the servers are up and running, log into the <emphasis
+        role="bold">Primary</emphasis> and go to <emphasis
+        role="bold">System</emphasis> and select <emphasis role="bold">Cluster
+        View</emphasis>. The list of Enea Edge Management servers should be
+        displayed, with one listed as Primary and the rest as Backup.</para>
+      </section>
+    </section>
+
+    <section id="ha_upgrade">
+      <title>Upgrading a High Availability Deployment</title>
+
+      <para>Upgrading a High Availabilty deployment is a highly complex,
+      multi-step process that requires care to ensure both consistency and
+      high-availability. Some steps need to be done manually.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>We start with the assumption that <literal>ucpeManager-1
+          </literal>is the "PRIMARY" server.</para>
+        </listitem>
+
+        <listitem>
+          <para>Shut down database services on one side of the network, for
+          example: MariaDB-4, MariaDB-5 and MariaDB-6.</para>
+        </listitem>
+
+        <listitem>
+          <para>Disconnect the network interfaces towards the VPN for machines
+          MariaDB-4, MariaDB-5 and MariaDB-6. This will prevent any attempts
+          at failover/synchronization.</para>
+        </listitem>
+
+        <listitem>
+          <para>Run the upgrade process on <literal>ucpeManager-3</literal>
+          and <literal>ucpeManager-4</literal>. This will upgrade the service
+          to the current release. Once the upgrade process completes, shutdown
+          the Enea Edge Management service on both machines.</para>
+        </listitem>
+
+        <listitem>
+          <para>Disconnect the <literal>ucpeManager-2</literal> machine from
+          the network (which will take MariaDB-2 offline as well). At this
+          point, only the "PRIMARY" server is running, this is the start of
+          the interval when we are susceptible to single-server
+          failure.</para>
+        </listitem>
+
+        <listitem>
+          <para>Shutdown the MariaDB-2 process and run the Enea Edge
+          Management upgrade process on <literal>ucpeManager-2</literal>. This
+          will upgrade the service to the current release. Once the upgrade
+          process completes, shutdown the Enea Edge Management service on the
+          machine.</para>
+        </listitem>
+
+        <listitem>
+          <para>Reconnect the network interfaces towards the VPN for MariaDB-4
+          (<literal>ucpeManager-3</literal>), MariaDB-5
+          (<literal>ucpeManager-4</literal>) and MariaDB-6
+          (<literal>ucpeManager-2</literal>). Restart database services on
+          MariaDB-2, MariaDB-4, MariaDB-5 and MariaDB-6. This will allow
+          database services on all machines to synchronize, any data that has
+          been modified during the upgrade process will be made
+          consistent.</para>
+        </listitem>
+
+        <listitem>
+          <para>Shutdown the "Primary" server
+          (<literal>ucpeManager-1</literal>). At this point, the service is no
+          longer available.</para>
+        </listitem>
+
+        <listitem>
+          <para>Start the Enea Edge Management services on
+          <literal>ucpeManager-2</literal>. This machine will come up as the
+          new "PRIMARY" with the upgraded software. As part of the startup
+          process, it will upgrade the database and perform any other
+          upgrade-related functionality.</para>
+        </listitem>
+
+        <listitem>
+          <para>At this point (once startup completes), service is available.
+          However, we are still susceptible to single-server failure.</para>
+        </listitem>
+
+        <listitem>
+          <para>Start the Enea Edge Management services on
+          <literal>ucpeManager-3</literal> and
+          <literal>ucpeManager-4</literal>. At this point, we are in
+          highly-available mode.</para>
+        </listitem>
+
+        <listitem>
+          <para>Upgrade the Enea Edge Management on
+          <literal>ucpeManager-1</literal> (the one that has been shut down).
+          Once that upgrade is complete and the service restarts, the entire
+          setup has been upgraded to the new version.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/book.xml b/doc/book-enea-edge-getting-started/doc/book.xml
new file mode 100644
index 0000000..f02f770
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/book.xml
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
+]>
+<book id="book_enea_edge_getting_started">
+  <title><trademark class="registered">Enea</trademark> Edge Getting Started</title>
+
+  <subtitle>Release Version
+         <xi:include href="../../s_doceneacommon/doc/eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
+         xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
+
+  <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
+
+  <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="introduction.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+                          
+  <xi:include href="installation_guide.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="upgrade_ena.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+                                
+  <xi:include href="advanced_configurations.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+                                
+  <xi:include href="net_config_options.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+                                
+  <xi:include href="vnf_mg.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="log_collector.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="grafana.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="troubleshooting.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
diff --git a/doc/book-enea-edge-getting-started/doc/grafana.xml b/doc/book-enea-edge-getting-started/doc/grafana.xml
new file mode 100644
index 0000000..05276ed
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/grafana.xml
@@ -0,0 +1,266 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="grafana">
+  <title>Using Grafana and InfluxDB</title>
+
+  <para>InfluxDB is essentially a time series database process that runs on a
+  server, while Grafana is a visualization tool for time series data. Grafana
+  is a very lightweight server-side application, and most of the monitoring
+  runs in a browser.</para>
+
+  <section id="telemetry_deployment">
+    <title>Deploying Grafana and InfluxDB</title>
+
+    <para>Grafana and InfluxDB can be deployed using images for Docker on
+    linux. These images are provided by Enea along with a deploy script and
+    predefined dashboards.</para>
+
+    <para>The Grafana and InfluxDB images can be deployed on the same machine
+    or on separate machines.</para>
+
+    <section id="prereq_deploy">
+      <title>Prerequisites for Deploying an Image</title>
+
+      <para>The following must be present in order to deploy an image:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>CentOS 7 Linux.</para>
+        </listitem>
+
+        <listitem>
+          <para>Docker for CentOS 7 installed on the machine and set to
+          <literal>autostart</literal> as a service.</para>
+        </listitem>
+
+        <listitem>
+          <para>Superuser rights on the CentOS 7 machine.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="deploy_steps">
+      <title>Deploying Grafana and InfluxDB</title>
+
+      <para>On the CentOS 7 server open a terminal, log into a bash shell with
+      the root account and perform the following:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Extract
+          <filename>Enea_Edge_Telemetry_Deploy_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</filename>.</para>
+
+          <para>The directory in which the archive will be unpacked will be
+          denoted as: <literal>&lt;Telemetry-installdir&gt;</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enter <literal>&lt;Telemetry-installdir&gt;</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Run the provided <filename>telemetry_deploy.sh</filename>
+          script.</para>
+        </listitem>
+
+        <listitem>
+          <para>When prompted, select what images you want to deploy.</para>
+
+          <para>If an image is already deployed, you will be prompted to
+          replace it.</para>
+        </listitem>
+
+        <listitem>
+          <para>During the InfluxDB deployment, you will be prompted to
+          provide a username and password. These must match the ones
+          configured in the Enea Edge Management for Telemetry.</para>
+
+          <note>
+            <para>Changing the InfluxDB username and password requires
+            redeploying the InfluxDB image.</para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>Verify the installation by running the command <literal>docker
+          ps -a</literal>. The Grafana and InfluxDB containers should be
+          present and have the status <literal>Up</literal>.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+
+  <section id="grafana_settings">
+    <title>Setting Grafana and InfluxDB parameters</title>
+
+    <para>Customizing InfluxDB and Grafana parameters can be done by selecting
+    <emphasis role="bold">System</emphasis>, then the <emphasis
+    role="bold">Configuration</emphasis> menu, accessing the <emphasis
+    role="bold">Properties</emphasis> tab, and clicking on the <emphasis
+    role="bold">Telemetry</emphasis> tab. The settings that can be changed are
+    listed in the table below:</para>
+
+    <table>
+      <title>Telemetry settings</title>
+
+      <tgroup cols="3">
+        <colspec align="left" colname="1" colwidth="1*" />
+
+        <colspec align="left" colname="2" colwidth="3*" />
+
+        <colspec align="left" colname="3" colwidth="1*" />
+
+        <tbody>
+          <row>
+            <entry><emphasis role="bold">Field name</emphasis></entry>
+
+            <entry><emphasis role="bold">Description</emphasis></entry>
+
+            <entry><emphasis role="bold">Default value</emphasis></entry>
+          </row>
+
+          <row>
+            <entry>Grafana Hostname or IP Address</entry>
+
+            <entry>The hostname or IP address where the Grafana instance is
+            installed.</entry>
+
+            <entry>no default</entry>
+          </row>
+
+          <row>
+            <entry>Grafana Port</entry>
+
+            <entry>The port Grafana uses.</entry>
+
+            <entry>3000</entry>
+          </row>
+
+          <row>
+            <entry>Grafana Dashboard</entry>
+
+            <entry>The dashboard that should be used when opening Grafana
+            using the Enea Edge Management.</entry>
+
+            <entry>host</entry>
+          </row>
+
+          <row>
+            <entry>InfluxDB Hostname or IP Address</entry>
+
+            <entry>The hostname or IP address where the InfluxDB database is
+            installed.</entry>
+
+            <entry>no default</entry>
+          </row>
+
+          <row>
+            <entry>InfluxDB Port</entry>
+
+            <entry>The port used for communication between InfluxDB and the
+            Telemetry server.</entry>
+
+            <entry>25826</entry>
+          </row>
+
+          <row>
+            <entry>InfluxDB Username</entry>
+
+            <entry>The username used for encrypting communication between
+            InfluxDB and the Telemetry server.</entry>
+
+            <entry>admin0</entry>
+          </row>
+
+          <row>
+            <entry>InfluxDB Password</entry>
+
+            <entry>The password used for encrypting communication between
+            InfluxDB and the Telemetry server.</entry>
+
+            <entry>admin</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <para>When changing any of the settings in the <emphasis
+    role="bold">Telemetry</emphasis> tab, the Enea Edge Management will inform
+    all uCPE devices of the change if they have telemetry running.</para>
+
+    <figure>
+      <title>Telemetry Properties</title>
+
+      <mediaobject>
+        <imageobject>
+          <imagedata contentwidth="615"
+                     fileref="images/telemetry_settings.png" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+  </section>
+
+  <section id="telemetry_start_stop">
+    <title>Starting and stopping Telemetry</title>
+
+    <para>When a uCPE Device is selected, in the <emphasis
+    role="bold">Operations</emphasis> menu, the <emphasis role="bold">Start
+    Telemetry</emphasis> and <emphasis role="bold">Stop Telemetry</emphasis>
+    options are available.</para>
+
+    <para>When starting Telemetry for a uCPE device, the Enea Edge Management
+    sends the following information about the InfluxDB:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The IP address and hostname where InfluxDB is installed.</para>
+      </listitem>
+
+      <listitem>
+        <para>The port used for communication between InfluxDB and the
+        Telemetry server.</para>
+      </listitem>
+
+      <listitem>
+        <para>The credentials used for encrypting communication between
+        InfluxDB and the Telemetry server.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>These fields are read-only and are populated with the values already
+    set in the <emphasis role="bold">System Configuration</emphasis>. If one
+    of the fields is not set or if it does not have the desired value, modify
+    it in the <emphasis role="bold">System Configuration</emphasis>. The
+    password is sent encrypted using the Base64 scheme.</para>
+
+    <figure>
+      <title>Telemetry Start Dialog</title>
+
+      <mediaobject>
+        <imageobject>
+          <imagedata contentwidth="615" fileref="images/telemetry_start.png" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <para>When the Telemetry status is changed on a uCPE device, a
+    notification is sent to the Enea Edge Management. These notifications can
+    be inspected under <emphasis role="bold">Fault</emphasis> found in the
+    <emphasis role="bold">Event</emphasis> menu.</para>
+  </section>
+
+  <section id="grafana_launch">
+    <title>Launching Grafana</title>
+
+    <para>When a uCPE Device is selected, the <emphasis
+    role="bold">Telemetry</emphasis> button is available. Pressing this button
+    will open a new window pointing to Grafana. The current uCPE device will
+    be selected in Grafana.</para>
+
+    <para>The hostname or IP Address and the port of the Grafana installation
+    can be customized by selecting <emphasis role="bold">System</emphasis>,
+    then the <emphasis role="bold">Configuration</emphasis> menu, accessing
+    the <emphasis role="bold">Properties</emphasis> tab, and clicking on the
+    <emphasis role="bold">Telemetry</emphasis> tab. The default dashboard
+    available when launching Grafana can be customized as well.</para>
+  </section>
+</chapter>
diff --git a/doc/book-enea-edge-getting-started/doc/images/archive_list.png b/doc/book-enea-edge-getting-started/doc/images/archive_list.png
new file mode 100755
index 0000000..302f32d
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/archive_list.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png b/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png
new file mode 100755
index 0000000..6582737
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/debug_settings.png b/doc/book-enea-edge-getting-started/doc/images/debug_settings.png
new file mode 100755
index 0000000..2c97b2c
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/debug_settings.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png b/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png
new file mode 100755
index 0000000..a4a4f5c
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/download_files.png b/doc/book-enea-edge-getting-started/doc/images/download_files.png
new file mode 100755
index 0000000..cb686e4
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/download_files.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/edit_inter.png b/doc/book-enea-edge-getting-started/doc/images/edit_inter.png
new file mode 100755
index 0000000..fddde37
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/edit_inter.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png b/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png
new file mode 100755
index 0000000..f9ab8aa
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/fault_events.png b/doc/book-enea-edge-getting-started/doc/images/fault_events.png
new file mode 100755
index 0000000..aeec955
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/fault_events.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png b/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png
new file mode 100644
index 0000000..d119ecb
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png b/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png
new file mode 100755
index 0000000..da52202
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png b/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png
new file mode 100755
index 0000000..0b3ec54
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png b/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png
new file mode 100755
index 0000000..2db2487
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/prep_execution.png b/doc/book-enea-edge-getting-started/doc/images/prep_execution.png
new file mode 100755
index 0000000..404760b
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/prep_execution.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png b/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png
new file mode 100644
index 0000000..276b716
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png b/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png
new file mode 100644
index 0000000..81510b5
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/vnf_space.png b/doc/book-enea-edge-getting-started/doc/images/vnf_space.png
new file mode 100755
index 0000000..57ed581
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/vnf_space.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png b/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png
new file mode 100644
index 0000000..ee49fc1
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png
diff --git a/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png b/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png
new file mode 100644
index 0000000..b7c77bf
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png
diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
new file mode 100644
index 0000000..d9784a0
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
@@ -0,0 +1,1193 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="installation_guide">
+  <title>Setting up and Installing the Enea Edge Base Configuration</title>
+
+  <para>The setup and installation steps detailed below will deploy a base
+  configuration which will be used as a reference for more complex deployment
+  scenarios.</para>
+
+  <section id="hw_reqs">
+    <title>Hardware Requirements</title>
+
+    <para>The following hardware is needed for deploying the base
+    configuration:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>One server running the CentOS 7 distribution</para>
+
+        <note>
+          <para>The CentOS 7 server must be updated to the latest revision
+          before installing Enea Edge.</para>
+        </note>
+
+        <para>The following will detail CPU, RAM and storage requirements for
+        the Enea Edge Management.</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>For small-sized deployments (tens of devices):</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>4 cores</para>
+              </listitem>
+
+              <listitem>
+                <para>16 GB RAM</para>
+              </listitem>
+
+              <listitem>
+                <para>300 GB single disk storage</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>For mid-sized deployments (hundreds of devices):</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>8 cores</para>
+              </listitem>
+
+              <listitem>
+                <para>32 GB RAM</para>
+              </listitem>
+
+              <listitem>
+                <para>300 GB single disk storage</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>For large deployments (thousands of devices):</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>16 cores</para>
+              </listitem>
+
+              <listitem>
+                <para>64-256 GB RAM</para>
+              </listitem>
+
+              <listitem>
+                <para>1-2 TB single disk storage</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+        </itemizedlist>
+
+        <para>The purpose of the CentOS 7 server is to host the Enea Edge
+        Management. Network access between the CentOS 7 server and the uCPE
+        devices is required. The Enea Edge Management and the uCPE devices
+        will be connected on separate subnets to avoid inconsistencies.</para>
+      </listitem>
+
+      <listitem>
+        <para>One or more uCPE devices.</para>
+
+        <para>Whitebox devices where the Enea Edge Runtime will be installed,
+        containing a minimum of 2 cores and 4 GB RAM and at least two ethernet
+        ports that will be configured as WAN and LAN during deployment.</para>
+
+        <para>When hosting an entire solution including one or several network
+        services, the hardware must also have the resources to host one or
+        more VNFs. During a typical evaluation, a dual VNF service on the Enea
+        Edge Runtime needs a CPU with 4-8 cores and at least 8 GB RAM. The
+        supported Intel CPUs of Enea Edge are documented in the <xi:include
+        href="../../s_docbuild/olinkdb/pardoc-common.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(book_enea_nfv_access_release_info/1)" />
+        manual.</para>
+
+        <para>Enea Edge Runtime needs EFI support in BIOS to boot. When
+        configuring the uCPE device BIOS a serial connection is
+        required.</para>
+      </listitem>
+
+      <listitem>
+        <para>A laptop.</para>
+
+        <para>The laptop is used for 2 scenarios:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Installing the Enea Edge Runtime on uCPE Devices.</para>
+          </listitem>
+
+          <listitem>
+            <para>Connecting to the GUI of the Enea Edge Management for
+            management and configuration. Network access between the CentOS 7
+            server and the laptop is required. Please see the <xi:include
+            href="../../s_docbuild/olinkdb/pardoc-common.xml"
+            xmlns:xi="http://www.w3.org/2001/XInclude"
+            xpointer="element(book_enea_nfv_access_release_info/1)" /> manual
+            available with your release, for recommended browsers.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>A 16 GB USB stick used for the uCPE Device Installation.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="sw_config">
+    <title>Software Configuration</title>
+
+    <para>The CentOS 7 server requires a specific configuration for the setup
+    to work.</para>
+
+    <section id="firewall_config">
+      <title>Firewall Configuration</title>
+
+      <para>Any firewall running on the CentOS 7 server may block the
+      management protocols required to communicate between the uCPE device and
+      the Enea Edge Management as well as between the Enea Edge Management and
+      its northbound clients. Quick handling of a blocking firewall would be
+      to disable it, typical for a lab environment, through:</para>
+
+      <programlisting>sudo systemctl stop firewalld
+sudo systemctl disable firewalld
+sudo systemctl mask now firewalld</programlisting>
+
+      <para>For an advanced firewall configuration, the following ports need
+      to be opened:</para>
+
+      <table>
+        <title>Ports to be Activated</title>
+
+        <tgroup cols="3">
+          <colspec align="left" />
+
+          <tbody>
+            <row>
+              <entry>80</entry>
+
+              <entry>TCP</entry>
+
+              <entry>Required for GUI Access.</entry>
+            </row>
+
+            <row>
+              <entry>443</entry>
+
+              <entry>TCP</entry>
+
+              <entry>Required for GUI Access and Device Connectivity.</entry>
+            </row>
+
+            <row>
+              <entry>54327</entry>
+
+              <entry>UDP</entry>
+
+              <entry>Required for the Enea Edge Management High Availability
+              Configuration.</entry>
+            </row>
+
+            <row>
+              <entry>5701:5708</entry>
+
+              <entry>TCP</entry>
+
+              <entry>Required for the Enea Edge Management High Availability
+              Configuration.</entry>
+            </row>
+
+            <row>
+              <entry>4334</entry>
+
+              <entry>TCP</entry>
+
+              <entry>Required for Call Home.</entry>
+            </row>
+
+            <row>
+              <entry>2021:2040</entry>
+
+              <entry>TCP</entry>
+
+              <entry>Required for Call Home when connecting uCPE Devices using
+              Enea NFV Access 2.3.0 or older.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <para>Use the following command sequence to enable the required ports
+      for deployment of the Enea Edge Management:</para>
+
+      <programlisting>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 --reload</programlisting>
+
+      <note>
+        <para>If the Enea Edge Management host resides behind a corporate
+        port-filtering firewall, then all the aforementioned ports need to
+        also be enabled on the respective firewall. As an additional
+        requirement, port 22/TCP also needs to be enabled for reverse SSH to
+        the Enea Edge Management.</para>
+
+        <para>No enabling and no forwarding rules are necessary for ports
+        2021-2040 if using Enea Edge 2.4.0 or newer.</para>
+      </note>
+    </section>
+
+    <section id="openjdk_postgresql_config">
+      <title>Configuring OpenJDK and PostgreSQL</title>
+
+      <para>The Enea Edge Management requires a specific Java version (OpenJDK
+      11) and a PostgreSQL version to operate correctly.</para>
+
+      <para><emphasis role="bold">Installing OpenJDK</emphasis></para>
+
+      <orderedlist spacing="compact">
+        <listitem>
+          <para>Install OpenJDK 11 using the root account:</para>
+
+          <programlisting>yum install java-11-openjdk-devel</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Verify the installation:</para>
+
+          <programlisting>java -version
+openjdk version "11.0.3" 2019-04-16 LTS
+OpenJDK Run Time Environment 18.9 (build 11.0.3+7-LTS)
+OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7-LTS, mixed mode, sharing)</programlisting>
+
+          <note>
+            <para>If there are multiple java versions installed, switch
+            between them using the following command:</para>
+
+            <programlisting>alternatives --config java</programlisting>
+
+            <para>Optionally, the user can switch between the
+            <literal>javac</literal> versions using:</para>
+
+            <programlisting>alternatives --config javac</programlisting>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>The following system variables need to point to the OpenJDK 11
+          installation:</para>
+
+          <programlisting>export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which java)))))
+export PATH=$PATH:$JAVA_HOME/bin
+export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar</programlisting>
+
+          <note>
+            <para>In order to make these system variables persistent, the
+            commands given above should be added to a script in the
+            <literal>/etc/profile.d/</literal> folder. <emphasis
+            role="bold">Sudo</emphasis> access is needed for this
+            operation.</para>
+          </note>
+        </listitem>
+      </orderedlist>
+
+      <para>The Enea Edge Management requires a specific PostgreeSQL version.
+      This is embedded in the Enea Edge Management installation. In order to
+      avoid conflicts, any existing PostgreeSQL installation needs to be
+      uninstalled.</para>
+
+      <para><emphasis role="bold">Uninstalling PostgreSQL</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Open a terminal with administrative rights, i.e. log into a
+          bash shell with root privileges.</para>
+        </listitem>
+
+        <listitem>
+          <para>Execute the following command to check if you have a currently
+          running PostgreSQL database server:</para>
+
+          <programlisting>ps -ef | grep post</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Remove the installed PostgreSQL server (including the existing
+          postgres user):</para>
+
+          <note>
+            <para>This step is not necessary if the Enea Edge Management will
+            be using an external database (like MariaDB).</para>
+          </note>
+
+          <programlisting>yum remove postgres\*
+rm -rf /var/lib/pgsql
+rm -f /etc/postgres-reg.ini
+userdel postgres</programlisting>
+        </listitem>
+      </orderedlist>
+
+      <para>If you have multiple spindles, it is recommended to let the
+      application run off one and the database off the other. This will result
+      in optimum performance. It is also recommended that the swap disk be the
+      same as the one used for the application.</para>
+
+      <para>Assuming another spindle is used (<literal>/drive2</literal>) do
+      the following:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Create a folder which will host the database (e.g.
+          <literal>emsDatabase</literal>).</para>
+        </listitem>
+
+        <listitem>
+          <para>Create a soft-link that will point to this folder:</para>
+
+          <programlisting>ln -s /opt/ems/elementcenter/database /drive2/emsDatabase</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Follow the installation steps for the Enea Edge Management
+          available in <olink targetdoc="book_enea_nfv_access_getting_started"
+          targetptr="install_ucpe_mg">Installing the Enea Edge Management in
+          the <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+          Manual.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+
+  <section id="ucpe_config">
+    <title>uCPE Device Configuration</title>
+
+    <section id="wan_lan_ports">
+      <title>Determining the WAN and LAN ports</title>
+
+      <para>A typical whitebox comes with multiple physical network ports,
+      ready to be used. The user must determine the purpose and allocation of
+      each port. The allocation is later aligned with the software
+      configuration within the Web-installer.</para>
+
+      <para>A common way is to allocate the left ports to WANs and the right
+      ports to LANs. At least one port must be allocated to WAN and one to
+      LAN.</para>
+    </section>
+
+    <section id="ucpe_identifier">
+      <title>Determining the Device ID</title>
+
+      <para>Each uCPE device needs a unique identifier. This identifier is
+      used to match the registration in the Enea Edge Management and the
+      offline configuration of the uCPE device during ZTP (Zero Touch
+      Provisioning).</para>
+
+      <para>Select a text string to represent the uCPE device, e.g.
+      <literal>uCPE-1</literal> or <literal>fwa-t1012vc_boston_1234</literal>.
+      It can have any length and any type of characters with the exception of
+      quotation characters (' or ") or line terminators (\n or \r) which can
+      interfere with the JSON format of the
+      <filename>install_data.json</filename> file.</para>
+    </section>
+
+    <section id="bios_config">
+      <title>Configuring the BIOS</title>
+
+      <para>The factory configuration of the BIOS may not match the
+      requirements of Enea Edge Runtime. The BIOS configuration needs to be
+      reviewed and potentially reconfigured to prepare for a successful
+      installation.</para>
+
+      <para>Access the BIOS using a serial cable between the uCPE device and
+      the laptop, to review and configure the BIOS correctly. The whitebox
+      vendor is expected to provide the right serial cable for the box. A
+      terminal emulator (such as putty) is needed on the laptop.</para>
+
+      <para>Enable the following BIOS features/configurations:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>EFI</para>
+        </listitem>
+
+        <listitem>
+          <para>Intel Virtualization Technology (VT-x)</para>
+        </listitem>
+
+        <listitem>
+          <para>Intel Virtualization Technology for Directed I/O (VT-d)</para>
+        </listitem>
+
+        <listitem>
+          <para>SR-IOV</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>The boot order may also need to be modified to support
+      installation and execution of the Enea Edge Runtime on the uCPE
+      device.</para>
+
+      <para>The following boot order is recommended for a base
+      configuration:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Boot from USB</para>
+        </listitem>
+
+        <listitem>
+          <para>Boot from Disk</para>
+        </listitem>
+      </orderedlist>
+
+      <para>By arranging the above boot order there is no need for a further
+      configuration of the BIOS during installation and deployment.</para>
+    </section>
+  </section>
+
+  <section id="prep_deploy">
+    <title>Preparing the Deployment</title>
+
+    <section id="install_ucpe_mg">
+      <title>Installing the Enea Edge Management</title>
+
+      <para>The Enea Edge Management can be installed using a fresh
+      (first-time) configuration or using a backup file of a previous
+      installation, created within the Enea Edge Management GUI.</para>
+
+      <section id="fresh_ucpemg_install">
+        <title>Fresh Installation of the Enea Edge Management</title>
+
+        <para>On the CentOS 7 server open a terminal, log into a bash shell
+        with the root account and perform the following:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>Extract
+            <literal>Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</literal></para>
+
+            <para>The directory in which the archive has been unpacked will be
+            denoted as: <literal>&lt;uCPEM-installdir&gt;</literal>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Enter <literal>&lt;uCPEM-installdir&gt;/dist</literal>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Choose the target installation folder, e.g.
+            <literal>/opt/ems</literal>. Everything will be installed under a
+            folder called <literal>/ucpemanager</literal> within the target
+            installation folder.</para>
+
+            <para>The application files will be installed in
+            <literal>/opt/ems/ucpemanager/application</literal>. The database
+            will be installed in
+            <literal>/opt/ems/ucpemanager/database</literal>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Run the following interactive command:</para>
+
+            <programlisting>./install.sh /opt/ems \
+Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
+
+            <para>The default configuration values are specified in brackets.
+            If no other value is preferred and typed in, pressing
+            <literal>ENTER</literal> will keep the default values. When there
+            is an option within parentheses (i.e.Y/N), a value must be
+            specified.</para>
+
+            <note>
+              <para>The same configuration values set now will need to be
+              provided when upgrading or uninstalling the Enea Edge
+              Management.</para>
+            </note>
+
+            <itemizedlist>
+              <listitem>
+                <para>Database Configurations:</para>
+
+                <itemizedlist spacing="compact">
+                  <listitem>
+                    <para>Are you using the embedded PostgreSQL database?
+                    [Y/N]: <literal>Y</literal>.</para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify the database process password
+                    <literal>[postgres]:</literal></para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify the database ID (or name)
+                    <literal>[ucpemanager]:</literal></para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify the database server port
+                    <literal>[5432]:</literal></para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify a database user name
+                    <literal>[postgres]:</literal></para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify a database password
+                    <literal>[postgres]:</literal></para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify the database startup thread pool size
+                    <literal>[1]:</literal></para>
+                  </listitem>
+                </itemizedlist>
+              </listitem>
+
+              <listitem>
+                <para>Service Configurations:</para>
+
+                <itemizedlist spacing="compact">
+                  <listitem>
+                    <para>Specify a service username
+                    [<literal>ucpemanager</literal>]:</para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Specify a service password
+                    <literal>[ucpemanager</literal>]:</para>
+                  </listitem>
+                </itemizedlist>
+              </listitem>
+
+              <listitem>
+                <para>High Availability Configurations:</para>
+
+                <itemizedlist spacing="compact">
+                  <listitem>
+                    <para>Specify the IP address of the local interface: The
+                    CentOS 7 Server loopback address:
+                    <literal>127.0.0.1</literal>.</para>
+                  </listitem>
+
+                  <listitem>
+                    <para>Is this server part of a cluster? [Y/N]:
+                    <literal>N</literal>.</para>
+                  </listitem>
+                </itemizedlist>
+              </listitem>
+
+              <listitem>
+                <para>Heap Configuration: <literal>Please enter the new
+                Maximum Heap Size [4g]</literal>:</para>
+              </listitem>
+
+              <listitem>
+                <para>Create the self-signed certificate: <literal>Specify IP
+                or domain name:</literal></para>
+
+                <note>
+                  <para>The certificate can be generated again by running the
+                  <filename>createCertificate</filename> script from the
+                  distribution folder.</para>
+                </note>
+              </listitem>
+            </itemizedlist>
+
+            <para>This command will:</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>Extract the application files from the compressed
+                installation kit.</para>
+              </listitem>
+
+              <listitem>
+                <para>Install the bundled database.</para>
+              </listitem>
+
+              <listitem>
+                <para>Install the Enea Edge Management as a service with the
+                name <literal>ucpemanager</literal>.</para>
+              </listitem>
+
+              <listitem>
+                <para>Start the <literal>ucpemanager</literal> service</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>Using the IPv4 address of the CentOS 7 Server in a web
+            browser, running on the laptop, log into the Enea Edge Management
+            GUI using the default username and password:
+            <literal>admin/admin</literal>.</para>
+          </listitem>
+        </orderedlist>
+
+        <note>
+          <para>The IPv4 address of the CentOS 7 Server, connected to the same
+          network as the uCPE Devices, will be used as a configuration
+          parameter when setting up the uCPE devices.</para>
+
+          <para>If the CentOS 7 Server is installed behind NAT, the IPv4
+          address used will be the public IP of the NAT device and port
+          forwarding rules must be created to ensure the uCPE device can
+          access the Enea Edge Management. For more details, please see <link
+          linkend="firewall_config">Firewall Configuration</link>.</para>
+        </note>
+      </section>
+
+      <section id="install_ucpemg_from_backup">
+        <title>Installation of the Enea Edge Management using a System
+        Back-up</title>
+
+        <para>The Enea Edge Management can be restored if a backup file has
+        been previously created.</para>
+
+        <para>A backup file can be created by accessing the <emphasis
+        role="bold">System</emphasis> menu, and clicking <emphasis
+        role="bold">System Backup</emphasis>, from the Enea Edge Management
+        GUI. The resulting zip archive will be located in the
+        <filename>/opt/ems/ucpemanager/application/backup</filename> folder
+        and will be named
+        <literal>SystemBackup_MMMDD_YYYY_HHMM_SS.zip</literal> (e.g
+        System-Backup_Feb19_2013_2257_42.zip). Save the archive to another
+        location outside the Enea Edge Management installation folder for
+        future use.</para>
+
+        <note>
+          <para>The System Back-up file obtained from the Enea Edge Management
+          GUI (<filename>SystemBackup_MMMDD_YYYY_HHMM_SS.zip</filename>) is
+          different from the snapshot obtained during a Enea Edge Management
+          Upgrade or Uninstall operation
+          (<filename>ucpemanager-Backup-YYYYddMMHHmm.tar.gz</filename>) needed
+          for recovery of the Enea Edge Management. For more details, see
+          <olink targetdoc="book_enea_nfv_access_getting_started"
+          targetptr="restore_prev_ucpe_install">Restoring a previous Enea Edge
+          Management installation in the <xi:include
+          href="../../s_docbuild/olinkdb/pardoc-names.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+          Manual.</para>
+        </note>
+
+        <para>To install the Enea Edge Management with the restore option
+        provide an additional argument as shown below during
+        installation:</para>
+
+        <programlisting>./install.sh \
+/opt/ems Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz \
+SystemBackup_MMMDD_YYYY_HHMM_SS.zip</programlisting>
+      </section>
+    </section>
+
+    <section id="prep_usb_ena">
+      <title>Preparing the USB stick for installation of the Enea Edge
+      Runtime</title>
+
+      <para>To install the Enea Edge Runtime, create a bootable USB stick with
+      the image you intend to install.</para>
+
+      <para>In the example below, step by step instructions are provided for
+      the CentOS 7 distribution. It's possible with the appropriate tools to
+      also use Windows OS or MacOS.</para>
+
+      <note>
+        <para>The <filename>.hddimg</filename> image is available in the
+        <filename>Enea_Edge_Runtime_Platform_
+        &lt;processor&gt;_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</filename>
+        file you downloaded with your release.</para>
+      </note>
+
+      <para><emphasis role="bold">Create a bootable USB stick
+      image</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Copy the <filename>.hddimg</filename> image file provided by
+          Enea, into the CentOS 7 server.</para>
+        </listitem>
+
+        <listitem>
+          <para>Connect the USB stick to the CentOS 7 Server and identify the
+          USB device name given by the system with
+          <literal>lsblk</literal>:</para>
+
+          <programlisting>NAME    MAJ:MIN  RM   SIZE    RO  TYPE   MOUNTPOINT
+sda       8:0    1    28.7G   0   disk
+sdb       8:0    0    111.8G  0   disk
+|-sdb1    8:1    0    111.8G  0   part</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Copy the <filename>.hddimg</filename> image onto the USB
+          stick, e.g:</para>
+
+          <programlisting>sudo dd if=./enea-nfv-access-&lt;machine&gt;.hddimg \
+of=/dev/sdb bs=4M conv=fsync</programlisting>
+
+          <para>Where
+          <filename>enea-nfv-access-&lt;machine&gt;.hddimg</filename> is the
+          <filename>.hddimg</filename> file and <literal>sdb</literal> is the
+          assigned USB device name.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="prep_phys_deploy">
+      <title>Preparing Physical Deployment for Installation</title>
+
+      <figure>
+        <title>Preparing for Hardware Installation</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/prep_deploy.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>While the uCPE device is powered off, in order to install and
+      configure the Enea Edge Runtime (using the prepared USB stick), connect
+      the laptop to a uCPE device LAN port. For this purpose, a Layer 2 switch
+      or direct cable connection can be used.</para>
+    </section>
+
+    <section id="install_ena_device">
+      <title>Installing Enea Edge - uCPE Device Installation</title>
+
+      <para>To initiate the installation of the Enea Edge Runtime do the
+      following:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Plug the USB stick into the uCPE device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Power up the uCPE device and boot the USB stick.</para>
+        </listitem>
+
+        <listitem>
+          <para>The Web-installer application will start automatically and can
+          be accessed in a web browser on the laptop at
+          <literal>http://172.16.1.1</literal> (port 80).</para>
+        </listitem>
+
+        <listitem>
+          <para>On the <emphasis role="bold">Requirements</emphasis> page of
+          the Web-installer, the user must confirm the current state of
+          installation prerequisites is inline with the desired state:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Requirements table. Minimum values apply to the
+              installation process only. For runtime operations, additional
+              resources should be available depending on the specific
+              workload. Requirements are color coded (green when met, red when
+              mandatory and not met, orange when optional and not met). The
+              Requirements table has the following fields:</para>
+
+              <itemizedlist spacing="compact">
+                <listitem>
+                  <para>Disk size (mandatory). 2GB or more are required for
+                  the installation.</para>
+                </listitem>
+
+                <listitem>
+                  <para>CPU cores (mandatory). 2 cores or more are required
+                  for the installation.</para>
+                </listitem>
+
+                <listitem>
+                  <para>RAM (mandatory). 2GB or more are required for the
+                  installation.</para>
+                </listitem>
+
+                <listitem>
+                  <para>VT-x (mandatory). Intel Virtualization Technology must
+                  be enabled.</para>
+                </listitem>
+
+                <listitem>
+                  <para>VT-d (optional, recommended). Intel Virtualization
+                  Technology for Directed I/O should be enabled.</para>
+                </listitem>
+
+                <listitem>
+                  <para>IOMMU Group separation (optional). If the hardware
+                  does not support IOMMU Group separation, there are certain
+                  limitations regarding how the <literal>vfio-pci</literal>
+                  driver can be used. For more details, see the <olink
+                  targetdoc="book_enea_nfv_access_release_info"
+                  targetptr="bugs-limitations">Known Issues and Limitations in
+                  this Release in the <xi:include
+                  href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                  xmlns:xi="http://www.w3.org/2001/XInclude"
+                  xpointer="element(book_enea_nfv_access_release_info/1)" /></olink>
+                  Manual.</para>
+                </listitem>
+              </itemizedlist>
+            </listitem>
+
+            <listitem>
+              <para>Force installation checkbox. When enabled, the
+              installation can be performed even if some of the mandatory
+              requirements are not met or if non-fatal problems are detected
+              during the process.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>On the Enea <emphasis role="bold">Edge Management
+          settings</emphasis> page of the Web-installer, the user must fill
+          in:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>The static Enea Edge Management IP Address or FQDN. This can be
+              either:</para>
+
+              <itemizedlist spacing="compact">
+                <listitem>
+                  <para>The IP address of the Enea Edge Management host
+                  machine, if the device can directly access it.</para>
+                </listitem>
+
+                <listitem>
+                  <para>The IP address of the NAT device, if the Enea Edge
+                  Management host is located behind a NAT. For more details,
+                  please see <link linkend="firewall_config">Firewall
+                  Configuration</link>.</para>
+                </listitem>
+
+                <listitem>
+                  <para>The Fully Qualified Domain Name (FQDN) of the Enea
+                  uCPE Manager host machine.</para>
+                </listitem>
+              </itemizedlist>
+            </listitem>
+
+            <listitem>
+              <para>The unique identifier of the uCPE device (called
+              "DeviceId" in this guide).</para>
+            </listitem>
+
+            <listitem>
+              <para>Customer Tags. They are used for Zero Touch Provisioning
+              (ZTP) and can be left empty for a base configuration. What can
+              be entered here (if needed), are the tag(s) specified when
+              creating an offline configuration in the Enea Edge Management. A
+              later addition of customer tags can only be done by reinstalling
+              the uCPE devices.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Connect the WAN cable to the uCPE device (see Figure 2). This
+          will be used as the uCPE management network interface, as described
+          below.</para>
+        </listitem>
+
+        <listitem>
+          <para>On the <emphasis role="bold">Network Setup</emphasis> page of
+          the Web-installer, the user must do the following:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Select a WAN interface to use as the management network
+              interface. This interface is used by the Enea Edge Management to
+              communicate with the uCPE device.</para>
+            </listitem>
+
+            <listitem>
+              <para>Plug-in additional WAN interfaces (if applicable) and
+              provide their Layer 3 configuration.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+      </orderedlist>
+
+      <para>When the user has completed the configuration steps in the
+      Web-installer, Enea Edge Runtime is installed on the hard drive. At this
+      stage, the user should remove the USB stick and the LAN cable, and
+      shutdown the uCPE device. It will be started after necessary
+      configurations are done in the Enea Edge Management, as described
+      below.</para>
+
+      <note>
+        <para>If errors are detected during installation, full logs will be
+        available on the last page of the Web-installer. Please contact Enea
+        for log analysis. The system is not expected to be usable if errors are
+          reported during installation.</para>
+
+        <para>If the USB stick was booted in UEFI mode, a UEFI boot entry is
+        automatically created and the system will start booting from the hard
+        drive without further user configuration.</para>
+      </note>
+    </section>
+
+    <section id="prep_phys_exec">
+      <title>Preparing Physical Deployment for Execution</title>
+
+      <figure>
+        <title>Preparing for Deployment Execution</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/prep_execution.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>The following network configuration is needed for managing the
+      uCPE device and service deployment:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Network connection between the server running the Enea Edge
+          Management and the laptop.</para>
+        </listitem>
+
+        <listitem>
+          <para>Network connection between the server running the Enea Edge
+          Management and the uCPE device.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+  </section>
+
+  <section id="mg_ucpe_devices">
+    <title>Management of uCPE Devices</title>
+
+    <para>When the installation is complete the uCPE device can be managed in
+    the Enea Edge Management.</para>
+
+    <section id="add_offline_config">
+      <title>Add a default Offline Configuration</title>
+
+      <para>Zero Touch Provisioning is always turned on when a uCPE device
+      connects to the Enea Edge Management. To enable it in the Enea Edge
+      Management, an offline configuration needs to be registered for Day-0
+      configuration.</para>
+
+      <note>
+        <para>Day-0 configuration is a software lifecycle term referring to
+        early configurations used to put the uCPE device in an active state.
+        Day-1 Configurations are applied after Day-0 and set the uCPE device
+        and its service in an active state. Day-2 Configurations are live
+        configurations on the uCPE device and its service, applied after they
+        have been activated.</para>
+      </note>
+
+      <para>The offline configuration consists of data and parameters that are
+      meant to be automatically set when a uCPE device connects to the Enea
+      Edge Management for the first time. The configuration is typically
+      focused on setting up the network management of the uCPE device, e.g.
+      configuring network interfaces, WAN and LAN networking and service
+      chains.</para>
+
+      <para>For this base configuration, the offline configuration will be
+      left blank. The blank offline configuration can be filled with
+      user-specific values and data once the service is created, which is done
+      after the installation is complete.</para>
+
+      <note>
+        <para>If the offline configuration is not configured, an alarm will be
+        raised: <literal>Day-0 Config:ZTP:Major</literal> when the uCPE device
+        tries to connect to the Enea Edge Management, informing the user that
+        the ZTP setup failed for the uCPE device.</para>
+      </note>
+
+      <para><emphasis role="bold">To create an offline
+      configuration</emphasis><orderedlist>
+          <listitem>
+            <para>In a browser access the Enea Edge Management, open <emphasis
+            role="bold">Applications</emphasis> and select <emphasis
+            role="bold">Offline Config</emphasis>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Create a new offline configuration in the GUI by selecting
+            the <emphasis role="bold">Add</emphasis> button and filling in the
+            mandatory fields: <literal>name</literal>,
+            <literal>deviceVersion</literal> and
+            <literal>deviceId</literal>.</para>
+
+            <para>The name is user defined and can be set to any unique text
+            string identifying the configuration. The
+            <literal>deviceVersion</literal> must match the Enea Edge Runtime
+            version of the uCPE device and the <literal>deviceId</literal>
+            must be the previously set identifier of the uCPE device
+            (DeviceId).</para>
+          </listitem>
+        </orderedlist></para>
+    </section>
+
+    <section id="add_ucpe_mg">
+      <title>Add a uCPE device to the Management System</title>
+
+      <para>In order to enroll a uCPE device in the management system and
+      establish a management connection, the user will add uCPE device
+      information in the Enea Edge Management. This is accomplished by going
+      to <emphasis role="bold">Devices</emphasis>, selecting <emphasis
+      role="bold">Manage</emphasis> and then clicking the <emphasis
+      role="bold">Add</emphasis> button.</para>
+
+      <para>The relevant parameters are:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">Type.</emphasis> The type of device to
+          be added, i.e Enea universal CPE.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Name.</emphasis> The name by which the
+          uCPE device is referred to in the Enea Edge Management.
+          (Mandatory).</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">SSH Port.</emphasis> The NETCONF Port
+          used for communications. Default is set to 830.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">SSH User Name.</emphasis> The user name
+          for SSH connectivity. Default user is root.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">SSH Password.</emphasis> Leave this
+          blank.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Device Calls Home.</emphasis> This
+          checkbox indicates the direction of uCPE device communications. For
+          a base configuration, leave this flag unchecked.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Device ID.</emphasis> The unique
+          identifier of the uCPE device. (Mandatory).</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>For more details concerning Device Calls Home, please see <olink
+      targetdoc="book_enea_nfv_access_getting_started"
+      targetptr="device_callhome_nat">Device Call Home Connection for
+      Deployment behind NAT in the <xi:include
+      href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+      Manual.</para>
+    </section>
+
+    <section id="boot_device_add_map">
+      <title>Booting the uCPE device and adding it to the Map</title>
+
+      <para>When connectivity is established with the Enea Edge Management and
+      a uCPE device is already registered with a matching <literal>Device
+      ID</literal>, the installation is complete, and the connection is
+      established.</para>
+
+      <para>When a uCPE device is registered it can be manually added to the
+      map for overview. <emphasis role="bold">Right-click</emphasis> on the
+      map and select <emphasis role="bold">Place Device</emphasis> to put the
+      uCPE device on the map.</para>
+
+      <para>In case of management connection failure (e.g. due to a
+      misconfiguration), the uCPE device status will be seen as RED
+      (disconnected) in the Enea Edge Management. The uCPE device
+      configuration can be corrected by removing the WAN cable(s),
+      reconnecting the laptop to the LAN interface of the uCPE device and
+      rebooting it. At this point, the Web-installer can be accessed from the
+      laptop as described in <olink
+      targetdoc="book_enea_nfv_access_getting_started"
+      targetptr="install_ena_device">Installing Enea Edge - uCPE Device
+      installation in the <xi:include
+      href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+      Manual.</para>
+    </section>
+  </section>
+
+  <section id="ucpe_monitor">
+    <title>uCPE Device Monitorization and Control</title>
+
+    <para>Once the uCPE device is connected to the Enea Edge Management, it is
+    ready for central management. Two important functions available in the
+    Enea Edge Management GUI are alarm checking and resource
+    allocation.</para>
+
+    <section id="check_alarms">
+      <title>Checking Alarms</title>
+
+      <para>The Enea Edge Management dashboard presents alarms in a specific
+      window on the front page.</para>
+
+      <para>An alarm can be easily triggered by disconnecting and reconnecting
+      the WAN ethernet cable from the uCPE device. The management system will
+      detect the broken link and raise an alarm: <literal>Device
+      Disconnected::Critical</literal>.</para>
+
+      <para>A separate Alarm Management window can be accessed from the Enea
+      Edge Management menu for in-depth access and programming of Alarms and
+      Events.</para>
+    </section>
+
+    <section id="ck_resource_alloc">
+      <title>Checking uCPE device Resource Allocation</title>
+
+      <para>When the uCPE device is connected to the Enea Edge Management it
+      is of interest to check the amount of hardware resources in use.</para>
+
+      <para>To check CPU, RAM and disk utilization simply select the uCPE
+      device and go to the <emphasis role="bold">Virtual Machines</emphasis>
+      tab in the map view. The same view will show active VNFs running on the
+      uCPE device once instantiated.</para>
+    </section>
+
+    <section id="access_device_cli">
+      <title>Accessing the uCPE device CLI</title>
+
+      <para>As a final check to make sure the uCPE device was installed and
+      configured correctly, access the uCPE device Linux CLI by selecting the
+      uCPE device on the map and using the <emphasis role="bold">SSH
+      button</emphasis> from the panel. A new window will appear for CLI
+      access. The default user and password are <literal>root</literal> and
+      blank, respectively.</para>
+
+      <para>This is a pure Linux CLI providing access to standard Linux CLI
+      commands. The CLI is a central feature for running custom
+      scripting.</para>
+
+      <note>
+        <para>In case the uCPE device was installed behind a NAT device, the
+        reverse SSH connection will be used. For more details, please see
+        <olink targetdoc="book_enea_nfv_access_getting_started"
+        targetptr="device_callhome_nat">Device Call Home Connection for
+        deployment behind NAT in the <xi:include
+        href="../../s_docbuild/olinkdb/pardoc-names.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+        Manual.</para>
+      </note>
+    </section>
+  </section>
+</chapter>
diff --git a/doc/book-enea-edge-getting-started/doc/introduction.xml b/doc/book-enea-edge-getting-started/doc/introduction.xml
new file mode 100644
index 0000000..4dec1e1
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/introduction.xml
@@ -0,0 +1,264 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="intro_ucpe">
+  <title>Overview</title>
+
+  <para>This document describes the Enea Edge and provides installation
+  steps for deploying a base configuration in order to create:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>A functional Enea Edge Management installation ready to manage uCPE
+      devices.</para>
+    </listitem>
+
+    <listitem>
+      <para>One or several managed uCPE devices, ready to host network
+      services, using one wired WAN and one wired LAN connection.</para>
+    </listitem>
+  </itemizedlist>
+
+  <para>Extended deployment and configuration options are also detailed in the
+  following chapters.</para>
+
+  <section id="ena_solution">
+    <title>Enea Edge</title>
+
+    <para>Enea Edge for universal Customer Premise Equipment (uCPE) is a
+    virtualization and management platform, which allows end-users to onboard,
+    instantiate, and run third-party VNFs onto their systems. It is comprised
+    of two major components working in close cooperation:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The Enea Edge Runtime, which acts as the host
+        for Virtualized Network Functions (VNFs) and provides management over
+        NETCONF.</para>
+      </listitem>
+
+      <listitem>
+        <para>The Enea Edge Management, a solution that runs on an external
+        server, used for VNF Management and managing large numbers of uCPE
+        devices.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>In addition, Enea Edge includes a framework for
+    automation and testing. More information can be found in
+    <xi:include href="../../s_docbuild/olinkdb/pardoc-common.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_auto_fw_user_guide/1)" />.</para>
+
+    <para>Details concerning release content, including documentation
+    structure, are provided in the <xi:include
+    href="../../s_docbuild/olinkdb/pardoc-common.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_release_info/1)" /> manual included
+    with your release.</para>
+
+    <section id="nfv_access">
+      <title>Enea Edge Runtime</title>
+
+      <para>Enea Edge Runtime 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
+      functionalties and technologies.</para>
+
+      <para>Virtualization methods include Virtual Machines (KVM / QEMU) and
+      container(s) (Docker). High networking throughput and low latency are
+      ensured by accelerated data plane relying on technologies like DPDK,
+      OVS-DPDK and SR-IOV/PCI-Passthrough. Key functionalities, such as
+      platform software management, virtualized networking, VNFs life-cycle
+      management and FCAPS are provided through the YANG-modelled NETCONF
+      protocol.</para>
+
+      <figure>
+        <title>VNF Space</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" contentwidth="600"
+                       fileref="images/vnf_space.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+
+    <section id="ucpe_manager">
+      <title>Enea Edge Management</title>
+
+      <para>The Enea Edge Management is centralized control system providing
+      uCPEs domain management capabilities through a GUI and REST API. It can
+      be deployed on a host or a virtual machine running 64-bit CentOS 7 on an
+      x86 platform. The Enea Edge Management uses a southbound NETCONF protocol
+      to connect and manage uCPE devices.</para>
+
+      <para>The Enea Edge Management provides the following key features:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Enea Edge Runtime Software Management</para>
+        </listitem>
+
+        <listitem>
+          <para>VNF Onboarding</para>
+        </listitem>
+
+        <listitem>
+          <para>VNF Management</para>
+        </listitem>
+
+        <listitem>
+          <para>FCAPS</para>
+        </listitem>
+
+        <listitem>
+          <para>Zero Touch Provisioning</para>
+        </listitem>
+
+        <listitem>
+          <para>Alarms / Events management and monitoring</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+  </section>
+
+  <section id="def_and_acr">
+    <title>Definitions and Acronyms</title>
+
+    <section id="definitions">
+      <title>Definitions</title>
+
+      <table>
+        <title>Definitions</title>
+
+        <tgroup cols="2">
+          <colspec align="left" colname="1" colwidth="1*" />
+
+          <colspec align="left" colname="2" colwidth="3*" />
+
+          <tbody>
+            <row>
+              <entry>Enea Edge</entry>
+
+              <entry>The Enea Edge Runtime and the Enea Edge
+              Management.</entry>
+            </row>
+
+            <row>
+              <entry>Enea Edge Runtime</entry>
+
+              <entry>A lightweight, multi-architecture virtualization
+              platform, supporting Virtual Machines.</entry>
+            </row>
+
+            <row>
+              <entry>Enea Edge Management</entry>
+
+              <entry>Enea Universal Customer Premises Equipment
+              Manager.</entry>
+            </row>
+
+            <row>
+              <entry>uCPE device</entry>
+
+              <entry>A whitebox running the Enea Edge
+              Runtime.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
+
+    <section id="acronyms">
+      <title>Acronyms</title>
+
+      <table>
+        <title>Acronyms</title>
+
+        <tgroup cols="2">
+          <colspec align="left" colname="1" colwidth="1*" />
+
+          <colspec align="left" colname="2" colwidth="3*" />
+
+          <tbody>
+            <row>
+              <entry>API</entry>
+
+              <entry>Application Programming Interface.</entry>
+            </row>
+
+            <row>
+              <entry>DPDK</entry>
+
+              <entry>Data Plane Development Kit.</entry>
+            </row>
+
+            <row>
+              <entry>EFI</entry>
+
+              <entry>Extensible Firmware Interface.</entry>
+            </row>
+
+            <row>
+              <entry>FCAPS</entry>
+
+              <entry>Fault-management, Configuration, Accounting, Performance
+              and Security.</entry>
+            </row>
+
+            <row>
+              <entry>NETCONF</entry>
+
+              <entry>Network Configuration Protocol.</entry>
+            </row>
+
+            <row>
+              <entry>NFV</entry>
+
+              <entry>Network Functions Virtualization.</entry>
+            </row>
+
+            <row>
+              <entry>OVS</entry>
+
+              <entry>Open vSwitch.</entry>
+            </row>
+
+            <row>
+              <entry>UEFI</entry>
+
+              <entry>Unified Extensible Firmware Interface.</entry>
+            </row>
+
+            <row>
+              <entry>SR-IOV</entry>
+
+              <entry>Single Root Input/Output Virtualization.</entry>
+            </row>
+
+            <row>
+              <entry>PCI</entry>
+
+              <entry>Peripheral Component Interconnect.</entry>
+            </row>
+
+            <row>
+              <entry>REST</entry>
+
+              <entry>Representational State Transfer.</entry>
+            </row>
+
+            <row>
+              <entry>VNF</entry>
+
+              <entry>Virtual Network Function.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/log_collector.xml b/doc/book-enea-edge-getting-started/doc/log_collector.xml
new file mode 100644
index 0000000..baa1340
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/log_collector.xml
@@ -0,0 +1,401 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="log_collector">
+  <title>Using the Log Collector</title>
+
+  <para>Troubleshooting problems on the uCPE device require an analysis of a
+  set of information i.e. logs collected from the uCPE device and/or the Enea
+  Edge Management. The following information describes how the log collection
+  mechanism works.</para>
+
+  <section id="log_collect_ucpem">
+    <title>Log collecting using the Enea Edge Management</title>
+
+    <para>The Enea Edge Management allows for collecting a set of logs and state
+    information from a uCPE device.</para>
+
+    <section id="log_collect">
+      <title>Collecting the Logs</title>
+
+      <para>Collect the necessary log files and system details, then create an
+      archive (a tar file) on the uCPE device in the
+      <filename>/var/odm/log/archives</filename> folder:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access <emphasis role="bold">Operations</emphasis> and then
+          select <emphasis role="bold">Collect Debug Logs</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Provide a file name in the new window.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">Execute</emphasis> button.</para>
+
+          <para>A success message is shown in the same window as shown below.
+          At this moment, the process of collecting logs on the uCPE device
+          starts.</para>
+        </listitem>
+
+        <figure>
+          <title>Collecting Debug Logs</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" contentwidth="500"
+                         fileref="images/collect_debug_logs.png" />
+            </imageobject>
+          </mediaobject>
+        </figure>
+      </orderedlist>
+
+      <note>
+        <para>It might take some time for the archive to be created. When the
+        operation completes, a "CollectLogsComplete" notification is sent from
+        the uCPE device to the Enea Edge Management. This can be viewed in the
+        GUI in the <emphasis role="bold">Faults</emphasis> menu, after selecting 
+<emphasis role="bold">Events</emphasis>.</para>
+
+        <figure>
+          <title>Collecting Debug Logs</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" contentwidth="500"
+                         fileref="images/fault_events.png" />
+            </imageobject>
+          </mediaobject>
+        </figure>
+      </note>
+    </section>
+
+    <section id="view_logs">
+      <title>View collected Logs</title>
+
+      <para>A list with the archives containing already collected logs will be
+      shown in the <emphasis role="bold">Device File Listing</emphasis> table:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access <emphasis role="bold">Files</emphasis> and then the 
+<emphasis role="bold">Download</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">List</emphasis> button.</para>
+
+          <figure>
+            <title>Device File Listing Table</title>
+
+            <mediaobject>
+              <imageobject>
+                <imagedata align="center" contentwidth="500"
+                           fileref="images/archive_list.png" />
+              </imageobject>
+            </mediaobject>
+          </figure>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>If the filename you specified does not appear, it might still be
+        in the process of creation. Click on the <emphasis role="bold">Refresh</emphasis> 
+        icon at the bottom of the table until you can see the desired file
+        listing.</para>
+      </note>
+    </section>
+
+    <section id="download_fr_dev">
+      <title>Downloading Logs from the uCPE Device</title>
+
+      <para>This option transfers a debug file archive from the uCPE device to
+      Enea Edge Management.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access <emphasis role="bold">Files</emphasis> and choose the 
+          <emphasis role="bold">Download</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">List</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <emphasis role="bold">Device File Listing</emphasis> table, select
+          the archive you want to download from the uCPE device to Enea Edge
+          Management.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">Download from Device</emphasis> 
+          button.</para>
+
+          <para>The archive will be downloaded from the uCPE device and stored
+          on the Enea Edge Management.</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>The archive will not be deleted from the uCPE device after
+        download.</para>
+      </note>
+    </section>
+
+    <section id="download_logs_locally">
+      <title>Downloading collected Logs locally</title>
+
+      <para>This option downloads a logs archive from the Enea Edge Management to
+      a local (user) machine for analysis. The archive must first be available
+      in the Enea Edge Management in order to be downloaded.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu and select 
+<emphasis role="bold">Files</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the <emphasis role="bold">Downloaded Files</emphasis> tab.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select an archive from the <emphasis role="bold">Downloaded Files</emphasis> 
+          table.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">Download</emphasis> button.</para>
+
+          <para>The file will be downloaded in browser's download
+          folder.</para>
+
+          <figure>
+            <title>Downloaded Files Table</title>
+
+            <mediaobject>
+              <imageobject>
+                <imagedata align="center" contentwidth="500"
+                           fileref="images/download_files.png" />
+              </imageobject>
+            </mediaobject>
+          </figure>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="delete_log_archive_dev">
+      <title>Deleting a Logs Archive from a uCPE device</title>
+
+      <para>Use this option when you want to delete unnecessary collected logs
+      on the uCPE device.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access <emphasis role="bold">Files</emphasis> and then click the 
+          <emphasis role="bold">Download</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">List</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <emphasis role="bold">Device File Listing</emphasis> table, select
+          the archive you want to delete from the uCPE device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">Delete</emphasis> button.</para>
+
+          <para>The archive will be deleted from the uCPE device and the table
+          will be updated.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>The same can be achieved using these alternative options:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Operations</emphasis> menu and 
+select <emphasis role="bold">Delete Debug Log Archive</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Provide a file name in the new window.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press the <emphasis role="bold">Execute</emphasis> button.</para>
+
+          <para>A success message is displayed if the file is deleted from the
+          uCPE device correctly.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="delete_archives_ucpem">
+      <title>Deleting a Logs Archive from the Enea Edge Management</title>
+
+      <para>This option deletes a logs archive from the Enea Edge
+      Management.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu, then select 
+          <emphasis role="bold">Files</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the <emphasis role="bold">Downloaded Files</emphasis> tab.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select an archive from the <emphasis role="bold">Downloaded Files</emphasis> 
+table.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">Delete</emphasis> button.</para>
+
+          <para>The file will be deleted from the Enea Edge Management and the
+          table will be updated.</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>Deleting the logs file from the Enea Edge Management does not
+        affect the file located on the uCPE device.</para>
+      </note>
+    </section>
+
+    <section condition="hidden" id="enable_disable_via_perms">
+      <title>Enabling/Disabling of the Log Collector via Permissions</title>
+
+      <para>To disable the ability to access/download the uCPE device's
+      debug-log files from the Enea Edge Management, the appropriate permissions
+      must be changed:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Security</emphasis> menu, 
+then select <emphasis role="bold">Configuration</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">Security Groups</emphasis> tab.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the desired group.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">Permissions</emphasis> tab on the right
+          side.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">Devices</emphasis> tab like in the image
+          below.</para>
+        </listitem>
+
+        <listitem>
+          <para>Change the <emphasis role="bold">Device File Management</emphasis> option to
+          <emphasis role="bold">none</emphasis> to disable the feature.</para>
+        </listitem>
+      </orderedlist>
+
+      <figure>
+        <title>Device File Management</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" contentwidth="500"
+                       fileref="images/dev_file_mg.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+
+    <section id="download_ucpemg_logs">
+      <title>Downloading Enea Edge Management Logs</title>
+
+      <para>Often, sending the Enea Edge Management logs together with collected
+      uCPE device logs to the support team provides important information for
+      troubleshooting (especially in cases of connectivity issues with the
+      uCPE device and error popups).</para>
+
+      <para>Enea Edge Management log files are located in
+      <filename>application/logs/</filename> in the Enea Edge Management's
+      installation folder
+      (e.g.<filename>/opt/ems/ucpemanager/application/logs</filename>). They
+      can be copied from that location, or they can be downloaded using the
+      Enea Edge Management GUI by performing the following:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access <emphasis role="bold">Test</emphasis>, then <emphasis role="bold">Debug
+          Settings</emphasis> and select the <emphasis role="bold">Log Files</emphasis> tab.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the desired log file
+          (<filename>ucpemanager.log</filename> or
+          <filename>watchdog.log</filename>) and press the
+          <emphasis role="bold">Download</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>A new (blank) popup window opens and the file is downloaded
+          locally. This popup can be closed after the download.</para>
+        </listitem>
+
+        <listitem>
+          <para>Repeat steps 2. And 3. Until all the desired log files have
+          been downloaded</para>
+        </listitem>
+      </orderedlist>
+
+      <figure>
+        <title>Debug Settings</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" contentwidth="500"
+                       fileref="images/debug_settings.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+  </section>
+
+  <section id="log_collect_no_ucpem">
+    <title>Log collecting without using the Enea Edge Management</title>
+
+    <para>Log collection from uCPE Devices can also be done when there is no
+    Enea Edge Management connection. A SSH connection to uCPE Device is needed
+    for use of the log collector script, which can be found in the uCPE Device
+    file system in <literal>/usr/local/enea/</literal>.</para>
+
+    <para>The Log collector script takes relevant information about the system
+    and collects it in an archive:</para>
+
+    <programlisting>./log-collector.sh -p &lt;LOG_PATHh&gt; -n &lt;ARCHIVE_NAME&gt;</programlisting>
+
+    <para>Where <literal>-p</literal> is the path where the log archive will
+    be saved, <literal>-n</literal> is the archive name.</para>
+
+    <note>
+      <para>If <literal>-p</literal> is not provided, the default path will be
+      used: <literal>/var/logcollector</literal>. If <literal>-n</literal> is
+      not provided, the default name will be used:
+      <filename>log_archive_&lt;timestamp&gt;.tar.gz</filename>.</para>
+    </note>
+
+    <para>To access the help menu of the script:</para>
+
+    <programlisting>./log-collector.sh -h</programlisting>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/net_config_options.xml b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
new file mode 100644
index 0000000..dae5b36
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
@@ -0,0 +1,886 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="net_config_operations">
+  <title>Network Configuration Options</title>
+
+  <para>Various Advanced Network Configuration options can be done from Enea
+  Edge Management GUI.</para>
+
+  <section id="device_callhome_nat">
+    <title>Device Call Home Connection for Deployment behind NAT</title>
+
+    <para>The Device Call Home option enables the initiation of the connection
+    between the uCPE Device and the Enea Edge Management, from the uCPE
+    device. The Device Call Home option is required when deploying a uCPE
+    device behind NAT since the IP address of the uCPE device is hidden for
+    the Enea Edge Management.</para>
+
+    <para>Enable Device Call Home by marking the Device Call Home checkbox
+    when registering the uCPE device in Enea Edge Management. When using this
+    mechanism, the device will initiate a connection to the Enea Edge
+    Management for NETCONF traffic (over SSH), while the Enea Edge Management
+    waits for a device connection.</para>
+  </section>
+
+  <section id="device_net_config">
+    <title>uCPE Device Network Configuration</title>
+
+    <para>The following describes the steps required for setting up the
+    virtualization infrastructure, ensuring that a uCPE device has networking
+    setup for virtualized service deployment. Networking is enabled by
+    selecting physical interfaces to be used by virtualized networking and
+    creating different types of bridges to enable VNF communication.</para>
+
+    <para>The Zero Touch Provisioning mechanism is also touched upon, as
+    alternative to manual configuration of the virtualization
+    infrastructure.</para>
+
+    <section id="config_dpdk">
+      <title>Configure DPDK</title>
+
+      <para>DPDK is an important functionality for accelerating networking
+      performance. The DPDK is enabled by default and should be utilized in
+      most configurations.</para>
+
+      <para>In use cases where CPU capacity is very limited, disabling DPDK
+      can free up CPU capacity and overall performance can improve. Navigate
+      to <emphasis role="bold">Configuration</emphasis>, then <emphasis
+      role="bold">DPDK</emphasis> and deselect <emphasis role="bold">Enable
+      DPDK</emphasis> to disable the DPDK.</para>
+
+      <note>
+        <para>Disabling the DPDK cannot be done after other network
+        configurations have been made.</para>
+      </note>
+
+      <para>In <emphasis role="bold">Configuration</emphasis>, select
+      <emphasis role="bold">DPDK</emphasis> where DPDK resources can also be
+      configured such as:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">LCore Mask</emphasis>. Allocated cores
+          for non-datapath OVS-DPDK threads (CPU core bitmask). Default:
+          0x2.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">PMD CPU Mask</emphasis>. Allocated cores
+          for datapath processing (CPU core bitmask). Default: 0x4.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Socket Memory</emphasis>. Hugepage
+          memory allocated for DPDK. Default: 1494.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="config_ext_interfaces">
+      <title>Configure External Interfaces</title>
+
+      <para>Once a management connection with the uCPE device has been
+      established by using any of the supported methods, the virtualization
+      networking infrastructure can be configured either manually or by using
+      Zero Touch Provisioning.</para>
+
+      <para>Available network interfaces can be added to the management
+      system, for use by the networking virtualization infrastructure.</para>
+
+      <para>In order to make physical network interfaces available to the
+      virtualization infrastructure and VNFs, they must be configured into the
+      management system.</para>
+
+      <para>To add an interface into the Enea Edge Management, select the uCPE
+      device, then from the top toolbar select <emphasis
+      role="bold">Configuration</emphasis>, then <emphasis
+      role="bold">External Interfaces</emphasis>, <emphasis
+      role="bold">Configuration</emphasis>, and click the <emphasis
+      role="bold">Add</emphasis> button. The available Interface types are
+      detailed below.</para>
+
+      <section id="dpdk_interface_type">
+        <title>DPDK Interface Type</title>
+
+        <para>Configuring a physical interface in DPDK mode will require a
+        DPDK-based application (e.g. OVS-DPDK) in order to access and use the
+        interface. An interface set as DPDK can be attached to an OVS-DPDK
+        bridge.</para>
+
+        <note>
+          <para>Make sure the <emphasis role="bold">Enable DPDK</emphasis>
+          checkbox is selected by accessing <emphasis
+          role="bold">Device</emphasis>, <emphasis
+          role="bold">Configuration</emphasis> and choosing <emphasis
+          role="bold">DPDK</emphasis>, otherwise no interface can be assigned
+          as DPDK.</para>
+        </note>
+
+        <para>To add a DPDK interface under the management system, set
+        appropriate values for the following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Source: name of the physical interface.</para>
+          </listitem>
+
+          <listitem>
+            <para>Networking-type: dpdk</para>
+          </listitem>
+
+          <listitem>
+            <para>Dpdk-type: the kernel module that allows user space access
+            to the physical interface. Either the <literal>vfio-pci</literal>
+            (most commonly used type) or the <literal>igb_uio</literal> driver
+            can be used.</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+
+      <section id="sriov_interface_type">
+        <title>SR-IOV Interface Type</title>
+
+        <para>SR-IOV technology allows for the creation of a number of virtual
+        functions on the host interface, which can be used by VNFs running on
+        the uCPE device.</para>
+
+        <para>For SR-IOV mode configuration, the user must set values for the
+        following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Source: name of the physical interface.</para>
+          </listitem>
+
+          <listitem>
+            <para>Networking-type: srIov</para>
+          </listitem>
+
+          <listitem>
+            <para>sriov-mode: adapter-pool</para>
+          </listitem>
+
+          <listitem>
+            <para>sriov-num-vfs: the number of virtual functions to
+            create.</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+
+      <section id="standard_interface_type">
+        <title>Standard Interface Type</title>
+
+        <para>Some of the physical network interfaces available on a uCPE
+        device, including Ethernet interfaces, do not have DPDK or SR-IOV
+        support. Instead, the Linux kernel driver has to be used.</para>
+
+        <para>To add Standard Interfaces under the management system, the user
+        must set values for the following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Source: the name of physical interface.</para>
+          </listitem>
+
+          <listitem>
+            <para>Networking-type: standard.</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+
+      <section id="wan_interface_type">
+        <title>Wan Interface Type</title>
+
+        <para>WAN interfaces configured during the installation of the uCPE
+        device are automatically added in the Enea Edge Management as type
+        <literal>wan</literal>. The WAN interface used for management of the
+        uCPE device is marked with the <literal>Management</literal> property
+        set to <literal>True</literal>.</para>
+
+        <para>If a WAN interface is to be assigned for use by a VNF, it must
+        be changed into another interface type depending on the type of
+        connection that will be used. The management WAN interface cannot be
+        changed to a different type. It is automatically used when an In-band
+        management bridge is created.</para>
+
+        <para><emphasis role="bold">How to Edit the Configuration of a Wan
+        Interface</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>To edit an interface configuration type from the Enea Edge
+            Management, select the uCPE device, then from the top toolbar
+            select the <emphasis role="bold">Configuration</emphasis> menu,
+            then <emphasis role="bold">External Interfaces</emphasis> and
+            <emphasis role="bold">Configuration</emphasis>. The already
+            configured interfaces are displayed here, as seen in the figure
+            above.</para>
+          </listitem>
+
+          <listitem>
+            <para>In order to edit an already configured interface, (as in the
+            example popup shown below, a WAN interface) double click on the
+            desired one and a popup will appear. A different popup appears for
+            each type of interface. From the <emphasis role="bold">Host
+            Interface</emphasis> window, a user can change the networking type
+            and the IP address assignment:</para>
+
+            <figure>
+              <title>Editing an Interface</title>
+
+              <mediaobject>
+                <imageobject>
+                  <imagedata align="center" contentwidth="450"
+                             fileref="images/edit_inter.png" />
+                </imageobject>
+              </mediaobject>
+            </figure>
+          </listitem>
+        </orderedlist>
+
+        <note>
+          <para>When changing the <literal>address-assignment</literal> from
+          static to DHCP, if any of the <literal>ip-address</literal>,
+          <literal>netmask</literal> or <literal>gateway</literal> fields have
+          invalid values a validation error will be triggered. These fields
+          must be empty or have the valid values for their respective address
+          assignment.</para>
+        </note>
+      </section>
+
+      <section id="wap_interface_type">
+        <title>Wap Interface Type</title>
+
+        <para>Wireless Access Point (Wap) interfaces are used to create
+        Wireless Access Points. Only interfaces with
+        <literal>wap-capable</literal> capabilities can be added as WAP
+        interfaces.</para>
+
+        <para><emphasis role="bold">How to edit the Configuration of a Wap
+        Interface</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>To edit an interface configuration from the Enea Edge
+            Management, select the uCPE device, then from the top toolbar
+            select the <emphasis role="bold">Configuration</emphasis> menu
+            then <emphasis role="bold">External Interfaces</emphasis> and
+            select <emphasis role="bold">Configuration</emphasis>. The already
+            configured interfaces will be displayed here.</para>
+          </listitem>
+
+          <listitem>
+            <para>In order to edit an already configured interface, (as in the
+            example popup shown below, a WAP interface) double click on the
+            desired one and a pop-up will appear. A different pop-up appears
+            for each type of interface. From the <literal>Host
+            Interface</literal> window, the following parameters are
+            configurable:</para>
+
+            <itemizedlist>
+              <listitem>
+                <para>Country Code: the country code, a 2 letter
+                ISO3166-alpha2 identifier.</para>
+              </listitem>
+
+              <listitem>
+                <para>Wireless Band: 2.4 GHz or 5 GHz. Depending on the band
+                selection, the correct <literal>Wireless Mode</literal> and
+                <literal>Radio Channel</literal> must be provided.</para>
+              </listitem>
+            </itemizedlist>
+
+            <figure>
+              <title>Editing an Interface</title>
+
+              <mediaobject>
+                <imageobject>
+                  <imagedata align="center" contentwidth="475"
+                             fileref="images/wap_external_interface.png" />
+                </imageobject>
+              </mediaobject>
+            </figure>
+          </listitem>
+        </orderedlist>
+
+        <note>
+          <para>Correct <emphasis role="bold">Country Code</emphasis>
+          selection is mandatory. All configuration options are available in
+          the Enea Edge Management GUI but only the Radio Settings that
+          conform with the selected country's official regulatory laws will be
+          applied when the Wireless AP is started on the uCPE Device.</para>
+        </note>
+      </section>
+
+      <section id="man_configuration">
+        <title>Manual Configuration</title>
+
+        <para>For Manual Configuration of uCPE networking, select the uCPE
+        device first, then access the <emphasis
+        role="bold">Configuration</emphasis> menu, and choose <emphasis
+        role="bold">External Interfaces</emphasis>, where a list of available
+        network interfaces and their capabilities can be found.</para>
+
+        <para>After networking interfaces have been added to the Enea Edge
+        Management, the user can change the interface type (DPDK, SR-IOV,
+        Standard, WAN, WAP).</para>
+
+        <figure>
+          <title>Configuration of External Interfaces</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" contentwidth="600"
+                         fileref="images/edit_inter_config.png" />
+            </imageobject>
+          </mediaobject>
+        </figure>
+      </section>
+    </section>
+
+    <section id="configure_bridges">
+      <title>Configuring Bridges</title>
+
+      <para>After networking interfaces have been added to the Enea Edge
+      Management, the user can create the necessary OVS bridges.</para>
+
+      <figure>
+        <title>OVS Bridges</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" contentwidth="600"
+                       fileref="images/ovs_bridges_tab.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para><emphasis role="bold">How to add OVS bridges in the Enea Edge
+      Management</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Select the uCPE device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select <emphasis role="bold">Configuration</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click <emphasis role="bold">OpenvSwitch</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the <emphasis role="bold">Bridges</emphasis> option,
+          then click <emphasis role="bold">Add</emphasis>.</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>Depending on the settings found when accessing the <emphasis
+        role="bold">Configuration</emphasis> menu and selecting <emphasis
+        role="bold">DPDK</emphasis>, OVS bridges with or without DPDK support
+        will be used on the uCPE device.</para>
+      </note>
+
+      <para>There are three types of bridges which can be created, each one
+      fulfiling a different role.</para>
+
+      <section id="inband_mg_bridge">
+        <title>uCPE In-band Management bridge</title>
+
+        <para>In-band Management refers to a model where both the data plane
+        and control plane flow over the same network path. In some situations
+        (e.g. the uCPE device has only one routable IP address), this is the
+        only option available to both control and configure the uCPE device,
+        while also allowing for data-path traffic to pass over the same
+        physical interface.</para>
+
+        <para>The solution provided by Enea for in-band management is based
+        upon an OpenvSwitch bridge managing all traffic passing through the
+        WAN physical port. Any standard or DPDK-assigned network interface can
+        be used for the In-Band management bridge.</para>
+
+        <para>To create the In-Band Management bridge, the user must set
+        values for the following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>name: name of the bridge.</para>
+          </listitem>
+
+          <listitem>
+            <para>ovs-bridge-type: inbandMgmt</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+
+      <section id="inband_mg_br_vnfs">
+        <title>In-band Management bridge for VNFs</title>
+
+        <para>If VNF management can be done over a dedicated virtual
+        interface, its possible to extend the networking infrastructure
+        configuration to also access the VNF's management interface over the
+        WAN port.</para>
+
+        <para>For this setup, three types of traffic will pass over the WAN
+        physical interface:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><emphasis role="bold">Device management</emphasis>. Part of
+            the device configuration done by the Enea Edge Management.</para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">VNF(s) management</emphasis>. Enabling
+            or disabling features of a VNF. E.g. enabling/disabling the
+            firewall or VPN setup.</para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">Data-path</emphasis>. All other
+            traffic that is not used in the control plane and needs to reach a
+            LAN network.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>To create a VNF In-Band Management bridge, the user must set
+        values for the following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>name: name of the bridge.</para>
+          </listitem>
+
+          <listitem>
+            <para>ovs-bridge-type: vnfMgmt</para>
+          </listitem>
+
+          <listitem>
+            <para>vnf-mgmt-address: select IPv4 as the type and fill in an
+            internal IP address for the bridge interface that will be
+            connected to the VNF management network, e.g 10.0.0.1.</para>
+          </listitem>
+        </itemizedlist>
+
+        <note>
+          <para>VNF management interfaces must be configured in same subnet as
+          that used by the bridge interface connected to the VNF management
+          network.</para>
+        </note>
+      </section>
+
+      <section id="dataplane_bridge">
+        <title>Data-plane bridge</title>
+
+        <para>Data-plane bridges are generic bridges used for the VNF
+        data-plane. There are two supported sub-types:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><emphasis role="bold">communication</emphasis>:
+            <itemizedlist>
+                <listitem>
+                  <para>Allows for VNF communication towards LAN/WAN networks.
+                  This bridge type has at least one physical port attached to
+                  it.</para>
+                </listitem>
+
+                <listitem>
+                  <para>Allows for creation of <literal>Wireless Access
+                  Points</literal>. This bridge type does not need a physical
+                  port attached to it.</para>
+                </listitem>
+              </itemizedlist></para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">integration</emphasis>: allows for
+            VNF-to-VNF communication (usually for service function chaining).
+            This bridge type does not have any physical port attached.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>To create a Data-plane bridge, the user must set values for the
+        following fields:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><emphasis role="bold">name</emphasis>: name of the
+            bridge.</para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">ovs-bridge-type</emphasis>: select
+            <literal>communication</literal> or
+            <literal>integration</literal>, depending on intended usage. For
+            communication bridges, physical interfaces can be added to the
+            bridge.</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+    </section>
+  </section>
+
+  <section id="zero_touch_prov">
+    <title>Zero Touch Provisioning - Creating an Offline Configuration</title>
+
+    <para>Zero-Touch Provisioning (ZTP) refers to the process of when a device
+    starts up for the first time and its initial configuration is pushed down
+    by an external management system, so that it is setup for proper operation
+    without additional manual intervention by an operator. ZTP is an
+    alternative to Manual configuration.</para>
+
+    <para>A variety of operations can occur as part of ZTP such as initial
+    device setup, configuration of managed objects, etc. The goal is to set up
+    a device to the maximum possible extent without forcing an operator to be
+    physically present (initially) to manage the device.</para>
+
+    <para>An offline configuration is usually prepared in advance for the Enea
+    Edge Management to setup the virtualization infrastructure on the uCPE
+    device, as soon as a device enrolls into the management system.</para>
+
+    <section id="offline_configuration">
+      <title>Offline Configuration</title>
+
+      <para>The Offline Configuration subsystem is used to pre-populate a
+      configuration for a device that will be brought under management at a
+      future point in time. When creating an offline configuration store a
+      <literal>Device ID</literal> can be specified. This ID uniquely
+      identifies the device to be initialized.</para>
+
+      <para>Alternatively, a wildcard can be used in the <literal>Device
+      ID</literal> field, which results in a configuration being pushed on all
+      uCPE devices upon their initial connection towards the Enea Edge
+      Management.</para>
+
+      <para>If the offline configuration is not configured for a uCPE device,
+      an alarm will be raised: <literal>Day-0 Config:ZTP:Major</literal>,
+      which occurs when the uCPE device connects to the Enea Edge Management
+      informing that the ZTP setup failed for the specific uCPE device.</para>
+
+      <para>To create an offline configuration, select from the top toolbar
+      the <emphasis role="bold">Applications</emphasis> menu, then <emphasis
+      role="bold">Offline Config</emphasis> and choose <emphasis
+      role="bold">Add</emphasis>. The following fields should be
+      filled:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Name: name of the device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Device type: Enea universal CPE.</para>
+        </listitem>
+
+        <listitem>
+          <para>DeviceVersion: <xi:include
+          href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(EneaLinux_REL_VER/1)" /></para>
+        </listitem>
+
+        <listitem>
+          <para>Config Set: uCPE Config</para>
+        </listitem>
+
+        <listitem>
+          <para>Device ID: device ID or a wildcard(*).</para>
+        </listitem>
+
+        <listitem>
+          <para>Device Grouping Tags: a tag to group devices. These tags match
+          the customer tags provided during the installation of the
+          device.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>The Name is user defined and can be set to any unique text string
+      identifying the configuration. The Device Version will match the Enea
+      Edge version of the uCPE device and the Device ID will be set to the
+      previously set identifier of the uCPE device.</para>
+
+      <para>When a device connects to the Enea Edge Management for the first
+      time, it checks the device to see if it has been Zero Touch Provisioned
+      (ZTP). If not, it looks for an offline configuration that matches these
+      values, in the following order:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>The Device ID.</para>
+        </listitem>
+
+        <listitem>
+          <para>The set of tags.</para>
+        </listitem>
+
+        <listitem>
+          <para>A "*" for Device ID (wildcard).</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>If a match is found, the offline configuration is sent to the
+      device as part of Zero-Touch-Provisioning.</para>
+
+      <para>After creating the Offline Config Store, access the device by
+      selecting <emphasis role="bold">Applications</emphasis>, then <emphasis
+      role="bold">offline config</emphasis> and clicking <emphasis
+      role="bold">Config App</emphasis>, to provision it with the required
+      initial configuration. This operation mirrors what happens during manual
+      configuration described previously.</para>
+
+      <note>
+        <para>The ZTP will only be triggered the first time a uCPE device
+        connects to the Enea Edge Management. Just changing an offline
+        configuration will not push the new changes to the device. If an
+        offline configuration is changed after uCPE device registration, a
+        factory reset can be executed to force a new ZTP to execute. Select
+        the device, then access the <emphasis
+        role="bold">Operations</emphasis> menu and select <emphasis
+        role="bold">factory reset</emphasis>.</para>
+      </note>
+    </section>
+  </section>
+
+  <section id="custom_scripts">
+    <title>Custom Scripts for Custom Networking Configurations</title>
+
+    <para>The custom scripts feature allows users to execute user-defined
+    scripts on the uCPE device at various times.This allows for more flexible
+    and advanced configurations such as a LTE modem configuration, advanced
+    network configurations or OVS flow rule programming at any time.</para>
+
+    <section id="upload_scripts">
+      <title>Uploading Scripts</title>
+
+      <para>The scripts need to be uploaded to the Enea Edge Management prior
+      to use. When uploading scripts to the Enea Edge Management make sure to
+      select the right script type.</para>
+
+      <para>The following script types are supported:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>Once-before-startup</literal>. This script will only
+          execute once after the system has rebooted, prior to processing any
+          device configuration.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>Always-before-startup</literal>. This script will
+          always execute after the system has rebooted, prior to processing
+          any device configuration.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>Once-after-startup</literal>. The script will always
+          execute after the system has rebooted, after all device
+          configuration processes have completed.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>Always-after-startup</literal>. This script will
+          always execute after all device configuration processes have
+          completed after the system has rebooted.</para>
+        </listitem>
+      </itemizedlist>
+
+      <note>
+        <para>After a factory reset, any of the
+        <literal>Once-before-*</literal> or <literal>Once-after-*</literal>
+        scripts will be re-run as described above.</para>
+      </note>
+
+      <para>Follow the instruction below to upload scripts:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu, then
+          <emphasis role="bold">Custom Scripts</emphasis> and choose <emphasis
+          role="bold">Configure</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select <emphasis role="bold">Upload to EMS</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <emphasis role="bold">Script Type</emphasis> menu,
+          select the type the uploaded script should have.</para>
+        </listitem>
+
+        <listitem>
+          <para>Press <emphasis role="bold">Choose File</emphasis> to select
+          the scripts needed, and then click <emphasis
+          role="bold">Send</emphasis>.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="remove_scripts">
+      <title>Removing Scripts</title>
+
+      <para>Follow the instruction below to remove scripts:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu, then
+          <emphasis role="bold">Custom Scripts</emphasis> and select <emphasis
+          role="bold">Configure</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the script you want to delete from the <emphasis
+          role="bold">Uploaded Scripts</emphasis> tab and then click <emphasis
+          role="bold">Delete</emphasis>, which will remove the script
+          immediately from the Enea Edge Management.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="configure_scripts">
+      <title>Configuring Script Location</title>
+
+      <para>The location where the scripts are staged in the Enea Edge
+      Management can be chanaged as described below:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu,
+          choose <emphasis role="bold">Custom Scripts</emphasis> and select
+          <emphasis role="bold">Configure</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the <emphasis role="bold">Configuration</emphasis> tab
+          and specify a new location to store the scripts.</para>
+
+          <note>
+            <para>Change the script storage location only if you have many
+            scripts which you would prefer to store on another partition,
+            otherwise leave this configuration as is.</para>
+          </note>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="run_the_scripts">
+      <title>Running the Scripts</title>
+
+      <para><emphasis role="bold">How to run Custom Scripts</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Devices</emphasis> menu,
+          choose <emphasis role="bold">Custom Scripts</emphasis> and select
+          <emphasis role="bold">Apply Scripts</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <emphasis role="bold">Script Config Screen</emphasis>
+          pop up, select the devices from the device(s) chooser list on which
+          to run the scripts. Press the <emphasis role="bold">&gt;</emphasis>
+          button to move the devices to the right side of the chooser, which
+          is the list of devices that will execute the selected
+          scripts.</para>
+        </listitem>
+
+        <listitem>
+          <para>Select the scripts from the list under the device(s) chooser
+          by pressing the <emphasis role="bold">+</emphasis> button.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the pop-up window, select the scripts from the list. If
+          there are no scripts to select, then there is no script uploaded
+          with that particular type. Upload the script(s) needed and try
+          again.</para>
+        </listitem>
+
+        <listitem>
+          <para>Check the <emphasis role="bold">Reboot devices</emphasis>
+          checkbox if you want to reboot and execute the scripts at once and
+          then select <emphasis role="bold">ok</emphasis>.</para>
+
+          <note>
+            <para>The status of execution for the scripts can be seen by
+            accessing <emphasis role="bold">Fault</emphasis>, opening the
+            <emphasis role="bold">Events</emphasis> screen and filtering by
+            device and/or the event name
+            <filename>CustomScriptExecuted</filename>.</para>
+          </note>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+
+  <section  id="wireless_access_point">
+    <title>Wireless Access Point</title>
+
+    <para>The Wireless AP Screen from the Enea Edge Management Configuration
+    menu allows users to configure a <literal>Wireless Access Point</literal>.
+    A <literal>wap-capable</literal> interface and a LAN bridge must be added
+    before doing the Wireless AP configuration. For more details see sections
+    <link linkend="wap_interface_type">Wap interface Type</link> and <link
+    linkend="dataplane_bridge">Data-plane bridge</link>.</para>
+
+    <para>The following parameters are configurable:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>SSID: the Wireless network name - any string with a max. length
+        of 32 octets.</para>
+      </listitem>
+
+      <listitem>
+        <para>Interface Name: the <literal>wap-capable</literal> external
+        interface.</para>
+      </listitem>
+
+      <listitem>
+        <para>Lan Bridge: the LAN bridge where wireless clients will be
+        hosted.</para>
+      </listitem>
+
+      <listitem>
+        <para>WAP Security Mode: <literal>open</literal> or
+        <literal>wpa2Psk</literal>. When choosing <literal>wpa2Psk</literal>,
+        a <literal>password</literal> and an <literal>encryption</literal>
+        must be provided. The <literal>password</literal> can be any string
+        with a minimum length of 8 and a maximum length of 63
+        characters.</para>
+      </listitem>
+
+      <listitem>
+        <para>DHCP Server: <literal>disabled</literal> or
+        <literal>enabled</literal>. When <literal>enabled</literal> is
+        selected, the range of IPs (<literal>IP Address Start</literal> -
+        <literal>IP Address End</literal>), <literal>Netmask</literal> and
+        <literal>Gateway</literal> values must be provided.</para>
+      </listitem>
+    </itemizedlist>
+
+    <figure>
+      <title>Wireless AP</title>
+
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" contentwidth="600"
+                     fileref="images/wap_wireless_ap.png" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <note>
+      <para>Only a single Wireless AP is allowed on a physical interface. The
+      validation of the <literal>wap-capable</literal> interface is done when
+      adding the Wireless AP, so, in case of an error, the parameters of the
+      <literal>wap-capable</literal> interface must be rechecked. This can be
+      done by accessing the <emphasis role="bold">Configuration</emphasis>
+      menu and selecting <emphasis role="bold">External
+      Interfaces</emphasis>.</para>
+    </note>
+  </section>
+</chapter>
diff --git a/doc/book-enea-edge-getting-started/doc/troubleshooting.xml b/doc/book-enea-edge-getting-started/doc/troubleshooting.xml
new file mode 100644
index 0000000..4984a35
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/troubleshooting.xml
@@ -0,0 +1,226 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="troubleshooting">
+  <title>Troubleshooting and Recovery</title>
+
+  <para>In all scenarios where possible, collect the logs for debugging. More
+  information on log collecting can be found in <olink
+  targetdoc="book_enea_nfv_access_getting_started"
+  targetptr="log_collector">Using the Log Collector in the <xi:include
+  href="../../s_docbuild/olinkdb/pardoc-names.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+  Manual.</para>
+
+  <para>The following is a small list of possible Enea Edge problems, and
+  their solutions. If you encounter other issues or can't get Enea Edge to
+  work successfully after consulting the information below, please use the
+  <olink targetdoc="book_enea_nfv_access_release_info"
+  targetptr="contacting_enea_support">Enea Support Team Form, available in the
+  <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(book_enea_nfv_access_release_info/1)" /></olink> Manual
+  downloaded with your release.</para>
+
+  <table>
+    <title>Troubleshooting and Recovery</title>
+
+    <tgroup cols="2">
+      <colspec align="left" />
+
+      <thead>
+        <row>
+          <entry align="center">Enea Edge Problem</entry>
+
+          <entry align="center">Solution</entry>
+        </row>
+      </thead>
+
+      <tbody>
+        <row>
+          <entry>A uCPE device fails to connect to the Enea Edge Management
+          after installation.</entry>
+
+          <entry>If the uCPE device is not able to connect to the Enea Edge
+          Management after an installation, the Web-installer application is
+          started automatically on the uCPE device to change the configuration
+          via a web browser. Please see <olink
+          targetdoc="book_enea_nfv_access_getting_started"
+          targetptr="boot_device_add_map">Booting the uCPE device and adding
+          it to the Map in the <xi:include
+          href="../../s_docbuild/olinkdb/pardoc-names.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+          Manual.</entry>
+        </row>
+
+        <row>
+          <entry>The uCPE Device cannot boot after an upgrade.</entry>
+
+          <entry><orderedlist>
+              <listitem>
+                <para>Perform a hardware reboot of the uCPE Device and select
+                the previous Enea Edge Runtime image from the GRUB menu. This
+                action assumes physical access to the uCPE device.</para>
+              </listitem>
+
+              <listitem>
+                <para>Reinitiate the Upgrade procedure according to the steps
+                in section <olink
+                targetdoc="book_enea_nfv_access_getting_started"
+                targetptr="upgrade_devices">uCPE device upgrades in the
+                <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+                Manual.</para>
+              </listitem>
+            </orderedlist></entry>
+        </row>
+
+        <row>
+          <entry>After a failed uCPE device upgrade the previous Enea Edge
+          image (from the GRUB menu) does not boot.</entry>
+
+          <entry>Reinstall Enea Edge on the uCPE device and redeploy the
+          initial configuration and virtualized services, by following the
+          steps in <olink targetdoc="book_enea_nfv_access_getting_started"
+          targetptr="install_ena_device">Installing Enea Edge - uCPE Device
+          installation in the <xi:include
+          href="../../s_docbuild/olinkdb/pardoc-names.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+          Manual.</entry>
+        </row>
+
+        <row>
+          <entry>The Enea Edge Management upgrade fails and a working snapshot
+          is available.</entry>
+
+          <entry>If a working snapshot obtained during a previous Upgrade or
+          Uninstall is available
+          (<filename>ucpemanager-Backup-YYYYddMMHHmm.tar.gz</filename>):
+          <orderedlist>
+              <listitem>
+                <para>Cleanup the current upgrade attempt with:</para>
+
+                <programlisting>./cleanup.sh /opt/ems</programlisting>
+              </listitem>
+
+              <listitem>
+                <para>Restore the previous installation as described in <olink
+                targetdoc="book_enea_nfv_access_getting_started"
+                targetptr="restore_prev_ucpe_install">Restoring a previous
+                Enea Edge Management installation in the <xi:include
+                href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+                Manual.</para>
+              </listitem>
+            </orderedlist></entry>
+        </row>
+
+        <row>
+          <entry>The Enea Edge Management upgrade fails and no working
+          snapshot is available, but a System Back-up file exists.</entry>
+
+          <entry><orderedlist>
+              <listitem>
+                <para>Cleanup the current upgrade attempt with:</para>
+
+                <programlisting>./cleanup.sh /opt/ems</programlisting>
+              </listitem>
+
+              <listitem>
+                <para>Perform an installation with the restore option of a
+                previous Enea Edge Management configuration as described in
+                <olink targetdoc="book_enea_nfv_access_getting_started"
+                targetptr="install_ucpemg_from_backup">Installation of the
+                Enea Edge Management using a System Back-up in the <xi:include
+                href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+                Manual.</para>
+              </listitem>
+            </orderedlist></entry>
+        </row>
+
+        <row>
+          <entry>The uCPE device is booted, the ssh connection is available
+          but the device is not connected to the Enea Edge Management.</entry>
+
+          <entry><orderedlist>
+              <listitem>
+                <para>Perform a hardware reboot on the uCPE device to
+                reinitiate the connection mechanism.</para>
+              </listitem>
+
+              <listitem>
+                <para>Use the <emphasis role="bold">Reconnect</emphasis>
+                button from the Enea Edge Management's GUI.</para>
+              </listitem>
+
+              <listitem>
+                <para>Connect to uCPE Device console and run the factory reset
+                script:</para>
+
+                <programlisting>/usr/local/odm/bin/factory_reset.sh</programlisting>
+              </listitem>
+
+              <listitem>
+                <para>If the above actions do not work, reinstall and
+                reconfigure the device using the steps provided in <olink
+                targetdoc="book_enea_nfv_access_getting_started"
+                targetptr="install_ena_device">Installing Enea Edge - uCPE
+                Device installation in the <xi:include
+                href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+                Manual.</para>
+              </listitem>
+            </orderedlist></entry>
+        </row>
+
+        <row>
+          <entry>The SSH connection to the device cannot be
+          established.</entry>
+
+          <entry>Perform a hardware reboot on the uCPE device. If the problem
+          is not fixed, reinstall and reconfigure the device using the steps
+          provided in <olink targetdoc="book_enea_nfv_access_getting_started"
+          targetptr="install_ena_device">Installing Enea Edge - uCPE Device
+          installation in the <xi:include
+          href="../../s_docbuild/olinkdb/pardoc-names.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+          Manual.</entry>
+        </row>
+
+        <row>
+          <entry>The VNF Service is not working as expected after
+          reconfiguration (e.g. a VNF chain is malfunctioning).</entry>
+
+          <entry><orderedlist>
+              <listitem>
+                <para>Undo all flows and/or configuration changes in order to
+                move the system to a previously working configuration.</para>
+              </listitem>
+
+              <listitem>
+                <para>Reboot the device by accessing <emphasis
+                role="bold">Operations</emphasis> and then selecting <emphasis
+                role="bold">Reboot</emphasis> from within the Enea Edge
+                Management.</para>
+              </listitem>
+
+              <listitem>
+                <para>If the above actions do not work, redeploy all services.
+                This is done by cleaning up the existing configuration by
+                accessing <emphasis role="bold">Operations</emphasis>, then
+                selecting <emphasis role="bold">Factory Reset</emphasis> for a
+                specific device and redeploying the VNF services.</para>
+              </listitem>
+            </orderedlist></entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </table>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
new file mode 100644
index 0000000..641775d
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
@@ -0,0 +1,588 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="upgrade_ena">
+  <title>Upgrading Enea Edge</title>
+
+  <para>Enea provides regular releases that will require the upgrading of Enea
+  Edge components. The Enea Edge Management must be upgraded first, followed
+  by upgrading the Enea Edge Runtime on the uCPE devices.</para>
+
+  <section id="upgrade_mg">
+    <title>Upgrading the Enea Edge Management</title>
+
+    <note>
+      <para>It is recommended to create a system backup by accessing <emphasis
+      role="bold">System</emphasis> and selecting <emphasis role="bold">System
+      Backup</emphasis> from the Enea Edge Management GUI, for recovery in
+      case of an upgrade failure.</para>
+    </note>
+
+    <orderedlist>
+      <listitem>
+        <para>Extract the
+        <filename>Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</filename>
+        folder.</para>
+
+        <para>The directory in which the archive has been unpacked will be
+        denoted as <literal>&lt;uCPEM-installdir&gt;</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enter <literal>&lt;uCPEM-installdir&gt;/dist</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Run the following command with the root account and change
+        <literal>/opt/ems</literal> to the correct location of the Enea Edge
+        Management installation:</para>
+
+        <programlisting>./upgrade.sh /opt/ems \
+Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
+      </listitem>
+    </orderedlist>
+
+    <para>Running this command will:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Stop the currently running <literal>ucpemanager</literal>
+        service.</para>
+      </listitem>
+
+      <listitem>
+        <para>Create a compressed file of the <literal>ucpemanager</literal>
+        application folder
+        (<filename>ucpemanager-Back-up-YYYYddMMHHmm.tar.gz</filename>), which
+        contains a snapshot of the existing installation in the
+        <literal>&lt;uCPEM-installdir&gt;/dist</literal> directory.</para>
+
+        <note>
+          <para>The snapshot file created during the upgrade can be used for
+          restoring the Enea Edge Management.</para>
+        </note>
+      </listitem>
+
+      <listitem>
+        <para>Extract the application files from the specified compressed
+        install kit.</para>
+      </listitem>
+
+      <listitem>
+        <para>Start the <literal>ucpemanager</literal> service.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para><olink targetdoc="book_enea_nfv_access_getting_started"
+    targetptr="fresh_ucpemg_install">Fresh Installation of the Enea Edge Management
+    in the <ns:include
+    href="../../s_docbuild/olinkdb/pardoc-names.xml"
+    xmlns:ns="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+    Manual contains information about the input required to be entered during
+    the execution of the upgrade script.</para>
+
+    <para>For an example on how to upgrade an Enea Edge Management installation
+    in a High Availability setup, consult <olink
+    targetdoc="book_enea_nfv_access_getting_started"
+    targetptr="ha_upgrade">Upgrading a High Availability Deployment in the
+    <ns:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+    xmlns:ns="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+    Manual.</para>
+
+    <section id="restore_prev_ucpe_install">
+      <title>Restoring a previous Enea Edge Management Installation</title>
+
+      <para><emphasis role="bold">How to restore a previous Enea Edge
+      Management installation</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Extract
+          <filename>Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</filename></para>
+        </listitem>
+
+        <listitem>
+          <para>The directory in which the archive has been unpacked will be
+          denoted as <literal>&lt;uCPEM-installdir&gt;</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Copy the snapshot file
+          (<filename>ucpemanager-Backup-YYYYddMMHHmm.tar.gz</filename>)
+          created during a previous Enea Edge Management Upgrade or Enea Edge
+          Management Uninstall Operation into the
+          <literal>&lt;uCPEM-installdir&gt;</literal> directory.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enter <literal>&lt;uCPEM-installdir&gt;/dist</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Run the following command with the root user and change
+          <literal>/opt/ems</literal> to the correct location of the Enea Edge
+          Management installation:</para>
+
+          <programlisting>./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz</programlisting>
+        </listitem>
+      </orderedlist>
+
+      <para>Running this command will:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Remove any vestiges of the existing
+          <literal>ucpemanager</literal> service, if they exist.</para>
+        </listitem>
+
+        <listitem>
+          <para>Reinstall the Enea Edge Management application on the
+          specified target location, restoring the data in the database and
+          files in the process.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>The <literal>ucpemanager</literal> service will then start with
+      the older version now running on the system.</para>
+    </section>
+
+    <section id="uninstall_ucpem_install">
+      <title>Uninstalling an existing Enea Edge Management
+      Installation</title>
+
+      <para><emphasis role="bold">How to uninstall an existing Enea Edge
+      Management installation</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Navigate to the folder where the Enea Edge Management is
+          installed: <filename>&lt;uCPEM-installdir&gt;</filename>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Run the following command with the root user and change
+          <literal>/opt/ems</literal> to the correct location of the Enea Edge
+          Management installation:</para>
+
+          <programlisting>./uninstall.sh /opt/ems</programlisting>
+        </listitem>
+      </orderedlist>
+
+      <para>Running this command will:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Stop the currently running <literal>ucpemanager</literal>
+          service.</para>
+        </listitem>
+
+        <listitem>
+          <para>Create a compressed file of the <literal>ucpemanager</literal>
+          application folder:
+          <filename>ucpemanager-Back-up-YYYYddMMHHmm.tar.gz</filename>, which
+          contains a snapshot of the existing installation and functions as a
+          restore point.</para>
+
+          <note>
+            <para>The snapshot file created during the uninstall can be used
+            for restoring Enea Edge Management.</para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>Uninstall the <literal>ucpemanager</literal> service, so that
+          it will not start up on reboot.</para>
+        </listitem>
+
+        <listitem>
+          <para>Uninstall the database service.</para>
+        </listitem>
+
+        <listitem>
+          <para>Completely remove the contents of the application and database
+          folders.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>After these steps, the Enea Edge Management is completely removed
+      from the system.</para>
+    </section>
+  </section>
+
+  <section id="upgrade_devices">
+    <title>uCPE device Upgrades</title>
+
+    <para>A uCPE device can be upgraded using the Enea Edge Management
+    GUI.</para>
+
+    <section id="device_up_process">
+      <title>The uCPE device Upgrade Process</title>
+
+      <para>The Device Upgrade/Install option performs the following
+      operations to the uCPE device:</para>
+
+      <orderedlist>
+        <listitem>
+          <para><emphasis role="bold">Prepare for upgrade.</emphasis> This
+          stage prepares the files needed for an upgrade.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Install file on device.</emphasis> This
+          stage copies the file to the uCPE device.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Upgrade Device.</emphasis> This stage
+          upgrades the uCPE device to a newer version.</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>Upgrading from Enea NFV Access 2.3.0 is not possible when using
+        the Enea uCPE Manager in HTTPS mode. Either switch to HTTP by accessing
+        <emphasis role="bold">System</emphasis>, <emphasis
+        role="bold">Configuration</emphasis>, <emphasis role="bold">Web
+        Access</emphasis> and checking the <emphasis role="bold">Enable
+        HTTP</emphasis> box, or installing it manually.</para>
+      </note>
+    </section>
+
+    <section id="mg_upgrade">
+      <title>Managing the uCPE device Upgrade</title>
+
+      <para>Before an installation or upgrade can be completed, certain
+      configuration data must be set. Files also need to be uploaded to the
+      Device Upgrade image repository in order to be uploaded to the
+      device.</para>
+
+      <para>Launch the Device Upgrade management console by selecting
+      <emphasis role="bold">Devices</emphasis> and then the <emphasis
+      role="bold">Upgrade</emphasis> button from the top tool-bar. The console
+      will contain the following tabs:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">Image Library</emphasis>. To add/delete
+          an image.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Upgrade Operations</emphasis>. See
+          upgrades that are currently running, cancel any upgrades in
+          progress, or start a uCPE device upgrade.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Configuration</emphasis>. Upgrade
+          configuration parameters.</para>
+        </listitem>
+      </itemizedlist>
+
+      <note>
+        <para>The uCPE Device upgrade is done with image files of the type
+        <literal>rootfs.ostree.tar.bz2</literal>, which are available in the
+        <filename>Enea_Edge_Runtime_&lt;processor&gt;_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</filename>
+        file you downloaded with your release.</para>
+      </note>
+
+      <section id="image_lib">
+        <title>Image Library</title>
+
+        <para><emphasis role="bold">Adding an image to the image
+        repository/library</emphasis><orderedlist>
+            <listitem>
+              <para>Select <emphasis role="bold">Devices</emphasis> and then
+              the <emphasis role="bold">Upgrade</emphasis> button.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select <emphasis role="bold">Add</emphasis> from the
+              <emphasis role="bold">Image Library</emphasis> tab to add a new
+              image file.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select <emphasis role="bold">Choose File</emphasis> to
+              provide the path to the image file (must be of type
+              <literal>rootfs.os-tree.tar.bz2</literal>).</para>
+            </listitem>
+
+            <listitem>
+              <para>Select the target hardware platform corresponding to the
+              image being uploaded (<literal>xeon-d</literal> or
+              <literal>atom-c3000</literal>).</para>
+            </listitem>
+
+            <listitem>
+              <para>Click <emphasis role="bold">Send</emphasis> to upload the
+              image to the image repository.</para>
+            </listitem>
+          </orderedlist></para>
+
+        <para><emphasis role="bold">Deleting an image from the image
+        repository</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>Select <emphasis role="bold">Devices</emphasis> and then the
+            <emphasis role="bold">Upgrade</emphasis> button.</para>
+          </listitem>
+
+          <listitem>
+            <para>Select the image you want to delete from the <emphasis
+            role="bold">Image Library</emphasis> tab and then click <emphasis
+            role="bold">Delete</emphasis>.</para>
+          </listitem>
+        </orderedlist>
+      </section>
+
+      <section id="upgrade_options">
+        <title>Upgrade Operations</title>
+
+        <para>The <emphasis role="bold">Upgrade Operations</emphasis> tab
+        allows a user to manage uCPE device upgrades in the system. It allows
+        the user to see all the upgrades that are currently in progress, as
+        well as listing the completed ones. If an upgrade succeeds or fails,
+        then a row will be added to the completed upgrades table. If one
+        fails, the failure message will be visible in the table.</para>
+
+        <note>
+          <para>The list of completed upgrade tasks resides in the cache
+          memory and will not persist across reboots of the server.</para>
+        </note>
+
+        <para><emphasis role="bold">How to Install/Upgrade a device
+        immediately or schedule the process for later</emphasis><orderedlist>
+            <listitem>
+              <para>Select <emphasis role="bold">Devices</emphasis> and then
+              the <emphasis role="bold">Upgrade</emphasis> button.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select <emphasis role="bold">Upgrade Devices</emphasis>
+              from the <emphasis role="bold">Upgrade Operations</emphasis>
+              tab. This will launch a <literal>Multi Device Install
+              Image</literal> screen that will allow the user to install and
+              upgrade more than one uCPE device at a time or upgrade
+              later.</para>
+            </listitem>
+          </orderedlist></para>
+
+        <para>The configurable parameters are:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><literal>Scheduling</literal>. Click this checkbox if the
+            upgrade will be done later. Schedule the day, hour and minute for
+            when to run the upgrade.</para>
+
+            <note>
+              <para>The hour represents the local Enea Edge Management server
+              hour.</para>
+            </note>
+          </listitem>
+
+          <listitem>
+            <para><literal>Description</literal>. An optional description of
+            the operation. It is recommended to add a description so that
+            different upgrades happening simultaneously can be
+            distinguished.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>Image File</literal>. Click on <emphasis
+            role="bold">Choose Image File</emphasis> to select the image
+            file.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>Devices</literal>. The list of uCPE Devices that
+            can accept an image file is populated when the image file is
+            chosen.</para>
+
+            <para>Mark the uCPE devices that you wish to upgrade and press the
+            <emphasis role="bold">&gt;</emphasis> button to move the uCPE
+            devices to the right side of the selector. Those chosen form the
+            list of uCPE devices that will be upgraded.</para>
+          </listitem>
+
+          <listitem>
+            <para><literal>Upgrade Operation</literal>. The available options
+            are:</para>
+
+            <itemizedlist>
+              <listitem>
+                <para><literal>Install and Activate</literal>. This will do an
+                image installation as well as an upgrade.</para>
+              </listitem>
+
+              <listitem>
+                <para><literal>Install Only</literal>. This will do an image
+                installation only. The image is copied to the uCPE device, and
+                an upgrade will be done later either at a scheduled time or
+                when the option <literal>Activate Only</literal> is
+                selected.</para>
+              </listitem>
+
+              <listitem>
+                <para><literal>Activate Only</literal>. This will activate an
+                already installed image on the uCPE device.</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>To start the upgrade, click <emphasis
+            role="bold">ok</emphasis>.</para>
+          </listitem>
+        </itemizedlist>
+
+        <note>
+          <para>When the uCPE device activates the upgrade, it will be
+          rebooted automatically.</para>
+        </note>
+      </section>
+
+      <section id="releases_installed">
+        <title>Releases installed on a uCPE device</title>
+
+        <para>The installed releases on a uCPE device can be viewed by
+        selecting the uCPE device first, then from the top toolbar selecting
+        <emphasis role="bold">Configuration</emphasis> and then the <emphasis
+        role="bold">Upgrade</emphasis> button.</para>
+
+        <para>The installed releases on the uCPE device, the release status,
+        release state, <literal>commit-id</literal> and release version will
+        be listed in a table.</para>
+      </section>
+
+      <section id="upgrade_status">
+        <title>uCPE device Upgrade Status</title>
+
+        <para>The status of the installation and upgrade can be viewed in the
+        <emphasis role="bold">Upgrade Operations</emphasis> tab. Ongoing or
+        scheduled upgrade operations can be viewed or cancelled.</para>
+
+        <para><emphasis role="bold">To view the status of an installation or
+        upgrade operations</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>Select <emphasis role="bold">Devices</emphasis> and then the
+            <emphasis role="bold">Upgrade</emphasis> button.</para>
+          </listitem>
+
+          <listitem>
+            <para>Select <emphasis role="bold">Upgrade Operations</emphasis>.
+            The ongoing operations are listed at the top and a history of
+            failed or successful operations are listed at the bottom.</para>
+          </listitem>
+
+          <listitem>
+            <para>Select an <emphasis role="bold">Active</emphasis> or
+            <emphasis role="bold">Completed Upgrade Operation</emphasis> and
+            then the <emphasis role="bold">Device Status</emphasis> button to
+            see detailed information regarding the upgrade operation,
+            including the uCPE devices involved and information per uCPE
+            device.</para>
+          </listitem>
+        </orderedlist>
+
+        <para><emphasis role="bold">To cancel an upgrade
+        operation</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>Select <emphasis role="bold">Devices</emphasis>, then the
+            <emphasis role="bold">Upgrade</emphasis> button and choose
+            <emphasis role="bold">Upgrade Operations</emphasis>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Select an operation from the list and choose <emphasis
+            role="bold">Cancel Upgrade</emphasis> and <emphasis
+            role="bold">Confirm</emphasis>. The operation will then be deleted
+            from the list.</para>
+          </listitem>
+        </orderedlist>
+      </section>
+
+      <section id="config">
+        <title>Configuration</title>
+
+        <note>
+          <para>The default values present in the configuration of each uCPE
+          device are recommended for use. Modifying them is for an <emphasis
+          role="bold">Advanced User</emphasis> only.</para>
+        </note>
+
+        <para><emphasis role="bold">How to Configure the uCPE device
+        Upgrade</emphasis><orderedlist>
+            <listitem>
+              <para>Select <emphasis role="bold">Devices</emphasis> and then
+              the <emphasis role="bold">Upgrade</emphasis> button.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select <emphasis
+              role="bold">Configuration</emphasis>.</para>
+            </listitem>
+
+            <listitem>
+              <para>The configurable parameters are:</para>
+
+              <itemizedlist>
+                <listitem>
+                  <para><literal>deviceImageDir</literal>. This is the disk
+                  location of the device image repository.</para>
+
+                  <note>
+                    <para>If no absolute path name is given it is assumed to
+                    be relative to the installation directory.</para>
+                  </note>
+                </listitem>
+
+                <listitem>
+                  <para><literal>maxThreads</literal>. This number dictates
+                  how many upgrades the system can manage at one time, either
+                  individually launched or launched from the multi-device
+                  screens. This value defaults to 20, which means that 20 uCPE
+                  devices may be updated at one time.</para>
+                </listitem>
+
+                <listitem>
+                  <para><literal>KeepAlive</literal>. This number represents
+                  the number of seconds that a thread will be kept alive
+                  before it is collected. If multiple installations are
+                  occurring, this will keep the thread alive for X seconds
+                  before it is released. If not released, it can be used by
+                  the internal scheduling system as soon as it has completed
+                  an upgrade.</para>
+                </listitem>
+              </itemizedlist>
+            </listitem>
+          </orderedlist></para>
+      </section>
+
+      <section id="related_functionality">
+        <title>Related Functionality for a uCPE device Upgrade</title>
+
+        <para>Each uCPE device can receive image files and use them to
+        upgrade. This can be done by selecting the uCPE device in the
+        <emphasis role="bold">System</emphasis> view and clicking the
+        <emphasis role="bold">Upgrade</emphasis> button. In the new window, an
+        upgrade image can be chosen from the <emphasis role="bold">Image
+        Files</emphasis> tab by selecting the image file from the list and
+        clicking the <emphasis role="bold">Install on Device</emphasis>
+        button.</para>
+
+        <para>Once an image is installed on the uCPE device, the image will be
+        available on the uCPE device and be visible in the <emphasis
+        role="bold">Releases</emphasis> tab. It can then be selected from the
+        list and the upgrade started by clicking the <emphasis
+        role="bold">Upgrade</emphasis> button.</para>
+      </section>
+    </section>
+  </section>
+</chapter>
diff --git a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
new file mode 100644
index 0000000..bd2fb0b
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
@@ -0,0 +1,477 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="vnf_mg">
+  <title>VNF Management</title>
+
+  <para>The Enea Edge Management is responsible for onboarding, configuring
+  (e.g. CloudInit) and ensuring life cycle management of VNFs that are
+  instantiated and run on the various uCPE devices.</para>
+
+  <section id="onboarding_a_vnf">
+    <title>Onboarding a VNF</title>
+
+    <para>The onboarding of a VNF means adding it to the Enea Edge Management
+    VNF Catalogue and preparing it for instantiation (deployment on connected
+    uCPE devices). This is accomplished using the Enea Edge Management
+    Onboarding graphical user interface.</para>
+
+    <para>Typically, the Getting Started Guide of a VNF, provided by the VNF
+    vendor, contains all necessary information needed to onboard a VNF.</para>
+
+    <section id="retrieve_art">
+      <title>Retrieving Artifacts</title>
+
+      <para>The user must first retrieve the necessary artifacts from the VNF
+      vendor:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Download the VNF from the commercial vendor.</para>
+        </listitem>
+
+        <listitem>
+          <para>Procure any VNF-specific files from the VNF vendor, e.g.
+          license file.</para>
+
+          <note>
+            <para>There are no standard ways of managing VNF licenses,
+            therefore no general guidelines can be provided. One example of
+            license handling that can be employed in the Enea Edge Management
+            is the adding of a license during the Cloud-Init setup.</para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>Optionally, get access to the VNF specific VNF Manager for day
+          1 and 2 configuration (in cloud or for local deployment).</para>
+        </listitem>
+
+        <listitem>
+          <para>Procure the Getting Started Guide from the VNF vendor,
+          preferably for KVM deployment for VNF specific configuration
+          information.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="onboard_prep">
+      <title>Preparation</title>
+
+      <para>Once all needed downloadables, documentation and more have been
+      attained, preparation for onboarding must be completed:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Determine the use-case and performance requirements of the VNF
+          you wish to deploy:</para>
+
+          <itemizedlist spacing="compact">
+            <listitem>
+              <para>This decides what resources the VNF is configured for,
+              along with networking and day zero configurations.</para>
+
+              <note>
+                <para>Generally, the Getting Started Guide for the VNF
+                provides guidelines for resource allocation, but since
+                performance is dependent on hardware capacity, the right
+                resource allocation for deployment is determined through
+                benchmarking.</para>
+              </note>
+            </listitem>
+
+            <listitem>
+              <para>Determine the amount of hardware resources needed for the
+              VNF (RAM, number of CPUs and storage size).</para>
+            </listitem>
+
+            <listitem>
+              <para>Determine how many Virtual Network Interfaces the VNF will
+              use.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Determine the Day-0 configuration method from the VNF Getting
+          Started guidelines.</para>
+
+          <note>
+            <para>For many VNFs, day zero configuration can be skipped in
+            early onboarding efforts when automation is not of
+            importance.</para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>Determine any requirements needed by the Cloud-Init file
+          structure and the content needed when this structure is used.</para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="onboard_in_ucpemg">
+      <title>Onboarding into the Enea Edge Management</title>
+
+      <para><emphasis role="bold">How to onboard a VNF into the Enea Edge
+      Management </emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Select from the top toolbar <emphasis
+          role="bold">VNF</emphasis> and then <emphasis
+          role="bold">Descriptors</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Click the <emphasis role="bold">On-board</emphasis>
+          button.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>This window contains data fields where both necessary and optional
+      information about the VNF can be supplied. After doing so, press the
+      Onboard button, the Enea Edge Management will create the VNF descriptor
+      and add it to its VNF Catalog.</para>
+
+      <figure>
+        <title>Onboard a VNF</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" contentwidth="600"
+                       fileref="images/onboard_a_vnf_image.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para><emphasis role="bold">Main fields</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">VM Image File</emphasis>. This is the
+          Virtual Machine image file for the VNF. Typically, it is a QCOW
+          image. Press <emphasis role="bold">Choose File</emphasis> and select
+          the image you wish to upload.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Image Format</emphasis>. Select the
+          format which matches the image file format.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">VNF Type Name</emphasis>. This is the
+          name that will be used to identify this VNF. It will be shown in the
+          VNFs list.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Description</emphasis>. This field
+          contains any description provided and is only displayed in the GUI
+          tables in the Enea Edge Management.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Version</emphasis>. This is the version
+          of the current VNF that you are hosting. It's used to distinguish
+          this VNF from other versions of the same type.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Memory in MB</emphasis>. This is the
+          amount of memory (in megabytes) that will be provided to this type
+          of VNF when it is instantiated. To determine the value for this
+          field, consult the VNF vendor.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Num of CPUs</emphasis>. The number of
+          CPUs that will be dedicated to an instance of this VNF when created.
+          To determine the value for this field, consult the VNF
+          vendor.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Storage in GB</emphasis>. How much disk
+          space to provide an instance of this VNF. To determine the value for
+          this field, consult the VNF vendor.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Interfaces Tab</emphasis></para>
+
+      <para>Click on the <emphasis role="bold">Interfaces</emphasis> tab to
+      show the Interfaces table.</para>
+
+      <para>This table will contain the interfaces required by this VNF to be
+      configured, when creating an instance. Consult the VNF vendor to
+      determine which and how many are required. Each interface requires a
+      name, and optionally a description, used only by the Enea Edge
+      Management.</para>
+
+      <note>
+        <para>CAUTION: The user MUST conserve the same order for the virtual
+        interfaces during both onboarding and instantiation phases.</para>
+      </note>
+
+      <para><emphasis role="bold">Cloud Init Tab</emphasis></para>
+
+      <para>Click the <emphasis role="bold">Cloud Init</emphasis> tab to
+      provide the Cloud-Init configuration. There are three fields that need
+      to be populated:</para>
+
+      <orderedlist>
+        <listitem>
+          <para><emphasis role="bold">Cloud-Init Datasource</emphasis></para>
+
+          <para>To onboard a VNF you must specify the <literal>Cloud-Init
+          Datasource</literal> that the VNF uses. This information is procured
+          from the VNF Vendor. Choose one of the following methods to specify
+          the datasource:</para>
+
+          <itemizedlist spacing="compact">
+            <listitem>
+              <para><emphasis role="bold">None</emphasis>. If there is no
+              datasource.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">ConfigDrive</emphasis>. This method
+              allows you to provide any number of content-data files
+              containing Cloud-Init data.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">NoCloud</emphasis>. This is a
+              simpler method that uses only one cloud init file
+              (User-Data).</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">ISO</emphasis>. Pre-cooked
+              cloud-init image. This image must be created by the user
+              according to VNF requirements.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Cloud-Init Disk Type</emphasis></para>
+
+          <para>The <literal>Cloud-Init Disk Type</literal> field must be set
+          to either <literal>Disk</literal>, or <literal>CD-ROM</literal>,
+          depending on what the VNF requires. You can get this information
+          from the VNF Vendor.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Content Files Table</emphasis></para>
+
+          <para>The <literal>Content Files Table</literal> is ONLY used if
+          <literal>ConfigDrive</literal> is chosen as the Cloud-Init
+          Datasource. For each content file added, a <literal>Path</literal>
+          must be provided. When the Enea Edge Management is used to create an
+          instance for multiple VNFs, the user will be prompted to provide a
+          data file for each entry in this table. Each type of VNF will
+          require different cloud-init files, e.g.: a license file. The data
+          files will be added to the cloud-init image that the user provides
+          at the instantiation of the VNF. If the cloud-init image is not
+          provided, no Cloud-Init Data Source will be created for that VNF and
+          there will be no warning.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>Consult with the VNF vendor to determine what is required for the
+      VNF you are onboarding.</para>
+
+      <para><emphasis role="bold">Properties Tab</emphasis></para>
+
+      <para>In this table, you can enter values for properties that will be
+      used during instantiation of the VNF. The values will augment the
+      default values in the <filename>domain.xml</filename> file used by
+      <literal>libvirt/virsh</literal> (running in Enea Edge) when creating an
+      instance of the VNF. Consult with the VNF Vendor or ENEA support for
+      values needed by specific VNFs.</para>
+
+      <para><emphasis role="bold">Property Values</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>numHugePages</literal> defines the number of huge
+          memory pages the VNF uses (for DPDK).</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>vnfMgmtIpAddress</literal>: the IP address of the
+          VNF's management interface, connected to a
+          <literal>vnfMgmt</literal> bridge (e.g. 10.0.0.2).</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>internalMgmtPort</literal>: the VNF's TCP/UDP port
+          used for management (e.g. 443).</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>externalMgmtPort</literal>: the Management port used
+          for external access (e.g. 60001).</para>
+        </listitem>
+      </itemizedlist>
+
+      <note>
+        <para>The last three properties are useful in conjuction with the
+        <literal>vnfMgmt</literal> bridge type. They allow the user to map the
+        internal VNF management port to an external port, useful for VNF
+        configuration from WAN.</para>
+
+        <para>In the previous example, the internal TCP port 443 (HTTPS) was
+        mapped to the external port 60001, which allows the user to access the
+        VNF management port from a web browser e.g.
+        <literal>https://&lt;WAN_IP&gt;:60001</literal>.</para>
+      </note>
+    </section>
+  </section>
+
+  <section id="instantiating_a_vnf">
+    <title>Instantiating a VNF</title>
+
+    <para>When a VNF is onboarded and available in the VNF catalog, it can be
+    instantiated on connected uCPE devices. The configurations provided when
+    the VNF is onboarded, serve as a template for instantiation. Before
+    instantiating any VNF, please make sure the available storage space on the
+    uCPE device is big enough to accommodate the VNF you need to
+    instantiate.</para>
+
+    <para>Follow the instructions below to instantiate a VNF:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Select from the top toolbar <emphasis role="bold">VNF</emphasis>
+        and choose <emphasis role="bold">Instances</emphasis>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Click the <emphasis role="bold">Add</emphasis> button.</para>
+      </listitem>
+
+      <listitem>
+        <para>Fill out the following mandatory fields:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Name: a descriptive name.</para>
+          </listitem>
+
+          <listitem>
+            <para>VNF Type: a list of onboarded VNFs.</para>
+          </listitem>
+
+          <listitem>
+            <para>uCPE Device: the uCPE device to instantiate the VNF
+            on.</para>
+          </listitem>
+
+          <listitem>
+            <para>Networking Configuration:</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>Connect each configured NIC with a bridge, SR-IOV or PCI
+                Passthrough.</para>
+              </listitem>
+
+              <listitem>
+                <para>Set up each NIC with a driver method.</para>
+              </listitem>
+            </itemizedlist>
+
+            <note>
+              <para>All configured NICs must be set up before instantiating a
+              VNF. Failure to do so will end in a failed instantiation.</para>
+            </note>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Add VNF-specific configuration data by uploading a Cloud-Init
+        file (when the Cloud-Init is used).</para>
+      </listitem>
+
+      <listitem>
+        <para>Add any VNF-specific files (e.g license files).</para>
+      </listitem>
+
+      <listitem>
+        <para>Hit the <emphasis role="bold">Create</emphasis> button to deploy
+        the VNF and run it on the specified uCPE device.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>Selecting the <emphasis role="bold">VNF</emphasis> menu then
+    choosing <emphasis role="bold">Events</emphasis> will show that the VNF
+    was created and a connection was established.</para>
+  </section>
+
+  <section id="enter_console">
+    <title>Accessing the VNF console</title>
+
+    <para>Once the VNF is deployed, the VNF console can be entered using SSH
+    and virsh commands. The VNF Console is a typical starting point for
+    determining a successful deployment and configuring a VNF beyond Day
+    Zero.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>SSH to the uCPE device from the Enea Edge Management (Access the
+        <emphasis role="bold">Device</emphasis> menu and select <emphasis
+        role="bold">SSH</emphasis>) using:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>For normal connections: the <literal>Username</literal>
+            (default: root), the <literal>Password</literal> (default: no
+            password), the <literal>Port</literal> (default: 22) and the
+            <literal>Reverse ssh</literal> checkbox: unchecked.</para>
+          </listitem>
+
+          <listitem>
+            <para>For reverse ssh connections (ssh to a uCPE device behind
+            NAT): the <literal>Username</literal> (default: root) and the
+            <literal>Reverse ssh</literal> checkbox checked. The port will be
+            automatically chosen by the Enea Edge Management in the range
+            defined in the <emphasis role="bold">SSH</emphasis> configuration
+            panel, available when accessing <emphasis
+            role="bold">System</emphasis>, then <emphasis
+            role="bold">Configuration</emphasis> and choosing <emphasis
+            role="bold">Reverse SSH</emphasis> . By default, the start port
+            will be <literal>7000</literal> and the maximum number of ports
+            allocated to all devices is 10. Only one port per device is
+            allowed.</para>
+
+            <para>When the SSH window is closed, the tunnel configuration is
+            deleted on the uCPE device and the tunnel is destroyed, so that
+            the port can be reused to establish a new tunnel when
+            needed.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>In SSH:</para>
+
+        <orderedlist spacing="compact">
+          <listitem>
+            <para>Use the <command>virsh list</command> command to list all
+            running VNFs and to determine the VNF's instance number.</para>
+          </listitem>
+
+          <listitem>
+            <para>Use the <command>virsh console &lt;instance
+            number&gt;</command> command to enter the VNF-specific
+            console.</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
diff --git a/doc/book-enea-edge-getting-started/swcomp.mk b/doc/book-enea-edge-getting-started/swcomp.mk
new file mode 100755
index 0000000..41e4416
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-getting-started
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Getting Started"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)