Lantronix ETS Reference Manual page 272

Show/Monitor/List Commands
Bit Send Failure
Reason
0 Unused, should be 0
1 Unused, should be 0
2 At least one collision has
occurred while transmit-
ting
3 Transmit aborted due to
excessive (more than 16)
network collisions
4 Carrier sense was lost
during transmission
5 FIFO underrun: Ethernet
controller could not
access transmit data in
time to send it out
(ERROR)
6 ETS did not receive CD
heartbeat after transmit
7 Out-of-window collision
detected
8-15 Unused, should be 0
Examples
See Also
12-110
Table 12-12 shows the ETS failure reasons and their meanings.
Table 12-12: Failure Reasons
Receive Failure
Reason
Unused, should be 0
Packet received with
CRC error
Received packet did not
end on byte boundary
FIFO overrun: could not
write received data
before new data arrived
Receive packet could not
be accommodated due to
lack of available receive
buffers
Received a packet larger
than the maximum Ether-
net size (1536 bytes)
Unused, should be 0
Unused, should be 0
Unused, should be 0
Status
Displays current ETS use, such as active ports, services, and circuits.
Local> SHOW SERVER STATUS
Local> MONITOR SERVER COUNTERS
Set/Define Server Commands, page 12-62; General Server Parameters, page
4-1; Status Displays, page 6-9.
Connect Failure
Reason
Internal failure, should
be 0
Internal failure, should
be 0
No nameserver defined
for a text hostname
Attempted nameservice
failed
No gateway has been
configured for non-local
connections
Attempted ARP failed
Remote host did not
answer
Host rejected the con-
nection
Unused, should be 0
Command Reference
Invalid Packet
Reason
Data received outside
window
Connection terminated
abnormally
Packet received with an
invalid data checksum
Packet received with an
invalid data header
RST packet sent to
remote node
Packet received for an
unknown local user
Unused, should be 0
Unused, should be 0
Unused, should be 0