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.

Similar Messages

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.

How to Fix Disappearing 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.

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

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

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
========

Device Discovery Error (Lenovo Toolbox)

Today when I went to run Lenovo Toolbox, it would not completely load and would complain that it had a Device Discovery error and to hit ok and restart the application. Has anyone else been running into this issue? When I log in as another user it works fine. Someone elsewhere had mentioned something about Firefox causing the problem, but if it works on one profile and not another I don't see how the two are related.

I have the same problem on my T42p. Installed toolbox version 5.1.5183.17, with Firefox 3.0.8, upgraded from 3.0.7 and problem persists. Have tried with toolbox allowed and not allowed to go online, but halfway through its initial screening, the error appears: Device Discovery Error Your system was busy performing other tasks when Lenovo System Toolbox attempted to collect information. Click OK and restart the application. If the error persists, restart the system.
Restarting does no good. Firefox can be on or off. Same problem.
p.

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.

Device discovery does not work with Yosemite

After updating to Yosemite, my (13-inch late 2010) Macbook Air can no longer find the printer on my home network, although I can print by specifying the printer’s IP address. Furthermore, Airport Utility cannot find my Airport Extreme; it says Device Not Found while acknowledging that the Airport Extreme was previously part of my network. However, the same Mac has no difficulty connecting to the internet through the Airport Extreme. It seems that some device discovery protocol (Bonjour?) is no longer working on that Mac.
I updated our other Macbook Air (11-inch mid 2011) to Yosemite without any issues. It finds the printer on the network, and Airport Utility finds the Airport Extreme.
Any suggestions?

Hi, this is Detective Vdawg, and I came across a similar issue when I updated to Yosemite on my MacBook Pro (Retina, 15-inch, Early 2013). Here is what I did. First, turn off all bluetooth devices turn off your printer and your computer. Wait about 15-30 seconds, then press and hold these four buttons for five seconds: shift, control, option, and the power button. What that does is refresh the hardware components; your settings will remain the same as they were before. After the computer reboots, then everything should be working the way it normally does including your device discovery. If that helps, please let me know; also let me know if it does not resolve your issue for whatever reason. I will be searching for different ways to resolve this problem. If you come across any more issues along the way, I would be happy to help you if I can.

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.

Cisco ANM 5.2 Device Import Issue

Hello,
I have installed ANM 5.2 virtual appliance.
I have an issue importing a Catalyst 6500 device.
When I try to import it, I get the following error:
Device discovery failed: Cannot communicate to the device.
Authentication failure while attempting to connect. Verify the device
type and credentials.
I double verified and the credentials are correct.
I user SSH version 2.
I use the following special carachters in the password:
"!" and space.
I don't use enable password to connect to the 6500 device. The 6500 device has a privilege 15 username.
In ANM, the enable password is a requirement so I just fill in the regular password.
I think the issue is appearing due to one of the following:
1.) The ANM does not support the special carachters I use in the 6500 password.
2.) Then ANM requires enable password, while I don't use enable password in the 6500 switch.
The 6500 runs SXI6 software version.
I can't configure an enable password or configure a test username without special carachters beacause it's against the organization's policy.
Does anyone familiar with this issue?

Hi Ehud,
Please read this link: http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/5.2/user/guide/UG_manage_devices.html
I used this guide without problem.

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

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

CUOM 8.6 - Device Discovery Issue

Similar Messages

Maybe you are looking for