01-15-2008 02:48 AM
"CM0060 PRIMARY RUNNING Config fetch SUCCESS for
wsd15231.netiss.intesabci.net, version number 3
archived.CM0057 VLAN RUNNING Config fetch SUCCESS, archival
failed for wsd15231.netiss.intesabci.net Cause: CM0012:
Unable to create new version on archive $1 Action: Check if
disk space is available and directory has required
permissions Action: Verify that archive exists for device. "
01-15-2008 11:34 AM
A couple of things for you to check:
1. Do you have multiple versions available for that (those) device(es) in your version summary ?
2. Do you have sufficent disk space to store all of the configurations that the archiver is collecting ?
01-15-2008 01:36 PM
Assuming akemp's suggestions check out, you are most likely hitting the bug CSCsh39475. This bug is fixed in RME 4.0.6 and RME 4.1. Once you have upgraded to a fixed version, you will need to delete then re-add the device within RME to complete the fix.
10-15-2009 09:19 AM
Ran into this myself. In RME, do you delete devices under RME or Normal devices or does that matter? If its locked in with DCR, does that matter like it does w/ DFM?
10-15-2009 09:20 AM
Delete under RME > Devices > Device Management > RME Devices. As long as you do not remove it from DCR, it will not affect other LMS applications.
10-15-2009 09:49 AM
Thanks Joe! What is the interval that RME uses where it will re-add them from DCR?
10-15-2009 09:56 AM
You should re-add them manually under the same interface.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide