Click the Diag button to present the Diagnostics View.
Use this view to execute Trace Route, Ping commands, and to look at a current Routing Table.
To execute trace route at the Monitor Tool:
The Monitor Tool trace route provides information about the route between the node running Monitor Tool and the node specified by the Destination Address you type in the trace route field.
PingThe Ping diagnostic tool confirms
connectivity between the node that is running Monitor Tool and the specified node.To execute Ping at the Monitor Tool:
Ping sends a message once a second for the number of seconds specified in the Repeat Times field.
If the Ping is unsuccessful, it will report that 0 packets were received
Routing Table
This tool shows information about the network status.
To present a routing table at the Monitor Tool:
The following figure shows an example of a routing table (partial view).
The section that follows describes the fields in the routing table.
Flag |
Name |
Definition |
---|---|---|
1 | RTF_PROTO2 | Protocol specific routing flag #1 |
2 | RTF_PROTO2 |
Protocol specific routing flag #2 |
3 | RTF_PROTO3 |
Protocol specific routing flag #3 |
B | RTF_BLACKHOLE |
Just discard pkts (during updates) |
C | RTF_CLONING |
Generate new routes on use |
c | RTF_PRCLONING |
Generate new routes on use (protocol-specified) |
D | RTF_DYNAMIC |
Created dynamically (by redirect) |
G | RTF_GATEWAY |
Destination requires forwarding by intermediary |
H | RTF_HOST |
Host entry (otherwise, net) |
L | RTF_LLINFO |
Valid protocol to link address translation |
M | RTF_MODIFIED |
Modified dynamically (by redirect) |
R | RTF_REJECT |
Host or net unreachable |
S |
RTF_STATIC |
Manually added |
U | RTF_UP |
Route usable |
W | RTF_WASHCLONED |
Route was generated as a result of cloning |
X | RTF_XRESOLVE |
External daemon translates proto to link address |