(PM) error: port S13 stopped too long (fwd)

MegaZone (megazone@megazone.org)
Wed, 22 Jul 1998 15:45:14 -0700 (PDT)

Once upon a time Butch Kemper shaped the electrons to say...
> pm3-1 error: port S37 stopped too long - flushing packet queue
>>Anyway, the port was flow controlled for too long, the buffer filled,
>>and was flushed.

Usually this is the users modem being flow controlled off, and then sticking
that way. Perhaps it is set for software flow control and a binary stream
contained the 'off' character.

On the PM make sure the ports are set for RTS/CTS ONLY - no XON/XOFF. Though
I don't believe this will impact the PM-3 - still, it is a good thing to do.

>Is this a problem with the boxes? If not, why does it only happen on 3 of
>the 4 boxes?

Can you correlate this with any particular users? Perhaps they just keep
landing on the first units in the hunt group. Are those three boxes more
heavily used? If it is a linear hunt, that would increase the probability
of them hitting those boxes.

>Is it possible that this problem is caused by something that the user does
>or their configuration?

Yes.

-MZ

-- 
<URL:mailto:megazone@megazone.org> Gweep, Discordian, Author, Engineer, me..
Join ISP/C Internet Service Providers' Consortium <URL:http://www.ispc.org/>
"A little nonsense now and then, is relished by the wisest men" 781-788-0130
<URL:http://www.gweep.net/>  <URL:http://www.megazone.org/>  Hail Discordia!
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>