ASA 5524-X and LMS

Ian Beck · ‎11-22-2012

Hi,

Any one see the pronl;em where LMS 4.2.2 cannot backup an ASA 5525-X (UKHSL-N01-AFW02)..

The Inventory collection is fine, to a point.

I have applied all updates LSM etc

Ian

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-10],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator,getOperator,72,Got the operator for in GetOperator

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-10],com.cisco.nm.rmeng.dcma.configmanager.ConfigOperatorThread,run,61,Got the Cli Operator Ifcom.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator@11dc32c

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-10],com.cisco.nm.rmeng.dcma.configmanager.ConfigOperatorThread,run,64,Adding to Operator List

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-10],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,triggerConfigFetch,56,#### Start of Sweep Thu Nov 22 15:23:10 GMT 2012 ####

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4175,ConfigFetchArgs value for this device is com.cisco.nm.rmeng.dcma.configmanager.ConfigFetchArgs@12b6836

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4179,ConfigFetchArgs value Req Id for this device is 1353597789754

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4181,ConfigFetchArgs value Device Name for this device is UKHSL-N01-AFW02

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4183,ConfigFetchArgs value Device Id for this device is 161

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4185,ConfigFetchArgs value fileTypesToFetch for this device is 3

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4193,User Context Value = com.cisco.nm.rmeng.dcma.configmanager.SecurityContext@c6e417

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4197,UserContext User Name value for this device is

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4199,UserContext App Name value for this device is Archive Mgmt

[ Thu Nov 22 15:23:10 GMT 2012 ],INFO ,[Thread-91],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,performCollection,4201,UserContext App Version value for this device is 5.2.2

Ian Beck · ‎12-12-2012

Hi,

This is still an issue for the back up of a ASA5525-X

[ Wed Dec 12 10:48:27 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator,fetchConfig,88,I am here

[ Wed Dec 12 10:48:29 GMT 2012 ],ERROR,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1899,PRIMARY STARTUP Config fetch Failed for UKHSL-N01-AFW02

[ Wed Dec 12 10:48:29 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,129,resource is not null....

[ Wed Dec 12 10:48:29 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,updateStatusTable,643,Calling UDMDeviceAccessManager.updateCollectorStatusTOUDM

[ Wed Dec 12 10:48:29 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,addToDeviceQ,37,Adding the Device for UDM Status Update After Config Collection 161

[ Wed Dec 12 10:48:29 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator,fetchConfig,88,I am here

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,run,44,Going to update the UDM devices 1

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1864,+++ getDCRIdMapLite +++

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1867,CSV converted values:161

[ Wed Dec 12 10:48:30 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 (161)

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,88,Getting DCR ID for the deviceID161

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,97,Got the DCR ID for the deviceID161

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,120,Going to Call the UDM

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,122,Going to delete the MemoryCache of Devices

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.cache.load.MemoryCache,deleteMemeoryData,296,Going to delete the device from Memory Cache DCR device is 161

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.cache.load.MemoryCache,deleteMemeoryData,296,Going to delete the device from Memory Cache UDM device is 161

[ Wed Dec 12 10:48:30 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,125,After Deleteing the Memory Cache of Devices

[ Wed Dec 12 10:48:31 GMT 2012 ],ERROR,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1899,PRIMARY RUNNING Config fetch Failed for UKHSL-N01-AFW02

[ Wed Dec 12 10:48:31 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,129,resource is not null....

[ Wed Dec 12 10:48:31 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,updateStatusTable,643,Calling UDMDeviceAccessManager.updateCollectorStatusTOUDM

[ Wed Dec 12 10:48:31 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,addToDeviceQ,37,Adding the Device for UDM Status Update After Config Collection 161

[ Wed Dec 12 10:48:32 GMT 2012 ],INFO ,[Thread-63],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,writePerDeviceResultFile,3201,Serializing the Device Result = D:/CISCO_~1/files\/rme/jobs\ArchiveMgmt\1686/161.device

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,run,44,Going to update the UDM devices 1

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1864,+++ getDCRIdMapLite +++

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getDCRIdMapLite,1867,CSV converted values:161

[ Wed Dec 12 10:48:36 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 (161)

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,88,Getting DCR ID for the deviceID161

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,97,Got the DCR ID for the deviceID161

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,120,Going to Call the UDM

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.dcma.configmanager.UDMDeviceStatusUpdater,updateUDMDeviceStatus,122,Going to delete the MemoryCache of Devices

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.cache.load.MemoryCache,deleteMemeoryData,296,Going to delete the device from Memory Cache DCR device is 161

[ Wed Dec 12 10:48:36 GMT 2012 ],INFO ,[Thread-27],com.cisco.nm.rmeng.util.cache.load.MemoryCache,deleteMemeoryData,296,Going to delete the device from Memory Cache UDM device is 161

Marvin Rhoads · ‎12-12-2012

I just added a 5515X in our lab to LMS 4.2.2. Inventory worked OK for me. Did you verify credentials in device center?

Ian Beck · ‎12-13-2012

Hi,

Inventory is no problem that works for me also.

Its the archive of the CFG that fails.

Thanks

Marvin Rhoads · ‎12-13-2012

Hi Ian, sorry about that. I dug deeper on mine and am seeing the same error as you.

I tweaked the transport and timeout stting etc. and had no luck. I checked my ASA while trying an unsuccessful archive sync and noticed that I was authenticating but then the ssh sesion was terminating with an error message 315001: reason: "Internal error" (0x00).

I doublechecked my ssh setup on the ASA and it's all correct. I even ssh'd in from the LMS console successfully to verify that the ssh key exchged OK with LMS. that all worked. So I turned on debug ssh on the ASA. I see the ssh key excahnge work OK, my authentication is granted OK and then the session drops unexpectedly.

It certainly looks like a bug to me. My other devices, including a 5510 running 8.4, are working fine.

5515X debug ssh excerpt:

SSH2 1: authentication successful for mrhoads

SSH2 1: channel open request

SSH2 1: pty-req request

SSH2 1: requested tty: dumb, height 0, width 0

SSH2 1: shell request

SSH2 1: shell message receivedSSH1: receive SSH message: [no message ID: variable *data is NULL]

SSH1: Session disconnected by SSH server - error 0x00 "Internal error"

Lab-ASA5515-X#

Ian Beck · ‎12-20-2012

Hi,

Have today updated to the latest Device Software updates and the backup of the 5525-X now works

For this intrested.

Ian

Marvin Rhoads · ‎12-20-2012

Thanks for the update. I installed the update on my lab LMS but it failed to fix my issue. The updated ASA package version is 7.1.

+ 5 for following up and posting the solution that worked for you.

Happy holidays.

Ian Beck · ‎12-21-2012

HI,

I did not just apply the ASA fix, but all the latest updates that came out. So not sure which update fixed it.

I am running 8.6.1-5 on my ASA.

Thanks