From: Ivan Centeno (icenteno2001@yahoo.com)
Date: Wed Nov 27 2002 - 12:40:32 GMT-3
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 ----
> 10.1.2.113/24
> (source) \ /
> (member)
> RTC
>
> I have used Auto-RP for a multicast PIM-SM network.
> Both RTC (10.224.1.1) &
> RTB (10.224.1.2) are the candidate RPs, while RTD is
> the mapping agent
> (10.224.1.3). The entire multicast domain is
> advertised with OSPF.
>
> The multicast group traffic is 228.13.20.216
>
> question is:
>
> What I'm very confused is that why doesn't RTA gets
> a RP at all?? The
> interface command "ip pim sparse-mode" has been used
> on all interfaces for
> all the routers, including RTA.
>
> RTA#sh ip pim rp mapping
> PIM Group-to-RP Mappings
>
> RTA#
>
>
> RTB#sh ip pim rp
> Group: 228.13.20.216, RP: 10.224.1.2, v2, v1, uptime
> 00:37:04, expires
> 00:03:26
>
> RTB#sh ip pim rp mapping
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
>
> Group(s) 224.0.0.0/4
> RP 10.224.1.2 (?), v2v1
> Info source: 10.224.1.3 (?), elected via Auto-RP
> Uptime: 00:33:07, expires: 00:02:37
> RTB#
>
> And RTC says the Group-to-RP mappings is not active,
> is this normal??
>
> RTC#sh ip pim rp
> RTC#
>
> RTC#sh ip pim rp mapping
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
>
> Group(s) 224.0.0.0/4
> RP 10.224.1.2 (?), v2v1
> Info source: 10.224.1.3 (?), elected via Auto-RP
> Uptime: 00:36:02, expires: 00:02:43
> RTC#
>
>
> RTD & RTE can see the RP fine (same output as RTB
> above).
>
> I have also attached the Multicast Forward tables
>
> RTA#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:03:14/00:02:59, RP 0.0.0.0,
> flags: DP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (10.1.1.88, 228.13.20.216), 00:03:14/00:02:38,
> flags: PT
> Incoming interface: Ethernet0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (*, 224.0.1.39), 00:37:32/00:02:59, RP 0.0.0.0,
> flags: DP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (10.224.1.1, 224.0.1.39), 00:02:33/00:00:26, flags:
> PT
> Incoming interface: Serial0, RPF nbr 10.2.2.2
> Outgoing interface list: Null
>
> (10.224.1.2, 224.0.1.39), 00:01:17/00:01:42, flags:
> PT
> Incoming interface: Serial1, RPF nbr 10.2.1.2
> Outgoing interface list: Null
>
> (*, 224.0.1.40), 00:38:13/00:00:00, RP 0.0.0.0,
> flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse, 00:32:46/00:00:15
>
> RTA#
>
>
> RTB#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:44:52/00:03:11, RP
> 10.224.1.2, flags: S
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/2, Forward/Sparse, 00:44:52/00:03:11
>
> (*, 224.0.1.39), 01:45:37/00:02:59, RP 0.0.0.0,
> flags: DP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (10.224.1.1, 224.0.1.39), 00:00:09/00:02:50, flags:
> PT
> Incoming interface: Serial1/0, RPF nbr 10.2.4.1
> Outgoing interface list: Null
>
> (10.224.1.2, 224.0.1.39), 00:02:53/00:00:06, flags:
> PT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (*, 224.0.1.40), 01:46:40/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, 01:46:40/00:02:15
>
> (10.224.1.3, 224.0.1.40), 00:45:11/00:02:53, flags:
> CLT
> Incoming interface: Serial1/0, RPF nbr 10.2.4.1
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:45:11/00:02:15
>
> RTB#
>
> RTC#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
>
> (*, 224.0.1.39), 00:59:41/00:02:59, RP 0.0.0.0,
> flags: DP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (10.224.1.1, 224.0.1.39), 00:01:58/00:01:01, flags:
> PT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:23:11 GMT-3