Config Archive Mgmt failed LMS 3.2

Hi
Archive mgmt failed for 14 devices and working fine for only 2 devices..The communicaion between the LMS and Switches is through SSH,but ssh also failed.
Thanks,

Hey Clarke,
Hope you;re doing well,
i have tried from ur below instructions,i have attached logs from packet capture and the tftp permission denied error.
Am receiving an error permission denied while copying vlan.dat file from switch to tftp server (LMS Server) same error i can see in packet capture,Is it anywhere in LMS server i have to give permission for TFTP server.
I tried installing a different vendor TFTP server but the LMS TFTP is listening on this port.How can i disable the tftp port on LMS server and open for open vendor product such tftpd32.exe OR solarwinds tftp server.
LMS Server IP add 10.28.73.50 and the switch IP add 10.28.72.2
Awaiting ur reply soon.

Similar Messages

Error Message in config Archive in RME in LMS 4.2

I got the below error message in the config archive in the LMS 4.2.
CM0056 Config fetch failed for 10.0.0.10 Cause: CM0204 Could not create DeviceContext for 797 Cause: CM0202 Could not access 10.0.0.10 via SNMP. Action: Check the Read Community string Action: Check if required device packages are available. Action: Check if protocol is supported by device and required device package is installed.
Switch model type is 3560 and 2960
Please tell me the reason for this issue.

Are you usig only TFTP option to archive configuration. Try to use the telnet/ssh. TFTP as a protocol set for config archive.
Check the Credential verificatio job to see if the crendentials are configured correctly.
-Thanks

RME config archive problem - lms 3.2

just wondering if anyone else has seen this.
about a month or so ago, I grabbed about 6 or 7 patches for our ciscoworks machine, across cm, rme, and cs. (yeah, we were a little behind)
after applying these patches, it seems, all of the 2960s and 4948s are failing the config archive with the following:
cm00139: could not archive config:cause: action: verify that device is managed and credentials are correct. Increase timeout
value if required.
so I've triple checked the credential set applied to these devices, adjusted timeout and retry values, and have gotten nowhere.
Deleting these devices doesn't seem to help, they are rediscovered just fine, but the config archive continues to fail.
Other than maybe trying to reinstall the rme patches (or uninstall) that were recently applied, I'm out of ideas. This is LMS 3.2.1 with
cm 5.2.2
cs 3.3.1
rme 4.3.2
running on windows server 08.
So if anyone may have seen this and/or has any advice, I'd appreciate it. Thanks - chris

ok, so it's been a year and a half since last post. So in addition to the above mentioned archive failures with the 4948s, the 4948s were also showing up in config out of sync summary. The only difference that were showing between running and startup was the ntp clock period.
I did see that the clock period statement was in the exclude list for routers and a bunch of other things, but not for the 4948s. I added this as an exclusion yesterday. Today when I checked, all 4948s are archiving now, and are off the out of sync report. Never would have crossed my mind to check there, but that exclusion seems to have done the trick. Maybe someone else can use this if they're seeing the same thing. - chris

LMS 3.2 factory default Archive Mgmt Exclude commands

I'm working through LMS 3.2 initial setup and got to configuring device config commands to be ignored for alerting.
I notice that the Archive Mgmt Exclude commands for the Device Category "Routers" has a factory default Exclude list
"end,exec-timeout,length,width,certificate,ntp clock-period"
However, it seems that the "Switches and Hubs" Device Category has no exclude list configured by default, so I'm getting ntp clock-period alerts for my IE3000 switches for example.
Does anyone here have an opinion or reason why I shouldn't copy the default exclude list from the Routers category "end,exec-timeout,length,width,certificate,ntp clock-period" to the Switches and Hubs category?

OK thanks, Joe.
Maybe a factory default candidate for the next release?
Actually, on this subject. It's quite difficult to show which entries have which settings and therefore which item in the hiearchy is taking prcedence. Would be nice to have a similar kind of system ala the DFM overriding group.
Anyway, until then
is there some config or properties file somewhere where I can see a better overall view? (and maybe reconfigure them) [fingers crossed]

LMS 4.2 | Archival Summary failed

Hi Netpro
at the Archival Summary failed part the reason behind the failure is as below , pls how to solve this issue and let lms download all configuration from the devices
TELNET: Failed to establish TELNET connection to 10.1.1.9 - Cause: Authentication failed on device 3 times.
PRIMARY-RUNNING config Fetch Operation failed for TFTP. Could not detect SSH protocols running on the device Failed to fetch config using RCP. Verify RCP is enabled or not
Thanks
ibrahim

I was referring to the LMS server. From the Device Center where you checked the credentials, you can choose "Tools, Edit Device Credentials". from the window that opens up from that, re-type your SNMP RW credentials to verify that you are using the correct ones as configured on the device.
After you do that, then re-submit the Archive job and telll us your results.

Cisco VG248 config archive fails

I beleive in the past these devices could not be managed bij RME config management, but now it says in the supported device table:
The following features are supported:
Network Topology Layer 2 Services
Fault Management
Inventory Collection
Configuration Deploy Protocols: TELNET, SSH, TFTP, RCP
Configuration Fetch Protocols: TELNET, SSH, TFTP, RCP
The password and enable pasword are correct and simply work when I try a telnet from the server.
The gui is not CLI but menu driven.
RME just says:
TELNET: Failed to establish TELNET connection to 10.1.1.7 - Cause: Authentication failed on device 3 times. PRIMARY-RUNNING config Fetch Operation failed for TFTP. Could not detect SSH protocols running on the device.
What can be wrong?
Cheers,
Michel

Hi Michel,
Thanks for the screenshot. I found that you now have customized prompts in tacacspropmt.ini file.
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username: *
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username: *
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : login: *
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username:*
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username:*
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : login:*
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username:*
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username:*
[ Fri Aug 26 11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for password prompt : Password: *
and look like RME is able to login to device as well now :-
[ Fri Aug 26 11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,State traversal for telnet login:
[ Fri Aug 26 11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Connected
[ Fri Aug 26 11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Verify
[ Fri Aug 26 11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Success
[ Fri Aug 26 11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,login succeeded
Kindly run the credentials verification job and let me know the results --> Is the device still failing for the telnet and enable password ?
Also navigate to CSCOpx\objects\cmf\data and uncomment the following on file cmdsvc.properties like this :-
InitialTransportTimeout=50000
TransportTimeout=90000
TuneSleepMillis=3000
DelayAfterConnect=1000
LMS was not able to login to device successfully yet or it could be timeout issue. After this LMS try to get the config of the device using SNMP and tftp, but look like tftp is blocked in network too, See this :-
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,170,Initialized SNMP
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.LibCommon.snmp.ConfigCopyMib,copyFromRunning,119,FileName= 20110826113104185-10.13.192.9.cfg tftpDir = User = password = serverAddr = 10.1.3.156
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.LibCommon.snmp.ConfigCopyMib,copyFromRunning,130,Cannot create variable binding list com.cisco.nm.lib.snmp.lib.SnmpException: SnmpResponseGenErr on 10.13.192.9 while performing SnmpSet at index = 0
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,182,Fetch completed
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,190,PRIMARY-RUNNING config Fetch Operation failed
[ Fri Aug 26 11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,196,PRIMARY-RUNNING config Fetch Operation failed for TFTP. java.lang.Exception: PRIMARY-RUNNING config Fetch Operation failed for TFTP.
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator.fetchConfig(GenericTftpOperator.java:192)
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator.fetchConfig(GenericTftpOperator.java:93)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation.performOperation(SimpleFetchOperation.java:61)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.ConfigOperation.doConfigOperation(ConfigOperation.java:111)
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator.fetchConfig(GenericConfigOperator.java:72)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1317)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3307)
    at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)
So, in summary, kindly edit the cmdsvc.properties file and make the changes as I suggested . Also let me know the results of the credentials verification job and run the packet capture while running the credentials verification job.
Many Thanks,
Gaganjeet

Config archive failed for devices no longer on DCR

RME reported 30 devices failed config archive but this devices are already removed from DCR but RME keep reporting this devices. how I can clean up thiese devices from RME?
Thanks

You can contact TAC, and they can give you the procedure to surgically remove these device records from the RME database.

LMS 3.2 archieve mgmt failing

config collection is failing.in detail its partial success(config fetch is success but archieve is failed).
do i need to do any changes???
Thanks..
Regards,
Channa

Hi Channa,
Have you recently made any changes in the shadow directory or anything like this.
Many Thanks,
Gaganjeet

Config Archive Failure

This image shows that I have Telnet, SSH, TFTP and HTTPS configured for Config Fetch. What am I missing?
Thanks Joseph!
I don't know why, but nearly ALL of my Config Archive VLAN is failing. I am receiving the following:
TELNET: Failed to establish TELNET connection to xxx.xxx.xxx.xxx - Cause: Connection refused. Command failed VLAN Config fetch is not supported using RCP. VLAN Config fetch is not supported using TFTP.
The above switch is using SSH - not Telnet, but it doesn't try???
The other error is:
Command failed Could not detect SSH protocols running on the device VLAN Config fetch is not supported using RCP. VLAN Config fetch is not supported using TFTP.
On this one, it should be using Telnet as that is what is supported on this particular switch.
I have verified the credentials are set up correctly for both of these.
Also, this isn't isolated - it's happening on 293 devices. Only 2 are successful.
Any help would be GREATLY appreciated! I am running LMS 3.2

The following is what I see in the logs:
],ERROR,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1355,VLAN RUNNING Config fetch Failed for csw-a1xc-201-004
[ Fri Oct 08 06:27:18 MDT 2010 ],DEBUG,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1361,Message : Command failedSSH: Failed to establish SSH connection to x.x.x.x -
Cause: Authentication failed on device 3 times.
VLAN Config fetch is not supported using TFTP.
Please ensure that you have the credentials corrected in the DCR under Common Services --> Device and Credentials --> Devices Management --> Select all the devices in question, edit credentials.
1. Ensure the primary enable username and password is correct and populated.
2. Ensure you are using the correct SNMP RO/RW community string and must be populated.
3. Ensure that all firewall rules allow traffic to and from LMS and devices. Check port 69 UDP and high ports number are allowed.
4. If this is a multi-home system with two nic cards, go to RME ---> Administration --> System Preferences --> RME Device Attribute --> Add Natted RME IP Address
Afterwards, rerun the device credential verification to test for telnet, ssh, SNMP RO and RW and ensure it passes. Then do a sync archive and let me know the results.

Authentication failed on device 3 times. Failed to detect SSH version running on the device. PRIMARY-STARTUP config Fetch Operation failed for TFTP

I have devices loaded but new devices keep getting this error "Authentication failed on device 3 times. Failed to detect SSH version running on the device. PRIMARY-STARTUP config Fetch Operation failed for TFTP" - which trying to get configurations. I am using LMS 3.0.1
I tried to TELNET on devices via Putty port 22 no good. Please help?
Name Version License Status Size CiscoWorks Common Services 3.1.1 Licensed Not applicable Campus Manager 5.0.3 Purchased 1500 CiscoView 6.1.7 Licensed Not applicable CiscoWorks Assistant 1.0.1 Licensed Not applicable Device Fault Manager 3.0.3 Purchased 1500 Internetwork Performance Monitor 4.0.1 Purchased 1500 Integration Utility 1.7.1 Licensed Not applicable LMS Portal 1.0.1 Licensed Not applicable Resource Manager Essentials 4.1.1 Purchased 1500

Showing 1-1 of 1 records
Go to page:
of 1 pages
Device Name
SysObjectID
Model
Device Status
Inventory Status
Inventory Last Updated Time
Config Status
Config Last Updated Time
1.
R2020012_01
.1.3.6.1.4.1.9.1.576
Cisco 2811 Integrated Services Router
Normal
Success
Jan 13 2011 10:43:49 EST
Failed
Jan 13 2011 10:37:24 EST
Rows per page:
20 50 100 500
Go to page:
of 1 pages

Config archiving problem

Hi
am having problem in archiving config from switches in cisco works. am having problem in only 5 switches all others switch configurations archived when I try to do this I found following error.
TELNET: Failed to establish TELNET connection to 172.25.2.102 - Cause: Authentication failed on device 3 times. PRIMARY-RUNNING config Fetch Operation failed for TFTP. Failed to detect SSH version running on the device. Failed to fetch config using RCP.Connection refused: connect Verify RCP is enabled or not.
can any one help me to fix this
Thanks

Hi
Thanks for that apparently nearly 200 switches are working only 5 switches we have a problem. please see snmp config below. I have added RW recently it is not taking effect. please see screen shot of working one and not working
snmp-server community comms RO
snmp-server community comms RW
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
snmp-server enable traps fru-ctrl
snmp-server enable traps entity
snmp-server enable traps cpu threshold
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps flash insertion removal
snmp-server enable traps port-security
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps license
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps hsrp
snmp-server enable traps bridge newroot topologychange
snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
snmp-server enable traps syslog
snmp-server enable traps vlan-membership
snmp-server host 172.16.25.12 comms
snmp-server host 172.16.25.13 comms

Call manager and rme config archive report

Hi,
I know that rme does not support the call manager for config archive. It is clear.
The RME home page show config archive status for failed devices and there are some devices which are not supported by RME config archive.
I've set this devices to suspended state in RME but config archiv is trying with this devices also.
This is a financial costumer and the local Financial supervisory authority would like to see all devices config is saving successfully.
How can i exclude the call manager and similar devices from config archiv process and status reports?
Regards,

Hi,
I would like to qoute from RME help.
Working With Suspended Devices
Suspended device state cannot participate in any RME application flows but all historical data pertaining to the device will continue to be maintained by RME.
Nevertheless the RME is trying to fetch the config from suspended devices!!!
What is the truth in this thing?
Regards,

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)

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

(EE) config/hal: NewInputDeviceRequest failed

Since I upgraded to xorg 1.5.3. _and_ kernel 2.6.28.7-1 i have random lockups. Screen starts to flicker and mouse or keyboard don't work -- only thing I can do is to reset PC.
Looking at Xorg.0.log.old i can see several (EE) config/hal: NewInputDeviceRequest failed messages so I guess that's what causes problems.
I do have AutoAddDevices set to false in xorg.conf and my keyboard don't work without that setting so I am sure that it is active.
There are some posts that evdev may be causing the problems but I can't remove it without removing xorg server.
I lost several days trying to debug nvidia card and sound card because it looked like problem related to this two cards.
/confused, looking for help/

I have narrowed problem to sound settings. Nvidia glitches are just side product of original problem.
I have followed all alsa setting steps from wiki but there is bunch of modules in my rc.conf and I suspect they are leftovers. Can somebody help me remove what's not needed there?
MODULES=(acpi_cpufreq cpufreq_ondemand cpufreq_powersave slhc tg3 snd-hda-intel snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-opl3-lib snd-cmipci soundcore uinput !snd_pcsp)

TFTP 'configuration update' from 5508 WLC fails stating reason as '%Error: Config file transfer failed – Unknown error –refer to log'

Dear Experts,
I have two WLCs and other management devices as part of same subnet. I am able to upload ‘configs’ from all the devices on to my TFTP server. However when I am attempting to do the same from one of my WLC, it is failing consistently stating error message as:
‘%Error: Config file transfer failed – Unknown error –refer to log
Has anyone else too faced the same issue and how would we overcome this? Any specific debug that could help get more details on it?
Though the error message says, refer to log but still I don’t see anything that gets reflected in ‘Monitor logs’ which is related to ‘configuration file’ upload failure.
WLC code: 7.4.100.0
PFA as the error snippet.
Thanks and Regards,
Adnan

Hi Kaneswaran,
Just a soft reboot helped me solved the problem :). Still I am on 7.4 and facing no issues after this.
Apologies for coming too late to respond. Getting a down time window was not that easy and so was much delayed to try soft reload. I am still on 7.4 and facing no issue.
Glad that in your case it starting working all of a sudden. Could you please verify from 'show tech-support' to confirm if by chance your WLC had undergone any crash that could have caused the WLC to reload and thus accidently fixing the issue :)
Best Regards,
Muhammed Adnan

Config Archive Mgmt failed LMS 3.2

Similar Messages

Maybe you are looking for