05-16-2004 08:27 PM - edited 03-02-2019 03:44 PM
Job failed 8 out of 10 tries: Says it cannot put device into priv mode when it fails. We do have the correct credentials for enable secret. Anyone seeing this behavior?
-----------------------------------------------------------------
JOB ID - 11 SUMMARY
Device Name : [OUR DEVICE]
Software upgrade result - Failed
Total number of devices scheduled for upgrade: 1
Number of devices upgraded: 0
Number of devices failed : 1
Total time taken for Job - 6 mins 57 secs
-----------------------------------------------------------------
Starting Job: ID - 11
Owned by :
Job description: RETRY: Final Test
Results e-mailed to : [MY EMAIL]
Time created : 17 May 2004 00:02:53 EDT
Scheduled time : 17 May 2004 00:02:53 EDT
Total number of devices in the job: 1
Reboot devices immediately after download : no
Update boot commands in config file: yes
Back up current running image: no
Stop if error detected : no
Use Tftp Fallback for Image Boot : no
Job running on : [OUR CISCO WORKS SERVER]
Tftp Root Directory : /tftpboot
Processing Device : [OUR DEVICE] (#1 of 1)
Start Time : 17 May 2004 00:03:10 EDT
Running System S/W : 12.0(5)WC9a ENTERPRISE|COMMAND-CAPABLE
Upgrading System S/W : 12.0(5)WC9a ENTERPRISE|COMMAND-CAPABLE
Bootldr upgrade not selected or not applicable
Device is being locked for exclusive write access.
Connecting to device now ...
Device not reachable using SNMP. Will retry connecting after 3 mins
Trying to connect to device again. (2 Retries left)
Trying to connect to device again. (1 Retries left)
Device cannot be connected via SNMP skipping the software upgrade on this device
Error Info Code: '4021'
Message: 'Device Error: Cannot put the device into privileged mode. '
Action/Reason:
'Probable Cause: Invalid access information for the device.
Recommended Action: Verify enable password, enable secret in the
inventory, then retry the operation.'
Device has been unlocked from exclusive access.
Image Upgrade Failed
End Time : 17 May 2004 00:10:04 EDT
Time Taken: 6 mins 54 secs
Job encountered error. Job aborted.
End of Job
05-16-2004 11:15 PM
Hi,
never seen such an errror.
But according to "Device cannot be connected via SNMP skipping the software upgrade on this device " error message I'd check the SNMP community strings.
Regards,
Milan
05-17-2004 04:47 AM
Strings are correct. Upgrade worked twice out of 8 tries.
05-17-2004 06:32 AM
How busy is your network when you try upgrading? SNMP runs at such a low priority compared to other traffic, you may want to increase your timeouts.
What image are you trying to upgrade too? Is it the same that's currently running on the device? I seem to remember putting the same image set as currently running leads to problems similiar to downgrading IOS images. Suggest trying to do a manual load and see what happens.
05-17-2004 07:16 AM
I did a trace and it appears that the attempts to telnet to the device are failing. It seems as if RME is sending terminal parameters while the device is expecting passwords. SNMP works all-day long, I could see that in the trace. Something is amiss with the attempts to telnet to the device...
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