Ciscoworks Archive Management Partially successful

Answered Question
Jan 11th, 2009

Dear All,

I am getting the error from Ciscoworks

CM063 Error polling for change on PRIMARY STARTUP config, not fetching the config. CM0065 No change in PRIMARY RUNNING config, config fetch not required CM0059 Config fetch not required for ROUTER-1

is this an error? Since this is showing Partial successful then there should be some issue?

Thanks in advance

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 8 years 1 week ago

A fix would be an upgrade. The problem stems from the ccmHistoryStartupLastChanged object not returning proper data. There are quite a few known bugs with this object, but all should be fixed in the latest code in the various branches.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
Loading.
Joe Clarke Sun, 01/11/2009 - 23:08

This is most likely a problem with the CISCO-CONFIG-MAN-MIB implementation on the router. However, it's not a serious error. If you have periodic config collection configured, your startup config will be fetched.

If you want to fetch the startup config now, go to RME > Config Mgmt > Archive Mgmt > Sync Archive, and check the Fetch Startup box.

prasad.gsmc Sun, 01/11/2009 - 23:14

Hi,

Thanks for the update.

Yes it is collecting data. But can i fix this issue with the CISCO-CONFIG-MAN-MIB, so that I can have a work order status of 100% successful.

Correct Answer
Joe Clarke Sun, 01/11/2009 - 23:21

A fix would be an upgrade. The problem stems from the ccmHistoryStartupLastChanged object not returning proper data. There are quite a few known bugs with this object, but all should be fixed in the latest code in the various branches.

Actions

This Discussion