My update from 5.1 -> 5.2 went smooth. I did read the known bug pages before hand. One thing you need to realize about that though, is that its a cumulative of all known bugs with CSA. So, just tread cautiously, but I believe your upgrade will go smooth.
With regards to the firewall, that has been a known bug since 4.0. I would suggest just running the firewall rule sets with CSA vs. the Windows provided. You may find it more flexible in regards to ports and a security stance as a whole.
Ok, I did find the documentation for upgrading to 5.2 for MC, and it talks about migrating in there.
My real question would then be, what would need to be done to ensure a backup plan? IE, what needs to be done if we need to roll back to 5.0? I would guess we'd just keep a backed up copy of the DB, un-install 5.2, re-install 5.0 pointing it to the restored DB? Then I'm not sure if we'd do the same "migration" steps to bring the config data back into 5.0 or if it wouldn't be necessary? We've been doing weekly exports of our configuration data, would just importing that suffice?
This project was just kind've dumped in my lap yesterday, so I didn't read thoroughly enough then...
Yes, this will be a server switchover, as well as a DB switchover (remote using 2000 right now, but organization is pushing towards 2005).
I think I understand everything now, I would make a disk image in case, but even then I'm not worried too much. Only have 2 remaining issues/questions...
1. How long can migration be spread out? I want to run only a few agents in 5.2 for a few days in case we get some big bugs, plus our organization is big on back out planning and testing. I want to make sure running these two concurrently won't make things crazy.
2. In the install notes (specifically the same system upgrade), it says to un-install 5.0, then re-install "that same system". Does this mean I need to un-install 5.0 on the 2k server and then re-install it on the 2k server? "That same system" is a bit confusing...
Digging a little into my second question, it appears that it wants CSA 5.0 installed on the Windows 2003 server. Is this because CSA 5.2's install detects the old version and starts installing 5.1?
If possible, I'd rather just leave 5.0 on the 2k server, do a fresh 5.2 install on the new 2k3 server, and import from there. But, I'd rather be sure the data is able to be brough over to the new CSA version.
You don't need to do anything to the old server except run the migration tool from the new server when you are ready.
You can take as long as you want to migrate.
If I was you, I'd do a dry run on some VM servers to get comfortable with it. You can import your current config to a 5.0 VM MC and then do the fresh install for a 5.2 VM MC. You can use a 3rd VM for your SQL.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :