Netconfig jobs stuck on RME 3.5

[jaregalado]

Hello fellow netpros,

We currently have CiscoWorks LMS 2.2 installed and sometimes when a netconfig job is run it just get's stuck in the "Job Started" state for no reason.

Then I restart the Change Audit deamon under Ciscoworks Admin, run the same job again and it completes succesfully.

Sometimes jobs also stops and checking the job details the status appears as "Device was not attempted for update".

The CW Server has:

-RME 3.5 with IDU 13

-CM 3.3 with IDU 11

-DFM 1.2 with IDU 5

-CiscoView 5.5

The latest patches are applied

This case has been on TAC's hands for 2 weeks.

Also, I would like to know what is the current procedure for applying Microsoft patches to the CiscoWorks server, I mean is it advisable to run Windows Update on the CW server ? Is it recommended by Cisco ?

I would appreciate if anyone can shed a light on this.

Regards.

[getwithrob]

Did Netconfig jobs run successfully before IDU 13 or did you just bring the application up and go straight to IDU 13?

[getwithrob]

Will the Netconfig jobs complete everytime with Change Auditing disabled?

[jaregalado]

Hi

Thanks for your response.

The behaviour observed has been the same regardless of IDUs and whenever the jobs fail I restart the change audit process, retry the job and it succeeds.

Also I have noticed some CORBA and Java socket exception errors when using Configuration Management from RME, then I have to restart the CiscoWorks daemon to get it back working.

Regards.

[getwithrob]

All I know to say is make 100% sure the IDU installed with zero errors and make sure the OS is patched all the way....

[martyyates]

I know that Windows updates are not allowed for Call Mgr servers - they must be obtained only via Cisco.

However,I am running LMS 2.5 on W2003 server (std) and have run Win updates ok.

regards,

Marty.