cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
797
Views
15
Helpful
5
Replies

RME 4.2 RICS0001: Internal Error,unable to process the collected data...

yjdabear
VIP Alumni
VIP Alumni

Sol 10 with all the latest LMS 3.1 appl and device updates.

System Inventory Collection returns "RICS0001: Internal Error,unable to process the collected data from the device" against 14 devices of the WS-C6509-E (R7000) or WS-C6509-V-E (R7000) variety. Is there something peculiar between LMS 3.1 RME 4.2 and the cat6500-e hardware?

Debug is enabled on IC_Server and InventoryPoller. IC_Server logs are attached to TAC case 610289399.

5 Replies 5

Joe Clarke
Cisco Employee
Cisco Employee

The only error I see in these logs is for 172.18.255.198 which points to an invalid community string in DCR, or an SNMP misconfiguration on the device.

I'm afraid the three IC_Server.log files do not have any info on the 14 devices in question, due to the volume, once debug is on. Is there any way to either increase the size of IC_Server.log or prevent it from rolling over?

TAC's first solution is to delete the devices and re-add them. Does the (re-)addition of devices to the DCR trigger immediate Inventory Collection that'd be logged to IC_Server.log?

Yes, the file size can be increased in NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/util/logger/base.property. After changing the size, dmgtd needs to be restarted.

A delete from RME, then resync from DCR will trigger an automatic inventory collection.

It appears simply deleting the devices and adding them back does get them collected successfully. Maybe it's a side-effect of different/no 6509E support in LMS 2.6 vis-a-vis LMS 3.1. TAC says there's no new bug ID assigned to this issue in RME 4.2, since the above fix works.

Upgrades may still be plagued with the bad data from the older bugs. If you can remove and re-add the device, and get three inventory collections to complete, then you're fine.

Review Cisco Networking for a $25 gift card