You need to enable ArchiveMgmt Service debugging and then reproduce the fetch failure for one of the affected devices. Debugging can be enabled under RME > Admin > System Preferences > Application Loglevel Settings. Once the job has failed, post the dcmaservice.log.
You should be triggering an update for one device only under RME > Config Mgmt > Sync Archive. If nothing is updated in the log then, you may have a thread lock. In which case, you will need to bounce ConfigMgmtServer with the commands:
If that causes your config archive to work, then you will need to upgrade to LMS 3.2.1 (downloadable from Cisco.com) to get some needed bug fixes.
ok, so it's been a year and a half since last post. So in addition to the above mentioned archive failures with the 4948s, the 4948s were also showing up in config out of sync summary. The only difference that were showing between running and startup was the ntp clock period.
I did see that the clock period statement was in the exclude list for routers and a bunch of other things, but not for the 4948s. I added this as an exclusion yesterday. Today when I checked, all 4948s are archiving now, and are off the out of sync report. Never would have crossed my mind to check there, but that exclusion seems to have done the trick. Maybe someone else can use this if they're seeing the same thing. - chris
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...