path: root/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="sdwan_arch_evalkit">
  <title>SD-WAN Branch to Branch Connection</title>

  <para>Software-Defined Wide Area Networking (SD-WAN), provides the benefits
  of software-defined networking (SDN) technology to traditionally
  hardware-based networking. It is an overlay architecture providing a
  networking foundation that is much easier to manage than legacy WANs,
  essentially moving the control layer to the cloud and in the process,
  centralizing and simplifying network management. This overlay design
  abstracts software from hardware, enabling network virtualization and making
  the network more elastic.</para>

  <para>The setup detailed in this chapter covers all the steps required to
  create a connection between two branch offices. On each site a uCPE device
  is installed and connected to a WAN network. NFV Access should be installed
  on each uCPE device, and flexiWAN and pfSense VNFs will be instantiated on
  each site.</para>

  <para>The flexiWAN VNF will create the tunnel between the two branches while
  the pfSense VNF (connected in the service chain), will cover the
  communication with LAN on each branch. The setup will be configured from the
  uCPE Manager GUI.</para>

  <figure>
    <title>Branch to Branch Connection Overview</title>

    <mediaobject>
      <imageobject>
        <imagedata align="center" contentwidth="600"
                   fileref="images/br_to_br_conn_setup.png" />
      </imageobject>
    </mediaobject>
  </figure>

  <para>The figure above represents the uCPE configuration of one of the
  branches. The second uCPE device (site2) will be configured in a similar
  way, described in the following sections.</para>

  <para>Since there is only one physical network interface connected to WAN,
  the configuration allows for multiple types of traffic to pass over this
  interface. The <literal>ibm_br</literal> bridge is the main bridge that
  connects the physical network interface to the virtual
  infrastructure.</para>

  <para>The Data-Path represents the traffic that passes over the physical
  interface between the in-band management bridge (<literal>ibm_br</literal>),
  the flexiWAN VNF, the service chain bridge (<literal>sfc_br</literal>), the
  pfSense VNF, and the <literal>lan_br</literal> bridge to finally reach the
  LAN.</para>

  <para>The VNF management interface for the pfSense VNF can be accessed from
  WAN using a web browser. VNF management for flexiWAN is done from a
  centralized management location where the user needs an account in order to
  have access. Please contact the flexiWAN VNF provider before beginning to
  set up the configuration.</para>

  <para>For infrastructure configuration of each uCPE device Zero Touch
  Provisioning (ZTP) will be used. This is a feature that allows the user to
  create an offline configuration before starting and connecting a uCPE device
  to the uCPE Manager. NFV Access allows a user to preconfigure interfaces and
  bridges using ZTP so that, all that is left to do in order to have a full
  setup running correctly after adding uCPE devices, is simply instantiation
  of the VNFs on the designated devices.</para>

  <section id="prelim_setup">
    <title>Preliminary Setup</title>

    <orderedlist>
      <listitem>
        <para>Connect each uCPE device to the network/Internet using one
        physical interface as the designated WAN access interface.</para>

        <note>
          <para>The uCPE device must have Internet access beforehand.</para>
        </note>
      </listitem>

      <listitem>
        <para>Install NFV Access on the uCPE devices. See the <remark>make
        this into an olink</remark> Enea NFV Access Getting Started manual,
        chapter Getting Started with the Enea NFV Access, for more
        details.</para>
      </listitem>

      <listitem>
        <para>Install the uCPE Manager on the CentOS host or VM. See the
        <remark>make this into an olink</remark> Enea NFV Access Getting
        Started manual, chapter Getting Started with Enea uCPE Manager, for
        more details.</para>

        <note>
          <para>The uCPE Manager host machine must be connected to the network
          so all uCPE devices can access it.</para>
        </note>
      </listitem>

      <listitem>
        <para>Connect to the uCPE Manager: <literal>https://&lt;uCPE Manager
        IP&gt;</literal></para>
      </listitem>
    </orderedlist>
  </section>

  <section id="ucpe_mg_evalkit221">
    <title>The uCPE Manager</title>

    <para>Log into the uCPE Manager using the default credentials,
    username:admin and password: admin.</para>

    <para>Zero Touch Provisioning (ZTP) will be used to preconfigure the
    infrastructure in the uCPE Manager for each device. The interface and
    bridge configurations are pushed onto each uCPE device when
    connected.</para>

    <para>Onboarding is the process of registering VNFs into the uCPE Manager
    after devices are configured. The flexiWAN and pfSense VNFs are used along
    with example configuration data.</para>

    <section id="onboard_flexiwan_vnf">
      <title>Onboarding the FlexiWAN VNF</title>

      <para>Add a VNF by accessing the <literal>VNF</literal> menu from the
      top toolbar then <literal>Descriptors</literal> -&gt;
      <literal>On-board</literal> -&gt; <literal>VM Image</literal>.</para>

      <para>Use the following values to fill the required fields:</para>

      <table>
        <tgroup cols="2">
          <tbody>
            <row>
              <entry>VM image file</entry>

              <entry>
                <literal>flexiWAN.qcow2</literal>
              </entry>
            </row>

            <row>
              <entry>Image format</entry>

              <entry>QCOW2</entry>
            </row>

            <row>
              <entry>VNF Type Name</entry>

              <entry>flexiWAN</entry>
            </row>

            <row>
              <entry>Description</entry>

              <entry>Flexiwan VNF</entry>
            </row>

            <row>
              <entry>Version</entry>

              <entry>1.0</entry>
            </row>

            <row>
              <entry>Memory in MB</entry>

              <entry>4096. More memory can be allocated if required.</entry>
            </row>

            <row>
              <entry>Num of CPUs</entry>

              <entry>2. More CPUs can be reserved if required and
              available.</entry>
            </row>

            <row>
              <entry>Interfaces to add (click the " + " button):</entry>

              <entry>wan and lan. Please make sure to add them in this order.</entry>
            </row>

            <row>
              <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>

              <entry>ISO</entry>
            </row>

            <row>
              <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>

              <entry>cdrom</entry>
            </row>

            <row>
              <entry>Onboard</entry>

              <entry>Wait for the message: "VNF package onboarded
              successfully" then close the pop-up.</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </section>

    <section id="onboard_pfsense_vnf">
      <title>Onboarding the pfSense VNF</title>

      <para>Add the other VNF by accessing the <literal>VNF</literal> menu
      from the top toolbar once again, then <literal>Descriptors</literal>
      -&gt; <literal>On-board</literal> -&gt; <literal>VM
      Image</literal>.</para>

      <para>Use the following values to fill the required fields:</para>

      <table>
        <tgroup cols="2">
          <tbody>
            <row>
              <entry>VM image file</entry>

              <entry>
                <literal>pfSense.qcow2</literal>
              </entry>
            </row>

            <row>
              <entry>Image format</entry>

              <entry>QCOW2</entry>
            </row>

            <row>
              <entry>VNF Type Name</entry>

              <entry>pfSense</entry>
            </row>

            <row>
              <entry>Description</entry>

              <entry>pfSense VNF</entry>
            </row>

            <row>
              <entry>Version</entry>

              <entry>1.0</entry>
            </row>

            <row>
              <entry>Memory in MB</entry>

              <entry>1024</entry>
            </row>

            <row>
              <entry>Num of CPUs</entry>

              <entry>1</entry>
            </row>

            <row>
              <entry>Interfaces to add (click the " + " button):</entry>

              <entry>wan, lan and mgmt. Please make sure to add them in this order.</entry>
            </row>

            <row>
              <entry>Cloud Init -&gt; Cloud-Init Datasource</entry>

              <entry>ISO</entry>
            </row>

            <row>
              <entry>Cloud Init -&gt; Cloud-Init Disk Type</entry>

              <entry>cdrom</entry>
            </row>

            <row>
              <entry>Properties to add (click the " + " button):</entry>

              <entry>
                <itemizedlist>
                  <listitem>
                    <para>Name: <literal>vnfMgmtIpAddress</literal>. Value:
                    10.0.0.3<superscript>1</superscript></para>
                  </listitem>

                  <listitem>
                    <para>Name: <literal>internalMgmtPort</literal>. Value:
                    443<superscript>2</superscript></para>
                  </listitem>

                  <listitem>
                    <para>Name: <literal>externalMgmtPort</literal>. Value:
                    60002<superscript>3</superscript></para>
                  </listitem>
                </itemizedlist>
              </entry>
            </row>

            <row>
              <entry>Onboard</entry>

              <entry>Wait for the message: "VNF package onboarded
              successfully" then close the pop-up.</entry>
            </row>
          </tbody>
        </tgroup>
      </table>

      <para>Please note the following:</para>

      <itemizedlist>
        <listitem>
          <para><superscript>1</superscript>vnfMgmtIpAddress (10.0.0.3)
          represents the IP address of the management interface of the pfSense
          VNF. Changing this value requires an update of the pfSense
          configuration to match the new IP address.</para>
        </listitem>

        <listitem>
          <para><superscript>2</superscript>HTTPS access (443) can be changed
          to another type of access. Please consult the official pfSense
          documentation for more details and make sure the pfSense VNF is
          configured to accept another type of connection before changing the
          port number.</para>
        </listitem>

        <listitem>
          <para><superscript>3</superscript>externalMgmtPort (60002)
          represents the external port on which a user can access the VNF
          management interface from a web browser. The user can select another
          port if needed. There are no other changes required or components
          affected by this change.</para>
        </listitem>
      </itemizedlist>
    </section>

    <section id="offline_config_ucpe_device1">
      <title>Offline Configuration for uCPE device1</title>

      <para>A Zero Touch Provisioning configuration for a device is done in
      two steps from the uCPE Manager's GUI. The first step is to create a
      data store and then to add the offline configuration for the device
      infrastructure into that data store.</para>

      <orderedlist>
        <listitem>
          <para><emphasis role="bold">Create the "device1" data
          store</emphasis>: <literal>Applications</literal> -&gt;
          <literal>Offline Config</literal> -&gt;
          <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields:</para>

          <table>
            <tgroup cols="2">
              <colspec align="left" />

              <tbody>
                <row>
                  <entry>Name</entry>

                  <entry>
                    <literal>device1</literal>
                  </entry>
                </row>

                <row>
                  <entry>Device Type</entry>

                  <entry>Enea universal CPE</entry>
                </row>

                <row>
                  <entry>Device Version</entry>

                  <entry>2.2.1</entry>
                </row>

                <row>
                  <entry>Config Set</entry>

                  <entry>uCPE Config</entry>
                </row>

                <row>
                  <entry>
                    <literal>deviceId</literal>
                  </entry>

                  <entry>The ID extracted from <literal>device1</literal>
                  after running <filename>list_deviceID.sh</filename> on the
                  NFV Access CLI. </entry>
                </row>
              </tbody>
            </tgroup>
          </table>

          <para>Press the Create button.</para>
        </listitem>

        <listitem>
          <para>Prepare the infrastructure configuration for
          <literal>device1</literal> in the data store:
          <literal>Applications</literal> -&gt; <literal>Offline
          Config</literal> -&gt; &lt;select "device1" data store&gt; -&gt;
          <literal>Config App...</literal>. This window layout is very similar
          to the Configuration window of a device.</para>
        </listitem>

        <listitem>
          <para>Disable the DPDK: <literal>DPDK</literal> -&gt;
          <literal>Advanced Settings</literal> -&gt; uncheck <literal>Enable
          DPDK</literal> to disable the DPDK and click "Create".</para>
        </listitem>

        <listitem>
          <para><emphasis role="bold">Configure the host
          interface(s):</emphasis> <literal>OpenVSwitch</literal> -&gt;
          <literal>Host Interfaces</literal> -&gt;
          <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields:</para>

          <itemizedlist>
            <listitem>
              <para><emphasis role="bold">Source</emphasis>:
              <literal>enp7s0f1</literal>. <note>
                  <para>This is just an example interface. The user must
                  select the interface needed for use with the LAN connection.
                  To locate the name of the interface, run
                  <command>ifconfig</command> on the NFV Access CLI.</para>
                </note></para>
            </listitem>

            <listitem>
              <para><emphasis role="bold">networking-type</emphasis>:
              standard.</para>
            </listitem>
          </itemizedlist>

          <para>Click <literal>Create</literal>, and the
          <literal>enp7s0f1</literal> interface will be ready to use in a
          bridge (LAN).</para>
        </listitem>

        <listitem>
          <para><emphasis role="bold">Configure the bridges</emphasis>:
          <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>
          -&gt; <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields for the
          four bridges that need to be created: <itemizedlist>
              <listitem>
                <para><literal>ibm_br</literal>:</para>

                <itemizedlist spacing="compact">
                  <listitem>
                    <para><emphasis role="bold">Name</emphasis>:
                    <literal>ibm_br</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                    <literal>inbandMgmt</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">mgmt-address</emphasis>:
                    Provide the IPv4 address of the uCPE Manager machine (E.g.
                    172.24.3.109).</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">mgmt-port</emphasis>:
                    830.</para>
                  </listitem>
                </itemizedlist>

                <para>Click <literal>Create</literal>.</para>
              </listitem>

              <listitem>
                <para><literal>vnf_mgmt_br</literal>:</para>

                <itemizedlist spacing="compact">
                  <listitem>
                    <para><emphasis role="bold">Name</emphasis>:
                    <literal>vnf_mgmt_br</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                    <literal>vnfMgmt</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
                    10.0.0.1</para>
                  </listitem>
                </itemizedlist>

                <para>Click <literal>Create</literal>.</para>
              </listitem>

              <listitem>
                <para><literal>sfc_br</literal>:</para>

                <itemizedlist spacing="compact">
                  <listitem>
                    <para><emphasis role="bold">Name</emphasis>:
                    <literal>sfc_br</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                    <literal>dataPlane</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">Sub-type</emphasis>:
                    integration.</para>
                  </listitem>
                </itemizedlist>

                <para>Click <literal>Create</literal>.</para>
              </listitem>

              <listitem>
                <para><literal>lan_br</literal>:</para>

                <itemizedlist spacing="compact">
                  <listitem>
                    <para><emphasis role="bold">Name</emphasis>:
                    <literal>lan_br</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                    <literal>dataPlane</literal>.</para>
                  </listitem>

                  <listitem>
                    <para><emphasis role="bold">Sub-type</emphasis>:
                    communication. Name: <literal>enp7s0f1</literal></para>
                  </listitem>
                </itemizedlist>

                <para>Click <literal>Create</literal>.</para>
              </listitem>
            </itemizedlist></para>
        </listitem>
      </orderedlist>
    </section>

    <section id="offline_config_ucpe_device2">
      <title>Offline Configuration for uCPE device2</title>

      <para>A Zero Touch Provisioning configuration for a device is done in
      two steps from the uCPE Manager's GUI. The first step is to create a
      data store and then to add the offline configuration for the device
      infrastructure into that data store.</para>

      <orderedlist>
        <listitem>
          <para><emphasis role="bold">Create the "device2" data
          store</emphasis>: <literal>Applications</literal> -&gt;
          <literal>Offline Config</literal> -&gt;
          <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields:</para>

          <table>
            <tgroup cols="2">
              <colspec align="left" />

              <tbody>
                <row>
                  <entry>Name</entry>

                  <entry>
                    <literal>device2</literal>
                  </entry>
                </row>

                <row>
                  <entry>Device Type</entry>

                  <entry>Enea universal CPE</entry>
                </row>

                <row>
                  <entry>Device Version</entry>

                  <entry>2.2.1</entry>
                </row>

                <row>
                  <entry>Config Set</entry>

                  <entry>uCPE Config</entry>
                </row>

                <row>
                  <entry>
                    <literal>deviceId</literal>
                  </entry>

                  <entry>The ID extracted from <literal>device2</literal>
                  after running <filename>list_deviceID.sh</filename> on the
                  NFV Access CLI. </entry>
                </row>
              </tbody>
            </tgroup>
          </table>

          <para>Press the Create button.</para>
        </listitem>

        <listitem>
          <para>Prepare the infrastructure configuration for
          <literal>device2</literal> in the data store:
          <literal>Applications</literal> -&gt; <literal>Offline
          Config</literal> -&gt; &lt;select "device2" data store&gt; -&gt;
          <literal>Config App...</literal>. This window layout is very similar
          to the Configuration window of a device.</para>
        </listitem>

        <listitem>
          <para>Disable the DPDK: <literal>DPDK</literal> -&gt;
          <literal>Advanced Settings</literal> -&gt; uncheck <literal>Enable
          DPDK</literal> to disable the DPDK and click "Create".</para>
        </listitem>

        <listitem>
          <para><emphasis role="bold">Configure the host
          interface(s):</emphasis><literal> OpenVSwitch</literal> -&gt;
          <literal>Host Interfaces</literal> -&gt;
          <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields:</para>

          <itemizedlist>
            <listitem>
              <para><emphasis role="bold">Source</emphasis>:
              <literal>eno4</literal>. <note>
                  <para>This is just an example interface. The user must
                  select the interface needed for use with the LAN connection.
                  To locate the name of the interface, run
                  <command>ifconfig</command> on the NFV Access CLI.</para>
                </note></para>
            </listitem>

            <listitem>
              <para><emphasis role="bold">networking-type</emphasis>:
              standard.</para>
            </listitem>
          </itemizedlist>

          <para>Click <literal>Create</literal>, and the
          <literal>eno4</literal> interface will be ready to use in a bridge
          (LAN).</para>
        </listitem>

        <listitem>
          <para><emphasis role="bold">Configure the bridges</emphasis>:
          <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>
          -&gt; <literal>Add</literal>.</para>

          <para>Use the following values to fill the required fields for the
          four bridges that need to be created:</para>

          <itemizedlist>
            <listitem>
              <para><literal>ibm_br</literal>:</para>

              <itemizedlist spacing="compact">
                <listitem>
                  <para><emphasis role="bold">Name</emphasis>:
                  <literal>ibm_br</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                  <literal>inbandMgmt</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">mgmt-address</emphasis>: Provide
                  the IPv4 address of the uCPE Manager machine (E.g.
                  172.24.3.109).</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">mgmt-port</emphasis>:
                  830.</para>
                </listitem>
              </itemizedlist>

              <para>Click <literal>Create</literal>.</para>
            </listitem>

            <listitem>
              <para><literal>vnf_mgmt_br</literal>:</para>

              <itemizedlist spacing="compact">
                <listitem>
                  <para><emphasis role="bold">Name</emphasis>:
                  <literal>vnf_mgmt_br</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                  <literal>vnfMgmt</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">vnf-mgmt-address</emphasis>:
                  10.0.0.1</para>
                </listitem>
              </itemizedlist>

              <para>Click <literal>Create</literal>.</para>
            </listitem>

            <listitem>
              <para><literal>sfc_br</literal>:</para>

              <itemizedlist spacing="compact">
                <listitem>
                  <para><emphasis role="bold">Name</emphasis>:
                  <literal>sfc_br</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                  <literal>dataPlane</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">Sub-type</emphasis>:
                  integration.</para>
                </listitem>
              </itemizedlist>

              <para>Click <literal>Create</literal>.</para>
            </listitem>

            <listitem>
              <para><literal>lan_br</literal>:</para>

              <itemizedlist spacing="compact">
                <listitem>
                  <para><emphasis role="bold">Name</emphasis>:
                  <literal>lan_br</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">ovs-bridge-type</emphasis>:
                  <literal>dataPlane</literal>.</para>
                </listitem>

                <listitem>
                  <para><emphasis role="bold">Sub-type</emphasis>:
                  communication.</para>

                  <para>Name: <literal>eno4</literal></para>
                </listitem>
              </itemizedlist>

              <para>Click <literal>Create</literal>.</para>
            </listitem>
          </itemizedlist>
        </listitem>
      </orderedlist>
    </section>

    <section id="upload_offline_config">
      <title>Uploading the offline Configuration</title>

      <para>The offline configuration can be uploaded and applied on a uCPE
      device only once. If the setup needs to be rerun on a device where ZTP
      was already used, please do the following:</para>

      <orderedlist spacing="compact">
        <listitem>
          <para>Add the device manually from the uCPE manager GUI.</para>
        </listitem>

        <listitem>
          <para>Clean the entire configuration on the device.</para>
        </listitem>

        <listitem>
          <para>Reset the ZTP: <literal>device</literal> -&gt; Configuration
          -&gt; Host -&gt; initial-config-complete: false -&gt; Apply.</para>
        </listitem>

        <listitem>
          <para>Delete the device from the uCPE Manager.</para>
        </listitem>
      </orderedlist>
    </section>
  </section>

  <section id="add_ucpe1_mg">
    <title>Adding the uCPE device1 into the uCPE Manager</title>

    <para>Access the <literal>Devices</literal> menu, then
    <literal>Manage</literal> -&gt; <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <table>
      <tgroup cols="2">
        <colspec align="left" />

        <tbody>
          <row>
            <entry>Type</entry>

            <entry>Enea universal CPE</entry>
          </row>

          <row>
            <entry>Release</entry>

            <entry>2.2.1</entry>
          </row>

          <row>
            <entry>Name</entry>

            <entry>Ucpe1</entry>
          </row>

          <row>
            <entry>IP/DNS Address</entry>

            <entry>Dynamic IP received by the device from the DHCP server
            (E.g. 172.24.12.74).</entry>
          </row>

          <row>
            <entry>Description</entry>

            <entry>ucpe device site 1</entry>
          </row>

          <row>
            <entry>SSH Port</entry>

            <entry>830</entry>
          </row>

          <row>
            <entry>SSH User Name</entry>

            <entry>root</entry>
          </row>

          <row>
            <entry>Password</entry>

            <entry />
          </row>

          <row>
            <entry>Device ID</entry>

            <entry>Extract the device ID from device1, by running
            <literal>list_deviceID.sh</literal>.</entry>
          </row>

          <row>
            <entry>OK</entry>

            <entry>
              <itemizedlist>
                <listitem>
                  <para>Green status indicates connection with the device was
                  established.</para>
                </listitem>

                <listitem><para>To add the device on the map: Right-Click on
                the Map -&gt; Place Device -&gt; Ucpe1</para>.</listitem>
              </itemizedlist>
            </entry>
          </row>
        </tbody>
      </tgroup>
    </table>
  </section>

  <section id="add_ucpe2_mg">
    <title>Adding the uCPE device2 into the uCPE Manager</title>

    <para>Access the <literal>Devices</literal> menu, then
    <literal>Manage</literal> -&gt; <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <table>
      <tgroup cols="2">
        <colspec align="left" />

        <tbody>
          <row>
            <entry>Type</entry>

            <entry>Enea universal CPE</entry>
          </row>

          <row>
            <entry>Release</entry>

            <entry>2.2.1</entry>
          </row>

          <row>
            <entry>Name</entry>

            <entry>Ucpe2</entry>
          </row>

          <row>
            <entry>IP/DNS Address</entry>

            <entry>Dynamic IP received by the device from the DHCP server
            (E.g. 172.24.12.74).</entry>
          </row>

          <row>
            <entry>Description</entry>

            <entry>ucpe device site 2</entry>
          </row>

          <row>
            <entry>SSH Port</entry>

            <entry>830</entry>
          </row>

          <row>
            <entry>SSH User Name</entry>

            <entry>root</entry>
          </row>

          <row>
            <entry>Password</entry>

            <entry />
          </row>

          <row>
            <entry>Device ID</entry>

            <entry>Extract the device ID from device2, by running
            <literal>list_deviceID.sh</literal>.</entry>
          </row>

          <row>
            <entry>OK</entry>

            <entry>
              <itemizedlist>
                <listitem>
                  <para>Green status indicates connection with the device was
                  established.</para>
                </listitem>

                <listitem><para>To add the device on the map: Right-Click on
                the Map -&gt; Place Device -&gt; Ucpe2</para>.</listitem>
              </itemizedlist>
            </entry>
          </row>
        </tbody>
      </tgroup>
    </table>

    <para>After the two devices are added into the uCPE Manager all offline
    configuration data prepared for them is pushed automatically onto the
    devices. To check if a device is configured, add the device onto the map
    and select &lt;Ucpe1&gt; -&gt; <literal>Configuration</literal> -&gt;
    <literal>OpenVSwitch</literal> -&gt; <literal>Bridges</literal>.</para>
  </section>

  <section id="flexiwan_inst_device1">
    <title>FlexiWAN VNF Instantiation on device1</title>

    <para>Instantiate the FlexiWAN VNF by selecting the Ucpe1 device, then the
    VNF menu -&gt; <literal>Instances</literal> -&gt;
    <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <itemizedlist>
      <listitem>
        <para><emphasis role="bold">Name:</emphasis>
        <literal>Flexiwan_ucpe1</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNF Type:</emphasis>
        <literal>flexiWAN</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Cloud Init File:</emphasis>
        <filename>flexiWAN_cloudinit.iso</filename>.</para>

        <note>
          <para>Example cloud-init image provided. Please see the Appendix for
          details on how to generate a new cloud-init image with a different
          token. Please contact flexiWAN in order to get a valid token and
          access to the flexiWAN manager.</para>
        </note>
      </listitem>

      <listitem>
        <para>Create the <literal>wan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>wan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>ibm_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>lan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>lan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>sfc_br</literal>.</para>

        <para>Click <literal>Create</literal>.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="pfSense_inst_device1">
    <title>pfSense VNF Instantiation on device1</title>

    <para>Instantiate the pfSense VNF by selecting the ucpe1 device, then the
    VNF menu -&gt; <literal>Instances</literal> -&gt;
    <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <itemizedlist>
      <listitem>
        <para><emphasis role="bold">Name:</emphasis>
        <literal>Pfsense_ucpe1</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNF Type:</emphasis>
        <literal>pfSense</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe1.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Cloud Init File:</emphasis>
        <filename>pfsense_192_168_1_1.iso</filename>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>wan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>wan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>sfc_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>lan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>lan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>lan_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>mgmt</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>mgmt</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>vnf_mgmt_br</literal>.</para>

        <para>Click <literal>Create</literal>.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="flexiwan_inst_device2">
    <title>FlexiWAN VNF Instantiation on device2</title>

    <para>Instantiate the FlexiWAN VNF by selecting the ucpe2 device, then the
    VNF menu -&gt; <literal>Instances</literal> -&gt;
    <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <itemizedlist>
      <listitem>
        <para><emphasis role="bold">Name:</emphasis>
        <literal>Flexiwan_ucpe2</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNF Type:</emphasis>
        <literal>flexiWAN</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Cloud Init File:</emphasis>
        <filename>flexiWAN_cloudinit.iso</filename>.</para>

        <note>
          <para>Example cloud-init image provided. Please see the Appendix for
          details on how to generate a new cloud-init image with a different
          token. Please contact flexiWAN in order to get a valid token and
          access to the flexiWAN manager.</para>
        </note>
      </listitem>

      <listitem>
        <para>Create the <literal>wan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>wan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>ibm_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>lan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>lan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>sfc_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>

        <para>Click <literal>Create</literal>.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="pfSense_inst_device2">
    <title>pfSense VNF Instantiation on device2</title>

    <para>Instantiate the pfSense VNF by selecting the ucpe2 device, then the
    VNF menu -&gt; <literal>Instances</literal> -&gt;
    <literal>Add</literal>.</para>

    <para>Use the following values to fill the required fields:</para>

    <itemizedlist>
      <listitem>
        <para><emphasis role="bold">Name:</emphasis>
        <literal>Pfsense_ucpe2</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNF Type:</emphasis>
        <literal>pfSense</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">VNFD Version:</emphasis> 1.0.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Flavour:</emphasis> Canonical.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">uCPE Device:</emphasis> Ucpe2.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Cloud Init File:</emphasis>
        <filename>pfsense_192_168_2_1.iso</filename>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>wan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>wan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>sfc_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>lan</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>lan</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>lan_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>
      </listitem>

      <listitem>
        <para>Create the <literal>mgmt</literal> Interface:</para>

        <para><emphasis role="bold">ID:</emphasis>
        <literal>mgmt</literal>.</para>

        <para><emphasis role="bold">Type:</emphasis>
        <literal>tap</literal>.</para>

        <para><emphasis role="bold">IF Name:</emphasis> Bridge:
        <literal>vnf_mgmt_br</literal>.</para>

        <para><emphasis role="bold">NIC Model</emphasis>:
        <literal>virtio</literal>.</para>

        <para>Click <literal>Create</literal>.</para>
      </listitem>
    </itemizedlist>

    <para>Once all VNFs are up and running, the setup is ready for final VNF
    configuration and testing.</para>

    <figure>
      <title>SD-WAN branch-to-branch connection setup Overview</title>

      <mediaobject>
        <imageobject>
          <imagedata align="center" contentwidth="600"
                     fileref="images/br_to_br_conn_overview.png" />
        </imageobject>
      </mediaobject>
    </figure>

    <para>In order to have the full setup working properly, a tunnel between
    two SD-WAN devices needs to be created. The FlexiWAN VNF provides the
    functionality to create the VPN tunnel.</para>
  </section>

  <section id="flexiwan_config">
    <title>FlexiWAN configuration</title>

    <para>Connect to <ulink
    url="https://manage.flexiwan.com">https://manage.flexiwan.com</ulink> and make
    sure to have an account and at least two valid device tokens. For more
    information please contact the flexiWAN VNF provider.</para>

    <para>Proceed to the Inventory menu and click on <literal>Devices</literal>,
    the devices should already be present and need to be configured.</para>

    <para><emphasis role="bold">How to configure a device</emphasis></para>

    <orderedlist>
      <listitem>
        <para>Select each Unknown device and make sure to set the following
        values:</para>

        <para><table>
            <tgroup cols="2">
              <tbody>
                <row>
                  <entry>Device1 (ucpe1)</entry>

                  <entry>Device2 (ucpe2)</entry>
                </row>

                <row>
                  <entry>Device Name: Device1</entry>

                  <entry>Device Name: Device2</entry>
                </row>

                <row>
                  <entry>Description: uCPE device1 </entry>

                  <entry>Description: uCPE device2 </entry>
                </row>

                <row>
                  <entry>Set "Approved".</entry>

                  <entry>Set "Approved".</entry>
                </row>

                <row>
                  <entry>Click "Update Device" button.</entry>

                  <entry>Click "Update Device" button.</entry>
                </row>

                <row>
                  <entry>Select Interfaces tab.</entry>

                  <entry>Select Interfaces tab.</entry>
                </row>

                <row>
                  <entry>Set IPv4 for the second interface
                  (ens3): <literal>10.0.1.1/24</literal></entry>

                  <entry>Set IPv4 for the second interface
                  (ens3): <literal>10.0.2.1/24</literal></entry>
                </row>

                <row>
                  <entry>Click "Update Interfaces".</entry>

                  <entry>Click "Update Interfaces".</entry>
                </row>

              </tbody>
            </tgroup>
          </table></para>

        <note>
          <para>uCPE devices can installed under the same local network, i.e.
          having the same public IP, or on different networks (different
          public IPs). If both devices are installed under the same local network
            (the same public IP), delete the public IP address from the <literal>Interfaces</literal>
          configuration tab before creating a tunnel: <ulink
          url="https://manage.flexiwan.com">https://manage.flexiwan.com</ulink>
          -&gt; <literal>Inventory</literal> -&gt; <literal>Devices</literal>
          -&gt; <literal>&lt;device&gt;</literal> -&gt; <literal>Interfaces</literal>
          -&gt; Public IP.</para>
        </note>
      </listitem>

      <listitem>
        <para>Select the "&gt;" option for each device to be put in the
        "running" state.</para>
      </listitem>

      <listitem>
        <para>Wait for each "vRouter" device to also enter the "running"
        state.</para>
      </listitem>

      <listitem>
        <para>Select the main top up checkbox in order to select all devices
            and hit "Actions" -&gt; "Create Tunnels". At this moment a direct
            connection should be available between those two devices. Check to 
          see if the tunnel was created by selecting <literal>Inventory</literal>
          -&gt; <literal>Tunnels</literal>.</para>
      </listitem>
    </orderedlist>
  </section>

  <section id="pfsense_config">
    <title>pfSense configuration</title>

    <para>For the pfSense VNF there is no need for manual configuration. The
    configuration provided into the cloud init image is good enough to run the
    setup.</para>

    <para>The management interface can be accessed from a web browser at:
    <literal>https://&lt;deviceIP&gt;:60002</literal></para>
  </section>
</chapter>