You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on recent feedback from the field we probably made an error assuming multicast is allowed for VNFs on top of all private, and public cloud offerings.
Example for such an environment turned out to be AWS.
To be able to survive in those environments, but still be able to interwork with strict port security settings Netwatcher should not create host VTEPs with source-learning enabled.
Instead, Netwatchers of all hosts' should update the VTEPs' neighbour table based on the DanmEp API.
Other possible solution would be employing some proven techniques and protocols automating just that, e.g. BGP.
The text was updated successfully, but these errors were encountered:
Levovar
changed the title
Disable source learning aka. multicast flooding on Netwatcher created VxLANs
Disable source learning aka. multicast flooding on Netwatcher created VTEP interfaces
Oct 4, 2019
Based on recent feedback from the field we probably made an error assuming multicast is allowed for VNFs on top of all private, and public cloud offerings.
Example for such an environment turned out to be AWS.
To be able to survive in those environments, but still be able to interwork with strict port security settings Netwatcher should not create host VTEPs with source-learning enabled.
Instead, Netwatchers of all hosts' should update the VTEPs' neighbour table based on the DanmEp API.
Other possible solution would be employing some proven techniques and protocols automating just that, e.g. BGP.
The text was updated successfully, but these errors were encountered: