cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
987
Views
0
Helpful
16
Replies

LMS 3.2, why so many duplicate?

andrea.meconi
Level 2
Level 2

With LMS 3.2, CS and RME are showing the same device twice: once with the hostname and once with the IP. For the same device, RME reports an alias, also.

Many thanks for help.

Andrea

16 Replies 16

Michel Hegeraat
Level 7
Level 7

This is usually cause by the fact that DNS did not work on the first discovery, and you devices gets discovered with the IP as display name.

Next it gets discovered again, now while DNS works and for some reason the display name does not get updated but a new device with the same IP gets added to the DCR.

I'm not sure why cisco has decided for this to work this way.

I try to convince my customers to get the DNS entrys in place before device deployment.

Cheers,

Michel

Thanks Michel.

I'm not using DNS, but populating local file hosts.

When I add a new device we insert hostname, display name and IP.

So many and different devices are reported like alias and I don't understand why?

Regards.

Andrea

I've only seen this where the decive initially did not resolve

If the CS discovery is always able to resolve the ip addresses then normally no new device is created.

Can you post the Discovery Settings Summary here?

Cheers,

Michel

Attached the Discovery Settings Summary.

Preferred management IP is resolved by name.

Thanks for help.

Regards.

Andrea

So on the servers console a ping -a with the device ip, will give you the hostname?

And if you resolve the duplicate in RME, (and thus delete the device with the IP address in the display name), it comes back after the next discovery?

That is new to me. Not seen that behaviour yet.

Cheers,

michel

Are the devices that come back also used as seed device?

if you remove them and use DCR as seed. Do the devices still come back?

Cheers,

Michel

No, we are not using discovery, I believe.

Nothing appears on discovery schedule!

Andrea

An example.

One 2651 with one serial and one ethernet interface.

If I manually add the device using IP on ethernet, that the device appears twice one with correct hostname and one with serial IP.

Adding and removing are done by manual operation.

Thanks for your patience.

Andrea

If you don't want to use discovery then disable/remove the discovery schedule.

If you want both active then best you use the "Resolve by SysName" option.

Cheers,

Michel

Discovery schedule is already empty.

Now I'm going to set resolve by sysname.

Regards.

Andrea

Then someone is runnning discovery manually from time to time?

Strange....

Yes, strange.

No, it doesn't resolve.

If I delete the device with IP in display name, it comes back after the next discovery.

Thanks.

Andrea

You are not using discovery? I'm not following here?

How do you add devices then? From an import file?

A IP address should resolve if you hosts file is OK

I configured a name in my hosts file ( old-vmhost ) and I can do this

I:\>ping -a 10.170.46.120

Pinging old-vmhost [10.170.46.120] with 32 bytes of data:

Reply from 10.170.46.120: bytes=32 time=3ms TTL=126
Reply from 10.170.46.120: bytes=32 time=1ms TTL=126

Ping statistics for 10.170.46.120:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 3ms, Average = 2ms
Control-C
^C
I:\>ping old-vmhost

Pinging old-vmhost [10.170.46.120] with 32 bytes of data:

Reply from 10.170.46.120: bytes=32 time=2ms TTL=126
Reply from 10.170.46.120: bytes=32 time=1ms TTL=126
Reply from 10.170.46.120: bytes=32 time=1ms TTL=126

Ping statistics for 10.170.46.120:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms
Control-C

Check your hosts file

Cheers,

Michel

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco