PIM-SW1-6-INVALID_RP_JOIN Log entry

[killabee]

Ever since I configured PIM on some downstream switches I've been seeing these errors (names and IPs changed to protect the innocent):

Code Select Expand


Jan 25 20:24:03: %PIM-SW1-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join from 1.1.1.129 for invalid RP 2.198.2.2

I've googled this several times, but I either find myself going in circles over the description of the issue or find myself even more confused over the multicast terminology (I'm no multicast pro...I just copied a working config to get it up).

Here's a quick depiction of the topology:

Multicast_Sources -> Firewall -> L3_Switches -> Firewall -> L3_Switch -> Receivers

The multicast source delivers video streams to the receivers.  There's several L3 switches and firewalls between the sources and the receivers.  The video streams work fine, so this error is more of a nuisance than anything.  And now that I do a close stare and compare, I'm only seeing the log entries on two of the L3 switches, which appear to be the only two devices that have an ACL tied to the "ip pim rp-address" command.

The switches that are seeing this error are NOT the RPs and do NOT have the Multicast_Sources attached to them...they're just switches smack dab in the middle of the sources and the receivers. 

Here's some configuration that I think may be pertinent:

Code Select Expand


Switch8#sh run | include ip pim
ip pim rp-address 2.198.2.2 MCAST_ACL override
Switch8#

Switch8#sh ip access-list MCAST_ACL
Standard IP access list MCAST_ACL
    10 permit 224.100.10.0, wildcard bits 0.0.0.255
    20 permit 224.100.15.0, wildcard bits 0.0.0.255
    30 permit 224.100.175.0, wildcard bits 0.0.0.255
    40 permit 224.100.255.0, wildcard bits 0.0.0.255
    50 permit 224.100.249.0, wildcard bits 0.0.0.255 (1509638 matches)
    60 permit 224.101.24.0, wildcard bits 0.0.0.255 (72325 matches)
    70 permit 224.101.29.0, wildcard bits 0.0.0.255 (17096 matches)
    80 permit 224.101.59.0, wildcard bits 0.0.0.255 (3424176 matches)
    90 permit 224.101.60.0, wildcard bits 0.0.0.255
    100 permit 224.100.174.0, wildcard bits 0.0.0.255 (7543432 matches)
    110 permit 224.101.104.0, wildcard bits 0.0.0.255 (532 matches)
    120 permit 224.101.105.0, wildcard bits 0.0.0.255
    130 permit 224.100.120.0, wildcard bits 0.0.0.255 (1959875 matches)
Switch8#

Switch8#sh ip route 2.198.2.2
Routing entry for 2.198.0.0/16
  Known via "ospf 1", distance 110, metric 19, type extern 2, forward metric 5
  Last update from 3.3.3.1 on Port-channel10, 7w0d ago
  Routing Descriptor Blocks:
  * 3.3.3.1, from X.X.X.X, 7w0d ago, via Port-channel10
      Route metric is 19, traffic share count is 1

Switch8#sh run int po10
interface Port-channel10
description <MULTICAST SOURCES IN THIS DIRECTION>
no switchport
ip address 3.3.3.2 255.255.255.252
ip pim sparse-mode
end

Switch8#sh run int po1
interface Port-channel1
description <MULTICAST RECEIVERS IN THIS DIRECTION>
no switchport
ip address 1.1.1.130 255.255.255.252
ip pim sparse-mode
end

Switch8#sh ip pim neighbor
Neighbor          Interface                Uptime/Expires    Ver   DR
Address                                                            Prio/Mode
1.1.1.129    Port-channel1            15w0d/00:01:16    v2    1 / S P G
3.3.3.1       Port-channel10           12w4d/00:01:39    v2    1 / S P G
Switch8#


Please let me know if you need more information or better "show" commands.  As I said, the video stream is working fine...it's just these log entries (which occur very frequently) are bothering me.

Thanks for your help!

[that1guy15]

From the error it is saying that IP host 1.1.1.129 is trying to join the multicast tree for auto-rp (224.0.1.40) with an RP of 2.198.2.2. But from the error it looks like that RP does not have the RP role for that mcast address.

Auto-rp uses 224.0.1.40 and .39 to establish an RP and setup a shared tree. To support this each device needs to have "ip pim sparse-dense-mode" configured on all Mcast interfaces. Check the path end to end to make sure this is consistent. You might also see "ip pim sparse-mode" used along with "ip pim autorp listener" My guess is the misconfig is on the device with the error.

Or if you are using static RPs or no RPs (dense mode) then use "ip pim sparse-mode" or ip pim dense-mode" on the interfaces.

[wintermute000]

+1

that1guy15 you too have been slogging through the INE multicast labs I see God they are painful.

http://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/16450-mcastguide0.html

[that1guy15]

+1

that1guy15 you too have been slogging through the INE multicast labs I see God they are painful.

http://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/16450-mcastguide0.html

mid last year I did a 1 month deep-dive on multicast, almost 100 hours worth. Multicast is one of those topics that is dead simple once you get through the learning curve. INE material was great along with CiscoLive presentations. Oh and dont forget Developing IP Multicast Networks and Routing TCP/IP vol 2.