From 5059f4838aef6204ea08862a9c5649a32d76c16f Mon Sep 17 00:00:00 2001 From: mrpa Date: Fri, 20 Dec 2019 16:51:06 +0100 Subject: Last updates needed. Change-Id: I9784e1a0c5103364f2e7df60b0c0d2dbd22312fa --- .../doc/prerequisites.xml | 104 +++++++++++++++------ .../doc/run_example_uc_auto_fm.xml | 12 ++- .../doc/sdwan_arch.xml | 94 ++++++++++--------- .../doc/setup_cleanup.xml | 49 ++++------ 4 files changed, 152 insertions(+), 107 deletions(-) (limited to 'doc') diff --git a/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml b/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml index 943e1ef..922be79 100644 --- a/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml +++ b/doc/book-enea-nfv-access-evalkit/doc/prerequisites.xml @@ -3,11 +3,9 @@ Prerequisites
- Prerequisites + Required Elements - Required Elements - @@ -23,7 +21,7 @@ Two uCPE whitebox devices containing: - Processor: Intel xeon-D/atom-C3000 with min. 4 + Processor: Intel Xeon D-1500 / Atom C3000 with min. 4 CPUs. @@ -40,9 +38,14 @@ - + + - One network interface connected to WAN. + One network interface connected to WAN. + For this release, only a dynamic IP address is + supported. The WAN interfaces receives the IP address + from the DHCP server. + @@ -51,23 +54,24 @@ 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. + Enea NFV Access Getting Started Manual, + chapter "Getting Started with Enea NFV Access" 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 + machine. See the Enea NFV Access Getting Started Manual, chapter "Getting Started with - Enea uCPE Manager" for more details make this into - an olink. + Enea uCPE Manager" for more details. @@ -81,7 +85,8 @@ from any machine connected on the same network with the uCPE device. - + + @@ -89,25 +94,66 @@
- Release structure + Release Structure |----enea-nfv-access-atom-c3000-20191210210825.hddimg |----ea-nfv-access-xeon-d-20191210210913.hddimg -|----nfvaccess2.2.1_af-th.zip +|----nfvaccess_evalkit_2.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 + |----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 +
+ +
+ Known Issues and Limitations + + + + The flexiWAN VNF image was generated by Enea for use only under + the scope of this EvalKit release. + + + + The pfSense cloud-init image was configured only for the EvalKit + setup. + + + + The usage of VNFs images mentioned above outside of the + delivered scenario is not guaranteed and not supported. + + + + The customer must be aware and follow the pfSense and flexiWAN + legal requirements availble in the following links: + + + + https://flexiwan.com/legal/eula/ + + + + https://github.com/pfsense/pfsense/blob/master/LICENSE + + + + + + See the Enea NFV Access 2.2.1 Release Information for more + details.
\ 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 index 725e4e0..d157c06 100644 --- 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 @@ -2,6 +2,15 @@ Running Example Use-cases from the Automation Framework + + Before running the EvalKit setup the user must add the designated + devices (device1 and device2) under + the lab_config folder and replace all occurrences of + fwa1021vc-1 with device1 and + intelc3850-1 with device2 under + automation_framework/unittestSuite/config/evalkit. + + 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. @@ -12,7 +21,8 @@ Access System Test Specification manual for more details. - > python unittestSuite.py -u admin -p admin -H 172.24.3.109 \ + > cd automation_framework/unittestSuite/ +> 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" diff --git a/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml b/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml index 4fcb6df..aeed4ed 100644 --- a/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml +++ b/doc/book-enea-nfv-access-evalkit/doc/sdwan_arch.xml @@ -175,7 +175,7 @@ - Interfaces to add: + Interfaces to add (click the " + " button): wan and lan @@ -261,7 +261,7 @@ - Interfaces to add: + Interfaces to add (click the " + " button): wan, lan and mgmt. @@ -279,7 +279,7 @@ - Properties to add: + Properties to add (click the " + " button): @@ -392,8 +392,9 @@ deviceId - The ID extracted from device1 after running - list_deviceID.sh. + The ID extracted from device1 + after running list_deviceID.sh on the + NFV Access CLI. @@ -430,23 +431,16 @@ Source: enp7s0f1. This is just an example interface. The user must - select the interface needed for use with the LAN - connection. + select the interface needed for use with the LAN connection. + To locate the name of the interface, run + ifconfig on the NFV Access CLI. - - Type: N/A. - - networking-type: standard. - - - dpdk-type: N/A. - Click Create, and the @@ -616,8 +610,9 @@ deviceId - The ID extracted from device2 after running - list_deviceID.sh. + The ID extracted from device2 + after running list_deviceID.sh on the + NFV Access CLI. @@ -654,23 +649,16 @@ Source: eno4. This is just an example interface. The user must - select the interface needed for use with the LAN - connection. + select the interface needed for use with the LAN connection. + To locate the name of the interface, run + ifconfig on the NFV Access CLI. - - Type: standard. - - networking-type: standard. - - - dpdk-type: N/A. - Click Create, and the @@ -778,7 +766,9 @@ Sub-type: - communication. Name: eno4 + communication. + + Name: eno4 @@ -806,8 +796,8 @@ - Reset the ZTP: device -> Configure -> - Host -> initial-config-complete: false -> Apply. + Reset the ZTP: device -> Configuration + -> Host -> initial-config-complete: false -> Apply. @@ -839,7 +829,7 @@ Release - 1.0 + 2.2.1 @@ -897,7 +887,7 @@ To add the device on the map: Right-Click on - the Map -> Place Device -> ucpe1. + the Map -> Place Device -> Ucpe1. @@ -928,7 +918,7 @@ Release - 1.0 + 2.2.1 @@ -986,7 +976,7 @@ To add the device on the map: Right-Click on - the Map -> Place Device -> ucpe2. + the Map -> Place Device -> Ucpe2. @@ -997,14 +987,14 @@ 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 -> + and select <Ucpe1> -> Configuration -> OpenVSwitch -> Bridges.
FlexiWAN VNF Instantiation on device1 - Instantiate the FlexiWAN VNF by selecting the ucpe1 device, then the + Instantiate the FlexiWAN VNF by selecting the Ucpe1 device, then the VNF menu -> Instances -> Add. @@ -1057,7 +1047,8 @@ IF Name: Bridge: ibm_br. - Click Create. + NIC Model: + virtio. @@ -1126,7 +1117,8 @@ IF Name: Bridge: sfc_br. - Click Create. + NIC Model: + virtio. @@ -1141,7 +1133,8 @@ IF Name: Bridge: lan_br. - Click Create. + NIC Model: + virtio. @@ -1217,7 +1210,8 @@ IF Name: Bridge: ibm_br. - Click Create. + NIC Model: + virtio. @@ -1232,6 +1226,9 @@ IF Name: Bridge: sfc_br. + NIC Model: + virtio. + Click Create. @@ -1286,7 +1283,8 @@ IF Name: Bridge: sfc_br. - Click Create. + NIC Model: + virtio. @@ -1301,7 +1299,8 @@ IF Name: Bridge: lan_br. - Click Create. + NIC Model: + virtio. @@ -1316,6 +1315,9 @@ IF Name: Bridge: vnf_mgmt_br. + NIC Model: + virtio. + Click Create. @@ -1373,11 +1375,11 @@ - Description: Set IPv4 for the second interface - (ens3): 10.0.1.1/24. + 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. + Description (set IPv4 for the second interface + (ens3)): 10.0.2.1/24 diff --git a/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml b/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml index 6a129e8..3a7e72d 100644 --- a/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml +++ b/doc/book-enea-nfv-access-evalkit/doc/setup_cleanup.xml @@ -3,47 +3,28 @@ Setup Clean-up In order to remove the setup all components need to be deleted in - reverse order: + reverse order. - - - Select the ucpe1 device, access the VNF menu - then Instances FlexiWAN and pfSense and press - Delete. - + Perform the following steps for both Ucpe1 and Ucpe2 + respectively: + - 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 + Select the 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 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. + Select the device, access the Configuration + menu, then OpenVSwitch -> Host + Interfaces. Select all interfaces and press Delete. @@ -57,5 +38,11 @@ Offline Config. Select both device configurations and delete them. + + + Access the Device menu, select + Manager. Select both uCPE devices and remove + them. + \ No newline at end of file -- cgit v1.2.3-54-g00ecf