Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

RME failed config / inventory collection.

Hi all,

have added 3 new devices to RME. Collection station to device is fine (ping / telnet / SNMP get). RME is however unable to collect the config or the inventory. RME output for the config collection:

*** Device Details for sil-vg-comp-sov-1.silver.secure24.com ***

Protocol ==> Unknown / Not Applicable

CM0056 Config fetch failed for sil-vg-comp-sov-1.silver.secure24.com Cause: CM0204 Could not create DeviceContext for 6266 Cause: CM0206 Could not get the config transport implementation for 50.130.240.4 Cause: UNKNOWN Action: Check if required device packages are available in RME. Action: Check if protocol is supported by device and required device package is installed.

The devices are a 3825 and 2x 2800 - which we have a number of already in RME. Also have the Rtr3800 package loaded (have done an uninstall and reinstall for this).

Any further checks for new RME device packages has a null return.

Bit odd really..

Regards,

Marty.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: RME failed config / inventory collection.

Given the errors, I would be more inclined to believe the packages are missing or unreadable to casuser. In either event, unless you know exactly what caused this error to occur, it would be safer to reinstall the application (or even the whole bundle) to ensure that no other files are missing or corrupt. Else you could be chasing errors for weeks or months.

Another solution would be to restore from a known good file system backup.

10 REPLIES
Cisco Employee

Re: RME failed config / inventory collection.

What are the sysObjectIDs for these new devices? What is the error you get trying to collect inventory?

New Member

Re: RME failed config / inventory collection.

Hi Joe,

Inventory collection for the one device at time ran for 5.5 hrs(!) and returned the following:

"Timed out. Make sure that ICServer is running."

ICServer is running fine (now). Nothing jumped out at me from the logs.

OIDS:

1) Cisco IOS Software, 3800 Software (C3825-ADVIPSERVICESK9-M), Version 12.4(8c), RELEASE SOFTWARE (fc3)

sysObjectID.0 '1.3.6.1.4.1.9.1.543'

2) 'Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(8b), RELEASE SOFTWARE (fc2)

'1.3.6.1.4.1.9.1.577'

3) 'Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(8), RELEASE SOFTWARE (fc1)

'1.3.6.1.4.1.9.1.577'

regards,

Marty.

Cisco Employee

Re: RME failed config / inventory collection.

Without seeing the full log with ICServer debugging enabled, I cannot say why collection is timing out. These are supported devices, however.

New Member

Re: RME failed config / inventory collection.

Hi Joe,

ICServer debug attached for latest failed inventory collection.

- Marty.

Cisco Employee

Re: RME failed config / inventory collection.

It looks like you may have a lot of bad RME devices packages under NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/pkgs. SharedInventoryRouter.zip, SharedSwimIOS.zip, SharedInventoryCatIOS.zip, SharedInventoryCatSwitch.zip, and SharedInventoryONS15xxx.zip are all bad or unreadable. On top of that, there are a few devices that appear to have incorrect SNMP credentials in DCR, and thus RME cannot obtain the sysObjectID for these devices.

Given that the packages are bad, if this is not something obvious with permissions, you should probably uninstall then reinstall RME.

New Member

Re: RME failed config / inventory collection.

hmmm - not good JC. Especially as we have a number of customers grouped in RME. What about uinstalling and reinstalling the corrupt packages first?

thanks,

Marty.

Cisco Employee

Re: RME failed config / inventory collection.

Given the errors, I would be more inclined to believe the packages are missing or unreadable to casuser. In either event, unless you know exactly what caused this error to occur, it would be safer to reinstall the application (or even the whole bundle) to ensure that no other files are missing or corrupt. Else you could be chasing errors for weeks or months.

Another solution would be to restore from a known good file system backup.

New Member

Re: RME failed config / inventory collection.

Hi Joe,

so an uninstall and then restore from backup?

Cisco Employee

Re: RME failed config / inventory collection.

If you are going to do a file system restoration, you do not need to uninstall. Just make sure you restore everything. If you are going to just do a CiscoWorks backup, then you will need to uninstall, reinstall, then restoer the backup.

New Member

Re: RME failed config / inventory collection.

Hi Joe - sorry - one more q:

we are going to uninstall and then reinstall RME.

- So we will first export all the customer and device credentials to a csv file.

- then uninstall RME.

- Do we then install RME from the LMS 2.5.1 bundle and then the LMS 2.6 patch and finally any device package updates?

- Lastly import the customer / User Defined Groups.

thanks,

Marty.

209
Views
0
Helpful
10
Replies