Inventory Collection internal command

Which command is used internally to obtain Inventory
Collection? I have seen some targets are not detected....
Thanks

For example, in Inventory I can't see target's as 1000 Base SX SFP or 100Base FXSFP or VWIC2-2MFT-G703 or HWIC-1ADSL . Should they appear? or only devices that supports SNMP? I'm not sure how does it work...
Thanks.

Similar Messages

  • LMS4.0.1 Nexus 5020 - internal error in inventory collection

    Hello,
    2 Nexus 5020 (SysObjId ...3.719) brings internal error in inventory collection as following:
    "RICS0001: Internal Error, unable to process the collected data from the device"
    whereby 2 other devices from same type, same sysobjid are working well. SDT from v401 shows this device as supported.
    What can we do?
    Steffen

    Hi Steffen,
    Try updating the MDF and device packages for RME first and check the issue..
    If you have not applied the below patch before ,kindly apply this :
    Download the Patch for this BUg from cisco.com and apply it ..I hope that should take care of the issue.
    CSCto46927    Psu support changes from CCO to SPRIT
    lms40x-win-CSCto46927-0.zip (For windows)
    lms40x-sol-CSCto46927-0.tar (For solaris)
    Thanks
    Afroj

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

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

  • Cisco MDS 9148 Inventory Collection

    Hi
    I get the following error on an inventory collection of a MDS 9148 (NOS 5.0.4). I have tried deleting and recreating the device.
    RME 4.3.1
    RICS0001:Internal Error,unable to process the collected data from the device.
    [ Thu Dec 30  13:48:46 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.LibInventory.PortInterfaceAGI_RFC1213_HelperMethods,getIfTableEntriesFromDevice,759,Entry speed after if block: 1000000000 Index value : 101191680
    [ Thu Dec 30  13:48:46 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,58,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:populating AssetAG attributes, begins...
    [ Thu Dec 30  13:48:53 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,57,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,64,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:AssetAG Collection aborted com.cisco.nm.xms.xdi.ags.system.CollectionFailedDeviceSensed: java.lang.ArrayIndexOutOfBoundsException: 5 >= 5
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,549,DP time is 20 seconds for 172.23.32.129
    [ Thu Dec 30  13:48:55 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,458,
    java.lang.NullPointerException
    at com.cisco.nm.rmeng.inventory.ics.invdata.containment.ContainmentAGInvData.compare(ContainmentAGInvData.java:103)
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processContainmentAG(InvDataProcessor.java:864)
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:330)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
    at java.lang.Thread.run(Thread.java:595)
    [ Thu Dec 30  13:48:55 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,935, Exception occured in process method while processing: 172.23.32.129 null
    ICSException
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:473)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
    at java.lang.Thread.run(Thread.java:595)
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1191,No Trap
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1203,CALLING SELF TEST
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1207,DONE WITH SELF TEST

    Hi Naem,
    have just read the othre reply's, the intresting bit it is in the MDF.
    - <DEVICE NAME="Cisco  MDS 9148 Multilayer Fabric Switch" MDFID="282867260" CISCOMDFID="282867260">
    <SYSOID OID="1.3.6.1.4.1.9.12.3.1.3.841" NAME="OID:1.3.6.1.4.1.9.12.3.1.3.841" />
    The device adds ok, I just can not run an Inventory but can run a backup !
    Thanks

  • Inventory Collection Failure with LMS 3.2

    Hi,
    I've been running LMS 3.2 with RME 4.3.1.
    Inventory Collection fails while trying to collect data from 7825I Media Convergence Servers running Call Manager 6.1.
    It fails with the following error:
    RICS0001:Internal Error,unable to process the collected data from the device.
    I have tried deleting and adding the device again, but with no effect.
    The Call Manager server has ip 192.168.5.5, here it is the IC_Server.log attached.
    Looking at the log, I see there is some kind of database error, but I don't know how can be avoided.
    Any suggestions?
    Regards,
    Velin

    I have removed the Call Managers from RME, and then re-added them again.
    After that I started a inventory collection job but it failed again with the same error. I've tried some times with the inventory job but it fials every time.
    I read about the bug you've mentioned and it is advised to patch the RME. Since i'm running the latest version, what can i do?

  • Prime failed inventory collection

    Hi
    I am having problems too numerous to mention on prime.
    But i need to get it to try an inventory collection as they last one was nearly a month ago.
    However when i try and get it to do this it fails 
    I am on my menu/default dashboards/device status 
    then under collection summary i go to Schedule and shedule and immediate collection
    It always fails ... why is that ?
    Any ideas at all on this gratefully accepted
    Steve

    Hi Steve,
    Check the status of "pdshow" command
    make sure all the necessary services are running..
    Try to restart the LMS services (net stop crmdmgtd && net start crmdmgtd ) / /etc/init.d/dmgts stop  && /etc/init.d/dmgd start)
    If above does not help share the status of "pdshow" and IC_server.log
    Thanks-
    Afroz
    ****Ratings Encourages Contributors ****

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

  • 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

Maybe you are looking for