03-28-2011 02:32 AM
Hello All,
We have a strange problem with LMS 3.2 regarding Inventory Collection.
This problem started immediatelly after the LMS installation/upgrade (LMS 3.2 was installed on a new server, and LMS 2.6 database migrated to it).
All Jobs finish as failed, with all devices "not attempted".
Job hangs for a five and a half hours and then reports failed status.
The symptoms are the same for scheduled jobs and manually created jobs.
I also have opened a TAC case, but it seems that nothing relevant can be found in the IC_Server.log.
Also, according to a packet capture, it seems that LMS does collect SNMP data from devices after a job is started...
We tried to upgrade RME 4.3.0 to 4.3.1.
One Job immediately after the upgrade was succesful (Inventory was collected for manually selected device), but the next day all Inventory Jobs were failing again with the same symptoms...
Does anyone have a sugestion where to look for a problem trace?
Thanks in advance!
Ragards,
Jasmina
03-28-2011 02:42 AM
Hi Jasmina,
Kindly attached the output of pdshow ..
--Also enable the Debugging for Inventory , run a new job and send me the new IC_server.log
Thanks--
Afroj
03-28-2011 05:03 AM
Hello Afroj,
Please find the following files attached:
- pdshow.txt - taken while the job was run
- 3656.log - the log file for the specific Inventory job (just one device selected and the job created manually)
- IC_Server.log - log with DEBUG level logging enabled. It contains logs for the job ID "3635" started at 07:45:22h and also two more jobs were started: one at 07:54:43h (also finished with the same failure) and one at 10:49:36h (still hanging, but will probably finish as failed in the same way...)
Best regards,
Jasmina
03-28-2011 05:31 AM
Hi ,
Go to RME >Admin >System Preferences > RME Device Attributes
Increase the SNMP Timeout to 18
Increase the SNMP Retry to 3
--Now Re-run the Inventory Job and Let me know how it works !!!
Thanks--
Afroj
If this post answers your question, please click the "Correct Answer" button"
03-28-2011 11:32 PM
Hi Afroj,
It does not help.
The symptoms are the same: Job lasts for a couple of hours and finishes as failed, devices "not attempted"...
Best regards,
Jasmina
03-28-2011 11:53 PM
Hi Jasmina ,
Please chech the Existing MDF pacakge :
go to common service > software center > device update >>> check the checkbox for Cisco works common service and click on check for updates
--if there is an Update , please upgarde the MDF version..
--Similarly look for any Available Device Pacakges update for RME , if there are Upgarde all the Device Pacakages ....
--After all of the above Task is done , Now re-run the Job and it still fails then share the IC_server.log again..
Thanks--
Afroj
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide