Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Basic LMS Troubleshooting
The CiscoWorks LAN Management Solution (LMS) is a collection of powerful management applications that provide configuration, administration, monitoring, fault detection, and troubleshooting tools for campus networks. It includes applications for managing LAN switching and routing environments. Cisco LMS provides a centralized system to share device information along the network, increasing the manageability of the network. The traffic management features will keep the load balanced across the network and reduce network latency. Cisco LMS also has step-by-step wizards to help you quickly set up or troubleshoot your network.
Often you face many issues regarding LMS such as live graph not working, device not discovering and many more. This document shows you a basic/initial troubleshooting steps you can take before opening a TAC case.
1.First try to ping the device in concern from the LMS and vice versa. Check for any latency/packet drop related issue between the devices.
2.If your ping is Ok, then you can check for SNMP reachability between the LMS and your device.
Basically there are two methods to do so:
SNMP walk from the LMS :
SNMP walk allows you to gather SNMP information.
From the LMS command line try to execute the below commands.
If for this query you are receiving the below response, then it means that the SNMP reachability is through.
iso.18.104.22.168.22.214.171.124 = OID: iso.126.96.36.199.188.8.131.524
But in case it shows as Timeout: No Response from 10.171.18.181 then it indicates there is some issue with the SNMP reachability.
In this scenario you could check for two things:
1) Check whether the SNMP configuration done in the device is correct (community string should be same in both LMS as well as device).
2) Check the access-list if any configure in your snmp community command
snmp-server community XYZRO RO 10
In this command 10 is the ACl that has been specified for the SNMP.
Check whether the ACL is denying any LMS IP. If it is doing so then please correct it.
3) If any firewall in between the LMS and the device then you need to open udp/161/(snmp) from your LMS-server to all your devices, and udp/162(snmp-trap) from your devices to your LMS-server. For testing ping responce from LMS to ICMP or vise versa you also need to open for icmp in both directions.
By using troubleshooting tools in LMS GUI:
Troubleshooting workflow in LMS collects information from the network and helps you to overcome network management challenges.
• Go to the following mentioned path Monitor > Troubleshooting Tools > Troubleshooting Workflows
• Select the device diagnostics and enter the IP address of the device you want to do diagnostic check.
• Keep the number of hops as 1 and click on troubleshoot.
• You will get all the details of ping, snmp v1/v2, ssh, telnet for the device you have entered like whether the result is pass or fail.
• Please follow the steps mentioned above if you observe any ping or snmp reachability issue.
3. After following the steps 1 and 2 also if the issue persists (like live graph not working, device still showing unreachable) then it might be possible there are some LMS processes that might have got hung. So to clear that you need to restart the ciscoworks daemon manger services. You can do that it in two ways.
• From the LMS Windows server goes to run and type in services.msc. In that list of services you will find a service named ciscoworks daemon manager. Try to stop and re-start that service.
• From the command line of LMS windows server, type the below commands:
net stop crmdmgtd , to stop daemon.
Then wait 5 minutes until all processes are stopped.
net start crmdmgtd , to start the daemon.
Then wait 15 minutes until all processes are up.
The second option is the preferred method of restarting the services, which is recommended by TAC.
4. The next step is to delete the device from the device inventory and adding it again. For deleting the device from inventory please follow the below mentioned steps.
• Go to the CiscoWorks home page and select Inventory > Device Administration > Add / Import / Manage Devices. The Device Management page appears.
• Select one or more devices from the Device Selector and click delete. You can search for the IP/Name of the device you want to delete.
• After clicking delete, a Delete Devices Confirmation dialog box opens with the following details:
Number of devices selected for deleting.
Number of devices that are managed by applications in the current DCR domain.
• Click on Delete all the device(s) selected and click on Continue.
All information about the selected devices is deleted from DCR. There may be few devices that are deleted from DCR. A message appears stating that the devices are deleted successfully.
To add the device back in the DCR/Inventory please follow the steps mentioned below:
• Go to the CiscoWorks home page and select Inventory > Device Administration > Add / Import / Manage Devices.
• Click Add. And then select type as Standard.
• Enter the Device IP address, the host name, domain name, the device display name, and the device type in the corresponding fields.
• Enter the following credentials in the Standard Credentials page. Primary Credenials(You can ask site team to enter credentials). Also enter the enable password.
• On clicking next you will get a SNMP credential page. Please enter the snmp community string that you have entered in all devices.
• You can skip the http credential page and click on Finish. A message appears that the devices are added successfully in DCR.
5. After deleting and re-adding the devices in the DCR you may have to restart the services once again (Step 3).
If even after performing, all the above mentioned steps, if you are facing the issue the you can take PCAP trace on the LMS machine and try to analyze for any unexpected messages or errors.
Lastly if everything fails you can open a TAC case as there is possibility of LMS hitting a bug or it might need some deeper analysis.