getting started: add in-band management section

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

3 files changed, 46 insertions, 2 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/book.xml b/doc/book-enea-nfv-access-getting-started/doc/book.xml
index 3ba3241..b0b0534 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/book.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/book.xml
@@ -32,6 +32,8 @@
                           
   <xi:include href="device_configuration_and_provisioning.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />                       
+  <xi:include href="in_band_management.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
                           
   <xi:include href="demo_usecases.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml b/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml
new file mode 100755
index 0000000..fa5a2a8
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/in_band_management.xml
@@ -0,0 +1,41 @@
+<?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="in_band_managemen">
+  <title>In-band Management</title>
+
+  <para>In-band Management refers to administrative access to systems and
+  network devices, over the same network used by the traffic being
+  filtered.</para>
+
+  <para>In some situations, In-band Management can represent a significant
+  risk to the administrator if certain precautions are not taken. These risks
+  center predominantly around the use of unencrypted communications channels.
+  In other cases, In-Band Management is the only option available to both
+  control and configure the device, while also allowing for data-path traffic
+  to pass over the same physical interface. This use-case is required on a
+  setup with a poor infrastructure configuration. The main requirement for this
+  use-case solution is to have all traffic pass through a defined WAN physical
+  port. Three types of traffic are mentioned:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>Device management - e.g.: firmware upgrades done by the uCPE Manager.</para>
+    </listitem>
+
+    <listitem>
+      <para>VNFs configuration - like enabling or disabling the firewall, the
+      VPN or other features.</para>
+    </listitem>
+
+    <listitem>
+      <para>Data-path - all the other traffic that needs to reach a LAN
+      network. <remark>This is not ever clear, it needs to be a explain a
+      little bit better.</remark></para>
+    </listitem>
+  </itemizedlist>
+
+  <para>For use-cases where latency is very important, it is recommended to
+  use out-of-band management with a dedicated physical interface for the
+  data-path.</para>
+</chapter>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
index 6cf8a8a..30934e1 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -104,8 +104,9 @@
 
     <para>For additional information about the features provided in Enea NFV Access,
     refer to the <olink>Reference Guide</olink> provided with your release. For how to
-    install and run Enea NFV Access on supported devices, please refer to <xref>Chapter
-    4, Getting Started with Enea NFV Access</xref>.</para>
+    install and run Enea NFV Access on supported devices, please refer to <xref
+    linkend="plat-release-content">
+    Chapter 4, Getting Started with Enea NFV Access</xref>.</para>
   </section>
 
   <section id="ucpe_manager">