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

Software distribution reboot verification

Does anyone know what RME uses to verify that the new image is now running after a reboot?

Most of my jobs fail because after the reboot it determines that the new image isn't running. Oddly, the jobs are actually quite successful and since the old images are deleted it better be running the new image or I'd be in a really bad spot.

I've attached an output of the report for a device that was successfully upgraded but reported back failed.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Software distribution reboot verification

This looks like it should for a 12.2(44)SE6 image. More debugging will need to be done to determine why the verification step is failing. I suggest you open a TAC service request so they can walk you through enabling debug, and collecting the various log files.

9 REPLIES
Cisco Employee

Re: Software distribution reboot verification

This error could indicate the reboot failed. Do you have "snmp-server system-shutdown" configured on your devices?

New Member

Re: Software distribution reboot verification

Yes. I have the command on the switch.

The switches do reboot just fine in the job and they are up and running on the new version. It just reports back to LMS that it failed.

Cisco Employee

Re: Software distribution reboot verification

SWIM will use the CISCO-IMAGE-MIB to determine what image is currently running on the device. If you walk ciscoImageMIB on this device, what do you see?

New Member

Re: Software distribution reboot verification

Looks normal on the ones I upgraded last night. I'll try again first thing in the morning after the next job completes.

# snmpwalk -v 2c -c Q4roM8yeDa3 10.251.198.213 1.3.6.1.4.1.9.9.25

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.1 = STRING: "CW_BEGIN$-gs-advipservicesk9-m$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.2 = STRING: "CW_IMAGE$C3750-ADVIPSERVICESK9-M$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.3 = STRING: "CW_FAMILY$C3750$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.4 = STRING: "CW_FEATURE$IP|LAYER_3|PLUS|SSH|3DES|MIN_DRAM_MEG=128$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.5 = STRING: "CW_VERSION$12.2(44)SE6$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.6 = STRING: "CW_MEDIA$RAM$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.7 = STRING: "CW_SYSDESCR$Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(44)SE6, RELEASE SOFTWARE (fc1).Copyright (c) 1986-2009 by Cisco Systems, Inc..Compiled Mon 09-Mar-09 17:56 by gereddy$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.8 = STRING: "CW_END$-gs-advipservicesk9-m$"

New Member

Re: Software distribution reboot verification

hmm... looks the same. The devices are all running 12.2(44)SE6 and yet they read "failed" in the reports.

# snmpwalk -v 2c -c Q4roM8yeDa3 10.251.198.196 1.3.6.1.4.1.9.9.25

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.1 = STRING: "CW_BEGIN$-gs-advipservicesk9-m$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.2 = STRING: "CW_IMAGE$C3750-ADVIPSERVICESK9-M$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.3 = STRING: "CW_FAMILY$C3750$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.4 = STRING: "CW_FEATURE$IP|LAYER_3|PLUS|SSH|3DES|MIN_DRAM_MEG=128$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.5 = STRING: "CW_VERSION$12.2(44)SE6$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.6 = STRING: "CW_MEDIA$RAM$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.7 = STRING: "CW_SYSDESCR$Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(44)SE6, RELEASE SOFTWARE (fc1).Copyright (c) 1986-2009 by Cisco Systems, Inc..Compiled Mon 09-Mar-09 17:56 by gereddy$"

SNMPv2-SMI::enterprises.9.9.25.1.1.1.2.8 = STRING: "CW_END$-gs-advipservicesk9-m$"

#

Cisco Employee

Re: Software distribution reboot verification

This looks like it should for a 12.2(44)SE6 image. More debugging will need to be done to determine why the verification step is failing. I suggest you open a TAC service request so they can walk you through enabling debug, and collecting the various log files.

New Member

Re: Software distribution reboot verification

Just thought I'd share the resolution:

Apparently I was hitting bug CSCsw42682

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsw42682

Just recently made public thanks to my issue. I completely disagree with the "Purely Cosmetic" rating on the bug. It keeps you from being able to select "stop on errors" or you'd never get past the first device. This actually could have caused a major issue after I had a flash disk go bad on two different 6509's I was using for remote staging and CW kept going on it's merry way erasing flash on 3750 after 3750 leaving them with no image until I came in in the morning and had to scramble to get an image on them before someone did something silly like reboot them or a power outage occured.

Re: Software distribution reboot verification

thanks for reporting the "solution" or better the cause of this issue. Perhaps it should be a common usage guide to verify the result by setting up a Netshow job. A quick thought is a new feature like "Baseline Templates" that checks the output of a Netshow command to match a predefined string (RegEx).

New Member

Re: Software distribution reboot verification

That was my next option if I couldn't get the verification to work. I just wasn't too crazy about writing a separate function to tell me if my first function worked. :-)

That would be a useful addition. We actually use a couple perl/expect scripts to run through our switches to run show commands and verify/record the results. I'm a fan of keeping it all in one place.

320
Views
5
Helpful
9
Replies
CreatePlease to create content