CCIE R&S v5 Mock Lab 1 - Troubleshooting

Expand all



Contents

CCIE R&S v5 Mock Lab 1 - Troubleshooting

Last updated: July 1, 2015

Diagram

A video walkthrough of this lab is available in here in the CCIE RSv5 Lab Cram Session. Diagrams and initial configs for this lab are located under the Resources section on the righthand portion of this page.

Difficulty Rating (10 highest): 8

Lab Overview

  • Do not change the following configuration on any device:
    • Hostname
    • Enable password
    • Console or VTY configuration
  • Use the password of cisco for any authentication.
  • Points are awarded for finding and resolving faults in the topology. An inserted fault is an introduced break for a scenario that was previously working. Depending on the scenario, fixing inserted faults could require one or multiple command lines on the same or multiple devices.
  • The resolution of one incident MAY depend on the resolution of previous incident(s).The dependency will not be visible if incidents are resolved in sequence.
  • There are NO physical faults in the network.
  • Do not change any routing protocol boundaries. Refer to the provided diagram.
  • Do not add new interfaces or IP addresses.
  • Do not remove any feature configured to resolve a ticket; you must resolve the issue, rather than remove the configuration.
  • Do not remove or shut down any physical or logical interfaces.
  • Static default routes are NOT permitted unless preconfigured.
  • Routes to null0 that are generated as a result of a dynamic routing protocol solution are permitted.
  • Routers do not need to ping themselves when verifying reachability.
  • Tunneling and policyased routing is not permitted unless preconfigured.

Ticket 1

  • Server 1 (R20) is not able to ping R2's Loopback0.
  • Correct the issue and match the output below:

R20#ping vrf SERVER1 150.1.2.2
Type escape sequence to abort.
Sending 5, 100yte ICMP Echos to 150.1.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), roundrip min/avg/max = 1/1/3 ms

Score: 2 Points

Ticket 2

  • After the latest change window, Server 2 (R20) has lost access to the network.
  • Fix the network per the below output so that Server 2 can access network resources.
  • Do not configure static IP addresses on any device to solve this task.

R20#ping vrf SERVER2 172.31.215.15
Type escape sequence to abort.
Sending 5, 100yte ICMP Echos to 172.31.215.15, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), roundrip min/avg/max = 1/5/20 ms                           

Score: 2 Points

Ticket 3

  • Configure the network to match the output below.
  • Note that only the highlighted fields are relevant.
  • Do not change any OSPF area boundries to accomplish this task.

R15#traceroute 4.2.2.1
Type escape sequence to abort.
Tracing the route to 4.2.2.1
VRF info: (vrf in name/id, vrf out name/id)
  1 10.254.255.12 [AS 1000] [MPLS: Label 20 Exp 0] 3 msec 2 msec 7 msec
  2 10.254.255.8 [AS 1000] [MPLS: Label 20 Exp 0] 20 msec 20 msec 20 msec
  3 10.254.255.2 [AS 1000] 20 msec 11 msec 11 msec
  4 40.40.1.20 [AS 30000] 11 msec

Score: 2 Points

Ticket 4

  • R6 is not able to telnet to R5.
  • Resolve this problem so that you match the output below.
  • Ensure that the routing table size does not increase while solving this task.

R6#ssh -l cisco 150.1.5.5
Password: cisco

R5#exit

Score: 2 Points

Ticket 5

  • R16 is not able to reach R11's Loopback0 network.
  • Resolve this problem so that you match the output below.

R16#ping 2001::11 source 2001::16
Type escape sequence to abort.
Sending 5, 100yte ICMP Echos to 2001::11, timeout is 2 seconds:
Packet sent with a source address of 2001::16
!!!!!
Success rate is 100 percent (5/5), roundrip min/avg/max = 3/38/86 ms

Score: 2 Points

Ticket 6

  • R15 is unable to reach R1's Loopback0.
  • Fix the issue and match the output below.
  • Note that the hops on the traceroute do not have to be identical.

R15#traceroute 2001::1
Type escape sequence to abort.
Tracing the route to 2001::1

  1 2001:10:254:255::C 3 msec 1 msec 2 msec
  2 2001:10:254:255::8 1 msec 1 msec 1 msec
  3 2001:10:254:255::2 11 msec 15 msec 14 msec
  4 2001:40:40:1::20 14 msec 15 msec 14 msec
  5 2001:10:10:1::1 15 msec 14 msec 14 msec

Score: 3 Points

Ticket 7

  • Match the output below to ensure that R19 is able to reach the Internet host 4.2.2.1.
  • Do not remove any global configuration commands to accomplish this task.

R19#telnet 4.2.2.1 22 /source-interface loopback 0
Trying 4.2.2.1, 22 ... Open
SSH.99isco.25

[Connection to 4.2.2.1 closed by foreign host]

Score: 3 Points

Ticket 8

  • SW1 is unable to receive a multicast feed from SW2.
  • Fix the issue preventing the multicast stream, and match the output below.

SW2#ping                   
Protocol [ip]: 
Target IP address: 224.21.21.21           
Repeat count [1]: 10
Datagram size [100]: 
Timeout in seconds [2]: 
Extended commands [n]: y
Interface [All]: loopback0
Time to live [255]: 
Source address or interface: 
Type of service [0]: 
Set DF bit in IP header? [no]: 
Validate reply data? [no]: 
Data pattern [0xABCD]: 
Loose, Strict, Record, Timestamp, Verbose[none]: 
Sweep range of sizes [n]: 
Type escape sequence to abort.
Sending 100, 100yte ICMP Echos to 224.21.21.21, timeout is 2 seconds:

Reply to request 0 from 119.3.192.21, 17 ms
Reply to request 1 from 119.3.192.21, 1 ms
Reply to request 2 from 119.3.192.21, 1 ms
Reply to request 3 from 119.3.192.21, 1 ms
Reply to request 4 from 119.3.192.21, 1 ms

Score: 2 Points

Ticket 9

  • The Reno customer has opened a support ticket that their traffic to Site Blue 1 is not meeting the provider's SLA.
  • Fix the network and match the output below.
  • Note that the MPLS Label number does not need to match.

R9# traceroute 150.1.17.17
Type escape sequence to abort.
Tracing the route to 150.1.17.17
VRF info: (vrf in name/id, vrf out name/id)
  1 172.31.129.12 [AS 40000] 11 msec 1 msec 1 msec
  2 172.31.236.16 [AS 40000] [MPLS: Label 32 Exp 6] 5 msec 49 msec 107 msec
  3 172.31.236.23 [AS 40000] 58 msec 49 msec 48 msec
  4 192.168.237.17 [AS 40000] 90 msec *  6 msec

Score: 2 Points

Ticket 10

  • Match the output below to ensure that SW3 can reach R18 in 1 hop.

SW3#traceroute 150.1.18.18

Type escape sequence to abort.
Tracing the route to 150.1.18.18

  1 192.168.238.18 0 msec *  0 msec

Score: 2 Points

^ back to top