Lantronix MPS100 EPS Reference Manual - Page 191

Send Failure, Reason, Receive Failure, Connect Failure, Invalid Packet

Page 191 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223

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