To resolve this issue, disable Reverse Path Forwarding using REST API.
Note: RPF can be a desirable security feature filtering traffic that should not originate from certain networks, this should be taken into consideration before disabling it.
For example, the
<edge-ID> of the Edge in question is found on the Web User Interface (UI). The number of vNic interfaces to disable it depends on how many interfaces the Edge has. RPF can be re-enabled by running the same API again and replacing
=0 with
=1.
VMware vCloud Networking and Security 5.x:
PUT https://vShield_manager_IP/api/3.0/edges/<edge-ID>/systemcontrol/config<systemControl>
<property>sysctl.net.ipv4.conf.all.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_0.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_1.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_2.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_3.rp_filter=0</property>
</systemControl>HTTP Result Code: 204 NO CONTENT
VMware NSX for vSphere 6.x:
PUT https://NSX_mgr_IP/api/4.0/edges/<edge-ID>/systemcontrol/config
<systemControl>
<property>sysctl.net.ipv4.conf.all.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_0.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_1.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_2.rp_filter=0</property>
<property>sysctl.net.ipv4.conf.vNic_3.rp_filter=0</property>
</systemControl>
HTTP Result Code: 204 NO CONTENT
For more information on how to make API calls to the NSX Manager, see: