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

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

Hi All,

I am trying to archive a PIX 515E and i get this error:

-------------------------------------------------------------------------------------------------------------------

*** Device Details for                           172.16.60.1                          ***
Protocol ==>                           Unknown / Not Applicable
Selected Protocols with order ==>                                                                                     Telnet,SSH,TFTP,RCP,HTTPS
Execution Result:
CM0062 Polling 172.16.60.1 for changes to configuration.
CM00 Polling not supported on PRIMARY STARTUP config, defaulting to fetch.
CM00 Polling not supported on PRIMARY RUNNING config, defaulting to fetch.
STARTUP
CM0151 PRIMARY STARTUP Config  fetch failed for 172.16.60.1 Cause: TELNET: Failed to establish TELNET  connection to 172.16.60.1 - Cause:  connect timed out.
Failed to get the start tag-: in  the configuration.  Action: Check if protocol is supported by device and  required device package is installed. Check device credentials.  Increase timeout value, if required.
RUNNING
CM0151 PRIMARY RUNNING Config  fetch failed for 172.16.60.1 Cause: TELNET: Failed to establish TELNET  connection to 172.16.60.1 - Cause:  connect timed out.

Failed to get the start tag-: in  the configuration.  Action: Check if protocol is supported by device and  required device package is installed. Check device credentials.  Increase timeout value, if required.

-------------------------------------------------------------------------------------------------------------------

also here is the dcmaservice.log output:

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1943,Sync Archive for 1 devices - Sync Archive

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1957,Number of devices in fetch Q = 0

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveIfRequired,2057,Compared the device with running thread devices.Adding to Fetch Q

[ Mon Feb 20  13:14:33 GMT 2012 ],INFO ,[Thread-74],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,triggerConfigFetch,52,#### Start of Sweep Mon Feb 20 13:14:33 GMT 2012 ####

[ Mon Feb 20  13:14:34 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1803,Inside RMEDeviceContext's getCmdSvc ....

[ Mon Feb 20  13:14:34 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1813,Protocol and Platforms passed = TELNET , RME_PIX

[ Mon Feb 20  13:14:34 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1821,trying for Telnet

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1803,Inside RMEDeviceContext's getCmdSvc ....

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1813,Protocol and Platforms passed = SSH , RME_PIX

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1837,Iam inside ssh ....

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1839,Initial time_out : 0

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1849,Computed time_out : 36

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1865,After computing time_out : 36

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,1903,inside getSshCmdSvc with timeout : 36000

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshProtocols,2009,Inside getsshprotocols with time out : 36000

[ Mon Feb 20  13:14:39 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,1917,SSH2 is running

[ Mon Feb 20  13:14:59 GMT 2012 ],ERROR,[Thread-181],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1357,PRIMARY STARTUP Config fetch Failed for 172.16.60.1

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,updateStatusTable,634,Calling UDMDeviceAccessManager.updateCollectorStatusTOUDM

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,84,Parameters....

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,85,Dev_id : 6

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,86,apptype : 5

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,87,status : 0

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,88,updatedtime : 2012-02-20 13:14:59.262

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,89,reason : TELNET: Failed to establish TELNET connection to 172.16.60.1 -

Cause:  connect timed out.

Failed to get the start tag-: in the configuration.

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,120,status to update the last config time: 0

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1803,Inside RMEDeviceContext's getCmdSvc ....

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1813,Protocol and Platforms passed = TELNET , RME_PIX

[ Mon Feb 20  13:14:59 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1821,trying for Telnet

[ Mon Feb 20  13:15:17 GMT 2012 ],ERROR,[Thread-181],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1357,PRIMARY RUNNING Config fetch Failed for 172.16.60.1

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,updateStatusTable,634,Calling UDMDeviceAccessManager.updateCollectorStatusTOUDM

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,84,Parameters....

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,85,Dev_id : 6

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,86,apptype : 5

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,87,status : 0

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,88,updatedtime : 2012-02-20 13:15:17.775

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,89,reason : TELNET: Failed to establish TELNET connection to 172.16.60.1 -

Cause:  connect timed out.

Failed to get the start tag-: in the configuration.

[ Mon Feb 20  13:15:17 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.inventory.dm.UDMDeviceAccessManager,updateCollectorStatusTOUDM,120,status to update the last config time: 0

[ Mon Feb 20  13:15:21 GMT 2012 ],INFO ,[Thread-181],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,writePerDeviceResultFile,2445,Serializing the Device Result = C:/PROGRA~4/CSCOpx/files\/rme/jobs\ArchiveMgmt\1071/6.device

[ Mon Feb 20  13:15:31 GMT 2012 ],INFO ,[Thread-2],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,run,105,#### End of Sweep Mon Feb 20 13:15:31 GMT 2012 ####

------------------------------------------------------------------------------------------------

I am using cisco prime lms 4.1 on windows 2008 R2

Thanks and appreciated.

Everyone's tags (6)
5 REPLIES
New Member

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

Any help appreciated

Hall of Fame Super Silver

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

Have you checked if you can ssh from your LMS server to the target Pix or ASA? The logs indicate telnet fails (as expected - generally not enabled on firewalls since it is not secure) and then ssh seems to as well.

Please verify that a 3rd party ssh client (Putty, SecureCRT, Xshell, etc.) can ssh to the target devices from the LMS server.

New Member

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

Thanks Marvin for replying,

Yes, the server can ssh to the PIX and I did not want to change the protocol order (telnet, ssh, ...) cause I have switches that I want the LMS to access them using telnet first, do you need other information to help troubleshoot the issue ?

Thanks,

Hall of Fame Super Silver

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

I realize I failed to confirm the obvious - have you done a device credentials verification from Device Center and tried increasing your timeouts?

New Member

Cisco Prime LMS 4.1 Archiving issue with PIX and ASA

Hi Marvin,

Yes I did and I realized that the issue is for all the devices including the switches and not just for the PIX device, is there anything I can do ?

Thanks,

1260
Views
0
Helpful
5
Replies
CreatePlease to create content