LMS 3.1 - CV and RME 4.2

Answered Question
Aug 7th, 2009

1. while clicking the Software summary in RME i get the following error.

HTTP Status 500 -


type Exception report


description The server encountered an internal error () that prevented it from fulfilling this request.












note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.


Apache Tomcat/5.5.17

2. In CV my 2960 switches ports are swapped. (fa0/3 shows conf for fa0/1). IOS is 12.2(25)FX

Correct Answer by Joe Clarke about 7 years 6 months ago

No. The patch was for inventory collection. This problem is with reporting, and the contents of the RME database.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Joe Clarke Sun, 08/09/2009 - 10:13

1. This points to a problem with your RME inventory. There is a device in RME which doesn't exist in DCR. The invreports.log will reveal the problem device, but you will need TAC's help to remove it from the database.

2. This is actually a conflict between the older version of switch code, and the new Cat2960 CiscoView package. The bug is CSCsj23639. Essentially, you need to upgrade the switch to 12.2(25)SEE3, 12.2(35)SE1, or 12.2(37)SE (or higher) to fix this problem.

Rajiv Dasmohapatra Sun, 08/09/2009 - 10:26

1. Thanks. I will take it from here and will get back to u if i face anything more.

2. but the bug says "Cisco IOS software 12.2(25)FX is not affected by this problem". so i am not sure why u suggest upgrading.

Joe Clarke Sun, 08/09/2009 - 10:30

The problem is a conflict between the package and the switch code. Essentially, the Cat2960 team changed the way the ENTITY-MIB behaved in newer versions of code (i.e. after 12.2(25)FX). So, the CiscoView developers updated the package code to handle this. Unfortunately, the two ENTITY-MIB schemes are incompatible. So, if you have 12.2(25)FX, you need to run an older version of the CiscoView Cat2960 package (which you can no longer do). Therefore, you must move forward in your switch code in order to catch up with CiscoView.

This problem has already been seen by two other customers, and an upgrade fixed them both.

Rajiv Dasmohapatra Sun, 08/09/2009 - 10:59

1. one more thing. i recently patched for the bug CSCsx58694. By any chance can this be the source of the issue.

2. thanks this cleared my doubt.

Correct Answer
Joe Clarke Sun, 08/09/2009 - 11:15

No. The patch was for inventory collection. This problem is with reporting, and the contents of the RME database.

Joe Clarke Sun, 08/09/2009 - 21:26

No. The problem is that the DCR ID in the RME database no longer exists. DCR IDs always increment, and are never reused. Database surgery will be required. Alternatively, you can reinitialize the RME database, but that will cause you to lose all of the RME data you have collected thus far.

Rajiv Dasmohapatra Mon, 08/10/2009 - 01:42

I reinitialised the database. Manually imported the devices from DCR. I noticed that when the devices are less. it works fine. but as the number of devices grows, it seems to have a problem.

pl help.


This Discussion