Reference no: EM132160386

Case Study -

Deliverables:

1. EVE configuration file containing your configured network.

2. A document (.doc .odt or PDF) containing:

a. An outline of the IP subnet allocations used in your network.

b. The results of your testing of various aspects of the network and its operation.

Please include your student number and name in the filename for the EVE topology and the document.

Topology -

Scenario -

Donald Trump has employed you to implement a network providing connectivity for guests and administration at the Trump Hotel. In addition he would like you to provide connectivity to his personal PC located at Trump Towers.

Before trusting you to work on his network he would like you to create a prototype using the provided EVE topology and provide some brief documentation outlining your addressing structure and the results of your tests of the network and its functionality.

Requirements -

There is considerable flexibility in terms of how you complete the configuration of the network. Don't make things more complex than they need to be.

IP addressing structure

Head office has allocated you two blocks of addresses. See the table at the end of this document for the IP address ranges you have been allocated.

Addressing the core-core-border point to point links. Head office have allocated you three /30's starting from 192.168.0.Core in a continuous block. For example if your starting point is 192.168.0.140 then you can use 192.168.0.140 /30; 192.168.0.144 /30 and 192.168.0.148 /30. You should use these networks to address the three links between the border and the core routers.

Addressing the rest of the network. Head office have allocated you a block of addresses in the form of 10.Main.0.0 /16. You are free to allocate these addresses as required. It is corporate policy that all point-to-point links are /30 (between core and distribution) and all LANs are /24 (Hotel Guest; Hotel Admin; Trump Tower).

There is no requirement to use VLSM to further subnet the address space. Just use /24 for the LANs and /30 for the links. The complexity in this section relates to careful structuring of the addresses to allow for summarisation. A passing mark is does not require summarisation but you will receive more marks for an optimised design.

You need to submit your IP addressing structure as part of your documentation. It doesn't need to be elaborate. A simple table outlining the network, mask and where it is applied is all that is required. If your addressing scheme lends itself to summarisation then you should include the summary address in your documentation.

Routing

It is corporate policy that all routing is performed using OSPF protocol.

Border Router connection to the ISP

You can examine the configuration of the ISP router and use it for troubleshooting but you should not make permanent changes to the ISP configuration. If you do make unathorised changes these may be removed when your case study is graded.

• The ISP uses PPP encapsulation with CHAP authentication.
• The ISP username is "ISP" and it assumes that the border router username is "TrumpBorderRtr" the password for CHAP is "H4rd2gu355". Take care with capitalisation.
• The ISP has allocated you the global address 134.115.0.2 255.255.255.252 which needs to be configured on your router s1/0 interface. Their address is 134.115.0.1.

Basic Functionality

First and foremost the network should work. Prior to implementing security (ACLs), all hosts should be able to ping on another and the internet sites (4.3.2.1 and 200.100.50.1-99). A significant number of marks are assigned to functionality. You should be very cautious in configuring the optimisations to ensure that you don't break the network.

Security

Construct and apply suitable ACLs to implement the following policies:

• Donald is annoyed that the Internet news web server at 200.100.50.25 (port 80) is publishing "fake" news. He has asked that you block this web service for guests of the Trump Hotel.
• No one in the Trump network who is outside Trump Towers is permitted to send packets directly to Donalds computer.

Configuring Test PCs

The PCs are actually routers with a PC icon.

• Configure their IP address on e0/0 as you would any other router.
• The same effect as a default-gateway can be achieved using a default-route. For example: ip route 0.0.0.0 0.0.0.0 10.0.0.1 (in this example the gateway address is 10.0.0.1).
• The configuration of the PC's will be saved with the normal EVE "export" function.

NAT

As the Trump network uses private addresses you will need to configure NAT. The configuration for NAT is given to you below:

TrumpBorderRtr(config-if)#int e0/0

TrumpBorderRtr(config-if)#ip nat inside

TrumpBorderRtr(config-if)#int e0/1

TrumpBorderRtr(config-if)#ip nat inside

TrumpBorderRtr(config-if)#int s1/0

TrumpBorderRtr(config-if)#ip nat outside

TrumpBorderRtr(config-if)#exit

TrumpBorderRtr(config)#ip nat inside source list NAT-ACL interface serial 1/0 overload

TrumpBorderRtr(config)#ip access-list standard NAT-ACL

TrumpBorderRtr(config-std-nacl)#permit 10.0.0.0 0.255.255.255

Optimisation

A portion of the marks for the case study are given for a well designed and configured network. This is the difficult part of the case study and you may find that errors in your optimisation will break your functionality. It is recommended that you only implement the optimisations that you can get to work.

Best practice

• Give each router a meaningful hostname.

Summarisation

• By carefully assigning your address ranges and breaking OSPF into areas you can use the "area range" command to summarise addresses and minimise the number of routes in the routing table.
• A well designed and summarised IP addressing structure will simplify your ACL statements.

Network resilience

• There are redundant links between the core routers and the border router. You should be able to shut down either of the links and full connectivity should still be possible.
• Trump Towers has a redundant distribution router. It should be possible to shut down either of these and Donald should still have access to the network. For this to work you would need to implement HSRP.

TESTING

You must thoroughly test the functionality of your network and document the results. Document the type of testing you employed and the results of those tests. The test results need to clearly identify any problems with your network and its functionality. If you state that something works when it does not you will lose marks in this section. The tests need to be accurate and thorough but try to be concise. There is no need to provide screenshots of tests. Just list the test such as: "Donald can ping 4.3.2.1" and the result such as "PASS". A table would be a suitable way to present this information.

Don't limit yourself to to simple connectivity "Donald can ping the Internet". If you configure HSRP how do you test that? How do you test ACLs? The tests don't need to be elaborate but you should cover the technologies configured.

Notes: There is no requirement to configure the switches.

Attachment:- Assignment File.rar