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

Similar Messages

Hp system insight manager-device discover issue

Hi,
I have recently installed hp System Insight Manager 7.4. But I can't discover any hp device. The system did not respond to SNMP. when discover any hp device then System Insight Manager showing error:
Major: The system cannot be identified properly for HP SIM to manage;
              unable to get one or more of the following: model, serial number or
              unique identifier (UUID). For management processors, verify the
              system is running the latest firmware. For Linux based operating
              systems, you must have dmidecode installed, enable the
              PermitRootLogin and PasswordAuthentication in sshd, and use root
              sign-in credential. For HP-UX, verify the sign-in credential. For
              Windows, check if WMIMapper is configured correctly on the CMS and
              verify the sign-in credential.
Any ideas on a fix for this?
Thank you,
Nahid

I know there might be issues with cimserver and different versions of SMI-S solutions. SAN-OS 3.2 uses 1.1 and 3.3 and above uses 1.2. The changes are considerable and can make some SMI-S system not work well. I don't know if NX-OS is supported yet.
I don't use HP SIM so I really can't say for sure but its worth checking on what is supported.

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.

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.

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

My iPhone 5S has not connected to 4G LTE service in the last few days? Is there an outage/issue with 4G in my area (Pittsburgh) or is this a device specific issue?

My iPhone 5S has not connected to 4G LTE service in the last few days? Is there an outage/issue with 4G in my area (Pittsburgh) or is this a device specific issue?

JHblues Let's get your data working again. There are not any reported issues in the area. Try this step: http://vz.to/1kUSSk2
Sheritah_vzw
Follow us on Twitter
@VZWSupport

The Ultimate Guide to Resolving Profile and Device Manager Issues

The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
Hello,
I have been plagued with Profile Manager and Device Manager issues since day one.
I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
(Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile and Device Manager may need a Code Signing Certificate.
The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
I shall outline a sensible strategy:
1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
2. Start the server fom the clone and shut down ALL services.
3. It may be sensible to set up a root user access.
4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
Erase database:
sudo /usr/share/devicemgr/backend/wipeDB.sh
7. Note your Directory (diradmin) password for later if you want to re-use it.
8. Open Open Server Admin and demote OD Master to Standalone Directory.
9. In Terminal delete the old Certificate Authority
sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
This step is crucial because else re-building you OD Master will fail.
9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
11. Go back to Workgroup Manager and re-import users and groups.
NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
If the home directory has not been defined you cannot login from a network account.
13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
sudo serveradmin stop devicemgr
sudo serveradmin start postgres
sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
sudo serveradmin start devicemgr
14. You can now switch back on your services, including Profile Manager.
In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
16. Check that Apple Push Notifications are set.(you easily check if they are working later)
17. You may want to re-boot OS Server from the clone now.
18. After re-boot open Server App and check that your server is running well.
19. Delete all profiles in System Preferences -> Profiles.
19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name should read "Trust Profile for...) and underneath in green font "Verified".
21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
Now enjoy Profile and Device Manager !
Regards,
Twistan

HI
1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
also make sure that u have the message processing role
Hope it clarifies ur doubt and resolve ur prob
Regards
Prakhar

Apple iPod USB Device driver issue on Win XP - syncing shuffle 2nd gen.

Hello fellow iPod shuffle users. Any of you run into this problem using the following configurations? Any advise/recommendations/workarounds much appreciated as I've burned 3 days on this issue and I'm still stonewalled.
I personally think it's a device driver issue/bug and am searching for a way to update my Apple iPod USB device driver for Win XP. Two brand new ipod shuffles (received for Christmas 2008) are both behaving this way, so the problem most likely points to a global software issue more-so than to shuffle hardware issue.
PROBLEM STATEMENT: Driver data i/o streaming issue does not allow shuffle to sync data with iTunes after initial sync (i.e. reading the content of the shuffle is good, but writing modified content fails). Posted error message "The ipod ... cannot be synced. Required disk cannot be found". After cracking the hood on my device driver, the problem seems to point to the Apple iPod USB device driver for Win XP. Driver will recognize the shuffle and read to it, but subsequent write attempts will result in device driver balks that "this device cannot start (code 10)".
ATTEMPTED WORKAROUNDS:
*Read All "How to Get Started Manuals" to make sure I was using the right technique for syncing my two shuffles from within iTunes... tried and failed
*Ensure only one shuffle was plugged in at a time (saw notice that two shuffles plugged in at the same time is not yet a supported config)... tried and failed
*The 5 R's as recommended by Apple Support... tried and failed.
*I've tried all 3 built in USB ports on my Lenovo T60. no love... tried and failed.
*Per discussion board: From Window's Device Manager-> Scaned for new hardware while shuffle was syncing...tried and failed.
* Per Discussion board: From Window's Disk Management -> Ensured shuffle came up as a FAT32 filesystem... connection tore down as quickly as windows recognized it.... tried and failed.
*From Windows Software config utility: Ran repair to re-install itunes 8... same results.
*From Windows software management utility: Uninstalled and reinstalled itunes 8... same results.
Hardware: IBM Thinkpad/Lenovo T60. Using build in k/b & no external mouse. Has 3 USB built in ports.
Software: Windows XP Pro SP2/iTunes 8.0.2/shuffle (2nd gen) driver 1.0.4 (same behavior using the original driver 1.0.3).
Apple iPod USB Device properties:
Driver Provider - Microsoft
Driver Date - 7/1/2001
Driver Version - 5.1.2535.0
Digital Signer - Microsoft Windows Publisher

Hi. Ive got pretty much the same problem.... Got a new shuffle for christmas..having real problems syncing with itunes. Funnily enough I managed to get 25 tracks on it but then it just stopped. error message says " The ipod shuffle cannot be synced. The required disk cannot be found." Ive done restore, and downloaded a reset utility thingy to try but still no joy.

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 ~]#

LMS 4.1 Energywise Endpoint issue

I have 10 switches as members of the same, local, energywise domain. When I perform a show energywise neighbors on any of the given switches, they all appear. If i perform show energywise children on a given switch, i see the children of that switch.
When i attempt to "Collect Endpoints" the collection is a success, but my 10 switches only show 2 endpoints, which are 2 of the 10 switches that are configured as a stack. When i remove that stacked 3750G from the energywise domain, it still only shows 2 endpoints, but now they are 2 other switches that are configured as a stack.
Is it that LMS 4.1 has difficulty detecting endpoints in a group where Stack switches are used, or am I missing something in my config? LMS 4.1 says it "knows the secrets" and has not had a single Energywise query error out, so i can only assume its gathering all the information its supposed to be, but somehow it never detects any of my actual endpoints, only the 1st set of stacked switches in the group.

Hello,
Are you sure that the LMS support the config collection on these devices ?
Check on this link :
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html
If yes, it means that you have a problem for the file transfer... I would suggest to debug like this :
1) Check the credentials (Inventory->Job Browser->Device Credential Verification Jobs, then create a new one)
2) Is it possible to do a tftp from the device to the LMS ? (If the config is done by tftp)
     Create a tmp file on /tftpboot on LMS
     Copy the startup or running file from the device to the LMS with the name of your tmp file (it is not allowed to create a file on the LMS with TFTP)
3) Do a sniffing of the traffic between the LMS and the device in order to see what happen
     Go on :1741/cwhp/PacketCapture.do">http://:1741/cwhp/PacketCapture.do
BR

Multiple RDS Device CALs Issued through Windows 2003 RDS Hosts

Environment
Windows 2012 R2 RDS license server issuing device CALs
5 Citrix farms (PS4, PS4.5, XA5, XA6, and XA6.5)
Symptoms
- RDS device CALs issued through the PS4/Windows 2003 R2 and PS4.5/Windows 2003 R2 servers show the Citrix server name in the Window 2012 R2 RD license manager console instead of the workstation name (See below).
- The PS4/Windows 2003 R2 and PS4.5/Windows 2003 R2 servers are issuing a large number of device CALs to workstations. For example, we have two PS4/Windows 2003 R2 servers that publish a single application. There are 20 users
of the applications with dedicated workstations that should all have a device CAL, but everyday I see device CALs being issued from these servers (See below).
Any help would be greatly appreciated. Thank you.
Scott

Hi Scott,
Thank you for posting in Windows Server Forum.
Have you find any Error\Event Id for this case?
From the description it appears that there is some misconfiguration for redirecting the server during load balancing the device CAL among the server and that’s why device is getting misplaced. You can please relook at configuration for License server with following
article.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

I have not been able to stay connected to Internet since upgrade to os 7. Other devices no issues just iPad 2. HELP

I have not been able to stay connected to Internet since upgrade to os 7. Other devices no issues just iPad 2. HELP, please and thank you.

Hey Elder25,
I would troubleshoot these Wi-Fi issues you're encountering while using your iPad by following the steps in this link:
iOS: Troubleshooting Wi-Fi networks and connections
http://support.apple.com/kb/TS1398
Welcome to Apple Support Communities!
Regards,
Delgadoh

Ciscoworks LMS 4.0 – Fault Device Details Issue

       We currently use Ciscoworks LMS 4.0 but when I go into, Monitor > Fault Settings > Setup > Fault Device Details
       I get the following message (see attached document with screenshot) and being a LMS newbie am unsure what to do? As have tried to search for this
       file but no luck.
       So thanks in advance for any advice.

Check if the fault management rediscovery page shows device as discovered and known or does it have any errors?
Are you able to generate any fault management reports and view other pages?
Just try to reboot the server/restart daemon to see if it is goes away.
Else it is mostly corrupt FM DB. Which would need to be re-initialized.
Fault Mgmt reinitialize is very simple task, which doesnt removes a lot of data, except past 31 days of FM history and custom notifications, if configured.
Thanks
Vinod
**Rating Encourages contributors, and its really free. **

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 4.2 Device Discovering issue

Similar Messages

Maybe you are looking for