Discussion:
[c-nsp] ip device tracking on IOS-XE
Sebastian Beutel
2016-08-08 17:28:52 UTC
Permalink
Dear list,

we ran into trouble with the ip device tracking feature that seems to be
enabled by default on devices running ios-xe. There's allready a trouble
shooting guide:

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

As ip device tracking is disabled by default on most of our devices anyway
(those running ios) my first idea was to just disable it globaly. But even
though command line completion and online help knows about "no ip device
tracking <cr>" and a global line "ip device tracking" shows up in sho run
all, i get an error message saying: "IP device tracking is disabled at the
interface level by removing the relevant configs".

Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same error
message.

But it get's wilder: If i use one of the suggestions of the above link and
type a "ip device tracking probe delay 10" on just a single interface, the
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global line is
now changed and a "show ip device tracking all" reveals:

Global IP Device Tracking Probe Delay Interval = 10

Any ideas how that makes sense? How to disable device tracking globaly? For
what use device tracking could be beneficial anyway?

Best,
Sebastian.
_______________________________________________
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/
Nathan Lannine
2016-08-08 17:38:29 UTC
Permalink
Sebastian,
Post by Sebastian Beutel
Any ideas how that makes sense? How to disable device tracking globaly? For
what use device tracking could be beneficial anyway?
I agree it does not make sense to be unable to disable it, which I
believe you cannot. It is my understanding per the documentation that
device tracking is to assist with RADIUS CoA for Dot1X or something
like that.

I have nearly one hundred little switches on which this behavior was
relatively recently introduced and had to update our configs as
recommended because every once in awhile a Windows client would get an
IP conflict error.

Good luck,
Nathan
_______________________________________________
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/
Antoine Monnier
2016-08-09 07:24:55 UTC
Permalink
try this under every interface:
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)

or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)

On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems to be
enabled by default on devices running ios-xe. There's allready a trouble
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices anyway
(those running ios) my first idea was to just disable it globaly. But even
though command line completion and online help knows about "no ip device
tracking <cr>" and a global line "ip device tracking" shows up in sho run
all, i get an error message saying: "IP device tracking is disabled at the
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same error
message.
But it get's wilder: If i use one of the suggestions of the above link and
type a "ip device tracking probe delay 10" on just a single interface, the
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global line is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking globaly? For
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
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/
Sebastian Beutel
2016-08-09 16:50:28 UTC
Permalink
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what this
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to succeed
but actually does nothing at all: A "sho ip device tracking" makes clear,
that it's still running.

Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems to be
enabled by default on devices running ios-xe. There's allready a trouble
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices anyway
(those running ios) my first idea was to just disable it globaly. But even
though command line completion and online help knows about "no ip device
tracking <cr>" and a global line "ip device tracking" shows up in sho run
all, i get an error message saying: "IP device tracking is disabled at the
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same error
message.
But it get's wilder: If i use one of the suggestions of the above link and
type a "ip device tracking probe delay 10" on just a single interface, the
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global line is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking globaly? For
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Dipl.-Ing. Sebastian Beutel tel: +49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
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/
Pavel Skovajsa
2016-08-09 17:25:54 UTC
Permalink
In case it helps: TAC engineer advised us that a global command "no nmsp
enable" disables the IPDT on all the Cisco switches.

-pavel

On Tue, Aug 9, 2016 at 6:50 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what this
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to succeed
but actually does nothing at all: A "sho ip device tracking" makes clear,
that it's still running.
Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems
to
Post by Antoine Monnier
Post by Sebastian Beutel
be
enabled by default on devices running ios-xe. There's allready a
trouble
Post by Antoine Monnier
Post by Sebastian Beutel
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-
software/8021x/116529-
Post by Antoine Monnier
Post by Sebastian Beutel
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices
anyway
Post by Antoine Monnier
Post by Sebastian Beutel
(those running ios) my first idea was to just disable it globaly. But
even
Post by Antoine Monnier
Post by Sebastian Beutel
though command line completion and online help knows about "no ip
device
Post by Antoine Monnier
Post by Sebastian Beutel
tracking <cr>" and a global line "ip device tracking" shows up in sho
run
Post by Antoine Monnier
Post by Sebastian Beutel
all, i get an error message saying: "IP device tracking is disabled at
the
Post by Antoine Monnier
Post by Sebastian Beutel
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same
error
Post by Antoine Monnier
Post by Sebastian Beutel
message.
But it get's wilder: If i use one of the suggestions of the above link
and
Post by Antoine Monnier
Post by Sebastian Beutel
type a "ip device tracking probe delay 10" on just a single interface,
the
Post by Antoine Monnier
Post by Sebastian Beutel
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global
line
Post by Antoine Monnier
Post by Sebastian Beutel
is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking
globaly? For
Post by Antoine Monnier
Post by Sebastian Beutel
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
+49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
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/
Sebastian Beutel
2016-08-12 16:36:31 UTC
Permalink
Hi Pavel,
Post by Pavel Skovajsa
In case it helps: TAC engineer advised us that a global command "no nmsp
enable" disables the IPDT on all the Cisco switches.
Would that also disable the build in wireless controler of the 3850 (or at
least restrict it's usefulness)?

Best,
Sebastian.
Post by Pavel Skovajsa
On Tue, Aug 9, 2016 at 6:50 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what this
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to succeed
but actually does nothing at all: A "sho ip device tracking" makes clear,
that it's still running.
Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems
to
Post by Antoine Monnier
Post by Sebastian Beutel
be
enabled by default on devices running ios-xe. There's allready a
trouble
Post by Antoine Monnier
Post by Sebastian Beutel
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-
software/8021x/116529-
Post by Antoine Monnier
Post by Sebastian Beutel
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices
anyway
Post by Antoine Monnier
Post by Sebastian Beutel
(those running ios) my first idea was to just disable it globaly. But
even
Post by Antoine Monnier
Post by Sebastian Beutel
though command line completion and online help knows about "no ip
device
Post by Antoine Monnier
Post by Sebastian Beutel
tracking <cr>" and a global line "ip device tracking" shows up in sho
run
Post by Antoine Monnier
Post by Sebastian Beutel
all, i get an error message saying: "IP device tracking is disabled at
the
Post by Antoine Monnier
Post by Sebastian Beutel
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same
error
Post by Antoine Monnier
Post by Sebastian Beutel
message.
But it get's wilder: If i use one of the suggestions of the above link
and
Post by Antoine Monnier
Post by Sebastian Beutel
type a "ip device tracking probe delay 10" on just a single interface,
the
Post by Antoine Monnier
Post by Sebastian Beutel
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global
line
Post by Antoine Monnier
Post by Sebastian Beutel
is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking
globaly? For
Post by Antoine Monnier
Post by Sebastian Beutel
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Dipl.-Ing. Sebastian Beutel tel: +49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
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/
Antoine Monnier
2016-08-10 07:45:40 UTC
Permalink
"nmsp attachment suppress" came from googling, we implemented it and
verified it stopped device tracking for us.
which hardware are you working with?

On Tue, Aug 9, 2016 at 6:50 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what this
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to succeed
but actually does nothing at all: A "sho ip device tracking" makes clear,
that it's still running.
Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems
to
Post by Antoine Monnier
Post by Sebastian Beutel
be
enabled by default on devices running ios-xe. There's allready a
trouble
Post by Antoine Monnier
Post by Sebastian Beutel
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-
software/8021x/116529-
Post by Antoine Monnier
Post by Sebastian Beutel
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices
anyway
Post by Antoine Monnier
Post by Sebastian Beutel
(those running ios) my first idea was to just disable it globaly. But
even
Post by Antoine Monnier
Post by Sebastian Beutel
though command line completion and online help knows about "no ip
device
Post by Antoine Monnier
Post by Sebastian Beutel
tracking <cr>" and a global line "ip device tracking" shows up in sho
run
Post by Antoine Monnier
Post by Sebastian Beutel
all, i get an error message saying: "IP device tracking is disabled at
the
Post by Antoine Monnier
Post by Sebastian Beutel
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same
error
Post by Antoine Monnier
Post by Sebastian Beutel
message.
But it get's wilder: If i use one of the suggestions of the above link
and
Post by Antoine Monnier
Post by Sebastian Beutel
type a "ip device tracking probe delay 10" on just a single interface,
the
Post by Antoine Monnier
Post by Sebastian Beutel
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global
line
Post by Antoine Monnier
Post by Sebastian Beutel
is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking
globaly? For
Post by Antoine Monnier
Post by Sebastian Beutel
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
+49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
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/
Sebastian Beutel
2016-08-12 16:30:02 UTC
Permalink
Hi Antoine,
Post by Antoine Monnier
"nmsp attachment suppress" came from googling, we implemented it and
verified it stopped device tracking for us.
Did you noticed any side effects? Do you use a Cisco Mobility Services
Engine (MSE) or have planes to use it?
Post by Antoine Monnier
which hardware are you working with?
Until now we noticed the problem on 3850 and 4k5 (Sup 8-E).

Best,
Sebastian.
Post by Antoine Monnier
On Tue, Aug 9, 2016 at 6:50 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device tracking but
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what this
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to succeed
but actually does nothing at all: A "sho ip device tracking" makes clear,
that it's still running.
Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that seems
to
Post by Antoine Monnier
Post by Sebastian Beutel
be
enabled by default on devices running ios-xe. There's allready a
trouble
Post by Antoine Monnier
Post by Sebastian Beutel
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-
software/8021x/116529-
Post by Antoine Monnier
Post by Sebastian Beutel
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices
anyway
Post by Antoine Monnier
Post by Sebastian Beutel
(those running ios) my first idea was to just disable it globaly. But
even
Post by Antoine Monnier
Post by Sebastian Beutel
though command line completion and online help knows about "no ip
device
Post by Antoine Monnier
Post by Sebastian Beutel
tracking <cr>" and a global line "ip device tracking" shows up in sho
run
Post by Antoine Monnier
Post by Sebastian Beutel
all, i get an error message saying: "IP device tracking is disabled at
the
Post by Antoine Monnier
Post by Sebastian Beutel
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all" on an
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same
error
Post by Antoine Monnier
Post by Sebastian Beutel
message.
But it get's wilder: If i use one of the suggestions of the above link
and
Post by Antoine Monnier
Post by Sebastian Beutel
type a "ip device tracking probe delay 10" on just a single interface,
the
Post by Antoine Monnier
Post by Sebastian Beutel
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the global
line
Post by Antoine Monnier
Post by Sebastian Beutel
is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking
globaly? For
Post by Antoine Monnier
Post by Sebastian Beutel
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Dipl.-Ing. Sebastian Beutel tel: +49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
--
Dipl.-Ing. Sebastian Beutel tel: +49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
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/
Antoine Monnier
2016-08-13 09:48:38 UTC
Permalink
we are not using anything that would be dependent on ip device tracking so
we have not seen any side effects (we are not using MSE)

On Fri, Aug 12, 2016 at 6:30 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
"nmsp attachment suppress" came from googling, we implemented it and
verified it stopped device tracking for us.
Did you noticed any side effects? Do you use a Cisco Mobility Services
Engine (MSE) or have planes to use it?
Post by Antoine Monnier
which hardware are you working with?
Until now we noticed the problem on 3850 and 4k5 (Sup 8-E).
Best,
Sebastian.
Post by Antoine Monnier
On Tue, Aug 9, 2016 at 6:50 PM, Sebastian Beutel <
Post by Sebastian Beutel
Hi Antoine,
Post by Antoine Monnier
nmsp attachment suppress
(yeah I know... does not seem related in anyway to IP device
tracking but
Post by Antoine Monnier
Post by Sebastian Beutel
Post by Antoine Monnier
it does turn it off for us)
Even after reading the sparse documentation i can't figure out what
this
Post by Antoine Monnier
Post by Sebastian Beutel
does. May i aks where did you get the suggestion to this?
Post by Antoine Monnier
or better, upgrade do a more recent release? it seems 3.6.2aE has it
disabled by default (Cat 3850)
On the particular switch i had 03.07.03E running. Because 03.06.05E is
currently the suggested release i rolled back to this version and what
happend? A "no ip device tracking" i global config mode seems to
succeed
Post by Antoine Monnier
Post by Sebastian Beutel
but actually does nothing at all: A "sho ip device tracking" makes
clear,
Post by Antoine Monnier
Post by Sebastian Beutel
that it's still running.
Best,
Sebastian.
Post by Antoine Monnier
On Mon, Aug 8, 2016 at 7:28 PM, Sebastian Beutel <
Post by Sebastian Beutel
Dear list,
we ran into trouble with the ip device tracking feature that
seems
Post by Antoine Monnier
Post by Sebastian Beutel
to
Post by Antoine Monnier
Post by Sebastian Beutel
be
enabled by default on devices running ios-xe. There's allready a
trouble
Post by Antoine Monnier
Post by Sebastian Beutel
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-
software/8021x/116529-
Post by Antoine Monnier
Post by Sebastian Beutel
problemsolution-product-00.html
As ip device tracking is disabled by default on most of our devices
anyway
Post by Antoine Monnier
Post by Sebastian Beutel
(those running ios) my first idea was to just disable it globaly.
But
Post by Antoine Monnier
Post by Sebastian Beutel
even
Post by Antoine Monnier
Post by Sebastian Beutel
though command line completion and online help knows about "no ip
device
Post by Antoine Monnier
Post by Sebastian Beutel
tracking <cr>" and a global line "ip device tracking" shows up in
sho
Post by Antoine Monnier
Post by Sebastian Beutel
run
Post by Antoine Monnier
Post by Sebastian Beutel
all, i get an error message saying: "IP device tracking is
disabled at
Post by Antoine Monnier
Post by Sebastian Beutel
the
Post by Antoine Monnier
Post by Sebastian Beutel
interface level by removing the relevant configs".
Next thing is, that no "relevant config" appears in "sho run all"
on an
Post by Antoine Monnier
Post by Sebastian Beutel
Post by Antoine Monnier
Post by Sebastian Beutel
interface level. There are only globaly lines. And if i try to do a
"no ip device tracking" on a single interface i get the exact same
error
Post by Antoine Monnier
Post by Sebastian Beutel
message.
But it get's wilder: If i use one of the suggestions of the above
link
Post by Antoine Monnier
Post by Sebastian Beutel
and
Post by Antoine Monnier
Post by Sebastian Beutel
type a "ip device tracking probe delay 10" on just a single
interface,
Post by Antoine Monnier
Post by Sebastian Beutel
the
Post by Antoine Monnier
Post by Sebastian Beutel
command goes through without an error. The result is, that again no
corresponding configuration shows up on the interface but the
global
Post by Antoine Monnier
Post by Sebastian Beutel
line
Post by Antoine Monnier
Post by Sebastian Beutel
is
Global IP Device Tracking Probe Delay Interval = 10
Any ideas how that makes sense? How to disable device tracking
globaly? For
Post by Antoine Monnier
Post by Sebastian Beutel
what use device tracking could be beneficial anyway?
Best,
Sebastian.
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Dipl.-Ing. Sebastian Beutel tel: +49-711-685-64538
Rechenzentrum Universitaet Stuttgart
http://www.rus.uni-stuttgart.
Post by Antoine Monnier
Post by Sebastian Beutel
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
--
+49-711-685-64538
Rechenzentrum Universitaet Stuttgart http://www.rus.uni-stuttgart.
de/nks
Netze und Kommunikationssysteme Allmandring 30A, D-70550 Stuttgart
_______________________________________________
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...