From ab617d889d170121bc3a055a2f1503d9cac65394 Mon Sep 17 00:00:00 2001 From: jaar Date: Mon, 20 Jan 2020 14:55:30 +0100 Subject: Text changes in example use cases Update of prerequisities for all example use cases. Update of memory requirement for VNF chaining example. Change-Id: I0aee42c2de3cb3ec8250db51eb1ffc6fc9dc48e2 Signed-off-by: jaar --- .../doc/clav_vnf_examples.xml | 180 +++++++++++++-------- .../doc/forti_vnf_examples.xml | 174 +++++++++++++------- .../doc/vnf_chaining.xml | 150 ++++++++--------- 3 files changed, 286 insertions(+), 218 deletions(-) diff --git a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml index 7d69d43..1da91fe 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml @@ -5,54 +5,6 @@ The Clavister VNF is a telco-ready, carrier-grade virtual next generation firewall. -
- Prerequisites - - System requirements for the uCPE devices: - - - - 1 Network Interface - - - - 2 GB of RAM memory - - - - The following files are needed for this example use case: - - - VNF images: - - - Enea Test VNF. Please contact Enea to get this image. - - - - Clavister VNF. Please contact Clavister to get this - image. - - - - - VNF Configuration files, these files are provided with your Enea - NFV Access release: - - - clavister-cloudinit.conf. - - - - enea-vnf-iperf-client.conf. - - - - enea-vnf-iperf-server.conf. - - -
-
Clavister VNF using an Open vSwitch Bridge @@ -61,20 +13,71 @@ applications. The uCPE devices are connected using OVS-DPDK bridges. -
- Clavister VNF using an Open vSwitch bridge +
+ Prerequisites + + Two uCPE devices will be required for this setup. The system + requirements for each uCPE device are: + + + + 1 Network Interface + + + + 2 GB of RAM memory + + + + The following files are needed for this example use-case: - - - - - -
+ + + Enea Test VNF image. Please contact Enea to get this image. + + + + Clavister VNF image. Please contact Clavister to get this + image. + + + VNF Configuration files. These files are provided with your Enea + NFV Access release: + + + clavister-cloudinit.conf. + enea-vnf-iperf-client.conf. + enea-vnf-iperf-server.conf. + + + +
Use-case Setup + In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE + device 2 runs two Enea Test VNFs with iPerf client and server + applications. The uCPE devices are connected using OVS-DPDK + bridges. + +
+ Clavister VNF using an Open vSwitch bridge + + + + + + +
+ + + When connecting, the uCPE devices can use a back-to-back or a VPN connection. + An appropriate interface with the required capabilities needs to be chosen for + this purpose. + + Network Configuration: @@ -301,24 +304,63 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10
Clavister VNF using SR-IOV - The following use-case is essentially the same as the one detailed - above, in this scenario however, the uCPE devices are connected using - SR-IOV, with two virtual functions. +
+ Prerequisites + + Two uCPE devices will be required for this setup. The system + requirements for each uCPE device are: -
- Clavister VNF using SR-IOV + + + 1 Network Interface + + + + 2 GB of RAM memory + + - - - - - -
+ The following files are needed for this example use-case: + + + + Enea Test VNF image. Please contact Enea to get this image. + + + + Clavister VNF image. Please contact Clavister to get this + image. + + + VNF Configuration files. These files are provided with your Enea + NFV Access release: + + clavister-cloudinit.conf. + enea-vnf-iperf-client.conf. + enea-vnf-iperf-server.conf. + + + +
Use-case Setup + The following use-case is essentially the same as the one detailed + above, in this scenario however, the uCPE devices are connected using + SR-IOV, with two virtual functions. + +
+ Clavister VNF using SR-IOV + + + + + + +
+ Network Configuration: diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml index 1187b07..547cda4 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml @@ -7,50 +7,6 @@ appliances. The virtual appliances can be integrated in Firewall or SD-WAN solution development. -
- Prerequisites - - System requirements for the uCPE device: - - - - 4 x Network Interfaces - - - - 4 cores - - - - 4 GB of RAM memory - - - - The following files are needed for this example use case: - - - VNF image: - - - FortiGate VNF. Please contact Fortinet to get a VNF image and - its license file. - - - - - VNF Configuration files, provided with your Enea NFV Access - release: - - - fortigate-basic-fw.conf. - - - - fortigate-sdwan<x>.conf. - - -
-
FortiGate VNF as a Firewall @@ -66,20 +22,57 @@ xpointer="element(book_enea_nfv_access_example_usecases/1)" /> Manual. -
- Fortigate VNF as a Firewall +
+ Prerequisites + + System requirements for the uCPE device: + + + + 4 x Network Interfaces + + + + 4 cores + + + + 4 GB of RAM memory + + + + The following files are needed for this example use-case: + + + + FortiGate VNF image. Please contact Fortinet to get a VNF image and + its license file. + - - - - - -
+ VNF Configuration files, provided with your Enea NFV Access + release: + + fortigate-basic-fw.conf. + fortigate-sdwan<x>.conf. + + + +
Use-case Setup +
+ Fortigate VNF as a Firewall + + + + + + +
+ Network Configuration: Since the firewall uses three External Network Interfaces, three @@ -234,6 +227,13 @@ Outgoing Interface type to DPDK and connect it to the lan2 ovs bridge. + + + The names of the ports used during instantiation need to be + the same as the ones described above, as the same names will be used in + the configuration files provided for this example use-case. + +
@@ -279,20 +279,64 @@ Example SD-WAN configurations for the FortiGate VNF are provided by Enea. -
- Fortigate VNF as an SD-WAN or a VPN +
+ Prerequisites + + Two uCPE devices will be needed for this setup. The system + requirements for each uCPE device are: + + + + 4 x Network Interfaces + + + + 4 cores + + + + 4 GB of RAM memory + + + + The following files are needed for this example use-case: + + + + FortiGate VNF image. Please contact Fortinet to get a VNF image and + its license file. + - - - - - -
+ VNF Configuration files, provided with your Enea NFV Access + release: + + fortigate-basic-fw.conf. + fortigate-sdwan<x>.conf. + + + +
Use-case Setup +
+ Fortigate VNF as an SD-WAN or a VPN + + + + + + +
+ + + When connecting, the uCPE devices can use a back-to-back or a VPN connection. + An appropriate interface with the required capabilities needs to be chosen for + this purpose. + + Network Configuration: Since the SD-WAN VNF uses three External Network Interfaces, three @@ -466,6 +510,12 @@ Instantiate the FortiGate VNF on uCPE device 1 using the sdwan1 example configuration file. + + The names of the ports used during instantiation need to be the + same as the ones described above, as the same names will be used in + the configuration files provided for this example use-case. + + To complete the branch-to-branch setup, configure uCPE device 2 in the same way as uCPE device 1. Make sure to use the sdwan2 configuration file for diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml index 18bc226..83dd51e 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml @@ -11,83 +11,72 @@ In the example setup the following commercial VNFs are used: Juniper vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall. -
- Prerequisites - - System requirements for the uCPE device: - - - - 3 x Network Interfaces - - - - 4 GB of RAM memory - - - - The following files are needed for this example use case: - - - VNF images: - - - Fortigate VNF. - - - - Juniper vSRX VNF. - - - - For VNF images and their license files, please contact the VNF - provider. - - - VNF Configuration files, provided with your Enea NFV Access - Release: - - - vSRX-domain-update-script. - - - - vSRX-Site<x>.conf. - - - - FortiFW-Site<x>.conf. - - -
-
VNF Chaining with FortiGate - The setup requires two physical appliances (uCPEs), each of them - having three DPDK-compatible NICs and one interface available for uCPE - management (i.e. connected to Enea uCPE Manager). On each uCPE, one of the - DPDK-compatible interfaces is connected back-to-back with one interface - from the other uCPE device. This link simulates a WAN/uplink - connection. +
+ Prerequisites - Optionally, one additional device (PC/laptop) can be connected on - the LAN port of each branch to run LAN-to-LAN connectivity tests. + Two uCPE devices will be needed for this setup. The system + requirements for each uCPE device are: -
- VNF Chaining with Fortigate + + + 4 x Network Interfaces + - - - - - -
+ + 4 GB of RAM memory + + + + + On each uCPE device, 3 interfaces need to be DPDK compliant and one + of these needs to be connected back-to-back to the other uCPE + device. This link simulates a WAN/uplink connection. Optionally, + one additional device (PC/laptop) can be connected on the LAN port + of each branch to run LAN-to-LAN connectivity tests. + + + The following files are needed for this example use-case: + + To procure the VNF image files and their licenses, please contact each respective VNF + provider. + + + + Fortigate VNF image file. + + + + Juniper vSRX VNF image file. + + + VNF Configuration files, provided with your Enea NFV Access + Release: + + vSRX-domain-update-script. + vSRX-Site<x>.conf. + FortiFW-Site<x>.conf. + + + +
Use-case Setup +
+ VNF Chaining with Fortigate + + + + + + +
+ Network Configuration: Both branches in the example have similar setups, therefore @@ -139,7 +128,7 @@ The networking setup (Steps 1-3) can be modeled using the Offline Configuration entry, so that it is automatically - provisioned on the uCPE, once it gets enrolled into the management + provisioned on the uCPE device, once it gets enrolled into the management system (uCPE Manager). @@ -152,12 +141,12 @@ Onboard Juniper vSRX using the VNF by filling the required fields with the following values: - + - The Flavor selected must have at least 2 CPUs and 4 GB RAM + The Flavor selected must have at least 2 CPUs and 3 GB RAM since vSRX is quite resource consuming. - Tested-inhouse with 4 vCPUs/ 6 GB RAM. + Tested in-house with 4 vCPUs/ 3 GB RAM. @@ -178,7 +167,7 @@ The Flavor selected can be quite light in resource - consumption, e.g. 1 CPU and 2 GB RAM. + consumption, e.g. 1 CPU and 1 GB RAM. @@ -196,11 +185,6 @@ in the Cloud-Init tab files. - - - Steps 4-5 are done only once, i.e. they will not be repeated - for Site 2. - @@ -216,7 +200,7 @@ file. - Please follow the Juniper's documentation to create + Please follow Juniper's documentation to create the vSRX-Site1.iso file. @@ -236,16 +220,12 @@ Management interface added to vnf_mgmt_br. - - WAN interface added to wan_br. - - LAN interface added to sfc_br. @@ -265,7 +245,7 @@ - Use FortiFW-Site1.conf as Cloud-Init + Use FortiFW-Site1.conf as the Cloud-Init file. @@ -282,16 +262,12 @@ Management interface added to vnf_mgmt_br. - - WAN interface added to sfc_br. - - LAN interface added to lan_br. -- cgit v1.2.3-54-g00ecf