Quick EIGRP Ticket

This is a really simple EIGRP lab, based off of a lab objective I ran into over this past weekend. There are a couple different ways to solve it, but for as simple as the topology is it makes for an interesting lab. As promised, I'll deliver on my MPLS labs, but I wanted to post this one as it was really quick to set up.

Here's the scenario, you have three routers, conveniently named R1 R2 and R3. All connected on a shared Ethernet segment. The objective is to have a full mesh peers, but achieve hub-and-spoke routing with R1 as the hub (i.e. R2 and R3 route all traffic through R1). When completed, your results should look similar to the following:

R2#show ip route eigrp

     1.0.0.0/32 is subnetted, 1 subnets

D       1.1.1.1 [90/156160] via 10.10.123.1, 00:00:53, FastEthernet0/0

     3.0.0.0/32 is subnetted, 1 subnets

D       3.3.3.3 [90/158720] via 10.10.123.1, 00:00:28, FastEthernet0/0

D EX 213.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:05:43, FastEthernet0/0

D EX 212.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:05:43, FastEthernet0/0

D EX 211.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:05:43, FastEthernet0/0

D EX 210.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:05:43, FastEthernet0/0

R2#show ip eigrp neighbors

IP-EIGRP neighbors for process 200

H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq

                                            (sec)         (ms)       Cnt Num

1   10.10.123.3             Fa0/0             12 00:05:51   27   200  0  17

0   10.10.123.1             Fa0/0             11 00:07:33  137   822  0  19

R3#show ip route eigrp

     1.0.0.0/32 is subnetted, 1 subnets

D       1.1.1.1 [90/156160] via 10.10.123.1, 00:02:40, FastEthernet0/0

     2.0.0.0/32 is subnetted, 1 subnets

D       2.2.2.2 [90/158720] via 10.10.123.1, 00:02:01, FastEthernet0/0

D EX 200.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:07:30, FastEthernet0/0

D EX 201.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:07:30, FastEthernet0/0

D EX 202.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:07:30, FastEthernet0/0

D EX 203.0.0.0/24 [170/2560005376] via 10.10.123.1, 00:07:30, FastEthernet0/0

R3#show ip eigrp neighbors

IP-EIGRP neighbors for process 200

H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq

                                            (sec)         (ms)       Cnt Num

1   10.10.123.2             Fa0/0             11 00:07:46  186  1116  0  19

0   10.10.123.1             Fa0/0             10 00:07:46  183  1098  0  19

While meeting the following restrictions:

 - You may not change the IP Address on any interface.

 - You may not create any new interfaces.

 - You may not add any route-maps.
 - You can not modify the configuration on the switch.

GNS3 Files 

Diagrams:

Solution:

Fun with MPLS - Part 1/'however many of these I feel like doing'

So you're an Engineer for a small company with offices in Delaware and Carmel, both locations are just awful but at least in Delaware you're near the water. Your SP provides both Layer 3 and Layer 2 MPLS VPN between both locations, you're not entirely sure why you have both but suffice to say the solutions engineer had a few extra drinks on you after that sale. Currently you have 768K per pvc, and you've noticed that you're not load sharing traffic between the two available connections. Weeks after discovering this the SP still has not resolved your issue, so you've offered to come work for them for a day to get it resolved. Sure it's a bit extreme, but if you get one more status call informing no progress has been made you might be looking at first degree murder and based on your research Delaware supports the death penalty.

With all that, your goal is to get Carmel and Delaware to load share traffic over their two available PVCs. You can test this via Delaware and Carmel's loopback address (192.1.1.1/192.2.2.2). Here are your restrictions.

- You may not add any new interfaces
- You may not modify the configuration on either the LEC Frame switches, or on P1 or P2.
- No static routing is allowed.
- You may not enable any additional routing protocols.

GNS3 Files

Diagrams:

Solution:

R3's clock is out of sync!

You've just received a ticket from the NOC stating that R3's clock is out of sync. Please make sure R3 is receiving accurate time from it's NTP server. Also note that you may not disable any security features on any device, per company policy. Also note the solution of this ticket isn't based around clocks showing any particular time, but rather that NTP is just in sync.

GNS3 Files

Diagram:

Solution: 

Sorry about the quality, I'll be back in HD for the next one!

Starting off with the basics

So, after a fun bout on Facebook I decided to take this troubleshooting ticket on the road! Here's the scenario. You have two routers directly connected via a Serial connection. R1's is assigned IP address 10.1.1.1/24 and R2 is assigned 10.2.2.2/24. Your mission, should you choose to accept it, restore reach-ability between these two devices within the restrictions below. The results of your solution should closely match that of the attached picture. 

  RESTRICTIONS:

• You may not modify the IP Address or subnet mask of any interface
• You may not create any new interfaces, or connect existing ones.
• You may not enable any routing protocol.
• Do not add any static routes.
• Your results should closely match the attached picture.
• Your solution should allow for running RIP over this connection in the future.

Check here for GNS3 files: https://drive.google.com/folderview?id=0B_siZpm5m5eINkotYlZlUUVKaUk&usp=sharing


  SOLUTION: