6: Basic Parameters
SLC™ 8000 Advanced Console Manager User Guide 113
To view results for a Performance Monitoring probe:
1. Click the Network tab and select the Perf Monitoring option. The Network > Perf Monitoring
page displays.
2. Select a probe from the table in the lower part of the page and select the Operations link. The
Performance Monitoring - Operations page displays.
Figure 6-13 Performance Monitoring - Operations
3. A table will list all available operations for the selected probe, with the most recent operation
listed first. The table may be empty if no operations have been run for the probe or the
operations for the probe have been deleted. Select an operation by clicking the radio button to
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 SLC 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.
Error Condition Description
To Next Page
Loading...
Need help?
General
