You could do a two part CAM upgrade.... 4.1.2.1, then to 4.1.3 According to the release notes, this will skip over the problem. Assuming that is the problem you are having.
Mike On Jan 4, 2008 8:58 AM, Frisk, David P <[EMAIL PROTECTED]> wrote: > Yea, that's what I did this morning, didn't seem to help... > > David Frisk > NPU | Systems Manager > > > -----Original Message----- > From: Cisco Clean Access Users and Administrators [mailto: > [EMAIL PROTECTED] On Behalf Of Nathaniel Austin > Sent: Friday, January 04, 2008 7:54 AM > To: [email protected] > Subject: Re: upgrade from 4.0.4 to 4.1.3 > > Hi David, > > That is a known issue in the upgrade script: > > > http://www.cisco.com/en/US/docs/security/nac/appliance/release_notes/413/413rn.html#wp74736 > > You can delete all the agent reports from your CAM to expedite the > upgrade process (brings it down to the normal install time of ~5 > minutes). Otherwise you can let it run, and the upgrade will eventually > complete. I believe it was timed at 90-100 minutes. > > Nate > > Frisk, David P wrote: > > > > Happy New Year all, > > > > Has anyone else attempted an upgrade from 4.0.4 to 4.1.3? How long did > > it take? I'm pushing 90 minutes again (had to kill it yesterday and > > reload/restore back to 4.0.4)... Seems excessively long to me. Since > > Cisco's upgrade screen output only tells me what just finished > > (sorta), I have no idea what it's working on. > > > > If I ps ux in another ssh session, I see the upgrade command as well > > as an sql data import command (some sql 4.0.4 -> 4.1.3 file I assume > > it created earlier in the upgrade process. Both STAT S (Interruptible > > sleep, waiting for another process to finish). > > > > All I see on my screen is that the agent was successfully upgraded. > > > > I've read the warning in the docs about the Agent Reports in the > > database being "quite large"; But with Cisco talking about 30,000 > > records in the database being the limit, I assumed my measly 107 > > didn't qualify as "quite large". After it bombed yesterday, I assumed > > this was the issue (that Cisco's definition of "quite large" meant > > greater than 1), and used their suggested workaround of deleting the > > reports... I also assumed that it would now take it's "upgrade window of > > 15 minutes per server". > > > > Since I now lost my morning window to upgrade its HA pair, I'm just > > going to halt the primary, and start up the un-upgraded secondary. > > Since I haven't touched the CASs yet, this should just mean I'm not > > running HA for the weekend. Hopefully this thing really finishes. > > > > Thanks in advance for any ideas you may have! > > > > *David Frisk* > > > > Systems Manager > > > > North Park University > > > > [EMAIL PROTECTED] > > > > 773.244.5544 > > >
