switch#sh run | inc trackin ip device tracking switch#This usually happens on Windows Vista, Windows 2008 and Windows 7 clients, when disconnecting and connecting again (or shut no shut on switch), after locking and unlocking, or logging off and then logging on. Reason behind this is that windows machines could send ARP packets at the same time the switch is probing for device status. Possible solutions are:
Solution 1 - Delay ip device tracking ARP probe for few seconds (you should have IOS version that supports this command).
Switch(config)# ip device tracking [probe {delay interval}]ARP packet will be sent few seconds after link-up, and it will not happen at same time when windows 7 clients send first ARP packets. For example:
switch(config)#ip device tracking probe delay 5
Solution 2 - Disable gratuitous ARP in Windows registry [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] Set ArpRetryCount (32-bit DWORD) to 0 If you decide to use second method, please be sure to manage duplicate address problem with some other controls on switches or elsewhere.
With device tracking probe delay we had really good results, and believe there is no need for registry tuning (and problem with it is that when new machine with default registry settings is connected, you will again get same duplicate IP address problem).
speaking about that issue on cisco support forums : https://supportforums.cisco.com/message/3765025
ReplyDeleteThis is the only post so far that appears to describe the issue I'm having on my network. It seemed to only appear after we started to deploy 3850s. I'm applying this config change to our 3850s in hopes that it will correct the issue.
ReplyDeleteBlaze, Did you find that this corrected the issue? When you applied the probe delay, was there any "hiccups" or other issues with the switch(es)?
DeleteThis comment has been removed by the author.
Delete