lclient Option Summary
The following command line options are available for mtping. For more information about MTP/IP bandwidth management and performance tuning options, see DEI Tech Note 0005.
These options apply to all modes of operation.
| CLI | Value | |
| -d | <0 to 6> | |
| Enable MTP/IP diagnostic output. Level 1 is recommended any time you are experiencing difficulties. Levels above 1 will produce copious output and may degrade performance. | ||
| -e | (Unix only) Take the count as an elapsed time for the test, instead of a number of bytes. | |
| -p | <port> | |
| Specify the UDP and TCP port number of the server. Use this option if the server is running on a port other than the default 8082. | ||
| -m | Use MTP/IP to perform the test. | |
| -R | Modify or remove license code registration. | |
| -t | Use TCP/IP to perform the test. | |
| -v | Display verbose output. The volume of text may be very high and may degrade performance. | |
These options apply only when -m is selected.
| CLI | Value | |
| -a | <-3 to 5> | |
| Advise MTP/IP as to how aggressive it should be in fully utilizing the network path. Positive values may increase performance at the expense of third-party traffic. Negative values may reduce path latency and allow better performance for other traffic, at the cost of reducing MTP/IP performance. | ||
| -A | <bytes> | |
| Set the starting address of the test request. | ||
| -l | <Kbytes/sec> | |
| Limit the rate of MTP/IP downloading to this many kilobytes per second. | ||
| -N | <4 to 5000> | |
| MTP/IP normally regards packet loss as an indication of network congestion. This option will cause MTP/IP to ignore packet losses up to a rate of one in N, for a given number N. For example, a value of 100 will cause MTP/IP to ignore a loss rate of up to 1%. This option should only be used on noisy data paths where loss is occurring due to external factors such as uncorrected bit errors. | ||
| -r | <milliseconds> | |
| Limit MTP/IP to prevent the observed path Round Trip Time from exceeding this many milliseconds. | ||
| -T | <bytes> | |
| Limit the size of network datagram payloads to no more than this amount. The full IP datagram size will be 56 bytes larger when MTP/UDP/IP headers are included. Tunneling, VPNs, IPsec, MPLS and other encapsulations will add more. If your network is known to have problems with IP fragmentation, try setting a value of 1424 or smaller. | ||
| -U | <bytes> | |
| Use network datagram payloads of at least this size. If your network path is very fast (gigabit or more) and every device along that path supports Jumbo frames (MTU 9000), you may be able to reduce CPU overhead by setting this to a value between 1424 and 8192. Use of this setting without Jumbo frames fully supported may cause severe performance problems or loss of connectivity. | ||