LMS 3.1 all config related operations failing

Unanswered Question
Oct 10th, 2008
User Badges:

Recently there was an upgrade done from LMS 3.0 to LMS 3.1. In the LMS 3.0 there was a problem with the Inventory collection (Inventory collection jobs failing). After the upgrade the Inventory is OK, however the Config Polling, Config Collection or ArchiveMgmt all failing withthe following status for all the devices:


Protocol ==> Unknown / Not Applicable

Selected Protocols with order ==> Telnet,TFTP,SSH,HTTPS

Execution Result:

Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings




Enabling ArchiveMgmt job manually for a single device and have the app log for the ArchiveMgmt set to DEBUG gives the following:

Fri Oct 10 15:20:59 EDT 2008 ],DEBUG,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,getStatusOfRequest,468,Total devices due for reqId = 1223664349663 is 1

[ Fri Oct 10 15:21:04 EDT 2008 ],DEBUG,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,getStatusOfRequest,468,Total devices due for reqId = 1223664349663 is 1

[ Fri Oct 10 15:21:09 EDT 2008 ],DEBUG,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,getStatusOfRequest,468,Total devices due for reqId = 1223664349663 is 1

[ Fri Oct 10 15:21:14 EDT 2008 ],DEBUG,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,getStatusOfRequest,468,Total devices due for reqId = 1223664349663 is 1


The job itself sits in RMEJobs as running and cannot be stopped from the GUI, only via jobcli


Thanks for any imput on the problem


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Fri, 10/10/2008 - 13:39
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It looks like there is a problem with ConfigMgmtServer. Troubleshooting that is not a straight-forward thing. You should open a TAC service request to get the instructions. However, to unwedge the process, simply restart it:


pdterm ConfigMgmtServer

pdexec ConfigMgmtServer


Then run your config jobs.

dmitry Fri, 10/10/2008 - 14:31
User Badges:

Thanks Joe, the restart of the Config process fixed the problem.

If this happens again, will open a case


Thanks

Actions

This Discussion