NTX_DLLI(1) — USER COMMANDS

NAME

ntx_dlli − access the diagnostic link layer interface

SYNOPSIS

ntx_dlli [−d device] [−f framesize] [−h] [−l] [−v] [−s [−r repeat_count] [−c|−n]]
ntx_dlli [−d device] [−f framesize] [−h] [−v] [−e [−i iterations]]

DESCRIPTION

Ntx_dlli accesses the diagnostic link layer interface (DLLI) to test the DLLI functions. Additionally, ntx_dlli may be used, for testing purposes, to generate spurious traffic on the network, even to saturate the network bandwidth.

Note that DLLI is a simple diagnostic interface only. Its message-passing interface is not sufficient to support higher-layer protocols above it, and should not be used as a general purpose interface to the link layer.

In normal mode, ntx_dlli transmits link layer frame(s), which are compiled-in, and then enters an endless loop, receiving frames from the link layer and displaying them on the standard output device in raw hexadecimal format. Terminate ntx_dlli with a KILL signal.

In external loopback mode, ntx_dlli enters a loop where it transmits a compiled-in frame, receives it back, and verifies that it received what it sent. This loop is endless unless the −i flag is given, then the loop is executed iteration times. In external loopback mode, an external loopback connector is required on the AUI port, and no output is printed unless the −v flag is specified.

Ntx_dlli uses a 64-byte compiled-in frame. With the −f flag on the command line, this may be enlarged to 1024 bytes.

OPTIONS

−dSet the MVME339 raw device file name. This option will override the default MVME339 device name of /dev/xedt/mvme338_c0.

−fSpecify a framesize other than the default 64 bytes. The maximum is 1024 bytes.

−hGet the file descriptor for the NTX board from stdin. This is only useful when running ntx_dlli via execve(2). Command lines of the type "ntx_dlli ... −h < device" will not work due to shell handling of redirection.

−lLose receive frames. When in the receive loop, do not display the frames on the standard output device. Just discard them, and try to receive another frame.

−vVerbose output. At end of execution, print the number of transmitted and received frames. Used with −e option, print the result of each transmit/receive/compare loop.

−sTransmit a predefined, compiled-in frame on the network. The default is to not transmit anything and proceed to enter the endless receive-frame loop. This flag is mutually exclusive with the −e flag.

−rRepeat count. For each DLLI transmit request the host (ntx_dlli) sends to the board, transmit the Ethernet frame repeat_count times. This option is useful for network loading tests. This flag is only valid when used in conjunction with the −s flag.

−cContinuous transmission. Perform the DLLI transmit request endlessly until ntx_dlli exits upon receipt of a KILL signal. This flag is only valid when used in conjunction with the −s flag.

−nWhen the transmission(s) are complete, exit without entering the endless receive-frame loop. This flag is only valid when used in conjunction with the −s flag.

−eRun ntx_dlli in external loopback mode. Frames are actually sent and received over the network port, where an external loopback connector is required. Received frames are then checked against the transmitted ones for consistency. If too many errors are recorded, ntx_dlli will exit. This mode is used to continually drive the hardware. The transmit/receive/compare loop will execute indefinitely and exit upon receipt of a KILL signal. If the −i flag is given, the loop will execute iteration times. This flag is mutually exclusive with the −s flag.

−iSpecify the number of transmit/receive/compare iterations to be executed. This flag is only valid when used in conjunction with the −e flag.

FILES

/dev/xedt/mvme338_c0
~/include/ntx/net.h

Museum