LMS 4.0 Fault discovery snmp timeout

Hi all,
I am running LMS 4.0 on windows 2008 SP2 64-bit.
I have the problem that all devices from dcr stay in the questioned State with error state snmp timeout.
I have done a credential verification and snmpwalk to the devices and this works correctly.
regards
Joerg

Joerg,
What kind of devices are they that are being questioned?
Make sure Fault Management in 4.0 supports the devices.
Rob

Similar Messages

  • LMS 4.2.2 Fault discovery stalls, never complete

                      Using LMS 4.2.2 on a network with approx 800 devices. Fault discovery runs for long periods without completion, previously known devices sit in learning state for long long periods. Some devices do become known but this seems random as to which ones. Faults are still reported on devices in a learning state, which means there are often many faults reported which are false. However because devices are in learning state the false positives cannot be weeded out. This problem has been occuring since LMS 4.0 so have not had Fault and event monitoring working properly for some time, however would seriously like to utilise this feature.
    Would appreciate any pointers as to where to start... Mark

    I am having the IP vs. device name issue as well. The funny thing is if you hover over the IP of the device in Fault Monitor, you can see the device name listed. I was on a conference call with Cisco recently and pointed this out. One of the reps said the faults and alerts showing IP address issue should be fixed in version 4.2.3, but I don't know if he was basing this on first-hand knowledge or was just assuming. Does anyone know if this is the case?
    As for throttling alerts. I had a false positive alert from a device that I put in a custom fault group and changed the threshold on to keep them from firing. You probably have already resolved this issue, but I didn't see a resolution listed here. You would have to determine if raising a threshold for a device is adequate for your situation.
    Thank you,
    Mark

  • LMS 3.2 DFM-all devices QUESTIONED-SNMP Timeout

    I imported 26 devices to DFM. All devices became QUESTIONED, error is SNMP timeout. Here are the troubleshooting steps that I tried:
    1. rediscovered devices
    2. deleted and rediscovered devices
    3. increase snmp timeout settings
    4.re-entered snmp strings in device credentials
    But I still get the same result.I noticed that devices become questioned so fast.Any advise on this?

    Hi,
    What version of SNMP you are using on these 26 devices ?Try to do the following:
    - Go to Device Center
    - Select one device for test
    - click on "check device credentials", select SNMP according to the version you are using.
    - See the results.
    May be you get more technical and detailed information about the SNMP timeout error. I have already experienced some problems using SNMP v3. The problem was resolved when I configured the SNMP v2c instead of v3.
    Also, I suggest you to try do "SNMP walk" test in the Device Center. If you get some results reading, for example, the value of "sysObjectId", just verify the Credentials Settings in DCR. You can edit the Credentials trhough the Device Center -> Edit device credentials.
    Regards,
    Wando N. Rocha

  • LMS 4.0: Fault Monitoring Device Administration stuck in learning

    Hello Members,
    i have a problem with Fault Monitoring Device Administration. i have two devices which stuck in learning mode for almost forever. When the job is done the devices report an error SNMP timeout. I run a credential verfication job and the credentials for the devices are correct.
    any ideas?
    regards
    alex

    Assuming these are the only four devices using SNMPv3 in LMS, then the engineID is a non-issue.  However, if any other device has the same engineID as those two non-working devices, the problem could still be a duped engineID.  Debugging with logs is fairly complex.  The easiest way to identify the problem is to use a sniffer.  Start a sniffer trace filtering on all traffic to one of the failing devices.  Then, rediscover the device in Fault Monitoring under Admin > Collection Settings > Fault > Fault Monitoring Device Administration.  When it goes to a Questioned state, look at the sniffer trace.
    If you see SNMP report packets indicating an error of notInWindow, that points to the duplicate engineID problem.  ICMP packets without responses points to problems with ping.

  • C370 - 7.6.3-019 An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370'

    I got the following CRITICAL error at C370:
    The Critical message is:
    An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370', "<type 'exceptions.ValueError'>", "invalid literal for int() with base 10: 'no reading'", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8477)|757] [egg/interface_controller.py poll_ipmi|1409] [snmp/hardware.py update_sensors|89] [snmp/ipmi_handlers.py update_sensors|609] [snmp/ipmi_handlers.py _parse_sensor_lines|583] [snmp/ipmi_handlers.py _handle_fan_result|370]')
    Version: 7.6.3-019
    Maybe this bug is related to WSA bug CSCzv78978...
    Need a help to see if this bug is resolved at 8.0.1-023 release.

    This is ESA defect on 7.6 family... see the following:
    https://tools.cisco.com/bugsearch/bug/CSCzv22991
    You'll need to upgrade to 8.0.1-023, or you can open support case, we can provision 8.5.6 FCS, or you can wait for our 8.5.6 GA release shortly...
    I hope this helps!
    -Robert
    (*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

  • WLSE Configuration archive download SNMP timeout

    HI, I´m new to WLSE. My AP´s are already discovered and managed, but when I try to download the configuration archive from them, the Job Always fail with a SNMP timeout error message. This problem occur in the upgrade firmware job too.
    Whe I go to reports, device center, I can see the AP configuration, but in the configuration>archives>view archive I have nothing.
    I appreciate your help

    You can configure the timeout value by selecting Firmware > Advanced Parameters. From this option you can change the "Per device job operation timeout value" to a higher value

  • LMS 4.2.2 Fault Discovery - Network Adapters Limit Exceeded

    Running fault device discovery after adding approx 50 new devices to LMS DCR. It seems I have reached a limit in DFM with regards to how many device components it can manage. The devices are put into questioned mode and the following error is seen in the Question State Device Report
    Network Adapters Limit Exceeded.The number of Network Adapters discovered by Fault Management exceeded the maximum supported limit.Please check on screen help for more information.     
    What is the limit that is being referred to here? Is it independent of the LMS device licence? Where can I see how many "network adapters" LMS is monitoring? I have approx 900 devices being managed by LMS on a 1500 device licence. I am running LMS 4.2.2
    Any light you could shed on this would be appreciated
    Thanks,
    Mark         

    I've come across this a few times. I did not find a solution. It went away with a reinstall.
    What seems to happen is that somehow DFM puts all the device interfaces in a managed state.
    It should not.
    It should only manage the ports and interfaces that connect to another managed device.
    There is a hardcoded limit of 40.000 managed ports in DFM.
    Suspected situations:
    On one server where I found this the system locale that I put to us-english, was somehow put back to be-french. Maybe even during the installation, not sure who or what did this.
    On another server the anti-virus which I  had turned off, was turned back on during installation,probably by a policy server.
    Cheers,
    Michel

  • 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 4.2 Fault Manager Issue

    Hi All,
    We are seeing many Unidentified traps on the DFM for multiple devices. 
    274.              008ZETI      Active          InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9       04-Feb-2015 01:59:28                    NA
    275.              008ZETG    Cleared      InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9       04-Feb-2015 01:59:03                    NA
    276.              008ZETA     Active          InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:2 EnterpriseOid:.1.3.6.1.4.1.9.9.109.2            04-Feb-2015 01:58:22                    NA
    274.              008ZETI      Active          InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9       04-Feb-2015 01:59:28                    NA
    275.              008ZETG    Cleared      InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9       04-Feb-2015 01:59:03                    NA
    276.              008ZETA     Active          InformAlarm                   Mumbai_6509-1          Mumbai_6509-1: Unidentified Trap Generic Trap:6 Specific Trap:2 EnterpriseOid:.1.3.6.1.4.1.9.9.109.2            04-Feb-2015 01:58:22                    NA
    Regards,
    Channa

    Hi,
    The unidentified trap message in fault manager is expected when LMS receives a trap that is not in the list of traps that the fault manager is capable of processing.
    Here are the traps that fault manager can process:
    http://www.cisco.com/c/en/us/td/docs/net_mgmt/ciscoworks_lan_management_solution/4-2/user/guide/lms_monitor/lms_mnt/TrapFwd.html
    The SNMP traps are only processed by the fault manager and as per the document above the ones that will be identified are pre-defined and the list cannot be modified.
    Clearing an Unidentified Trap
    You can manually clear Unidentified Traps from LMS. To do this:
    Step 1 Select the Unidentified Trap and click Clear.
    A message appears prompting you to confirm the clearing.
    Step 2 Enter your user ID.
    This will be used as a reference to identify who cleared the Unidentified Trap.
    Step 3 Click OK to confirm.
    The Unidentified trap is cleared.
    To retain the trap click Cancel.
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • 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

  • LMS 3.2 not forwarding SNMP Traps

    I am using LMS 3.2 and under DFM... Notification Services... SNMP Trap Notification, I have a Subscription set up to forward Traps to Unicenter 11.1.  I have tried a combination of sending Alerts and Events, Critical and Informational, Active and Cleared messages.
    At this time I have it set to send:
    Alerts Informational and Cleared
    Events Critical and Informational, Active and Cleared.
    Every Trap that is forwarded from LMS I get in the Unicenter console Twice.   Also, I occasionally get a clear in Unicenter, but normally clears are not being forwaded.
    Any ideas on this issue?
    Thanks
    -Scott

    You should first install the consolidated DFM 3.2 patch from http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=3.2.0&mdfid=282640771&sftType=CiscoWorks+Device+Fault+Manager+Patches&optPlat=Windows&nodecount=2&edesignator=null&modelName=CiscoWorks+Device+Fault+Manager+3.2&treeMdfId=268439477&treeName=Network+Management&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y (patch for CSCta56151).  If the problem persists after that, post the NMSROOT/log/dfmLogs/NOS/nos.log after reproducing the problem with a new event/alert.

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

  • 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 4.0 Live Graph Request Timeout

    Hi All,
    I try develop my new LMS 4.0, I already discovered my devices. But I got error when I try to run live graph. In LMS, live graph / histograph detect my devices is "request timeout". Actually, LMS can reach all devices without RTO ( I try ping my devices from LMS Server, it works well).
    I also attach my HUMLivegraph.log

    Joerg,
    What kind of devices are they that are being questioned?
    Make sure Fault Management in 4.0 supports the devices.
    Rob

  • 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

Maybe you are looking for