From: zzk (ccie_99@yahoo.com)
Date: Wed Dec 17 2003 - 07:35:19 GMT-3
hi
It is not anycast RP problem, since we have disabled
the anycast RP but the problem remains.
The config are simple:
IP pim spare mode on all interfaces, and ip pim
rp-address 192.168.200.9 on all routers.
I realised now the problem is:
server
|
R1---------------------R2
| |
| |
Core 1 (RP)-----------Core 2
| |
link 1 link 2
| |
R3---------------------R4
| |
| |
SW1---------------------
|
|
client
when R3 is the DR for the client subnet vlan 202, if
link 1 is down, the multicast stops.
Vice Versa, if R4 is the DR for the subnet vlan 202,
if link 2 is down, the multicast stops.
When link 1 is down, if we force R4 to be the DR,
multicast will recover.
I suspect if link 1 is down, R4 should be the
multicast forwarder for Vlan 202 (but I did not see R4
has the mroute entry, dont understand, can someone
help to explain?), but R3 is still the dr of vlan 202.
Will this cause this problem?
below are the show IP mroute and show ip igmp group on
R3 and R4 when link 1 is down. (the multicast address
we use is 224.2.207.24 and my client ip is
152.226.116.5.
R3#sh ip igmp group
IGMP Connected Group Membership
Group Address Interface Uptime
Expires Last Reporter
239.255.255.250 Vlan202 15:05:42
00:02:27 152.226.116.5
224.2.207.24 Vlan202 15:02:06
00:02:27 152.226.116.5
224.0.1.40 Vlan203 16:35:32
00:02:37 152.226.116.67
R3#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, s - SSM Group, C -
Connected, L - Local,
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD,
State/Mode
(*, 224.2.207.24), 15:05:46/stopped, RP 192.168.200.9,
flags: SJC
Incoming interface: Port-channel2, RPF nbr
192.168.204.26, Partial-SC
Outgoing interface list:
Vlan202, Forward/Sparse, 15:02:06/00:02:27, H
(152.226.152.4, 224.2.207.24), 15:00:24/00:02:52,
flags: JT
Incoming interface: Port-channel2, RPF nbr
192.168.204.26, RPF-MFD
Outgoing interface list:
Vlan202, Forward/Sparse, 15:00:24/00:02:27, H
R4#sh ip igmp group
IGMP Connected Group Membership
Group Address Interface Uptime
Expires Last Reporter
239.255.255.250 Vlan202 15:05:57
00:02:13 152.226.116.5
224.2.207.24 Vlan202 15:02:21
00:02:13 152.226.116.5
224.0.1.40 Vlan203 16:35:47
00:02:22 152.226.116.67
R4#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, s - SSM Group, C -
Connected, L - Local,
P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set,
J - Join SPT, M - MSDP created entry, X - Proxy
Join Timer Running
A - Candidate for MSDP Advertisement, U - URD,
I - Received Source Specific Host Report
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD,
State/Mode
(*, 224.2.207.24), 15:06:00/00:02:13, RP
192.168.200.9, flags: SP
Incoming interface: Port-channel2, RPF nbr
192.168.204.30, RPF-MFD
Outgoing interface list: Null
--- "Jung, Jin" <jin.jung@lmco.com> wrote:
>
>
> Can you post your config and sh ip mroute?
>
>
>
> > Jin Jung CCIE#12368
> > Network Infrastructure Engineer
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of zzk
> Sent: Monday, December 15, 2003 9:10 AM
> To: Craig Dorry
> Cc: ccielab@groupstudy.com
> Subject: Re: ip mulitcast anycast rp problem
>
>
> The mroute shows the correct entries, i.e. R3's
> incoming interface is R4...
> They are all Cat6, so default is IGMP snooping.
>
> any other possibility?
>
> Btw, got another question even for the normal
> operation:
> When all the links are up, our NMS found the
> multicast
> traffics from R1 both reach Core 1 and R2.
> Show IP mroute shows, the traffics reach R2 and
> pruned
> by it.
> I feel the traffics only need to reach Core 1, but
> why
> it reaches R2 also?
>
> Thanks!
>
> --- Craig Dorry <chdorry@yahoo.com> wrote:
> > If the traffic is reaching R3, then the tree is
> > being
> > built correctly. Can you do a show ip mroute for
> > the
> > group on R3 and R4? Also, are you running IGMP or
> > CGMP on the L2 switch and R3/R4 (if CGMP)?
> >
> >
> >
> > --- zzk <ccie_99@yahoo.com> wrote:
> > > Hello
> > > Thanks for the suggestion. The commands are
> > already
> > > there. :(
> > > We followed the sample anycast RP config with
> > MSDP.
> > >
> > > Acutally, we noticed the multicast traffics
> reach
> > R3
> > > during the failover case, but it somehow did not
> > > reach
> > > the client on the layer 2 switch.
> > >
> > > Regards
> > >
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:42 GMT-3