***
First of all, thanks to all that responded to directly to me. I beleive
the consensus is that 3.3.2 is bad and that the ComOS should be upgraded.
to 3.3.3.
**
Well, as quickly as the problem came, it appears to have gone away. The
Pm2 in question has been acting fine since yesterday 10am. I have upgraded
the unit to 3.3.3 for good measure.
I have been concerned about upgrading without a concrete definition of
the problem. Could it be that the process of upgrading the unit fixes the
problem and that the upgrade itself was irrelevant? It would be really nice
to know (trivia) why the ports all reset.
Anyhow we will wait and see what happens now with 3.3.3.
>
> > Has anyone seen this kind of problem before? Could it be a hardware problem?
> > Will clearing the config in flash and redefining the config clean this up?
> > Should the COMOS be upgraded and can the ComOS be upgarded without a
> > network connection (ie via PC and console port) - should this be an RFE?
>
> Why wouldn't you just upgrade it via the WAN port, or hook up the PC via
> an ethernet card to the PM? I think a serial port load would take forever
> at 9600 baud.
Well the Wan connection is only 56Kbps with typical turnaround times of
500 ms (there is alot of network between me at the PM2). 9600 does not look
that bad in these conditions. While the unit was behaving erraticly
I could not maintain a connection via the WAN port (reboots and what appeared
to be lockups as well). As such I was concerned that the upgrade may not be
completable. The location that the PM2 is installed in had no LAN facilities
and I do not have a LAN card in the laptop I use for field work (yes, I know
I should).
It is always nice to know that you can use good old RS-232 as a connection
medium. I figure that I can flash upgrade my Supra modem using X-modem
protocol, why can't I do something similar with the PM2.
>
> There is a way to upgrade via the console port, but I've heard of the
> ComOS getting corrupted during the upload.
I guess alternatively a PPP connection via one of the async ports could be
used but that may not be acheivable with the unit constantly reseting the
ports!
>
> Brian
>
Thanks again to all who responded to me.
-- Darren R Besler PO Box 2207 Stn Main Beehive Enterprises Winnipeg, Manitoba, Canada, R3C 3R5 Ph: 204-896-6103 Fax: 204-896-4168 Email: dbesler@beehive.mb.ca