Re: Trouble with ComOS 3.3.3

Jacob Suter (jsuter@intrastar.net)
Fri, 29 Nov 1996 03:27:53 -0600

> Just one thing I need to know:
>
> Was it written in the Project Assignment for Livingston guys that
> ComOS 3.3.3 has to reboot PM-2e-30 every 3 days???? The biggest
> problem is not just the reboot itself, but rather problems after it
> reboots itself. We have to do a "hard" reboot on PM - flip the power
> switch - or otherwise it will never accept any connections.... So,
> afterwards downtime for 10 hours is not a "biggy" but customers
> somehow get upset (I wonder, why???)

It seems strange, but my connection seems to get boggy (I have an
PM2-ER-10) after I read between 1 gig and 2 gigs through the WAN port. I
have never had a chance to get it over 2.2 gigs (the one time my generator
decided to lock up).

I run 3.3.3, and have since the day it was released... Here are my current
stats..

----------------------- Current Status - Port W1
---------------------------
Status: ESTABLISHED
Input: 952432532 Abort Errors: 11
Output: 167748315 CRC Errors: 0
Pending: 0 Overrun Errors: 0
TX Errors: 0 Frame Errors: 0
Modem Status: DCD+ CTS+

pm1> ver
Livingston Enterprises PortMaster Version 3.3.3
System uptime is 6 days 44 minutes
pm1>

I've never had it over 12 days (that was the time I ran 2.2 gigs). Right
now its running great.. I am running 6.3K/sec through it on an FTP, which
is about all I can ask off a non-compressed 56K...

I've only power cycled my PM from the power switch or outside problem (UPS
runs out eventually) a couple times, because it was easier than finding a
console and saying 'reboot'... or all the telnets were locked up.

Of course, everyones milage varies... I get 50 MPG in my 1978 Ford Van w/
4bbl, and 5 MPG in a geo (are geo's designed to pull 10,000 pounds?)...

JS