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.

Tags: troubleshooting, Multicast

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

Enjoy!

Tags: troubleshooting, Multicast

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.

Tags: IGP, BGP, Multicast

This is a video solution for ticket #04

This is my first video solution! I hope you will like it, and that it will help you troubleshoot better.

Please comment this video. This will help me to improve.

To watch this video, I recommend using the full screen view.

Tags: troubleshooting, video, Multicast