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

RME Out of Sync Partially Successfull

We recently upgraded to LMS 3.2 from 2.6, RME is reporting some devices as out of sync and details are partially successfull failing to fetch the vlan.dat. I've checked device credentials.

Here is a a snapshot of the device details from one of the devices.

Protocol ==> SSH
Selected Protocols with order ==> SSH,Telnet,TFTP,RCP
Execution Result:
RUNNING
Primary Login Succeeded
/ Primary Enable Succeeded
CM0060 PRIMARY RUNNING Config fetch SUCCESS for , version number 11 archived.
VLAN
CM0151 VLAN RUNNING Config fetch failed for  Cause: Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.
VLAN Config fetch is not supported using TFTP.
VLAN Config fetch is not supported using RCP.
Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.


What I find strange is 'Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory'. We installed LMS in it's own directory under C:\ciscoworks\cscopx so why do only a few devices that fail look like they are pointing to the program files directory and is that the true cause ? Incidently there is a folder in there as we installed another cisco tool for upgrading access points, but I have no idea why RME wants to point there ?

2 REPLIES
Cisco Employee

Re: RME Out of Sync Partially Successfull

This could be a database issue, but it may only be limited to regdaemon.xml.  Post the NMSROOT/MDC/etc/regdaemon.xml file.

New Member

Re: RME Out of Sync Partially Successfull

I uninstalled the upgrade tool wanting to see if the error msg changed and it did.....

Now it reports "CM0151 VLAN RUNNING Config fetch failed for 142.99.56.75 Cause: Couldnot create file in N/A directory.Couldnot create file in N/A directory."...

I've attached the regdaemon.xml you requested.

281
Views
0
Helpful
2
Replies
CreatePlease to create content