Contest #2: EIGRP Troubleshooting

Posted: July 6, 2015 in Contests
Tags: , , , ,

Using the network diagram below and the output from the show commands on the routers, identify and resolve why a host on the 192.168.20.0/24 subnet cannot reach a host with IP address 172.16.0.100. Contest #2 network   Contest #2 R1 Contest #2 R2 Contest #2 R3 The rules remain the same: 1st to comment with the right solution wins. We wanted to make this contest available to more people around the globe and so we have made several options available for the prize:

  • N3,000 sent to a Nigerian bank account
  • Amazon gift card worth $15
  • $15 sent to a PayPal account

Unfortunately, these are the only prize options available. Hopefully the winner will be able to receive the prize in any of the forms above. Remember to subscribe via Email to receive updates about new contests and solutions. Success!

Advertisements
Comments
  1. crUnk says:

    Here are some errors I have seen from the o/p commands

    R1: -> run EIGRP on the 192.168.20.0 network (NOT 192.168.28.0, as shown in the output), add the network to EIGRP

    R3: -> EIGRP AS should be 123 NOT 23, Means R3 will not form neighborship with any of the
    routers
    -> Change the Metric K values as well on R3, else neighborship wont come up.

    Like

  2. Mr Sturvs says:

    1.Wrong network advertised under eigrp 123 on R1, should be 192.168.20.0 instead of 192.168.28.0
    2. gateway of last resort unnecessary on R1, else should be via fa0/0
    3. Wrong eigrp AS on R3, 23 instead of 123
    4. Eigrp metric weight mismatch on R3, K5 should be set to 0
    5. Passive interface command for fa0/1 should be removed.
    6. My account details are….. GTB 00……. to be continued.

    Like

  3. saurabh says:

    apart from above answer eigrp is only advertising /32. it must have 172.16.0.64/26 under eigrp.

    Like

    • iContests says:

      Actually, even though the “show ip protocols” is showing 172.16.0.65/32, it is actually advertising 172.16.0.64/26. The reason it is showing that way is because of how the network statement was written: network 172.16.0.65 0.0.0.0 as opposed to network 172.16.0.64 0.0.0.63.

      The “network” statement in EIGRP (and OSPF) actually tells the router which interface should run that routing protocol and not necessarily what network should be advertised.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s