12-12-2012 04:55 AM
Hi,
I have today applied the latest RME updates to bring the enviromnet up todate and now the majority of devices (Routers, Switches etc) do not backup< I have changed nothing in relation to timeouts etc and see no reason why I should have to as things where fine before the update.
But all of a sudded devices no longer backup !
Any ideas
Thanks
12-12-2012 04:58 AM
Looking in the dcmaservice.log, I am seeing the "keyboard Interactive" issue again !!!
Which I have hightlighted before as a client isse when connectecting to devices.
[ Wed Dec 12 12:50:09 GMT 2012 ],ERROR,[Thread-825],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,Unknown authentication method: keyboard-interactive
[ Wed Dec 12 12:50:48 GMT 2012 ],ERROR,[Thread-825],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,IOException received during block() of Channel[UInt32[ 0 ]:UInt32[ 3 ]]
[ Wed Dec 12 12:50:48 GMT 2012 ],ERROR,[Thread-825],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1899,PRIMARY RUNNING Config fetch Failed for HKG-R-006
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,129,resource is not null....
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,129,resource is not null....
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,updateStatusTable,643,Calling UDMDeviceAccessManager.updateCollectorStatusTOUDM
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,addToDeviceQ,37,Adding the Device for UDM Status Update After Config Collection 51
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.dcma.utils.DCMAPreferences,getVlanConfigDisabled,163,vlan_disable====true
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1817,vlan config fetch is disabled
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-825],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,writePerDeviceResultFile,3201,Serializing the Device Result = D:/CISCO_~1/files\/rme/jobs\ArchiveMgmt\1693/51.device
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,run,44,Going to update the UDM devices 1
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1864,+++ getDCRIdMapLite +++
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1867,CSV converted values:51
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1869,Query SELECT DCR_ID,NETWORKELEMENTID FROM DM_Dev_State WHERE NETWORKELEMENTID IN (51)
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,88,Getting DCR ID for the deviceID51
[ Wed Dec 12 12:50:48 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,97,Got the DCR ID for the deviceID51
12-20-2012 02:11 PM
Hello Ian -
We opened a Cisco TAC case for this, because all of our archiving jobs were failing after the upgrade.
According to Cisco TAC it is a bug:
Not sure when the Cisco LMS product team will release a patch for this annoying issue.
Regards,
Kris
12-21-2012 01:40 AM
Many thanks for the update, hopefully it can be released quickly.
Regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide