From: Bob Sinclair (bsin@cox.net)
Date: Sat May 08 2004 - 00:26:10 GMT-3
Mike,
Glad to see you have gotten a ping (amazing how hard we will work for a
couple exclamation marks!) We usually find it necessary to put PIM on the
joined interface - but it would be nice if it was consistent.
Bob Sinclair
CCIE #10427, CISSP, MCSE
www.netmasterclass.net
----- Original Message -----
From: "MMoniz" <ccie2002@tampabay.rr.com>
To: "Bob Sinclair" <bsin@cox.net>; "MMoniz" <ccie2002@tampabay.rr.com>;
<ccielab@groupstudy.com>
Sent: Friday, May 07, 2004 11:14 PM
Subject: RE: IP Multicast over FR!!!
> Strange, here is the mroute from R1, which responds. Putting the join on
the
> lo on R2 also worked as did the pim
> on R2 eth0
>
> But this shouldn't be necessary correct?
>
>
> R1#sho ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, 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.0.1.40), 3d10h/00:00:00, RP 133.5.5.5, flags: SJCL
> Incoming interface: Serial0, RPF nbr 133.5.12.2
> Outgoing interface list:
> Loopback0, Forward/Sparse, 2d11h/00:02:26
>
> (133.5.5.5, 224.0.1.40), 02:11:19/00:02:45, flags: CLJT
> Incoming interface: Serial0, RPF nbr 133.5.12.2
> Outgoing interface list:
> Loopback0, Forward/Sparse, 02:11:19/00:02:26
>
> (*, 224.64.64.10), 1d10h/00:00:00, RP 133.5.5.5, flags: SJPL
> Incoming interface: Serial0, RPF nbr 133.5.12.2
> Outgoing interface list: Null
>
> (133.5.5.5, 224.64.64.10), 00:00:55/00:02:45, flags: PLT
> Incoming interface: Serial0, RPF nbr 133.5.12.2
> Outgoing interface list: Null
>
> (133.5.52.5, 224.64.64.10), 00:00:55/00:02:45, flags: PLT
> Incoming interface: Serial0, RPF nbr 133.5.12.2
> Outgoing interface list: Null
>
> R1#
>
> R5#ping 224.64.64.10
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 224.64.64.10, timeout is 2 seconds:
>
> Reply to request 0 from 133.5.55.5, 8 ms
> Reply to request 0 from 133.5.12.1, 24 ms
> Reply to request 0 from 133.5.52.2, 20 ms <<<<<<R2
> Reply to request 0 from 133.5.12.1, 20 ms
> Reply to request 0 from 133.5.52.2, 16 ms
> Reply to request 0 from 133.5.235.4, 16 ms
> Reply to request 0 from 133.5.56.6, 12 ms
> Reply to request 0 from 133.5.235.3, 12 ms
> Reply to request 0 from 133.5.5.5, 12 ms
>
>
> R5#ping 133.5.22.2 <<<<<R2 eth int...So I know it is reachable
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 133.5.22.2, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms
> R5#
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Bob Sinclair
> Sent: Friday, May 07, 2004 10:44 PM
> To: MMoniz; ccielab@groupstudy.com
> Subject: Re: IP Multicast over FR!!!
>
>
> Mike,
>
> A couple of ideas.
>
> Compare the ip mroute on routers that are returning pings. Do they have
S,G
> for the group? Also, could you try puttin sparse mode on E0, also
perhaps
> try doing a join-group on a loopback of R2. Just casting around for ideas
> here.
>
> Bob Sinclair
> CCIE #10427, CISSP, MCSE
> www.netmasterclass.net
>
> ----- Original Message -----
> From: "MMoniz" <ccie2002@tampabay.rr.com>
> To: "Bob Sinclair" <bsin@cox.net>; "MMoniz" <ccie2002@tampabay.rr.com>;
> "Yasser Aly" <blackyeyes00@hotmail.com>; <sejimenez@its.co.cr>;
> <ccielab@groupstudy.com>
> Sent: Friday, May 07, 2004 10:20 PM
> Subject: RE: IP Multicast over FR!!!
>
>
> > Also, no I didn't put any pim commands on any of the interfaces with the
> > join
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Bob Sinclair
> > Sent: Friday, May 07, 2004 10:12 PM
> > To: MMoniz; Yasser Aly; sejimenez@its.co.cr; ccielab@groupstudy.com
> > Subject: Re: IP Multicast over FR!!!
> >
> >
> > Mike,
> >
> > Thanks for the output. It seems odd to me that you do not have an S,G
> entry
> > for the 224.64.64.10 group. Is it possible that you just missed it on
the
> > copy/paste?? I don't see how R1 is getting traffic through R2 if there
is
> > no S,G for that group on R2.
> >
> > On which interface of R2 did you put the join-group command for
> > 224.64.64.10? Since there is no C flag, I have to think that R2 is
> missing
> > the join-group command. If you did add a join-group command, did you
put
> > sparse mode on that interface?
> >
> > sorry to respond with more questions than answers!
> >
> >
> > Bob Sinclair
> > CCIE #10427, CISSP, MCSE
> > www.netmasterclass.net
> >
> > ----- Original Message -----
> > From: "MMoniz" <ccie2002@tampabay.rr.com>
> > To: "Bob Sinclair" <bsin@cox.net>; "MMoniz" <ccie2002@tampabay.rr.com>;
> > "Yasser Aly" <blackyeyes00@hotmail.com>; <sejimenez@its.co.cr>;
> > <ccielab@groupstudy.com>
> > Sent: Friday, May 07, 2004 9:39 PM
> > Subject: RE: IP Multicast over FR!!!
> >
> >
> > > Thanks Bob,
> > >
> > > R5 is both the RP and MA. Auto RP is being announced and R6 R1 respond
> > fine.
> > > I have static RP for the
> > > spokes, however, like I said after getting no results I put R2 on it's
> own
> > > sub int to R5
> > > and still the same results. Here is the output of what you asked.
> > >
> > > It makes no sense that R1 rssponds, which is connected to R2 but R2
> > doesn't.
> > >
> > > R2#sho ip mrout
> > > IP Multicast Routing Table
> > > Flags: D - Dense, S - Sparse, 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
> > > Outgoing interface flags: H - Hardware switched
> > > Timers: Uptime/Expires
> > > Interface state: Interface, Next-Hop or VCD, State/Mode
> > >
> > > (*, 224.0.1.39), 08:42:31/00:02:55, RP 133.5.5.5, flags: SJPC
> > > Incoming interface: Serial0, RPF nbr 133.5.52.5
> > > Outgoing interface list: Null
> > >
> > > (*, 224.0.1.40), 08:42:31/00:00:00, RP 133.5.5.5, flags: SJCL
> > > Incoming interface: Serial0, RPF nbr 133.5.52.5
> > > Outgoing interface list:
> > > Serial1, Forward/Sparse-Dense, 08:41:47/00:02:45
> > > Loopback0, Forward/Sparse, 08:42:31/00:02:57
> > >
> > > (133.5.5.5, 224.0.1.40), 08:41:46/00:02:50, flags: CLT
> > > Incoming interface: Serial0, RPF nbr 133.5.52.5
> > > Outgoing interface list:
> > > Loopback0, Forward/Sparse, 08:41:46/00:02:57
> > > Serial1, Forward/Sparse-Dense, 08:41:46/00:02:45
> > >
> > > (*, 224.64.64.10), 00:54:47/00:02:47, RP 133.5.5.5, flags: S
> > > Incoming interface: Serial0, RPF nbr 133.5.52.5
> > > Outgoing interface list:
> > > Serial1, Forward/Sparse-Dense, 00:51:22/00:02:47
> > >
> > > R2#
> > >
> > > R5#
> > >
> > > Reply to request 0 from 133.5.55.5, 8 ms
> > > Reply to request 0 from 133.5.12.1, 88 ms
> > > Reply to request 0 from 133.5.235.4, 88 ms
> > > Reply to request 0 from 133.5.56.6, 88 ms
> > > Reply to request 0 from 133.5.235.3, 84 ms
> > > Reply to request 0 from 133.5.12.1, 12 ms
> > > Reply to request 0 from 133.5.5.5, 8 ms
> > >
> > > R2#sho ip pim rp
> > > Group: 224.0.1.39, RP: 133.5.5.5, v1, uptime 08:43:23, expires
00:04:01
> > > Group: 224.0.1.40, RP: 133.5.5.5, v1, uptime 08:43:30, expires
00:04:01
> > > Group: 224.64.64.10, RP: 133.5.5.5, v2, v1, uptime 00:56:22, expires
> > > 00:03:39
> > > R2#
> > >
> > > R2#sho ip pim rp map
> > > PIM Group-to-RP Mappings
> > >
> > > Group(s) 224.0.0.0/4
> > > RP 133.5.5.5 (?), v2v1
> > > Info source: 133.5.5.5 (?), via Auto-RP
> > > Uptime: 08:44:19, expires: 00:02:45
> > > Group(s) 224.0.1.39/32
> > > RP 133.5.5.5 (?), v1
> > > Info source: local, via Auto-RP
> > > Uptime: 1d08h, expires: never
> > > Group(s) 224.0.1.40/32
> > > RP 133.5.5.5 (?), v1
> > > Info source: local, via Auto-RP
> > > Uptime: 1d08h, expires: never
> > > Group(s): 224.0.0.0/4, Static
> > > RP: 133.5.5.5 (?)
> > > R2#
> > > interface Ethernet0
> > > ip address 133.5.22.2 255.255.255.0
> > > ip igmp join-group 224.64.64.10
> > >
> > > ip pim rp-address 133.5.5.5
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Bob Sinclair [mailto:bsin@cox.net]
> > > Sent: Friday, May 07, 2004 9:16 PM
> > > To: MMoniz; Yasser Aly; sejimenez@its.co.cr; ccielab@groupstudy.com
> > > Subject: Re: IP Multicast over FR!!!
> > >
> > >
> > > Hi Mike,
> > >
> > > Sounds like an interesting problem. I have to think that the failure
of
> > R2
> > > to respond to the pings from R5 is a config or IOS issue. Can you
start
> > an
> > > extended ping to the group address on R5, then run a sh ip mroute on
R2?
> > > You should see a "C" flag on the *,G indicating a connected member.
> > >
> > > I have found that I can pretty reliably get sparse mode to work
through
> > the
> > > hub with nbma mode on the hub. In other words, I have seen successful
> > pings
> > > from spoke to spoke.
> > >
> > > Are you doing auto-rp? You could simplify by making sure mapping
agent
> > and
> > > candidate are both on R5, or you could do static to R5. BTW, on
recent
> > IOS
> > > I find that the static rp statement must also be on the RP itself.
> > >
> > > HTH,
> > >
> > > Bob Sinclair
> > > CCIE #10427, CISSP, MCSE
> > > www.netmasterclass.net
> > >
> > >
> > > ----- Original Message -----
> > > From: "MMoniz" <ccie2002@tampabay.rr.com>
> > > To: "Bob Sinclair" <bsin@cox.net>; "Yasser Aly"
> > <blackyeyes00@hotmail.com>;
> > > <sejimenez@its.co.cr>; <ccielab@groupstudy.com>
> > > Sent: Friday, May 07, 2004 8:42 PM
> > > Subject: RE: IP Multicast over FR!!!
> > >
> > >
> > > > Bob, you seem very knowledgeable in mcast... can you help with this
> > > scenario
> > > > I posted but got no response..
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > > >
> > > >
> > > > Here is the scenario. R5 is the hub and connects to R2, R3, R4 via
MP
> > > frame.
> > > > R5 also connects to R6 via PTP frame.
> > > >
> > > > Running PIM sparse on the MP link with nbma mode as well. Running SD
> to
> > > R6.
> > > > R5 is the RP and MA for all groups.
> > > >
> > > > R2 also has a PPP link to R1, running SD on that link.
> > > >
> > > > On ether int's on all routers I did join mcast group 224.64.64.10.
> > > >
> > > > When I ping the group from R5 all routers respond except R2. After
> > trying
> > > > and trying I decide to put R2 on it's own frame ptp link to R5.
Still
> > the
> > > > same results. R2 doesn't respond. R1 that is connected to R2
responds
> no
> > > > problem. When I ping from R2 I get response from R5 and R1.
> > > >
> > > > Also, when I ping from any Rtr connected to R5, like R3, R4, etc. I
> only
> > > get
> > > > response from R5. Is this normal mcast
> > > > behavior?
> > > >
> > > > Any ideas??
> > > >
> > > > mike
> > > >
> > > > R5#ping 224.64.64.10
> > > >
> > > > Type escape sequence to abort.
> > > > Sending 1, 100-byte ICMP Echos to 224.64.64.10, timeout is 2
seconds:
> > > >
> > > > Reply to request 0 from 133.5.55.5, 8 ms
> > > > Reply to request 0 from 133.5.12.1, 20 ms
> > > > Reply to request 0 from 133.5.12.1, 20 ms
> > > > Reply to request 0 from 133.5.56.6, 12 ms
> > > > Reply to request 0 from 133.5.235.4, 12 ms
> > > > Reply to request 0 from 133.5.235.3, 8 ms
> > > > Reply to request 0 from 133.5.5.5, 8 ms
> > > > R5#
> > > >
> > > > R6#ping 224.64.64.10
> > > >
> > > > Type escape sequence to abort.
> > > > Sending 1, 100-byte ICMP Echos to 224.64.64.10, timeout is 2
seconds:
> > > >
> > > > Reply to request 0 from 133.5.66.6, 4 ms
> > > > Reply to request 0 from 133.5.56.5, 24 ms
> > > > Reply to request 0 from 133.5.6.6, 4 ms
> > > > R6#
> > >
> > >
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:07 GMT-3