LMS3.2.1 Device discovery

[Rowan State]

Hello,

We currently discover our devices using a Ping-Sweep IP range that has the WAN IP addresses of all our site routers, and also enable CDP discovery so that all our site switches that reside behind each router can also be discovered. - This solution has worked well for us for many years. We have however now configured Tunnel interfaces on each site router that provide tunnelled connectivity through to some central routers. It is a requirement for us to enable CDP desvivery across these tunnel interfaces.

The problem we have now is that LMS is rediscovering the site routers by their tunnel address instead of their WAN address which is causing us management problems. - Does anyone know if it is possible to get LMS to ignore tunnel interfaces during device discovery/rediscovery?

[Vinod Arya]

LMS discovery algorithm has a lot of modules which can be used, along with CDP to discovery neoighbouring devices and sometimes with multiple IP addresses.

What end's as the Management IP address of a discovered device is a configurable option and you should decide on what is should be.

For sure, this is probably the single most confusing part of Discovery.  How does Discovery determine what IP address (and optionally hostname) is used to manage a given device?

It has following options :

>> Use LoopBack Address

>> Resolve By Name

>> Resolve By SysName

>> None

I would recommend you to check this guide which explains discovery and specially Mgmt IP:

https://supportforums.cisco.com/docs/DOC-9005#Preferred_Management_IP

Please check you have configured this part properly to populate IP address proprely after discovery.

-Thanks

Vinod
**Rating Encourages contributors, and its really free. **