|
Description
|
Category
kernel
Sub-Category
io-multipath
Description
In a IPMP system, when a IGMP join request is send out. The IGMP join request version is default to V3. If a router only handle V2 IGMP request, no multicast
can be recieved. The system would not fall to IGMP V2 request, until it receives a IGMP querry from the router. It would than send all subsequent requests as IGMP V2 request.
When a failover occurs, a standby NIC take over traffic. The IGMP join requests revert back to IGMP V3. This again causes long delay before any multicast data can be received. The IGMP previous version should be used instead of the default when any NIC failover. When a failover occur and falls back to primary NIC, then it again revert to IGMP V3 as the default.
Frequency
Always
Regression
No
Steps to Reproduce
Set up a system with IPMP set and for 2 NICs to be in a multipath group.
Run a program to join a multicast group. Take note of the version that is be sent
out via snoop.
Cause a failover to occur on the primary and the standy NIC should start handle traffic. Have the program rejoin the multicast group and take note of the join version.
Expected Result
IGMP join version should be the version when the system 1st started on the primary
NIC. After the system discover the current router version when it receives IGMP querry, it should continue with this version even on NIC failover.
Actual Result
IGMP join version default back to V3 on every failover or even when you restart the application after a long rest period where the router has remove all IGMP membership from its table.
Error Message(s)
Test Case
Workaround
Submitter wants to work on bug
No
Additional configuration information
|
