Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Performing a TraceRoute on a device by using the TR line command
A TraceRoute is a series of pings that progress outward in incremental hops from the
BMC AMI Ops Monitor for IP
client to the final trace target destination. By default, each hop is sent three requests; the response time is determined from these requests.
Use one of the following procedures to perform a TraceRoute on a device by using the TR line command.
- Select an IP address that is displayed in the Tracerte IPAddr field
- Type a TRACEROUTE command on the COMMAND line
- Issue the TR line command from a Tracerte Information view
To issue the TR line command from a connections view
- From the EZIP menu, select CONNECTIONS from the TCP/IP Activity section.
From the EZCONS menu, select one of the following types of connections from the CONNECTIONS section and press Enter:
- All
- Listen
- Active
- TCP
- UDP
- TN3270
- SMC
The panel for the selection is displayed with a list of IP addresses. For example, selecting All displays the ALLCONS panel.
In the CMD field, type TR beside the IP address to be traced, and then press Enter.The TraceRte Connection pop-up is displayed:
+--------------------------- TraceRoute Connection ---------------------------+
| |
| Specify IP Address or Host Name |
| IPAddress: 172.28.21.73 |
| Host Name: |
| |
| TCPIP Stack: |
| Attempts: 3 (1-20) |
| Max Hops: 30 (1-255) |
| Max Wait: 5 (1-255) |
| Port: 33434 (2048-60000) |
| Command Wait: 10 (3-180) |
| |
| Intfname: |
| Source IP Address: |
| |
| END to TraceRoute connection |
| CANCEL to NOT TraceRoute connection |
| HELP to view related help |
| |
| |
| |
| COMMAND ===> SCROLL ===> CSR |
+-----------------------------------------------------------------------------+
Edit the fields as needed and press F3:
- For TCP/IP stack, specify the TCPIP Stack to use when issuing the PING command.
- For Attempts, specify the maximum number of attempts that BMC AMI Ops Monitor for IP should try.
- For Max Hops, specify the maximum number of hops on the traceroute (The valid values are 1-64, and the default is 32)
- For Max Wait, specify the maximum wait on each hop of the traceroute (The valid values are 1-255, the default is 5 seconds).
- For Port, specify the port number to use when performing the traceroute the IP address.
- For Command Wait, specify the time (seconds) to wait for the traceroute command.
- For Intfname, specify the local interface over which the packets will be sent.
- For Source IP Address, specify the source IP address that BMC AMI Ops Monitor for IP will use to send packets.
The following figure shows the TRACED view:
06NOV2020 ------------------------------------------------- BMC AMI Ops WINDOW INTERFACE (V7.0.00)
CURR WIN ===> 1 ALT WIN ===>
>W1 =TRACED============TCPIP====*========06NOV2020==05:38:17====MVIP=====D====1====================
TraceRoute Parms
Host Name........... am-mbauman-w1.bmc.com
IP Address.......... 172.28.21.73
Port................ 33434
Max Hops............ 30
Max Wait............ 5
Max Attempts........ 3
Stack Name..........
Interface Name......
Source IPAddr.......
Command Wait........ 10
Response Data
Status.............. Successful
1 ips-prod-core-usa-phx2-int-mf-trust2.bmc.com (172.24.51.253) 1 ms 1 ms 1 ms
2 172.24.240.163 (172.24.240.163) 1 ms 1 ms 1 ms
3 sw-agg-usa-phx2-02-po30.bmc.com (172.24.252.73) 1 ms 1 ms 1 ms
4 rtr-level3-p2p-usa-phx2-t001.bmc.com (172.24.252.81) 0 ms 1 ms 1 ms
5 rtr-twtc-p2p-usa-aus2-ge004.bmc.com (172.24.252.13) 20 ms 21 ms 20 ms
6 sw-agg-usa-aus2-02-vlan80.bmc.com (172.22.252.83) 22 ms 22 ms 26 ms
7 ips-egr-usa-aus2-vpn-trust.bmc.com (172.22.252.36) 21 ms 21 ms 21 ms
8 am-mbauman-w1.bmc.com (172.28.21.73) 67 ms * 67 ms
Related topics