cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1408
Views
0
Helpful
24
Replies

Ciscowork RME not able to fetch config from CatOS device

roger.malik
Level 1
Level 1

getting below error

CM0056 Config fetch failed for ATL-6506-1-2 Cause: CM0204 Could not create DeviceContext for 249 Cause: CM0206

Please help

24 Replies 24

David Stanford
Cisco Employee
Cisco Employee

What version of RME is this and what device type (sysObjectID)?

This error has been seen a few times when the service pack does not support the hardware you are trying to fetch the config for.

thanks Davistan, what can get is

we are using LMS2.6 and i am using 6506 swtich with 8.4 2a,

pls help if how to get sysobjectid if you require

You'll need to do an snmpget/walk on the switch to get the sysObjectID. Is this a 6506 or something like 6506-E?

Also, still need your version of RME

1.3.6.1.2.1.1.2. --sysObjectID

Hardware Version: 3.0 Model: WS-C6506

Version & Patch Level:

4.0.6 -RME version.

Please let me know if your require more info thanks again

This isn't the sysObjectID of the device, this is just the numerical OID for the object itself.

You'll want to go to Device Troubleshooting - Device Center and then select the device and when the main frame loads select snmpwalk. Then enter either 1.3.6.1.2.1.1.2 or sysObjectID as the object you want to walk. What is the result?

sorry, here is result

RFC1213-MIB::sysObjectID.0 = OID: CISCO-STACK-MIB::wsc6506sysID

This is a 6506-E which is supported in your version

Is there a FWSM in this switch?

You might want to enable debugs for ArchiveMgmt in under RME - Admin - System Preferences - Loglevel Settings and then try a sync archive on the switch.

Also, enable a packet capture at the same time

i will do that but does it slow the device ?

if yes then i might need to run in night i.e. 12hrs from now

and what this result will give info?

These aren't device level debugs, they are application debugs.

thanks a lot. i have started the archive mgmt job now. job completed wher cani get output which you required

Don't forget about the packet capture which you'll want to look at as well.

the debug output will be in te dcmaservice.log

Hi Davistan,

i am extremely sorry for troublehsoot this again as i went on leave, but i would lik this to be continue from tomorrow morning

if possible thank you.

Hi Davistan an all, i am attaching the log file for you, please help me in closing this issue. thanks a ton

Hey guys,

can anyone please help in getting this cleared. thanks a ton

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco