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

Similar Messages

  • 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 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.

  • 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 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.

  • 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?

  • 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

  • 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!

  • 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.

  • 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.

  • LMS - Add Discovered Devices to a Group

    Hi Netpro
    i have created 5 UDG (Ex CampusA - to- CampusE and five different discovery jobs based on the user defined group,
    Also i have created a discovery job and added to the UDG CampusA  ( Subnet 172.16.16.0) in order to see only devices in campusA , but the LMS Discover  all our devices in the organasations!!!!
    what rong i have done to let LMS  sees all Devices
    thanks
    jamil

    I hope you see the filter on the UDG determents what devices are in that group.
    It is not the discovery job that puts the devices in a UDG.
    Although you can place the newly discovered devices in a group in 4.1 or higher but after the next discovery this changes.
    You can have multiple discoveries for different subnets. You can when you create the discovery job tell it to filter on an IP range.
    The steps of the discovery are modules, community string(s), filter and global settings.
    In the filter part you can say what to include or exclude and so limit the discovery to that range..
    Cheers,
    Michel

  • How to Fix Disappeari​ng HP Printer Drivers -- Disable HP CUE Device Discovery Service

    I have a new HP G60-530US laptop with Windows 7 installed (less than 2 months old). It is connected to an HP 7410 All-in-One Printer and a Brother laser printer.
    Three times now, the HP 7410 printer has mysteriously disappeared from the installed printers. The Brother printer does not disappear.
    To re-install the HP 7410 printer requires disabling the AVS using the Services,msc utility (not just shutting down the AVS (Panda in my case)).  It takes 20 minutes or so to re-install the HP printer driver software.
    HP tech support is clueless about the cause or cure for this.
    The laptop people referred me to the printer support people and the printer support people referred me to the laptop support people. The last tech support guy suggested that I restore the system on the theory that if the problem persisted it would be a hardware problem and not a software problem. He seemed to miss the fact that the disappearing printer driver software only occured with HP printers.
    HP technical support was worthless.
    Some internet forums suggest that this occurs when HP machines are connected to different networks. I noticed my problem occur after I took the laptop on a business trip and connected to a different wireless network.
    On Vista forums, I've discovered that the disappearing HP printer drivers has been a problem for some time over a wide range of HP printers. 
    The solution identified on those forums is to stop and disable the HP CUE Device Discovery Service. Apparently, this service is used to detect HP printers and add them to the HP Solutions Center software.
    In my experience, the HP printer drivers disappeared when my laptop comes into range of a "foreign" HP printer with wireless capabilities. For example, my laptop dropped my configured HP wireless printer when I went to an office that had a different wireless HP printer installed. The HP CUE service trashes the existing printer driver even though you do not intend to install and use the "foreign" printer. That would also explain why the printer drivers disappear when visiting a hotel or other location where any HP wireless devices exist. It would also explain why non-HP drivers do not disappear.
    I've disabled the CUE Device Detection Service (using the Services utility). I'll see if that works.  From what I've read, the CUE Device Detection Service is not needed after you have installed your printer, but it remains in your computer's active memory just "in case" you want to connect to a new HP printer and install software for that printer.  Said differently, after your printer is installed, it remains as useless HP software that clogs your machine's resources.
    A patch from Microsoft or HP (e.g., a patch that disables the CUE service) would be a big help to users if the number of posts on this issue are any indication of how pervasive this problem is.

    This seems to be a common problem that exists for many HP devices, varying computer moakes and models and different operating systems. So, the conclusion must be that it is a HP issue. WHY ARE THEY NOT FIXING IT?
    Based on this I am quite happy to buy a different make of printer so how does HP justify the continuing lack of support?
    I posted a message about my C7180 All-in-one which had been causing problems but I put it down to me making (unrelated) changes to my system then noticed it got worse when I connected a new Trust digital pad. However, even when the pad is not connected I get the problem of disappearing drivers with the printer still visible.
    What seems to happen to my set-up is it works when it is first reloaded and used, but the next time I open the HP software it fails and no other software is able to print/scan on the device.
    Can somebody explain what the CUE is? I'll give it a try but I don't know what it refers to.
    Who'd have thought that in the 21st century, software/hardware engineeers still can't make a simpy process for a computer. Whatever happened to the promise of plug'n'play?
    P.

  • How to specify a wildcard in LMS 4.2 Device Manager

                       I am in the process of transitioning from LMS 3.2 to LMS 4.2.    Device Manager in LMS 3.2 uses asterisk as a wildcard when searching for a device.   When I use the asterisk in LMS 4.2 it does not work.   For instance I enter VCG1* and get "The device is not available in the Device Credential Repository, or you are not authorized to view the device details."   VCG100-IT-AX is visible, selectable, and editable if I select the icon to list the devices available.    How do wildcards work in LMS 4.2 Device Manager?

    You're welcome. Thanks for the rating.
    Here's an example:
    LMS01/sysadmin# show version
    Cisco Application Deployment Engine OS Release: 2.0
    ADE-OS Build Version: 2.0.1.043
    ADE-OS System Architecture: x86_64
    Copyright (c) 2005-2010 by Cisco Systems, Inc.
    All rights reserved.
    Hostname: LMS01
    Version information of installed applications
    Cisco Prime LAN Management Solution
    Version  : 4.2.1
    Vendor   : Cisco Systems, Inc.
    LMS01/sysadmin# shell
    Enter shell password :
    Starting shell...
    [LMS01/root-ade ~]# uname -a
    Linux LMS01 2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
    [LMS01/root-ade ~]#ls -a
    .   .bash_history  .bash_profile  .cshrc    .rnd  .tcshrc          bin          install.log.syslog
    ..  .bash_logout   .bashrc        .lesshst  .ssh  anaconda-ks.cfg  install.log
    [LMS01/root-ade ~]# pwd
    /root
    [LMS01/root-ade ~]#

  • Device discovery failed in ANM

    Hi,
    I've got the following error message when I want to import a 6506 in 12.2(33)SXI2 with an ACE module.
    I've tried in ANM 2.2 and 3.0 = same problem.
    Can someone help me ?
    Device discovery failed: Exception occured for model:VlanModel
    Exception occured for model:InterfaceModel
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
    com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort.
    Thanks,
    Greg.

    Hi Greg,
    The error message you are seeing is likely triggered by some un-expected configuration on the cat6k.
    It is likely your cat6k configuration has an interface defined as a switchport which has a subinterface  defined on it.
    This is usually not allowed on most sup versions that we  have seen and hence is not modeled/ cannot be discovered in  ANM.
    We have bug id CSCtd94658 opened for this issue.
    You  could try to have your customer remove the subinterface indicated above and then  try the import into ANM.
    Also,  they could maybe add back that interface if really required after the initial  import.
    Since  Cat6k configs are not auto-sync'ed in ANM, they will be okay until they do a  manual sync.
    This workaround in also documented in the release notes of CSCtd94658.
    Thanks
    Sujatha
    ========

  • Add device, discovery device, configure and trobleshoot device

    Hi
    I am new on network management, and I installed cisco prime 1.2 this week
    I need to perform these action on the ISE and on many catalyst switch
    - Add device
    - discovery device
    - Monitor, configure and trobleshoot device
    Which information should I ask to the network administrator (snmp version , ip address ...)
    How should I perform thses 3 action (any step by step document should be good for me)
    Regards

    Hi,
    Chekc the below links:
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/gettingstarted.html#wp1069890
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/gettingstarted.html#wp1070951
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/gettingstarted.html#wp1070638
    Thanks-
    Afroz

Maybe you are looking for

  • Macbook doesn't wake up after automatic sleep

    I've got a problem with my macbook. Whenever it goes asleep from not using it ( automatic, I set the time at 15 minutes ) I need to push the power button for like 2 minutes before it wakes up again. I've many friends who have macbooks, whenever they

  • Need Help in improving logic for determining the range

    Hi guys, I need some help in my program logic to determine the range of value. My purpose of this program is to find which combinations have the lowest amplitude. In the attachment is a set of number. e.g 10    0 is a combination. Each combination, I

  • Dual 1.8 Refuses to Burn 16X DVD

    Any way to get my Mac to burn 15Xs DVDs? Every time I try to use a 16Xs blank DVD for burning purpose I get a no can do type message. 8Xs DVDs are fine. I know that my Sony DVD burner is limited to *Xs burns but why does it refuse to use 16Xs disks?

  • 1004 Error in App Store when trying to update Logic Pro

    I keep getting a 1004 error when I try to update Logic through the App Store. I've already tried relogging and deleting the .plist cookies and preferences. Help?

  • Cant sign into facetime

    Ok i have tried signing into FaceTime with two different accounts and it keeps saying,"Cant sign in. Please check your network connection and try again." I am positive my wifi is working. Any suggestions?