RE: Multicast over FR

From: Ramy Sisy (ramysisy@inspiredmaster.com)
Date: Wed Jul 09 2008 - 17:45:10 ART


I had same problem before. I recommend you to enabl ip pim sparse-mode over
lopback0 in R2.

Plus this link will give you some information about multicast over
Frame-relay
http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers
/frm_rlay.html

BEST REGARDS,

RAMY SISY, CCIE X 2 (SECURITY, ROUTING/SWITCHING)#17321, CCSI#30417
CCIE PROGRAM MANAGER

INSPIRED MASTER
                        INSPIRING CREATIVE THINKING ....

WWW.INSPIREDMASTER.COM
E. RAMYSISY@INSPIREDMASTER.COM

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
akyccie
Sent: Wednesday, July 09, 2008 9:45 AM
To: Marc La Porte; ccielab@groupstudy.com
Subject: Re: Multicast over FR

I try with Auto-RP but the result is same. I not still not able to ping igmp
group 224.1.1.1 from R2

Multicast interface (spare-mode) R1 (fa0/0, s1/0) R2 (fa0/1, s1/0) R3
(s1/0,
lo0)

=====
R1
=====
!
ip multicast-routing
!
interface FastEthernet0/0
 ip address 1.1.14.1 255.255.255.0
 ip pim sparse-mode
!
interface Serial1/0
 ip address 1.1.123.1 255.255.255.0
 ip pim sparse-mode
 encapsulation frame-relay
 ip ospf priority 0
 frame-relay map ip 1.1.123.1 103
 frame-relay map ip 1.1.123.2 103 broadcast
 frame-relay map ip 1.1.123.3 103 broadcast
 no frame-relay inverse-arp
!
R1#sh ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.1.1.1/32
  RP 1.1.3.3 (?), v2v1
    Info source: 1.1.3.3 (?), elected via Auto-RP
         Uptime: 00:43:30, expires: 00:00:14
Group(s) 224.2.2.2/32
  RP 1.1.3.3 (?), v2v1
    Info source: 1.1.3.3 (?), elected via Auto-RP
         Uptime: 00:43:48, expires: 00:00:13
R1#R2#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 1.1.123.2, 560 ms
Reply to request 0 from 1.1.123.2, 564 ms

=====
R2
=====
!
ip multicast-routing
!
interface FastEthernet0/1
 ip address 150.2.1.1 255.255.255.0
 ip pim sparse-mode
 ip igmp join-group 224.2.2.2
 ip igmp join-group 224.1.1.1
!
interface Serial1/0
 ip address 1.1.123.2 255.255.255.0
 ip pim nbma-mode
 ip pim sparse-mode
 encapsulation frame-relay
 frame-relay map ip 1.1.123.2 203
 frame-relay map ip 1.1.123.1 203 broadcast
 frame-relay map ip 1.1.123.3 203 broadcast
 no frame-relay inverse-arp
ip ospf priority 0
!
R2#sh ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.1.1.1/32
  RP 1.1.3.3 (?), v2v1
    Info source: 1.1.3.3 (?), elected via Auto-RP
         Uptime: 00:29:18, expires: 00:00:12
Group(s) 224.2.2.2/32
  RP 1.1.3.3 (?), v2v1
    Info source: 1.1.3.3 (?), elected via Auto-RP
         Uptime: 00:29:36, expires: 00:00:14
R2#

R2#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,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.2.2.2), 00:33:28/00:02:16, RP 1.1.3.3, flags: SJCL
  Incoming interface: Serial1/0, RPF nbr 1.1.123.3
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:33:28/00:02:16

(*, 224.1.1.1), 00:33:28/00:02:21, RP 1.1.3.3, flags: SJCL
  Incoming interface: Serial1/0, RPF nbr 1.1.123.3
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:33:28/00:02:21

(*, 224.0.1.39), 00:32:48/stopped, RP 0.0.0.0, flags: DP
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(1.1.3.3, 224.0.1.39), 00:02:16/00:00:43, flags: PT
  Incoming interface: Serial1/0, RPF nbr 1.1.123.3
  Outgoing interface list: Null

(*, 224.0.1.40), 00:33:33/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:33:33/00:02:09

(1.1.3.3, 224.0.1.40), 00:33:19/00:02:59, flags: LT
  Incoming interface: Serial1/0, RPF nbr 1.1.123.3
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:33:19/00:02:09

R2#ping 1.1.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/69/116 ms
R2#
R2#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
.
R2#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
.
R2#
R2#debug ip mpacket
IP multicast packets debugging is on
R2#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

*Mar 1 00:35:25.883: IP(0): s=1.1.2.2 (FastEthernet0/1) d=224.1.1.1 id=18,
ttl=254, prot=1, len=114(100), not RPF interface.
*Mar 1 01:19:36.387: IP(0): s=1.1.2.2 (FastEthernet0/1) d=224.1.1.1 id=35,
ttl=254, prot=1, len=114(100), not RPF interface.
*Mar 1 01:19:39.787: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3763, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:19:44.791: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3768, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:19:49.759: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3771, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:19:54.779: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3774, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:19:59.775: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3779, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:20:04.819: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3782, ttl=14, prot=17, len=54(54), mforward
*Mar 1 01:20:09.819: IP(0): s=1.1.3.3 (Serial1/0) d=224.0.1.40
(FastEthernet0/0) id=3786, ttl=14, prot=17, len=54(54), mforward

R2#

R2#ping 1.1.123.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 68/122/236 ms
R2#ping 1.1.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 80/140/240 ms
R2#

====
R3
===
!
ip multicast-routing
!
interface Loopback0
 ip address 1.1.3.3 255.255.255.0
 ip pim sparse-mode
 ip ospf network point-to-point
!!
interface Serial1/0
 ip address 1.1.123.3 255.255.255.0
 ip pim nbma-mode
 ip pim sparse-mode
 encapsulation frame-relay
 frame-relay map ip 1.1.123.2 302 broadcast
 frame-relay map ip 1.1.123.1 301 broadcast
 frame-relay map ip 1.1.123.3 301
 no frame-relay inverse-arp
!
ip pim send-rp-announce Loopback0 scope 16 group-list 10
ip pim send-rp-discovery Loopback0 scope 15 interval 5

R3#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 1.1.123.2, 304 ms
Reply to request 0 from 1.1.123.2, 304 ms
R3#

R3#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:

Reply to request 0 from 1.1.123.2, 252 ms
Reply to request 0 from 1.1.123.2, 252 ms
R3#

R3#ping 1.1.123.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/124/264 ms
R3#ping 1.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 92/172/312 ms

R3#ping 150.2.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 150.2.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/143/356 ms
R3#

---- Original Message -----
  From: Marc La Porte
  To: akyccie
  Cc: ccielab@groupstudy.com
  Sent: Tuesday, July 08, 2008 4:20 PM
  Subject: Re: Multicast over FR

  are you using static-RP or auto-RP? Is the frame-relay cloud one single
subnet? Are your Frame Relay mappings correct?

  On Tue, Jul 8, 2008 at 12:42 PM, akyccie <akyccie@gmail.com> wrote:

    I am having a issue with Multicast. There is a frame-realy could between
R1 R2
    and R3. R3 is hub here. configured the spare-mode on all the three
router
    including the ethernet port. R3 loopback is configured as RP and R3 is
also
    mapping agent. Question has asked to configure the join group 224.1.1.1
on
    ethernet port of R2 router.

    I am using the nbma mode on R3. I can ping 224.1.1.1 from R1 and R3 but
not
    able to ping from R2 itself. on R2 RP maping show correctly. What could
be
the
    issue here.

    Thanks

    _______________________________________________________________________
    Subscription information may be found at:
    http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:54 ART