Advanced networking settings like ReversePathFwdCheckPromisc and IGMPVersion do not work on the host after performing one of the following operations:
Impact related to ReversePathFwdCheckPromisc setting:
The user experiences an issue when migrating/powering on an edge VM on an affected ESXI host with edge bridging.
Notes:
More details about edge bridging with promiscuous mode and forged transmits, please see "Option 2b" in this document.
Configure an Edge VM for Bridging in Manager Mode
Impact related to IGMPVersion setting:
After configuring IGMP version 2, IGMP version 3 queries are still being sent.
List of networking settings impacted due to this issue:
Net.IGMPQueries
Net.IGMPQueryInterval
Net.IGMPRouterIP
Net.IGMPV3MaxSrcIPNum
Net.IGMPVersion
Net.MLDRouterIP
Net.MLDV2MaxSrcIPNum
Net.MLDVersion
Net.MaxRARPsPerInterval
Net.RARPAdvertisementDuration
Net.ReversePathFwdCheck
Net.ReversePathFwdCheckPromisc
Net.SendIGMPReportToUplink
Net.TeamPolicyUpDelay
Net.TeamingNUMAAware
VMware vSphere ESXi 7.0.x
VMware vSphere ESXi 8.0.x
Due to a bug, upon DVS upgrade or NSX uninstallation, the value configured in advanced networking setting is not read anymore by the DVS implementation.The issue is fixed in 7.0.3 P10 and 8.0.3.0 P05. ESX 7.0 and 8.0 releases prior to those releases are impacted.
The issue is being fixed in 7.0.3 P10 and 8.0.3.0 P05. ESX 7.0 and 8.0 releases prior to those releases are impacted.
Workaround:
1. Set the advanced setting via vCenter UI or esxcli as usual:
For ex:
#esxcli system settings advanced set -o /Net/ReversePathFwdCheckPromisc -i 1
#esxcli system settings advanced set -o /Net/IGMPVersion -i 2
2. In addition execute the below CLI:
#netdbg vswitch runtime set <config_option_name_without_Net._prefix> value
For ex:
#netdbg vswitch runtime set ReversePathFwdCheckPromisc 1
#netdbg vswitch runtime set IGMPVersion 2