networking protocol_error ai_generated partial

IGMP: Membership query timeout on interface eth0, group 239.0.0.1

ID: networking/multicast-igmp-query-timeout

Also available as: JSON · Markdown · 中文
85%Fix Rate
83%Confidence
1Evidence
2024-08-22First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
Linux 5.10+ active — — —
Cisco IOS 12.2 active — — —
Arista EOS 4.28 active — — —
Mellanox ONYX 3.6 active — — —

Root Cause

The IGMP querier (typically a router) stopped sending periodic membership queries, causing the multicast group to time out and traffic to stop being forwarded to receivers.

generic

中文

IGMP查询器（通常是路由器）停止发送周期性成员查询，导致多播组超时，流量停止转发到接收者。

Official Documentation

https://datatracker.ietf.org/doc/html/rfc2236

Workarounds

  1. 90% success Restart the IGMP querier process on the router: on Cisco, 'no ip igmp snooping querier' followed by 'ip igmp snooping querier 10.0.0.1' 
    Restart the IGMP querier process on the router: on Cisco, 'no ip igmp snooping querier' followed by 'ip igmp snooping querier 10.0.0.1'
  2. 80% success Manually send an IGMP membership report from the receiver using a tool like 'igmpjoin' to rejoin the group: igmpjoin -i eth0 -g 239.0.0.1 
    Manually send an IGMP membership report from the receiver using a tool like 'igmpjoin' to rejoin the group: igmpjoin -i eth0 -g 239.0.0.1

中文步骤

  1. Restart the IGMP querier process on the router: on Cisco, 'no ip igmp snooping querier' followed by 'ip igmp snooping querier 10.0.0.1'
  2. Manually send an IGMP membership report from the receiver using a tool like 'igmpjoin' to rejoin the group: igmpjoin -i eth0 -g 239.0.0.1

Dead Ends

Common approaches that don't work:

  1. 85% fail

    If the querier is still not sending queries, the host will again time out after the group membership expires.

  2. 75% fail

    This delays the timeout but does not fix the root cause of missing queries from the querier.