RME Device Collection failure/UserTracking Hostname

A couple of months ago I upgraded our 2 old 6500 to a pair of 6509 running as a Virtual Switching System. Now I am having 2 problems that I hope are related. The first problem is that RME fails when it tries to do an inventory. The message I get is: "Failed (Device Collection Failed. Device side issue)."
I'm not sure what this means. All my credentials are correct, and this seems to be the only thing failing.
The next problem I'm having is since I upgraded to the 6509 VSS, User Tracking no longer pulls the device hostname from DNS. User tracking still works with MAC & IP address, just not with the hostname anymore.
Any ideas?
Thanks

RME 4.2.0
IOS Version 12.2(33)SXI
[ Tue Dec 29 20:26:51 CST 2009 ],WARN ,[Thread-22],com.cisco.nm.rmeng.util.logger.XDILogger,67,com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatSwitch.ContainmentAGI_ENTITY_Mib,g$eval,140,com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatSwitch:ContainmentAGI_ENTITY_Mib:g$eval:populating ContainmentAG failed for Entity's AGI, falling back to Cisco-STACK-Mib AGI...
[ Tue Dec 29 20:26:51 CST 2009 ],ERROR,[Thread-22],com.cisco.nm.rmeng.util.logger.XDILogger,57,com.cisco.nm.xms.xdi.SdiEngine,initAndEvalAGIs,385,rp Software (s72033_rp-IPSERVICESK9_WAN-M)
[ Tue Dec 29 20:28:40 CST 2009 ],ERROR,[Thread-22],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,721,Exception for device 172.21.90.1 is
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:711)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NumberFormatException: rp Software (s72033_rp-IPSERVICESK9_WAN-M)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.CiscoVersionString.parseVersionString(CiscoVersionString.java:154)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.CiscoVersionString.(CiscoVersionString.java:86)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.compareVersions(ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.java:139)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.iosVersionCheck(ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.java:201)
at com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatSwitch.ContainmentAGI_ENTITY_Mib.g$eval(ContainmentAGI_ENTITY_Mib.java:147)
at com.cisco.nm.xms.xdi.ags.ContainmentAGI.g$eval(ContainmentAGI.java:21)
at com.cisco.nm.xms.xdi.SdiEngine.initAndEvalAGIs(SdiEngine.java:383)
at com.cisco.nm.xms.xdi.SdiEngine.request(SdiEngine.java:309)
at com.cisco.nm.xms.xdi.SdiEngine.getDevRepr(SdiEngine.java:302)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:531)
... 1 more
[ Tue Dec 29 20:28:40 CST 2009 ],ERROR,[Thread-22],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,769,Unknown Exception
java.lang.NumberFormatException: rp Software (s72033_rp-IPSERVICESK9_WAN-M)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.CiscoVersionString.parseVersionString(CiscoVersionString.java:154)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.CiscoVersionString.(CiscoVersionString.java:86)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.compareVersions(ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.java:139)
at com.cisco.nm.xms.xdi.pkgs.LibInventory.ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.iosVersionCheck(ImageAGI_CISCO_ENHANCED_IMAGE_HelperMethods.java:201)
at com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatSwitch.ContainmentAGI_ENTITY_Mib.g$eval(ContainmentAGI_ENTITY_Mib.java:147)
at com.cisco.nm.xms.xdi.ags.ContainmentAGI.g$eval(ContainmentAGI.java:21)
at com.cisco.nm.xms.xdi.SdiEngine.initAndEvalAGIs(SdiEngine.java:383)
at com.cisco.nm.xms.xdi.SdiEngine.request(SdiEngine.java:309)
at com.cisco.nm.xms.xdi.SdiEngine.getDevRepr(SdiEngine.java:302)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:531)
at java.lang.Thread.run(Thread.java:595)

Similar Messages

Lms 3.1 Device Collection Failure for Cat 6506-E

Unable to pull an updated device collection for a Cat6506-E running 12.2(33)SXI3. Was able to pull one when the device was running 12.2(33)SXH3, but not now. Anyone aware of a bug with the 12.2(33)SXI3 code? All other devices function correctly so I'm guessing an IOS bug, although I got tired of searching for it. Thanks in advance, Ernie

I've just upgraded to LMS 3.2, and LMS still can't inventory my two 6506-E.
I've run an "SNMP Walk" against one device, and it seems to work : here's the first few lines of it :
The following is a SNMP walk of device 10.x.x.x starting from
SNMP Walk Output
RFC1213-MIB::sysDescr.0 = STRING: "Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9-VM), Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Tue 01-Sep-09 22:55 by prod_re"
RFC1213-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::cat6506
EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (803850159) 93 days, 0:55:01.59
And I checked the IC_Server.log... this time it mentions SNMP timeout... I tried bumping the timeout to 20 seconds with 2 retries in Campus Manager.
I've attached my IC_Server.log excerpt.
Thanks for the help!
Alex.

RME 4 - Inventory Collection Failure

I am getting the following RME inventory collection error on 4 devices. These 4 devices were recently added to the network and were all attached to a new radius server. I have tested AAA to the 4 switches and am confident that radius is working as intended.
The devices are a mix of 2950 and 3550 switches.
Here is the error.
RICS0001:Internal Error,unable to process the collected data from the device.
Thanks in advance.

In that case, this is probably CSCsk65355 which should be fixed in 4.1.1. However, 4.1.1 suffers from CSCsm97530. So I would suggest to first upgrade to RME 4.1.1. If you continue to see this, then you can contact TAC and apply patch for CSCsm97530 over 4.1.1.

RME Inventory collection - device sensed, collection failed

Hello, i have this problem with
cisco AP12XX. Some of the AP works fine some not.
I have checked the IOS version on two of them (one working and one not) it is the same version 12.3(7)JA1
Thanks a lot for your help

You are seeing a timeout reading the FLASH-MIB. Increase your SNMP timeout in RME to 10 seconds under RME > Devices > Device Management > RME Devices. Edit the attributes for this AP, then do an inline edit, and change the timeout. Be sure to save then apply the changes on the previous window.
Please support CSC Helps Haiti
https://supportforums.cisco.com/docs/DOC-8895
https://supportforums.cisco.com

Prime Infrastructure 2.0: Inventory Collection - Partial Collection Failure on 2 of 4 VSS WS-C6509-E

Hello,
I've got a strange behaviour regarding the inventory collection for 2 of 4 virtual switching systems.
That means the inventory collection for two VSS is succesfull (inventory collections status = Completed) for the other two systems it is not, see attachments.
The device credentials like SNMP-RW, SSH acces are OK. I've already tried to increase SNMP timout and retries as well as telnet/ssh timout without success
All 4 systems are identical regarding hardware model and software vesion.
HW: WS-C6509-E
SW: 12.2(33)SXJ3
Any ideas or suggestions?
Best regards,
Bastian

TAC and I found a bug, CSCum05301.
May be that is also helpfull for others.
https://tools.cisco.com/bugsearch/bug/CSCum05301/
Symptom:
Inventory collection will fail if following keywords are used as part on description command on the interface config level of IOS device: 1Gbps, 10Mbps etc.
Following error message is visible on the DWC:
Inventory Collection Status: Partial Collection Failure
Collection Status Failed feature(s)
Unable to configure DSL, Serial, POS, Ethernet, Loopback, Virtual-Interface, Tunnel, Vlan, Switchport and Service Module interfaces on ISR, ASR and Switches.
Conditions:
Speed keywords like 1Gbps, 10Mbps etc. available as part of descrption command in IOS interface level.
For example:
interface FastEthernet0/3
description 10Mbps
Workaround:
Use a space character between number and unit keyword, like 1 Gbps.

Prime Infrastructure 2.0 Collection Failure for WLC 5508

Hi,
We have installed prime infrastructure 2.0 as a VM.
I added 2 WLCs (AIR-CT5508) in the device work center.
Both the WLCs are showing as "Managed" but under the collection status it says "Collection Failure".
When I hover over the message it reads:
Other Error: Wireless Controller added successfully but some tables had their records dropped as their key fields failed validation"
Any ideas?
Thanks
Satyaki

Hi Satyaki,
Try to reboot the WLC ,if possible and then check the status of the issue.
Regards-
Afroz
**Ratings Encourages Contributors ****

Prime Infrastructure 2.1 ASA5580- Security Context Partial Collection Failure

I am attempting to add my ASAs into prime but get stuck almost instantly after adding the new device. Prime is able to get the device name and Device type (Cisco ASA-5580 Adaptive Security Appliance Security Context) Admin status shows up as Managed but Inventory Collection Status shows up as "Partial Collection Failure" For more detail it says "feature_image_firewall Unexpected error. See the log file inventory.log for details."
The only failure in inventory.log I could find was
[2014-09-26 12:40:01,868] [ICE Service[ 1]Thread: 20] [inventory] [ERROR] - 192.168.0.19 For device id: 2848866 Feature = feature_image_firewall and Procedure = ImageFireWal failed in time 45 with the following error and continuing with other features: com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
[2014-09-26 12:40:01,868] [ICE Service[ 1]Thread: 20] [ice] [ERROR] - com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
As far as the ASA config goes:
snmp-server enable
snmp-server host management 192.168.10.27 community c!$c0PR!me version 2c
logging enable
logging history 7
snmp-server enable traps
The above config works on our ASA5520s except I still haven't set up the traps right because there isn't any useful information on those devices so I am not sure what I need to change?

My ASA is using DH 1.
For 9.2(1) I read this in the release notes.
Note The ASA 5510, ASA 5520, ASA 5540, ASA 5550, and ASA 5580 are not supported in this release or later. ASA Version 9.1 was the final release for these models.

PI2.1: collection failure with all 2950

Hello
I have all Switches 2950 with The collection status "collection failure".
PI version is 2.1
OID of 2950 is : 1.3.6.1.4.1.9.1.324 : Catalyst295024
Software version is : flash:/c2950-i6q4l2-mz.121-20.EA1a.bin
--> Should be supported by PI2.1
If I hit the detail of the "collection status detail" , I have this error message:
"An unexpected error occured"
# Check the device is in supported device list in deployment guide --> Yes !
# Check the device credentials provided are valid --> Yes !
# Finally if the problem still persists then contact Cisco System's technical assistance center
I tried to change the snmp timeout, and also to use snmpv1.
In the inventory.log, I have this first ERROR message:
[2014-05-14 15:26:42,420] [ICE Service[ 1]Thread: 8] [ice] [ERROR] - java.lang.IllegalStateException: Business key attribute: name on entity com.cisco.xmp.model.managed.vendorSpecificTechnologies.cisco.accessControlList.IpAce is null.
java.lang.IllegalStateException: Business key attribute: name on entity com.cisco.xmp.model.managed.vendorSpecificTechnologies.cisco.accessControlList.IpAce is null.
And finaly:
[2014-05-14 15:26:42,826] [ICE Service[ 1]Thread: 8] [inventory] [INFO ] - Complete inventory for deviceid 2300304 ...
Could you please help me.
Michel Misonne

Leo,
I think you are not correct ...
( to be truth - I hope it ;- ) )
in PI 2.2 the Cat 3550 is listed under the supported devices whereas the Cat 2950, 2955 are not:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/release/notes/cpi_rn.html#pgfId-43885
But the latter are listed as being supported in PI 2.1 (while the Cat 3550 is not...)
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/supported/devices/pi21-supported-devices-list.xlsx?mdfid=284540974
So hopefully it is just a matter of time to get them ALL on the list of supported devices for the current version of PI 2.2 ...
I just saw that for Prime Network (Management SW for Service Providers) they even have Cat 3500XL on the list of supported devices... (but I do not know for which type of management they do support these devives, e.g. config, alarming,etc)
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/prime/network/4-2/supported/vnes/CiscoPrimeNetwork-4-2-SupportedCiscoVNEs.pdf

Inventory Collection Failure Following Upgrade to 3.2

We have 90 Cisco VPN 3002 Hardware clients deployed that we manage using Ciscoworks. Before our recent upgrade from 3.1 to 3.2 all VPN 3002 devices previously inventoried and fetched configs successfully.
Following upgrade this week we are seeing Inventory Collection failures for some (not all) of the VPN 3002 devices.
Not sure if upgrade from 3.1 to 3.2 installs a new device package for this device, but checked following upgrade and there are no Software, Device or Package updates on CCO that we need to install.
I have attached output from IC_Server.log for one of the failed VPN 3002 devices and it looks like the Inventory Collection failure is SNMP related (see attached).
Any idea if we need to upgrade code on the VPN 3002 devices? I tried deleting device from Ciscoworks and readding without success and Config Fetch is working on readded device.

There appears to be a problem getting the ifTable from these devices. It would be helpful to see a sniffer trace filtering on SNMP traffic to one failing device, then on one successful 3002 when performing inventory collection to see if there are any obvious problems. The device is replying with a noSuchName error, but it's not obvious exactly which object is causing the problem.
The other error here is related to the following Altiga objects:
alSepModuleStatsType
alSepModuleStatsState
alSepModuleStatsDspCodeVersion
Again, a noSuchName error is coming from the device.
There were no code changes in the 3.2 device package for VPN3000 devices, so something must be going on with these devices.

Create Device Collection WITH Refresh Schedule using Powershel CMDLets

Hello everyone
I'm attempting to create a PowerShell script to create a device collection and I'm running into a very frustrating issue. I want to be able to set the collections refresh time but can't seem to get it to work. This code here works to create the
collection and tell it to do incremental updates but I cannot figure out how to set refresh time. Everything I've attempted has failed and google seems to be no help right now.
$CollectionName = "Test"
$CollectionQueryValue = 'select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.NetBIOSName in ("Hostname")' $CollectionQueryName = "Direct by Hostname"
New-CMDeviceCollection -Name $CollectionName -LimitingCollectionName "All Systems" -RefreshType ConstantUpdate
Thanks for your help!

I haven't tried it, but the following should work:
$Sched = New-CMSchedule -Start "01/02/2014 1:00 AM"
-DayOfWeek Sunday -RecurCount 1
New-CMDeviceCollection -Name "C1"
-LimitingCollectionName "All Systems" -RefreshSchedule $Sched -RefreshType Both
Torsten Meringer | http://www.mssccmfaq.de

Device Collections vs Reports

Fairly new user to System Center 2012 here, so still trying to learn the ins and outs.
Last Thursday, we deployed new software to every PC in our environment. The deployment uninstalled the old application and installed the new one. The job itself was a success (not bad for my first one!).
Anyhow, I had built a SQL based device collection for each application so that I could monitor how many PCs have each application. Essentially, I wanted to watch one grow while the other declined.
I also built a report for each application based on what Add/Remove Programs is reporting so that I could have something to export to Excel to provide updates to management. We run software scans daily on all of our PCs and 90% physically remain
on the network all hours of the day.
My question is: Why is the device collection showing so many more computers having the new software than the report is? I would think they would both always report the same number. For example, the device collection shows 2021 members with
the new application, however the report shows 1565. The report makes it appear as though the deployment was a failure, but the device collection says otherwise. Today is day 5 so I just find it odd that it's taking so long for the report to catch
up. Maybe I've missed a setting to configure the clients to run an inventory scan daily?
Administration - Client Settings - Software Inventory - Occurs every 1 day effective mm/dd/yyyy 10:00AM.

Yep hardware inventory is the one you want.
Do you really need a software inventory every day?
http://be.enhansoft.com/post/2013/10/03/Slow-Software-Inventory-Cycle-in-SCCM-2012.aspx
You can also force a hardware inventory full / delta with the right click tools by now micro. it's a very good free addition.

Partial collection Failure for nexus 5548UP in PI 2.1

Hi there,
I get "Partial Collection Failure" in the inventory collection status in Prime Infrastructure for all my Nexus 5548UP (8 devices).
i have seen in the PI 2.1 release notes that a bug CSCum16230 which look like my problem has been resolved in PI 2.1 but i continue getting the "partail collection failure"
Would like to know if the bug is still exist or get any other help to solve this problem.
Regards,
Alon.

hello
I have this problem as well...
we've got four N5K-C5548UP. Two with a layer 3 daughter card and two without.
interestingly we see the issue just on those boxes with the l3 daughter cards N55-D160L3-V2 installed...
Any help or ideas are highly appreciated
regards
roman
Sh inventory:
OK:
device-a# sh module
Mod Ports Module-Type Model Status
1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
3 0 O2 Non L3 Daughter Card N55-DL2 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 5.1(3)N2(1c) 1.0 --
3 5.1(3)N2(1c) 1.0 --
NOT OK:
device-b# sh modu
Mod Ports Module-Type Model Status
1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
3 0 O2 Daughter Card with L3 ASIC N55-D160L3-V2 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 5.1(3)N2(1c) 1.0 --
3 5.1(3)N2(1c) 1.0 --

LMS 3.2 RME Device Update failed

Hello experts,
I got a new error on my LMS 3.2 with RME 4.3.1
I can´t install any of the RME Device updates.
e.g. : "Installation failed for product [Resource Manager Essentials] with message : com.cisco.nm.xms.psu.packagemgmt.InstallerException: Repository in use. Another Package Support Updater client session may be modifying device support."
I looked up for a .lock file in my CW dir but there is no one.
NMSROOT/Psu.Lock and NMSROOT/www/classpath/com/cisco/nm/xms/psu/Psu.Lock does not exist.
There are no other .lock files in the CW dir and subdirs.
I attatched a psu.log file. Maybe u will see the failure.
What I tried:
- Restart daemon
- install from cisco.com
- install from local dir
... everytime the package installation failed.
Bye,
Patrick

You will need an identical server (RME 4.3.1) with an updated/healthy package repository. If you have that, you can follow these steps to regenerate maps:
1. Shutdown daemons:
net stop crmdmgtd
2. On the bad server, delete all .zip files under the two RME package repositories:
NMSROOT\www\classpath\com\cisco\nm\xms\psu\pkgs\rme
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\pkgs
3. Copy all of the packages under one of the above locations on the good server to both of these locations on the bad server.
4. Delete your bad rme*.map files under NMSROOT/www/classpath/com/cisco/nm/xms/psu/maps/ and replace them with the good ones.
5. Restart daemons:
net start crmdmgtd

Cisco Prime 2.1- Partial collection failure

Dear Experts,
We are seeing many devices (around 1000+ devices) showing as "partial collection failure". We found this coz of not updated Telnet/SSH Cli username and password. So instead of editing each and every device, is there any way to select all devices and update cli credentials in one shot..?
If someone helps me this option, it will be so helpful.

Hi ,
Other way is to export all the devices , Edit it and then Import it.
Operate >device workcenter > EXPORT device \ BULK IMPORT
Thanks-
Afroz
****Ratings Encourages Contributors ****

Cisco Prime 2.1 - Collection Failure 2950 Series Switch

Hi All,
I am trying to add various devices in the Cisco Prime Infrastructure 2.1, but with the followings I get a message: Collection Failure (Inventory Collection Status).
Cisco Catalyst 2950 24 Switch
Cisco Catalyst 2950G 24 EI DC Switch
¿Why I can't sync this devices?
Kind Regards!
JEFFERSSONQG

Leo,
I think you are not correct ...
( to be truth - I hope it ;- ) )
in PI 2.2 the Cat 3550 is listed under the supported devices whereas the Cat 2950, 2955 are not:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/release/notes/cpi_rn.html#pgfId-43885
But the latter are listed as being supported in PI 2.1 (while the Cat 3550 is not...)
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/supported/devices/pi21-supported-devices-list.xlsx?mdfid=284540974
So hopefully it is just a matter of time to get them ALL on the list of supported devices for the current version of PI 2.2 ...
I just saw that for Prime Network (Management SW for Service Providers) they even have Cat 3500XL on the list of supported devices... (but I do not know for which type of management they do support these devives, e.g. config, alarming,etc)
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/prime/network/4-2/supported/vnes/CiscoPrimeNetwork-4-2-SupportedCiscoVNEs.pdf

RME Device Collection failure/UserTracking Hostname

Similar Messages

Maybe you are looking for