LMS 3.1 /RICS001 - Inventory is failed each time on CS2950

Unanswered Question
Nov 23rd, 2009

Hello dears all,

When we tried to do an inventory on LMS with this switch, CS2950 we've got an error message like " RICS001 - Internal error ........     "

I went on the RME page for CISCOWoRKS where we can download devices packages.

The version 3.1 is only proposed

it seems that 6.0 version is available and should be downloaded for avoid this message.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.4 (5 ratings)
Joe Clarke Mon, 11/23/2009 - 10:28

Make sure this switch is running 12.1(11)EA1 code at the very least.  If not, then an inventory error is expected.  Once you upgrade this switch, the problem will go away.

richard.tetu Tue, 11/24/2009 - 05:26

The switch is running with this version:12.1(22)EA13 - so, it means that this index is up to (11). Bu the error is still existing.

Joe Clarke Tue, 11/24/2009 - 08:41

Post the IC_Server.log after performing an inventory collection for this device.

richard.tetu Tue, 11/24/2009 - 08:59

Thanks Joe,

Please see in attachement the file IC_Server.log. I think that's it one with no debug active as i didn't see any default.

I let you have a look inside

Joe Clarke Tue, 11/24/2009 - 09:00

This is not the IC_Server.log.  Even without debugging, that log would show the error.

jabouaf Tue, 11/24/2009 - 10:24


Could you tell us approximatively when this new release 12.1.(22)EA14 should/could  be available ?

I just checked for some cat2950g-12/48-ei and the lastest release is 12.1.(22)EA13 .



Joe Clarke Tue, 11/24/2009 - 10:27

It is expected to FCS in Q2 2010, so sometime between April and June of next year.

Joe Clarke Tue, 11/24/2009 - 10:31

There is a workaround for this bug in RME.  You can go to RME > Admin > Inventory > Inventory Change Filter, and check the boxes for Image:System Description and Image:Description.  Then inventory should get collected.

jabouaf Tue, 11/24/2009 - 14:08

Hello Joe,

Thank you very much for this workaround, we'll use it (I'm a colleague of Richard who posted this issue).

I wonder is renaming the IOS file would help (to have the name+path shorter), but your workaround is much easy.

Your workaround should be added to the bug's release note.

Best regards,



This Discussion