L2 is now in the TS section

L2 is now in the TS section of the R&S lab:

L2 is in our TS workbook from day one!

L2 is in the TS workbook from day one because the TS workbook was written not just to prepare the students for the TS section of the lab, but also to summarize, test and sharpen the skills of the CCIE R&S students.

Please notice that although the TS section is the first section of the lab, I recommend to practice the TS section after doing technology focused labs and moc labs. You will need all your networking skills to solve the labs in the TS workbook.

Enjoy your studies :)

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:

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 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 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: /32, /32, /32 and /32 R1 is configured with the following policy for routes coming from BB4:
  • R1 should be configured such that R5 does NOT advertise network /32 to R6
  • R1 should filter network /32 However, R5 does NOT see network /32 and network /32 that should have come from BB4.

Ticket 9
R6 can NOT ping 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.


Send your complete answers to me:

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


For solutions click here.