Lab Minutes Forum

Technical Discussion => Routing and Switching => Topic started by: MC on November 20, 2013, 10:00:54 AM

Title: Device Tracking Issue on Catalyst Switches 15.2(1)E
Post by: MC on November 20, 2013, 10:00:54 AM
I ran into issue where a switch complains about seeing duplicate source IP 0.0.0.0 in ARP probe packet.

2013 Nov 19 16:18:09.498218 arp: Src 0023.445f.dfgc/0.0.0.0 Dst 002a.23rf.fd2d/192.168.0.1

It turns out this is the behavior of Device tracking feature which gets enabled by default when upgrading to 15.2(1)E on most Catalyst switches (2960,3850,4500,4900 etc.). But if you try to disable device tracking, you get

Switch(config)#no ip device tracking       
% IP device tracking is disabled at the interface level by removing the relevant configs


This seems to be a known issue (bug) and the current workarounds are the followings. Depending on the switch model, hopefully one of the options should work for you.

On switch interface,
Option 1:  enter "ip device tracking probe delay 10"
Option 2:  enter "ip device tracking max 0"
Option 3:  enter "nmsp attach suppress"

Title: Re: Device Tracking Issue on Catalyst Switches 15.2(1)E
Post by: adecisco on November 20, 2013, 10:20:31 AM
Thanks for this useful information. I think it save lots of headaches during my ISE deployment if a switch came up with strange behavior.

Thank u MC.
Title: Re: Device Tracking Issue on Catalyst Switches 15.2(1)E
Post by: MC on November 20, 2013, 10:23:55 AM
Device tracking is actually needed on switch that is used for wired 802.1X with ISE so there is no need to disable the feature.
SimplePortal 2.3.7 © 2008-2024, SimplePortal