Cisco Bug: CSCus62432 - RP not treating itself as rp for remote source traffic.
Feb 11, 2018
- Cisco Nexus 7000 Series Switches
Known Affected Releases
Symptom: If the RP is rebooted, it's discarding PIM register messages from itself and the other PE: 2015 Jan 20 14:13:30.092655 pim:  (default-base) Received Register from 10.1.1.18 for (10.1.1.18/32, 126.96.36.199/32) 2015 Jan 20 14:13:30.092702 pim:  (default-base) We are not RP for group 188.8.131.52, message discarded Conditions: RP router reboot AND Customer has an interface configured with a primary AND secondary IP address, and the secondary address is used as the address called in the "ip pim rp-address" command. There is a bug in the code that if the secondary address is configured AFTER the rp info is created by PIM, PIM does not identify itself as the RP. It is possible during bootup that before IP component had a chance to configure the secondary address, PIM process reads the static RP configuration and then it receives the secondary address addition message and hence the bug.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases