cli:tmss10ping
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cli:tmss10ping [2017/06/07 11:04] – [Environment] Gerard Nicol | cli:tmss10ping [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== TMSS10Ping ====== | ====== TMSS10Ping ====== | ||
| - | Test the connection with a TapeTrack Framework Server. | + | |
| + | Command line programs are executed via a [[technote: | ||
| ===== Synopsis ===== | ===== Synopsis ===== | ||
| - | '' | + | '' |
| ===== Description ===== | ===== Description ===== | ||
| - | TMSS10Ping sends dummy packets to a TapeTrack Framework Server and receives a reply packet. It | + | '' |
| - | should be noted that unlike the ping command, TMSS10Ping sends payload packets via the TCP/IP protocol. | + | |
| + | <note tip> | ||
| + | Unlike the [[https:// | ||
| + | </ | ||
| ===== Options ===== | ===== Options ===== | ||
| The options which apply to the TMSS10Ping command are: | The options which apply to the TMSS10Ping command are: | ||
| - | * '' | + | * '' |
| - | * '' | + | * '' |
| - | * '' | + | * '' |
| ===== Exit Status ===== | ===== Exit Status ===== | ||
| Line 23: | Line 26: | ||
| * [[variable: | * [[variable: | ||
| * [[variable: | * [[variable: | ||
| + | |||
| + | ===== Files ===== | ||
| + | |||
| + | * '' | ||
| ===== Examples ===== | ===== Examples ===== | ||
| Line 36: | Line 43: | ||
| --- tapetrack.ironmountain.com TMSS10Ping statistics --- | --- tapetrack.ironmountain.com TMSS10Ping statistics --- | ||
| 4 packets transmitted | 4 packets transmitted | ||
| - | TMSS10Ping | + | |
| - | 2 | + | |
| round-trip min/avg/max = 0.00/ | round-trip min/avg/max = 0.00/ | ||
| </ | </ | ||
| Line 49: | Line 55: | ||
| fi | fi | ||
| </ | </ | ||
| - | Example 1. TMSS10Ping: send pings request via a proxy server, creates a trace file | + | |
| - | and displays the trace file. | + | This example sends ping request via a proxy server, creates a trace file and displays the trace file. |
| + | |||
| + | < | ||
| set PROXYIP=192.168.1.10 | set PROXYIP=192.168.1.10 | ||
| set PROXYPORT=3128 | set PROXYPORT=3128 | ||
| Line 63: | Line 71: | ||
| type " | type " | ||
| pause | pause | ||
| - | Set variable for HTTP Proxy Server address. | + | </code> |
| - | Set TCP/IP port of HTTP Proxy Server. | + | |
| - | Set variable for HTTP Proxy Server User-ID (if any). | + | |
| - | Set variable for HTTP Proxy Server password (if any). | + | |
| - | Set variable for HTTP Proxy Server address. | + | |
| - | Set variable for TapeTrack Server address. | + | |
| - | Set variable for TapeTrack Server port. | + | |
| - | Set variable for output directory to Windows temp folder. | + | |
| - | Set variable that tells TMSS10Ping to go via a proxy. | + | |
| - | Run TMSS10Ping command. | + | |
| - | List the results. | + | |
| - | Files | + | |
| - | stdout Program messages indicating statistics from ping. | + | |
| - | See Also | + | |
| - | TMSS10(1) | + | |
| - | Bugs | + | |
| - | On the Linux platform all TapeTrack command line programs are compiled with static C runtimes. This | + | |
| - | means that on some older Linux versions DNS name resolution does not work and you must use dotted | + | |
| - | IP addresses. | + | |
| - | TMSS10Ping | + | |
| - | 3 | + | |
| + | --> Changelog | ||
| + | [filterrss http:// | ||
| + | <-- | ||
| + | <- ^ cli: | ||
cli/tmss10ping.1496833456.txt.gz · Last modified: 2025/01/21 22:07 (external edit)
