From: zhuqingliu (zql@xxxxxxxxxx)
Date: Wed Jan 31 2001 - 22:18:58 GMT-3
Allyn,
Yes, The hub router has been configured with sparse-mode and nbma-mode on the f
rame relay interface. Here are the configurations for these routers.
/////////////////////////////////
!!!!! R3
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Serial0
ip address 137.20.100.35 255.255.255.224
ip pim sparse-mode
encapsulation frame-relay
ip ospf network broadcast
ip ospf priority 0
frame-relay map ip 137.20.100.33 305 broadcast
frame-relay map ip 137.20.100.34 305 broadcast
!
ip pim rp-address 137.20.64.5
/////////////////////////////////
!!!!! R2
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Ethernet0
ip address 137.20.64.5 255.255.240.0
ip accounting output-packets
ip pim sparse-mode
interface Serial0
no ip address
encapsulation frame-relay
clockrate 64000
frame-relay lmi-type ansi
!
interface Serial0.1 multipoint
ip address 137.20.100.34 255.255.255.224
ip pim nbma-mode
ip pim sparse-mode
ip ospf network broadcast
ip ospf priority 100
frame-relay map ip 137.20.100.33 501 broadcast
frame-relay map ip 137.20.100.35 503 broadcast
//////////
!!! r1
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Ethernet0
ip address 137.20.20.1 255.255.255.0
ip pim sparse-mode
ip igmp join-group 224.1.1.1
!
interface Serial0
ip address 137.20.100.33 255.255.255.224
ip pim sparse-mode
encapsulation frame-relay
ip ospf network broadcast
ip ospf priority 0
no fair-queue
clockrate 64000
frame-relay map ip 137.20.100.34 105 broadcast
frame-relay map ip 137.20.100.35 105 broadcast
!
ip pim rp-address 137.20.64.5
////////////////////////
The rp address is the ethernet address of r2.
Thanks.
Perry
----- Original Message -----
From: Allyn Baskerville <abaskerville@ibeam.com>
To: 'zhuqingliu' <zql@liming.com>
Sent: Thursday, February 01, 2001 1:06 AM
Subject: RE: IP multicast over framerelay
> You have to use sparse-mode PIM in conjunction with the pim nbma-mode on the
> frame interface. Have you done this? Allyn
>
> -----Original Message-----
> From: zhuqingliu [mailto:zql@liming.com]
> Sent: Wednesday, January 31, 2001 3:14 AM
> To: ccielab@groupstudy.com
> Subject: IP multicast over framerelay
>
>
> Hi, All,
>
> The following chart is the work arround.
>
> Join 224.1.1.1 RP
> r1---------------/--r2---------------r4
> F.R. /
> /
> /
> r3
> PIM sparse-mode
>
> r1 , r2 and r3 are connected with frame-relay and r2 is the hub. no
> sub-interface is used for r2.
> r1 join group 224.1.1.1
> r2 is the RP and pim nbma-mode configured for r2's frame-relay interface.
>
> The problem is that r3 can only ping 224.1.1.1 once in a while.
> ////////////////////////////////////////////////////////////////////////////
> ////////////////////////////
> 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 137.20.100.33, 156 ms
> 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:
> .
> 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:
> .
> r3#
> ////////////////////////////////////////////////////////////////////////////
> ////////////////////////////
>
> Thanks in advance.
>
> Perry
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:50 GMT-3