Multicast - not willing to be IP

[manuscript1]

HI !

I do not have a fault but my logs are full of RP messages as follows - my objective is to get rid of these as they are annoying !!!! Any help be appreciated !

3641169: Jan 10 12:36:40.851 GMT: %PIM-1-INVALID_RP_REG: Received Register from router 10.128.90.165 for group 224.0.1.24, 10.128.100.10 not willing to be RP
3641170: Jan 10 12:37:34.243 GMT: %PIM-6-INVALID_RP_JOIN: Received (*, 235.80.68.83) Join from 10.128.90.165 for invalid RP 10.128.100.10

The 10.128.90.165 is a FWSM that has multicast routing enabled but no extra filtering  with some interfaces allowed pim-sparse where we want Kaspersky !

My config for PIM/Multicast is as follows - idea being to allow kasepersky multicast but not a lot else !  - vlan interfaces have IP PIM-sparse mode

ip pim rp-address 10.128.100.10 KaspMcast

ip access-list standard KaspMcast
 permit 239.255.76.65
 deny   any

interface Loopback1
 description "Multicast RP to support Kaspersky AV"
 ip address 10.128.100.10 255.255.255.255
 ip pim sparse-mode

CORE-1#sh ip pim rp mapping
PIM Group-to-RP Mappings

Acl: KaspMcast, Static
    RP: 10.128.100.10 (?)

[Richard Burts]

Try changing the mode from sparse to sparse-dense

ip pim sparse-dense-mode

Give it a try and let us know if the behavior changes.

HTH

Rick

[manuscript1]

Hi Richard

Im afraid i do not see relevence of changing the PIM-sparse to PIM-sparse-dense - the multicast is working - its only teh fact i am getting jregistration messages in te log due to my filter on treh multicast - its more about getting rid of these log messages to my "logging buffer " on teh switch itself - ive seen something called "logging discriminator " but its not clear to me how thsi would be applied to teh buffer log output when i show logiing on tthe switch

regarsd

[Richard Burts]

Is your multicast really working completely? It seems to me that part of the message says that the RP function is really not working

10.128.100.10 not willing to be RP

So why is 10.128.100.10 not willing to be RP as you configured it? If you read the documentation carefully it states that RP needs to operate in sparse-dense mode. That is why I made my suggestion. If 10.128.100.10 becomes willing to be RP then the log messages would stop.

HTH

Rick

[manuscript1]

Hi Rick

The reason it doesnt want to be is because it has the acl KaspMcast applied i assume ..?

If i remove thsi I am sure all will be fine ,,,, but that defeats whatever someone was trying to achieve by applying it ... why on earth we would want different RPS for possible future required multicast is beyond me !

I may try your suggestion as a alst resort but its pretty heavyweight considering im just trying to tidy logs

ta

.

[manuscript1]

I hav eresolved thsi using logging discriminator command ... just hides the logs i dont want to see...

[paul driver]

Hello
I guess is you since your using static RP then these host should not be trying to declare to be the RP - Do you auto-listerner enabled anywhere?

If applicable -- try an additional acl to negate these announcements on the interfaces you dont want them to be received

access-list 10 deny host 224.0.1.40
access-list 10 permit any

int x/x
ip multicast-boundary 10

res
paul

[manuscript1]

Thansk paul - i can try this and i see what it woyuld do - thank you

i have resolved thsi using the logging discriminator as below - although i know thsi is a fudge

logging discriminator RPrem mnemonics drops INVALID_RP
logging buffered discriminator RPrem

To be honest I dont know why we are actually stopping these multicasts coming through - the RP pushing them through is an asa so could resolve at that point if need be .

thanks again !