The entry "Traffic gets black-holed for up to 1 minute if a host changes IP within its L3VNI VPC subnet" in docs/known-limitations/known-limitations.md gives the window as up to 1 minute. That number is not a property of the defect, it is the result of the Fabric agent setting the drop-neighbor aging time to 60 seconds, which is the lowest value the platform accepts. Without that setting the platform default applies and the black-hole lasts up to 5 minutes.
The agent only began setting it in Fabric v0.126.0. A user running an earlier version who follows the current wording will measure roughly 5 minutes, conclude the documentation is wrong, and have no way to tell whether they are hitting the documented limitation or a different problem.
Proposed change to that section:
- state that up to 1 minute applies from the release that ships Fabric v0.126.0 onward, and that earlier releases see up to 5 minutes
- keep the existing diagnosis and the static DHCP lease workaround as they are
The entry "Traffic gets black-holed for up to 1 minute if a host changes IP within its L3VNI VPC subnet" in docs/known-limitations/known-limitations.md gives the window as up to 1 minute. That number is not a property of the defect, it is the result of the Fabric agent setting the drop-neighbor aging time to 60 seconds, which is the lowest value the platform accepts. Without that setting the platform default applies and the black-hole lasts up to 5 minutes.
The agent only began setting it in Fabric v0.126.0. A user running an earlier version who follows the current wording will measure roughly 5 minutes, conclude the documentation is wrong, and have no way to tell whether they are hitting the documented limitation or a different problem.
Proposed change to that section: