7: Networking
EMG™ Edge Management Gateway User Guide
144
Positive Min/Avg/Max: 0/0/0 msec
Positive Number Of/Sum of All/Sum of All Squared: 0/0/0 msec
Negative Min/Avg/Max: 0/0/0 msec
Negative Number Of/Sum of All/Sum of All Squared: 0/0/0 msec
Number of Successes: 10
Number of Errors: 0
Lost Packet: 0 (0%)
Out of Sequence: 0
Late Arrival: 0
Miscellaneous Error: 0
Table 7-16 Error Conditions Detected by Probes
The following error conditions are detected by the probes. Except where noted, the RTT results for
a packet with errors will not be counted in the accumulated statistics.
Error Condition
Description
Timeout
A response was never received for the packet. These packets are listed as
Lost Packets under the accumulated statistics.
Late Arrival
A response was received for a packet, but the response was received after
the timeout configured for the probe. The EMG will wait at most 2 times the
probe's timeout for late arrival packets. The RTT results will be included in
the accumulated statistics.
Not Connected
A packet could not be sent because the connection to the destination host
could not be established, or because the attempt to send the packet failed.
Sequence Error
A packet response was received with an unexpected sequence number.
Possible reasons are: a duplicate packet was received, a response was
received after it timed out, a corrupted packet was received and was not
detected.
Verify Data Error
A response was received for a packet with payload data that does not match
the expected data.
DNS Server Timeout
A DNS lookup could not be completed because the EMG could not connect
to the DNS name server.
DNS Lookup Error
A DNS lookup failed - the requested hostname could not be resolved. This is
not considered a protocol error, but rather an expected result, depending on
the hostname being resolved. The RTT results will be included in the
accumulated statistics.
TCP Connect Timeout
A TCP connect could not be completed because a connection to the TCP
server could not be established.
HTTP Transaction Timeout
An HTTP Get that failed because no response was received from the HTTP
server before the timeout expired.
HTTP Error
An HTTP Get succeeded, but the HTTP content (base page) that was
downloaded had errors: missing "HTTP/" header string, missing
"Connection: close" string, or response has an HTTP error code (the code
was not 200/OK). This is not considered a protocol error. The RTT results
will be included in the accumulated statistics.
Generic Error
Any error that does fall into any of the above error conditions.
Summary of Contents for EMG 7500
Page 100: ...7 Networking EMG Edge Management Gateway User Guide 100 Figure 7 5 Network Wireless Settings ...
Page 353: ...15 Maintenance EMG Edge Management Gateway User Guide 353 Figure 15 12 About EMG ...
Page 474: ...EMG Edge Management Gateway User Guide 474 Figure E 3 EU Declaration of Conformity ...
Page 475: ...EMG Edge Management Gateway User Guide 475 Figure E 4 EU Declaration of Conformity continued ...