RE: Spoke-to-spoke multicast on multipoint FR

From: sameer khan <khanzadap_at_hotmail.com>
Date: Wed, 28 Mar 2012 12:21:02 +0000

Thanks for reply below is the config and show output
R2#ping 239.0.0.3
Type escape sequence to abort.Sending 1, 100-byte ICMP Echos to 239.0.0.3,
timeout is 2 seconds:
Reply to request 0 from 123.0.0.3, 168 msReply to request 0 from 123.0.0.3,
188 msR2#ping 239.0.0.3 rep 10
Type escape sequence to abort.Sending 10, 100-byte ICMP Echos to 239.0.0.3,
timeout is 2 seconds:
Reply to request 0 from 123.0.0.3, 156 ms.........R2#

R1(config-subif)#do s ip mrIP Multicast Routing TableFlags: 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, Z - Multicast Tunnel, z - MDT-data group sender, Y -
Joined MDT-data group, y - Sending to MDT-data groupOutgoing interface flags:
H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface
state: Interface, Next-Hop or VCD, State/Mode
(*, 239.0.0.3), 00:17:32/00:02:42, RP 1.1.1.1, flags: S Incoming interface:
Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial0/0.123, 123.0.0.3,
Forward/Sparse, 00:16:32/00:02:42
(2.2.2.2, 239.0.0.3), 00:01:31/00:01:34, flags: P Incoming interface:
Serial0/0.123, RPF nbr 123.0.0.2 Outgoing interface list: Null
(123.0.0.2, 239.0.0.3), 00:01:32/00:01:56, flags: PT Incoming interface:
Serial0/0.123, RPF nbr 123.0.0.2 Outgoing interface list: Null
(*, 224.0.1.40), 00:29:42/00:01:54, RP 0.0.0.0, flags: DCL Incoming
interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial0/0.123,
224.0.1.40, Forward/Sparse, 00:15:58/00:01:54
R1(config-subif)#

R2#s ip mrouteIP Multicast Routing TableFlags: 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,
Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data
group, y - Sending to MDT-data groupOutgoing interface flags: H - Hardware
switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface,
Next-Hop or VCD, State/Mode
(*, 239.0.0.3), 00:00:52/stopped, RP 1.1.1.1, flags: SPF Incoming interface:
Serial0/0.123, RPF nbr 123.0.0.1 Outgoing interface list: Null
(2.2.2.2, 239.0.0.3), 00:00:52/00:02:39, flags: PFT Incoming interface:
Loopback0, RPF nbr 0.0.0.0 Outgoing interface list: Null
(*, 224.0.1.40), 00:29:00/00:02:42, RP 0.0.0.0, flags: DCL Incoming
interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Loopback0,
Forward/Sparse, 00:29:02/00:02:41
R2#
R3#s ip mrouIP Multicast Routing TableFlags: 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,
Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data
group, y - Sending to MDT-data groupOutgoing interface flags: H - Hardware
switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface,
Next-Hop or VCD, State/Mode
(*, 239.0.0.3), 00:17:09/stopped, RP 1.1.1.1, flags: SJCL Incoming interface:
Serial0/0.123, RPF nbr 123.0.0.1 Outgoing interface list: Loopback0,
Forward/Sparse, 00:17:09/00:02:18
(2.2.2.2, 239.0.0.3), 00:01:07/00:02:04, flags: LJT Incoming interface:
Serial0/0.123, RPF nbr 123.0.0.2 Outgoing interface list: Loopback0,
Forward/Sparse, 00:01:07/00:02:18
(123.0.0.2, 239.0.0.3), 00:01:09/00:01:52, flags: LJT Incoming interface:
Serial0/0.123, RPF nbr 0.0.0.0 Outgoing interface list: Loopback0,
Forward/Sparse, 00:01:09/00:02:16
(*, 224.0.1.40), 00:29:07/00:02:19, RP 0.0.0.0, flags: DCL Incoming
interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Loopback0,
Forward/Sparse, 00:29:07/00:02:19
R3#

R2#ping 3.3.3.3
Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 3.3.3.3,
timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip
min/avg/max = 4/46/120 msR2#
R2#ping 1.1.1.1
Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.1,
timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip
min/avg/max = 4/44/80 msR2#
R2#s ip pi bsPIMv2 Bootstrap information BSR address: 1.1.1.1 (?) Uptime:
00:16:48, BSR Priority: 0, Hash mask length: 0 Expires: 00:01:34R2#
R3#s ip pi bsPIMv2 Bootstrap information BSR address: 1.1.1.1 (?) Uptime:
00:17:22, BSR Priority: 0, Hash mask length: 0 Expires: 00:02:02R3#

R2#s ip pi rp maPIM Group-to-RP Mappings
Group(s) 224.0.0.0/4 RP 1.1.1.1 (?), v2 Info source: 1.1.1.1 (?), via
bootstrap, priority 0, holdtime 150 Uptime: 00:15:29, expires:
00:01:33R2#
R3#s ip pi rp maPIM Group-to-RP Mappings
Group(s) 224.0.0.0/4 RP 1.1.1.1 (?), v2 Info source: 1.1.1.1 (?), via
bootstrap, priority 0, holdtime 150 Uptime: 00:15:45, expires:
00:02:19R3#

R2#s ip pi bsPIMv2 Bootstrap information BSR address: 1.1.1.1 (?) Uptime:
00:14:29, BSR Priority: 0, Hash mask length: 0 Expires: 00:01:52R2#
R3#s ip pi bsPIMv2 Bootstrap information BSR address: 1.1.1.1 (?) Uptime:
00:15:01, BSR Priority: 0, Hash mask length: 0 Expires: 00:01:20R3#
R3#ping 1.1.1.1
Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.1,
timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip
min/avg/max = 12/66/108 msR3#

############# R1 ######

interface Loopback0 ip address 1.1.1.1 255.255.255.0 ip pim
sparse-mode!interface Serial0/0 no ip address encapsulation frame-relay no ip
route-cache cef no ip route-cache clock rate 2000000!interface Serial0/0.123
multipoint ip address 123.0.0.1 255.255.255.0 ip pim dr-priority 100 ip pim
nbma-mode ip pim sparse-mode no ip route-cache no ip mroute-cache ip ospf
network broadcast ip ospf priority 100 snmp trap link-status frame-relay map
ip 123.0.0.2 102 broadcast frame-relay map ip 123.0.0.3 103 broadcast!ip pim
bsr-candidate Loopback0 0ip pim rp-candidate Loopback0

!router ospf 1 log-adjacency-changes network 0.0.0.0 255.255.255.255 area 0

############# R2 ######
interface Serial0/0 no ip address encapsulation frame-relay clock rate
2000000!interface Serial0/0.123 multipoint ip address 123.0.0.2 255.255.255.0
ip pim sparse-mode ip ospf network broadcast snmp trap link-status frame-relay
map ip 123.0.0.3 201 frame-relay map ip 123.0.0.1 201 broadcast!!router ospf 1
log-adjacency-changes network 0.0.0.0 255.255.255.255 area 0

############# R3 ######
interface Loopback0 ip address 3.3.3.3 255.255.255.0 ip pim sparse-mode ip
igmp join-group 239.0.0.3!interface FastEthernet0/0 no ip address shutdown
duplex auto speed auto!interface Serial0/0 no ip address encapsulation
frame-relay clock rate 2000000!interface Serial0/0.123 multipoint ip address
123.0.0.3 255.255.255.0 ip pim sparse-mode ip ospf network broadcast snmp trap
link-status frame-relay map ip 123.0.0.2 301 frame-relay map ip 123.0.0.1 301
broadcast

> CC: ccielab_at_groupstudy.com
> From: marco207p_at_gmail.com
> Subject: Re: Spoke-to-spoke multicast on multipoint FR
> Date: Wed, 28 Mar 2012 06:53:51 -0500
> To: khanzadap_at_hotmail.com
>
> Sameer, I do not believe that the nbma configuration is doing anything for
you in the bSR setup as the BSR multicast packets will have the rp-candidate
encapsulated inside the packets unlike auto-rp where the rp-announce is a
separate packet.
>
> Go to each spoke and run (sh ip pim rp mapping) to ensure you are seeing the
the correct RPs.
>
> Ensure you can ping the BSR ip address from your spokes. Multicast rides on
top of you IGP so ensure you have full reachability.
>
>
> Regards,
> Joe Sanchez
>
> On Mar 28, 2012, at 5:09 AM, sameer khan <khanzadap_at_hotmail.com> wrote:
>
> > hey guys
> >
> > I am trying to configure spoke-to-spoke multicast on multipoint FR. i
have
> > configured ip pim nbma on Hub but still not joy. For RP i am using BSR
> > configured on hub.
> > I can ping from hub-to-spoke but not spoke-to-spoke. can any one please
shed
> > some light on it
> >
> > thanks
> >
> >
> > 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
Received on Wed Mar 28 2012 - 12:21:02 ART

This archive was generated by hypermail 2.2.0 : Sun Apr 01 2012 - 07:56:52 ART