Re: PM2-ER WAN port CRC errors and lockups

Charles Scott (cscott@freeway.net)
Tue, 12 Sep 1995 08:12:09 -0400 (EDT)

Stefan:
Let me guess. You have a PM2ER-30? We have tried 2 PM2ER-30's with
and had problems with both that were similar to what you describe. Do you
run PPP or SLIP connections on that PortMaster or login only. We find
that the problem is data content sensitive and has more problems with
data from binary and image transfers. It's particularly apparent for
users who do Web browsing where it seems to come to a virtual halt
(apparently as it has a problem getting good packets over the WAN port).
Do this. Ping your PortMaster over the W1 port using a pattern of ff.
Start with a short packet then try larger ones. With the units we have
the following is guarenteed to cause serious problems.

ping -s 1400 -p ff {pm address}

When we do this, we immediatly get CRC and Framing errors on the WAN
port. One of the units will totally stop communicating over the WAN port
until it's reset. We have received dammaged packets back from them when
pinging them this way which indicate that the first few characters fail
and the rest of the packet is OK.
The interesting thing is that when, under Livingston's direction, we
disconnected the 20 additional ports by disconnecting the bus cable from
the main board, the problem went away. However, that leaves us with only
10 ports.
We have had an open trouble ticket on these for more than a month now
and I'm getting a bit concerned. It's our guess that they have a problem
with that data bus, or at least the drivers associated with the WAN
port but have not yet received any confirmation of that from Livingston.
FYI, we're running the WAN port at 56K on those units. I've had
messages back from other people who are running at other speeds that they
do not have this problem. Almost sounds like ringing on the data bus,
which I can believe because it appears to be terminated at one end only.
Please let me know if this matches your experience and if you can
verify it with the ff ping.

Chuck Scott, Pres.
Freeway, Inc.
cscott@freeway.net

On Mon, 11 Sep 1995, Stefan Hudson wrote:

> We have a PM2-ER running ComOS 3.1.2. At seemingly random intervals,
> ranging from a few minutes to a few days, the W1 port will lock up and
> stop passing packets. Every time this happens, there are one or two
> CRC errors reported. After reseting the port, everything works fine,
> and the CRC error counter goes back to zero.
>
> Any ideas what could be causing this, or what the best solution is?
> I'm about to write something that tests the connection with pings, and
> resets the port if it doesn't get a response for 30 seconds or so, but
> this is an ugly solution.
>
> I'm tempted to try the beta ComOS version that was just released to
> fix the telnet security bug, but Livingston doesn't support Linux (WHY?
> It can't be THAT hard to port pmconsole from one Unix to another? Hell,
> give us the source and WE'LL do it!), and I'm REALLY hesitant to trust
> something as mission-critical as the terminal server brains to a hack
> like windoze.
>
> Thanks,
> --
> /// Stefan Hudson <hudson@mbay.net>
> __ /// Senior Network Administrator
> \\\/// Monterey Bay Internet - Email: info@mbay.net
> \XX/ Voice: 408-642-6100 Fax: 408-642-6101 Modem: 408-642-6102
>