On our CiscoWorks 2000 installation, running on Solaris with LMS3.2 and RME4.3.1, we noticed a few weeks ago, that the job "Inventory Collection" needs more and more time to finish. At the moment the job execution time is as high as 8 hours, compared to 3 hours before. When we look at the network traffic during job execution, we see after the collection phase (~3h) several hours with no traffic together with a very high CPU load. I mean to remember that this job used to complete around 15 minutes after data collection phase. Restarting the application and rebooting the system didn't help.
When we look in to the IC_Server.log, we find devices with a completion time of over 20'000 seconds. Increasing from day to day.
Example from log: [ Wed Jun 08 13:34:15 MEST 2011 ],INFO , [Thread-43],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,498,Total time is 26832 seconds for .....".
Affected devices are Cisco Nexus 5548P. We tried to delete/add these devices. That helps for a few days, then the runtime starts to increase again.
Are we hitting a bug? And is it possible, as a workaround, to exclude devices from only the Inventory Collection?
Listen: https://smarturl.it/CCRS9E18Follow us: https://twitter.com/CiscoChampion Reaching the height of your career is no simple feat. It often requires a combination of pursuing the right education, building the right professional network and being ...
In a typical production SD-WAN deployment, we would probably have many remote sites connected via many different Internet connections to a centralized data center or a regional hub. In most regions in the world, Internet providers will always use some typ...
Listen: https://smarturl.it/CCRS9E16 Follow us: https://twitter.com/CiscoChampion
For all end-users across Cisco’s ecosystem, counterfeiting presents serious risks to network quality, performance, safety, and reliability. It is dangerous becaus...