Ticket #16

Ticket #16 is published under the CCIE Flyer. Click here for direct link.

Enjoy!

Ticket #15 - Repubished

I am reposting here Lab 15, which was published on ccieflyer.com. Next ticket, Ticket 16, which will be about IP services will be published on CCIEFlyer.com, then it will be republished here again. And so on for the next few Tickets.

Network diagram



IGP diagram



Lab

file


This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R1 is using v2 RIP broadcast. The network was configured with multicast-helper to transport the RIP broadcast over the multicast network to R6. However, R6 do not see R1's Lo route in its routing table. Find and fix the problem.


For the solution Click here

For more mini labs, have a look at the mini labs page.

Also have a look at the complete troubleshooting workbook.

Ticket #15

Ticket #15 is published under the CCIE Flyer. Click here for direct link.

Enjoy!

Ticket #14 - Repubished

I am reposting here Lab 14, which was published on ccieflyer.com. Next ticket, Ticket 15, which will be about multicast will be published on CCIEFlyer.com, then it will be republished here again. And so on for the next few Tickets.

Network diagram



BGP diagram



IGP diagram



Lab file


This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R1 can't telnet R6's Lo0. Find and fix the problem.

For the solution Click here

For more mini labs, have a look at the mini labs page.

Also have a look at the complete troubleshooting workbook.

Ticket #14

Ticket #14 is published under the CCIE Flyer. Click here for direct link.

Enjoy!

Ticket #13 - Republished

I am reposting here Lab 13, which was published on ccieflyer.com. Next ticket, Ticket 14, which will be about BGP, OSPF and telnet will be published on CCIEFlyer.com, then it will be republished here again. And so on for the next few Tickets.

Network diagram



BGP diagram



Lab file


This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R3 was configured to send to BB1 only routes originated in AS3. So only R3 can ping BB1 from its Lo0. However, its not working, as no router can ping BB1 from it's Lo0. Find and fix the problem.

For the solution Click here

For more mini labs, have a look at the mini labs page.

Also have a look at the complete troubleshooting workbook.

TS workbook dynamips files - BETA

If you are an owner of the TS workbook and want to use dynamips, please contact me offline to participate in the BETA.

Ticket #13

Ticket #13 is published under the CCIE Flyer. Click here for direct link.

Enjoy!

Ticket #12 - Republished

I am reposting here Lab 12, which was published on ccieflyer.com. Next ticket, Ticket 13, which will be about BGP, will be published on CCIEFlyer.com, then it will be republished here again. And so on for the next few Tickets.

Network diagram



IGP diagram




Lab file


This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R3, R1 and R5 can't ping R2's Lo0 IP address. Fix the problem without touching R1.

For the solution Click here

For more mini labs, have a look at the mini labs page.

Also have a look at the complete troubleshooting workbook.

Troubleshooting workbook promotion

I got some good news!

For a limited time, the troubleshooting workbook price is discounted to 200$.

You can purchase the workbook here.

Ticket #12

Ticket #12 is published under the CCIE Flyer. Click here for direct link.

Enjoy!

Ticket #11

Network diagram



IGP diagram



BGP diagram




Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R1 can’t ping R2’s Lo0 IP address. Fix the problem

For the solution Click here

For more mini labs, have a look at the mini labs page.

Also have a look at the complete troubleshooting workbook.

Back from vacation

I am back from a long vacation. Stay tuned for more mini trouble shooting labs...

Troubleshooting challenge lab solutions

Thank you all for participation in the Troubleshooting Challenge lab.

We hope that you not only enjoyed the lab, but also learned TS techniques and advance R&S topics.

Please have a look at our Troubleshooting workbook for more challenging TS labs. Remember that practicing TS, not only good for the TS section, but it also a great tool for sharpening your advance R&S config skills.

Narbik will announce the winners at the Micronics forum. Stay tuned...

For solutions click here or checkout the Micronics forum.

Please stay tuned to this blog for more TS mini labs and other TS/R&S related topic.

The TS challenge has ended

Thank you all for participating in the TS Challenge.

I hope that you have enjoyed the lab, and most important also learned in the process about TS and advance R&S topics.

If you want to dive deeper into CCIE R&S troubleshooting and advanaced CCIE R&S topics, you are welcomed to have a look at the TS workbook.

In the following days I’ll publish the list of winners and the solutions.

If you have any questions don’t hesitate to contact me.

TS Challenge update

There is still a good chance to win the TS challenge. Keep on the good work!

First winner

Congratulations to the first student to solve the TS Challenge lab.

Vladimir Michalec, you are the king of TS!

For the rest of you, keep going. It is solvable!

TS Challenge update

No students have provided a full solution for the TS Challenge. You still got a good chance to win a free TS and CCIE 2.0 workbook.

Some are close.

I have seen many solutions with PBR. PBR is essentially just a static route with policy. PBR is not allowed!

Keep on working!

TS Challenge is on

Network diagram


IGP diagram


BGP diagram



Higher resolution images can be found here:


Hi-Res images


Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The trouble tickets:


Terms:
The competition terms are not listed here. You can find them on CCIE Flyer and the attached files there.

Lab rules:
  • Configuration of static routes are NOT allowed
  • Configuration of default routes are NOT allowed
  • Adding and/or removing interfaces are NOT allowed
  • You are NOT allowed to change IP addresses
  • DO NOT look for BB4, its emulated by BB1
  • Do not use your keyboard to type any commands (Just kidding)

Lab Setup:
  • Load the initial configuration onto the routers from the initial­config directory
  • The “.NET” file is provided; please change the IOS to reflect yours.
  • Reload R5 after loading the initial config file
  • If you are new to dynamips/dynagen then have a look at the video tutorial

Ticket 1
R2 can’t ping R6’s Lo0 interface from it’s Lo0.

Ticket 2
R6 can NOT ping BB1’s Lo0, which is 21.21.21.21. You should fix this problem without changing R6’s routing table.

Ticket 3
R6 can’t ping R2’s F0/0. You should fix this problem using a single interface configuration command. DO NOT use a global config command to resolve this problem.

Ticket 4
R2 can NOT ping R5’s F0/0.

Ticket 5
R5 can NOT ping R4’s Lo0.

Ticket 6
R4 can NOT ping R1’s or R3’s Lo0.

Ticket 7
R6 is configured to join 239.6.6.6. R4 can NOT ping this group address. You should use an interface command on R4 to fix this problem.

Ticket 8
The following routes are sent from BB4 to R1: 24.24.24.24 /32, 24.24.24.1 /32, 24.24.24.2 /32 and 24.24.24.3 /32 R1 is configured with the following policy for routes coming from BB4:
  • R1 should be configured such that R5 does NOT advertise network 24.24.24.2 /32 to R6
  • R1 should filter network 24.24.24.1 /32 However, R5 does NOT see network 24.24.24.24 /32 and network 24.24.24.3 /32 that should have come from BB4.

Ticket 9
R6 can NOT ping 24.24.24.3. You should fix this problem without configuring BGP or any redistribution.

Ticket 10
R6 is configured to ONLY allow R2 to Telnet to BB1, R2 can NOT Telnet to BB1. You should fix this problem while keeping the policy.

Answers:


Send your complete answers to me: danshtr@gmail.com.

The answers should include a short explanation about the cause of the problem, how to fix it and final configs.

Solutions

:
For solutions click here.

TS Challenge is ready

TS Challenge lab is ready.

Be ready for an announcement any time today!

It’s a really nasty lab. You will love it!

Ticket #10

Network diagram



IGP diagram



Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R6 was configured to summarize R3's Lo30,Lo31,Lo32 and Lo33, so R4 would see only one summarized route for them.
However, R4 still sees all the routes.
Fix the problem while, making sure R6 sees all R3's routes.

For the solution Click here

Ticket #09

Network diagram



Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R1 can't telnet R3. Fix the problem without compromising security.

For the solution Click here

Ticket #08

Network diagram



IGP diagram



BGP diagram




Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R4 can't ping R5's Lo0 IP address. Configure R2 to fix the problem.

For the solution Click here

Ticket #07

Network diagram



IGP diagram



Lab file



This lab is using dynamips. Please follow the instructions found here about how to use the lab file.


Lab file


The problem:

R2 can't ping to R1's Lo0 IPv6 address from all of its interfaces. Fix the problem.

For the solution Click here

CCIE Flyer and the TS workbook

My beloved CCIE troubleshooting workbook was mentioned on the very interesting interview with Narbik on the CCIE Flyer. Read it here.

Quote:

Just finished our Troubleshooting labs, I partnered with a VERY GOOD FRIEND OF MINE CALLED Dan Shechter, what a gentleman, a Triple CCIE with unbelievable amount of knowledge. Together we wrote 10 Trouble Shooting Mock labs. We thought that each lab was going to take 5.5 hours to complete but they will take 8 hours each. But man O man, these labs are really GR8. They cover all aspect of CCIE R&S, and ALSO the NEW, YES the NEW “CCIE 2.0 Protocol specific Mock labs” hahahaha, these labs are really tough, I should put a warning and a disclaimer on the bottom of each page, guaranteed to frustrate the best of us.

Ticket #06 video solution

Click here for a video walkthrough of Ticket #6 solution.