Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Disconnect Code 35?
At 01:15 PM 3/9/98 +0100, Andre Beck wrote:
>From the Event MIB:
>
>mpNullMessageTimeout(35), -- failed to receive a NULL MP message
>
>Not that I knew what it means - I had one of my low level bundled E1
lines
>go down with this cause in 6.0, never seen it before.
>From RFC 1990:
<bigger>Loss of the final fragment of a transmission can cause the
receiver to stall until new packets arrive. The likelihood of this may
be
decreased by sending a null fragment on each member link in a bundle
that would otherwise become idle immediately after having transmitted a
fragment bearing the (E)nding bit, where a null fragment is one
consisting only of a multilink header bearing both the (B)egin and
(E)nding bits (i.e., having no payload). Implementations concerned about
either wasting bandwidth or per packet costs are not required to send
null fragments and may elect to defer sending them until a timer expires,
with the marginally increased possibility of lengthier stalls in the
receiver. The receiver SHOULD implement some type of link idle timer to
guard against indefinite stalls.
</bigger>
Matt Holdrege http://www.ascend.com matt@ascend.com
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: