Inventory collection

Team
IN RME inventory collection some of the device inventory arent displayed
Inventory Never Collected and Inventory Recently Failed
Kindly suggest how to rectify this
Thanks

Pick one failing device, then run a new inventory collection for it under RME > Inventory > Inventory Collection Jobs. Then post the IC_Server.log.

Similar Messages

RME 4.3, Inventory Collection doesn't work for 6500

I have a issue with Inventory collection for 6500 devices running IOS 12.2.33 SXI1, fails with a message, "device collection failed"
From IC_Server log i could see SNMP Request timeout exception, so increased SNMP timeout to 10 under device attributes for the device but still it fails.
attacehd is the extract from IC_Server log.
Could anybody help me on this? Thanks

You have not increased the timeout properly. You need to go to RME > Devices > Device Management > RME Devices, and edit the attributes for the required device. Select the device from the list in the left-hand pane to pre-populate the current attributes. Then increase the SNMP timeout to 10, and save the changes. On the previous screen, you will need to APPLY those changes before the 10 second timeout will take effect.

RME 3.2 Inventory Collection Failure with error

Hi,
Inventory collection fails with error is "Timed out. Make sure that ICServer is runningâ. But the ICServer process is running. I enabled debug on could see the following in the IC_Server.log which I'm not sure if it indicates any issues.
I can find the devices in DCR and the devices are classified as Normal in RME.
Series of following message for all the devices
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Request,115,Removing device 181from request 1255347128972
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,163,Removing, 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,171,got device, 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Device,51,Removing request 1255347128972 for device 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,177,Removed2 dev, 175from Priority of the ENUM is : 0
then,
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,89,Adding Device :175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Device,46,Adding request 1255347128973 for device 175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,142,Found dup device in queue: 175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Request,75,Adding device 175 to request 1255347128973
and then the below messages
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called
I highly appreciate any help on this. Thanks

The ICServer process could have locked up which means a full thread dump will be required to see why this is happening. Open a TAC service request, and they can walk you through getting this.

LMS 3.0.1, RME 4.1.1 - Inventory Collection Status displays too many device

Running LMS 3.0.1 with RME 4.1.1 on a Windows box. On the Inventory Collection Status screen I see the following:
Inventory Collection Status No. of Devices
Inventory Collected: 1246
Inventory Never Collected: 0
Inventory Recently Failed: 34
Total 1246
The problem with this is that I only have 668 devices. Is this just a cosmetic issue?

Assuming you're not integrated with ACS, then yes. If integrated with ACS, some of the devices may not be authorized. You will need to check your ACS configuration to make sure all devices in LMS are known to ACS and that your user (and the System Identity User) is authorized to manage them.

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.

LMS 3.2 Inventory collection - Job timeouts after ~5h, all devices "Not attempted"

Hello All,
We have a strange problem with LMS 3.2 regarding Inventory Collection.
This problem started immediatelly after the LMS installation/upgrade (LMS 3.2 was installed on a new server, and LMS 2.6 database migrated to it).
All Jobs finish as failed, with all devices "not attempted".
Job hangs for a five and a half hours and then reports failed status.
The symptoms are the same for scheduled jobs and manually created jobs.
I also have opened a TAC case, but it seems that nothing relevant can be found in the IC_Server.log.
Also, according to a packet capture, it seems that LMS does collect SNMP data from devices after a job is started...
We tried to upgrade RME 4.3.0 to 4.3.1.
One Job immediately after the upgrade was succesful (Inventory was collected for manually selected device), but the next day all Inventory Jobs were failing again with the same symptoms...
Does anyone have a sugestion where to look for a problem trace?
Thanks in advance!
Ragards,
Jasmina

Hi Jasmina ,
Please chech the Existing MDF pacakge :
go to common service > software center > device update >>> check the checkbox for Cisco works common service and click on check for updates
--if there is an Update , please upgarde the MDF version..
--Similarly look for any Available Device Pacakges update for RME , if there are Upgarde all the Device Pacakages ....
--After all of the above Task is done , Now re-run the Job and it still fails then share the IC_server.log again..
Thanks--
Afroj

Inventory Collection problem for RME 4.3.1 LMS 3.2

I recently upgraded from LMS 3.1 to LMS 3.2 and RME v 4.3.1. I have problems with the inventory collection. It will start scanning, but stops after approximately 10 devices. The rest of them will have a pending state. If I stop the collection job and start it again none (0) devices will be scanned. If I restart the ICServer it will result in the first option. That is, it will scan only 10 devices and then stop. I have extended the SNMP timeout to 30 secs and zero retries. Any suggestion would be appreciated

I have read through the dump and cant find anything in particular. Another discovery I've made is that the SNMP walk of an unsuccessful device takes 10 times longer than a successful device. An inventory job on a unsuccessful device only goes into pending and the job never starts.

LMS 3.2 - RME 4.3.1 Inventory Collection never stops (Job Result = pending)

Hello all,
with our LMS-System running on Solaris 10 we have the following problem:
- Inventory Collection never stops after starting
- This can be seen with all devices or 1 device selected
- Config-Mgmt is working
- After re-init of RME-DB the problem persists
In Logfile (IC_Server.log) no problems are shown.
In Job-Logfile only the collection request is shown.
Any help is appreciated
Thanks for your feedback
Lothar

Hi Joe,
with further troubleshooting this problem I discoverd the following.
- Having problems with inventoring certain Cat4000 we requested patch for Bug-ID CSCtb16925 (LibInventory.zip-File).
- Replacing this file with the old one or installing the newest IDU for RME the problem was solved.
It seems that the LibInventory.zip file given with Bug-ID CSCtb16925 is somewhat buggy (maybe in context with device-number) greater
than 1000.
Thanks for your support.
Lothar

LMS 3.2 RME 4.3.1 Inventory collection failing for switches

I have 6 switches that inventory is failing for. They do run the 12.2(33)SXI3 software but I have the CSCtb16925-1.0 patch installed. I've tried to increase the SNMP timeout for the devices but they still fail.
Ideas?
Chris Jasztrab

You did not properly increase the SNMP timeout. Go to RME > Devices > Device Management > RME Devices, and edit the attributes of the device in question. Perform an inline edit. Click on the device name, then change the existing SNMP timeout value to 10. Then save your changes, and apply them on the previous screen. Then inventory collection should work.

LMS 3.1 Inventory Collection fails

I have the same problem as the following post:
https://supportforums.cisco.com/thread/176673?tstart=0&viewcondensed
Also, LMS fails inventory collection every time. I click on the "failed" link from LMS Portal, but the page never comes up detailing why it has failed. This is after I fixed an issue with group policy overwriting the "Logon as batch" setting for casuser. Everything appeared to be up and running normally again, when I noticed the next day that inventory polling/collection is failing. pdshow attatched.
The following error message continues to show up in the rme_ctm.log file:
[ Tue Feb 22 07:40:55 CST 2011 ] URN_NOT_FOUND : urn "JRM" : Not found !!
The last entry in the CTMJrmServer.log file is:
[ Thu Feb 10 10:52:55 CST 2011 ],INFO ,[main],com.cisco.nm.rmeng.jrmwrapper.server.CTMJobManagerServer,publishDaemonOk,99,Called CreateReady file. Return Value 0
I've been blindly trying to chase this down and getting nowhere.

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Hi ,
Great ..
The issue was this Port was blocked 47001, which was blocked . what we did will skip that Port and
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
the ctmregistry should have EssentialsDM on a new port, and the conflict should not reoccur.
Thanks--
Afroj

RME 4.3.1 Inventory collection failing for cisco 3925

Hi,
I've a customer having LMS 3.2 and RME 4.3.1. He has 14 Cisco 3925 routers out of which inventory collection for 2 fails.
Router IOS is: c3900-universalk9-mz.SPA.150-1.M.bin".
Can someone suggest what might be going wrong? Attached is the IC_Server log file for reference.
Thanks in advance,
inner_silence

Hi,
Here are the exception found from the log :-
[ Fri Mar 18 16:28:24 EDT 2011 ],ERROR,[Thread-17],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,729,Exception for device 10.103.251.12 is
java.lang.reflect.InvocationTargetException
    at sun.reflect.GeneratedMethodAccessor12.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:719)
    at java.lang.Thread.run(Thread.java:595)
Caused by: com.cisco.nm.xms.xdi.ags.system.CollectionFailed: java.lang.StringIndexOutOfBoundsException: String index out of range: 2
    at com.cisco.nm.xms.xdi.pkgs.LibInventory.EnergyWise_HelperMethods.getDeviceEnergyWise(EnergyWise_HelperMethods.java:72)
    at com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatIOS.EnergyWiseAGI_ENERGYWISE_Mib.g$eval(EnergyWiseAGI_ENERGYWISE_Mib.java:51)
    at com.cisco.nm.xms.xdi.ags.EnergyWiseAGI.g$eval(EnergyWiseAGI.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:539)
    ... 1 more
[ Fri Mar 18 16:28:24 EDT 2011 ],ERROR,[Thread-17],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,761, Collection failed for the device : 63
com.cisco.nm.xms.xdi.ags.system.CollectionFailed: java.lang.StringIndexOutOfBoundsException: String index out of range: 2
Kindly check if the your device is running the required IOS on the device as per the device supported list :-
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html
There are two 3925 listed with different versions :-
Cisco 3925 Integrated Services Router   --> 1.3.6.1.4.1.9.1.1042 --> 15.0(1)M [RME]. if this is your device then upgrade to
3925 to 150-1.M2
and
Cisco 3925E Integrated Services Router --> 1.3.6.1.4.1.9.1.1144 --> 15.1(1)T
Thanks,
Gaganjeet
If this post answers your question, please click the "Correct Answer" button

LMS 3.2 Inventory Collection Failing

Inventory collection is failing without any detailed error information. I'm attaching IC_Server.log. Example device is 10.79.82.250, towards end of log. I see these messages but not sure what to make of them. SNMP communication is ok and walk of system mib is ok.
[ Fri Dec 11 09:37:29 EST 2009 ],INFO ,[Thread-21],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventorySatellite.SatelliteHelperMethods,isVirtualMibSupported,32,
cisco virtual mib,exception while interpreting cvsChassisMode value
com.cisco.nm.lib.snmp.lib.SnmpValueException: Illegal Access. NoSuchObject being accessed as Integer.
[ Fri Dec 11 09:37:29 EST 2009 ],INFO ,[Thread-21],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventorySatellite.SatelliteHelperMethods,isVirtualMibSupported,32,
cisco virtual mib,exception while interpreting cvsChassisMode value
com.cisco.nm.lib.snmp.lib.SnmpValueException: Illegal Access. NoSuchObject being accessed as Integer.

Go to RME > Devices > Device Management > RME Devices, and edit the device attributes for this device. Change the SNMP timeout to 10 seconds. Make sure you apply the changes you make. After doing that, inventory collection should work.

Inventory collection fails on VSS and 6509 switches

We have approximately 12 devices that are listed as "Inventory Never Collected". When trying to run the collection manually we get errors as shown in the attached log files.
We are running RME 4.3.1 under LMS3.2.
The devices are running IOS versions:
12.2(18)SXF7
Can anyone assist?
Jon

The last error I saw was a timeout issue, and that is a known issue that can be solved by increasing the timeout. With the higher timeout, clear out the IC_Server.log, then run a new inventory collection job and post the new log. You may also need to do a sniffer trace filtering on all SNMP traffic to the device while performing the inventory collection. This should indicate to what value the timeout needs to be set.

Inventory collection fails for ACE module (RME 4.3.1)

I am trying to collect the inventory and ultimately the configurations for my ace modules. When i try to do an inventory collection I get the error
Device sensed, but collection failed
Anybody have any ideas?
Chris

Post your IC_Server.log.
Please support CSC Helps Haiti
https://supportforums.cisco.com/docs/DOC-8895
https://supportforums.cisco.com

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.

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.

Inventory collection

Similar Messages

Maybe you are looking for