1. Backing up the log collector on CLI to remote repository.
2. Assign another secondary server as log collector in the deployment. (however I believe this means assigning the primary server as the log collector as I have only 2 servers in my deployment). Am I correct?
3. Restoring log collector data back "uped" to new 5.2 log collector. They have subtly missed the step where former secondary server is upgarded to 5.2 (Do they mean you need to have another server which is already running on 5.2 already to install the backup data on or am I the one missing something here?)
4. De-register the old log collector from deployment and delete the instance on the primary ACS
5. Back up Primary ACS (configuration and monitoring) to repository
6. Upgrade ACS to 5.2
7. Backup ACS 5.2 to repository
8. Restore ACS 5.1 data to ACS 5.2 Server
9. On Primary Server of 5.1 deployment, define remote log target for 5.2 log collector server (at the end of this step, Upgraded server will function as ACS 5.2 Primary server as well as log collector)
10.On the ACS 5.1 Primary Server Configure appropiate logging categories for remote log target
11. Import local and outstanding Certificate Sign Requests
I would greatly appreciate comments that will provide some clarity on the issues highlighted above or on the whole process as a whole.
I have reviewed the upgrade path because the documentation on upgrading from 5.1 to 5.2 was unclear.
I will upgrade from 5.1 to 5.3 then to 5.4.
Basically will patch the servers first (with the last 5.1 patch) then move the log collector to the primary so as to upgrade the secondary,
deregister it and delete the secondary instance and then upgrade the old log collector.
Afterwards set it as the remote log target for the primary then upgrade the primary and then register it as the secondary back to the upgraded old log collector, which at that point is the primary and then promote it to the primary making the upgraded old log collector the secondary and then patch with the last 5.3 patch, which is 9.
Afterwards I will carry out the process all over again to upgrade the deployment from 5.3 to 5.4.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...