LocalTalk and GatorStar Statistics
The following packet and error statistics appear within the LocalTalk Statistics window:
Packets Fields
The Packet Fields display general performance information on the LocalTalk interface are as follows:
In Packets | The total number of good packets received by the |
| LocalTalk interface. |
Out Packets | The total number of packets transmitted from the |
| LocalTalk interface. |
Hard Errors
Hard errors are error conditions caused by physical layer problems, such as faults in the hardware, equipment, or wiring. Hard error fields are as follows:
In Errors | The total number of packets containing errors received |
| on the LocalTalk interface. In Errors are |
| magenta. |
Collisions | The total number of collisions assumed on the LocalTalk |
| interface due to the lack of a lapCTS (link access protocol |
| Clear To Send) reply. Collisions are |
Soft Errors
Soft errors are error conditions caused by corrupted data signals, such as failure along the transmission path. Soft error fields are as follows:
In No Handlers | The total number of good packets received on the |
| LocalTalk interface for which there was no protocol |
| handler. In No Handlers are |
In Length Errors | The total number of packets received on the LocalTalk |
| interface in which the actual packet length did not match |
| the length specified in the header. In Length Errors are |
| |
Defers | The total number of times the LocalTalk interface |
| deferred to other packets (postponed sending a packet |
| until after packets from other ports had already been |
| sent). This usually indicates that the network was busy |
| when the port wanted to send data. The link has to be |
| idle for at least 400 microseconds before it will start to |
| transmit. |
No Data Errors | The total number of times the LocalTalk interface |
| received a lapRTS (link access protocol Request To Send) |
| packet and expected a data packet, but did not receive |
| any data packets. |
Viewing LocalTalk Statistics |