From: Yasser Aly (blackyeyes00@hotmail.com)
Date: Thu May 27 2004 - 22:09:52 GMT-3
Hi Sergio,
R1 is the mapping agent.
R3 is Auto RP for 239.0.0.0
R5 is Auto RP for 226.0.0.0 --> 238.0.0.0
Required to configure announce-filter in R1 with min number of lines in the
ACL.
Configuration:
========
R1:
===
ip pim send-rp-discovery Loopback0 scope 16
ip pim rp-announce-filter rp-list 3 group-list 33
ip pim rp-announce-filter rp-list 5 group-list 55
access-list 3 permit 150.1.3.3
access-list 5 permit 150.1.5.5
access-list 33 permit 239.0.0.0 0.255.255.255
access-list 55 deny 239.0.0.0 0.255.255.255
access-list 55 permit 224.0.0.0 15.255.255.255
R3:
===
ip pim send-rp-announce Loopback0 scope 16 group-list 17
access-list 17 permit 239.0.0.0 0.255.255.255
R5:
===
ip pim send-rp-announce Loopback0 scope 16 group-list 17
access-list 17 deny 224.0.0.0 1.255.255.255
access-list 17 deny 239.0.0.0 0.255.255.255
access-list 17 permit 224.0.0.0 15.255.255.255
Debug Output:
==========
R1:
===
Rack1R1#debug ip pim auto
Rack1R1#debug ip pim auto-rp
PIM Auto-RP debugging is on
Rack1R1#
*Mar 1 07:03:08.703: Auto-RP(0): Build RP-Discovery packet
*Mar 1 07:03:08.703: Auto-RP: Build mapping (-224.0.0.0/7, RP:150.1.5.5),
PIMv2 v1,
*Mar 1 07:03:08.703: Auto-RP: Build mapping (224.0.0.0/4, RP:150.1.5.5),
PIMv2 v1.
*Mar 1 07:03:08.703: Auto-RP: Build mapping (239.0.0.0/8, RP:150.1.3.3),
PIMv2 v1.
*Mar 1 07:03:08.703: Auto-RP(0): Send RP-discovery packet on
FastEthernet0/0 (2 RP entries)
*Mar 1 07:03:08.707: Auto-RP(0): Send RP-discovery packet on Serial0/0 (2
RP entries)
*Mar 1 07:03:08.707: Auto-RP: Send RP-discovery packet on Loopback0 (2 RP
entries)
Rack1R1#
*Mar 1 07:03:29.292: Auto-RP(0): Received RP-announce, from 150.1.3.3,
RP_cnt 1, ht 181
*Mar 1 07:03:29.296: Auto-RP(0): Update (239.0.0.0/8, RP:150.1.3.3), PIMv2
v1
*Mar 1 07:03:29.296: Auto-RP(0): Received RP-announce, from 150.1.3.3,
RP_cnt 1, ht 181
*Mar 1 07:03:29.296: Auto-RP(0): Update (239.0.0.0/8, RP:150.1.3.3), PIMv2
v1
Rack1R1#
*Mar 1 07:03:30.326: Auto-RP(0): Received RP-announce, from 150.1.5.5,
RP_cnt 1, ht 181
*Mar 1 07:03:30.326: Auto-RP(0): Update (-224.0.0.0/7, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:03:30.326: Auto-RP(0): Filtered -239.0.0.0/8 for RP 150.1.5.5
*Mar 1 07:03:30.326: Auto-RP(0): Update (224.0.0.0/4, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:03:30.330: Auto-RP(0): Received RP-announce, from 150.1.5.5,
RP_cnt 1, ht 181
*Mar 1 07:03:30.330: Auto-RP(0): Update (-224.0.0.0/7, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:03:30.330: Auto-RP(0): Filtered -239.0.0.0/8 for RP 150.1.5.5
*Mar 1 07:03:30.330: Auto-RP(0): Update (224.0.0.0/4, RP:150.1.5.5), PIMv2
v1
R3:
===
Rack1R3#debug ip pim auto-rp
PIM Auto-RP debugging is on
Rack1R3#
*Mar 1 07:03:36.548: Auto-RP(0): Received RP-discovery, from 150.1.1.1,
RP_cnt 2, ht 181
*Mar 1 07:03:36.548: Auto-RP(0): Update (-224.0.0.0/7, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:03:36.548: Auto-RP(0): Update (224.0.0.0/4, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:03:36.548: Auto-RP(0): Update (239.0.0.0/8, RP:150.1.3.3), PIMv2
v1
Rack1R3#
*Mar 1 07:03:57.090: Auto-RP(0): Build RP-Announce for 150.1.3.3, PIMv2/v1,
ttl 16, ht 181
*Mar 1 07:03:57.090: Auto-RP(0): Build announce entry for (239.0.0.0/8)
*Mar 1 07:03:57.090: Auto-RP(0): Send RP-Announce packet on Ethernet0/0
*Mar 1 07:03:57.094: Auto-RP(0): Send RP-Announce packet on Ethernet0/1
*Mar 1 07:03:57.094: Auto-RP(0): Send RP-Announce packet on Serial1/0
*Mar 1 07:03:57.094: Auto-RP(0): Send RP-Announce packet on Serial1/1
*Mar 1 07:03:57.098: Auto-RP: Send RP-Announce packet on Loopback0
R5:
===
Rack1R5#debug ip pim auto-rp
PIM Auto-RP debugging is on
Rack1R5#
*Mar 1 07:04:51.490: Auto-RP(0): Received RP-discovery, from 150.1.1.1,
RP_cnt 2, ht 181
*Mar 1 07:04:51.490: Auto-RP(0): Update (-224.0.0.0/7, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:04:51.490: Auto-RP(0): Update (224.0.0.0/4, RP:150.1.5.5), PIMv2
v1
*Mar 1 07:04:51.494: Auto-RP(0): Update (239.0.0.0/8, RP:150.1.3.3), PIMv2
v1
Rack1R5#
*Mar 1 07:05:13.014: Auto-RP(0): Build RP-Announce for 150.1.5.5, PIMv2/v1,
ttl 16, ht 181
*Mar 1 07:05:13.014: Auto-RP(0): Build announce entry for (-)(224.0.0.0/7)
*Mar 1 07:05:13.014: Auto-RP(0): Build announce entry for (-)(239.0.0.0/8)
*Mar 1 07:05:13.014: Auto-RP(0): Build announce entry for (224.0.0.0/4)
*Mar 1 07:05:13.014: Auto-RP(0): Send RP-Announce packet on Ethernet0/0
*Mar 1 07:05:13.014: Auto-RP(0): Send RP-Announce packet on Serial0/0
*Mar 1 07:05:13.014: Auto-RP(0): Send RP-Announce packet on Ethernet1/0
*Mar 1 07:05:13.018: Auto-RP: Send RP-Announce packet on Loopback0
>From: "Sergio Jimenez Arguedas" <sejimenez@its.co.cr>
>Reply-To: "Sergio Jimenez Arguedas"
<sejimenez@its.co.cr>
>To: <ccielab@groupstudy.com>
>Subject: Fw: "sh ip pim rp mapping " output
>Date: Thu, 27 May 2004 17:01:15 -0600
>
>Hi Yasser,
>
>It means that the RP is not the RP to the Group, but according the
>information, It doesn`t match!!!
>
>Could you send the "debug ip pim" information, and the config
please!!!
>
>
>Sergio
>
>
>
>----- Original Message -----
>From: "Yasser Aly" <blackyeyes00@hotmail.com>
>To: <ccielab@groupstudy.com>
>Sent: Thursday, May 27, 2004 4:32 PM
>Subject: "sh ip pim rp mapping " output
>
>
> > Dear All,
> >
> > R1 is supposed to be a mapping agent where
> > R3 is candidate RP for ( 239.0.0.0/8)
> > R5 is candidate RP for ( 226.0.0.0 --> 238.255.255.255 )
> >
> > Checking from the mapping agent, I would like to know what does
the (-)
>sign
> > that appear in the output below means ?
> >
> > Rack1R1# sh ip pim rp mapping
> > PIM Group-to-RP Mappings
> > This system is an RP-mapping agent (Loopback0)
> >
> > Group(s) (-)224.0.0.0/7
> > RP 150.1.5.5 (?), v2v1
> > Info source: 150.1.5.5 (?), elected via Auto-RP
> > Uptime: 00:53:36, expires: 00:02:19
> > Group(s) 224.0.0.0/4
> > RP 150.1.5.5 (?), v2v1
> > Info source: 150.1.5.5 (?), elected via Auto-RP
> > Uptime: 00:53:36, expires: 00:02:20
> > Group(s) 239.0.0.0/8
> > RP 150.1.3.3 (?), v2v1
> > Info source: 150.1.3.3 (?), elected via Auto-RP
> > Uptime: 00:53:37, expires: 00:02:20
> >
> > _________________________________________________________________
> > Tired of spam? Get advanced junk mail protection with MSN Premium
> >
>http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
> >
> >
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:18 GMT-3