RME 4.0.6 Config archive problem

Unanswered Question
Dec 16th, 2009

Hi All,

I have configured one of my ASA5520 in Ciscoworks but its not getting archive since starting onwords.

Please find the below error message in Failed devices under RME and give me the correct solution.

ASA PRIMARY RUNNING Dec 17 2009 00:04:41 CM0056 Config fetch failed for ASA Cause: CM0204 Could not create DeviceContext for 70 Cause: CM0206 Could not get the config transport implementation for Cause: UNKNOWN Action: Check if required device packages are available in RME. Action: Check if protocol is supported by device and required device package is installed.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Wed, 12/16/2009 - 22:30

Make sure you have version 2.3 of the RME ASA package loaded.  If not, you can get all the updated packages under Common Services > Software Center > Device Update.  Be sure to download and install all of the available Common Services and RME packages.

Marvin Rhoads Wed, 12/16/2009 - 22:33

As the ACTION is advising...

Did you check your device for reachability from your CiscoWorks using the configured RME transport protocol(s) (e.g., telnet, ssh, snmpV1, 2, 3, etc.) and credentials?

Do you have the package files for ASA installed in RME?

Latchum Naidu Thu, 12/17/2009 - 06:58


Thank you very much for your valuable information.

How and from where I can check that version 2.3 of the RME ASA package loaded or not?

Could you please tell me what all of the available Common Services and RME packages can I download and how those will use?

Thanks in advance.



Marvin Rhoads Thu, 12/17/2009 - 08:06

You can see what versions of the various LMS components you are running by inspecting the "Software Center, Software Update" page on your LMS server. The overall product current version is 3.2. If fully updated, it would include Common Service 3.3.0 and RME 4.3.1, among others.

"Software Center, Device Update" shows your the various device packages associated with a given LMS component. Click on the "Device Type count" number to the right of, say, RME and it will list all the installed device packages and versions. If you have a fully updated installation, there will be quite a few (719 on my server). Click on the "Package Name" column header to sort by that field. That will help list ASA on the first of many pages. The current ASA package revision is 5.0.

You can also click on the RME link on the Device Update page to show the package level files as opposed to the devices within the various packages. Either way will show you your pacakge revision level.

If you don't have that revision level, go back to the Device Update page and click the radio button next to RME and then "Check for Updates". the subsequent page should present you the option of downloading the ASA and other package updates.

Latchum Naidu Sun, 12/20/2009 - 23:00


Thanks for your response.

I checked for the updated packages from cisco.cm, its asking CCO login credentials as of now I don't have with me.

Once I received the CCO credentials i will go a head with downloads.

I think it is the only way we can download the updated packages?



Latchum Naidu Mon, 02/08/2010 - 02:12

Hi Joe,

Hope you are doing well...

Finally I got the CCO login credentials and tried to download the ASA package from cisco.com, but its giving me the below error. Please find the attache doc. for detailed error description.

"Error while downloading package information from CCO for the selected products. See the log file for details."



Latchum Naidu Mon, 02/08/2010 - 23:20

Hi Joe,

Thanks for your reponse.

Could you please guide me from where I can get the psu.log?



Latchum Naidu Tue, 02/09/2010 - 22:39

Hi Joe,

I am sorry, I could not get the NMSROOT\log

Will it be in the LMS Server path like C:\Windows\Ciscoworks.... like that or it is in CiscoWorks web page?

Could you please give me the exact path where I can find the log file.

Thanks & Regards,


Joe Clarke Tue, 02/09/2010 - 22:58

NMSROOT is the path into which LMS was installed (e.g. C:\progra~1\cscopx).  Within the log subdirectory will be a psu.log file.

Joe Clarke Fri, 02/12/2010 - 20:57

Do you use a proxy?  Perhaps you need to configure your proxy settings under Common Services > Server > Security > Proxy Server Setup.  If that doesn't work, start a sniffer trace filtering on all traffic between the server and (www.cisco.com), then re-run the device package update.  The sniffer trace file should indicate why the problem is occurring.  If you use a proxy, you'll need to filter on all traffic between the LMS server and the proxy.

Latchum Naidu Mon, 02/15/2010 - 03:30

Hi Joe,

There is no proxy configured in my server.

If i make Proxy Server Setup, can you please tell me what are the Hostname/IP Address, Port, Username & Password I have to use. Is this LMS server IP and that credentials?

Regarding sniffer trace filtering, do you want me install a sniffer in server and check the trace (between server and cisco.com)?



Joe Clarke Mon, 02/15/2010 - 17:41

If you use a proxy on your clients to access external web servers, then chances are your CiscoWorks server must use the same proxy configuration.  In that case, you would need to fill in the same proxy hostname, ports, username, and password you have configured for your clients.

LMS comes with a sniffer by default.  You will need to install the WinPcap driver from NMSROOT/objects/jet/bin (double-click on winpcap.exe).  After that, you can go to Device Center > Tools > Packet Capture to start a new capture.  If you do not use a proxy, then filter on all TCP traffic between the LMS server and www.cisco.com (and cco.cisco.com).  Else, filter on all TCP traffic between the LMS server and the proxy.

Latchum Naidu Sun, 03/07/2010 - 22:42

Hi Joe,

Sorry for the delay reponse as I was on vacation.

I have installed WinPcap but I could not find any tools tab in the Device Center to start a packet capture. Please find the attached screenshot for the same.

Joe Clarke Sun, 03/07/2010 - 22:51

You have to select a device, or enter some IP address first.  Then the Tools box will appear at the bottom of the page.

Joe Clarke Mon, 03/08/2010 - 11:09

These traces are empty.  As I said before, if you use a proxy, you need to filter on all traffic to the proxy server, and not directly to Cisco.com.


This Discussion