Hello All,
My question relates to IP PIM RP filtering and the resulting log entry:
PIM-6-INVALID_RP_JOIN ....
An example of a log buffer from one of my switches. You can see these reocurring logs slowly fill up my log buffer and syslog server:
Feb 20 10:01:26.009 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.127) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:02:04.026 EST: %PIM-1-INVALID_RP_REG: Received Register from 10.10.100.100 for 239.255.255.250, not willing to be RP
Feb 20 10:02:26.274 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 239.255.255.250) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:03:26.799 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 232.44.44.233) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:04:18.256 EST: %PIM-1-INVALID_RP_REG: Received Register from 10.10.100.100 for 239.255.255.253, not willing to be RP
Feb 20 10:04:34.856 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.22) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:05:37.105 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 239.192.83.80) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:06:18.338 EST: %PIM-1-INVALID_RP_REG: Received Register from 10.10.100.100 for 239.255.255.253, not willing to be RP
Feb 20 10:06:41.154 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:07:55.811 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 239.255.255.253) Join from 0.0.0.0 for invalid RP 10.10.10.10
Feb 20 10:08:55.860 EST: %PIM-6-INVALID_RP_JOIN: Received (*, 225.1.1.2) Join from 0.0.0.0 for invalid RP 10.10.10.10
My current configuration on the IP RP switch:
sh-sb-c02#sh run | i pim
ip pim sparse-mode
ip pim sparse-mode
ip pim rp-address 10.10.10.10 GOOD-MULTICAST-ACL
I understand the PIM RP filtering is creating these logs. I have verified the ACL used for filtering is accurate and I am getting the results I want. I have a very large network so going to each and every host that generates this multicast traffic and turn it off at the source is not an option. My question is whether there is a way to disable this logging?
Thanks
