ESTRUCTURA DEL UNIVERSO Y
J. A. Rubiño
Before You Begin
Please look at the provided diagrams and read through the whole lab before you start. Read the directions very carefully to make sure you are doing what is being asked of you. This is very important when you take Cisco’s CCIE lab.
Each section contains a small diagram that is designed to show you the focus of where the issue is.
Multiple topology diagrams are available for this lab, including an IPv4 and a BGP diagram.
General Rules
• You may modify, but not delete or remove any prefix-lists, route-maps, or access-lists.
• Do not modify any IP addressing on any interfaces.
• The BB routers are not accessible.
• All routers have an interface loopback 0 with the address 10.x.x.x, where x is the router number.
ISP routers have a loopback address of 10.10x.10x.10x. BB routers have a loopback address of 100.x.x.x .Switches have loopback addresses of 172.xx.xx.xx.
• MPLS routers have a loopback address of 10.x.x.x /32.
• Static/default routes are NOT allowed unless otherwise stated in the task.
• Save your configurations often.
Estimated Time to Complete: 2 hours
Pre-Setup
Please login to your vRack and load the initial Configuration. This lab is intended to be used with
online rack access. Connect to the terminal server and complete the troubleshooting tasks as
detailed below.
Diagram 5.1
Diagram 5.2
Diagram 5.3
Diagram 5.4
Incident 1 (3 points)
• Users from remote branch-1 have lost connectivity to the iPexpert HQ office.
• The users mentioned that they can still reach the other remote branches.
• Fix the issues so that remote branch-1 can reach the HQ and all the remote branches, the
outputs should match the below:
R24#sh ip route eigrp
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 10.0.0.0/8 is variably subnetted, 7 subnets, 2 masks
D EX 10.4.4.0/24 [170/542771200] via 192.168.24.6, 03:11:05, Serial2/0 D 10.13.13.0/24 [90/27008000] via 40.40.40.13, 00:00:16, Tunnel66 D 10.15.15.0/24 [90/27033600] via 40.40.40.13, 00:00:16, Tunnel66 D EX 10.23.23.0/24 [170/28288000] via 40.40.40.23, 00:00:09, Tunnel66 D EX 10.25.25.0/24 [170/28288000] via 40.40.40.25, 00:00:09, Tunnel66
172.5.0.0/24 is subnetted, 1 subnets
D 172.5.5.0 [90/27033600] via 40.40.40.13, 00:00:16, Tunnel66 172.16.0.0/24 is subnetted, 4 subnets
D 172.16.200.0 [90/26905856] via 40.40.40.13, 00:00:16, Tunnel66 D 172.16.214.0 [90/26905600] via 40.40.40.13, 00:00:16, Tunnel66 D 172.16.215.0 [90/26905600] via 40.40.40.13, 00:00:16, Tunnel66 D 172.16.216.0 [90/26931200] via 40.40.40.13, 00:00:16, Tunnel66 D EX 192.168.0.0/16 [170/542771200] via 192.168.24.6, 03:11:05, Serial2/0 D 192.168.13.0/24 [90/34036062] via 192.168.24.6, 03:11:05, Serial2/0 D 192.168.15.0/24 [90/27417600] via 40.40.40.13, 00:00:16, Tunnel66 D 192.168.23.0/24 [90/44276062] via 192.168.24.6, 03:11:05, Serial2/0 D 192.168.25.0/24 [90/23796062] via 192.168.24.6, 03:11:05, Serial2/0 D 192.168.74.0/24 [90/34036062] via 192.168.24.6, 03:11:05, Serial2/0 D 192.168.76.0/24 [90/23796062] via 192.168.24.6, 03:11:05, Serial2/0
R24#traceroute 10.23.23.23 Type escape sequence to abort.
Tracing the route to 10.23.23.23
VRF info: (vrf in name/id, vrf out name/id) 1 40.40.40.23 37 msec 37 msec *
Incident 2 (1 points)
• Users that are located in VLAN100 of the IPexpert HQ office have lost access to the Server which is located in VLAN200.
• Isolate and fix the issues so R10 is reachable from R14 , the outputs should match the below:
R14#ping 172.16.200.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.200.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
R14#traceroute 172.16.200.2 num Type escape sequence to abort.
Tracing the route to 172.16.200.2
VRF info: (vrf in name/id, vrf out name/id) 1 172.16.100.1 1 msec 0 msec 0 msec 2 172.16.56.5 0 msec 0 msec 1 msec 3 172.16.200.2 0 msec * 0 msec
Incident 3 (2 points)
• ISP3 is trying to reach ISP2 network of 10.102.102.0 /24 but is unsuccessful.
• Isolate and fix the issues so that it is reachable from ISP3, the outputs should match the below:
ISP3#ping 10.102.102.102 Type escape sequence to abort.
Incident 4 (2 points)
• Starbucks Coffee branch-1 cannot communicate with Starbucks branch-2.
• Troubleshoot and fix the issues so that both sites have reachability.
• The outputs should match the below:
R16#ping 10.20.20.20 source lo0 Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.20.20.20, timeout is 2 seconds:
Packet sent with a source address of 10.16.16.16
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
R20#ping 10.16.16.16 so lo0 Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.16.16.16, timeout is 2 seconds:
Packet sent with a source address of 10.20.20.20
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Incident 5 (1 points)
• The Global Provider network engineer is having IPv6 connectivity issues between the Data Center and their DR site and cannot reach one of their IPv6 Management web sites.
• Fix the issue so that the following sequence of commands produces the same relevant result:
ISP3#ping www.global.com Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:50:50::50, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 25/28/30 ms
ISP3#telnet www.global.com 80
Translating "www.global.com"...domain server (255.255.255.255) Trying 2001:50:50::50, 80 ... Open
Date: Wed, 04 Feb 2015 11:01:43 GMT Server: cisco-IOS
Accept-Ranges: none
400 Bad Request
[Connection to www.global.com closed by foreign host]
Incident 6 (2 points)
• The NOC team has identified it has lost connectivity to the Global Provider DR Site.
• Isolate and fix the configuration such that the traffic can reach its destination as shown in the
output:
R2#sh ip route vrf ISP 221.50.0.50 Routing Table: ISP
Routing entry for 221.0.0.0/8, supernet Known via "bgp 7200", distance 20, metric 0 Tag 20001, type external
Last update from 123.10.1.6 00:07:20 ago Routing Descriptor Blocks:
* 123.10.1.6, from 123.10.1.6, 00:07:20 ago Route metric is 0, traffic share count is 1 AS Hops 1
Route tag 20001 MPLS label: none
R2#traceroute vrf ISP 221.50.0.50 num Type escape sequence to abort.
Tracing the route to 221.50.0.50
VRF info: (vrf in name/id, vrf out name/id) 1 123.10.1.6 9 msec
Incident 7 (3 points)
• ISP4 is trying to reach the internet ip address of 8.8.8.8 but is unsuccessful.
• Fix the issue so that the following sequence of commands produces the same relevant result:
R50#traceroute 192.168.44.1 source loopback1 Type escape sequence to abort.
Tracing the route to 192.168.44.1
VRF info: (vrf in name/id, vrf out name/id) 1 123.10.1.5 8 msec 9 msec 9 msec
2 123.10.82.8 [AS 10100] [MPLS: Labels 21/18 Exp 0] 26 msec 26 msec 26 msec 3 *
194.45.67.1 [AS 10100] [MPLS: Labels 17/18 Exp 0] 27 msec *
4 192.168.44.2 [AS 65505] [MPLS: Label 18 Exp 0] 17 msec 17 msec 17 msec 5 192.168.44.1 [AS 65505] 26 msec 26 msec *
ISP4#ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 27/28/30 ms
NOTE
This incident is dependent on Incident 6.
Incident 8 (2 points)
• Administrator users that are connected to the R5 router are not able to use tftp to download the configuration backup from BB1, which is located at the remote Office.
• Fix the problem so that the following tftp session is successful:
R5#copy tftp://192.1.1.2/startup-config null:
Accessing tftp://192.1.1.2/startup-config...
Loading startup-config from 192.1.1.2 (via Tunnel1): ! [OK - 2364 bytes]
2364 bytes copied in 0.110 secs (21491 bytes/sec)
NOTE
While resolving this issue, you are not allowed to create any new interface.
Incident 9 (1 points)
• Users traffic from the Starbucks Asia Pacific office must load balance traffic towards the 172.9.9.9 Server.
• Fix the issue so that BB3 can ping the server and we have the following output on SW2.
NOTE
You are not allowed to remove any configurations.
BB3#ping 172.9.9.9
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.9.9.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms SW2#sh ip route 172.9.9.9
Routing entry for 172.9.9.9/32
Known via "eigrp 400", distance 90, metric 307232, type internal Redistributing via eigrp 400
Last update from 172.17.12.1 on Vlan12, 00:00:02 ago Routing Descriptor Blocks:
* 172.17.218.2, from 172.17.218.2, 00:00:02 ago, via Vlan218 Route metric is 307232, traffic share count is 1
Total delay is 2001 microseconds, minimum bandwidth is 10000 Kbit Reliability 255/255, minimum MTU 1500 bytes
172.17.12.1, from 172.17.12.1, 00:00:02 ago, via Vlan12 Route metric is 307232, traffic share count is 1
Total delay is 2001 microseconds, minimum bandwidth is 10000 Kbit Reliability 255/255, minimum MTU 1500 bytes
Incident 10 (2 points)
• User BB3 is unable to reach the DNS server of 8.8.4.4 in the internet.
• Fix the issues so that we have reachability.
• The outputs should match the below:
BB3#ping 8.8.4.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.4.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/26/30 ms BB3#traceroute 8.8.4.4
Type escape sequence to abort.
Tracing the route to 8.8.4.4
VRF info: (vrf in name/id, vrf out name/id) 1 172.17.30.1 0 msec 2 msec 0 msec
2 172.17.217.2 0 msec 0 msec 1 msec 3 194.45.67.6 9 msec 8 msec 9 msec
4 194.45.67.10 [MPLS: Labels 23/32 Exp 0] 30 msec 28 msec 26 msec 5 194.45.67.2 [MPLS: Labels 23/32 Exp 0] 32 msec 24 msec 25 msec 6 123.10.1.5 [MPLS: Label 32 Exp 0] 18 msec 20 msec 14 msec 7 123.10.1.6 31 msec 26 msec *