Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
LMS 3.2 is running on Solaris 10.Is what somebody knows why the process DCRDevicePoll is never started after a LMS stop/start. I must restart it manually.thanks for your suggestions
Hi, allI am running LMS 3.2 SOLARIS 10 (RME4.3.1)Since some days, when I try to archive the configuration files from 1300 devices, I am getting the following message: CM0057 VLAN RUNNING config fetch SUCCESS, archival failed for xxxx CM0012: Unable ...
We have migrated the supervisor card from III to SUP 720 on Cisco 6509.I get this error from Inventory Collection :RICS0001: Internal Error,unable to process the collected data from the device.Normally, this change should be detected and the inventor...
I have a problem when i want to export the inventory via cwcli.cwcli export inventory -u xxxx -p xxxx -m xxxx -deviceRunning LMS 3.2 on Solaris 10.Actualy, there are 2000 devices.I get this error (cli.log):Java heap spacejava.lang.OutOfMemoryError: J...
I don't anderstand why i can't access to Management tasks functions from device center to a device and not to an other. It happens since a device package update. It seems i have not all permissions to access the device from "Device center". Remark : ...
Hi Jclarke,I confirm the DCRDevicePoll is scheduled to run daily at 00:05.You can see in the log file the Polling is running on th 17 and stop at 00:10:43We have restarted the LMS 3.2 in the morning. We had not seen that the DCRDevicePoll had not sta...
OK, but in my case, the DCR polling is configured to run daily. The job ID remains the same. I don't know wky it does not start automatically with each restart.
Hi,sincerely, i don't know if this issue was solved applying the last RME update or applying the last device package according with RME 4.3.1. New swapp, not necessary about 6500, were planned. I keep you informed.Regards
Hi,All packages were applied. It seems RME is working fine since it was upgraded to 4.3.1. The swapped device appeared like "conflicting device". Regards
