ISN 3210

WIDE AREA NETWORK

PRACTICALS

Professor Emmanuel TONYE et Engineer Rholy NKUH

[email protected] et [email protected]
https://sapiotech.enspy.net
https://www.researchgate.net/profile/Emmanuel_Tonye
2024

WIDE_AREA_NETWORK_Pr TONYE 1
Scheme Of Work
1. WAN – WIDE AREA NETWORK
• PRIVATE WAN: RNIS, FRAME RELAY, ATM, METRO ETHERNET,
VSAT, IP, MPLS, 3GPP
• PUBLIC WAN: xDSL, Cable, WIMAX, WIFI, 3GPP, VSAT, VPN
2. ROUTING,
3. QUALITY OF SERVICE,
4. CONTENT CENTRED NETWORK
5. PRACTICALS : REALISING AND
SIMULATING NETWORKS WITH GNS3
6. EXERCICES

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 2
 Educational materials

2013 2015

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 3
 Network design and simulation with GNS3
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 4
 Report
Network design and simulation with GNS3 (1 à 7) (Submit report August
31, 2024 to [email protected] and [email protected]) by a
link in a cloud

Detailed report to be submitted in two formats:

1) PPT as in the manual of the practical
2) Series of videos, one for each practical

Examples of videos of practicals 1 to 7 and more

https://mega.nz/fm/ZKFDCJYA

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 5
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 6
LAPTOP SPECIFICATIONS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 7
INSTALLATION AND SETUP

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 8
RESOURCES USED.
• GNS 3(GRAPHICAL NETWORK SIMULATOR 3).
• Oracle VirtualBox
• Vmware Workstation Pro

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 9
 INSTALLING GNS3
▪ Go to the GNS3 website:
▪ https://gns3.com/software/dow
nload
▪ Click Download on the OS of
your device.
▪ Select Download for Windows
because if you are running a
Windows OS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 10
INSTALLING GNS3 VM in VMware Workstation

▪ GNS3 VM and GNS3 the

application must be of the
same version.
▪ In my case I’m using GNS3
version 2.2.38 so my VM is
thesame 2.2.38.
▪ Click on Open a Virtual
machine on the VMware
Workstation and trace and
follow the steps in opening
the downloaded GNS3VM
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 11
INSTALLING ORACLE VIRTUALB

▪ Download Oracle
Virtualbox from the
website
▪ https://www.virtualbox.or
g/wiki/Downloads
▪ Click on Windows Hosts
under platform packages
and download.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 12
INSTALL an OPERATING SYSTEM IN
VIRTUALBOX
▪ Go to:
https://getintopc.com/ to
download the OS.
▪ Click on Operating
Systems on the header and
search for the OS of your
choice you wish to
download.
▪ I downloaded Windows 10
to run on my VirtualBox.
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 13
CREATING A VIRTUAL MACHINE IN ORACLE
VIRTUALBOX.

▪ Open Oracle VirtualBox.

▪ Click on NEW located at
the top right of the tool
bar to create a new
Virtual machine.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 14
INSTALLING THE DOWNLOADED OS ON THE
VIRTUALBOX
▪ Give a name to your new
Virtual machine, in my case I
named it « ICTUpracticals »
▪ Choose a folder where you
want the VM to be stored.
▪ Select the iso image
downloaded from
www.getintopc.com to
install the OS.
▪ Click on NEXT to follow the
installation wizard.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 15
NEW VIRTUAL MACHINE CREATED

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 16
HOW TO CREATE A LOOPBACK INTERFACE
CARD
• To enable a network topology under GNS3 to connect with a real
network, a loopback interface needs to be created to be used with a
real host interface.
• To create one, click start Orb (Win+r) and type « hddwwiz.exe » and
click « OK »
• Follow the necessary steps the wizard gives you as seen below;
• Click “NEXT” to continue;

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 17
Click on the second option “ Install the hardware that I manually select from a list(Advanced) and click
“NEXT”

• Search and click on “Network Adapters” in the list and click “NEXT”;
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 18
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 19
▪ Select the “Manufacturer” which is “MICROSOFT” and the “Model” which is “Microsoft KM-TEST Loopback Adapter” and
click “NEXT”;

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 20
▪ Loopback Interface card has been created and can be seen in “Control panel>Network and Internet>Network
Connections”.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 21
HOW TO DOWNLOAD IOS IMAGE FILES

▪ Go to the website:
▪ https://networkrare.
com/free-download-
cisco-ios-images-for-
gns3-and-eve-ng/

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 22
 HOW TO ADD AN IOS IMAGE IN GNS3.

▪ The illustration will show how i add an

ios image router C3600 in GNS3.
▪ On the Tool bar, on GNS3?, click on
« EDIT » then select « PREFERENCES »
then click on “IOS ROUTERS” on your
left
▪ Click on “NEW” to add image
▪ A pop up will show asking you to
choose a server you will like to run the
IOS router on
▪ In my case, and for this practicals i
chose to run the iOS router on my
GNS3 VM.
▪ Click on « NEXT »
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 23
 IOS IMAGE C3660
1. Click on « NEW IMAGE » and browse to
select where the downloaded ios image
is on your pc and click open.
2. A pop up will appear asking « If you would like to
decompress the IOS image » and I’d click « YES »
• Then id be able to see the iOS image location.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 24
 NEW IOS ROUTER IMAGE
1. Click on « NEXT » to the « Name and Platform » page and 2. Then click on NEXT to the Memory
leave everything to default. page and leave it as default as well.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 25
 IOS IMAGE 3660
• Click on the tab « IDLE-PC Finder to find a suitable value for
• On the « Network Adapters » page, choose the your iOS image so that it prevents the iOS to use up 100% of
default network adapters that should be your processor.
inserted on the slots of the router. • Click « OK » and « FINISH ».
• Click « NEXT ».

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 26
IOS ROUTER C7200

▪ Click « APPLY » to import

the c7200 router to GNS3
▪ Click « OK » to return to
GNS homepage.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 27
HOW TO ADD A VIRTUALBOX VM In GNS3

▪ On the GNS3 Tool bar click on

« EDIT », select
« PREFERENCES » then select
« VirtualBox VMs » on your
left.
▪ Click on « NEW » and choose
the server you want the
Virtual machine to run on, in
my case i chose « My local
Computer »
▪ Click « NEXT ».
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 28
HOW TO ADD A VIRTUALBOX VM In GNS3.

▪ Choose the VirtualBox

Virtual machine by clicking
the drop down arrow and
choosing the Virtual
machine we created. In my
case it was
« ICTUpracticals »
▪ Click on FINISH

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 29
VIRTUALBOX VM TEMPLATE

▪ Click « APPLY » to import

the Virtual machine
(ICTUpracticals) to GNS3
▪ Click « OK » to return to
GNS homepage.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 30
IOS Images
• 3725 Switch router

• 7200 Router

• 3660 Router. The "3600" represents the model of the

equipment (the chassis or the series of the router) so
we can't have an image in this case, on the other
hand, we can have system images (ISO) for the
routers deriving from this model like the 3660, or the
3640 or 3620... so the IOS under the form "36xx".

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 31
 Network design and simulation with GNS3
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 32
TP1: create a network consisting of an R1 router (Cisco 3660) and a
VirtualBox virtual machine. This network will be connected to the
Internet.

a) Creating a project in GNS3

b) Create a Cloud in GNS3
c) Add a router in GNS3
d) Add a VirtualBox VM in
GNS3
e) Add a static route on the
host
f) Save router configuration
and topology in GNS3
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 33
TP 2: create a network consisting of a router R1 (Cisco 3660),
a switch SW1 and two VPCS computers. This network will be
connected to the Internet.
a) Repeat TP1 to create the new
RES2 project. Create and
configure the Cloud and
router R1. Add the ethernet
switch SW1. Check from the
router console the link to the
Internet.
b) Add two VPCS hosts (nodes).
c) Configure VPCS hosts.
d) Save the configuration of
VPCS hosts.
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 34
Objectives of TP2
1) Set up the Cloud to create a link between the topology defined in
GNS3 and the Internet;
2) Set up the Cisco 3660 router to use the Internet;
3) Integrate an Ethernet switch SW1 and connect it to router R1;
4) Set up two computers VPCS1 and VPCS2 to perform functional
tests.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 35
TP 3: Create a network consisting of two 3600 routers equipped with
one NM-16ESW module each. The routers are then configured with two
VLan 10 and VLan 20. VPCS computers complete the topology for
functional testing.

a) Add a module in a 3600

router;
b) Configure the VPCS
computers;
c) Configure the VLANs and
the Trunk;
d) Test the operation of the
VLANs;
e) Capture an ICMP frame
with WireShark;
f) Activate the Spanning-Tree.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 36
Objectifs of TP 3
1) Set up two VLans;
2) Connect two VPCS computers per VLan on each router;
3) Perform Ping to verify the operation of the topology;
4) Capture, using WireShark, an ICMP frame;
5) Enable Spanning-Tree on each VLan.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 37
TP 4: create a network of two routers. The NM-16ESW and NM-4T
modules are installed on both routers. They are connected via the serial
interfaces s2/0. VPCS computers complete the topology for functional
testing.

a) Add modules in a 3600

router;
b) Connect and configure
VPCS computers;
c) Configure the serial
interfaces of the routers;
d) Configure an IP address on
the administration VLAN;
e) Configure a static route and
a default route;
f) Test the network operation
with Tracert.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 38
Objectives of TP 4
1) Configure the serial interfaces to simulate a WAN link between two
remote networks;
2) Connect two VPCS computers by Switch-router;
3) Configure the IP addresses of the Ethernet and serial interfaces of
the routers;
4) Configure static routes on the routers;
5) Configure the IP addresses of the VPCS computers;
6) Test the operation of the topology with Tracert.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 39
TP 5: create a network consisting of two routers. The NM-16ESW and
NM-4T modules are installed on both routers. They are connected by
the serial interfaces s2/0. VPCS computers complete the topology for
functional testing. RIP Version 2 will be activated.

a) Add modules in a 3600 router;

b) Connect and configure VPCS
computers;
c) Configure the serial interfaces
of the routers;
d) Configure an IP address on the
administration VLAN;
e) Configure RIP Version 2 on
routers;
f) Test the network operation
with Tracert.
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 40
Objectives of TP 5
1) Configure the serial interfaces to simulate a WAN link between two
remote networks;
2) Connect two VPCS computers by Switch-router;
3) Configure the IP addresses of the Ethernet and serial interfaces of
the routers;
4) Configure the RIP version 2 protocol on the routers;
5) Configure the IP addresses of the VPCS computers;
6) Test the operation of the topology with Tracert.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 41
TP 6 – VPCS, OSPF
a) Create a network consisting of two routers and four switch-routers.
b) The NM-16ESW module is installed on SWR1, SWR4, SWR5 and
SWR6.
c) The NM-4T module is installed on SWR1, R2 and R3.
d) The links between SWR1, R2 and R3 are done through the serial
interfaces.
e) VPCS computers complete the topology for functional testing.
f) OSPF will be activated and configured.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 42
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 43
Objectives of TP 6
1) Configure the serial interfaces to simulate a WAN link between two
remote networks;
2) Connect two VPCS computers on SWR1, SWR4 and SWR5;
3) Configure the IP addresses of the Ethernet and serial interfaces of the
routers;
4) Configure device identifiers;
5) Configure OSPF;
6) Modify the bandwidth of the serial interfaces;
7) Configure the VPCS computers;
8) Perform functional tests.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 44
TP 7: create a network consisting of a router and two switches. The
NM-16ESW module is installed on SW1 and SW2. VPCS computers
complete the topology for functional testing.

a) Create the network topology;

b) Connect and configure the
VPCS computers;
c) Configure switches SW1 and
SW2;
d) Configure router R1;
e) Display the configuration of
the Vlans using the useful
commands;
f) Test the operation of the
network topology.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 45
Objectives of TP 7
1) Create the network topology: router, switch, VPCs and Cloud;
2) Configure switches;
3) Configure the router;
4) Test the operation of the configuration.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 46
Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 47
TP 8: create a network consisting of a router and two switches (Type Cisco 3725).
The NM-16ESW module is installed on SWR1 and SWR2. SWR1 and SWR2 are
installed with a 128 MiB PCMCIA virtual disk for backup. VPCx computers
complete the topology for functional testing.

a) Create the network topology;

b) Connect and configure the
VPCx computers;
c) Configure SWR1 and SWR2
switches;
d) Configure the load balancing;
e) Configure the Router;
f) Use useful commands;
g) Test the operation of the
network topology.
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 48
Objectives of TP 8
1) Create the network topology: router, switch, VPCs and Cloud;
2) Configure the switches (VLAN, EtherChannel);
3) Configure the router;
4) Test the operation of the configuration.

EtherChannel is a link aggregation technology used on Cisco switches.

It allows the combination of several physical links into one logical link.
With this type of configuration, it is possible to increase speed and fault
tolerance.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 49
Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 50
TP 9
• Create a network consisting of a router and three switches (Type Cisco
3725).
• The NM-16ESW module is installed on SWR1, SWR2 and SWR3.
• Install a 128 MiB PCMCIA disk on each device to save
configurations.
• VPCx computers and VirtualBox virtual machines complete the
topology for functional testing.
• Java 6 update 3, Flash Player, Security Device Manager and Cisco
VPN Client are installed on WXP_2.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 51
TP 9 - InterVLans, SDM, Cisco VPN Client
a) Create the network topology;
b) Connect and configure the
VPCx computers;
c) Configure switches SWR1,
SWR2 and SWR3;
d) Configure router R1;
e) Configure the VirtualBox
virtual machines;
f) Configure a VPN connection
with SDM (Security Device
Manager);
g) Connect to the VPN with
Cisco VPN Client.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 52
Objectives of TP 9
1) Create the network topology: router, switch, VPCs, VirtualBox, Cloud ;
2) Configure switches (VLAN, EtherChannel);
3) Configure the router for VPN access via SDM;
4) Configure the VBox virtual machines (WXP_1 and WXP_2) ;
5) Configure the VPCx machines;
6) Test the operation of the configuration.

₋ EtherChannel is a link aggregation technology used on Cisco switches. It allows the

combination of several physical links into one logical link. This type of configuration can
increase speed and fault tolerance.
₋ The Loopback interface is an interface on router R1 for VPN connections.
₋ SDM (Security Device Manager) is a Cisco software to simplify the configuration of
routers via a Web interface.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 53
Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 54
TP 10: Build and simulate a network with 5 autonomous systems (1)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 55
TP 10: Build and simulate a network with 5 autonomous systems (2)

This PC is not part of the

architecture; it will be
connected in turn to the
console port of the routers for
the basic configurations

These switches render this architecture dynamic via Vlans

These 2 switches allow the creation of a LAN with all the routers for their management
(configuration via Telnet). In the case of the label, it is the network 10.0.0.0/16
The architecture is subdivided into 5 autonomous systems
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 56
TP 1O: Build and simulate a network with 5 autonomous systems(3)

Work to do
Introduce the basic configurations in all the routers of the architecture.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 57
Objective
The goal of this practical work is to allow the communication
between 5 autonomous systems. By autonomous system, we mean
an IP network whose internal routing policy is consistent. It is
generally a network of an entity or organization.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 58
SETTING UP OF THE EQUIPMENT
We click on the component at the
level of Node Type then we place
it on the workspace

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 59
ADDITION OF MULTI SWITCH LAYER

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 60
 Change of the multi switch layer symbol

Right click on the switch, choose

change symbol and select the
ethernet_switch symbol

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 61
 Performing the connections

Choose the type of connection in

the toolbar and choose the
connection interface on the
equipment, this is the
FastEthernet interface

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 62
 Framing
On réalise les cadres pour identifier
nos 5 systèmes autonomes

Click on rectangle in the

toolbar
We draw the rectangle then
right click on the frame to
change the style

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 63
Serial link

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 64
Making the links

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 65
Adding slots

Le nombre
d’interface étant
limité, pour
certaine
équipement du
réseau il est
indispensable
d’ajouter de slot
pour augmenter
le nombre
d’interfaces DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 66
Making the links

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 67
Configuration PC
We will connect in turn this pc on the different
equipments to be configured manually

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 68
 Material and equipment available in a laboratory of the National Advanced School of
Engineering of Yaoundé (ENSPY – Ecole Nationale Supérieure Polytechnique de Yaoundé)

CISCO bays
with
Routers and Switches
CISCO ASA 5510 SERIES
CISCO 2811
CISCO 2621
CISCO 3825
CISCO CATALYST 2950 series
CISCO CATALYST 3560 Series
PoE-48
CISCO CATALYST 2960 Series
CISCO CATALYST 2960 Series
PoE-24

CISCO ToIP 7962

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 69
INTERNAL CONFIGURATION

Dynamic routing protocol configuration

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 70
ROUTING

Creating routes

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 71
Configuring interface fa0/0

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 72
 CREATING VLAN 20
Configuring
interface fa0/10 in
access mode at
VLAN 20

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 73
Configuring interface fa1/0

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 74
Configuring VLAN 10 and 20

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 75
 Configuring VLAN 10
We configure interface f0/2 and f0/4 of the switch in
access mode at VLAN 10

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 76
FUNCTIONAL TEST
From router 1 we send the packets to router 2 belonging to the
autonomous system 2.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 77
FUNCTIONAL TEST

We send packets from

different routers to others
belonging to different systems

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 78
 CONCLUSION
For the configuration of the 5 autonomous systems, it is first necessary to
configure each autonomous system turn by turn (internal routing of the system)
and then the creation of the VLANs for the interconnection of the
autonomous systems,

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 79
Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 80
TP11: Set up and configure a ToIP network(1)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 81
TP11: Set up and configure a ToIP network(2)

Work to be done
• Configure a ToIP architecture
• Check the network operation.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 82
Task 2: Build and configure a ToIP network (3)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 83
 4321

4322

10.10.0.0/24
255.255.0.0
4323

4324

4325

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 84
 Interface viewing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 85
 ToIP: TELEPHONIE OVER IP

IP telephony is the ability to make and receive telephone calls via

the IP network.
It is also called ToIP for "Telephony over IP", or VoIP for Voice
over IP.
All IP telephony solutions start by converting voice into digital
data packets.
The voice packets are then transmitted over the Internet in the
same way as other types of traffic (web, email, FTP...).

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 86
 OBJECTIVE

The objective of this practical is to connect 5 phones so that they can make
calls to each other.
Configure the router that allows defining a route for a connection thanks to
the routing table and the switch that distributes the data to each recipient
while eliminating the possible collisions of packets by the segmentation of
the network.
Define a DHCP server that will be used to distribute an IP address to each
terminal on the network.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 87
Network Architecture

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 88
Construction of the network
Setting up the equipment

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 89
Construction of the network
Creating interconnections
We choose the switch interface for the IP
phones and FastEthernet between the
router and the switch

In the toolbar
• select the IP phone
• drag it to the worksurface
• select the wire type
• connect to a FastEthernet port of the
switch and to the switch port of the
IP phone

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 90
 IP Phone Overview
Connect the power cable of the IP Under the option Modules,
phone • Select and hold IP_PHONE_ADAPTER ".
click on the iphone to observe its initial • Attach the cable carried to the connection port
physical constitution Start the IP Phones, click on it to connect the AC adapter
to power it

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 91
 Router overview
left click on the router
To see its physical
constitution
▪ select "CLI" to access the
configuration space.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 92
ROUTER CONFIGURATION

select "CLI" to access

the configuration
space.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 93
CONFIGURATION OF INTERFACE fa0/0

"en" - to enter privileged mode

"conf t" - enter global configuration mode

"no shutdown" - enables or disables the interface

"wr" - save router configuration

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 94
DHCP SERVER CREATION

creation and configuration of the

DHCP server used to distribute an
IP address to each IP terminal on
the network.

"ip DHCP pool VOICE" - assign

an IP address dynamically to each
Ip phone.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 95
 Configuration of the "Call Manager Express" telephony service on the
router

We configure Call Manager Express to

enable VoIP support on our network.
The "telephony-service" command is
used to switch to the telephony service
configuration mode

– "max-dn 5 " defines the maximum

number of directory numbers
– "auto assign 4 to 6 " automatically
assigns the number extension to the
buttons

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 96
 Creating a Vlan Voice on the Switch
– Click on the switch
– Select CLI
– Type n <

– Type inter range fa0/1 - 5 to

configure all the interfaces of the
switch
– Type switchport voice vlan 1 to
define the VLAN for VOIP
packets

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 97
NUMBER CONFIGURATION

– "ephone-dn 1" allows you to enter the

configuration mode of IP phone 1
– "number 54001" allows you to assign
a number to this IP phone
– "ex" to exit

– We do the same thing for 2,3,4 and 5

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 98
Verification of the correct allocation of IPs and telephone
numbers

– click on an ephone
– select GUI
– make sure that the phone
is identifiable by its
number written here,
"54002

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 99
FUNCTIONAL TEST
• On the left we show the ip phone whose number is 54002 that receives a call from
the number 54003
• On the right we see that when we pick up the phone, they are connected.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 100

 CONCLUSION
We remember that the configuration of the voice over IP goes through the
creation of the DHCP server to dynamically address the ip-phones, then the
configuration of the telephony service Call Manager Express on the router,
then the configuration of the voice vlan on the switch and finally the
configuration of the telephones (number assignment).

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 101

 Material and equipment available in a laboratory of the National Advanced School of
Engineering of Yaoundé (ENSPY – Ecole Nationale Supérieure Polytechnique de Yaoundé)

CISCO bays
with
Routers and Switches
CISCO ASA 5510 SERIES
CISCO 2811
CISCO 2621
CISCO 3825
CISCO CATALYST 2950 series
CISCO CATALYST 3560 Series
PoE-48
CISCO CATALYST 2960 Series
CISCO CATALYST 2960 Series
PoE-24

CISCO ToIP 7962

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 102

Telephony over IP with a Raspberry Pi card

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 103

Objective
Use a Raspberry Pi nanocomputer to create an IP-PBX (Internet
Protocol-Private Branch eXchange) server, which is a private
telephone switch, allowing users of a private or public network to
exchange (at the using a smartphone, laptop or IP phone) multimedia
information, including audio and video calls, voicemail.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 104

ToIP (1)
Device Architecture
In this architecture we have:
1) SIP clients
Any station supporting the TCP/IP protocol stack can integrate the SIP client functions. The SIP protocol
(Session Initiation Protocol) [1] is a signaling protocol used by the clients and the IP-PBX server for the
management of VOIP communication sessions. The different SIP clients we used are:
▪ IP Phone: They already integrate SIP functions for VOIP;
▪ Computer Softphone: To allow a workstation to connect and initiate calls in the IP network, we install a
softphone in it. The one installed here is MicroSIP (https://www.microsip.org/ ).
▪ Smartphone softphone: The softphone installed here is Zoiper (https://www.zoiper.com/ )
2) The IP-IPBX server: Raspberry PI board
In a Raspberry Pi nano-computer connected to the network by Wi-Fi interface, we install the RasPBX
operating system (http://www.raspberry-asterisk.org/). Raspbx is a Linux distribution for Raspberry Pi
including Asterisk. It also integrates FreePBX which offers a WEB interface facilitating the configuration
of Asterisk.
The communication and management protocols used are:
▪ Asterisk server (SIP): port UDP/5060
▪ Asterisk server (RTP audio stream): UDP/10.000-20.000 ports
▪ SSH server: port TCP/22
▪ Web administration interface: port TCP/443|80
3) The wireless access point
This is the wireless router used to interconnect network equipment (SIP clients and VOIP server). The
communication medium is Wi-Fi.
4) Internet
For installations of certain dependencies and updates during the build phase of the device.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 105

ToIP (2)
Organigram

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 106

ToIP (3)
Sequence diagram of the authentication of a subscriber to the telephone network

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 107

ToIP (4)
Sequence diagram of the establishment of a call session between two subscribers

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 108

The subscriber base
The number of subscribers conditions the choice of physical interconnection equipment but also the
characteristics of the voice over IP server. The key feature here is bandwidth for voice traffic. The
bandwidth must be large enough to support multiple calls at the same time on the same medium. The
minimum bandwidth calculation is simple:
Minimum server bandwidth = (Number of subscribers/2) x Bandwidth required per subscriber.
To these we can add the hardware characteristics: CPU, RAM, Storage, …
Let's take an example starting from 20 subscribers of the ICTU department.
Bandwidth = 10x64kbps = 640kbps. Expect more than 1 Mbps

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 109

Références
[1] : https://fr.wikipedia.org/wiki/Session_Initiation_Protocol

Ressources
Installation du système RasPBX :
- http://www.raspberry-asterisk.org/downloads/ : Lien de téléchargement sur serveur IPBX RasPBX
- https://downloads.raspberrypi.org/imager/imager_latest.exe : Raspberry Pi Imager
Installation du système de téléphonie sur IP :
- https://pimylifeup.com/raspberry-pi-asterisk/
- http://www.raspberry-asterisk.org/
Configuration du client MicroSIP :
- https://www.microsip.org/help

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 110

Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 111

 TP 12: IP/MPLS core
network configurations

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 112

TP 12: IP/MPLS core network configurations

• Architecture of the considered network

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 113

Configuration steps
1) Assign IP addresses to the CE, P and PE interfaces
2) Configuration of routing processes at the CEs and within the ISP (internal ISP
routing)
3) Activation of MPLS to establish LSPs inside the ISP
4) Creation of VRFs at each PE (pay attention to IP addresses)
5) Associate a routing process to each VRF on each PE
6) Activation of BGP in its Multi-Protocol version (MP-BGP) for VPN interconnection
7) Redistribution of IGP by VRF in MP-BGP
8) Redistribution of BGP in IGP

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 114

VRF (VPN Routing and Forwarding) : Why?
› FACT: Modern networks integrate a multitude of
services and/or stakeholders
› CONSEQUENCES: ›
• Increasing need for security
• Need to segment networks
• Growing interest in virtualized solutions (lower costs)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 115

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 116
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 117
VRF : How ?
› VRF : Virtual Routing and Forwarding ›
Virtual routing and forwarding instance
Each VRF is independent of the others
Isolates users in "their" VRF

Allows the implementation of VPNs

Allows secure access to resources
Allows the use of overlapping IP networks (overlapping,
redundancy, ...).
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 118
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 119
VRF : General principles
An interface can belong to one and only one VRF
Packets are only routed according to the routes of the
VRF in which they travel.
Pooling resources from different VRFs requires the use
of additional techniques (BGP, GRE, ...)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 120

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 121
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 122
Step 1: Assign IP addresses to the CE, P
and PE interfaces
• Core : no shutdown ip address 172.16.10.1 255.255.255.0
interface fastethernet 0/1 interface fastethernet 0/0
• ip address 172.16.100.254 255.255.255.0
Conf t no shutdown
Hostn Core • ip address 172.16.100.1 255.255.255.0
interface loopback 100 • PE2 no shutdown
ip address 10.0.2.1 255.255.255.255 interface fastethernet 0/1
no shutdown Conf t ip address 192.168.1.1 255.255.255.0
interface F0/0 Hostn PE2 no shutdown
ip address 10.0.10.2 255.255.255.0 interface loopback 0
no shutdown ip address 10.0.3.1 255.255.255.255 CE2
interface f0/1 interface F0/0
ip address 10.0.20.2 255.255.255.0 ip address 10.0.20.1 255.255.255.0 Conf t
no shutdown no shutdown Hostn CE2
interface F0/1 interface loop0
PE1: ip address 172.16.200.254 255.255.255.0 ip address 172.16.20.1 255.255.255.0
no shutdown interface f0/0
Conf t ip address 172.16.200.1 255.255.255.0
Hostn PE1 CE1 no shutdown
interface loopback 0 interface fastethernet 0/1
ip address 10.0.1.1 255.255.255.255 Conf t ip address 192.168.2.1 255.255.255.0
interface F0/0 Hostn CE1 no shutdown
ip address 10.0.10.1 255.255.255.0 interface loop0

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 123

Step 2 : Configuring routing processes at CEs and
within the ISP (internal ISP routing)
Core CE1
router ospf 1 router ospf 1
network 10.0.0.0 0.255.255.255 area 0 network 172.16.0.0 0.0.255.255 area 0
PE1 network 192.168.1.0 0.0.0.255 area 0
router ospf 1 CE2
network 10.0.0.0 0.255.255.255 area 0 router ospf 1
PE2 network 172.16.0.0 0.0.255.255 area 0
router ospf 1 network 192.168.2.0 0.0.0.255 area 0
network 10.0.0.0 0.255.255.255 area 0
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 124
Step 3 : Activation of MPLS to establish
LSPs inside the ISP
Core PE1
mpls ldp advertise-labels mpls ldp advertise-labels
mpls ldp router-id loopback100 force mpls ldp router-id loopback0 force
interface F0/0 interface f0/0
mpls ip mpls ip
interface F0/1
mpls ip PE2
mpls ldp advertise-labels
mpls ldp router-id loopback0 force
interface f0/0
mpls ip

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 125

Step 4: Creation of VRFs at each PE (pay
attention to IP addresses)
• Creation of VRFs on each PE

PE1 :
ip vrf vrf_client
rd 65000:123
route-target both 65000:123

PE2 :
ip vrf vrf_client
rd 65000:123
route-target both 65000:123

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 126

Step 4: Creation of VRFs at each PE (pay
attention to IP addresses)
• Definition of the interfaces in the VRF
PE1 :
interface fastethernet 0/1
ip vrf forwarding vrf_client
ip address 172.16.100.254 255.255.255.0
no shut

PE2 :
interface fastethernet 0/1
ip vrf forwarding vrf_client
ip address 172.16.200.254 255.255.255.0
no shutdown

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 127

Step 5: Associate a routing process with
each VRF on each PE
Attention, each process of the same routing protocol must have a different
number
PE1 :
router ospf 2 vrf vrf_client
network 172.16.0.0 0.0.255.255 area 0

PE2 :
router ospf 2 vrf vrf_client
network 172.16.0.0 0.0.255.255 area 0

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 128

Step 6: Activation of BGP in its Multi-Protocol
version (MP-BGP) for VPN interconnection
BGP activation with neighbor
specification PE2
PE1
router bgp 1
router bgp 1 neighbor 10.0.1.1 remote-as 1
neighbor 10.0.3.1 remote-as 1 neighbor 10.0.1.1 update-source loopback0
neighbor 10.0.3.1 update-source loopback0 address-family vpnv4
address-family vpnv4 neighbor 10.0.1.1 activate
neighbor 10.0.3.1 activate neighbor 10.0.1.1 send-community both
neighbor 10.0.3.1 send-community both exit
exit

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 129

Step 7: Redistribution of IGPs by VRF in
MP-BGP
PE1
router bgp 1
address-family ipv4 vrf vrf_client
redistribute ospf 2
no synchronization
exit-address-family

PE2
router bgp 1
address-family ipv4 vrf vrf_client
redistribute ospf 2
no synchronization
exit-address-family

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 130

Step 8: BGP redistribution in IGP
PE1
router ospf 2 vrf vrf_client
redistribute bgp 1 metric 1 subnets

PE2
router ospf 2 vrf vrf_client
redistribute bgp 1 metric 1 subnets

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 131

Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 132

TP13: Virtualization of the functions of an
IP/MPLS core network using SDN
technology

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 133

Interest of network virtualization: SDN and NFV technology

1) Creates network abstractions to be

managed by applications
2) Increases network flexibility
3) Less investment in hardware

1) Create a competitive
offer of innovative Software
applications Open
Defined
Innovation
Networking

Network
Functions 1) Reduces space requirements
Virtualisation 2) Reduced expenses (CAPEX,
OPEX, consumption)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 134

 5 Differences between SDN and NFV
Principle SDN separates traffic control and data flow and centralizes network control and scheduling.
NFV transfers network functions by virtualizing them on standard servers.

Situation SDN operates in an enterprise network, data center and/or cloud environment.
NFV targets the service provider network.

Application SDN allows network and cloud orchestration.

NFV allows to virtualize network functions such as routers, firewalls, gateways, load balancers, WAN...

Protocols SDN - OpenFlow

NFV - based on existing standards
Organisation SDN : Open Networking Foundation (ONF)
NFV : Groupe de travail NFV de l'ETSI
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 135
Core network architecture with SDN controller under
GNS3

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 136

Configurations in OPEN VSWITCH

• In order for the topology to be observed as it is seen in GNS3 it is

important that the virtual switch configurations are done correctly. That
is, all ports used must have been created with the ovs-vsctl commands in
the terminal.
• https://ictexpertsluxembourg.lu/ict-cloud/sdn-vs-nfv-differences/

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 137

 PRESENTATION OF SOME OPEN SOURCE SOLUTIONS

1 2 3

• It is the most advanced communication • OPEN VSWITCH is a software that • It is among the most widely used SDN
protocol between a centralized control behaves like a virtual switch with all its controllers. Supported by a large
plan and the data plan. It is standardized advanced features present. community. It allows users to
by the ONF programmatically manage OPENFLOW-
enabled Ethernet switches.

4 5 6
• OPENSTACK enables the deployment of • It is a hypervisor (server virtualization • ONOS is a network operating system
cloud computing infrastructures. It is the tool) of type 1 or "bare-metal", i.e. it is and distributed SDN controller. It was
solution that requires the most technical installed directly on the hardware. born in the Open Networking Lab
skills.

INTEREST IN OPEN SOURCE TECHNOLOGIES

138

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 138

• Among the most widely used OPEN SOURCE
solutions for implementing SDN and NFV approaches
we have:
• the openflow protocol for communications between the
control plane and the data plane,
• open vswitch switches,
• opendaylight and ONOS controllers; ......
• We have proxmox as hypervisor
• and openstack to deploy cloud computing infrastructures

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 139

 CHOICE OF SOLUTION

OFM
• GNS3 • ORACLE • OPENDAYLIGHT • OPEN VSWITCH • OPENFLOW
VIRTUALBOX MANAGER
VM

Soutenance de PFE 140

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 140

To perform the practical, you can :
• emulate your network in GNS3
• run virtual machines with virtualbox
• use OPENDAYLIGHT as SDN controller
• use OPEN VSWITCH for plane forwarding
• use the Openflow manager module to manage the different flows.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 141

Core network architecture for tests

• Global view of our network under the OPENDAYLIGHT controller

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 142

For simulation
• Implement a core network made up of 4 P routers and 2 PE routers
managed by an SDN controller.
• virtualize the routing function, replacing the routers with virtual
switches, each of which must be installed in separate and remote
servers.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 143

Core network architecture seen from the OPENDAYLIGHT
controller

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 144

Core network architecture seen from the Openflow
Manager

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 145

Work plan
• INSTALLATION OF THE ENVIRONMENT
• GNS3
• VirtualBox
• Creation of Virtual Machines
• Open Daylight and Open Flow Manager

• TOPOLOGY REALIZATION
• The IP MPLS core network
• Virtualization and SDN
• Case Study

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 146

Part 1: SETTING UP THE
ENVIRONMENT

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 147

SDN technology

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 148

Work plan
• INSTALLATION OF THE ENVIRONMENT
• GNS3
• VirtualBox
• Creation of Virtual Machines
• Open Daylight and Open Flow Manager
• OpenVswitch
• REALIZATION OF THE TOPOLOGY

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 149

Part 1: SETTING UP THE
ENVIRONMENT

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 150

GNS3
The foundation of our work?

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 151

 GNS3

• In this part we will see how to start a

project with GNS3. To do this a
number of prerequisites are more
than necessary depending on the
operating system at our disposal. In
our case, it is Windows 8.1.
• With the settings shown in the figure
below.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 152

 GNS3

• For the purpose of our work we will

use the GNS3-2.2.2019-03-16-all-
in-one version
• A lot of other software will be
installed on top of it including :
• Wireshark
• WinPcap
• Dynamips
• Etc...

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 153

 GNS3

• Once the installation is

complete we choose to start
the GNS3 server from our
host machine

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 154

 GNS3

• Once the connection with the

server is established, we can,
observe the connection
parameter
• As shown here

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 155

 GNS3

• Here is the
interface of
GNS3
• You can see the
status of the
CPU and RAM

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 156

VIRTUALBOX
The first step in virtualization

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 157

 VIRTUALBOX
• After installing Oracle
VirtualBox, we need to install a
virtual machine, in which we
will make our tests of
connectivity to the Internet.
• The system to install is
Ubuntu 18.04 LTS
• Just click on "New" in the
menu, then choose Ubuntu as
system in the new window.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 158

 VIRTUALBOX
• The first thing to do is to define
the name, the type of virtual
machine and the version
• the version you want to create.
In our case, we have chosen to
name
• our machines CONTROLLER,
Vswitch1, Vswitch2, Vswitch3,
Vswitch4, Vswitch5 and
• Vswitch6. The type for all the
machines will be Linux and the
Ubuntu 64 bits version
• as shown in the figure
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 159
 VIRTUALBOX
• On the screen of the figure, it
is necessary to define the
quantity of memory to be
allocated to the virtual
machine.
• The memory will be shared
with the main system each
time the virtual machine is
started. We will slide the bar
to 512 megabytes.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 160

 VIRTUALBOX
• The next step will be to create
a virtual hard disk. Like
shared memory, this is the
storage space that will be
allocated to the virtual
machine.
• Click on "Create".

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 161

 VIRTUALBOX
• In the next step, select the type of hard disk to create.
• Leave the "VDI" option checked by default which is the native file type of VirtualBox.
• You will then be asked to choose the way the hard disk is created.
• We have chosen a dynamically allocated hard disk and we have assigned 10GB to each machine.
• The virtual machine has now been created. To start it, click on it and press the "Start" button at
the top of the toolbar.
• The first boot requires selecting a boot disk.
• VirtualBox does not carry the system natively. It will be necessary to have an ISO file of the Linux
distribution to install. Click on Start and wait.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 162

 VIRTUALBOX
• VirtualBox does not carry
the system natively. You
will need an ISO file of the
Linux distribution to install.
• Click on Start and wait.
• We have the choice
between trying Ubuntu and
installing it. Click on
"Install".
• Then follow the instructions
until the end of the
installation.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 163

 VIRTUALBOX
• VirtualBox does not carry
the system natively. You
will need an ISO file of the
Linux distribution to install.
• Click on Start and wait.
• We have the choice
between trying Ubuntu and
installing it. Click on
"Install".
• Then follow the instructions
until the end of the
installation.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 164

 VIRTUALBOX
• VirtualBox does not carry
the system natively. You
will need an ISO file of the
Linux distribution to install.
• Click on Start and wait.
• We have the choice
between trying Ubuntu and
installing it. Click on
"Install".
• Then follow the instructions
until the end of the
installation.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 165

VIRTUALBOX

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 166

VIRTUALBOX

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 167

 GNS3
• For GNS3 to work with
VirtualBox you need
• Download GNS3 VM
• Add it to VirtualBox
• Add the VirtualBox path as
environment variable
• When we've done all this we
get the following result

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 168

 GNS3
• We can then add our virtual
machines

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 169

OPENDAYLIGHT
To lay the groundwork!

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 170

OPENDAYLIGHT

• The OpenDaylight project is a

collaborative open-source project
hosted by the Linux Foundation. The
goal of the project is to promote
software-defined networking (SDN) and
network function virtualization (NFV).
The software is written in the Java
programming language.
• https://en.wikipedia.org/wiki/OpenDay
light_Project

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 171

OPENDAYLIGHT

• OpenDaylight enables cloud engineers to • On-demand service delivery

programmatically deploy, configure and control Schematic acquisition of network transport or
virtual network services. As noted on the
OpenDaylight website, ODL helps ISPs, universities virtual private network connections
and cloud service providers enable the following • Virtualization of the network function
services:
Adding new network services to your
• On-demand service delivery
Schematic acquisition of network transport or virtual
existing cloud provider's network stack (e.g.
private network connections OpenStack)
• Virtualization of the network function
Adding new network services to your
existing cloud provider's network stack (e.g.
OpenStack)
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 172
OPENDAYLIGHT

• Without modifying the default • When the Ubuntu server is installed, we

network settings (NAT card) of have to install an additional
the virtual machines, we will prerequisite for OPENDAYLIGHT.
install OPENDAYLIGHT in the • This is java because OPENDAYLIGHT is a
CONTROLLER machine and then Java based application.
OPEN VSWITCH in the vswitch1,
vswitch2, vswitch3, vswitch4,
vswitch5, vswitch6 machines.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 173

OPENDAYLIGHT-installation

• Prepare the operating system

• Install the Java JRE
• Download OpenDaylight
• Install OpenDaylight

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 174

OPENDAYLIGHT-installation

• Prepare the operating system

• Run an apt-get update to ensure that
your server receives all the latest
security and application packages.
$ sudo apt-get update

• Now install the following convenience

packages to make your life easier.
$ sudo apt-get -y install unzip
vim wget

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 175

OPENDAYLIGHT-installation

• Install Java JRE

• Installing OpenDaylight via the
release zip archive requires the
JAVA 8 runtime environment.
This section explains how to
install JRE.
• Run the following command to
install JRE.
$ sudo apt-get -y install
openjdk-8-jre
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 176
OPENDAYLIGHT-installation

• Now make sure Ubuntu is

pointing to JAVA 8. Run the
following command. If it does not
point to JAVA 8, make sure you
select version 8 from the list.
$ sudo update-alternatives
--config java

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 177

 OPENDAYLIGHT-installation

• With the path in hand, run the following command to

update your BASHRC file.
$ echo 'export JAVA_HOME=/usr/lib/jvm/java-8-
openjdk-amd64/jre' >> ~/.bashrc
• Now source your BASHRC file, then verify that
$JAVA_HOME resides in the environment.
$ source ~/.bashrc
• Check that $JAVA_HOME ends with /jre.
• echo $JAVA_HOME

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 178

 OPENDAYLIGHT-installation
• Download the OpenDaylight Zip file
• You can download a full version (all features) of OpenDaylight using the following links.
• Release Version Year Month
• Flourine 0.9.1 2018 Nov
• Oxygen 0.8.4 2018 Dec
• Nitrogen 0.7.3 2018 May
• Carbon 0.6.4 2018 Apr
• Boron 0.5.4 2017 Jun
• Beryllium 0.4.4 2016 Nov
• Lithium 0.3.4 2016 Mar
• Helium 0.2.4 2015 Aug
• Simply right-click on the version name, select "Copy Link" and then run the following command. The following
example describes the command to run to download Oxygen.
• $ wget https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/karaf/0.8.4/karaf-0.8.4.zip
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 179
 OPENDAYLIGHT-installation

• Install OpenDaylight
• Install OpenDaylight in the operating system.
• Start by creating a directory for the binary.
$ sudo mkdir /usr/local/karaf

• Move the zip archive to the installation workspace

and unpack the archive. Make sure you are using
the correct version. I downloaded version 0.8.4
and yours may be different.
$ sudo mv karaf-0.8.4.zip
/usr/local/karaf
$ sudo unzip /usr/local/karaf/karaf-
0.8.4.zip -d /usr/local/karaf/
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 180
 OPENDAYLIGHT-installation

• Install karaf in user space.

$ sudo update-alternatives --install /usr/bin/karaf karaf
/usr/local/karaf/karaf-0.8.4/bin/karaf 1

$ sudo update-alternatives --config karaf

$ which karaf
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 181
 OPENDAYLIGHT-installation

• Let's do a test. OpenDaylight needs to

write a PID file to /usr/bin/karaf,
which requires sudo privaleges. Run
the karaf command via sudo and
pass the -E flag to keep the
$JAVA_HOME environment variable.

$ sudo -E karaf

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 182

 OPENDAYLIGHT-installation

From the Karaf command prompt, now install the DLUX

GUI.

opendaylight-user@root>feature:install odl-l2switch-
switch-ui
opendaylight-user@root>

This may take a few minutes to warm up.

Alternatively (assuming your firewall/security groups
allow it), you can access your URL and connect to the
DLUX console using the admin/admin credentials. Make
sure you put your IP address in the following URL (keep
port 8181).
http://@ip:8181/index.html#/login
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 183
OPENDAYLIGHT-installation

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 184

 OPENDAYLIGHT-installation

We now have an OPENDAYLIGHT server installed

with a basic set of features. In addition, it is
necessary to install additional features in order
to have a suitable server for testing and use.
Installing the features (For GUI, RESTCONF
protocol support for OPENDAYLIGHT USERS,
Layer 2 switch functionality to the controller) is
very simple on the OPENDAYLIGHT server) you
just need to run the "feature:install" command
with the features as arguments.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 185

OPEN FLOW MANAGER

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 186

 OPENFLOW MANAGER-installation
In this part we will install OpenFlow manager,
This is done within the Controller, the steps are as
follows:
• Open the controller
• We have a list of commands contained in a text file that NB: From here the screenshots come
will guide us along the work: it is the file
LIST_COMMANDS_OpenFlow from another PC because the previous
• First of all we have to install some dependencies for one did not have the capacity to run
the good functioning of OpenFlow, these dependencies OPENDAYLIGHT
are normally installed at the same time as
opendaylight,
• The commands to type are :
feature:install odl-restconf odl-mdsal-apidocs odl-
dlux-all
feature:install odl-openflowplugin-all odl-mdsal-all
odl-restconf-all odl-l2switch-switch odl-dlux-core
odl-l2switch-all DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 187
 OPENFLOW MANAGER-installation
Now that all ODL dependencies are installed, we will To check that the installation is
install the OPENFLOW components correct you can type the following
• CURL commands:
• To install it, type the following commands
node --version
npm --version
npm update -g npm
• NODEJS 12,x ( optionnel )
• We install it with its package manager (Node Packet
Manager)
• The commands are:
curl -sL https://deb.nodesource.com/setup_12.x
| sudo -E bash
apt-get install nodejs DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 188
 OPENFLOW MANAGER-installation
Now we will install other features that allow access to the openflow project, including:
• GIT
• To install it, type the following commands
apt-get install git -y
git clone https://github.com/CiscoDevNet/OpenDaylight-Openflow-App.git

Note that this command allows to duplicate this project developed on GIT!
This finishes the installation aspect!

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 189

 OPENFLOW MANAGER-CONFIGURATION
First we will observe the state of our network interfaces,
Ifconfig

We see a specific ip address, this is the one we will use to open OPENFLOW, then the command:
nano OpenDaylight-Openflow-App/ofm/src/common/config/env.module.js

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 190

 OPENFLOW MANAGER-CONFIGURATION

This represents the parameters that OPENFLOW

will use, so it is a question of modifying localhost
to put an ip address that we will use in OPENFLOW
(make sure that it is the one we had previously)
• Then validate the changes
• Now we will check the changes with the
command
cat OpenDaylight-Openflow-
App/ofm/src/common/config/env.module.js
• It is a question of checking that the ip address
has been taken into account
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 191
 OPENFLOW MANAGER-installation
• Once this is done, we need to enter the folder where we will install everything. Let's use
the following command:

cd OpenDaylight-Openflow-App/

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 192

 OPENFLOW MANAGER-LANCEMENT
• Check the installation of grunt with the
• We are now going to use npm that we have following command
installed previously, for that type grunt –version
successively the following commands:
npm install gruntfile --save-dev
npm install -g grunt
• Launch grunt using the command
Grunt

The connection to the server is now effective!

(note well the port number)
If these errors appear, restart the installation!
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 193
 OPENFLOW MANAGER-CONNEXION
• You just have to type in the URL bar of the browser the previous ip address and the
corresponding port number

• There is a small problem for the display of the technology

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 194
OPEN VSWITCH

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 195

 OPENvswitch-initialisation
• Here it is a question of creating virtual machines that will act as virtual switches with
switching functions,
• We follow the previous procedure to create virtual machines (make sure to put the
network interface on host only adapter)
• The next step is to assign the previous IP address to the controller, to do this we enter
the following commands
ifconfig ( to display interfaces)
ifconfig enp0s3 192.168.1.101 netmask 255.255.255.0 (to configure this interface)
ifconfig enp0s3 up (to activate the interface)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 196

 OPENvswitch-initialisation
• To save the commands you have to go to a directory where the configuration file is
located. To do this, type the following command
nano /etc/network/interfaces

• We then update the file

auto enp0s3
iface enp0s3 inet static
address 192.168.1.101
netmask 255.255.255.0
gateway 192.168.1.1

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 197

 OPENvswitch-inSTallation
• We install the functionality with:
apt-get install openvswitch-switch bridge-utils

• We check the new system parameters

systemctl status openvswitch-switch

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 198

 OPENvswitch-creating vswitch
• We transform our virtual machine into a switch (switching functions)
ovs-vsctl add-br vswitch*

• We add security functionalities

ovs-vsctl set-fail-mode vswitch* secure

• You can check the ip configuration with ifconfig

• We add the interfaces of the machine as ports of the switch

ovs-vsctl add-port vswitch* enp0s3

ovs-vsctl add-port vswitch* enp0s8

ovs-vsctl add-port vswitch* enp0s9

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 199
 OPENvswitch-creating vswitch
• We modify the ip configuration in the configuration file of the said interfaces with the following
command:
nano /etc/network/interfaces

auto vswitch*
iface vswitch* inet static
address 192.168.1.*
netmask 255.255.255.0
gateway 192.168.1.1

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 200

 OPENvswitch-CONTROLLER ASSIGNMENT
• Now we need to indicate to each switch the controller that will be in charge of managing everything
that is signalization, having its ip address we will use the following command to index it
ovs-vsctl set-controller vswitch* tcp:192.168.1.101:6633

• Once this is done, we create a flow in order to route the packets

ovs-ofctl add-flow vswitch* action=normal
• Finally you can check the configuration with ovs-vsctl show

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 201

CONCLUSION 1

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 202

CONCLUSION 1
• Once we open Opendaylight in the terminal, to perform any other task in our
virtual machine, we need to have preferably 8 GB of RAM.
• In the case of a capable PC, we must pay attention to the ip addresses of the
interfaces, this is the one we must use for it to work.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 203

Carrying out the simulation
And on GNS3? What does it look like?

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 204

 Carrying out the simulation
Our goal is to implement the following topology

• Due to lack of
memory capacity we
will do it with only
two switches

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 205

 Carrying out the simulation
We will first create our topology on GNS3

• This project is called

MPLS
• We will link GNS3 to
virtualBox
• To do this we go to
Edit >> Preferences

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 206

 Carrying out the simulation
We will first create our topology on GNS3

• In virtualBox click on New, to

add a virtual machine
• You can then add all the virtual
machines in the environment

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 207

 Carrying out the simulation
We will first create our topology on GNS3

• So we can have access to what

we have created
• It is then up to us to modify
them appropriately

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 208

 Carrying out the simulation
This topology can therefore be mounted!

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 209

CONCLUSION 2

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 210

CONCLUSION 2
• NFV (network functions virtualization) is a way to reduce costs and speed up
service deployment for network operators by decoupling functions such as
firewall or encryption from any dedicated hardware and moving them to
virtual servers.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 211

Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 212

 TP 14 - VIRTUALIZATION OF THE
TELECOMMUNICATIONS
NETWORK OF AN AUTONOMOUS
SEAPORT

Source - NGOTTY MBANG Gilles Hervé. Méthode de virtualisation des réseaux d’entreprises : modification du code source solution
appliquée au cas du réseau de télécommunications du pak Mémoire de fin d’étude en vue de l’obtention du diplôme de Master Recherche,
Option Génie des Télécommunications à l’ENSPY, UYI, Cameroun 2022-2023, sous la direction du Pr Emmanuel TONYE

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 213

 Les échanges avec le GUCE
SITES DU PORT vont se faire via des EDI Links of the MPLS core network of the Autonomous Port with the main port partners
AUTONOME Niveau de sécurité:
maximal
GUCE

SITE 3
SITE 2
HQ2
PAK's MPLS cloud

GESTIONNAIRES
TERMINAUX
- service d
échanges de
SITE 1
données
HQ1

DSID_PAK
CŒUR DU RESEAU
IP/ MPLS
SIP/ERP

SITE 4

UPSTREAM
FOURNISSEUR DE SERVICES :
-internet
-MPLS... SITE 5

Les échanges avec la DGD

Clients DOUANE vont se faire sur la

plateforme d échange
Niveau de sécurité:
BENEFICIAIRES DE SERVICES DU maximal
- SYSTÈME DE LA DOUANE
PORT AUTONOME :
-internet
-MPLS...
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 214
 Types of virtualization:
✓ From the network
✓ Servers and Data Center
✓ data and apps
✓ Computers…

TECHNOLOGIES OF VIRTUALIZATION
1- Structures
NFV : Network Functions Virtualization 2- Concepts
3- Operation
SDN : Software Defined Network 4- Advantages in the IP network

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 215

 CONCEPT : BENEFITS :
Breaking the coupling between ▪ Optimization of
the physical part of a piece of configurations in real time
NFV : Network Functions Virtualization equipment and all its intrinsic ▪ Improved operational
functionalities... efficiency
ARCHITECTURE DNFV TECHNOLOGY ▪ QoS improvement
▪ Speed up routing and
switching times
▪ Resource Sharing
▪ Cost reduction
FONCTIONNEMENT :
▪ Optimization of energy
- VNF
consumption…
- Element
Management
- VNF Manager
- NFV Infrastructure
- VIM
- NFV Orchestrator

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 216

 BENEFITS :
▪ Centralized control
CONCEPT : ▪ Simplification of data
Separation of control and exchanges
SDN : Software Defined Network data flow planes ▪ Improved operational
efficiency
▪ Capex reduction
ARCHITECTURE OF SDN TECHNOLOGY ▪ QoS improvement
▪ Catalyst for virtualization

FUNCTIONING :
▪ Application layer
▪ Control layer
▪ Network infrastructure
layer
▪ Customers layer

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 217

 Flowchart of the methodological steps
1) Faire état des lieux des équipements du cœur du réseau IP/MPLS
Description et caractéristiques traditionnel à virtualiser
1. Description of a traditional IP/MPLS d un cœur de réseau IP/MPLS
traditionnel d un Port Autonome
2) Relever toutes les caractéristiques techniques du cœur du
réseau
3) Evaluer les performances du réseau traditionnel et les
core network of an Autonomous Port problèmes de lenteur de transmission des données numériques

2. Adaptation of the virtualization Adaptation de la méthode de virtualisation pour

l amélioration de l ingénierie de trafic et des
4) Proposer les méthodes d amélioration
de l ingénierie de trafic

method to improve traffic engineering performances du cœur du réseau IP/MPLS 5) Décrire les protocoles à exploiter pour
atteindre l objectif d amélioration des
performances
and core performance of the Proposition de l architecture de 6) Proposition de la virtualisation des fonctions à travers la technologie SDN
et le protocole Openflow
IP/MPLS network virtualisation des fonctions d un cœur
de réseau IP/MPLS
7) Proposition de la sécurisation du cœur du réseau virtualisé
8) Mettre en place la fonctionnalité MD-SAL

3. Proposal of the virtualization 9) Proposition de l architecture logique et physique du cœur de réseau

10) Mise en place du contrôleur SDN

architecture of the functions of an NON

Validation de
IP/MPLS core network l architecture

4. Architecture validation test OUI 11) Installation de l émulateur du réseau (Mininet pour ce cas)

5. Implementation of the architecture Mise en place de

12) Installation de l hyperviseur Oracle VM Virtualbox
13) Création des machines virtuelles du contrôleur et des switches
virtuels
simulation environment l environnement de simulation
de l architecture
14) Installation de OpenDayLight (version 0.8.4) dans le contrôleur
15) Installation de OpenFlow Manager
16) Installation des switch virtuels à travers l émulateur
6. Simulation validation test 17) Configuration des Vswitch
17) Présentation de l architecture virtualisée sous mininet
NON
7. Modification of the solution code in Validation de la
simulation

the virtualized IP/MPLS network OUI

core Modification du code de la 18) Modification du code source de Virtualisation des fonctions
d un cœur de réseau IP/MPLS grâce à la technologie SDN Pour
solution dans le cœur de l amélioration des performances de la transmission des données
réseau IP/MPLS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 218

PAK's traditional IP/MPLS network core to be virtualized

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 219

 Target architecture of network virtualization through SDN technology

Service and COUCHE DES SERVICES

ET APPLICATIONS
application layers

Control layer COUCHE DE CONTROLE CONTROLLEURS SDN

COUCHE DE
Communication layer
COMMUNICATION PE3 Centre de donnée
(network infrastructure) (Infrastructures réseau) P1 et de stockage
PE4
SITE LOCAL
PE1 P2 PA USER
SITE LOCAL
PE2
COUCHE DES Client 1
Equipment Layer (Clients) EQUIPEMENTS (clients)
...
Client 2 Client n

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 220

Computer and simulation tools

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 221

Detailed report to be submitted in two formats:
(1)Pdf or ppt like the practical work manual
(2)Videos of your experimentation procedure

(Submit report May 15, 2024)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 222

Computer : AMD7 avec 16 Go RAM et 1 To de SSD

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 223

 Simulation tools

Communication protocol between a centralized

control plane and the data plane

OpenFlow network manager

Software that behaves like a virtual switch

with advanced features

SDN controller. Provides network policy

The general hypervisor

The network emulator

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 224

 Simulation Solution Implementation Steps

1) Installing the network emulator

2) Installing the hypervisor

3) Creation of virtual servers

4) Creation of the ODL controller

5) Installing OFM and OVS

6) Basic general configurations

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 225

Implementation of the virtualization solution
Installing the network emulator

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 226

 Implementation of the virtualization solution
Installing the hypervisor

Oracle VM VirtualBox version 6.1.34 r150636

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 227

Implementation of the virtualization solution
Implementation of the virtualization solution

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 228

Implementation of the virtualization solution
Installation of ODL OFM and OVS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 229

Implementation of the virtualization solution
Basic configurations for the simulation

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 230

Adaptation of virtualization to the PAK network
Separation of data and control planes

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 231

 Architecture of the virtualized core network of the PAK

NUAGE IP/MPLS DU PORT AUTONOME

Client n

Client n+1
Client 2
PA USER
Contrôleurs SDN
PE3
PA USER

Client 2 P1 HQ1 P2 HQ2

PE2
PE1

Client n PE4

LEGENDE
PA USER
Plan de PA USER
contrôle
Plan de
données ........
........ Autres routeurs Clients Client 1 Client n Client n+1

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 232

Architecture of the virtualized core network of the PAK

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 233

Editable script in python of
virtualized architecture on
mininet

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 234

Command to start the simulation of our architecture

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 235

Core network architecture seen from the OPENDAYLIGHT controller

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 236

Virtualized network core with an SDN controller in OpenFlow Manager

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 237

Plan
Resources TP 8 - InterVLans and EtherChannel
Report TP 9 - InterVLans, SDM, Cisco VPN Client
GNS3 – Opensource software TP 10 – Five autonomous systems
Packet Tracer and GNS3 TP 11 – ToIP Networks
IOS Images TP 12 - Configurations of an IP/MPLS core
Installing GNS3 Windows network
Configuring GNS3 TP 13 – Virtualising the functions of an
IP/MPLS core network using SDN
TP 1 - Cloud, VirtualBox technology
TP 2 - Cloud, Switchs, VPCS TP 14 - Virtualization of the
telecommunications network of an
TP 3 - VLANS, WireShark autonomous seaport
TP 4 - VPCS, Tracert TP15 - Implémentation de la qualité de
TP 5 - VPCS, RipV2 service (QoS) dans un backbone IP/MPLS
TP 6 - VPCS, OSPF Practicals manuals made available to students
TP 7 – InterVLans Routing

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 238

TP 15 - Implementation of Quality of Service
(QoS) in an IP/MPLS backbone

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 239

Implementation of Quality of Service (QoS) in an IP/MPLS backbone

1) Entering the ip/mpls backbone of Telco on GNS3

2) MPLS-VPN implementation
3) Quality of service implementation
4) Traffic engineering implementation

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 240

Entering the ip/mpls backbone of Telco on GNS3
BACKBONE IP/MPLS OF TELCO

Routeurs clients
routeurs Cisco
Switch CISCO manageable de 48
7609-S et 24 ports
routeurs Cisco 7206-VXR

Routeurs permettant de se connecter a

internet
CISCO 7609

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 241

Entering the ip/mpls backbone of Telco on GNS3
BACKBONE IP/MPLS OF TELCO (Yaoundé-Douala)
Adresse
loopback
Adresse sous-réseau

Adresse interface

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 242

 WORK TO DO

1) Entering the IP/MPLS backbone of Telco on GNS3

2) MPLS-VPN implementation
3) Quality of service implementation
4) Traffic engineering implementation

Submit on May 15, 2023 a detailed report (text file and

audiovisual recording) on the implementation including all
phases with commented screenshots for all configurations.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 243

 MPLS-VPN IMPLEMENTATION

Description

routing protocol
RIP: between CE-PE
OSPF: distributing labels, determining
next hop
MP-BGP: the exchange of VPN routes
between PEs
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 244
MPLS-VPN IMPLEMENTATION
• Step 1: Addressing and routing protocols
• Step 2: Enabling MPLS on Routers and Interfaces
• Step 3: configuration of the VRFs (virtual routing and forwarding)
on ​the PEs
• Step 4: Configure BGP routing between PE and redistribute routes
between BGP and RIP
• Step 5: Connectivity Tests

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 245

 MPLS-VPN IMPLEMENTATION

Step 1: Addressing and routing protocols

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 246

 MPLS-VPN IMPLEMENTATION

Step 2: Enabling MPLS on Routers and Interfaces

❑ Enabling MPLS on all

backbone routers and their
interfaces

❑ Enabling the CEF switching

technique (cisco express
forwarding)

❑ Activation of the LDP label

distribution protocol

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 247

 MPLS-VPN IMPLEMENTATION

Step 3: configuration of the VRFs (virtual routing and forwarding) on ​the PEs

❑ RD (route distinguisher): unique identifier

associated with each VRF on the PE
❑ RT( route target): filter that allows the
import and export of client routes
❑ Associate VRFs with different interfaces

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 248

 MPLS-VPN IMPLEMENTATION

Step 4: Configure BGP routing between PE and redistribute routes between BGP and RIP

❑ BGP: allows communication

between two or more PEs for
precise VPN
❑ Configuring neighbors, enabling
and configuring address families

❑ Interconnection between BGP

and RIP

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 249

 MPLS-VPN IMPLEMENTATION

Step 5: Connectivity Tests

Ping from CE-A1 to CE-A2

Ping from CE-B1 to CE-B2

Ping from CE-A1 to CE-B2

Ping from CE-B1 to CE-A2

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 250

QUALITY OF SERVICE (QOS) IMPLEMENTATION

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 251

 QUALITY OF SERVICE (QOS) IMPLEMENTATION

Presentation

Most major networks offer different services to users to satisfy their needs.
telephony services, internet access, data transfer, server hosting

It is therefore necessary that some of these services are more accessible than others,
that is to say that one will prefer, for example, to improve the quality of transfer of
telephony services to the detriment of data transfers

Quality of Service is the ability to provide a service that meets the requirements

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 252

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Presentation

QOS parameters
QOS models
❑ Bandwidth: the number of bits
per second that a link can
transmit. ❑ the BEST EFFORT model

❑ Delay: refers to the time it

takes to get an elementary ❑ the service integration model
amount of data from the (INTSERV)
source to the destination.

❑ Jitter: the variation in delay ❑ the service differentiation model

between packets. (DIFFSERV)

❑ Packet loss: bytes lost during

the transmission of packets.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 253

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Overview QOS Management Mechanisms

❑ Filtering and classification authorize and

organize traffic into classes of service based on
specific criteria: address range, IP precedence
value, DSCP (DiffSer code point), COS (class of
service), MPLS EXP (MPLS label)

❑ Marking is the action of inserting a value in the

IP header that network equipment can
interpret and translate into behavior.

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 254

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Presentation

Buffer management
❑ discard packets in case of congestion of a router Scheduling
port buffer. The elimination is done selectively,
according to the QoS criteria of the traffic. Allows bandwidth to be shared between multiple
streams
❑ The WRED (weighter random early detection)
algorithm. FIFO: Packets are processed in the order they arrive

PQ: High priority packets are always served

WRR: Packets are served according to the weight of

the queue

WFQ: Fair bandwidth sharing

CBWFQ: Bandwidth sharing based on priorities and

classes

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 255

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Presentation

Policing and Shaping allow the verification of traffic compliance

SHAPING
Reclassifies packets with low priority in case of non-compliance

POLICING
Removes non-compliant packages

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 256

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - traffic study

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 257

 IMPLEMENTATION OF QUALITY
OF SERVICE (QOS)

Dimensioning - filtering and classification

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 258

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - creation of QOS policies

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 259

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - CE-PE policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 260

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - IP2MPLS policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 261

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - MPLS2MPLS policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 262

IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Dimensioning - MPLS2IP policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 263

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - CE-A1 router (same as CE-A2) - filtering and classification

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 264

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - CE-A1 router (same as CE-A2) - CE-PE policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 265

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - CE-A1 router (same as CE-A2) - attach policy to interface

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 266

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - PE-JAMOT router (same as PE-BONANDJO) - Filtering and classification

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 267

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-JAMOT(same as PE-BONANDJO) - policy IP2MPLS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 268

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-JAMOT(idem PE-BONANDJO) - policy MPLS2MPLS

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 269

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-JAMOT(same as PE-BONANDJO) - policy MPLS2IP

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 270

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - PE-JAMOT router (same as PE-BONANDJO) - policy attachment

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 271

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-YDE- CTN (same as PE-BAF et

PE-BDA) – filtering and classification

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 272

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-YDE- CTN (same as PE-BAF et

PE-BDA) – MPLS2MPLS policy

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 273

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

Configuration - router PE-YDE- CTN (same as PE-BAF et

PE-BDA) – policy attachment

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 274

 IMPLEMENTATION OF QUALITY OF SERVICE (QOS)

verification

❑show run

❑Show policy-map

❑Show policy-map interface

❑Show interface

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 275

 TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Description

Traffic engineering includes all routing control methods that optimize the use of resources
while guaranteeing quality of service

The objective of traffic engineering mechanisms is to maximize the amount of traffic that
can pass through a network in order to delay investments as much as possible, while
maintaining the quality of service

The MPLS-TE mechanism allows the establishment of explicitly or dynamically routed MPLS
tunnels based on traffic constraints and available network resources.

Traffic engineering is about putting traffic where the bandwidth is, while network engineering is
about putting bandwidth where the traffic goes.

The traffic engineering problem takes as input a network topology and a traffic demand in the form
of a traffic matrix with different characteristics (bandwidth, delay...) and provides as output a set of
paths to meet the demand.
DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 276
 TRAFFIC ENGINEERING (TE) IMPLEMENTATION

MPLS-TE Topology Description

MPLS-TE architecture
TE topology - MPLS-TE tunnels - constraint routing

A TE topology is an extended network graph including link traffic engineering parameters

The maximum bandwidth (BM): maximum bandwidth that can be used on the link. It generally
corresponds to the physical bandwidth of the link.

The maximum reservable bandwidth (BMR): the maximum amount of bandwidth that can be
reserved by all MPLS-TE tunnels on a link.

the available bandwidth of the link (BD): the residual bandwidth that can be reserved by tunnels on
the link. It is dynamically modified when a tunnel is created or deleted

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 277

 TRAFFIC ENGINEERING (TE) IMPLEMENTATION

MPLS-TE Tunnel Description

An MPLS-TE tunnel is an MPLS LSP with an associated set of TE parameters.

A TE tunnel includes, but is not limited to, the following:

❑ the address of the destination router

❑ the partial or complete explicit path
❑ the set of elements to be excluded from the path
❑ the preemption priorities (the hold priority (ph) which corresponds to
the ability to resist preemption and the setup priority (ps) corresponding
to the ability of a tunnel to preempt another tunnel)
❑ the administrative groups to include/exclude
❑ the bandwidth to reserve for the tunnel
❑ the metric to use for the tunnel

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 278

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Description Constrained routing

The TE topology discovery function: this function allows all routers to have an
updated view of the TE topology and in particular of the residual bandwidth that can
be reserved on the links

the tunnel placement (or computation) function: this function is based on a

constraint routing algorithm that takes the TE topology and the tunnel constraints as
input and returns a constrained path if it exists

the tunnel establishment function: it is responsible for establishing tunnels along the
explicit route provided by the placement function, as well as for maintaining and
deleting tunnels

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 279

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Description

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 280

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Dimensioning

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 281

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Configuration - TE activation and maximum bandwidth

configuration (BMR)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 282

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Configuration – Tunnel parameters

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 283

 TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Configuration – Tunnel parameters

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 284

TRAFFIC ENGINEERING (TE) IMPLEMENTATION

Configuration – IGP for MPLS-TE

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 285

 TRAFFIC ENGINEERING (TE) IMPLEMENTATION

verification

Show mpls traffic-eng tunnels tunnel 0

Show mpls traffic-eng tunnels destination

Work to be submitted
❑ Provide a detailed report on the QOS implementation including all
phases (screen shot for all configurations).

❑ Identify the parameters of the configured tunnels (tunnel identity,

tunnel type, TE parameter and tunnel path)

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 286

 TRAFFIC ENGINEERING (TE)
IMPLEMENTATION

configuration - verification

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 287

DESIGN AND ANALYSIS OF NETWORK SYSTEMS
ISN 6030

Network design and simulation with GNS3

END

Professeur Emmanuel TONYE et Ingénieur Rholy NKUH

[email protected] et [email protected]
https://sapiotech.enspy.net
https://www.researchgate.net/profile/Emmanuel_Tonye
2023

DESIGN_Analysis_NETWORK_Practicals_Pr TONYE 288