From d4c47887344cf9fb4b91426aadf5a7dfc481df2f Mon Sep 17 00:00:00 2001 From: mrpa Date: Fri, 20 Dec 2019 12:51:25 +0100 Subject: Correcting the file name. Change-Id: I7bdc7d088aa2dda79f0333d48680f8f8cd867d01 --- doc/Makefile | 2 +- .../doc/appendix_1.xml | 35 - .../doc/book.xml | 38 - .../doc/eltf_params_updated.xml | 209 --- .../doc/images/br_to_br_conn_overview.png | Bin 95022 -> 0 bytes .../doc/images/br_to_br_conn_setup.png | Bin 79858 -> 0 bytes .../doc/introduction.xml | 76 -- .../doc/prerequisites.xml | 113 -- .../doc/run_example_uc_auto_fm.xml | 38 - .../doc/sdwan_arch.xml | 1439 -------------------- .../doc/setup_cleanup.xml | 61 - .../doc/validating_setup.xml | 36 - doc/book-enea-nfv-access-evalkit-2.2.1/swcomp.mk | 10 - .../doc/appendix_1.xml | 35 + doc/book-enea-nfv-access-evalkit/doc/book.xml | 38 + .../doc/eltf_params_updated.xml | 209 +++ .../doc/images/br_to_br_conn_overview.png | Bin 0 -> 95022 bytes .../doc/images/br_to_br_conn_setup.png | Bin 0 -> 79858 bytes .../doc/introduction.xml | 76 ++ .../doc/prerequisites.xml | 113 ++ .../doc/run_example_uc_auto_fm.xml | 38 + .../doc/sdwan_arch.xml | 1439 ++++++++++++++++++++ .../doc/setup_cleanup.xml | 61 + .../doc/validating_setup.xml | 36 + doc/book-enea-nfv-access-evalkit/swcomp.mk | 10 + 25 files changed, 2056 insertions(+), 2056 deletions(-) delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/eltf_params_updated.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_overview.png delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_setup.png delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml delete mode 100644 doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml delete mode 100755 doc/book-enea-nfv-access-evalkit-2.2.1/swcomp.mk create mode 100644 doc/book-enea-nfv-access-evalkit/doc/appendix_1.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/book.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/eltf_params_updated.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_overview.png create mode 100644 doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_setup.png create mode 100644 doc/book-enea-nfv-access-evalkit/doc/introduction.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/run_example_uc_auto_fm.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml create mode 100644 doc/book-enea-nfv-access-evalkit/doc/validating_setup.xml create mode 100755 doc/book-enea-nfv-access-evalkit/swcomp.mk diff --git a/doc/Makefile b/doc/Makefile index 33ade18..1a705d7 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -50,7 +50,7 @@ DOCBOOK_TO_BOOKDIR ?= yes DOCBOOK_CLEANTMP ?= yes #Components (books) in this subsystem. Now use all books found here -COMPONENTS := book-enea-nfv-access-auto-fw-th-user-guide book-enea-nfv-access-cmc-example-usecases book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-open-source book-enea-nfv-access-release-info book-enea-nfv-access-system-test-specification book-enea-nfv-access-evalkit-2.2.1 +COMPONENTS := book-enea-nfv-access-auto-fw-th-user-guide book-enea-nfv-access-cmc-example-usecases book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-open-source book-enea-nfv-access-release-info book-enea-nfv-access-system-test-specification book-enea-nfv-access-evalkit # COMPONENTS += #book-enea-linux-eclipse-open-source #book-enea-nfv-access-dev-hardening-guide diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml deleted file mode 100644 index 0895bcb..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/appendix_1.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - How to create a flexiwan cloud-init iso image (day-0 - configuration) - - Prerequisites: - - - - Development host with a Linux shell. - - - - The Cloud-localds tool installed. - - - - - Contact the flexiWAN VNF provider to get access to their controller - and a valid token. - - - Unpack the - flexiwan/flexiwan-cloud-init-example.tar.gz and check - the README file for more details: tar -zxf flexiwant-cloud-init-example.tar.gz -cd flexiwan/cloud-init-example/ - - To generate the cloud-init iso image: - - > create_flexiwan_cloudinit.sh <token> -> create_flexiwan_cloudinit.sh $cat token.txt - - The flexiWAN_cloudinit.iso file can be used to - instantiate the flexiWAN VNF on NFV Access. - \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml deleted file mode 100644 index f1826e9..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/book.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -]> - - <trademark class="registered">Enea</trademark> NFV Access EvalKit Manual - - Release Version - - - - - - - - - - - - - - - - - - - diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/eltf_params_updated.xml deleted file mode 100644 index 1a640a3..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/eltf_params_updated.xml +++ /dev/null @@ -1,209 +0,0 @@ - - -
- File with Parameters in the Book Auto-updated by ELFT - - - See the eltf_params_updated_template_howto_use.txt text - file for description of how to create the final eltf_params_updated.xml from this template and for - all REQUIREMENTS. Use the command - "make eltf" to extract a full list of all - ELTF variables, which always begins with ELTF_ and don't only rely on the - howto text file list! The plan is that ELTF will auto-update this when - needed. - - -
- Common Parameters - - A programlisting, ID - "eltf-prereq-apt-get-commands-host" - - # Host Ubuntu 16.04 LTS 64bit -sudo apt-get -y update -sudo apt-get -y install sed wget subversion git-core coreutils unzip texi2html \ - texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \ - make gcc build-essential xsltproc g++ desktop-file-utils chrpath \ - libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \ - libxml-parser-perl - - A programlisting, ID - "eltf-getting-repo-install-command" - - mkdir -p ~/bin -curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo -chmod a+x ~/bin/repo -export PATH=~/bin:$PATH - - Several phrase elements, various IDs. Ensure EL_REL_VER is - correct also compared to the "previous" REL VER in pardoc-distro.xml - "prev_baseline". - - 2.2.1 - - 2.4 - - rocko - - http://www.yoctoproject.org/downloads - - https://linux.enea.com/6 - - A programlisting, ID "eltf-repo-cloning-enea-linux". Use - $MACHINE/default.xml as parameter, where MACHINE is one of the target - directory names in the manifest. - - mkdir enea-linux -cd enea-linux -repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \ - -b refs/tags/EL6 -m $MACHINE/default.xml -repo sync - - A table with ONE row, only the row with ID - "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set - condition hidden if eclipse is not in the release. Do this both in - template.xml and updated.xml. - - - - - - Eclipse version 4.3 (Mars) plus command line development - tools are included in this Enea NFV Access release. - - - - - - Below is one big section with title "Supported Processor with - Parameters". The entire section is included completely in the book via ID - "eltf-target-tables-section" and shall be LAST in the template. The - template contains ONE target subsection. COPY/APPEND it, if multiple - targets exist in the release and optionally add rows with additional - target parameters in each target subsection table. -
- -
- Supported Reference Processor with Parameters - - The table(s) below describes the processors supported in this Enea - NFV Access release. - - - Processor Information Intel Xeon D-1500 - - - - - - - Component - - Description - - - - - - Processor official name - - Intel Xeon D-1500 - - - - Architecture and Description - - x86-64 - - - - Link to processor datasheet - - Intel's - datasheet - - - - GCC version - - 7.3 - - - - Linux Kernel Version - - 4.14 - - - - Supported Drivers - - Ethernet, RTC, UART - - - -
- - - Processor Information Intel Atom C3000 - - - - - - - Component - - Description - - - - - - Processor official name - - Intel Atom C3000 - - - - Architecture and Description - - x86-64 - - - - Link to the processor datasheet - - Intel's - datasheet - - - - GCC version - - 7.3 - - - - Linux Kernel Version - - 4.14 - - - - Supported Drivers - - Ethernet, RTC, UART - - - -
-
-
diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_overview.png b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_overview.png deleted file mode 100644 index 977de0f..0000000 Binary files a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_overview.png and /dev/null differ diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_setup.png b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_setup.png deleted file mode 100644 index feb18a3..0000000 Binary files a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/images/br_to_br_conn_setup.png and /dev/null differ diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml deleted file mode 100644 index 7b92bcf..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/introduction.xml +++ /dev/null @@ -1,76 +0,0 @@ - - - Introduction - - The NFV Access EvalKit offered by Enea contains software that can be - used to deploy an SD-WAN setup. The branch-to-branch setup uses two - opensource based VNFs: flexiWAN and pfSense. These VNFs are provided as - examples and the configuration used only works on the documented - setup. - - Enea NFV Access for the universal Customer Premise Equipment (uCPE) is - a virtualization and management platform, which allows end-users to - introduce, instantiate, and run third-party VNFs onto their systems. - - The solution is comprised of two major components working in close - cooperation: - - - - The Enea NFV Access Run-Time Platform, which acts as the host for - Virtualized Network Functions (VNFs) and provides management over - NETCONF. - - - - The Enea uCPE Manager, a solution that runs on an external server, - providing VNF Management functionality and managing large numbers of - uCPEs. - - - - The current Enea NFV Access solution provides a working and deployable - configuration as an example for branch-to-branch connection setup using the - flexiWAN and pfSense VNFs service chained together on a uCPE device. - - This document will present all information required to replicate the - use case described in the user's environment. The first part of this manual - uses the GUI mode of the uCPE Manager to detail the steps in order to - reproduce the use cases, while the chapters thereafter use the automation - framework. - - - All VNF configurations should be seen as example configurations - working in Enea internal lab and the user must update these files with the - configuration data needed according to his network setup. Particularities - are described in Appendix A. - - This document assumes the user is familiar with Enea NFV Access and - has read the Enea NFV Access Getting Started manual before continuing with - the following. - - -
- Definitions and Acronyms - -
- uCPE Manager - - The Enea uCPE Manager is an EMS/NMS platform providing VNF - Management capabilities for NFV Access devices. The uCPE Manager can be - deployed on a Linux (CentOS) based physical or virtual server. -
- -
- Automation Framework - - The Automation Framework consists of a set of tooling and a - collection of Python based scripts that can be used to automate the - process of onboarding a VNF with all of the required configuration for - day zero deployment at scale. - - This tooling calls the auto generated REST API that's exposed on - the uCPE Manager as a north bound interface. -
-
- \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml deleted file mode 100644 index 943e1ef..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/prerequisites.xml +++ /dev/null @@ -1,113 +0,0 @@ - - - Prerequisites - -
- Prerequisites - - - Required Elements - - - - - - - Prerequisites - - Observations - - - - - - Two uCPE whitebox devices containing: - - Processor: Intel xeon-D/atom-C3000 with min. 4 - CPUs. - - - - Min. 2 network interfaces. - - - - Min. 10 GB SATA storage. - - - - Min 8 GB RAM. - - - - - - One network interface connected to WAN. - - - - One network interface to be used for LAN. - - - - NFV Access installed on both uCPE devices. Please see - Enea NFV Access Getting Started Manual, chapter "Enea NFV - Access Installer"make this into an olink - for more details. - - - - - - Management machine - Linux based (CentOS) - - - - The uCPE Manager is installed on this host or virtual - machine. Pease see the Enea NFV Access Getting - Started Manual, chapter "Getting Started with - Enea uCPE Manager" for more details make this into - an olink. - - - - The uCPE Manager must have access to the uCPE - device. - - - - A web browser will access the management interface of - the VNFs. Management interfaces of the VNF can be accessed - from any machine connected on the same network with the uCPE - device. - - - - - -
-
- -
- Release structure - - |----enea-nfv-access-atom-c3000-20191210210825.hddimg -|----ea-nfv-access-xeon-d-20191210210913.hddimg -|----nfvaccess2.2.1_af-th.zip -|----ucpeManager_1.0.1_b3-CentOS.tar.gz -|----doc -|----VNFs - |----EneaVNF - |----enea-nfv-access-vnf-qemux86-64.wic.qcow2 - |----flexiWAN - |----flexiWAN_cloudinit.iso - |----flexiWAN.qcow2 - |----flexiwant-cloud-init-example.tar.gz - |----pfSense - |----pfsense_192_168_1_1.iso - |----pfsense_192_168_2_1.iso - |----pfsense_config_192_168_1_1.xml - |----pfsense_config_192_168_2_1.xml - |----pfSense.qcow2 -
- \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml deleted file mode 100644 index 725e4e0..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/run_example_uc_auto_fm.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - Running Example Use-cases from the Automation Framework - - In order to run example use-cases from the Automation Framework, - offline configurations need to be added for both uCPE devices and for the - VNFs to be onboarded. - - - All tests are just examples. In order to run on user specific - devices they need to be updated accordingly. Please check the Enea NFV - Access System Test Specification manual for more details. - - - > python unittestSuite.py -u admin -p admin -H 172.24.3.109 \ --o ucpem -s EvalKit_addOfflineConfig_and_onBoardVNFs.json -d \ -"Set - offline config for uCPE1 and uCPE2" - -#add device1 -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \ --s EvalKit_Deploy1.json -d "Add taget1 and instantiate VNFs" - -#add device2 -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \ --s EvalKit_Deploy2.json -d "Add taget2 and instantiate VNFs" - - Once done, the device configurations need to be cleaned up: - - > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \ --s EvalKit_Cleanup1.json -d "Cleanup config on taget1" - -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \ --s EvalKit_Cleanup2.json -d "Cleanup config on taget2" - -> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -o ucpem -s \ -EvalKit_CleanupZTP_and_offboardVNFs.json -d \ -"Cleanup offline configuration and OffBoard VNFs" - \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml deleted file mode 100644 index 4fcb6df..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/sdwan_arch.xml +++ /dev/null @@ -1,1439 +0,0 @@ - - - SD-WAN Branch to Branch Connection - - 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. - - 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. - - 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. - -
- Branch to Branch Connection Overview - - - - - - -
- - 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. - - 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 ibm_br bridge is the main bridge that - connects the physical network interface to the virtual - infrastructure. - - The Data-Path represents the traffic that passes over the physical - interface between the in-band management bridge (ibm_br), - the flexiWAN VNF, the service chain bridge (sfc_br), the - pfSense VNF, and the lan_br bridge to finally reach the - LAN. - - 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. - - 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. - -
- Preliminary Setup - - - - Connect each uCPE device to the network/Internet using one - physical interface as the designated WAN access interface. - - - The uCPE device must have Internet access beforehand. - - - - - Install NFV Access on the uCPE devices. See the make - this into an olink Enea NFV Access Getting Started manual, - chapter Getting Started with the Enea NFV Access, for more - details. - - - - Install the uCPE Manager on the CentOS host or VM. See the - make this into an olink Enea NFV Access Getting - Started manual, chapter Getting Started with Enea uCPE Manager, for - more details. - - - The uCPE Manager host machine must be connected to the network - so all uCPE devices can access it. - - - - - Connect to the uCPE Manager: https://<uCPE Manager - IP> - - -
- -
- The uCPE Manager - - Log into the uCPE Manager using the default credentials, - username:admin and password: admin. - - 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. - - 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. - -
- Onboarding the FlexiWAN VNF - - Add a VNF by accessing the VNF menu from the - top toolbar then Descriptors -> - On-board -> VM Image. - - Use the following values to fill the required fields: - - - - - - VM image file - - - flexiWAN.qcow2 - - - - - Image format - - QCOW2 - - - - VNF Type Name - - flexiWAN - - - - Description - - Flexiwan VNF - - - - Version - - 1.0 - - - - Memory in MB - - 4096. More memory can be allocated if required. - - - - Num of CPUs - - 2. More CPUs can be reserved if required and - available. - - - - Interfaces to add: - - wan and lan - - - - Cloud Init -> Cloud-Init Datasource - - ISO - - - - Cloud Init -> Cloud-Init Disk Type - - cdrom - - - - Onboard - - Wait for the message: "VNF package onboarded - successfully" then close the pop-up. - - - -
-
- -
- Onboarding the pfSense VNF - - Add the other VNF by accessing the VNF menu - from the top toolbar once again, then Descriptors - -> On-board -> VM - Image. - - Use the following values to fill the required fields: - - - - - - VM image file - - - pfSense.qcow2 - - - - - Image format - - QCOW2 - - - - VNF Type Name - - pfSense - - - - Description - - pfSense VNF - - - - Version - - 1.0 - - - - Memory in MB - - 1024 - - - - Num of CPUs - - 1 - - - - Interfaces to add: - - wan, lan and mgmt. - - - - Cloud Init -> Cloud-Init Datasource - - ISO - - - - Cloud Init -> Cloud-Init Disk Type - - cdrom - - - - Properties to add: - - - - - Name: vnfMgmtIpAddress. Value: - 10.0.0.31 - - - - Name: internalMgmtPort. Value: - 4432 - - - - Name: externalMgmtPort. Value: - 600023 - - - - - - - Onboard - - Wait for the message: "VNF package onboarded - successfully" then close the pop-up. - - - -
- - Please note the following: - - - - 1vnfMgmtIpAddress (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. - - - - 2HTTPS 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. - - - - 3externalMgmtPort (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. - - -
- -
- Offline Configuration for uCPE device1 - - 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. - - - - Create the "device1" data - store: Applications -> - Offline Config -> - Add. - - Use the following values to fill the required fields: - - - - - - - - Name - - - device1 - - - - - Device Type - - Enea universal CPE - - - - Device Version - - 2.2.1 - - - - Config Set - - uCPE Config - - - - - deviceId - - - The ID extracted from device1 after running - list_deviceID.sh. - - - -
- - Press the Create button. - - - - Prepare the infrastructure configuration for - device1 in the data store: - Applications -> Offline - Config -> <select "device1" data store> -> - Config App.... This window layout is very similar - to the Configuration window of a device. - - - - Disable the DPDK: DPDK -> - Advanced Settings -> uncheck Enable - DPDK to disable the DPDK and click "Create". - - - - Configure the host - interface(s): OpenVSwitch -> - Host Interfaces -> - Add. - - Use the following values to fill the required fields: - - - - Source: - enp7s0f1. - This is just an example interface. The user must - select the interface needed for use with the LAN - connection. - - - - - Type: N/A. - - - - networking-type: - standard. - - - - dpdk-type: N/A. - - - - Click Create, and the - enp7s0f1 interface will be ready to use in a - bridge (LAN). - - - - Configure the bridges: - OpenVSwitch -> Bridges - -> Add. - - Use the following values to fill the required fields for the - four bridges that need to be created: - - ibm_br: - - - - Name: - ibm_br. - - - - ovs-bridge-type: - inbandMgmt. - - - - mgmt-address: - Provide the IPv4 address of the uCPE Manager machine (E.g. - 172.24.3.109). - - - - mgmt-port: - 830. - - - - Click Create. - - - - vnf_mgmt_br: - - - - Name: - vnf_mgmt_br. - - - - ovs-bridge-type: - vnfMgmt. - - - - vnf-mgmt-address: - 10.0.0.1 - - - - Click Create. - - - - sfc_br: - - - - Name: - sfc_br. - - - - ovs-bridge-type: - dataPlane. - - - - Sub-type: - integration. - - - - Click Create. - - - - lan_br: - - - - Name: - lan_br. - - - - ovs-bridge-type: - dataPlane. - - - - Sub-type: - communication. Name: enp7s0f1 - - - - Click Create. - - - - -
- -
- Offline Configuration for uCPE device2 - - 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. - - - - Create the "device2" data - store: Applications -> - Offline Config -> - Add. - - Use the following values to fill the required fields: - - - - - - - - Name - - - device2 - - - - - Device Type - - Enea universal CPE - - - - Device Version - - 2.2.1 - - - - Config Set - - uCPE Config - - - - - deviceId - - - The ID extracted from device2 after running - list_deviceID.sh. - - - -
- - Press the Create button. - - - - Prepare the infrastructure configuration for - device2 in the data store: - Applications -> Offline - Config -> <select "device2" data store> -> - Config App.... This window layout is very similar - to the Configuration window of a device. - - - - Disable the DPDK: DPDK -> - Advanced Settings -> uncheck Enable - DPDK to disable the DPDK and click "Create". - - - - Configure the host - interface(s): OpenVSwitch -> - Host Interfaces -> - Add. - - Use the following values to fill the required fields: - - - - Source: - eno4. - This is just an example interface. The user must - select the interface needed for use with the LAN - connection. - - - - - Type: standard. - - - - networking-type: - standard. - - - - dpdk-type: N/A. - - - - Click Create, and the - eno4 interface will be ready to use in a bridge - (LAN). - - - - Configure the bridges: - OpenVSwitch -> Bridges - -> Add. - - Use the following values to fill the required fields for the - four bridges that need to be created: - - - - ibm_br: - - - - Name: - ibm_br. - - - - ovs-bridge-type: - inbandMgmt. - - - - mgmt-address: Provide - the IPv4 address of the uCPE Manager machine (E.g. - 172.24.3.109). - - - - mgmt-port: - 830. - - - - Click Create. - - - - vnf_mgmt_br: - - - - Name: - vnf_mgmt_br. - - - - ovs-bridge-type: - vnfMgmt. - - - - vnf-mgmt-address: - 10.0.0.1 - - - - Click Create. - - - - sfc_br: - - - - Name: - sfc_br. - - - - ovs-bridge-type: - dataPlane. - - - - Sub-type: - integration. - - - - Click Create. - - - - lan_br: - - - - Name: - lan_br. - - - - ovs-bridge-type: - dataPlane. - - - - Sub-type: - communication. Name: eno4 - - - - Click Create. - - - - -
- -
- Uploading the offline Configuration - - 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: - - - - Add the device manually from the uCPE manager GUI. - - - - Clean the entire configuration on the device. - - - - Reset the ZTP: device -> Configure -> - Host -> initial-config-complete: false -> Apply. - - - - Delete the device from the uCPE Manager. - - -
-
- -
- Adding the uCPE device1 into the uCPE Manager - - Access the Devices menu, then - Manage -> Add. - - Use the following values to fill the required fields: - - - - - - - - Type - - Enea universal CPE - - - - Release - - 1.0 - - - - Name - - Ucpe1 - - - - IP/DNS Address - - Dynamic IP received by the device from the DHCP server - (E.g. 172.24.12.74). - - - - Description - - ucpe device site 1 - - - - SSH Port - - 830 - - - - SSH User Name - - root - - - - Password - - - - - - Device ID - - Extract the device ID from device1, by running - list_deviceID.sh. - - - - OK - - - - - Green status indicates connection with the device was - established. - - - To add the device on the map: Right-Click on - the Map -> Place Device -> ucpe1. - - - - - -
-
- -
- Adding the uCPE device2 into the uCPE Manager - - Access the Devices menu, then - Manage -> Add. - - Use the following values to fill the required fields: - - - - - - - - Type - - Enea universal CPE - - - - Release - - 1.0 - - - - Name - - Ucpe2 - - - - IP/DNS Address - - Dynamic IP received by the device from the DHCP server - (E.g. 172.24.12.74). - - - - Description - - ucpe device site 2 - - - - SSH Port - - 830 - - - - SSH User Name - - root - - - - Password - - - - - - Device ID - - Extract the device ID from device2, by running - list_deviceID.sh. - - - - OK - - - - - Green status indicates connection with the device was - established. - - - To add the device on the map: Right-Click on - the Map -> Place Device -> ucpe2. - - - - - -
- - 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 <ucpe1> -> Configuration -> - OpenVSwitch -> Bridges. -
- -
- FlexiWAN VNF Instantiation on device1 - - Instantiate the FlexiWAN VNF by selecting the ucpe1 device, then the - VNF menu -> Instances -> - Add. - - Use the following values to fill the required fields: - - - - Name: - Flexiwan_ucpe1. - - - - VNF Type: - flexiWAN. - - - - VNFD Version: 1.0. - - - - Flavour: Canonical. - - - - uCPE Device: Ucpe1. - - - - Cloud Init File: - flexiWAN_cloudinit.iso. - - - 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. - - - - - Create the wan Interface: - - ID: - wan. - - Type: - tap. - - IF Name: Bridge: - ibm_br. - - Click Create. - - - - Create the lan Interface: - - ID: - lan. - - Type: - tap. - - IF Name: Bridge: - sfc_br. - - Click Create. - - -
- -
- pfSense VNF Instantiation on device1 - - Instantiate the pfSense VNF by selecting the ucpe1 device, then the - VNF menu -> Instances -> - Add. - - Use the following values to fill the required fields: - - - - Name: - Pfsense_ucpe1. - - - - VNF Type: - pfSense. - - - - VNFD Version: 1.0. - - - - Flavour: Canonical. - - - - uCPE Device: Ucpe1. - - - - Cloud Init File: - pfsense_192_168_1_1.iso. - - - - Create the wan Interface: - - ID: - wan. - - Type: - tap. - - IF Name: Bridge: - sfc_br. - - Click Create. - - - - Create the lan Interface: - - ID: - lan. - - Type: - tap. - - IF Name: Bridge: - lan_br. - - Click Create. - - - - Create the mgmt Interface: - - ID: - mgmt. - - Type: - tap. - - IF Name: Bridge: - vnf_mgmt_br. - - Click Create. - - -
- -
- FlexiWAN VNF Instantiation on device2 - - Instantiate the FlexiWAN VNF by selecting the ucpe2 device, then the - VNF menu -> Instances -> - Add. - - Use the following values to fill the required fields: - - - - Name: - Flexiwan_ucpe2. - - - - VNF Type: - flexiWAN. - - - - VNFD Version: 1.0. - - - - Flavour: Canonical. - - - - uCPE Device: Ucpe2. - - - - Cloud Init File: - flexiWAN_cloudinit.iso. - - - 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. - - - - - Create the wan Interface: - - ID: - wan. - - Type: - tap. - - IF Name: Bridge: - ibm_br. - - Click Create. - - - - Create the lan Interface: - - ID: - lan. - - Type: - tap. - - IF Name: Bridge: - sfc_br. - - Click Create. - - -
- -
- pfSense VNF Instantiation on device2 - - Instantiate the pfSense VNF by selecting the ucpe2 device, then the - VNF menu -> Instances -> - Add. - - Use the following values to fill the required fields: - - - - Name: - Pfsense_ucpe2. - - - - VNF Type: - pfSense. - - - - VNFD Version: 1.0. - - - - Flavour: Canonical. - - - - uCPE Device: Ucpe2. - - - - Cloud Init File: - pfsense_192_168_2_1.iso. - - - - Create the wan Interface: - - ID: - wan. - - Type: - tap. - - IF Name: Bridge: - sfc_br. - - Click Create. - - - - Create the lan Interface: - - ID: - lan. - - Type: - tap. - - IF Name: Bridge: - lan_br. - - Click Create. - - - - Create the mgmt Interface: - - ID: - mgmt. - - Type: - tap. - - IF Name: Bridge: - vnf_mgmt_br. - - Click Create. - - - - Once all VNFs are up and running, the setup is ready for final VNF - configuration and testing. - -
- SD-WAN branch-to-branch connection setup Overview - - - - - - -
- - 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. -
- -
- FlexiWAN configuration - - Connect to https://app.flexiwan.com and make - sure you have an account and at least two valid device tokens. For more - information please contact the flexiWAN VNF provider. - - Proceed to the Inventory menu, click on Devices, - the devices should already be present and need to be configured. - - How to configure a device - - - - Select each device and make sure to set the following - values: - - - - - - Device1(ucpe1) - - Device2(ucpe2) - - - - Device Name: Device1 - - Device Name: Device2 - - - - Description: Set IPv4 for the second interface - (ens3): 10.0.1.1/24. - - Description: Set IPv4 for the second interface - (ens3): 10.0.2.1/24. - - - - Set "Approved". - - Set "Approved". - - - - Click "Update Device". - - Click "Update Device". - - - -
- - - 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 same local network - (same public IP), delete the public IP address from the device - configuration before creating a tunnel: https://app.flexiwan.com - -> Inventory -> Devices - -> <device> -> Public IP. - - - - - Select the ">" option for each device to be put in the - "running" state. - - - - Wait for each "vRouter" device to also enter the "running" - state. - - - - Select the main top up checkbox in order to select all devices - and hit "Create Tunnels". At this moment a direct connection should be - available between those two devices. You can check if the tunnel was - created by selecting Inventory -> Tunnels. - - -
- -
- pfSense configuration - - 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. - - The management interface can be accessed from a web browser at: - https://<deviceIP>:60002 -
- \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml deleted file mode 100644 index 6a129e8..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/setup_cleanup.xml +++ /dev/null @@ -1,61 +0,0 @@ - - - Setup Clean-up - - In order to remove the setup all components need to be deleted in - reverse order: - - - - Select the ucpe1 device, access the VNF menu - then Instances FlexiWAN and pfSense and press - Delete. - - - - Select the ucpe1 device, access the - Configuration menu, then - OpenVSwitch -> Bridges. Select - all bridges and press Delete. - - - - Select the ucpe1 device, access the - Configuration menu, then - OpenVSwitch -> Host Interfaces. - Select all interfaces and press Delete. - - - - Select the ucpe2 device, access the VNF menu - then Instances FlexiWAN and pfSense and press - Delete. - - - - Select the ucpe2 device, access the - Configuration menu, then - OpenVSwitch -> Bridges. Select - all bridges and press Delete. - - - - Select the ucpe2 device, access the - Configuration menu, then - OpenVSwitch -> Host Interfaces. - Select all interfaces and press Delete. - - - - Access the VNF menu, select - Descriptors. Select each descriptor and off-board - them. - - - - Access the Applications menu, select - Offline Config. Select both device configurations and - delete them. - - - \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml b/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml deleted file mode 100644 index 02d71d2..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/doc/validating_setup.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - Validating the Setup - - In order to access the web interfaces of the - pfSense VNF: - - - - Open a browser on a machine connected on the same network with the - WAN port of the uCPE device. - - - - Connect to: https://<publicIP>:60002 with - the username: admin and the password: pfsense. - - - - In order to validate the data - path: - - - - Connect a test machine to the LAN physical port. - - - - Check for a dynamic IP. The pfSense LAN interface is configured - with a DHCP server and should receive an IP from the corresponding - subnet (uCPE device1 has 192.168.1.XXX, while uCPE device2 has - 192.168.2.XXX).> dhclient eth1 -> ping 192.168.2.1 - - - \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit-2.2.1/swcomp.mk b/doc/book-enea-nfv-access-evalkit-2.2.1/swcomp.mk deleted file mode 100755 index 70f0766..0000000 --- a/doc/book-enea-nfv-access-evalkit-2.2.1/swcomp.mk +++ /dev/null @@ -1,10 +0,0 @@ -# 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-nfv-access-evalkit-2.2.1 -BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) for CMC Networks Example Use-cases" -BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) diff --git a/doc/book-enea-nfv-access-evalkit/doc/appendix_1.xml b/doc/book-enea-nfv-access-evalkit/doc/appendix_1.xml new file mode 100644 index 0000000..0895bcb --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/appendix_1.xml @@ -0,0 +1,35 @@ + + + How to create a flexiwan cloud-init iso image (day-0 + configuration) + + Prerequisites: + + + + Development host with a Linux shell. + + + + The Cloud-localds tool installed. + + + + + Contact the flexiWAN VNF provider to get access to their controller + and a valid token. + + + Unpack the + flexiwan/flexiwan-cloud-init-example.tar.gz and check + the README file for more details: tar -zxf flexiwant-cloud-init-example.tar.gz +cd flexiwan/cloud-init-example/ + + To generate the cloud-init iso image: + + > create_flexiwan_cloudinit.sh <token> +> create_flexiwan_cloudinit.sh $cat token.txt + + The flexiWAN_cloudinit.iso file can be used to + instantiate the flexiWAN VNF on NFV Access. + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/book.xml b/doc/book-enea-nfv-access-evalkit/doc/book.xml new file mode 100644 index 0000000..e78cbf9 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/book.xml @@ -0,0 +1,38 @@ + + +]> + + <trademark class="registered">Enea</trademark> NFV Access EvalKit Manual + + Release Version + + + + + + + + + + + + + + + + + + + diff --git a/doc/book-enea-nfv-access-evalkit/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-evalkit/doc/eltf_params_updated.xml new file mode 100644 index 0000000..1a640a3 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/eltf_params_updated.xml @@ -0,0 +1,209 @@ + + +
+ File with Parameters in the Book Auto-updated by ELFT + + + See the eltf_params_updated_template_howto_use.txt text + file for description of how to create the final eltf_params_updated.xml from this template and for + all REQUIREMENTS. Use the command + "make eltf" to extract a full list of all + ELTF variables, which always begins with ELTF_ and don't only rely on the + howto text file list! The plan is that ELTF will auto-update this when + needed. + + +
+ Common Parameters + + A programlisting, ID + "eltf-prereq-apt-get-commands-host" + + # Host Ubuntu 16.04 LTS 64bit +sudo apt-get -y update +sudo apt-get -y install sed wget subversion git-core coreutils unzip texi2html \ + texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \ + make gcc build-essential xsltproc g++ desktop-file-utils chrpath \ + libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \ + libxml-parser-perl + + A programlisting, ID + "eltf-getting-repo-install-command" + + mkdir -p ~/bin +curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo +chmod a+x ~/bin/repo +export PATH=~/bin:$PATH + + Several phrase elements, various IDs. Ensure EL_REL_VER is + correct also compared to the "previous" REL VER in pardoc-distro.xml + "prev_baseline". + + 2.2.1 + + 2.4 + + rocko + + http://www.yoctoproject.org/downloads + + https://linux.enea.com/6 + + A programlisting, ID "eltf-repo-cloning-enea-linux". Use + $MACHINE/default.xml as parameter, where MACHINE is one of the target + directory names in the manifest. + + mkdir enea-linux +cd enea-linux +repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \ + -b refs/tags/EL6 -m $MACHINE/default.xml +repo sync + + A table with ONE row, only the row with ID + "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set + condition hidden if eclipse is not in the release. Do this both in + template.xml and updated.xml. + + + + + + Eclipse version 4.3 (Mars) plus command line development + tools are included in this Enea NFV Access release. + + + + + + Below is one big section with title "Supported Processor with + Parameters". The entire section is included completely in the book via ID + "eltf-target-tables-section" and shall be LAST in the template. The + template contains ONE target subsection. COPY/APPEND it, if multiple + targets exist in the release and optionally add rows with additional + target parameters in each target subsection table. +
+ +
+ Supported Reference Processor with Parameters + + The table(s) below describes the processors supported in this Enea + NFV Access release. + + + Processor Information Intel Xeon D-1500 + + + + + + + Component + + Description + + + + + + Processor official name + + Intel Xeon D-1500 + + + + Architecture and Description + + x86-64 + + + + Link to processor datasheet + + Intel's + datasheet + + + + GCC version + + 7.3 + + + + Linux Kernel Version + + 4.14 + + + + Supported Drivers + + Ethernet, RTC, UART + + + +
+ + + Processor Information Intel Atom C3000 + + + + + + + Component + + Description + + + + + + Processor official name + + Intel Atom C3000 + + + + Architecture and Description + + x86-64 + + + + Link to the processor datasheet + + Intel's + datasheet + + + + GCC version + + 7.3 + + + + Linux Kernel Version + + 4.14 + + + + Supported Drivers + + Ethernet, RTC, UART + + + +
+
+
diff --git a/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_overview.png b/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_overview.png new file mode 100644 index 0000000..977de0f Binary files /dev/null and b/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_overview.png differ diff --git a/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_setup.png b/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_setup.png new file mode 100644 index 0000000..feb18a3 Binary files /dev/null and b/doc/book-enea-nfv-access-evalkit/doc/images/br_to_br_conn_setup.png differ diff --git a/doc/book-enea-nfv-access-evalkit/doc/introduction.xml b/doc/book-enea-nfv-access-evalkit/doc/introduction.xml new file mode 100644 index 0000000..7b92bcf --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/introduction.xml @@ -0,0 +1,76 @@ + + + Introduction + + The NFV Access EvalKit offered by Enea contains software that can be + used to deploy an SD-WAN setup. The branch-to-branch setup uses two + opensource based VNFs: flexiWAN and pfSense. These VNFs are provided as + examples and the configuration used only works on the documented + setup. + + Enea NFV Access for the universal Customer Premise Equipment (uCPE) is + a virtualization and management platform, which allows end-users to + introduce, instantiate, and run third-party VNFs onto their systems. + + The solution is comprised of two major components working in close + cooperation: + + + + The Enea NFV Access Run-Time Platform, which acts as the host for + Virtualized Network Functions (VNFs) and provides management over + NETCONF. + + + + The Enea uCPE Manager, a solution that runs on an external server, + providing VNF Management functionality and managing large numbers of + uCPEs. + + + + The current Enea NFV Access solution provides a working and deployable + configuration as an example for branch-to-branch connection setup using the + flexiWAN and pfSense VNFs service chained together on a uCPE device. + + This document will present all information required to replicate the + use case described in the user's environment. The first part of this manual + uses the GUI mode of the uCPE Manager to detail the steps in order to + reproduce the use cases, while the chapters thereafter use the automation + framework. + + + All VNF configurations should be seen as example configurations + working in Enea internal lab and the user must update these files with the + configuration data needed according to his network setup. Particularities + are described in Appendix A. + + This document assumes the user is familiar with Enea NFV Access and + has read the Enea NFV Access Getting Started manual before continuing with + the following. + + +
+ Definitions and Acronyms + +
+ uCPE Manager + + The Enea uCPE Manager is an EMS/NMS platform providing VNF + Management capabilities for NFV Access devices. The uCPE Manager can be + deployed on a Linux (CentOS) based physical or virtual server. +
+ +
+ Automation Framework + + The Automation Framework consists of a set of tooling and a + collection of Python based scripts that can be used to automate the + process of onboarding a VNF with all of the required configuration for + day zero deployment at scale. + + This tooling calls the auto generated REST API that's exposed on + the uCPE Manager as a north bound interface. +
+
+ \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml b/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml new file mode 100644 index 0000000..943e1ef --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml @@ -0,0 +1,113 @@ + + + Prerequisites + +
+ Prerequisites + + + Required Elements + + + + + + + Prerequisites + + Observations + + + + + + Two uCPE whitebox devices containing: + + Processor: Intel xeon-D/atom-C3000 with min. 4 + CPUs. + + + + Min. 2 network interfaces. + + + + Min. 10 GB SATA storage. + + + + Min 8 GB RAM. + + + + + + One network interface connected to WAN. + + + + One network interface to be used for LAN. + + + + NFV Access installed on both uCPE devices. Please see + Enea NFV Access Getting Started Manual, chapter "Enea NFV + Access Installer"make this into an olink + for more details. + + + + + + Management machine - Linux based (CentOS) + + + + The uCPE Manager is installed on this host or virtual + machine. Pease see the Enea NFV Access Getting + Started Manual, chapter "Getting Started with + Enea uCPE Manager" for more details make this into + an olink. + + + + The uCPE Manager must have access to the uCPE + device. + + + + A web browser will access the management interface of + the VNFs. Management interfaces of the VNF can be accessed + from any machine connected on the same network with the uCPE + device. + + + + + +
+
+ +
+ Release structure + + |----enea-nfv-access-atom-c3000-20191210210825.hddimg +|----ea-nfv-access-xeon-d-20191210210913.hddimg +|----nfvaccess2.2.1_af-th.zip +|----ucpeManager_1.0.1_b3-CentOS.tar.gz +|----doc +|----VNFs + |----EneaVNF + |----enea-nfv-access-vnf-qemux86-64.wic.qcow2 + |----flexiWAN + |----flexiWAN_cloudinit.iso + |----flexiWAN.qcow2 + |----flexiwant-cloud-init-example.tar.gz + |----pfSense + |----pfsense_192_168_1_1.iso + |----pfsense_192_168_2_1.iso + |----pfsense_config_192_168_1_1.xml + |----pfsense_config_192_168_2_1.xml + |----pfSense.qcow2 +
+ \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/run_example_uc_auto_fm.xml b/doc/book-enea-nfv-access-evalkit/doc/run_example_uc_auto_fm.xml new file mode 100644 index 0000000..725e4e0 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/run_example_uc_auto_fm.xml @@ -0,0 +1,38 @@ + + + Running Example Use-cases from the Automation Framework + + In order to run example use-cases from the Automation Framework, + offline configurations need to be added for both uCPE devices and for the + VNFs to be onboarded. + + + All tests are just examples. In order to run on user specific + devices they need to be updated accordingly. Please check the Enea NFV + Access System Test Specification manual for more details. + + + > python unittestSuite.py -u admin -p admin -H 172.24.3.109 \ +-o ucpem -s EvalKit_addOfflineConfig_and_onBoardVNFs.json -d \ +"Set - offline config for uCPE1 and uCPE2" + +#add device1 +> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \ +-s EvalKit_Deploy1.json -d "Add taget1 and instantiate VNFs" + +#add device2 +> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \ +-s EvalKit_Deploy2.json -d "Add taget2 and instantiate VNFs" + + Once done, the device configurations need to be cleaned up: + + > python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n fwa_1012vc-1 \ +-s EvalKit_Cleanup1.json -d "Cleanup config on taget1" + +> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -n intelc3850-1 \ +-s EvalKit_Cleanup2.json -d "Cleanup config on taget2" + +> python unittestSuite.py -u admin -p admin -H 172.24.3.109 -o ucpem -s \ +EvalKit_CleanupZTP_and_offboardVNFs.json -d \ +"Cleanup offline configuration and OffBoard VNFs" + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml b/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml new file mode 100644 index 0000000..4fcb6df --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml @@ -0,0 +1,1439 @@ + + + SD-WAN Branch to Branch Connection + + 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. + + 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. + + 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. + +
+ Branch to Branch Connection Overview + + + + + + +
+ + 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. + + 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 ibm_br bridge is the main bridge that + connects the physical network interface to the virtual + infrastructure. + + The Data-Path represents the traffic that passes over the physical + interface between the in-band management bridge (ibm_br), + the flexiWAN VNF, the service chain bridge (sfc_br), the + pfSense VNF, and the lan_br bridge to finally reach the + LAN. + + 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. + + 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. + +
+ Preliminary Setup + + + + Connect each uCPE device to the network/Internet using one + physical interface as the designated WAN access interface. + + + The uCPE device must have Internet access beforehand. + + + + + Install NFV Access on the uCPE devices. See the make + this into an olink Enea NFV Access Getting Started manual, + chapter Getting Started with the Enea NFV Access, for more + details. + + + + Install the uCPE Manager on the CentOS host or VM. See the + make this into an olink Enea NFV Access Getting + Started manual, chapter Getting Started with Enea uCPE Manager, for + more details. + + + The uCPE Manager host machine must be connected to the network + so all uCPE devices can access it. + + + + + Connect to the uCPE Manager: https://<uCPE Manager + IP> + + +
+ +
+ The uCPE Manager + + Log into the uCPE Manager using the default credentials, + username:admin and password: admin. + + 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. + + 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. + +
+ Onboarding the FlexiWAN VNF + + Add a VNF by accessing the VNF menu from the + top toolbar then Descriptors -> + On-board -> VM Image. + + Use the following values to fill the required fields: + + + + + + VM image file + + + flexiWAN.qcow2 + + + + + Image format + + QCOW2 + + + + VNF Type Name + + flexiWAN + + + + Description + + Flexiwan VNF + + + + Version + + 1.0 + + + + Memory in MB + + 4096. More memory can be allocated if required. + + + + Num of CPUs + + 2. More CPUs can be reserved if required and + available. + + + + Interfaces to add: + + wan and lan + + + + Cloud Init -> Cloud-Init Datasource + + ISO + + + + Cloud Init -> Cloud-Init Disk Type + + cdrom + + + + Onboard + + Wait for the message: "VNF package onboarded + successfully" then close the pop-up. + + + +
+
+ +
+ Onboarding the pfSense VNF + + Add the other VNF by accessing the VNF menu + from the top toolbar once again, then Descriptors + -> On-board -> VM + Image. + + Use the following values to fill the required fields: + + + + + + VM image file + + + pfSense.qcow2 + + + + + Image format + + QCOW2 + + + + VNF Type Name + + pfSense + + + + Description + + pfSense VNF + + + + Version + + 1.0 + + + + Memory in MB + + 1024 + + + + Num of CPUs + + 1 + + + + Interfaces to add: + + wan, lan and mgmt. + + + + Cloud Init -> Cloud-Init Datasource + + ISO + + + + Cloud Init -> Cloud-Init Disk Type + + cdrom + + + + Properties to add: + + + + + Name: vnfMgmtIpAddress. Value: + 10.0.0.31 + + + + Name: internalMgmtPort. Value: + 4432 + + + + Name: externalMgmtPort. Value: + 600023 + + + + + + + Onboard + + Wait for the message: "VNF package onboarded + successfully" then close the pop-up. + + + +
+ + Please note the following: + + + + 1vnfMgmtIpAddress (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. + + + + 2HTTPS 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. + + + + 3externalMgmtPort (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. + + +
+ +
+ Offline Configuration for uCPE device1 + + 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. + + + + Create the "device1" data + store: Applications -> + Offline Config -> + Add. + + Use the following values to fill the required fields: + + + + + + + + Name + + + device1 + + + + + Device Type + + Enea universal CPE + + + + Device Version + + 2.2.1 + + + + Config Set + + uCPE Config + + + + + deviceId + + + The ID extracted from device1 after running + list_deviceID.sh. + + + +
+ + Press the Create button. + + + + Prepare the infrastructure configuration for + device1 in the data store: + Applications -> Offline + Config -> <select "device1" data store> -> + Config App.... This window layout is very similar + to the Configuration window of a device. + + + + Disable the DPDK: DPDK -> + Advanced Settings -> uncheck Enable + DPDK to disable the DPDK and click "Create". + + + + Configure the host + interface(s): OpenVSwitch -> + Host Interfaces -> + Add. + + Use the following values to fill the required fields: + + + + Source: + enp7s0f1. + This is just an example interface. The user must + select the interface needed for use with the LAN + connection. + + + + + Type: N/A. + + + + networking-type: + standard. + + + + dpdk-type: N/A. + + + + Click Create, and the + enp7s0f1 interface will be ready to use in a + bridge (LAN). + + + + Configure the bridges: + OpenVSwitch -> Bridges + -> Add. + + Use the following values to fill the required fields for the + four bridges that need to be created: + + ibm_br: + + + + Name: + ibm_br. + + + + ovs-bridge-type: + inbandMgmt. + + + + mgmt-address: + Provide the IPv4 address of the uCPE Manager machine (E.g. + 172.24.3.109). + + + + mgmt-port: + 830. + + + + Click Create. + + + + vnf_mgmt_br: + + + + Name: + vnf_mgmt_br. + + + + ovs-bridge-type: + vnfMgmt. + + + + vnf-mgmt-address: + 10.0.0.1 + + + + Click Create. + + + + sfc_br: + + + + Name: + sfc_br. + + + + ovs-bridge-type: + dataPlane. + + + + Sub-type: + integration. + + + + Click Create. + + + + lan_br: + + + + Name: + lan_br. + + + + ovs-bridge-type: + dataPlane. + + + + Sub-type: + communication. Name: enp7s0f1 + + + + Click Create. + + + + +
+ +
+ Offline Configuration for uCPE device2 + + 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. + + + + Create the "device2" data + store: Applications -> + Offline Config -> + Add. + + Use the following values to fill the required fields: + + + + + + + + Name + + + device2 + + + + + Device Type + + Enea universal CPE + + + + Device Version + + 2.2.1 + + + + Config Set + + uCPE Config + + + + + deviceId + + + The ID extracted from device2 after running + list_deviceID.sh. + + + +
+ + Press the Create button. + + + + Prepare the infrastructure configuration for + device2 in the data store: + Applications -> Offline + Config -> <select "device2" data store> -> + Config App.... This window layout is very similar + to the Configuration window of a device. + + + + Disable the DPDK: DPDK -> + Advanced Settings -> uncheck Enable + DPDK to disable the DPDK and click "Create". + + + + Configure the host + interface(s): OpenVSwitch -> + Host Interfaces -> + Add. + + Use the following values to fill the required fields: + + + + Source: + eno4. + This is just an example interface. The user must + select the interface needed for use with the LAN + connection. + + + + + Type: standard. + + + + networking-type: + standard. + + + + dpdk-type: N/A. + + + + Click Create, and the + eno4 interface will be ready to use in a bridge + (LAN). + + + + Configure the bridges: + OpenVSwitch -> Bridges + -> Add. + + Use the following values to fill the required fields for the + four bridges that need to be created: + + + + ibm_br: + + + + Name: + ibm_br. + + + + ovs-bridge-type: + inbandMgmt. + + + + mgmt-address: Provide + the IPv4 address of the uCPE Manager machine (E.g. + 172.24.3.109). + + + + mgmt-port: + 830. + + + + Click Create. + + + + vnf_mgmt_br: + + + + Name: + vnf_mgmt_br. + + + + ovs-bridge-type: + vnfMgmt. + + + + vnf-mgmt-address: + 10.0.0.1 + + + + Click Create. + + + + sfc_br: + + + + Name: + sfc_br. + + + + ovs-bridge-type: + dataPlane. + + + + Sub-type: + integration. + + + + Click Create. + + + + lan_br: + + + + Name: + lan_br. + + + + ovs-bridge-type: + dataPlane. + + + + Sub-type: + communication. Name: eno4 + + + + Click Create. + + + + +
+ +
+ Uploading the offline Configuration + + 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: + + + + Add the device manually from the uCPE manager GUI. + + + + Clean the entire configuration on the device. + + + + Reset the ZTP: device -> Configure -> + Host -> initial-config-complete: false -> Apply. + + + + Delete the device from the uCPE Manager. + + +
+
+ +
+ Adding the uCPE device1 into the uCPE Manager + + Access the Devices menu, then + Manage -> Add. + + Use the following values to fill the required fields: + + + + + + + + Type + + Enea universal CPE + + + + Release + + 1.0 + + + + Name + + Ucpe1 + + + + IP/DNS Address + + Dynamic IP received by the device from the DHCP server + (E.g. 172.24.12.74). + + + + Description + + ucpe device site 1 + + + + SSH Port + + 830 + + + + SSH User Name + + root + + + + Password + + + + + + Device ID + + Extract the device ID from device1, by running + list_deviceID.sh. + + + + OK + + + + + Green status indicates connection with the device was + established. + + + To add the device on the map: Right-Click on + the Map -> Place Device -> ucpe1. + + + + + +
+
+ +
+ Adding the uCPE device2 into the uCPE Manager + + Access the Devices menu, then + Manage -> Add. + + Use the following values to fill the required fields: + + + + + + + + Type + + Enea universal CPE + + + + Release + + 1.0 + + + + Name + + Ucpe2 + + + + IP/DNS Address + + Dynamic IP received by the device from the DHCP server + (E.g. 172.24.12.74). + + + + Description + + ucpe device site 2 + + + + SSH Port + + 830 + + + + SSH User Name + + root + + + + Password + + + + + + Device ID + + Extract the device ID from device2, by running + list_deviceID.sh. + + + + OK + + + + + Green status indicates connection with the device was + established. + + + To add the device on the map: Right-Click on + the Map -> Place Device -> ucpe2. + + + + + +
+ + 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 <ucpe1> -> Configuration -> + OpenVSwitch -> Bridges. +
+ +
+ FlexiWAN VNF Instantiation on device1 + + Instantiate the FlexiWAN VNF by selecting the ucpe1 device, then the + VNF menu -> Instances -> + Add. + + Use the following values to fill the required fields: + + + + Name: + Flexiwan_ucpe1. + + + + VNF Type: + flexiWAN. + + + + VNFD Version: 1.0. + + + + Flavour: Canonical. + + + + uCPE Device: Ucpe1. + + + + Cloud Init File: + flexiWAN_cloudinit.iso. + + + 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. + + + + + Create the wan Interface: + + ID: + wan. + + Type: + tap. + + IF Name: Bridge: + ibm_br. + + Click Create. + + + + Create the lan Interface: + + ID: + lan. + + Type: + tap. + + IF Name: Bridge: + sfc_br. + + Click Create. + + +
+ +
+ pfSense VNF Instantiation on device1 + + Instantiate the pfSense VNF by selecting the ucpe1 device, then the + VNF menu -> Instances -> + Add. + + Use the following values to fill the required fields: + + + + Name: + Pfsense_ucpe1. + + + + VNF Type: + pfSense. + + + + VNFD Version: 1.0. + + + + Flavour: Canonical. + + + + uCPE Device: Ucpe1. + + + + Cloud Init File: + pfsense_192_168_1_1.iso. + + + + Create the wan Interface: + + ID: + wan. + + Type: + tap. + + IF Name: Bridge: + sfc_br. + + Click Create. + + + + Create the lan Interface: + + ID: + lan. + + Type: + tap. + + IF Name: Bridge: + lan_br. + + Click Create. + + + + Create the mgmt Interface: + + ID: + mgmt. + + Type: + tap. + + IF Name: Bridge: + vnf_mgmt_br. + + Click Create. + + +
+ +
+ FlexiWAN VNF Instantiation on device2 + + Instantiate the FlexiWAN VNF by selecting the ucpe2 device, then the + VNF menu -> Instances -> + Add. + + Use the following values to fill the required fields: + + + + Name: + Flexiwan_ucpe2. + + + + VNF Type: + flexiWAN. + + + + VNFD Version: 1.0. + + + + Flavour: Canonical. + + + + uCPE Device: Ucpe2. + + + + Cloud Init File: + flexiWAN_cloudinit.iso. + + + 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. + + + + + Create the wan Interface: + + ID: + wan. + + Type: + tap. + + IF Name: Bridge: + ibm_br. + + Click Create. + + + + Create the lan Interface: + + ID: + lan. + + Type: + tap. + + IF Name: Bridge: + sfc_br. + + Click Create. + + +
+ +
+ pfSense VNF Instantiation on device2 + + Instantiate the pfSense VNF by selecting the ucpe2 device, then the + VNF menu -> Instances -> + Add. + + Use the following values to fill the required fields: + + + + Name: + Pfsense_ucpe2. + + + + VNF Type: + pfSense. + + + + VNFD Version: 1.0. + + + + Flavour: Canonical. + + + + uCPE Device: Ucpe2. + + + + Cloud Init File: + pfsense_192_168_2_1.iso. + + + + Create the wan Interface: + + ID: + wan. + + Type: + tap. + + IF Name: Bridge: + sfc_br. + + Click Create. + + + + Create the lan Interface: + + ID: + lan. + + Type: + tap. + + IF Name: Bridge: + lan_br. + + Click Create. + + + + Create the mgmt Interface: + + ID: + mgmt. + + Type: + tap. + + IF Name: Bridge: + vnf_mgmt_br. + + Click Create. + + + + Once all VNFs are up and running, the setup is ready for final VNF + configuration and testing. + +
+ SD-WAN branch-to-branch connection setup Overview + + + + + + +
+ + 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. +
+ +
+ FlexiWAN configuration + + Connect to https://app.flexiwan.com and make + sure you have an account and at least two valid device tokens. For more + information please contact the flexiWAN VNF provider. + + Proceed to the Inventory menu, click on Devices, + the devices should already be present and need to be configured. + + How to configure a device + + + + Select each device and make sure to set the following + values: + + + + + + Device1(ucpe1) + + Device2(ucpe2) + + + + Device Name: Device1 + + Device Name: Device2 + + + + Description: Set IPv4 for the second interface + (ens3): 10.0.1.1/24. + + Description: Set IPv4 for the second interface + (ens3): 10.0.2.1/24. + + + + Set "Approved". + + Set "Approved". + + + + Click "Update Device". + + Click "Update Device". + + + +
+ + + 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 same local network + (same public IP), delete the public IP address from the device + configuration before creating a tunnel: https://app.flexiwan.com + -> Inventory -> Devices + -> <device> -> Public IP. + + + + + Select the ">" option for each device to be put in the + "running" state. + + + + Wait for each "vRouter" device to also enter the "running" + state. + + + + Select the main top up checkbox in order to select all devices + and hit "Create Tunnels". At this moment a direct connection should be + available between those two devices. You can check if the tunnel was + created by selecting Inventory -> Tunnels. + + +
+ +
+ pfSense configuration + + 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. + + The management interface can be accessed from a web browser at: + https://<deviceIP>:60002 +
+ \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml b/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml new file mode 100644 index 0000000..6a129e8 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml @@ -0,0 +1,61 @@ + + + Setup Clean-up + + In order to remove the setup all components need to be deleted in + reverse order: + + + + Select the ucpe1 device, access the VNF menu + then Instances FlexiWAN and pfSense and press + Delete. + + + + Select the ucpe1 device, access the + Configuration menu, then + OpenVSwitch -> Bridges. Select + all bridges and press Delete. + + + + Select the ucpe1 device, access the + Configuration menu, then + OpenVSwitch -> Host Interfaces. + Select all interfaces and press Delete. + + + + Select the ucpe2 device, access the VNF menu + then Instances FlexiWAN and pfSense and press + Delete. + + + + Select the ucpe2 device, access the + Configuration menu, then + OpenVSwitch -> Bridges. Select + all bridges and press Delete. + + + + Select the ucpe2 device, access the + Configuration menu, then + OpenVSwitch -> Host Interfaces. + Select all interfaces and press Delete. + + + + Access the VNF menu, select + Descriptors. Select each descriptor and off-board + them. + + + + Access the Applications menu, select + Offline Config. Select both device configurations and + delete them. + + + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/doc/validating_setup.xml b/doc/book-enea-nfv-access-evalkit/doc/validating_setup.xml new file mode 100644 index 0000000..02d71d2 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/doc/validating_setup.xml @@ -0,0 +1,36 @@ + + + Validating the Setup + + In order to access the web interfaces of the + pfSense VNF: + + + + Open a browser on a machine connected on the same network with the + WAN port of the uCPE device. + + + + Connect to: https://<publicIP>:60002 with + the username: admin and the password: pfsense. + + + + In order to validate the data + path: + + + + Connect a test machine to the LAN physical port. + + + + Check for a dynamic IP. The pfSense LAN interface is configured + with a DHCP server and should receive an IP from the corresponding + subnet (uCPE device1 has 192.168.1.XXX, while uCPE device2 has + 192.168.2.XXX).> dhclient eth1 +> ping 192.168.2.1 + + + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-evalkit/swcomp.mk b/doc/book-enea-nfv-access-evalkit/swcomp.mk new file mode 100755 index 0000000..4568a23 --- /dev/null +++ b/doc/book-enea-nfv-access-evalkit/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-nfv-access-evalkit +BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) for CMC Networks Example Use-cases" +BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) -- cgit v1.2.3-54-g00ecf