Re: PM2e-30/ComOS-3.3.2: telnet refused, dialup unreliable --

Administrator (admin@emporium.on.ca)
Sat, 21 Dec 1996 15:22:51 -0500

At 09:47 AM 12/21/96 -0800, you wrote:
>We've had this problem for two years and continue to have it. If you
>routinely telnet into your PM, plan on rebooting it every 3-4 weeks as a
>precaution. On the other hand, if you leave it alone, it will run for
>months.

I telnet into PMs on a daily basis. Sometimes old sessions go 'stale'
especially if you use a Windoze telnet client and just kill it rather than
exiting properly. Once you have about 3 of these, the box will refuse any
admin telnets. You just have to do some housekeeping once in a while to
clear the dead sessions.

Command> ver
Livingston Enterprises PortMaster Version 3.3.1
System uptime is 84 days 3 hours 26 minutes

To find old sessions, use the "sh netc" command. Look for .23 telnets that
have gone bad and reset them by using the command reset n# where # is the
first number on the line of the offending session (of the sh netc output).

I have had the above PM in service for about 8 months and have rebooted it
once when my upstream screwed up and I got in a panic 'cause I thought it
was me and reset *everything* ;) (pissed me off cause I had an uptime of
over 150 days)

Scott