Loading...
Loading...
Client roaming back to original Fabric Edge node while entry is on Stale state in Device-tracking can cause ARP reply drops
Host was initially connected to DIS-R-1 SISF entry on DIS-R-1 went from REACHABLE to STALE after sending ARP Probes. Client moved to DIS-R-2 Client moved back to DIS-R-1 when the entry was in STALE state. DIS-R-1 sent an ARP request which was responded by the client with an ARP reply. Since entry was on STALE state when the ARP reply was receive by DIS-R-1 the SISF incorrectly consumed that ARP reply thinking it was the ARP reply to its ARP probe packet, so it got processed by SISF and dropped, not forwarded to IP ARP module. Since SISF consumed the ARP reply it moved entry to REACHABLE State. A second ARP request was sent from DIS-R-1 and ARP reply was received and processed by IP ARP module recovering the traffic switch#sh device-tracking database vlanid 477 ... ARP 10.10.10.10 cccc.bbbb.f760 Po21 477 0005 11mn STALE try 0 493 s <<<
Trigger another ARP request from Fabric Edge will automatic recover the issue.
na
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.