diff options
Diffstat (limited to 'doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml')
-rw-r--r-- | doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml | 1064 |
1 files changed, 1064 insertions, 0 deletions
diff --git a/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml new file mode 100644 index 0000000..4529fbf --- /dev/null +++ b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml | |||
@@ -0,0 +1,1064 @@ | |||
1 | <?xml version="1.0" encoding="UTF-8"?> | ||
2 | <chapter id="service_chaining_128t_fortigate"> | ||
3 | <title>Service Chaining 128T - Fortigate Example Use-case</title> | ||
4 | |||
5 | <para>The following is an example of how to setup and configure a service | ||
6 | chain on top of the Enea Edge Runtime, using the following commercial VNFs: | ||
7 | 128T router and FortiGate.</para> | ||
8 | |||
9 | <section id="prereq_serv_chain_cust"> | ||
10 | <title>Prerequisites</title> | ||
11 | |||
12 | <para>The 128T router and the Fortinet firewall in a service chain require | ||
13 | the following prequisites for this example use case:</para> | ||
14 | |||
15 | <itemizedlist spacing="compact"> | ||
16 | <listitem> | ||
17 | <para>1 in band management port for device management.</para> | ||
18 | </listitem> | ||
19 | |||
20 | <listitem> | ||
21 | <para>1 in band management port for the 128T router.</para> | ||
22 | </listitem> | ||
23 | |||
24 | <listitem> | ||
25 | <para>1 in band management port for Fortinet.</para> | ||
26 | </listitem> | ||
27 | |||
28 | <listitem> | ||
29 | <para>1 WAN interface for Fortinet.</para> | ||
30 | </listitem> | ||
31 | |||
32 | <listitem> | ||
33 | <para>1 LAN facing interface for Fortinet.</para> | ||
34 | </listitem> | ||
35 | |||
36 | <listitem> | ||
37 | <para>1 WAN facing interface for the 128T router.</para> | ||
38 | </listitem> | ||
39 | |||
40 | <listitem> | ||
41 | <para>1 service chain (SFC Bridged interface) to sit between the | ||
42 | Firewall and vRouter.</para> | ||
43 | </listitem> | ||
44 | </itemizedlist> | ||
45 | |||
46 | <para>The following files are needed for this example use-case:</para> | ||
47 | |||
48 | <itemizedlist spacing="compact"> | ||
49 | <listitem> | ||
50 | <para>FortiGate VNF image. Please contact Fortinet to get a VNF image | ||
51 | and its license file.</para> | ||
52 | </listitem> | ||
53 | |||
54 | <listitem> | ||
55 | <para>128T router VNF image. Please contact 128 Technology to get a | ||
56 | VNF image and its license file.</para> | ||
57 | </listitem> | ||
58 | |||
59 | <listitem> | ||
60 | <para>Cloud-init iso image.</para> | ||
61 | </listitem> | ||
62 | </itemizedlist> | ||
63 | |||
64 | <note> | ||
65 | <para>To procure the VNF image files and their licenses, please contact | ||
66 | each respective VNF provider.</para> | ||
67 | </note> | ||
68 | </section> | ||
69 | |||
70 | <section id="ser_chain_uc"> | ||
71 | <title>Service Chaining 128T - Fortigate</title> | ||
72 | |||
73 | <figure> | ||
74 | <title>Service Chaining 128T - Fortigate Setup Overview</title> | ||
75 | |||
76 | <mediaobject> | ||
77 | <imageobject> | ||
78 | <imagedata contentwidth="600" fileref="images/trgt_servicechain.png" /> | ||
79 | </imageobject> | ||
80 | </mediaobject> | ||
81 | </figure> | ||
82 | |||
83 | <section> | ||
84 | <title>Use-case Setup</title> | ||
85 | |||
86 | <para><emphasis role="bold">Configuring Network Interfaces on uCPE | ||
87 | devices:</emphasis><orderedlist> | ||
88 | <listitem> | ||
89 | <para>Add the trgt uCPE device into the Enea Edge Management | ||
90 | application: <literal>Devices -> Manage -> Add</literal>, | ||
91 | and fill in the required fields with the following data:</para> | ||
92 | |||
93 | <table> | ||
94 | <title>Device Details</title> | ||
95 | |||
96 | <tgroup cols="2"> | ||
97 | <colspec align="left" /> | ||
98 | |||
99 | <colspec colwidth="2*" /> | ||
100 | |||
101 | <colspec colwidth="5*" /> | ||
102 | |||
103 | <thead> | ||
104 | <row> | ||
105 | <entry align="center">Field</entry> | ||
106 | |||
107 | <entry align="center">Value</entry> | ||
108 | </row> | ||
109 | </thead> | ||
110 | |||
111 | <tbody> | ||
112 | <row> | ||
113 | <entry>Type</entry> | ||
114 | |||
115 | <entry>Enea universal CPE</entry> | ||
116 | </row> | ||
117 | |||
118 | <row> | ||
119 | <entry>Release</entry> | ||
120 | |||
121 | <entry>2.2.2</entry> | ||
122 | </row> | ||
123 | |||
124 | <row> | ||
125 | <entry>Name</entry> | ||
126 | |||
127 | <entry>trgt</entry> | ||
128 | </row> | ||
129 | |||
130 | <row> | ||
131 | <entry>IP/DNS Address</entry> | ||
132 | |||
133 | <entry><unspecified></entry> | ||
134 | </row> | ||
135 | |||
136 | <row> | ||
137 | <entry>Description</entry> | ||
138 | |||
139 | <entry>Target 1</entry> | ||
140 | </row> | ||
141 | |||
142 | <row> | ||
143 | <entry>SSH Port</entry> | ||
144 | |||
145 | <entry>830</entry> | ||
146 | </row> | ||
147 | |||
148 | <row> | ||
149 | <entry>SSH User Name</entry> | ||
150 | |||
151 | <entry>root</entry> | ||
152 | </row> | ||
153 | |||
154 | <row> | ||
155 | <entry>Password</entry> | ||
156 | |||
157 | <entry>null</entry> | ||
158 | </row> | ||
159 | |||
160 | <row> | ||
161 | <entry>Device ID</entry> | ||
162 | |||
163 | <entry>Also configured during installation of the device | ||
164 | (E.g.: Target-15).</entry> | ||
165 | </row> | ||
166 | |||
167 | <row> | ||
168 | <entry>OK</entry> | ||
169 | |||
170 | <entry>Green status indicates connection with uCPE device | ||
171 | was established.</entry> | ||
172 | </row> | ||
173 | </tbody> | ||
174 | </tgroup> | ||
175 | </table> | ||
176 | </listitem> | ||
177 | |||
178 | <listitem> | ||
179 | <para>In order to add the device on the map: Right-Click on | ||
180 | <literal>Map -> Place Device -> trgt</literal>.</para> | ||
181 | </listitem> | ||
182 | |||
183 | <listitem> | ||
184 | <para>Configure the infrastructure for the 128T and Fortigate VNFs | ||
185 | in the service chain by creating four OVS bridges and a host | ||
186 | interface.</para> | ||
187 | |||
188 | <para>Add the Host Interface by selecting the trgt device, then | ||
189 | <literal>Configuration -> External Interfaces -> | ||
190 | Configuration -> Add</literal>, and fill in the required fields | ||
191 | with the following data:</para> | ||
192 | |||
193 | <table> | ||
194 | <title>Host Interface Details</title> | ||
195 | |||
196 | <tgroup cols="2"> | ||
197 | <colspec align="left" /> | ||
198 | |||
199 | <colspec colwidth="2*" /> | ||
200 | |||
201 | <colspec colwidth="5*" /> | ||
202 | |||
203 | <thead> | ||
204 | <row> | ||
205 | <entry align="center">Field</entry> | ||
206 | |||
207 | <entry align="center">Value</entry> | ||
208 | </row> | ||
209 | </thead> | ||
210 | |||
211 | <tbody> | ||
212 | <row> | ||
213 | <entry>Source</entry> | ||
214 | |||
215 | <entry><literal>enp4s0f1</literal>. The only interface | ||
216 | available for LAN connection.</entry> | ||
217 | </row> | ||
218 | |||
219 | <row> | ||
220 | <entry>networking-type</entry> | ||
221 | |||
222 | <entry>dpdk</entry> | ||
223 | </row> | ||
224 | |||
225 | <row> | ||
226 | <entry>dpdk-type</entry> | ||
227 | |||
228 | <entry>vfio-pci</entry> | ||
229 | </row> | ||
230 | |||
231 | <row> | ||
232 | <entry>Create</entry> | ||
233 | |||
234 | <entry><interface enp4s0f1 ready to be used in a LAN | ||
235 | bridge.></entry> | ||
236 | </row> | ||
237 | </tbody> | ||
238 | </tgroup> | ||
239 | </table> | ||
240 | |||
241 | <para>Add the OVS bridges by selecting the trgt device then: | ||
242 | <literal>Configuration -> OpenVSwitch -> Bridges -> | ||
243 | Add</literal>. Fill in the required fields for each bridge with | ||
244 | the following data from each table:</para> | ||
245 | |||
246 | <table> | ||
247 | <title>ibm_br Bridge Details</title> | ||
248 | |||
249 | <tgroup cols="2"> | ||
250 | <colspec align="left" /> | ||
251 | |||
252 | <colspec colwidth="2*" /> | ||
253 | |||
254 | <colspec colwidth="5*" /> | ||
255 | |||
256 | <thead> | ||
257 | <row> | ||
258 | <entry align="center">Field</entry> | ||
259 | |||
260 | <entry align="center">Value</entry> | ||
261 | </row> | ||
262 | </thead> | ||
263 | |||
264 | <tbody> | ||
265 | <row> | ||
266 | <entry>id</entry> | ||
267 | |||
268 | <entry><autogenerated - do not change></entry> | ||
269 | </row> | ||
270 | |||
271 | <row> | ||
272 | <entry>Name</entry> | ||
273 | |||
274 | <entry><literal>ibm_br</literal></entry> | ||
275 | </row> | ||
276 | |||
277 | <row> | ||
278 | <entry>ovs-bridge-type</entry> | ||
279 | |||
280 | <entry>inbandMgmt</entry> | ||
281 | </row> | ||
282 | |||
283 | <row> | ||
284 | <entry>Create</entry> | ||
285 | |||
286 | <entry></entry> | ||
287 | </row> | ||
288 | </tbody> | ||
289 | </tgroup> | ||
290 | </table> | ||
291 | |||
292 | <para></para> | ||
293 | |||
294 | <table> | ||
295 | <title>vnf_mgmt_br Bridge Details</title> | ||
296 | |||
297 | <tgroup cols="2"> | ||
298 | <colspec align="left" /> | ||
299 | |||
300 | <colspec colwidth="2*" /> | ||
301 | |||
302 | <colspec colwidth="5*" /> | ||
303 | |||
304 | <thead> | ||
305 | <row> | ||
306 | <entry align="center">Field</entry> | ||
307 | |||
308 | <entry align="center">Value</entry> | ||
309 | </row> | ||
310 | </thead> | ||
311 | |||
312 | <tbody> | ||
313 | <row> | ||
314 | <entry>id</entry> | ||
315 | |||
316 | <entry><autogenerated - do not change></entry> | ||
317 | </row> | ||
318 | |||
319 | <row> | ||
320 | <entry>Name</entry> | ||
321 | |||
322 | <entry><literal>vnf_mgmt_br</literal></entry> | ||
323 | </row> | ||
324 | |||
325 | <row> | ||
326 | <entry>ovs-bridge-type</entry> | ||
327 | |||
328 | <entry>vnfMgmt</entry> | ||
329 | </row> | ||
330 | |||
331 | <row> | ||
332 | <entry>vnf-mgmt-address</entry> | ||
333 | |||
334 | <entry>10.0.0.1</entry> | ||
335 | </row> | ||
336 | |||
337 | <row> | ||
338 | <entry>Create</entry> | ||
339 | |||
340 | <entry></entry> | ||
341 | </row> | ||
342 | </tbody> | ||
343 | </tgroup> | ||
344 | </table> | ||
345 | |||
346 | <table> | ||
347 | <title>lan_br Bridge Details</title> | ||
348 | |||
349 | <tgroup cols="2"> | ||
350 | <colspec align="left" /> | ||
351 | |||
352 | <colspec colwidth="2*" /> | ||
353 | |||
354 | <colspec colwidth="5*" /> | ||
355 | |||
356 | <thead> | ||
357 | <row> | ||
358 | <entry align="center">Field</entry> | ||
359 | |||
360 | <entry align="center">Value</entry> | ||
361 | </row> | ||
362 | </thead> | ||
363 | |||
364 | <tbody> | ||
365 | <row> | ||
366 | <entry>id</entry> | ||
367 | |||
368 | <entry><autogenerated - do not change></entry> | ||
369 | </row> | ||
370 | |||
371 | <row> | ||
372 | <entry>Name</entry> | ||
373 | |||
374 | <entry><literal>lan_br</literal></entry> | ||
375 | </row> | ||
376 | |||
377 | <row> | ||
378 | <entry>ovs-bridge-type</entry> | ||
379 | |||
380 | <entry>dataPlane</entry> | ||
381 | </row> | ||
382 | |||
383 | <row> | ||
384 | <entry>sub-type</entry> | ||
385 | |||
386 | <entry>communication</entry> | ||
387 | </row> | ||
388 | |||
389 | <row> | ||
390 | <entry>+</entry> | ||
391 | |||
392 | <entry>Name: enp4s0f1 OK</entry> | ||
393 | </row> | ||
394 | |||
395 | <row> | ||
396 | <entry>Create</entry> | ||
397 | |||
398 | <entry></entry> | ||
399 | </row> | ||
400 | </tbody> | ||
401 | </tgroup> | ||
402 | </table> | ||
403 | |||
404 | <table> | ||
405 | <title>sfc_br Bridge Details</title> | ||
406 | |||
407 | <tgroup cols="2"> | ||
408 | <colspec align="left" /> | ||
409 | |||
410 | <colspec colwidth="2*" /> | ||
411 | |||
412 | <colspec colwidth="5*" /> | ||
413 | |||
414 | <thead> | ||
415 | <row> | ||
416 | <entry align="center">Field</entry> | ||
417 | |||
418 | <entry align="center">Value</entry> | ||
419 | </row> | ||
420 | </thead> | ||
421 | |||
422 | <tbody> | ||
423 | <row> | ||
424 | <entry>id</entry> | ||
425 | |||
426 | <entry><autogenerated - do not change></entry> | ||
427 | </row> | ||
428 | |||
429 | <row> | ||
430 | <entry>Name</entry> | ||
431 | |||
432 | <entry><literal>sfc_br</literal></entry> | ||
433 | </row> | ||
434 | |||
435 | <row> | ||
436 | <entry>ovs-bridge-type</entry> | ||
437 | |||
438 | <entry>dataPlane</entry> | ||
439 | </row> | ||
440 | |||
441 | <row> | ||
442 | <entry>sub-type</entry> | ||
443 | |||
444 | <entry>integration</entry> | ||
445 | </row> | ||
446 | |||
447 | <row> | ||
448 | <entry>Create</entry> | ||
449 | |||
450 | <entry></entry> | ||
451 | </row> | ||
452 | </tbody> | ||
453 | </tgroup> | ||
454 | </table> | ||
455 | </listitem> | ||
456 | </orderedlist></para> | ||
457 | |||
458 | <para><emphasis role="bold">Onboarding the VNFs:</emphasis></para> | ||
459 | |||
460 | <para>Onboard the 128T VNF VM Image through <literal>VNF -> | ||
461 | Descriptors -> On-board</literal>, and fill in the required fields | ||
462 | with the following values:</para> | ||
463 | |||
464 | <table> | ||
465 | <title>128T VM Image Details</title> | ||
466 | |||
467 | <tgroup cols="2"> | ||
468 | <colspec align="left" /> | ||
469 | |||
470 | <colspec colwidth="2*" /> | ||
471 | |||
472 | <colspec colwidth="5*" /> | ||
473 | |||
474 | <thead> | ||
475 | <row> | ||
476 | <entry align="center">Field</entry> | ||
477 | |||
478 | <entry align="center">Value</entry> | ||
479 | </row> | ||
480 | </thead> | ||
481 | |||
482 | <tbody> | ||
483 | <row> | ||
484 | <entry>VM image file</entry> | ||
485 | |||
486 | <entry><literal>centos_128t_with_ci.qcow2</literal></entry> | ||
487 | </row> | ||
488 | |||
489 | <row> | ||
490 | <entry>Image format</entry> | ||
491 | |||
492 | <entry>QCOW2</entry> | ||
493 | </row> | ||
494 | |||
495 | <row> | ||
496 | <entry>VNF Type Name</entry> | ||
497 | |||
498 | <entry>128T</entry> | ||
499 | </row> | ||
500 | |||
501 | <row> | ||
502 | <entry>Description</entry> | ||
503 | |||
504 | <entry>128T Router</entry> | ||
505 | </row> | ||
506 | |||
507 | <row> | ||
508 | <entry>Version</entry> | ||
509 | |||
510 | <entry>1.0</entry> | ||
511 | </row> | ||
512 | |||
513 | <row> | ||
514 | <entry>Memory in MB</entry> | ||
515 | |||
516 | <entry>8192. More memory can be allocated if required | ||
517 | (<28672).</entry> | ||
518 | </row> | ||
519 | |||
520 | <row> | ||
521 | <entry>Num. of CPUs</entry> | ||
522 | |||
523 | <entry>2. More CPUs can be reserved if required | ||
524 | (<15).</entry> | ||
525 | </row> | ||
526 | |||
527 | <row> | ||
528 | <entry>Interfaces -> +</entry> | ||
529 | |||
530 | <entry>Name: mgmt</entry> | ||
531 | </row> | ||
532 | |||
533 | <row> | ||
534 | <entry>Interfaces -> +</entry> | ||
535 | |||
536 | <entry>Name: wan</entry> | ||
537 | </row> | ||
538 | |||
539 | <row> | ||
540 | <entry>Interfaces -> +</entry> | ||
541 | |||
542 | <entry>Name: lan</entry> | ||
543 | </row> | ||
544 | |||
545 | <row> | ||
546 | <entry>Cloud Init -> Cloud-Init Datasource</entry> | ||
547 | |||
548 | <entry>ISO</entry> | ||
549 | </row> | ||
550 | |||
551 | <row> | ||
552 | <entry>Cloud Init -> Cloud-Init Disk Type</entry> | ||
553 | |||
554 | <entry>cdrom</entry> | ||
555 | </row> | ||
556 | |||
557 | <row> | ||
558 | <entry>Properties -> +</entry> | ||
559 | |||
560 | <entry>Name: vnfMgmtIpAddress. Value: 10.0.0.2</entry> | ||
561 | </row> | ||
562 | |||
563 | <row> | ||
564 | <entry>Properties -> +</entry> | ||
565 | |||
566 | <entry>Name: internalMgmtPort. Value: 443</entry> | ||
567 | </row> | ||
568 | |||
569 | <row> | ||
570 | <entry>Properties -> +</entry> | ||
571 | |||
572 | <entry>Name: externalMgmtPort. Value: 60001</entry> | ||
573 | </row> | ||
574 | |||
575 | <row> | ||
576 | <entry>Onboard</entry> | ||
577 | |||
578 | <entry><Wait for message: VNF package onboarded | ||
579 | successfully></entry> | ||
580 | </row> | ||
581 | |||
582 | <row> | ||
583 | <entry>Close</entry> | ||
584 | |||
585 | <entry></entry> | ||
586 | </row> | ||
587 | </tbody> | ||
588 | </tgroup> | ||
589 | </table> | ||
590 | |||
591 | <note> | ||
592 | <itemizedlist> | ||
593 | <listitem> | ||
594 | <para>HTTPS access (443) can be changed to another type of access. | ||
595 | Please consult official 128T documentation and make sure the 128T | ||
596 | VNF is configured to accept another type of connection before | ||
597 | changing the port number.</para> | ||
598 | </listitem> | ||
599 | |||
600 | <listitem> | ||
601 | <para><literal>externalMgmtPort(60001)</literal> represents the | ||
602 | external port on which the user can access the VNF management | ||
603 | interface from the web browser via HTTPS. The user can select | ||
604 | another port if needed. There are no other changes required or | ||
605 | components affected by this change.</para> | ||
606 | </listitem> | ||
607 | |||
608 | <listitem> | ||
609 | <para><literal>vnfMgmtIpAddress</literal> (10.0.0.2) represents | ||
610 | the IP address of the management interface of the 128T VNF. | ||
611 | Changing this value requires an update to the 128T configuration | ||
612 | to match the new IP address.</para> | ||
613 | </listitem> | ||
614 | </itemizedlist> | ||
615 | </note> | ||
616 | |||
617 | <para>Onboard the Fortigate VNF VM Image through <literal>VNF -> | ||
618 | Descriptors -> On-board</literal>, and fill in the required fields | ||
619 | with the following values:</para> | ||
620 | |||
621 | <table> | ||
622 | <title>Fortigate VM Image Details</title> | ||
623 | |||
624 | <tgroup cols="2"> | ||
625 | <colspec align="left" /> | ||
626 | |||
627 | <colspec colwidth="2*" /> | ||
628 | |||
629 | <colspec colwidth="5*" /> | ||
630 | |||
631 | <thead> | ||
632 | <row> | ||
633 | <entry align="center">Field</entry> | ||
634 | |||
635 | <entry align="center">Value</entry> | ||
636 | </row> | ||
637 | </thead> | ||
638 | |||
639 | <tbody> | ||
640 | <row> | ||
641 | <entry>VM image file</entry> | ||
642 | |||
643 | <entry><literal>fortios.qcow2</literal>. Please make sure to | ||
644 | contact Fortinet for an official FortiGate KVM image.</entry> | ||
645 | </row> | ||
646 | |||
647 | <row> | ||
648 | <entry>Image format</entry> | ||
649 | |||
650 | <entry>QCOW2</entry> | ||
651 | </row> | ||
652 | |||
653 | <row> | ||
654 | <entry>VNF Type Name</entry> | ||
655 | |||
656 | <entry>Fortigate</entry> | ||
657 | </row> | ||
658 | |||
659 | <row> | ||
660 | <entry>Description</entry> | ||
661 | |||
662 | <entry>Fortigate VNF</entry> | ||
663 | </row> | ||
664 | |||
665 | <row> | ||
666 | <entry>Version</entry> | ||
667 | |||
668 | <entry>1.0</entry> | ||
669 | </row> | ||
670 | |||
671 | <row> | ||
672 | <entry>Memory in MB</entry> | ||
673 | |||
674 | <entry>1024. More memory can be allocated if required | ||
675 | (<28672).</entry> | ||
676 | </row> | ||
677 | |||
678 | <row> | ||
679 | <entry>Num. of CPUs</entry> | ||
680 | |||
681 | <entry>1. More CPUs can be reserved if required | ||
682 | (<15).</entry> | ||
683 | </row> | ||
684 | |||
685 | <row> | ||
686 | <entry>Interfaces -> +</entry> | ||
687 | |||
688 | <entry>Name: mgmt</entry> | ||
689 | </row> | ||
690 | |||
691 | <row> | ||
692 | <entry>Interfaces -> +</entry> | ||
693 | |||
694 | <entry>Name: wan</entry> | ||
695 | </row> | ||
696 | |||
697 | <row> | ||
698 | <entry>Interfaces -> +</entry> | ||
699 | |||
700 | <entry>Name: lan</entry> | ||
701 | </row> | ||
702 | |||
703 | <row> | ||
704 | <entry>Cloud Init -> Cloud-Init Datasource</entry> | ||
705 | |||
706 | <entry>ConfigDrive</entry> | ||
707 | </row> | ||
708 | |||
709 | <row> | ||
710 | <entry>Cloud Init -> Cloud-Init Disk Type</entry> | ||
711 | |||
712 | <entry>cdrom</entry> | ||
713 | </row> | ||
714 | |||
715 | <row> | ||
716 | <entry>Cloud Init -> +</entry> | ||
717 | |||
718 | <entry>Path: license</entry> | ||
719 | </row> | ||
720 | |||
721 | <row> | ||
722 | <entry>Properties -> +</entry> | ||
723 | |||
724 | <entry>Name: vnfMgmtIpAddress. Value: 10.0.0.3</entry> | ||
725 | </row> | ||
726 | |||
727 | <row> | ||
728 | <entry>Properties -> +</entry> | ||
729 | |||
730 | <entry>Name: internalMgmtPort. Value: 443</entry> | ||
731 | </row> | ||
732 | |||
733 | <row> | ||
734 | <entry>Properties -> +</entry> | ||
735 | |||
736 | <entry>Name: externalMgmtPort. Value: 60002</entry> | ||
737 | </row> | ||
738 | |||
739 | <row> | ||
740 | <entry>Onboard</entry> | ||
741 | |||
742 | <entry><Wait for message: VNF package onboarded | ||
743 | successfully></entry> | ||
744 | </row> | ||
745 | |||
746 | <row> | ||
747 | <entry>Close</entry> | ||
748 | |||
749 | <entry></entry> | ||
750 | </row> | ||
751 | </tbody> | ||
752 | </tgroup> | ||
753 | </table> | ||
754 | |||
755 | <note> | ||
756 | <itemizedlist> | ||
757 | <listitem> | ||
758 | <para>HTTPS access (443) can be changed to another type of access. | ||
759 | Please consult official Fortigate documentation and make sure the | ||
760 | Fortigate VNF is configured to accept another type of connection | ||
761 | before changing the port number.</para> | ||
762 | </listitem> | ||
763 | |||
764 | <listitem> | ||
765 | <para><literal>externalMgmtPort</literal> (60002) represents the | ||
766 | external port on which the user can access the VNF management | ||
767 | interface from the web browser via HTTPS. The user can select | ||
768 | another port if needed. There are no other changes required or | ||
769 | components affected by this change.</para> | ||
770 | </listitem> | ||
771 | |||
772 | <listitem> | ||
773 | <para><literal>vnfMgmtIpAddress</literal> (10.0.0.3) represents | ||
774 | the IP address of the management interface of the Fortigate VNF. | ||
775 | Changing this value requires an update to the Fortigate | ||
776 | configuration to match with new IP address.</para> | ||
777 | </listitem> | ||
778 | </itemizedlist> | ||
779 | </note> | ||
780 | |||
781 | <para><emphasis role="bold">Instantiating the VNFs:</emphasis></para> | ||
782 | |||
783 | <para>Instantiate the 128T VNF by selecting the trgt device, then | ||
784 | <literal>VNF -> Instances -> Add</literal>.</para> | ||
785 | |||
786 | <para>Fill in the required fields with the following values:</para> | ||
787 | |||
788 | <table> | ||
789 | <title>128T VNF Instantiation</title> | ||
790 | |||
791 | <tgroup cols="2"> | ||
792 | <colspec align="left" /> | ||
793 | |||
794 | <colspec colwidth="2*" /> | ||
795 | |||
796 | <colspec colwidth="5*" /> | ||
797 | |||
798 | <thead> | ||
799 | <row> | ||
800 | <entry align="center">Field</entry> | ||
801 | |||
802 | <entry align="center">Value</entry> | ||
803 | </row> | ||
804 | </thead> | ||
805 | |||
806 | <tbody> | ||
807 | <row> | ||
808 | <entry>Name</entry> | ||
809 | |||
810 | <entry>128T_trgt_1</entry> | ||
811 | </row> | ||
812 | |||
813 | <row> | ||
814 | <entry>VNF Type</entry> | ||
815 | |||
816 | <entry>128T</entry> | ||
817 | </row> | ||
818 | |||
819 | <row> | ||
820 | <entry>VNFD Version</entry> | ||
821 | |||
822 | <entry>1.0</entry> | ||
823 | </row> | ||
824 | |||
825 | <row> | ||
826 | <entry>Flavour</entry> | ||
827 | |||
828 | <entry>Canonical</entry> | ||
829 | </row> | ||
830 | |||
831 | <row> | ||
832 | <entry>uCPE Device</entry> | ||
833 | |||
834 | <entry>trgt</entry> | ||
835 | </row> | ||
836 | |||
837 | <row> | ||
838 | <entry>Cloud Init File</entry> | ||
839 | |||
840 | <entry><literal>centos_128t_internet_ci.iso</literal>.</entry> | ||
841 | </row> | ||
842 | |||
843 | <row> | ||
844 | <entry>Domain Update Script</entry> | ||
845 | |||
846 | <entry></entry> | ||
847 | </row> | ||
848 | |||
849 | <row> | ||
850 | <entry>Interfaces</entry> | ||
851 | |||
852 | <entry></entry> | ||
853 | </row> | ||
854 | |||
855 | <row> | ||
856 | <entry>ID</entry> | ||
857 | |||
858 | <entry>IF Name</entry> | ||
859 | </row> | ||
860 | |||
861 | <row> | ||
862 | <entry>mgmt (dpdk)</entry> | ||
863 | |||
864 | <entry>Bridge: vnf_mgmt_br</entry> | ||
865 | </row> | ||
866 | |||
867 | <row> | ||
868 | <entry>wan (dpdk)</entry> | ||
869 | |||
870 | <entry>Bridge: ibm_br</entry> | ||
871 | </row> | ||
872 | |||
873 | <row> | ||
874 | <entry>lan (dpdk)</entry> | ||
875 | |||
876 | <entry>Bridge: sfc_br</entry> | ||
877 | </row> | ||
878 | |||
879 | <row> | ||
880 | <entry>Create</entry> | ||
881 | |||
882 | <entry></entry> | ||
883 | </row> | ||
884 | </tbody> | ||
885 | </tgroup> | ||
886 | </table> | ||
887 | |||
888 | <note> | ||
889 | <para>To procure the VNF image files and their licenses, please | ||
890 | contact each respective VNF provider.</para> | ||
891 | </note> | ||
892 | |||
893 | <para>Instantiate the Fortigate VNF by selecting the trgt device, then | ||
894 | <literal>VNF -> Instances -> Add</literal>.</para> | ||
895 | |||
896 | <para>Fill in the required fields with the following values:</para> | ||
897 | |||
898 | <table> | ||
899 | <title>Fortigate VNF Instantiation</title> | ||
900 | |||
901 | <tgroup cols="2"> | ||
902 | <colspec align="left" /> | ||
903 | |||
904 | <colspec colwidth="2*" /> | ||
905 | |||
906 | <colspec colwidth="5*" /> | ||
907 | |||
908 | <thead> | ||
909 | <row> | ||
910 | <entry align="center">Field</entry> | ||
911 | |||
912 | <entry align="center">Value</entry> | ||
913 | </row> | ||
914 | </thead> | ||
915 | |||
916 | <tbody> | ||
917 | <row> | ||
918 | <entry>Name</entry> | ||
919 | |||
920 | <entry>fg_trgt_1</entry> | ||
921 | </row> | ||
922 | |||
923 | <row> | ||
924 | <entry>VNF Type</entry> | ||
925 | |||
926 | <entry>Fortigate</entry> | ||
927 | </row> | ||
928 | |||
929 | <row> | ||
930 | <entry>VNFD Version</entry> | ||
931 | |||
932 | <entry>1.0</entry> | ||
933 | </row> | ||
934 | |||
935 | <row> | ||
936 | <entry>Flavour</entry> | ||
937 | |||
938 | <entry>Canonical</entry> | ||
939 | </row> | ||
940 | |||
941 | <row> | ||
942 | <entry>uCPE Device</entry> | ||
943 | |||
944 | <entry>trgt</entry> | ||
945 | </row> | ||
946 | |||
947 | <row> | ||
948 | <entry>Cloud Init File</entry> | ||
949 | |||
950 | <entry><literal>fg_cust_basic_fw.conf</literal></entry> | ||
951 | </row> | ||
952 | |||
953 | <row> | ||
954 | <entry>License File</entry> | ||
955 | |||
956 | <entry>The FortiGate license file provided by Fortinet.</entry> | ||
957 | </row> | ||
958 | |||
959 | <row> | ||
960 | <entry>Domain Update Script</entry> | ||
961 | |||
962 | <entry></entry> | ||
963 | </row> | ||
964 | |||
965 | <row> | ||
966 | <entry>Interfaces</entry> | ||
967 | |||
968 | <entry></entry> | ||
969 | </row> | ||
970 | |||
971 | <row> | ||
972 | <entry>ID</entry> | ||
973 | |||
974 | <entry>IF Name</entry> | ||
975 | </row> | ||
976 | |||
977 | <row> | ||
978 | <entry>mgmt (dpdk)</entry> | ||
979 | |||
980 | <entry>Bridge: vnf_mgmt_br</entry> | ||
981 | </row> | ||
982 | |||
983 | <row> | ||
984 | <entry>wan (dpdk)</entry> | ||
985 | |||
986 | <entry>Bridge: sfc_br</entry> | ||
987 | </row> | ||
988 | |||
989 | <row> | ||
990 | <entry>lan (dpdk)</entry> | ||
991 | |||
992 | <entry>Bridge: lan_br</entry> | ||
993 | </row> | ||
994 | |||
995 | <row> | ||
996 | <entry>Create</entry> | ||
997 | |||
998 | <entry></entry> | ||
999 | </row> | ||
1000 | </tbody> | ||
1001 | </tgroup> | ||
1002 | </table> | ||
1003 | </section> | ||
1004 | |||
1005 | <section> | ||
1006 | <title>Testing the Use-case</title> | ||
1007 | |||
1008 | <para>In order to access the web interfaces of the 128T VNF, open a | ||
1009 | browser on a machine connected on the same network with the WAN port of | ||
1010 | the target and connect to: | ||
1011 | <literal>https://<publicIP>:60001</literal> using the username: | ||
1012 | admin and the password: 128Tadmin.</para> | ||
1013 | |||
1014 | <para>In order to access the web interfaces of the Fortigate VNF, open a | ||
1015 | browser on a machine connected on the same network with the WAN port of | ||
1016 | the target and connect to: | ||
1017 | <literal>https://<publicIP>:60002</literal> using the username: | ||
1018 | admin, and leaving the password blank.</para> | ||
1019 | |||
1020 | <note> | ||
1021 | <para>Make sure the WAN interface of the trgt device has access to the | ||
1022 | internet. The Fortigate VNF requires internet access to validate the | ||
1023 | license.</para> | ||
1024 | </note> | ||
1025 | |||
1026 | <para>In order to validate the data path connect a test machine to the | ||
1027 | LAN physical port and check for a dynamic IP (the Fortigate LAN | ||
1028 | interface is configured with a DHCP server):<programlisting>> dhclient eth1 | ||
1029 | > ping 8.8.8.8</programlisting>For data path validation, a new cloud-init | ||
1030 | image may need to be generated for the 128T VNF to match your network | ||
1031 | configuration.</para> | ||
1032 | </section> | ||
1033 | |||
1034 | <section> | ||
1035 | <title>Use-case Clean-up</title> | ||
1036 | |||
1037 | <para>In order to remove the setup created in previously, all components | ||
1038 | need to be deleted in reverse order:</para> | ||
1039 | |||
1040 | <orderedlist> | ||
1041 | <listitem> | ||
1042 | <para>Select the trgt uCPE device -> VNF -> Instances. Select | ||
1043 | the 128T and Fortigate VNFs -> Delete.</para> | ||
1044 | </listitem> | ||
1045 | |||
1046 | <listitem> | ||
1047 | <para>Select the trgt uCPE device -> Configuration -> | ||
1048 | OpenVSwitch -> Bridges. Select all bridges -> Delete.</para> | ||
1049 | </listitem> | ||
1050 | |||
1051 | <listitem> | ||
1052 | <para>Select the trgt uCPE device -> Configuration -> External | ||
1053 | Interfaces -> Configuration. Select all interfaces -> | ||
1054 | Delete.</para> | ||
1055 | </listitem> | ||
1056 | |||
1057 | <listitem> | ||
1058 | <para>VNF -> Descriptors. Select all bundles -> | ||
1059 | Offboard.</para> | ||
1060 | </listitem> | ||
1061 | </orderedlist> | ||
1062 | </section> | ||
1063 | </section> | ||
1064 | </chapter> \ No newline at end of file | ||