FW: IP Multicast - Auto -RP problems

From: Jason Cash (cash2001@swbell.net)
Date: Fri Jun 27 2003 - 14:35:55 GMT-3


OK, I have done that, but then I run into the problem that R4, R5 do not see
that auto-RP maps.

R6(s1/0)--------(s0/0)R4

            \-------(s0)R5

Also, the solution provided (which I don't rule out to be incorrect) does
not have R2 config's as an RP MA. The solution lists R1 as the RP MA as
well as C-RP. Is there any conflicts if there is multiple RP MAs?

  _____

From: Kissiedu, Felix [mailto:felix.kissiedu@cingular.com]
Sent: Friday, June 27, 2003 12:12 PM
To: 'Jason Cash'

R6 SHOULD KNOW THE MAPPING AGAENT IN ORDER TO GET RP INFORMATION. FROM WHAT
I SETT R6 HAS ONLY CONNECTIVITY TO R2 AND NOT R1 SO MAKE R2 THE MAPPING
AGENT.

-----Original Message-----
From: Jason Cash [mailto:cash2001@swbell.net]
Sent: Friday, June 27, 2003 12:58 PM
To: ccielab@groupstudy.com
Subject: IP Multicast - Auto -RP problems

I am working on multicast and having quite a few problems. Here is the
topo:

R1(e1)------(e0)R2(s0)----------(s1/0)R6

R1 is configured as a C-RP and the mapping agent:

interface Loopback0

 ip address 100.0.0.1 255.255.255.255

 ip pim sparse-dense-mode

!

interface Ethernet0

 description ethernet to BB1

 ip address 140.10.1.1 255.255.255.0

 ip pim sparse-dense-mode

!

interface Ethernet1

 description ethernet connected to R2

 ip address 140.10.12.1 255.255.255.0

 ip pim sparse-dense-mode

!

ip pim send-rp-announce Loopback0 scope 16 group-list 10

ip pim send-rp-discovery scope 16

R2 does not appear to be passing on the send-RP-discovery over the Frame
link to R6, but does have the auto-RP maps:

r2#sh ip pim rp map

PIM Group-to-RP Mappings

Group(s) 224.12.12.12/32

  RP 100.0.0.1 (?), v2v1

    Info source: 140.10.12.1 (?), via Auto-RP

         Uptime: 01:13:35, expires: 00:02:55

Group(s) 224.12.12.13/32

  RP 100.0.0.1 (?), v2v1

    Info source: 140.10.12.1 (?), via Auto-RP

         Uptime: 01:13:36, expires: 00:02:59

R6 sees R2 as a PIM neighbor, but will not map the auto-RP. I have tried to

set the FR interfaces to 'ip pim parse-mode' with 'ip pim nbma' and still no

luck:

r6#sh ip pim rp map

PIM Group-to-RP Mappings

r6#sh ip pim nei

PIM Neighbor Table

Neighbor Address Interface Uptime Expires Ver Mode

140.10.245.4 Serial1/0 01:02:44 00:01:32 v2

140.10.245.5 Serial1/0 01:02:44 00:01:30 v2

140.10.245.2 Serial1/0 01:02:44 00:01:33 v2

I am out of ideas and to top it off, the solutions do not have R2 or R6
configured as a mapping agent: below are the config for R2, R6:

R2:

interface Ethernet0

 description to R1 E0 (crossover)

 ip address 140.10.12.2 255.255.255.0

 ip pim sparse-dense-mode

!

interface Serial0

 ip address 140.10.245.2 255.255.255.0

 ip pim nbma-mode

 ip pim sparse-mode

 encapsulation frame-relay

 ip ospf network point-to-multipoint

 no fair-queue

 frame-relay map ip 140.10.245.2 106

 frame-relay map ip 140.10.245.4 106 broadcast

 frame-relay map ip 140.10.245.5 106 broadcast

 frame-relay map ip 140.10.245.6 106 broadcast

 no frame-relay inverse-arp

R6:

!

interface Serial1/0

 bandwidth 128

 ip address 140.10.245.6 255.255.255.0

 ip pim sparse-dense mode

 encapsulation frame-relay

 ip ospf network point-to-multipoint

 ip ospf priority 100

 no fair-queue

 serial restart-delay 0

 frame-relay map ip 140.10.245.2 601 broadcast

 frame-relay map ip 140.10.245.4 604 broadcast

 frame-relay map ip 140.10.245.5 605 broadcast

 frame-relay map ip 140.10.245.6 601

 no frame-relay inverse-arp

 frame-relay lmi-type cisco



This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:12 GMT-3