IEOC - Internetwork Expert's Online Community

No problem for me i was just explaining why he does not need additional tunnels ...

Okay. We just need INE to make that correction so we dont have long threads like this for no reason ;)

Good Day, even after changing R1 to the MA, an issue still exist between the MA on R1 and the RP on SW2. It appear that R5 is not sending the traffic correctly between SW2 and R1. After clearing mroute on R5 it looks like it starts to function but times out on R1. Not sure why R5 doesn't pass the auto-rp traffic properly between R1 an SW2.

Thanks Rich

ths question (page 9) still says Configure R1 as the RP intead of R5.  At this stage r5 is the MA.  the picture IPV6Freely snapped is fromt he solution which seems to have beter wording.

Just a tip for INE editors.

Net_OG:

ths question (page 9) still says Configure R1 as the RP intead of R5.  At this stage r5 is the MA.  the picture IPV6Freely snapped is fromt he solution which seems to have beter wording.

 

Just a tip for INE editors.

 

Heh... I only ever used the solutions.

Hi Guys

Offcourse, what the part 1 of this question has asked is not what SG is providing however, R1 can easily preempt R5 as another MA if RP discovery messages are sent with a higher IP Address from R1. I used 155.1.146.1 and it preempted R5 (which was not disabled).

With the use of a tunnel b/w R1 and R3 with an mroute on R3 makes the Solution work and with me, it's working.

Scott is right, with a little bit of effort, things work after analysing the issue in depth.

Cheers

Regards

Muhammad

Again, the entire task worked just fine for me, without any "extra effort". The only issue I had was that the workbook was wrong.

We will review this task again. Based on our initial edit we agreed with some of the posters that the wording of the question was the actual issue.  But in order to do due dilligence to all involved in this thread we will attempt to "fast track" this and get our results to you guys as soon as we can. Our primary focus at the moment is to complete the Chapter One edits (which are almost complete).  We appreciate your patience and your invaluable input.

--The TechEdit Team

Sure. The only correction that needs to be made is the one that I have shown in this post: http://ieoc.com/forums/p/6439/30756.aspx#30756

I might be being thick here but my workbook shows the corrected wording and I still cannot get it to work. The solution guide shows the removal of the mapping agent from R5 so when you setup R1 it does not send out the group announcements.

I just went through this again.  Pulled down fresh configs (DLCI mapping were missing on sub-ints) & guide, and went step by step.   I'm not seeing the RP announce traffic go across my frame relay interface.    Putting up tunnels works; but causes issue with task 8.16.

I am at this task, and I have about had it with this entire Multicast section.  I find the majority of the multicast task's to be "jacked up" in some fashion.

INE really needs to redo this entire section in my opinion.

PinGorilla,

I assure you that we verified everyone of these labs on gradelabs equipment and were able to reproduce the details provided in the solution guide.  I personally just verified each lab up to 8.15 in order to try to make sure an error wasn't introduced during any of the subsequent revisions.

Many of the labs had issues and those where corrected in the initial revison of this chapter. The solutions in the workbook were copied and pasted from the routers themselves, only the ip addressess where changed so that each would show command and addresses referencing Rack1.

If you would care to provide us with some constructive input we will do what we can to help you.

"Jacked up" conveys your frustration, and we are here to help, but its not empirically helpful.

--The TechEdit Team

Yup, agreed. This task worked just fine once I realized that "r1" and "r3" were backwards in the instructions in the solutions section. Assuming that mistake was fixed, this task worked exactly as specified. If it didn't, then you messed up in an earlier task somewhere.