Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CW2000 software distribution not working

When I try to distribute a software image to a device, the job stays pending long past the scheduled time, and eventually times out. The error returned is:

Error: Job has not been executed/

Reason: Job may have been halted because of a machine reboot.

As far as I can tell, this isn't the case. System is a CD One/5, with RME 3.4 (IDU 6), running on a Solaris box.

I've tried various devices, error is always the same. Device credentials in the Inventory check out (OK for SNMP R/RW, OK for TACACS). The log files tell me the same as the main error: not much at all.

Does anyone have any ideas about how to solve this?

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Re: CW2000 software distribution not working

Before performing the software image job, can you check Edit Preferences and select Debug checkbox.

after the job completes with error, type

cd /var/adm/CSCOpx/files/schedule/

there should be a swim_debug.log file which will give

more info on why the job is failing.

If you are running Solaris 7 or 8, please check

the casuser account to make sure that account is not LOCKED - *LK*, that'll prevent jobs being ran properly.

Hope that helps

2 REPLIES
New Member

Re: CW2000 software distribution not working

Before performing the software image job, can you check Edit Preferences and select Debug checkbox.

after the job completes with error, type

cd /var/adm/CSCOpx/files/schedule/

there should be a swim_debug.log file which will give

more info on why the job is failing.

If you are running Solaris 7 or 8, please check

the casuser account to make sure that account is not LOCKED - *LK*, that'll prevent jobs being ran properly.

Hope that helps

New Member

Re: CW2000 software distribution not working

casuser indeed turned out to be disabled. Enabling it solved the problem.

I already ran with debug enabled, but the logs didn't give any clues I could find.

89
Views
0
Helpful
2
Replies
CreatePlease login to create content