From: Ivan Centeno (icenteno2001@yahoo.com)
Date: Thu Nov 28 2002 - 18:12:46 GMT-3
Hunt,
Fist the Guoqi answer is correct the problem was the
location of the mapping agent. I agree with the fact
about the location of the mapping agent in the center
of the topology.
I misread your original question and I thought It was
a sparse-dense topology. In this type of network I
have seen moment where the routers don't show a RP
because they have not any multicast member connected
or in the path. In order to check the membership you
need to do a show ip igmp interface or show ip igmp
group.
Again this was not the case. Ooops !. Sorry.
Ivan
--- Hunt Lee <huntl@webcentral.com.au> wrote:
> Hello Guoqi & Ivan,
>
> So is it fair enough to say that with Auto-RP's
> "sparse-mode", we must
> placed the "CR Mapping Agent" to the center of the
> network which is directly
> connected to all other PIM-SM routers, or the
> alternative is to use
> "sparse-dense-mode" instead of "sparse-mode".
>
> Hence, I believe that these are the only 2 ways to
> get RTA to find the RP,
> any thoughts anyone??
>
> Ivan:
> Can you please explain a bit more on how you would
> like me to "check the
> membership for RTA"... how do i do that??
>
> Anyway, here is the "mroute table" for RTD & RTE.
>
> RTD#sh 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, s - SSM
> Outgoing interface flags: H - Hardware switched
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD,
> State/Mode
>
> (*, 228.13.20.216), 00:46:34/00:02:19, RP
> 10.224.1.2, flags: SP
> Incoming interface: Serial0/1, RPF nbr 10.2.4.2
> Outgoing interface list: Null
>
> (*, 224.0.1.39), 00:47:30/00:00:00, RP 0.0.0.0,
> flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:47:30/00:02:22
> Serial0/0, Forward/Sparse, 00:47:30/00:00:29
> Serial0/1, Forward/Sparse, 00:47:30/00:00:29
>
> (10.224.1.1, 224.0.1.39), 00:46:29/00:02:29, flags:
> CLT
> Incoming interface: Serial0/0, RPF nbr 10.2.3.1
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:46:31/00:02:20
> Serial0/1, Forward/Sparse, 00:46:31/00:01:29
>
> (10.224.1.2, 224.0.1.39), 00:46:14/00:02:45, flags:
> CLT
> Incoming interface: Serial0/1, RPF nbr 10.2.4.2
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:46:14/00:02:20
> Serial0/0, Forward/Sparse, 00:46:14/00:01:46
>
> (*, 224.0.1.40), 00:47:32/00:00:00, RP 0.0.0.0,
> flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:47:32/00:02:21
>
> (10.224.1.3, 224.0.1.40), 00:46:31/00:02:32, flags:
> PCLT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> RTD#
>
> RTE#sh 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, s - SSM
> Outgoing interface flags: H - Hardware switched
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD,
> State/Mode
>
> (*, 228.13.20.216), 00:29:03/00:02:51, RP
> 10.224.1.2, flags: SJC
> Incoming interface: Serial0, RPF nbr 10.2.5.2
> Outgoing interface list:
> Ethernet0, Forward/Sparse, 00:29:03/00:02:52
>
> (*, 224.0.1.39), 01:46:34/00:02:59, RP 0.0.0.0,
> flags: DC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Ethernet0, Forward/Sparse, 01:46:31/00:02:46
>
> (10.224.1.2, 224.0.1.39), 00:02:47/00:00:12, flags:
> CT
> Incoming interface: Serial0, RPF nbr 10.2.5.2
> Outgoing interface list:
> Ethernet0, Forward/Sparse, 00:02:48/00:02:45
>
> (*, 224.0.1.40), 01:47:18/00:00:00, RP 0.0.0.0,
> flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Ethernet0, Forward/Sparse, 01:47:18/00:00:00
> Serial0, Forward/Sparse, 00:29:07/00:00:00
>
> (10.224.1.3, 224.0.1.40), 00:47:28/00:02:59, flags:
> CLT
> Incoming interface: Ethernet0, RPF nbr 10.1.2.1
> Outgoing interface list:
> Serial0, Forward/Sparse, 00:29:59/00:00:00
>
> RTE#
>
>
> Thanks in advance,
> Hunt
>
>
> -----Original Message-----
> From: Guoqi Cui [mailto:guoqicui@yahoo.com]
> Sent: Thursday, 28 November 2002 10:33 AM
> To: Ivan Centeno
> Cc: Hunt Lee
> Subject: Re: To all Multicast guru...
>
>
> Correct me if I am wrong.
>
>
> RTB, RTC and RTE can get the rp information because
> they are dirrectly connnected to RTD (the map
> agent).
>
> RTA is not. For RTA to get the rp information, it
> need to register to a rp to join group 224.0.1.40.
> this is the controdiction, because RTA does not know
> who is rp.
>
> If you configure pim sparse mode, the location of
> rp-candidate and rp map agent is important.
>
> pim sparse-dense mode does not have this problem.
>
>
>
>
> --- Ivan Centeno <icenteno2001@yahoo.com> wrote:
> > Hunt,
> >
> > I don't think I am a multicast guru but i am going
> > to
> > try:
> >
> > In other to need a RP a router needs to be or a
> > group
> > member, be in the path of the share tree with a
> leaf
> > being connect or in the path through it, or be in
> > the
> > path of the source of a group. ( That is what I
> > remember ).
> >
> > I think thatyour yor case the show command says
> the
> > share tree is RTB - RTD/RTE. Could you check the
> > membership through RTA ? The mroute says that
> there
> > is
> > a source but it is being pruned. Looks like RTA
> > doesn't know there is another member in the
> network.
> > Could you post the mroute of RTD and E?
> >
> > Ivan Centeno
> > CCIE #10746.
> >
> >
> > --- Hunt Lee <huntl@webcentral.com.au> wrote:
> > > Hi folks, question for you...
> > >
> > > this is the topology:
> > >
> > >
> > > RTB --------- RTE
> > > / \ \
> > > 10.1.1.88/24 - RTA RTD ------- 2924 switch
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:23:12 GMT-3