Waiting for answer This question has not been answered yet. You can hire a professional tutor to get the answer.
Exercise 1 - Troubleshooting EIGRP The configurations that have been applied to the devices within this lab have a number of incorrect settings and...
Exercise 1 - Troubleshooting EIGRP
The configurations that have been applied to the devices within this lab have a number of incorrect settings and are causing numerous problems.
This exercise rolls up all your troubleshooting and configuration skills learnt within the modules of this course. You will need to use all of these skills to correct the configurations on each of the devices such that you resolve the symptoms that have been noted in the symptoms list below.
Pay close attention to the diagram shown below, this diagram will give you all the information you need to fix the issues. As with any real world scenario, if there is something you don't understand, you may need to refer to your favourite search engine to gain some additional understanding on a particular technology.Symptoms
The following symptoms have been observed. Use your skills and the information in the diagram below to resolve them.
- Server PLABCSCO01 is receiving intermittent ping replies from 172.16.16.1 as shown in the image below after this list.
- The route for 10.16.18.0/24 is going via NYEDGE2 and not directly via NYEDGE1 as it should when using a traceroute from PLABCSCO01.
- NYCORE2 has no EIGRP adjacencies.
- There is an incorrect route entry for 192.168.16.0, there should only be a /24 route in any of the routing tables for this subnet.
- There is no load balancing between NYWAN1 serial interfaces s0/0/0.641 and s0/0/0.256
- The route for 172.16.10.128/25 is not being advertised.
- The route for 172.16.11.0/28 is not being advertised.
- The route for 172.16.11.128/28 is not being advertised.
Intermittent ping results on PLABCSCO01 while pinging 172.16.16.1: