Modelling and Simulation of A Network Management Solution in GNS3 Using PRTG
Modelling and Simulation of A Network Management Solution in GNS3 Using PRTG
Course Instructor:
Dr. FOZIN Theophile
Dr. DEUSSOM Eric
ABSTRACT
Network Management today has become a real necessity in the world of Network Engineer ing.
Many network companies need to constantly check the state of their network and this requires
a god expertise which can be gotten through a mastery of the simulation process used. Network
Simulation is very important because it gives a sure way of predicting what the actual real
results will be.
A virtualized network function, or VNF, may consist of one or more virtual machines running
different software and processes, on top of standard high-volume servers, switches and storage
devices, or even cloud computing infrastructure, instead of having custom hardware appliances
for each network function
LIST OF ACRONYMS
ACRONYM MEANING
AS Autonomous system
DB Database
IP Internet Protocol
IT Information Technology
OS Operating System
VM Virtual Machine
LIST OF TABLES
LIST OF FIGURES
LIST OF PICTURES
TABLE OF CONTENTS
Abstract………………………………………………………………………………………...ii
List of Acronyms……………………………………………………………………………...iii
List of Tables…………………………………………………………………………………..v
List of Figures…………………………………………………………………………………vi
List of Pictures………………………………………………………………………………..vii
Chapter 1 INTRODUCTION…………………………………………...............................1
1.1 Background and Context of Study……………………………………………………1
1.1.1 Classful IP Addressing and Sub netting……………………………………….1
1.1.2 Virtualization overview………………………………………………………...5
1.2 Problem Statement……………………………………………………………………7
1.3 Objectives…………………………………………………………………………….8
1.3.1 General Objectives……………………………………………………………..8
1.3.2 Specific Objectives……………………………………………………………..8
1.4 Proposed Methodology……………………………………………………………….8
1.5 Research Questions…………………………………………………………………...8
1.6 Research Hypothesis………………………………………………………………….9
1.7 Significance of Study…………………………………………………………………9
1.8 Scope of Study………………………………………………………………………..9
1.9 Delimitation of Study…………………………………………………………………9
1.10Definition of Keywords and Terms…..……………………………………………..9
1.11Organization of Project Report……………………………………………………10
2.1 Introduction……………………………………………………………………….....11
2.2 Proposed Methodology……………………………………………………………...11
2.3 Design……………………………………………………………………………….12
2.4 Description of the Resolution Process………………………………………………13
2.5 Partial Conclusion……………………………………………………………….......13
3.1 Introduction………………………………………………………………………..14
3.2 Tools and Materials used…………………………………………………………..14
Chapter 4: CONCLUSION…………………………………………………………………25
REERENCES……………………………………………………………………………….27
Chapter 1: INTRODUCTION
When IP was first standardized in September 1981, the specification required that each system
attached to an IP-based Internet be assigned a unique, 32-bit Internet address value. Systems
that have interfaces to more than one network require a unique IP address for each network
interface. The first part of an Internet address identifies the network on which the host resides,
while the second part identifies the particular host on the given network. This creates the two
level addressing hierarchy that is illustrated in Figure 1 [1]
Three main classes of addresses are used for networking: Class A, Class B and Class C. Class
D addresses have their leading four bits set to 1-1-1-0 and are used to support IP Multicasting.
Class E addresses have their leading four bits set to 1-1-1-1 and are reserved for experimenta l
use.
Each Class A network address has an 8-bit network prefix, with the highest order bit set to
0 (zero) and a 7-bit network number, followed by a 24-bit host number. Today, Class A
networks are referred to as “/8s” (pronounced “slash eight” or just “eights”) since they have
an 8- bit network prefix. Since the /8 address block contains 2 31 (2,147,483,648 ) individ ua l
addresses and the IPv4 address space contains a maximum of 2 32 (4,294,967,296) addresses,
the /8 address space is 50 percent of the total IPv4 unicast address space
Each Class B network address has a 16-bit network prefix, with the two highest order bits
set to 1-0 and a 14-bit network number, followed by a 16-bit host number. Class B networks
are now referred to as “/16s” since they have a 16-bit network prefix. A maximum of
16,384 (214 ) /16 networks can be defined with up to 65,534 (216 -2) hosts per network. Since
the entire /16 address block contains 230 (1,073,741,824) addresses, it represents 25 percent
of the total IPv4 unicast address space
Each Class C network address has a 24-bit network prefix, with the three highest order bits
set to 1-1-0 and a 21-bit network number, followed by an 8-bit host number. Class C
networks are now referred to as “/24s” since they have a 24-bit network prefix. A
maximum of 2,097,152 (221 ) /24 networks can be defined with up to 254 (28 -2) hosts per
network. Since the entire /24 address block contains 2 29 (536,870,912) addresses, it
represents 12.5 percent (or one-eighth) of the total IPv4 unicast address space.
Subnetting
Subnetting attacked the expanding routing table problem by ensuring that the subnet structure
of a network is never visible outside of the organization’s private network. The route from the
Internet to any subnet of a given IP address is the same, no matter which subnet the destinatio n
host is on. This is because all subnets of a given network number use the same network prefix
but different subnet numbers. The routers within the private organization need to differentiate
between the individual subnets, but as far as the Internet routers are concerned, all of the subnets
in the organization are collected into a single routing table entry. This allows the local
administrator to introduce arbitrary complexity into the private network without affecting the
size of the Internet’s routing tables.
What exactly are dynamic routing protocols? Routing protocols are used to facilitate the
exchange of routing information between routers. Routing protocols allow routers to
dynamically learn information about remote networks and automatically add this informa tio n
to their own routing tables
Routing protocols determine the best path to each network, which is then added to the routing
table. One of the primary benefits of using a dynamic routing protocol is that routers
exchange routing information whenever there is a topology change. This exchange allows
routers to automatically learn about new networks and also to find alternate paths if there is
a link failure to a current network.
Routing protocols can be classified into different groups according to their characteristics:
i. IGP or EGP
ii. Distance vector or link-state
iii. Classful or classless
IGRP: The distance vector interior routing protocol developed by Cisco (deprecated from
Cisco IOS Release 12.2 and later)
EIGRP: The advanced distance vector interior routing protocol developed by Cisco
Interior gateway protocols (IGP) are used for intra-autonomous system routing, that is,
routing inside an autonomous system, while Exterior gateway protocols (EGP) are used for
inter-autonomous system routing, that is, routing between autonomous systems. An
autonomous system (AS)—otherwise known as a routing domain—is a collection of routers
under a common administration. Typical examples are a company’s internal network and an
ISP’s network. The figure below helps to explain the difference between IGP and EGP
Simple Network Management Protocol (SNMP) is probably the dominant method for devices
on a network to relay network management information to centralized management consoles
which are designed to provide a comprehensive operational view of the network.
There are three components of the SNMP protocol [5] Their functions are given in the following
figure.
Figure 1.6: SNMP suit of Protocol. Structure of management information (SMI), Network
operations center (NOC), Management information base (MIB) [6]
Virtualization software defines and divides IT resources, including CPUs, memories, disks,
network adapeters, and application programs. It dynamically allocates and schdeules IT
resources for VMs, increasing the resource usage.
Server virtualization refers to the creation of multiple logical computers (virtual machines or
VMs) on a single computer (physical host). Multiple VMs can run simultaneously on a physical
host and run different operating systems. Application programs on each VM run independently.
Server virtualization improves the working efficiency of the physical host.
In summary, virtualization is simply a way of running operating systems and resources from a
virtual platfrom in order to save resources and time. Virtualization is changing the mindset from
physical to logical. What virtualization means is creating more logical IT resources, called
virtual systems, within one physical system. That’s called system virtualization. It most
commonly uses the hypervisor for managing the resources for every virtual system. The
hypervisor is a software that can virtualize the hardware resources. [9]
Type 1 hypervisor: They are hypervisors that run directly on the system hardware – A “bare
metal” embedded hypervisor. Examples include VMware ESX and ESXi, Microsoft Hyper-V,
Citrix Xen server, Oracle VM
Type 2 hypervisor: They are hypervisors that run on a host operating system that provides
virtualization services, such as I/O device support and memory management. Examples include
VMware Workstation/Fusion/Player, VMware Server, Microsoft Virtual PC, Oracle VM
Virtual Box, Red Hat Enterprise Virtualization
In most networking companies such as HUAWEI, CISCO, CAMTEL, ZTE or others, there is
a constant need for continuous data flow and information exchange. Packets must arrive on
time and Engineers must reduce the latemcy as much as possible. With this in mind, a single
fault in the system might lead to hihly consequent failure of the network. Hence, monitor ing
the network is absolutely necessary, and today many network management platforms have been
developed for this purpose. GNS3 is a network simulator, and PRTG is an excellent network
monitoring platform which can easily give use the state of our networkin real time so that the
least fault will be detected by the alarm system set up by the SNMP traps.
1.3 OBJECTIVES
1.3.1 General Objectives
The ultimate objective of this work is to monitor a network designed in GNS3 platform,us ing
PRTG and CACTI. This network management is very close to the reality faced in Networking
and Telecommunications company, where the network needs to be constantly running and up
The proposed methodology we took to implement this project is to first of all understand how
the system works, then interconnect the various components of the system in a more accurate
way.
1.6RESEARCH HYPOTHESIS
The research hypothesis we used was simply to go on and answer the questions established
above. Once we got an answer to all of them we could establish the fact that redundancy routes
are important as the serve the purpose of security, and also, no specific IP address is to be used
for the routers.
This study is signifies a lot, as it will be a true means of monitoring a network connected
either in real life or for a developping project on a network management platform. Network
companies can learn from this concept and solve problems found in their companies.
The scope of this study encompasses a mastery of networking, IP addresses, routing protocols,
VLANs, network simulating tools, and network management platforms. Both the theoretical
and most importantly the practical part of this scope should be covered for excellent results to
be obtained.
This project report can easily be split into four main chapters. The first one here simply gives
some fundamental elements of networking, together with the scope, objectives, problem
statement, and other vital elements.
The next chapter deals with understanding the analysis and design of the project. This covers
the methodology used, and the global architecture of the system.
Chapter Three has to do with the implementation, realization and presentation of results. It is
in this chapter that we have a detail of the results.
Finally, chapter four is the conclusion of the project, giving a summary of findings, contributio n
to Engineering and Technology, recommendations, and a thought for future work.
2.1INTRODUCTION
This chapter deals with the getting in detail, the project methodology used in the project. Here
all the steps taken for the realization of the project are given. The flowchart and procedures
used are well revealed.
2.2PROPOSED METHODOLOGY
The project methodology flowchart above perfectly describes the methodology used for
designing and simulating the network. First of all, a VM needs to be created in virtual box, and
PRTG installed in its Windows server, or any other OS and DB. Then the network is designed
in GNS3, and we integrate our PRTG from the VM into the network using a special interface
unique to the VM. After that, the next step is to check if PRTG can connect to the network by
pinging the IP addresses of the various routers in the VM. If packets can be sent, then the
connection was ok, and the final step is simply to add each network device in PRTG and run
auto discovery on the list of sensors that show to monitor the entire network.
2.3DESIGN
Prerequisite:
2.5PARTIAL CONCLUSION
We have seen in detail the perfect design of the system. In the next chapter we shall see the
perfect simulation and realization of the network.
3.1INTRODUCTION
In this chapter we shall monitor the network using PRTG Network Monitor, and get the output
from the sensors.
Oracle Virtual Box was open and a new virtual machine was created. Its memory and
hard disk size were dynamically allocated, and we configured the machine to support the
windows server.
To allow the VM to connect to the network, a new interface needs to be added in the Network
Panel of the VM. There, we disable the NAT, create a second network interface and select
Virtual Box Host Only Adapter
To start the virtual machine, the icon was clicked and the installation process
of Windows server 2012 began
To install PRTG in the network, we went to its website at https://paessler.com, and from
there the first download link was cheked and we could download ans install the software.
The free license key was also given to us which is very imortant during the installa tio n
process. Once the virtual machine has been successfully created, next PRTG was
downloaded from the server’s internet and installed in the virtual machine. PRTG was the n
launched and verified working.
Code to configure the ip address of the routers in the console Site 1 for example
SITE1#config t
SITE 1(config)# interface ethernet 0/2
SITE 1(config- if)# ip address 172.24.20.2 255.255.255.248
SITE 1(config- if)# no shutdown
SITE 1(config- if)# exit
have been really given ip addresses, we ran the code SITE1# show ip route in SITE 1 for
example, and the following results were displayed:
From above, we can see three routes hence the ip addresses were successfully configured.
Now that all the routers were successfully configured, we need to configure the routing
protocol. The routing protocol chosen was RIP version 2
The commands are as follows:
Site 1:
SITE1#config t
SITE1(config)# router rip
SITE1(config-router)# version 2
SITE1(config-router)# network 172.24.20.2
SITE1(config-router)# network 172.24.40.1
SITE1(config-router)# network 172.24.30.2
SITE1(config-router)# no auto-summary
SITE1(config-router)# exit
SITE1(config)# exit
SITE1# write
This same process was done for all four routers in their console.
Then each routers were configured the SNMP protocol to enable PRTG send SNMP traps
to the routers. The following command was mae for one router, showing the example for
the rest. The ip address used here is the ip address of the virtual machine.
Site 1:
SITE1#config t
SITE1(config)# snmp-server community public RO
SITE1(config)# exit
SITE1# write
SITE1# snmp-server host 192.168.10.2 version 2c public
SITEsnm-server enable traps
Inside our GNS3 Architecture, we connected a cloud representing PRTG server, and then the
network interface of the virtual machine was selected and applied in the configuration
properties of the cloud.
After connecting the various elements of the network as planned, and making sure all IP address
are well configured to their respective ports, also making sure that the SNMP traps have been
configured on all routers, in PRTG we open the PRTG Administrator page which appears in a
web browser.
Then from there we add new devices. Each device has the IP address of a router in order to
make sure the sensors can check the data packets flowing to it.
When all the devices have been added, the final step is to run Auto Discovery in order to view
the output from the sensors.
Picture 3.12: Ping sensor used in PRTG for router ‘CENTRE DE SUPERVISION’
Picture 3.13: Various sensors connected to a single router. Green indicates working, and
red failure
From the above diagrams, we can see that the sensors have been well connected to the routers
through SNMP traps, and this gave us a good monitoring of the network.
3.6PARTIAL CONCLUSION
As we have seen, we had the above results obtained after monitoring with PRTG. We can
conclude that the network is operating well under normal circumstances, as can be revealed by
the sensors connected to them.
4.1SUMMARY OF FINDINGS
In a nutshell, we can say that the network has been successfully monitored using PRTG. Each
device had at least 8 sensors that collected information from the network elements in order to
display in real time the output in terms of traffic, speed, data, system health, uptime and much
more. Many other sensors could be added, such as Community SaaS. The design and
monitoring of GNS3 Network Architecture was a success.
4.3RECOMMENDATIONS
Networking Companies such as CISCO, HUAWEI, and CAMTEL can use such a project to
monitor the performance of their given networks.
4.4DIFFICULTIES ENCOUNTERED
Oracle Virtual Box we used did not support 64-bit software, therefore when we were
installing the Windows 12 server optical disk we encountered challenges. To solve this
problem, we had to boot the computer and check the virtualization box in the Data
configuration section, before restarting the computer.
Installing PRTG was quite challenging, as at first many .dll files were missing for proper
installation.
The initial IP address given by the lecturer for the various routers could not ping, so we
slightly changed the addresses to be able to ping the routers and monitor them with PRTG
4.5FUTURE WORKS
As a future scope we can use VMware Workstation instead of Oracle Virtual Box since it
offers a more effective way of working with the virtual machine, especially when
monitoring the network with CACTI.
Redundant links can be added for the connection of Centre de Supervision with Site 3 and
Site 2, in order to increase reliability of the network
Other network monitoring tools such as CACTI and Solar Winds can be used to monitor
the network and with different results obtained from different network monitoring tools,
the Network Engineer will know with precision the detail of information conveyed by each
network element.
REFERENCES
[1] 3com, “Understanding IP Addressing: Everything you ever wanted to know” White Paper,
3Com Corporation, Corporate Headquarters, 5400 Bayfront Plaza, Santa Clara, CA 95052-
8145, Copyright ©2001
[2] Dr. DEUSSOM Eric, “U2000 Virtualization Solution Overview”, Product Version:
V300R019C10, Euler OS, Taishan, EEF 679 Network Management, Faculty of
Engineering and Technology, University of Buea, 2021
[3] Tatap Perets, “Implementation of AVoIP Live Broadcasting Technology”, Internship
CRTV, Faculty of Engineering and Technology, University of Buea, 2018
[4] CISCO CCNA Exploration Guide, “Introduction to Dynamic Routing Protocols”, 2018
[5] Dr. Théophile FOZIN, “Network Management – SNMP”, EEF 679 Network Management,
Faculty of Engineering and Technology, University of Buea, 2021
[6] CISCO Labs, “Lab – Configuring SNMP”, Inch Techs, Open Technology, Cisco © 2001,
Public