ip device tracking issues

[elite2010]

Hi,

I have issues like duplicate ip address due to ip device tracking enabled .

I follwed the below document 

http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-problemsolution-product-00.html

ip device tracking probe delay 10

I tried to configure " 

ip device tracking probe auto-source fallback <host-ip> <mask> [override]

But the command does not work in 3850 switches . 

Now I dont have the duplicae  issue after enabling but it is giving another issue 

The current issue in microsoft dhcp server marking bad_address and the ip cannot be used  

for example the if the host ip address 10.10.10.100 , microsft dhcp server marks this ip address as bad_address and cannot be used 

I checked the client's  eventlog and found the below event

" Your computer has detected that the IP address 0.0.0.0 for the Network Card with network address 0xD9DCC91F41ED is already in use on the network. Your computer will automatically attempt to obtain a different address. " 

Thanks

[Georg Pauwen]

Hello,

I don't think the 3850 supports the solution described in the Cisco document.

Have you tried turning off gratuitous ARP on your Windows clients as described in the document below:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028373

[elite2010]

Hi,

The registry thing will be fine with microsoft , I am facing problem in printers also 

Thanks

[elite2010]

Hi,

what this command do ,Is there any impact if i change default 30 seconds 

ip device tracking probe interval <seconds>

Thanks

[Georg Pauwen]

Hello,

there is no impact other than that the probe gets sent at a different interval. Just make sure that the interval value is not lower than the delay interval (all of those values can be seen by issuing the 'show ip device tracking all' command...

[elite2010]

Hi,

I was trying to understand

How this help "ip device tracking probe delay 10 " duplicate issue ,I mean how does it work

Thanks

[elite2010]

Hi,

The below from the link
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-problemsolution-product-00.html

" Another method that is used in order to resolve this issue involves a troubleshoot of the client in order to determine the reason that duplicate address detection occurs so late after the link comes online. "

In addition to probe-delay, the delay also resets when the switch detects a probe from the PC

let's say link moved to up state at 10:00:00

after 10 minute pc started duplicate detection , switch detects the probe from pc , the delay reset

So what will happen then ?

Thanks

[Kn1ghtR1d3rOfD00m]

I had the same problem. I remember I fixed by disabling globally. IPDT has some bug issues on some IOS, so its worthless to have it enabled.