From d9ca884ea9ab048b795ed551ede0bee2d17319be Mon Sep 17 00:00:00 2001 From: mrpa Date: Thu, 27 Aug 2020 10:23:12 +0200 Subject: Final edits 2.2.3 part 3. Change-Id: I28eefc6092ebba6d77700a05ecbd12f0bcc00ae6 Signed-off-by: mrpa --- .../doc/128t_vnf_router.xml | 18 ++----------- .../doc/appendix_5.xml | 6 ++--- .../doc/book.xml | 9 ------- .../doc/introduction.xml | 30 ++++++++++++---------- .../doc/service_chaining_128t_fortigate.xml | 12 ++------- .../doc/known_bugs_and_limitations.xml | 9 +++++++ 6 files changed, 32 insertions(+), 52 deletions(-) diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml index d58f101..7ba8a7b 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml @@ -39,27 +39,13 @@ - cloud-init iso image. Please check Appendix A: How to create a 128T - cloud-init iso image (day-0 configuration) in the - Manual for more details. + cloud-init iso image. For data path validation, it may be required to generate a new - cloud-init image to match your network configuration. Please check - Appendix A: How to create 128T cloud-init - iso image (day-0 configuration) in the - Manual for more details. + cloud-init image to match your network configuration. diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml index 2097435..ea99e4f 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml @@ -42,16 +42,16 @@ The FortiGate and 128T VNF images need to be copied into the vnf_image directory. The names should be the same as - those described in Appendix D. + those described in the previous appendix. The FortiGate valid license file needs to be copied into the vnf_config/fortigate/ directory. The name should be the - same as that described in Appendix D. + same as that described in the previous appendix. The cloud init files that match the network, need to be copied into the vnf_config/fortigate/ and the vnf_config/128t/ directories respectively. The names - should be the same as those described in Appendix D. + should be the same as those described in the previous appendix.
Use-case 1: 128T VNF Router Example Use-case diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml index 05fd522..eb8b0c8 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml @@ -36,15 +36,6 @@ - - - - - - diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml index 456ab50..fc3559b 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml @@ -6,20 +6,22 @@ configuration, onboarding and instantiation of certain VNFs, VNF chaining, etc. + Before running any example use case make sure the uCPE device(s) have + been added to the uCPE Manager and placed on the map. For detailed + information on how to add a device to the uCPE Manager, how to configure the + network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF + configuration, please refer to the Manual. + - Before running any example use case make sure the uCPE device(s) have been - added to the uCPE Manager and placed on the map. + Examples presented in this document use 3rd-party VNFs, which are + not provided by Enea. To procure and use these VNF image files and license + files, please contact the VNF provider. - For detailed information on how to add a device to the uCPE Manager, - how to configure the network interfaces to use DPDK, PCI-passthrough or - SR-IOV drivers, or VNF configuration, please refer to the - Manual. + Request the VNF prerequisites from the VNF vendors, or alternatively + obtain the prerequisites based on instructions from each VNF vendor + respectively. - - Examples presented in this document use 3rd-party VNFs, which - are not provided by Enea. To procure and use these VNF image files and license files, - where applicable, please contact the VNF provider. - + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml index 43c3fce..1f3a6ce 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml @@ -57,14 +57,7 @@ - Cloud-init iso image. Please check Appendix A: How to create a 128T - cloud-init iso image (day-0 configuration) in the - Manual for more details. + Cloud-init iso image. @@ -1035,8 +1028,7 @@ interface is configured with a DHCP server):> dhclient eth1 > ping 8.8.8.8For data path validation, a new cloud-init image may need to be generated for the 128T VNF to match your network - configuration. Please check Appendix A "How to create 128T cloud-init - iso image (day-0 configuration)" for details. + configuration.
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml index cdea2be..0980783 100644 --- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml @@ -129,6 +129,15 @@ igb_uio. However, the limitation stated above still applies so all the interfaces must be assigned to vfio-pci. + + When an in-band management bridge is configured with DPDK enabled, + the igb_uio driver is used. If the in-band management + interface is assigned to a VM, and there are other interfaces assigned + to the VM that use the vfio-pci driver (this includes + SR-IOV interfaces and PCI passthrough interfaces), then the VM must be + stopped before restarting the vCPE service on the device + (systemctl restart vcpe). Rebooting the device does + not have this restriction. -- cgit v1.2.3-54-g00ecf