Issue with Config Archive and Partially Collected devices

[simon.bell]

I have over 500 devices showing up under Partially Collected with the following error:

CM0056 Config fetch failed for 10.107.197.30 Cause: CM0204 Could not create DeviceContext for 3909 Cause: CM0206 Could not get the config transport implementation for 10.107.197.30 Cause: No operator available for this device Action: Check if required device packages are available in RME. Action: Check if protocol is supported by device and required device package is installed.

This is for the "Running" type the same device has a "success" for "Startup"

What could be causing this?

[Joe Clarke]

This error typically points to a package problem. The dcmaservice.log should have more details about this.

[simon.bell]

Nothing in that log file is jumping out at me except for A LOT of:

-Valid resource adding it in allocatedResource

-Getting the resource from resourcePool

-Checking for validity again

this repeats thousands of times

The only errors in the log file are:

[ Thu Sep 11 08:33:16 EDT 2008 ],ERROR,[Thread-5], Unable to initialize logging infrastructure for localization

[ Thu Sep 11 08:33:16 EDT 2008 ],ERROR,[Thread-5],No resource is associated with key "Unable to initialize logging infrastructure for localization".

[ Thu Sep 11 08:33:16 EDT 2008 ],ERROR,[Thread-5],Unable to initialize logging infrastructure for localization

[ Thu Sep 11 11:24:31 EDT 2008 ],ERROR,[Thread-88],com.cisco.nm.rmeng.genericarchive.Archive,createArchive,162,7214#PRIMARY#STARTUPcom.sybase.jdbc2.jdbc.SybSQLException: SQL Anywhere Error -193: Primary key for table 'Config_Device_Archive' is not unique

at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:3281)

at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2548)

at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)

at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)

at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)

at com.sybase.jdbc2.jdbc.SybStatement.executeLoop(SybStatement.java:1785)

at com.sybase.jdbc2.jdbc.SybStatement.execute(SybStatement.java:1777)

at com.sybase.jdbc2.jdbc.SybStatement.execute(SybStatement.java:830)

at com.cisco.nm.rmeng.genericarchive.Archive.createArchive(Archive.java:146)

at com.cisco.nm.rmeng.config.archive.ConfigFileTypeSubArchive.createConfigFileTypeSubArchive(ConfigFileTypeSubArchive.java:136)

at com.cisco.nm.rmeng.config.archive.ConfigTypeSubArchive.createConfigFileTypeSubArchive(ConfigTypeSubArchive.java:107)

at com.cisco.nm.rmeng.dcma.configmanager.DeviceArchiveManager.checkAndCreateArchive(DeviceArchiveManager.java:1296)

at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1449)

at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3291)

at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)

[ Thu Sep 11 11:24:31 EDT 2008 ],ERROR,[Thread-88],com.cisco.nm.rmeng.dcma.configmanager.DeviceArchiveManager,checkAndCreateArchive,1299,CM0020: Error creating archive

[ Thu Sep 11 11:24:31 EDT 2008 ],ERROR,[Thread-88],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1581,Error archiving config for 10.26.16.49

[ Thu Sep 11 11:35:20 EDT 2008 ],ERROR,[Thread-162],com.cisco.nm.rmeng.dcma.configmanager.DBInterface,getPollTimes,209,Error executing query

[Joe Clarke]

This is not good. It looks like some database problem in the table which tracks the config archive unique IDs. This may be recoverable with some ad hoc database queries, but you will need to open a TAC service request to get the queries.

[simon.bell]

this product really tests my patience. I can't leave it alone for more than a day or two w/o something requiring a TAC case. I'm almost on a first name basis with the LMS support group.

[janvandek]

Unfortunatelly, You are not the only one :(