Re: Now *MY* PM2e30 is rebooting!
Gary N. McKinney (gmckinney@megabits.net)
Wed, 02 Oct 1996 05:44:42 -0700
Michael J. Hartwick wrote:
>
> Mike, I have noticed something similar to 2). Next time someone freezes
> do a show sX on the port. In our case we have noticed that CTS is -. We
> are using GVC 28.8's and ComOS 3.3.2. I have had a couple of reboots, but
> none in about 6 days now...Knock on wood. I stuck a small LED between CTS
> and GND to "watch" the CTS line, and when the CTS was - after a freeze,
> the LED was still on.
>
> On Tue, 1 Oct 1996, Mike Greene wrote:
>
> >Livingston PM 2e30
> >
> >Livingston Enterprises PortMaster Version 3.3.1
> >System uptime is 2 hours 30 minutes
> >
> >System memory 1048576 bytes - 843076 used, 205500 available
> >64:1 160:6 2048:6 128:4 80:11 96:1 144:8 16:81 208:1 32:5
> >System nbufs 1400 - 51 used, 1349 available
> >
> >30 US Robotics 33.6 Couriers
> >
> >***********************************************************************
> >
> >I just added 6 more modems to my PM2e30 a week ago, now my nice stable PM
> >box is rebooting or resetting every so often. It did it this morning at
> >8:40 am and last night at 7:30pm plus a few other times last week.
> >
> >My PM has been very stable up until this expansion of the modems.
> >
> >We have two other problems that we have been dealing with since upgrading
> >from 3.1.4 to 3.3.1, and that is this:
> >
> >1) Disconnects - This happens to some users, even to my box at home with
> >various brands of modems. We have verified the following on both ends of
> >the circuit.
> >
> >a) flow control
> >b) init strings
> >c) voltage on phone lines
> >d) db levels on phone lines
> >
> >2) "hung" connections, by hung I mean the modems are connected but I cannot
> >ping the remote client, the RD/SD lights flicker but no data gets transferred.
> >
> >Same steps were taken to track this problem down to no avail happens with
> >Win 3.x (trumpet, and MS Explorer dialer, and Netscape dialer) and Win95
> >clients, we don't know about Mac's but will check into it.
> >
> >I'm going to try the following for the disconnect problem,
> >
> >Increase the Carrier drop delay timeout from .5 to 2 seconds
> >
> >I don't know what to do about the hung connections and the reboots... well?
> >
> >I recall some dialog between John and another fellow that was gathering
> >stats on the disconnect/reconnect issue and found that the pattern the
> >customer fits ours too, however I do not have the time nor the background to
> >do this sort of detailed analysis. What became of this disscussion?
> >
> >Bottom line is:
> >
> >I am reluctant to try upgrading my PM to 3.3.2c1 since everything has been
> >more or less tolerant with my term server, however if this
> >reboot/disconnect/hung condition continues or gets worse I'll be forced to
> >do this upgrade. I've been holding out in hopes that there will be some
> >real progress in solving these problems either by software or hardware fixes.
> >
> >If this is a problem on my end then by all means show me what I'm doing
> >wrong, otherwise lets get some answers.
> >
> >I will be opening a support ticket on this to get it into the queue.
> >
> >- Mike
> >____________________________________________________
> >Mike Greene (mikeg@rockisland.com) / Internic (MG42)
> >Rock Island Internet / Office Ph. 360.378.5884
> >
>
> ----------------------------------------------------------------------------
> Michael J. Hartwick, VE3SLQ
> Hartwick Communications Consulting
> hartwick@primeline.net
Hi guys ... We had "problems" from the get-go with our PM2E30 (which came with
3.2.2 already loaded - bought the unit in July 96) connected to 30 USR
Sportsters (unit would cough a hairball and panic reboot whenever anyone tryed to
login to the unit). We had to upgrade to 3.2.2c1 "right out of the box" so to
speak and since then we have not had one single problem with the PM2E30 being
fully loaded.
Info from the unit:
Livingston Enterprises PortMaster Version 3.3.2c1
System uptime is 45 days 12 hours 24 minutes
>From what I've seen on the "list" I would perform the upgrade to 3.3.2c1 as I
have not seen many state they are NOT having problems with 3.3.2 version of the
software.
Hope the info helps...
GM..