LMS 3.1 Device Discovery issue

Hello,
I have been getting myself familiar with LMS, but can't figure out why I am having issues seeing some devices. I can't find any solution to my problem on other posts.
I have a server farm connected to my core switch, both can see each other via CDP, and the SF can ping the LMS server. However, I have 'device unreachable' on device discovery and CiscoView. SNMP community strings are the same on each device, and are configured on LMS.
Any suggestions? Thanks in advance!

Hi,
LMS tries to contact each device directly via SNMP. If it can talk directly to the device, the device is added into DCR as Reachable. If it cannot talk directly to the device, the device is deemed as Unreachable and it is not added into DCR to be managed by LMS.
If LMS is unable to communicate it could be due to any number of things including timeout, incorrect community string, snmp-server view, firewall or access list.
A definitive way to determine the issue would be to perform a packet capture during discovery to see the SNMP transaction between LMS and an 'unreachable' device.
You can also try increasing the timeout value.
Thanks.

Similar Messages

  • LMS 4.2 Device Discovery

    I have used every version of LMS since 1.0 and I'm very familiar with the software.  My problem is with the last few versions and the device discovery feature.  It seems that in earlier versions, once the seed device was configured and devices had the appropriate community strings and cdp was enabled, the device was discovered.  With these earlier versions, all of my devices were discovered.  Any new device added to the network was also discovered.  I never had to deal with devices that were "Unreachable" as all my devices were "Reachable". My network has not changed.  I still have the same core switch ip address since version 1.0.  My edge switches are still configured for the network as they always have.  Same community strings.  What has changed is the LMS discovery process.  What's going on with these "modules"?  I have 120 devices on my network and 117 will be "Unreachable".  Even the core switch is unreachable.  I have tried CDP, Global, seed device, DCR as seed.  Still the devices are unreachable.  There are no firewalls or access lists.  The LMS server has complete access to all devices.  Does anybody have any thoughts, comments??? Or am I just being too picky expecting the software to just work?  TIA                  

    Nothing has chnaged as considerable in discovery module since inception. Addition of new modules and algorithm has just made it stronger and smarter.
    If all the devices are unknown there is certainly some issue with communication using snmp. I would request to modify and if you think multiple communities may be there try to configure all and keep the target *.*.*.*.
    Following guide on LMS discovery stands from LMS old versions to till date similar on how it works :
    https://supportforums.cisco.com/docs/DOC-9005
    -Thanks

  • Help with LMS 4.1 device discovery?

    Hello,
    I'm new to the LMS family and seem to be having an issue with device discovery. The discovery session launches, (I get an email telling me it launched) but the summary page tells me that while the devices are discovered, none of them are reachable.
    I've checked the SNMP strings, and they match (and also worked under Whats Up). Is there a specific log I can look at to find out what's going on under the hood of LMS?
    Thanks,
    Cam Wynd

    If you go into the processes and click on CSDiscovery then start, it will run the discovery.  That's just a work around for now.

  • LMS 3.1 Device Discovery

    Hi, Having had a fully operational version of Ciscoworks on a very old server we were advised to move it to a virtual server, with a new IP address. Unfortunately since then the device discovery is not collecting data on all devices on our network, and showing them as unreachable. Even though I have replaced the IP address in the configs on the network switches.
    The odd thing is that it is finding 6 devices but not all of them. Just wondered if this is something anyone out there has seen before that may be able to shed some light for me.
    Thanks
    Jo

    Hi,
    Kindly make sure all the device are snmp reachable with the new IP from the CiscoWorks Server. However more information will be found by enabling the debugging for Device Discovery and then try to run the Device Discovery again.
    To enable the debug for Device Discovery , kindly to Common Services > Device & Credentials > Device Discovery > Discovery Logging Configuration > select the modules you are using for device discovery along with Data Collector, Discovery DeviceInfo , Discovery Framework, Discovery util and run the device discovery again and then send the ngdiscovery.log from CSCOpx\log location.
    Also kindly make sure you have make the required changes on the Schedule discovery settings as well since Schedule discovery have its own settings for Device Discovery as compared with Ad hoc Discovery settings.
    Here is the good doc link created by Sir Joseph Clarke to understand the Device Discovery and for troubleshooting purposes.
    https://supportforums.cisco.com/docs/DOC-9005
    Note :- ngdiscovery.log contain information about the IP address of your device in the network.
    Thanks,
    Gaganjeet

  • LMS 4.2 Device Discovering issue

    HI All
    I have experience in LMS 3.2 and my company asked me to install and LMS 4.2. I have all documents about LMS 4.2 but it is taking time to read and doing as per document. I started discovery but the problem is last two days it is running and finds 50 % of devices only and still the staus is running. The Network topology is 2 CORE switch ( Discovered) , connecto to 2 Distribute switch and Server form switch ( Discovered) Access Switches are connected to the Distribute switch some are Discovered most of not found. Some Access switches are connected to neighbor Access Switches it is not directly connected to Distribued Switch.
    Please advise normally how long will take for discovering 70-80 devices ? How to trouble shoot for non discovering devices ?
    Thanks and Regards,
    Abdul Hameed.

    If a device is missing or isn't added, it could be due to incorrect credentials. However you still can add it manually from DCR.
    You can use the Adding Devices to add devices, device properties or attributes, and device credentials to the Device and Credential Admin.
    Go to the CiscoWorks home page and select Inventory > Device Administration > Add / Import / Manage Devices.
    For more details on how to add devices, please check :
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/user/guide/inventory/mng_device.html#wp1172685
    -Thanks
    Vinod
    **Rating Encourages contributors, and its really free. **

  • LMS 3.2 Device Discovery

    Is there a document that gives a better technical explanation of the discovery process? The
    documentation I've found so far is fairly superficial.
    I'm testing discovery with a new LMS 3.2 installation and so far it seems like I will have to enter every IP subnet we have in a ping sweep, because devices just aren't getting discovered. I tried CDP alone with one seed - a router at the hub of our network. I tried discovery with that one seed router with both CDP and Routing Table - I would expect that to discover other devices via the subnets in the routing table. That's not what happened, so I'm wondering how the "Routing Table" module actually works.
    If we don't have CDP everywhere, will devices without CDP be discovered?
    Finally, I've seen a number of comments here that say not to use the DCR as a seed file. I must be missing something, because I would think that you'd want to do a discovery starting with what you already have to find out what's been added to it, without having to tell the app where to look. That seems to defeat the purpose of discovery.
    Any assistance would be greatly appreciated!

    Discovery requires that every device be reachable via SNMP using the SNMP credentials you configured in Discovery.  Devices which are found by the various algorithms which are not reachable via SNMP will be marked as unreachable, and will not be added to DCR.  So, while you may configure ping sweeps, and Discovery may be able to ping certain nodes, it does not mean that those nodes will be discovered.
    Generally, users choose CDP and ping sweep.  Routing Table is fine, but it can lead to SNMP CPU spikes on routers with large routing tables.  The way the routing table module works is to poll the ipRouteTable via SNMP, then go through each ipRouteNextHop to find the next hops.  Because polling this table can be CPU-intensive, it is often filtered out using an SNMP view.
    If you only go with CDP, then devices which do not have CDP neighbors will not be found dynamically.  Such devices would need to be manually added as seeds.
    And I generally recommend people enable "Use DCR as seed".  This can greatly cut down discovery time.

  • DFM device discovery issue "Devices stuck in Questioned state"

    Hi
    We have LMS 3.0.1 installed with DFM 3.0.4 The devices are showing Questioned with Error code "SNMP timeout" with no specific reason. The snmpwalk is coming for the device as I checked with snmpwalk command. The only device discovered as"known" has ICMP permitted from Server to device and no other device has. They only have SNMP permit. Can this affect the dicovery?? or what else can I try....Please suggest!!
    Rgds

    Yes. DFM requires that all devices be both SNMP and ICMP reachable. DFM uses ICMP to verify reachability to all IP addresses on the device. However, at the very least, the address by which you manage the device MUST be ICMP reachable.

  • CUOM 8.6 - Device Discovery Issue

    I have installed CUOM 8.6 in window 2008 Server. I have also opened the following ports (allowed exceptions) on the windows firewall as per the installation Document
    Description of Service
    Protocol
    Port Number
    CUOM Web Server
    TCP
    1741
    CUOM HTTPS
    TCP
    4431
    CUSM SFTP Server
    TCP
    22
    CUOM Trap Listener
    UDP
    161
    CUOM Trap Listener
    UDP
    162
    CUOM Syslog Receiver
    UDP
    514
    CUSM Syslog Receiver
    UDP
    5666
    In addition i have also enabled echo request for ping, and opened network discovery ports. But i am not able to discover any devices. i get a not reachable message, even though i am able to ping from the server. But if disable the firewall, everything is discoverable.
    Any ideas on what else to allow on firewall??

    I think you should maybe install CUOM 8.5 on a separate box to test if you'll experience the same challenge as now, i know this sounds strange but try it - try installing CUOM 8.5 (same version as your CUCM) on a separate box or degrade the current installation.
    As for ATA's, i'm not sure if they are monitored - were they monitored in your previous implementation of it's your first time discovering them? Please see below:
    Q. What devices does Cisco Unified Operations Manager 8.6 support?
    A. Cisco Unified Operations Manager 8.6 supports all the devices that were supported in UOM 8.0. It continues its industry-leading support for Cisco Unified Communications devices by adding support for newly released Cisco products.
    Support for components of the Unified Communications 8.6 solution includes:
    • Cisco Unified Communications Manager 8.6
    • Cisco Unified Communications Manager Session Management Edition 8.6
    • Cisco Unified Communications Manager Business Edition 8.6
    • Cisco Emergency Responder 8.6
    • Cisco Unity Connection 8.6
    • Cisco Unified Contact Center Enterprise 8.6
    • Cisco Unified Contact Center Express 8.6
    • Cisco Unified Voice Portal 8.6
    • Cisco Unified Presence 8.6
    • Cisco Unified Personal Communicator 8.6
    • Cisco Unified Communications Manager Express 8.6
    • Cisco Unity Express 8.6
    • Cisco Unified Border Element 1.4 and later
    • Cisco Unified Expert Advisor 8.6
    • Cisco Hosted Collaboration Solution 8.6
    • Cisco Unified Communications on Cisco Unified Computing System (Cisco UCS™), support for monitoring of the Cisco UCS server
    – Cisco Unified Communications on UCS - UC application only
    – Cisco Unity Connection on Cisco UCS - UC application only
    – Cisco Unified Contact Center Enterprise on Cisco UCS - UC application only
    – Cisco Unified Customer Voice Portal (CVP) on Cisco UCS - UC application only
    Refer to the Cisco Unified Operations Manager 8.6 Supported Devices Table at http://www.cisco.com/en/US/products/ps6535/products_device_support_tables_list.html or to the Cisco Unified Operations Manager 8.6 Release Notes at http://www.cisco.com/en/US/products/ps6535/prod_release_notes_list.html for a complete list.

  • Device discovery in Cisco Prime LMS 4.1

    Hi,
    im using CISCO PRIME LMS 4.1 for manage my network, i ran a device discovery job using a ping sweep on the ip ranges of my network, ie 192.168.1.0/24, 192.168.2.0/24 and so on... the discovery found all my devices, but it discovered duplicate devices with illegal ip Addresses, ie
    ip                                    device    
    192.168.1.255               S1
    192.168.2.0                    S1
    192.168.2.1                    S1 (the real address)
    all in reachable status.
    i dont undestad why the program adds that repeated illegal addresses.. someone can help me with that issue??
    how can i run the device discovery to avoid this problem?
    Many Thanks.

    Julio,
    Don't let LMS decide on what IP address it will manage the device.
    For example, let LMS do a lookup of the sysname in DNS, then it will use the IP address coming back from the DNS as management IP.
    This is what I do to avoid this.
    But I also feel that LMS should be bright enough to never manage the same device twice. I think Campus DFM or RME will eventually figure out the 2 devices are the same, but they can't "fix" what is wrong in the DCR.
    Cheers,
    Michel

  • LMS Discovery Issue

    We have a customer with an issue with LMS discovery.
    It will discover new devices but will fail to update them to the  DCR, because it does not match the credential set policy when the  credential set is defined by Device name and an SNMP OID is used.
    They have different devices and depending on the type  they use different credentials, Wireless AP’s for example use different  credentials to Routers.
    They can match on other fields to get a large amount of devices discovered however are still missing the majority.
    With little knowledge of this product, can anyone tell me if this is supported?
    Thanks
    Colin

    Hi Colin,
    Credentials set policy has nothing to do with the devices getting updated in DCR.
    while configuring the device discovery settings do not select any DCR credentilas set.
    One thing that you need to make sure is that devices are SNMP reachable and the Community string that you are using in the device disocvery settings should be CORRECT.
    Thanks
    Afroz

  • LMS 3.2 CS Discovery finding "0" devices

    All of a sudden, after my "friendly" Windows server admin re-booted my LMS 3.2 box (without stopping the daemon!), my Discovery jobs are returning zero devices discovered. Prior to this, I was discovering 135 devices; which is correct for our environment. Tried deleting all the jobs & configuring new ones, but I get the same results. Tried stopping & re-starting the daemon service with no luck. Basically, we use UTT to feed a NAM process which is still showing entries on a daily basis, so I assume the DCR is still functioning; albeit off older network scans. Discovery is just not updating, therefore, I'm missing recent network adds & moves. Jobs are completing as "successful" but only run for 1 or 2 seconds. Anybody ever see anything like this before? Thought I'd try here for a "quick fix" before calling in a TAC case.....
    All LMS modules are the latest. Recently updated to CS 3.3.0 and CM 5.2.1. Also updated RME to 4.3.1. Everything ran great after these updates. Box is an HP/Compaq DL360 G4 running Windows Server 2003 R2 64-bit; dual 3gig processors; 8gig RAM; dual mirrored 72.8gig SCSI Ultra 320 drives.
    Here's a screen shot of the discovery job report:
    Thanks,
    Rick

    The pdshow looks fine and it seems the discovery ran fine today:
        Process= CSDiscovery
        State  = Transient terminated
        Pid    = 0
        RC     = 0
        Signo  = 0
        Start  = 8/20/2010 12:22:55 PM
        Stop   = 8/20/2010 12:24:00 PM
    Campus Manager Data Collection and the discovery process are separate and should not be mixed up.  The discovery log showed this error:
    [ Thu Aug 19 13:32:43 CDT 2010 ] FATAL  [DiscoveryUtil : isDCRServerRunning]  : DCRServer is not running.
    This seems accurate comparing with the pdshow:
        Process= DCRServer
        State  = Running normally
        Pid    = 12136
        RC     = 0
        Signo  = 0
        Start  = 8/19/2010 1:34:04 PM
        Stop   = Not applicable
        Core   = Not applicable
        Info   = DCRServer is up and running
    So it seems this last discovery captured on the logs could not run because indeed the DCRServer was down at that time.
    Please post a screenshot of Common Services > Device and Credentials > Device Discovery.  Do you see 0 devices discovered there?  Check under Common Services > Device and Credentials > Device Management, if you expand "All Devices" do you see devices there?

  • CiscoWorks LMS 4.0.1 / Device Discovery

    Simple question, not so simple answer?
    I have tried multipule times to do device discoveries, the same 26 devices come up unreachable.  I have checked, double checked, and tripple checked the snmp community ro and rw strings on the switches and that snmp is enabled.. All seems configured correctly on the switches.  I have tried arp, ip ping, cdp, just about all of the proper discovery protocols.  I have tired using different seed devices, even already known reachable devices....  I'm stuck, no clue why I can't get this going! Please help.  As a side note.. If imanually added unreachable devices as an snmp target in snmp setting windows during device discovery configuration it will "reach" and add the devices.

    John...did you get this resolve? I am having the same issues. Several of my devices with subnet of 10.83.*.6 (seed switches) are unreachable in CW. I can telnet to many of the devices from the CW server and see that the community string (RO/RW) is the correct string in the configure however, still unreachable. Was you able to get this working? I do have a TAC case open for this. Still working through the issue. Write back...thanks in advance.

  • Cisco Prime LMS - Device discovery

    How do you configure Cisco Prime LMS Device Discovery, so that you can have two credentials sets for specific "special devices" (host based statement) and one for the of the devices (global subnet statement)?
    Thanks in advance.

    Hi,
    Here is the link to the document containing the detailed steps regarding Credential Sets.
    After defining your sets then set up Credential Set Policies.
    Thanks!

  • LMS 4.0.1 - DFM issue

    HI,
    I installed the LMS 4.0.1 and I'm facing a problem with DFM. None Fault is showed.
    The Fault Discovery Process never finishes, it is always Running, according attached file.
    I checked the LMS Process MAnagement and 4 process are as "Transient Terminated". The  process are: CSDiscovery, DCRDevicePoll, FHPurgeTask,UTMajorAcquisition. I started all process but 2 minutes later the process goes to "Transient Terminated".
    All Windows Services related with CiscoWorks are UP.
    Someone knows this issue?
    Thanks for your help.
    Luis

    Hi duong,
    I'm using the ping sweep. not using the "Use DCR as Seed List" as there were more than 5000 devices.
    Earliar LMS pick the devices. once the discovery was running for a long time . to stop the same we have restarted
    the CSDiscovry process. After this we are facing the issue.
    Channa

  • Device Discovery problem

    Hi,
    I am having problem starting device discovery in Campus Manager.  After looking at a couple of different things, noticed that DeviceDiscovery is in TRANSIENT TERMINATED ProcessState.
    I attached device discovery properties file. Please anyone check and help me to find the issue. Thanks.
    Best Regards
    S.Rajkumar

    Transient terminated is a normal state for DeviceDiscovery.  See my LMS daemon cheat sheet at https://supportforums.cisco.com/docs/DOC-8798 for more details.  When Discovery stops, the daemon will terminate.

Maybe you are looking for