After upgrading RME to 4.0.6,
The Inventory Collection jobs are failing with this error:
Can't find resource for bundle java.util.PropertyResourceBundle, key ICSJOB008
The Config Collection jobs are failing some devices with some devices being "Partially Successful" on the VLAN RUNNING config fetch, showing "Failed to establish TELNET connection"
These devices are getting configs collected via SSH, there is no telnet configured for these devices.
They were not failing prior ro the up grade and nothing has changed in the TFTP access to the devices.
Some of devices failing config collection with the "VLAN Running config fetch" are routers.
Looking in the shadow directory shows the routers had an empty config file in the "VLAN" folder under "Routers" prior to the upgrade.
The ICSJOB008 error means there was a problem telling ICServer to collect the inventory for the device. This could mean that ICServer is not running or is in a bad state. You might try restarting it.
As for the VLAN failure, it sounds like you're hitting CSCsq66458. A patch is available from the TAC.
I am unable to terminate the ICServer.
does not do it, it is as if the ICServer daemon cannot be found.
Is it supposed to be in the install directory "bin" folder?
If so, it is not there, I did a search and only found the log files.
Can RME 4.0.6 br upgraded to 4.1?
or is that not included in Smartnet?
ICServer is down. If running "pdexec ICServer" does not work, post the ICServer.log and IC_Server.log.
You must purchase the upgrade to LMS 3.x. A new license will be required. If you're considering upgrading, you should go to LMS 3.2.
That looks like it did it.
On the bug, four of the items that failed were 3800 series routers and the bug fix shows the workaround for it (copy empty vlan.dat to flash), but there were a couple of 2900 series switches also.
Is it the same fix for all failing items (were not failing before upgrade)?
Actually, it may be easier to simply entry vlan database on these devices, and create one bogus vlan. Yes, the workaround is the same for all devices where vlan.dat does not exist, and RME reports a failure. If the vlan.dat file DOES exist, and RME reports a failure, then there is a different problem.