From: ricky ong (longwaydown@live.com)
Date: Fri Sep 19 2008 - 05:51:34 ART
Hi Roberto,
I have reachibility for both the loopback on R4 and R5, i got the MSDP up but no SA exchange.. see the command output:
MSDP Peer 129.1.45.4 (?), AS 100 Connection status: State: Up, Resets: 0, Connection source: Ethernet0/1 (129.1.45.5) Uptime(Downtime): 00:08:35, Messages sent/received: 9/9 Output messages discarded: 0 Connection and counters cleared 00:09:02 ago SA Filtering: Input (S,G) filter: none, route-map: none Input RP filter: none, route-map: none Output (S,G) filter: none, route-map: none Output RP filter: none, route-map: none SA-Requests: Input filter: none Peer ttl threshold: 0 SAs learned from this peer: 0 Input queue size: 0, Output queue size: 0
As a result, R5 is not passing multicast to groups who registered to R4. I have tried to peer using the direct interface address but no luck still.
Hi Bogdan,
Did you get the MSDP working and sw2 is able to ping groups joined on R6 and registered with R4? You configured the same way as the solution does but still works with 2 RPs up at the same time?
Cheers,
Ricky
> From: Roberto.Clavero@TELINDUS.ES> To: bogdan.sass@catc.ro; longwaydown@live.com> CC: ccielab@groupstudy.com> Date: Fri, 19 Sep 2008 10:08:20 +0200> Subject: RE: iewb lab 12 Q6.3 anycast rp> > Hi,> From my experience you should to check If loopbacks are reachable from R4 and R5. An also, note that sometimes msdp is established but not working because the msdp id-originator is loopback by default. So I recommend to you change this source of msdp sessions to interfaces using the command ip msdp id-originator.> > Best regards,> Roberto> > -----Mensaje original-----> De: nobody@groupstudy.com [mailto:nobody@groupstudy.com] En nombre de Bogdan Sass> Enviado el: viernes, 19 de septiembre de 2008 8:43> Para: ricky ong> CC: ccielab@groupstudy.com> Asunto: Re: iewb lab 12 Q6.3 anycast rp> > ricky ong wrote:> > Hi all,> > I got some problems when working on IEWB VOL2 4.1 LAB 12 Q6.3. The question calls for anycast RP configuration. After configuring i realized that I can ping a mult!
icast group joined on R6 from SW2 (225.26.26.26). I got the MSDP peer up but it seems that multicast routing table is not exchanged between the two MSDP peer (R4, R5).> > I referred to the solution guide and was a bit surprised to find the below explanation:> >> > "When R4's lo is up, sw2 will not be able to ping 226.26.26.26 since the group is using R4 as RP and sw2 is using R5 as RP."> > Yes this is a problem, but isn't it the reason why MSDP is configured?> >> > "Now we will shutdown R4's lo which will mean R6 will use R5 as the RP "> > How can we provide RP redundancy then if multicast can not flow with two RP up at the same time?> >> >> I had the same "problem" while doing the lab. From what I read about> anycast RP, this is actually the normal, expected behavior (the> information about sources/clients is passed between the RPs via MSDP, so> any router can ping any multicast group).> > So I can only assume that the SG is wrong on this one.> > --> Bogdan Sass> CCAI,CCNP!
,CCSP,JNCIA-ER> Information Systems Security Professional> "Cu!
riosity
was framed - ignorance killed the cat"> > > Blogs and organic groups at http://www.ccie.net> > _______________________________________________________________________> Subscription information may be found at:> http://www.groupstudy.com/list/CCIELab.html> > > Blogs and organic groups at http://www.ccie.net> > _______________________________________________________________________> Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html> > > > > > >
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:18 ART