Loading...
Loading...
- Delay in the traffic. There is around 10-20 seconds gap in between when the multicast source starts sending traffic and when the receiver starts seen this traffic - First PIM Register shown as invalid/rejected/discarded/ignored in the RP logs followed by a valid one. After the valid one, multicast traffic starts working. Depending the platform, it is possible to see the reason of the invalid or discard to be with the value of IP total length.
- Multicast source inside ACI - Running 16.0.3e on the leaf where source is attached.
Downgrade to a previous version.
We see a delay in multicast traffic. After source starts sending traffic, takes around 10 to 20 seconds for the receiver to see this traffic. We are seeing messages in the RP stating PIM Register is invalid for first packet and then receives a valid RP and traffic starts working. The valid Register comes in after 10-20 seconds, causing the delay. Taking captures on the RP confirmed that the packet has an unexpected packet total length inside the IP header of the encapsulated UDP packet. Taking TCPdump on the Compute leaf, we see the UDP packet with correct total packet length in the IP header. Then we see the Register and in the encapsulated UDP packet, but the packet length is changed to a different number. This is a problem for paging systems like for example Informacast.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.