I'm having a problem with a 3.3 to 4.2 upgrade. The steps I'm following are;
1) install 3.3 on new server
2) replicate production server db to new db
3) upgrade to 4.1
4) upgrade to 4.2
5) apply patch 4.2.5
I've done this in the lab and it's worked fine. However when doing it for the production serversI lost my connection (RDP) at the end of the 3.3->4.1 upgrade. I booted the server and was able to log in to the ACS 4.1 server, everything looked ok. Next I ran the 4.1->4.2 upgrade and it errored with "The existing installation was not removed correctly. Do you want to try again or abort this installation?". If I try to remove 4.1 I get "The log file DeIsL1.isu" is not valid or the data has been corrupted Uninstallation will not continue"
I see to be in a catch-22. I would be fine with wiping the system clean and starting all over again 3.3->4.1->4.2. Short of reinstalling the OS, which comes from another group and will take 4-6 weeks, is there something I can do?
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...