From: Sameh El Tawil (eltawil@free.fr)
Date: Sun Nov 14 2004 - 07:36:04 GMT-3
Hi Guys,
I have been pulling my hair out for 2 days now trying to make a (normally)
basic auto RP config work. I am trying to build the case where one RP is
chosen for the administrativly scoped addresses and another performs RP
function for all other muticast groups.
The problem I am facing is that the RP announcing the 239.0.0.0/8 range is not
installed in the mapping. Instead when I look at the mapping agent I find a
mapping for this range with a minus (-) sign bound to the global RP. I have
run several debugs, the RP announcements are all received at the mapping
agent. This announcement coming with a minus sign worries me... am I doing
something wrong with the access list used with the send-rp-announce statement
?? If anyone has encountered this behaviour before please help.
Enough talking now let me show you some output. The topology looks like this:
[R1 (rp for global scope)]---ethernet---[R2 (MA)]--ethernet--[R3]--serial--[R4
(RP for 239/8)]
The routing protocol is eigrp, sparse-dense-mode is used on all interfaces.
R1 config:
--------------
interface Loopback0
ip address 10.1.60.6 255.255.255.0
ip pim sparse-mode
!
ip pim send-rp-announce Loopback0 scope 64 group-list not_admin_scoped
interval 30
!
ip access-list standard not_admin_scoped
deny 239.0.0.0 0.255.255.255
permit 224.0.0.0 15.255.255.255
R2 config:
--------------
interface Loopback99
ip address 10.1.99.1 255.255.255.255
ip pim sparse-mode
!
ip pim send-rp-discovery Loopback99 scope 64
R4 config:
--------------
interface Loopback99
ip address 10.1.99.2 255.255.255.255
!
ip pim send-rp-announce Loopback99 scope 64 group-list admin_scoped interval
30
!
ip access-list standard admin_scoped
permit 239.0.0.0 0.255.255.255
!
Here is how the mapping appears (Output from R2):
---------------------------------------------------------------------------
PIM Group-to-RP Mappings
This system is an RP-mapping agent (Loopback99)
Group(s) 224.0.0.0/4
RP 10.1.60.6 (?), v2v1
Info source: 10.1.60.6 (?), elected via Auto-RP
Uptime: 00:36:34, expires: 00:01:24
Group(s) (-)239.0.0.0/8
RP 10.1.60.6 (?), v2v1
Info source: 10.1.60.6 (?), elected via Auto-RP
Uptime: 00:36:34, expires: 00:01:25
Here is a "debug ip pim auto-rp" on R2 showing annpuncements being received
from both R1 and R4:
-----------------------------------------------------------------------------
------------------------------------------------------------------
2514#debug ip pim auto
PIM Auto-RP debugging is on
2514#
*Mar 1 01:46:25: Auto-RP: Build RP-Discovery packet
*Mar 1 01:46:25: Auto-RP: Build mapping (224.0.0.0/4, RP:10.1.60.6), PIMv2
v1,
*Mar 1 01:46:25: Auto-RP: Build mapping (-239.0.0.0/8, RP:10.1.60.6), PIMv2
v1.
*Mar 1 01:46:25: Auto-RP: Send RP-discovery packet on Ethernet0 (1 RP
entries)
*Mar 1 01:46:25: Auto-RP: Send RP-discovery packet on Ethernet1 (1 RP
entries)
*Mar 1 01:46:25: Auto-RP: Send RP-discovery packet on Loopback99 (1 RP
entries)
*Mar 1 01:46:25: Auto-RP: Received RP-discovery, from ourselves (10.1.99.1),
ignored
*Mar 1 01:46:25: Auto-RP: Received RP-discovery, from ourselves (10.1.99.1),
ignored
2514#
*Mar 1 01:46:26: Auto-RP: Received RP-announce, from 10.1.99.2, RP_cnt 1, ht
91
*Mar 1 01:46:26: Auto-RP: Received RP-announce, from 10.1.99.2, RP_cnt 1, ht
91
*Mar 1 01:46:26: Auto-RP: Received RP-announce, from 10.1.99.2, RP_cnt 1, ht
91
*Mar 1 01:46:26: Auto-RP: Received RP-announce, from 10.1.99.2, RP_cnt 1, ht
91
2514#
2514#
2514#un all
All possible debugging has been turned off
2514#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP-mapping agent (Loopback99)
Group(s) 224.0.0.0/4
RP 10.1.60.6 (?), v2v1
Info source: 10.1.60.6 (?), elected via Auto-RP
Uptime: 00:02:33, expires: 00:01:24
Group(s) (-)239.0.0.0/8
RP 10.1.60.6 (?), v2v1
Info source: 10.1.60.6 (?), elected via Auto-RP
Uptime: 00:02:34, expires: 00:01:24
2514#
Best Reagrds,
Sameh
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:43 GMT-3