Network Configuration and Algorithms Coursework

The learning outcomes that are assessed by this coursework are:

1. IPv4 Variable Length Subnet Mask (VLSM)

2. Static Routing

3. Distance Vector Routing Protocols (RIP)

4. Link State Routing Protocols

5. Multiarea OSPF

6. Network Address Translation (NAT)

7. Voice over IP (VoIP)

Your marked coursework and feedback will be available to you on: If for any reason this is not forthcoming by the due date your module leader will let you know why and when it can be expected. The Head of Studies ([email protected] ) should be informed of any issues relating to the return of marked coursework and feedback. Note that you should normally receive feedback on your coursework by no later than 20 University working days after the formal hand-in date, provided that you have met the submission deadline.

Late submission of coursework policy:

Late submissions will be processed in accordance with current University regulations which state: “The time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark

Tasks to be undertaken:

In this coursework, you are expected to answer a set of questions (Part 1 and Part 2) and configure a given network topology ‘CW.pkt’ according to a list of tasks (Part 3). You need to provide detailed stepwise justification for all parts in your report. Posting final results or configurations without proper explanation that can reflect your understanding will not be marked.

Subnet 200.25.11.0/24 to address the network topology depicted in Figure 1. Use the most efficient addressing possible. You have to present your stepwise solution with justification. Showing just the final subnets assignment will not be accepted.

B. You have decided to add a new serial link between Bldg1 and NY routers. What do you need to do to address the newly created network between the two routers?

Dijkstra’s Shortest Path First Algorithm

Figure 2 shows a network with nodes ‘a’ to ‘f’ (these are shown circled) with the indicated link costs, use Dijkstra’s algorithm to compute the least cost path from node ‘a’ to all network nodes. Show how the algorithm works by computing a Link-state (LS) table. Then show the least cost path and the forwarding table for source node ‘a’. You have to present a stepwise solution supplemented with proper justification. Showing the final results only will not be accepted.

Following the network labels, configure all of the routers’ serial interfaces with all DCE and DTE ends set to .1 and .2 IP addresses respectively. Clock rates have to be configured according . In your report, you are requested to include justification for a single serial link configuration.

B. All web servers on the Internet is approachable only via their public IP addresses as registered on Google Public DNS Server (already provided in file ‘CW.pkt’). Their private IP addresses are not routable and should not be disclosed to public. Configure their gateways to enforce this rule. Hint: use NAT. [5 marks]

C. Configure RIPv2 in the red-circled area.

D. Configure Multiarea OSPF {area 0, area 1, and area 2} giving proper route summarization, correct cost information, and router-id(s) if needed. [10 marks]

E. Redistribute RIPv2 updates into OSPF and vice versa.

F. Configure all of the devices in Organization A. Router 1 should act as a DHCP server for all of the workstations and IP Phones. They should all get private, unrouteable IP addresses as per the depicted network labels. PCs should be able to access the Internet via BT-ISP.

Enable telephone communication between Organization A and B. Hint: configure a dial-peer.

H. Microsoft has decided to offer its own public DNS service. For that, the topology is updated according . Update the topology and the configuration of ‘CW.pkt’ file so that the newly created Microsoft Public DNS Server is reachable using its public IP address 11.3.3.3. Do you notice any issues in the network? If yes, discuss how can you solve them.