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

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

IOS verification after a RME distribution job

I guess this is a two part question.

The first issue seems that some device jobs fail even though the IOS and commands are successfully applied. Often this is at sites where we have a significant amount of latency / saturated network links. Is there a way to "tune" RME to either try multiple times to verify or to wait longer for a response to timeout. I do believe a lot of these came when upgrading from 12.2(25) train so it may also be due to the IOS version.

Is there a way to verify with RME whether or not an IOS has been successfully updloaded to a device and that the boot commands are in place?

This would be helpful as well since we often push to a device and wait days/weeks to get authorization to reload the router/switch/etc. So it would be nice just to 'double check' that a device has an IOS before I schedule a reload to be pushed out.



Below is the version info:

NameVersionLicense StatusSize
LMS Portal1.1.0LicensedNot applicable
CiscoWorks Assistant1.1.0LicensedNot applicable
CiscoView6.1.8LicensedNot applicable
CiscoWorks Common Services3.2.0LicensedNot applicable
Integration Utility1.8.0LicensedNot applicable
Campus Manager5.1.1Purchased1500
Resource Manager Essentials4.2.0Purchased1500
Device Fault Manager3.1.1Purchased1500
Internetwork Performance Monitor4.1.0Purchased1500


Re: IOS verification after a RME distribution job

Part 1 of the problem:

1.  Go to RME ---> Admin ---> System Prefrences --> Application Log Level Settings ---> Application ---> SoftwareMgmt and change the logging level for both modules to "Debug". Note: After the test is completed, revert the debugs back to info.

2. Recreate the job for that triggered the error.

3. Get the logs for the job ID created from RME ---> Software Managerment ---> Software Management Jobs ---> Note the job ID.

4. On the server where LMS is installed, go to CSCOpx\files\rme\jobs\swim\. Compress the contents in this directory attach for analysis.

5. Get the swim_debug from CSCOpx\log directory.

6. A show ver or show tech of the offending devices, would be helpful for a lab re-create as well.

Part 2: Job verification

Typically the job id corresponding to the upgrade is what you would use to verify if the IOS and commands applied are successful or not. If you are getting a false postive, we need to investigate further by providing the information requested from above.