Device rediscovered through another interface

Unanswered Question
Apr 7th, 2009

I have device already defined in CiscoWorks through Loopback interface. The problem is the same device keep coming up in the device discovery through PortChannel interface, which is a different IP address, so it looks like a new device. Is there a way to make discovery aware that this device is already in DCR?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Tue, 04/07/2009 - 09:13

What versions of Campus Manager and Common Services do you have?

Joe Clarke Tue, 04/07/2009 - 09:35

Have you confirmed that it is Campus Manager Device Discovery which is adding the duplicate device? That is, if you remove the duplicate device, and disable Discovery, does the device not come back? If so, please post the running config from this device.

A.Shchukin Tue, 04/07/2009 - 09:47

I only see the dupe in DCR.

Here is the report on device discovery:

C6509-IOS . (manualy added)

Discovery show also which is the same device. Show tech attached.

Joe Clarke Tue, 04/07/2009 - 09:52

But are you sure it's Discovery that initially finds this dup? Do you have DFM installed on this server? It has also been known to cause duplicate devices in DCR.

A.Shchukin Tue, 04/07/2009 - 09:56

DFM is intalled on the same server. How do I check if DFM causes the dup in DCR?

Joe Clarke Tue, 04/07/2009 - 09:59

Run the command:

pdterm DfmServer

This will shutdown DFM's polling. Delete the duplicate device from DCR. Run a new Discovery in Campus. See if the duplicate device comes back.

To restart DFM polling, run:

pdexec DfmServer

A.Shchukin Tue, 04/07/2009 - 10:02

How can I delete a device from DCR?

The device is not in the managed state.

Joe Clarke Tue, 04/07/2009 - 10:05

If the device is listed under Common Services > Device and Credentials > Device Management, you can check it, then click the Delete button. Are you saying the device is not showing up in DCR?

A.Shchukin Tue, 04/07/2009 - 10:12

I can only see it in the discovery. But I am not able to find that discovered device in CS.

Joe Clarke Tue, 04/07/2009 - 10:15

And is the Port-channel IP showing up as unreachable in the Discovery report?

Joe Clarke Tue, 04/07/2009 - 10:37

Then that is nothing to worry about. Since Campus cannot contact that address, it does not know that it is a duplicate of another device. In any event, Discovery only sends reachable devices to DCR, so the switch will not be duplicated or managed by the Port-Channel address.

A.Shchukin Tue, 04/07/2009 - 10:46

I use discovery to find find if there are any new devices on the network.

Joe Clarke Tue, 04/07/2009 - 10:48

That's fine. My point is that this "duplicate" is not something to be concerned with. If you open your network such that Campus can poll it with SNMP, it will automatically determine that this device is a duplicate of the other managed device, and it should no longer appear in your Discovery report. Alternatively, you can just add this IP address to the Discovery exclude filter, and Discovery won't try to contact it at all.

A.Shchukin Tue, 04/07/2009 - 11:14

I suspect there are a lot of devices with a similar issue. So I would need to login into each discovered devices in order to find out which device it is.

Joe Clarke Tue, 04/07/2009 - 11:37

In order to weed out which devices were unique, and should be reachable from those that are being found by an unreachable CDP address, yes.

janvandek Mon, 05/18/2009 - 01:43


May I use this converation to ask a related question?

Which algorithm is used during the discovery? What I mean, if it sees a new device which IP address will be taken as the management (in DCR) address? (loopback, highest IP, lowest IP, ...)

A.Shchukin Mon, 05/18/2009 - 06:04

I had a ticket open with TAC on this issue.

If loopback option is enabled in a discovery option then it should be loopback.

Sometimes it finds a "new device" and it's an IP addresses of a VLAN interface.

Their recommendation was a command:

cdp source-interface looback X.

The problem is this command supported in a few IOS's... You would need to keep new devices, which are being discovered on that release and have that command in

How would it be a new device?


This Discussion