LMS 2.6 unable to install or remove device packages

Unanswered Question
Oct 15th, 2009
User Badges:

Hi there,


A few weeks ago I noticed that our 7206VXR routers could not be managed from Ciscoworks (devices were greyed out). This was no problem before. When I tried to reinstall (or even remove) the necessary device packages as part of my troubleshooting process it would fail. At one point I tried to remove all device packages for Ciscoview and RME. This succeeded for Ciscoview, but still failed for RME. I was able to reinstall device packages for Ciscoview, but RME is still a problem. Now there are even more device types in my network that I can NOT manage anymore.


In the attached screenshot you can see that there are more device packages installed under RME than that is possible (I assume this many device packages even don't exist). Before these problems the numbers were equal for Ciscoview and RME.


When I use "psucli" commandline tool to remove all device packages under RME I eventually get an errormessage about a Java OutOfMemoryException and nothing has happened to the administration.


I also have tried a database reinitialization procedure for RME, but this doesn't help.


Any advice/help is greatly appreciated. Maybe there's a way to manually clear the device package administration? I haven't find it yet...


Also, even though I managed to install packages for Ciscoview, I cannot actually view the devices in Ciscoview (can't find applicable device package error message).



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
Joe Clarke Thu, 10/15/2009 - 08:23
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

You cannot purge all packages for RME. This will corrupt your package repository as not all packages can simply be downloaded from Cisco.com. There is a procedure to recover from this, and give you all of the RME 4.0.6 packages, but you will need to open a TAC service request to get it. They will then send you a complete up-to-date package set and instructions to recover the repository.

Actions

This Discussion