/LOOP=(test_parameters)
Starts a LOOP test, transmitting packets as specified in the
test_parameters and expecting the target to loop the packets back
to the sender.
/RECEIVE=(test_parameters)
Starts a RECEIVE test. The RECEIVE test receives LAN request
from a remote XX sender. If the sender sends LOOP request,
the request will be transmitted back to the sender.
/TRANSMIT=(test_parameters)
Starts a TRANSMIT test. The TRANSMIT test sends LAN request
as specified in the test_parameters but it does not wait for
the target to respond to the request.
test_parameters
The test parameters are a list of comma separated keywords.
vci - The test will use the LAN VCIB interface
qio - The test will use the LAN QIO interface
Note: These two parameters are exclusive, the tester
has to choose one or the other.
alignment = integer-value (default is zero)
This is the number extra of bytes to add before the
beginning of the user data. It is used to change the
byte alignment of the address of the user buffer (payload).
This parameter is only meaningful for LOOP and TRANSMIT
test, and should not affect the receiver.
Note that default zero, will cause alignment faults!
Alignment faults can be avoided by setting this parameter
to 2.
amc
noamc - all multicast mode (default is no amc)
Sets the LAN device in all multicast mode allowing
to receive ALL multicast requests. Tis parameter is only
valid for QIO/RECEIVE test.
chaining = integer-value (default is zero, no segmentation)
Segment a request into smaller sections. Each segment is
sent switching buffer address between Virtual Address and
PTE. This parameter is only meaningful for LOOP and TRANSMIT
test, and should not affect the receiver.
compare
nocompare (default is no compare)
Do data integrity check on the user buffer. This parameter is
only meaningful for RECEIVE and LOOP tests.
count = integer-value (default is zero, do not stop on counter)
Number of packets to process before stopping the test.
duration = integer-value (default is zero, do not stop on time)
Number of seconds to run before stopping the test.
echo = echo-keyword
This parameter is only valid when used with QIO parameter and
for RECEIVE test only. It displays the information about the
a receive packet. The echo-keyword are:
full - displays the entire content of the receive packet
header - displays only the header information
none - displays no information
partial - displays partial information
filter_pty = protocol-type
filter_sap = sap-type
filter_pid = pid-type
filter_address = MAC=address
This parameter is only valid when used with QIO parameter and
for RECEIVE test only. It displays the information about the
a receive packet filtering-in according to the values specified
in the parameters
flow_control - reserved
loopback_mode - Sets the NIC in loopback mode
noloopback_mode - Default is no loopback
Sets the NIC in loop back mode so transmit can
be send without the need of connecting cables.
No all NICs/driver support loopback mode and
not all PDU sizes are supported in loopback mode.
multicast_address = list-of-mac-multicast-addresses
This parameter setup a list of multicast address
to listen for. It is only valid with QIO/RECEIVE test.
pid - IEEE 802.E PID value if sending 802.E, QIO only.
pipeline = integer-value (default is 1)
This is the number of simultaneous transmits a LOOP or TRANSMIT
test can do. By bumping up the pipeline more data will be
transmitted but at the risk of data loss in switch
and/or in the receiver system. On a TRANSMIT test and
depending on the NIC used, maximum data transfer will be
achieved with a pipeline around 32-64. Also, a VCRP is
allocated per count on the pipeline, therefore a large number
for this parameter will translate in higher pool usage while
the test is running.
loopline = integer-value (default is 1)
This is the number of outstanding transmits a LOOP
test can stand while waiting for a respond from the
receiver. By bumping up the loopline more data will be
transmitted but at the risk of data lost in switch (mostly)
and/or in the receiver system. A typical ES45 system with
gigabit NIC and a typical switch will stand a pipeline of
several thousands before losing packets in the switch.
To understand packet loss by the target system/NIC use
a point to point connection.
promiscuous_mode
nopromiscuous_mode (default is no promiscuous)
This parameter is only valid when used with QIO parameter and
for RECEIVE test only. It sets the NIC in promiscuous mode
allowing to receive ALL packets the adapter is able to receive.
pty = pty-value (defaults is 60-05 VMS-DIAG )
This parameter sets the user protocol for the test as
defined by the IEEE ethertype Field Registration Authority.
Values from 60-00 to 60-09 were originally assigned to
Digital Equipment Corporation and are still used by
VSI OpenVMS [60-01,60-02 MOP, 60-03 DECNET-IV, 60-04 LAT,
60-05 VMS-DIAG, 60-07 SCA]
rate = integer-value (default is 0, send as fast as possible)
This parameter sets the maximum number of packets to send
in a single second. It is only valid for TRANSMIT and
LOOP tests.
sap - IEEE 802.E PID value if sending 802, QIO only
size = (size-list)
This a comma separated list of integer-value data sizes to
send. It is only valid for TRANSMIT and LOOP tests.
stop_error
nostop_error - (default is no stopping)
Stop the test if an error is encountered.
stop_lostpacket
nostop_lostpacket - (default is no stopping)
Stop the test if packets get lost.
target_address = (mac-address-list)
This is a list of target MAC address for the LOOP and
TRANSMIT tests. QIO accepts up to 4 targets, while
VCI supports only one.
wait (default)
nowait
Requires waiting for the test to finish before
entering another command. The nowait parameter
allows entering new commands while the test is
running.
fastxmt (default)
nofastxmt
On fastxmt mode and right after the NIC has finished a
request, subsequent LOOP and TRANSMIT request
will be done by calling the transmision routine rather
than forking to it. This runs the risk of CPUSPINWAIT
crashes.
fastrcv (default)
nofastrcv
On fastrcv mode , receive request are processed on-line
and without giving up the CPU. On non fastrcv mode,
request are queued then processed by forking later on.
Fast rcv mode runs the risk of CPUSPINWAIT
crashes.