4.2 RFNM count problem

malis at BBNCCS.ARPA malis at BBNCCS.ARPA
Sun Oct 28 06:49:50 AEST 1984


From:  Andrew Malis <malis at BBNCCS.ARPA>

Art and Ron,

The IMP always resets its RFNM counters under any of the
following circumstances:

1. The IMP was restarted by the NOC.

2. The host flapped or dropped its ready line to the IMP.

3. The host went tardy to the IMP, and then recovered.

All of these conditions cause the IMP to send NOPs and an
Interface Reset to the host, which the host can use as a signal
that RFNM counters have been reset.  So, the code in Ron's
message should do the trick, given that "hostreset()" does the
right thing.

Section 3.2 of BBN Report 1822 accurately discusses the second
and third cases that I list above, but does neglect to mention
that the RFNM counters are reset.

Andy



More information about the Comp.unix.wizards mailing list