Device discovery failure in ANM

Anyone familiar with this error:
Device discovery failed: For input string:"1/0"
I am receiving it when attempting to import a new chassis into ANM. All of the credentials are correct.

Number one error with ANM 1.1 installs has been not having SSHv2 configured on the Supervisor (and the subinterfaces ANM may use to reach that module). Since ANM is managing the ACE, which in turn is often managing e-commerce applications with SSL and SSH connections, not having the control interfaces at the same level of security was undersirable.
ANM 1.2 is being updated to allow the operator to start off without SSHv2, though this will be strongly discouraged for production operations.
DK

Similar Messages

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

LMS 4.2 discovery failure

Hi
I have Cisco LMS 4.2 installed i was using SNMP V2c for polling my devices. After i turned on SNMPv3 all devices are reachable and even when i make credentials check it's ok, but the issue when i access any device from search pane it shows me in the collector status " Discovery failure"
Steps i made to troubleshoot but not succeeded :
1. Rediscover Devices
2. Modify SNMP timeout & retry settings
Devices: Catalyst 2960 , Catalyst 3560
I've attached a snapshot of collector error
Please help
Thanks

1. Please refer to the context-sensitive help when you get to this step. It will give you a page with very detailed file formats and fields that are used (see screenshot below from my lab server). That page is also in Chapter 4 of the Inventory Management guide online.
2. Device adjacencies are determined via a correlation of various MIB variables including CDP neighbor details and other details. I recommend you read through Joe Clarke's document on understanding LMS discovery.
One thing to note is that is is best to have the IP addresses of the devices in DNS. If that is difficult for whatever reason, the first create a local hosts file with the devices. You will get better results if the device IPs resolve to host names.

This device cannot start. (Code 10) Status Device Power Failure for Intel (R) Audio Display

Hi I just bought HP Envy M7 Sleekbook last week and upgraded from 8.0 to 8.1 for Windows 8.
Now I have no sound and this is the error message I get:
This device cannot start. (Code 10) Status Device Power Failure (for Intel (R) Audio Display)
under Sound, Vieo and Game Controllers in the Device Manager.
Anyone else having this issue after upgrading?
Getting a new lappy is stressful enough but to alreay have issues is ridiculous
If the upgrade is not the issue could something have happened in transit? (I have an issue with the way Best Buy packed it for shipment and wonder if it could have been compromised)
Any help is appreciated. Or should Ibe taing this back to best buy and have them address it?
Thanks
Pam

Ahmed, if your HP Envy has an Intel processor chances are it will be necessary to download new drivers for both sound and chipset due to compatibility issues with Windows 8.1. After 4-1/2 hours on the phone with various technical agents and a lot of frustration I finally got one who had the knowledge and training to resolve my issue. I believe he downloaded the new drivers from the HP support site. Good luck!!

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

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

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.

Device Descriptor Failure 8.1 and 8.0 reverted USB error

Hello,
After windows 8.1 update through windows update service Iam experiencing unrcognized usb device ERROR for all brands and devices of usb thumb drives and dynex and microsoft wireless mouse , dynex plug in mouse. Error defined as Device Descriptor Failure.
After looking the issue up Im told windows 8.1 has issues with usb devices that are 3.0 ready. I have tried 3 different brands of thumb drives and two brands of wireless mouses and my usb drive will not recognize anything the same error.
I tried uninstalling the drivers and reinstalling this did not work. I reverted back to windows 8 from 8.1 and the issue did not change, all devices worked properly before windows 8.1 upgrade. Several other similar reports all over the web.
please help
Lap Top Satelite C885D
recent updated operating system to 8.1 through windows update,

I think I solved this, at least for my machine. Lone_Wolf's suggestion about the fast boot possibly being an issue got me to poking around my bios a bit more. Under "Advanced CPU" I found another boot setting called "Boot performance mode" that was set to "Turbo" - what exactly that means I don't know. The little info box says that "Boot Performance Mode" is used to "Select the performance state that the BIOS will set before OS handoff" - again, not really clear what that means.
However, switching it from "Turbo" to "Max Non-Turbo Performance" has (so far) solved this problem. Not sure if it's just a coincidence and this will crop up again, but so far after several reboots I haven't had the described issue occur again. It's still not clear to me why this issue started all of the sudden, as I haven't made any changes to my bios settings in many months.
If anyone has any insight to what these settings are actually doing I'd be interested to know (brief googling hasn't turned up much). Asus Z87 Pro mobo, if that's relevant.
Marking as solved for now, thanks for the help.
Last edited by dgalt (2015-06-16 19:59:45)

Scsi device discovery in Cisco MDS switches

I was using this device discovery to find out how many luns can be seen on that server.
I tried to use discover scsi-target command and it does not give much useful information. and I do not want to add the OS WWNS on my LUN security in addition to HBA WWNS for the host group on the array end.
The problem that I am having is that I can see 7 LUNs out of 9 when I connect to Cisco MDS where as in brocade I can see all the LUNs.
I checked the LUN security and zoning and everything seems to be correct.
If Cisco SAN OS has commands where by I can see what LUNs can be seen on the switch, that would be really helpful. But It looks like LUN/LDEV info cannot be seen through discover command.
Please let me know how to troubleshoot this problem
Thanks

In the array, I tried to add switch wwn to the LUN Security and zoned the same switch wwn on the MDS. Is there anything I am missing. Thanks in advance
But still I could not see any LUNs. When I do discover command, NLUNS shows 0.
and the command sh scsi-target lun os win shows nothing.
discover scsi-target vsan 21 fcid 0xea000b os win
VSAN: 21 FCID: 0xea000b
PRLI RSP: 0x01 SPARM: 0x0012
SCSI TYPE: 31 NLUNS: 0
Vendor: HITACHI Model: DISK-SUBSYSTEM Rev: 5007
Other: 7f:00:03:12:cf:00:00:02

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.

Device discovery failure in ANM

Similar Messages

Maybe you are looking for