Discussion:
[c-nsp] vs ip device tracking on cisco3850
Arne Larsen / Region Nordjylland
2015-06-19 15:26:36 UTC
Permalink
Hi all.
Can someone help me out here
We have Cisco 3850 switches with ip device tracking enabled.
I looks like this tracking is sending out arp on behalf of hosts that are another switch.
This behaviour is making our surveillance video controller believe that there is an ip conflict because the arp is based on the controllers address.
I was of the assumption that device tracking was local on the switch, so I don't understand why the switch sends it out on trunk interface.
I'we tried to disable this tracking but without any luck.
The only thing that works is to remove the vlan that runs the video from the trunk towards the 3850.
All others switches in this setup is 3750v2 and 3560C

3850 --- 3850---|--3750-12g--|--3560-3560-video ctl
1 2 3 4 5
The arp is send from the number 2 3850 and is received on 5-3560 where the video ctl is connected.


/Arne
_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Lukas Tribus
2015-06-19 15:41:24 UTC
Permalink
Post by Arne Larsen / Region Nordjylland
Hi all.
Can someone help me out here
We have Cisco 3850 switches with ip device tracking enabled.
I looks like this tracking is sending out arp on behalf of hosts that are another switch.
I'we tried to disable this tracking but without any luck.
I have been troubleshooting a similar problem with IP device tracking on
a CAT4500 with SUP8. IDT was enabled by default and there was really
no way to properly disable it.

Upgrading to the XE3.6 train fixed all those issues for me.



Lukas


_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Tarko Tikan
2015-06-19 15:46:01 UTC
Permalink
hey,
Post by Lukas Tribus
I have been troubleshooting a similar problem with IP device tracking
on a CAT4500 with SUP8. IDT was enabled by default and there was
really no way to properly disable it.
AFAIR it was possible to disable it per interface, and thats not really
a solution. There was no global "no ip device tracking" knob.

It was indeed "fixed" later by code upgrade.
--
tarko
_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Christophe Fillot
2015-06-22 11:24:56 UTC
Permalink
Post by Tarko Tikan
hey,
Post by Lukas Tribus
I have been troubleshooting a similar problem with IP device tracking
on a CAT4500 with SUP8. IDT was enabled by default and there was
really no way to properly disable it.
AFAIR it was possible to disable it per interface, and thats not really
a solution. There was no global "no ip device tracking" knob.
We got a problem here with our IP cameras here (3750E involved), they
crashed because of the unicast ARP probes sent by the switches. We had
to disable IPDT on each interface with "ip device tracking maximum 0".


_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Loading...