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

Config archive for Cisco 4404 WLC devices

Nodes are discovered properly, with the correct icon, and inventory updated.... but when we try to download config, we got:

*** Device Details for XXXXXXX ***

Protocol ==> Unknown / Not Applicable

Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS

Execution Result:

Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings

We have configured only HTTPS credentials, because others are not permited, isn't it?

Telnet through port 22 works fine (i have read about https://supportforums.cisco.com/message/3053616#3053616)

7 REPLIES
New Member

Re: Config archive for Cisco 4404 WLC devices

If I run a snmpwalk, it works properly, but if I check credentials, I got "Failed to get value" for Read Community :-(

If I try to run CiscoView for those nodes:

Error
Message
Cannot access the required SNMP object.

Cause
This problem could be due to a restricted SNMP view setting or the wrong SNMP credentials.

Action
Please check the SNMP view setting on the device and SNMP credentials.

But SNMPWalk is working!

New Member

Re: Config archive for Cisco 4404 WLC devices

in dcmaservice.log:

[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1941,Sync Archive for 4 devices - Sync Archive
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1955,Number of devices in fetch Q = 0
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,addToDeviceIdToReqIdMap,2289,Device Id 7 already in Q
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,addToDeviceIdToReqIdMap,2289,Device Id 6 already in Q
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveIfRequired,2055,Compared the device with running thread devices.Adding to Fetch Q
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01  15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveIfRequired,2055,Compared the device with running thread devices.Adding to Fetch Q

Cisco Employee

Re: Config archive for Cisco 4404 WLC devices

You can only use telnet or SSH to get configs from WLC devices.  HTTPS will not work.  If you are using SSH, I think you're seeing my relatively new bug CSCtg43962.  If you contact TAC, a patch can be provided to fix this.

New Member

Re: Config archive for Cisco 4404 WLC devices

There is no bug using Telnet? we have configured both, if ssh is failing, we can use telnet, but it is not working neither...

Cisco Employee

Re: Config archive for Cisco 4404 WLC devices

No, telnet is not affected.  However, you may need to restart ConfigMgmtServer before trying it.  Run:

pdterm ConfigMgmtServer

pdexec ConfigMgmtServer

Then try a config sync using telnet.  You will need a proper username and password configured in DCR for this to work.

New Member

Re: Config archive for Cisco 4404 WLC devices

Thanks Joseph.

Yes, I have telnet and ssh properly configured, Read Community is failing with:Failed to get value, but snmpwalk is working fine!

I executed what you suggested, with the same result :-(

I have incremented response time for the job, as recomended in the error, with no success.

What else?

Thanks again....

Cisco Employee

Re: Config archive for Cisco 4404 WLC devices

If you're getting the same job timeout error, even with telnet, you're going to need to get a thread dump of the ConfigMgmtServer process.  Open a TAC service request, and they will walk you through the steps to do this.

You will also need to fix the SNMP issue.  I recommend you re-enter your SNMP credentials for this device in DCR.  A sniffer trace of the Device Credential Verification job will tell you what credentials RME is using, and how the WLC is responding.

666
Views
4
Helpful
7
Replies
CreatePlease login to create content