Subject: | |
From: | |
Reply To: | |
Date: | Fri, 17 Mar 2006 09:35:56 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi Brian, we just completed our upgrade from 3.5.5 to 3.6.1.1 yesterday.
As per the instructions in the release notes, we upgraded to 3.5.9
first, backed up our config/database, loaded 3.6.1 from CD, FTP'ed the
backed up config tarball back to the freshly installed CAM, unextracted
it, and then ran the script that restored the config. Everything went
pretty smoothly except for the FTP of the backed up config file to the
CAM. For whatever reason, the first two times we tried to FTP and then
extract it, the extraction failed, warning us that the file was
corrupted. While I waited on hold with TAC, my associate FTP'ed and
extracted it a third time and it worked. We have no idea what the
problem was, but it was the one moment of high drama in an otherwise
uneventful upgrade. We have two CAMs, and four CASes so we took two CDs
with us and did two CASes at a time after doing the CAMs. The last
steps were to apply the 3.6.1.1 patch, and then we enabled L2 strict
mode and TCP fingerprinting. We're really looking forward to Monday
when the students return and try to use their routers and the user-agent
switching trick to get around CCA :)
Jason
---
Jason Richardson
Manager, Security Systems
Enterprise Systems Support
Northern Illinois University
>>> [log in to unmask] 3/10/2006 8:13:31 AM >>>
Is it still recommended to upgrade to 3.6.x by doing a fresh install or
does
Cisco feel it is ok to performing an upgrade via their upgrade script?
We have been holding off for 3.6.1.x and sitting at 3.5.9.
Thanks for the replies.
Brian Beausoleil
Southern CT State University
|
|
|