Bug CSCtx03563

[otchristensen]

Hello,

I have read the discussions that came up reg. this bug.

We run 2 clusters of Cisco ACE 4710 - that is 4 devices - with software rel.  A4(2.1). Uptime is 741 days and there's problems synchronizing between members, as well as the well known report of  "write error: No space left on device".

So, I want to reload members in a requested window.

I know You will advice me to upgrade software but the part of the network, that uses the ACE is in the process of being transferred to other devices, so if a reload will last for 150 days it'll be fine.

Quote

CSCtx03563—If the ACE has been operating for approximately 150 days, you may find that it may produce huge httpd logs over time when you use the XML interface. This

behavior causes the file system to become full and the following messages may appear: "write error: No space left on device." If ACE reloads when in this state, and

you save the configuration on reload when prompted, this action will cause the ACE to wipe all configurations. Workaround: Perform the following actions:

–Do not save the configuration when prompted on reload.

–If necessary, contact Cisco TAC to provide a workaround script.

Unquote

Now to my question - have anyone done the reload during similar conditions with success? There has been performed "copy running-config startup-config" quite a few times but if the warning just covers the reload-situation we will be good unless I clumsy that up. Should be possible though....

I plan to disable autosync for all contexts on both devices and save. Then reload the (in some contexts) cold-standby member and when checked, continue with the active member. Will take out manual backups of all contexts as well as keys and certificates before any actual activity..

Any comments?

[ajayku2 · Accepted solution]

Hi,

You can raise a TAC case and TAC can help you with a script which can clear the data without doing reload.

also check the following command before reload :

show startup-config

If  the output is empty then it is not safe to reload the unit as it may come up with empty config. I will recommend you to get the script. If the show startup-config is not empty you can reload without saving the configuration.

regards,

Ajay Kumar

[otchristensen]

Thank You for Your answer, Ajay.

I checked and the startup config is similar to the running config in all contexts. I will probably be allowed to do the reload tomorrow. Else, later.

Either way I will update the thread with the outcome.

Regards

Ole

[otchristensen]

Well, I chanced and reloaded the standby unit. Unfortunately it lost it's configuration, including keys and certificates.

The cure was to upgrade software on both devices to 4_2.3 software and then synchronize from the active configuration.

The keys and certificates had to be installed all together off cause.

I would probably say like You do, to ask TAC for a script, since several things can go wrong. That is if I had to do it again.

Thanks...