ITC542 Internetworking with TCP/IP Network Design Project

Desklib provides solved assignments and past papers for students.

ITC542 - Internetworking with TCP/IP
Assessment Item - 4
Network Design
Student Name:
Student ID:

Executive Summary
The client side and server-side networks are different. Dynamic routing protocol is configured so
that client to server communication can be performed. Other network services like Web, DHCP
and DNS services are configured.
Student Name 1 Student ID

Table of Contents
Introduction......................................................................................................................................2
Task 1...............................................................................................................................................3
Task 2.............................................................................................................................................11
References......................................................................................................................................16
Student Name 2 Student ID

Introduction
Figure 1: Network Design
In figure 1, is the network topology for the assignment 4. In this network topology there are 2
Cisco routers, 2 Cisco switches, 3 client PCs and 3 Servers.
Student Name 3 Student ID

Task 1
1. Configuring server, PC and other router interfaces
Client Router Interface’s Configuration –
Figure 2: Client Router LAN interface’s configuration
In figure 2, the configuration is done of interface Gigabit Ethernet 0/0 with IP 192.168.0.1 and its
network subnet mask is 255.255.255.248 for the LAN network of Client-side network.
Figure 3: Client Router WAN interface’s configuration
In figure 3, the configuration is done of interface Serial interface 0/0/0 with IP 123.1.1.1 and its
subnet mask is 255.255.255.252 for the WAN network.
Student Name 4 Student ID

Server Router Interface’s Configuration –
Figure 4: Server Router LAN interface’s configuration
In figure 4, the configuration is done of interface Gigabit Ethernet 0/0 with IP 172.16.0.1, its
subnet mask is 255.255.255.248 for the LAN network of Server-side network.
Figure 5: Server Router WAN interface configuration
In figure 5, interface Serial interface 0/0/0 with IP 123.1.1.2 and its subnet mask is
255.255.255.252 for the WAN network.
Student Name 5 Student ID

Client PC Interface’s Configuration –
Figure 6: PC0 Interface’s configuration
In above figure, PC0 Ethernet interface with IP 192.168.0.2 and its subnet mask is
255.255.255.248 and the default - gateway is 192.168.0.1.
Figure 7: PC1 Interface’s configuration
In figure 7, the configuration is done of PC1 Ethernet interface with the IP 192.168.0.3 and its
subnet mask is 255.255.255.248 and the default gateway is 192.168.0.1.
Figure 8: PC2 Interface’s configuration
In figure 8, the configuration is done of PC2 Ethernet interface with the IP address 192.168.0.4
and its subnet mask 255.255.255.248 and the default gateway is 192.168.0.1.
Student Name 6 Student ID

Server Interface’s Configuration –
Figure 9: DHCP Server’s interface Configuration
Figure 10: Web Server interface’s Configuration
Figure 11: DNS Server interface’s Configuration
Student Name 7 Student ID

2. Configuring Classless Dynamic Routing on Routers
Classless Dynamic Routing on Client’s Router –
Figure 12: Classless routing on Client’s Router
In figure 12, EIGRP routing protocol is configured for networks 123.1.1.0 /30 and 192.168.0.0
/29 on client router.
Classless Dynamic Routing on Server’s Router –
Figure 13: Classless routing on Server’s Router
In figure 13, EIGRP routing protocol is configured for networks 123.1.1.0 /30 and 172.16.0.0 /29
on server router.
Student Name 8 Student ID

3. Client Ping results
To own interface –
Figure 14: Ping own interface
In figure 14, is result of ping from PC0 to its own interface.
To its local default gateway –
Figure 15: Ping to default gateway
In figure 15, is ping result from PC0 to default gateway.
Student Name 9 Student ID

To remote and router’s interface –
Figure 16: Ping to remote router’s interface
In figure 16, is ping result.
To remote server’s interface –
Figure 17: Ping to remote Server’s interface
In figure 17, is ping result shown.
Student Name 10 Student ID

4. Traceroute from the Client PC to remote server
Figure 18: Trace route to remote server
In figure 18, is result of traceroute command run PC0 to DHCP server IP address. The entries in
the traceroute are the in between hops that the packet has detected while tracerouting the server.
Student Name 11 Student ID