During a cisco ASA 5510 cluster migration this weekend, we experienced 2 times this error on the moment of writing the configuration to the startup-config file of the Cisco ASA primary cluster node. After this error we noticed that the startup-config file became corrupted and that the cluster lost replication. The solution was to run the "fsck disk0:" command and truncate the startup-config file.
The only question that is left. Is what is causing these errors. Could this be a flash hardware issue? Can I expect similar recurring errors in the future on this device after this fsck? Or did the fsck command repaired this issue for once and for all?
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...