L - Walden-family.com
L - Walden-family.com
L - Walden-family.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Bolt Beranek and Newman<br />
Inc.<br />
the idle buffer for output, there is a cyclic permutation of<br />
the input, output, and free buffers.<br />
Each of the routing messages sent and received carries a<br />
software checksum. In addition, the input, output, and timeout<br />
processes for routing all <strong>com</strong>pute a checksum on the program<br />
before executing it, and a reload is initiated in the event of<br />
failure. These reliability measures are discussed in more<br />
detail in the next section.<br />
2.5 Failure Protocols<br />
The network is designed to be largely invulnerable to circuit<br />
or IMP failure as well as to outages for maintenance. Special<br />
status and test procedures are employed to help cope with various<br />
failures. In the normal course of events the IMP program transmits<br />
hello bits in its routing messages. The acknowledgment<br />
for a hello packet is an I-heard-you (IHY) bit in a returning<br />
null packet.<br />
A dead line is detected by the sustained absence (approximately<br />
3.2 sec) of IHY messages on that line. No regular<br />
packets will be routed onto a dead line, and any packets awaiting<br />
transmission will be rerouted. Routing tables in the network<br />
are adjusted automatically to reflect the loss. Receipt of<br />
thirty consecutive I-heard-you packets is required (an event<br />
which consumes at least 15 seconds) before a dead line is defined<br />
to be alive once again.<br />
A dead line may reflect trouble either in the <strong>com</strong>munication<br />
facilities or in the neighboring IMP itself. Normal<br />
line errors caused by dropouts, impulse noise, or other similar<br />
conditions should not result in a dead line, because such<br />
2-14 9/73<br />
l<br />
_]<br />
I]<br />
J<br />
J<br />
1<br />
_j<br />
J