diff options
Diffstat (limited to 'doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml')
-rw-r--r-- | doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml | 10 |
1 files changed, 5 insertions, 5 deletions
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 8b82337..24442af 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,9 +11,9 @@ | |||
11 | 11 | ||
12 | <para>The following is an example of how to setup and configure a | 12 | <para>The following is an example of how to setup and configure a |
13 | branch-to-branch service comprised on two commercial VNFs (SD-WAN + | 13 | branch-to-branch service comprised on two commercial VNFs (SD-WAN + |
14 | Firewall). This service will run in a service chain on top of the Enea NFV | 14 | Firewall). This service will run in a service chain on top of the Enea |
15 | Access virtualization platform, deployed through the Enea uCPE | 15 | Edge Runtime, deployed through the Enea Edge |
16 | Manager.</para> | 16 | Management.</para> |
17 | 17 | ||
18 | <para>In the example setup the following commercial VNFs are used: Juniper | 18 | <para>In the example setup the following commercial VNFs are used: Juniper |
19 | vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.</para> | 19 | vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.</para> |
@@ -61,7 +61,7 @@ | |||
61 | </listitem> | 61 | </listitem> |
62 | 62 | ||
63 | <listitem> | 63 | <listitem> |
64 | <para>VNF Configuration files, provided with your Enea NFV Access | 64 | <para>VNF Configuration files, provided with your Enea Edge |
65 | Release:</para> | 65 | Release:</para> |
66 | 66 | ||
67 | <itemizedlist spacing="compact"> | 67 | <itemizedlist spacing="compact"> |
@@ -152,7 +152,7 @@ | |||
152 | <para>The networking setup (Steps 1-3) can be modeled using the | 152 | <para>The networking setup (Steps 1-3) can be modeled using the |
153 | Offline Configuration entry, so that it is automatically | 153 | Offline Configuration entry, so that it is automatically |
154 | provisioned on the uCPE device, once it gets enrolled into the | 154 | provisioned on the uCPE device, once it gets enrolled into the |
155 | management system (uCPE Manager).</para> | 155 | management system (Enea Edge Management).</para> |
156 | </note> | 156 | </note> |
157 | </listitem> | 157 | </listitem> |
158 | </orderedlist> | 158 | </orderedlist> |