No configuration archived yet but sync job details don't confirm that

js88888888 · ‎01-13-2010

I'm scrolling through my devices in LMS 3.2 Device Center and see many that say "No Configuration Archived Yet". I then ran a manual Sync Archive job from RME (not the individual device) that included all of my pertinent devices.

That job log shows that the devices that say "no config archived yet" in device center were successful.

24-hour Change Audit Summary	Number of records: 0
Inventory Last Collected Time	Jan 13 2010 00:44:52 MST
Configuration Last Archived Time	No configuration archived yet

Device: XX XXX Status: Successful

*** Device Details for XXXXXXXXXXXXXXXX ***

Protocol ==> Unknown / Not Applicable

Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS

Execution Result:

CM0062 Polling XXXXXXXXXXXXXXXXXXXX for changes to configuration.

CM0065 No change in PRIMARY STARTUP config, config fetch not required

CM0065 No change in PRIMARY RUNNING config, config fetch not required

CM0059 Config fetch not required for XXXXXXXXXXXXXXXXXXXXXXXXX


CLI Output
No CLI Output for this job

I always thought the Device center info indicated you either did or did not have a good config archive and if you did, it would tell how old the newest archive was. Is this still the case in 3.2?

My RME DB was re-initialized to 0 a few weeks ago, FYI.

Thanks!

Joe Clarke · ‎01-13-2010

While the job was successful, nothing was updated. Run a new Sync Archive job for this one device. Do NOT check the Poll box when defining the job parameters. Make sure the config is successfully fetched. Device Center should reflect that. If not, post the dcmaservice.log, dcmaclient.log, and the NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log.

js88888888 · ‎01-14-2010

Thanks Joe,

Now it shows as partially successful, along with a few dozen other devices.

Joe Clarke · ‎01-15-2010

So Device Center is updated now, or does it still show that no config was fetched? If so, what is the device name and IP that is still a problem?