Re: upgrading from ComOs 3.0.4 to 3.5.3
S. Van Steen (steven@glo.be)
Sun, 24 Aug 1997 09:50:08 +0200 (MET DST)
Forwarded message:
> From owner-portmaster-users@livingston.com Sun Aug 24 05:47:08 1997
> X-Originally-To: <listfeed@glo.be>
> Message-Id: <3.0.32.19970823203052.008c5840@mail.solgate.com>
> X-Sender: jvian@mail.solgate.com
> X-Mailer: Windows Eudora Pro Version 3.0 (32)
> Date: Sat, 23 Aug 1997 22:45:21 -0500
> To: Jake Messinger <jake@ams.com>, Terry Angel <terry@minfod.com>
> From: Jeff Vian <jvian@solgate.com>
> Subject: Re: upgrading from ComOs 3.0.4 to 3.5.3
> Cc: portmaster-users@livingston.com
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Sender: owner-portmaster-users@livingston.com
> Precedence: bulk
> Reply-To: Jeff Vian <jvian@solgate.com>
>
> At 04:07 PM 8/20/97 -0500, Jake Messinger wrote:
> >On Wed, 20 Aug 1997, Terry Angel wrote:
> >
> >> We're running a Portmaster pm2 model, with comos 3.0.4 and pmconsole
> >> 3.0.4, and would like to upgrade to the 3.5.3 models.
> >>
> >> I have the software downloaded and uncompressed, and think I have a
> >> firm understanding on how to proceed, I'm just asking if anybody has a
> >> cookbook-style recap of their previous experiences posted anywhere on
> >> the web, or anywhere previously on here for that matter.
> >1. Start up pmconsole (3.5.1.4)
> >2. Log into the portmangler
2a. do a "save all"
2b. backup the portmaster
2c. reboot (my experience from the past week is that old comoses with an uptime
beyond 50 days have a tendency to fail during upgrade - you have been warned)
2d. Log into the portmaster
> >3. Click the Upgrade Button
> >4. Choose the com os image (or_3.7L) and tell it to upgrade
3.0.4 is very old; it's not a bad idea to go thru some 3.3.x image
before going to 3.5/3.7.
4a. If you are religious, start praying. If not, go get some coffee.
> Should be pm2_3.7. This one wont work on his PM2
If something goes wrong during the upgrade, try erasing the flash with
"set register 0xffff 0x0f63" followed by "save all" and try again.
If it still doesn't work put a rarp/tftp server in place and go for
netbooting (SW 1 & 2 UP); the latest generic images are comos 3.5
and your saved configuration will survive and work after the boot.
> >5. reboot the unit
6. check your port and user configurations; things tend to change; this time
I only needed to reconfigure the idletimes but if you want to go classless
with "set all user-netmask on" you could be in for some fun.
--Steven.