Professional Documents
Culture Documents
❒ Summative Feedback:
Feedback:
+Physical:
-Physical Topology means the physical layout of the network.
-In this topology, we are concerned with how data will be transferred from the actual path.
-As per the requirement, we can modify the layout of the network.
+Logical:
-Logical topology means how the network device layout will be shown and how the data will be
transferred.
-This topology is concerned with the high-level representation of the data transfer.
User Requirements
From the model of system components in our generic system, the user component is at the highest
layer. The term user represents primarily the end users of the system, but it can be expanded to
include everyone involved in the system, such as network and system administrators and
management. User requirements is the set of requirements gathered or derived from user input and
is what is needed by users to successfully accomplish their tasks on the system. Typically, when
gathering requirements, everyone involved with that network is considered a potential user.
Figure 2.2 shows some example user requirements.
We begin describing requirements at this layer, which will lead to the development of more
specific requirements as we work through each of the components.
From the user perspective, we can ask, "What does it take to get the job done?" This will usually
result in a set of qualitative, not quantitative, requirements. Part of our job in gathering and
deriving user requirements is to make them quantitative whenever possible.
In general, the system should adapt to users and their environments, provide quick and reliable
information access and transfer, and offer quality service to the user. This indicates the following
general requirements:
Timeliness
Interactivity
Reliability
Presentation quality
Adaptability
Security
Affordability
Functionality
Supportability
Future growth
User requirements are the least technical and are also the most subjective. As shown in Figure 2.3,
requirements become more technical as they move from users to the network. All of these
requirements will be developed in more detail as we proceed through the application, device, and
network components.
A logical design of the network based on the specific requirements of the user:
A physical design of this network based on the specific requirements of the user:
Task 2 - Evaluate the design to meet the requirements
DHCP request successfully for all floors
2. Ping from Network Administrator pc - Teacher PC Successful
3. Ping from Network Administrator - Admin's pc Successful
4. Ping between teacher’s PC Successful
5. Ping between student’s PC Successful
6. Ping Student’s PC - Printers Successful
7. Ping Teacher’s PC - Printers Successful
DHCP SETTINGS
Router Settings
Router(config-if)# ip dhcp pool p1
Router(config)# network 192.168.1.0 255.255.255.0
Router(dhcp-config)# default-router 192.168.1.2
Router(dhcp-config)#exit
Dual Server is a freeware open source self-integrated DNS server for Windows/Linux. It has an
optional built-in DHCP server.
The DHCP server assigns IP addresses to computers, while the DNS server resolves them. You need
a DHCP server if you don't want to manage IP addresses manually or if you have fewer IP addresses
than computers, because the dynamic DHCP server recycles IP addresses across computers.
The DNS server is needed to resolve host names to their IP addresses. Normally your ISP will provide
you with DNS service. You may have your own DNS server, which will resolve hostnames by
forwarding them to the ISP's DNS server and caching the addresses as well.
If you have a home / small office network with Unix / Linux machines, these machines will not be
resolved by each other, as Unix / Linux machines do not support NBNS protocol and you need your
own DNS server. But what about troubleshooting local machines? Your ISP's DNS server doesn't
have this list and neither does your DNS server. Most DNS servers cannot do this (unless you
configure dynamic updates or use static IP addresses and enter them manually).
In addition to remote hosts, this server also automatically resolves DHCP-assigned local machines,
with the added benefit that both DHCP and DNS servers are always synchronous. Plus, there's no
need to create and maintain bulky zone files. Dual DHCP DNS Server is open source freeware.
Additionally, this server is designed for replicated load sharing operation
DNS features include forward and reverse lookup, zone transfer, primary / secondary mode of
operation, MX records, wildcard records, conditional and default forwarding. DHCP Fearures
supports 125 static and dynamic DHCP ranges, range filters, relay agents, and BOOTs. Options can
be specified for DHCP ranges, global, or static hosts.
Both DHCP and DNS can be used. If both services are used, DHCP-assigned hosts are automatically
added to DNS zones.
R1- R2 – R3 - Configuration
Step 1: Use global configuration commands.
Router1(config)#hostname R1
R1(config)#no ip domain-lookup
R1(config)#enable secret class
Step 2: Configure the console and virtual terminal line passwords on each of the routers.
R1(config)#line console 0
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exec-timeout 0 0
R1(config-line)#line vty 0 4
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exec-timeout 0 0
R1(config-line)#logging synchronous
Step 3: Add the logging synchronous command to the console and virtual terminal lines.
Repeat the same commands for R2 and R3
R1(config)#interface fa0/0
R1(config-if)#ip address 172.16.3.1 255.255.255.0
R1(config-if)#no sh
R1(config)#interface s0/0/0
R1(config-if)#ip address 172.16.2.1 255.255.255.0
R1(config-if)#clock rate 64000
R1(config-if)#no sh
R1(config-if)#description
R2 Interface
R2(config)#interface fa0/0
R2(config-if)#ip address 172.16.1.1 255.255.255.0
R2(config-if)#no sh
R2(config)#interface s0/0/0
R2(config-if)#ip address 172.16.2.2 255.255.255.0
R2(config-if)#no sh
Connecting DTE
R2(config)#interface s0/0/1
R2(config-if)#ip address 192.168.1.2 255.255.255.0
R2(config-if)#clock rate 64000
R2(config-if)#no sh
R3 Interface
R3(config)#interface fa0/0
R3(config-if)#ip address 192.168.2.1 255.255.255.0
R3(config-if)#no sh
R3(config)#interface s0/0/1
R3(config-if)#ip address 192.168.1.1 255.255.255.0
R2(config-if)#no sh
Pc 3
Static Routing
R1(config)#interface Serial0/0/0
R1(config-if)#ip route 0.0.0.0 0.0.0.0 172.16.2.2
R1 with default route
Client PC configuration
Network maintenance basically means you have to do what it takes
in order to keep a network up and running and it includes a number
of tasks:
Fault management: we will configure our network devices (routers, switches, firewalls, servers,
etc.) to capture logging messages and send them to an external server. Whenever an interface
goes down or the CPU goes above 80% we want to receive an e-mail so we can see what is going
on.
Configuration management: Any changes made to the network have to be logged. We will use a
change management so relevant personnel will be notified of planned network changes. Changes
to network devices have to be reported and acknowledged before they are implemented.
Accounting management: We will charge (guest) users for usage of the wireless network so
they’ll pay for each 100MB of data or something. It’s also commonly used to charge people for
long distance VoIP calls.
Performance management: Network performance will be monitored on all LAN and WAN links
so we know when things go wrong. QoS (Quality of Service) will be configured on the
appropiate interfaces.
Security management: We will create a security policy and implement it by using firewalls,
VPNs, intrusion prevention systems and use AAA (Authorization, Authentication and
Accounting) servers to validate user credentials. Network breaches have to be logged and a
appropiate response has to be made.
Test Results:
DHCP at the 2nd failed DHCP Overall Successful rate is 100% (13/13 devices got IP address
from DHPC).
Overall: I have a network system still not working properly and the process. It didn't work as
expected. Also, my network solution still does not meet the original user requirements. A nearby
educational institution due to a dangerous ping between devices on the 3rd floor above On the
positive side, the evidence above shows that the network system operates with little or no delay
or error on the first two floors. Network systems can also be upgraded and expanded to
accommodate additional computers. You can improve network security by installing a wireless
access point device and a firewall.
Things I need to improve: As mentioned above, due to the large number of computers, devices
are connected to the switch by: The cost of the cable itself or the cost of repairing/buying a new
cable is high. More wireless settings These costs can be effectively reduced. It also identifies
other ways to improve the security of this system. It is necessary if the design is practical.
Extension is only possible when two conditions are met Network systems can grow significantly.
CONCLUSION
When I completed this projectt , I learned and partially understood how to design and implement
a simple network. The project is a simple educational institution based on your requirements.
However, my work had some errors. Fix configurations that have not yet been recognized. To
help I learn and explore networks in the future, improve and develop my networking skills and
focus more on other big projects.
References:
https://www.tutorialspoint.com/what-are-the-differences-between-physical-and-logical-
topology
https://flylib.com/books/en/2.809.1.24/1/
https://networklessons.com/cisco/ccie-routing-switching-written/network-maintenance
https://www.linkedin.com/pulse/11-tips-design-secure-efficient-scalable-network-joe-baker
https://www.geeksforgeeks.org/advantages-and-disadvantages-of-computer-networking/
https://graduateway.com/difference-logical-physical-design-network/