Re: Multicast issue

From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Fri Oct 27 2006 - 18:06:20 ART


it was said that in older versions of IOS RP would understand that it
was appointed to be an RP... in newer versions one seems to have to pot
static RP entry on RP itself

A.

Frank wrote:
> I found out, when i configure:
>
> ip pim rp-address 150.1.3.3
>
> on the RP this message will go away. Is this neccessary for SD mode
> with Auto-RP?
> I have never read about this. Although it does not seem to change
> anything.
>
> Thanks,
>
> Frank
>> Hi,
>>
>> im getting these messages. But i don't have any "ip pim accept-rp" or
>> ip pim accept-register" configured. These messages sould appear if
>> the RP does
>> not want to accept. R3 is the RP and R5 is the mapping agent.
>>
>> *Mar 12 04:49:24.203: %PIM-1-INVALID_RP_REG: Received Register from
>> router 176.1.35.5 for group 239.3.1.1, 150.1.3.3 not willing to be RP
>> *Mar 12 04:46:11.451: %PIM-6-INVALID_RP_JOIN: Received (*, 239.3.1.1)
>> Join from 176.1.35.5 for invalid RP 150.1.3.3
>>
>>
>> Rack1R3#sh ip pim rp map
>> PIM Group-to-RP Mappings
>> This system is an RP (Auto-RP)
>>
>> Rack1R3#s | inc ann
>> ip pim send-rp-announce Loopback0 scope 15 group-list 33 interval 5
>>
>> Rack1R3#sh access-lists 33
>> Standard IP access list 33
>> 10 permit 239.3.0.0, wildcard bits 0.0.255.255
>>
>> Rack1R5#s | inc disc
>> ip pim send-rp-discovery Loopback0 scope 16
>>
>> Can someone help out?
>>
>>
>> Frank
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:06 ART