udplso(1) [debian man page]

UDPLSO(1)							  LTP executables							 UDPLSO(1)

NAME

       udplso - UDP-based LTP link service output task

SYNOPSIS

       udplso {remote_engine_hostname | @}[:remote_port_nbr] [txbps] remote_engine_nbr

DESCRIPTION

       udplso is a background "daemon" task that extracts LTP segments from the queue of segments bound for the indicated remote LTP engine,
       encapsulates them in UDP datagrams, and sends those datagrams to the indicated UDP port on the indicated host.  If not specified, port
       number defaults to 1113.

       UDP congestion can be controlled by setting udplso's rate of UDP datagram transmission txbps (transmission rate in bits per second) to the
       value that is supported by the underlying network.

       Each "span" of LTP data interchange between the local LTP engine and a neighboring LTP engine requires its own link service output task,
       such as udplso.	All link service output tasks are spawned automatically by ltpadmin in response to the 's' command that starts operation
       of the LTP protocol, and they are all terminated by ltpadmin in response to an 'x' (STOP) command.

EXIT STATUS

       0   udplso terminated normally, for reasons noted in the ion.log file.  If this termination was not commanded, investigate and solve the
	   problem identified in the log file and use ltpadmin to restart udplso.

       1   udplso terminated abnormally, for reasons noted in the ion.log file.  Investigate and solve the problem identified in the log file,
	   then use ltpadmin to restart udplso.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued to the ion.log log file:

       udplso can't initialize LTP.
	   ltpadmin has not yet initialized LTP protocol operations.

       No such engine in database.
	   remote_engine_nbr is invalid, or the applicable span has not yet been added to the LTP database by ltpadmin.

       LSO task is already started for this engine.
	   Redundant initiation of udplso.

       LSO can't open UDP socket
	   Operating system error.  Check errtext, correct problem, and restart udplso.

       LSO can't connect UDP socket
	   Operating system error.  Check errtext, correct problem, and restart udplso.

       Segment is too big for UDP LSO.
	   Configuration error: segments that are too large for UDP transmission (i.e., larger than 65535 bytes) are being enqueued for udplso.
	   Use ltpadmin to change maximum segment size for this span.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       ltpadmin(1), ltpmeter(1), udplsi(1), owltsim(1)

perl v5.14.2							    2012-05-25								 UDPLSO(1)

Check Out this Related Man Page

LTPCOUNTER(1)							  LTP executables						     LTPCOUNTER(1)

NAME

       ltpcounter - LTP reception test program

SYNOPSIS

       ltpcounter client_ID [max_nbr_of_bytes]

DESCRIPTION

       ltpcounter uses LTP to receive service data units flagged with client service number client_ID from a remote ltpdriver client service
       process.  When the total number of bytes of client service data it has received exceeds max_nbr_of_bytes, it terminates and prints
       reception and cancellation statistics.  If max_nbr_of_bytes is omitted, the default limit is 2 billion bytes.

       While receiving data, ltpcounter prints a 'v' character every 5 seconds to indicate that it is still alive.

EXIT STATUS

       0   ltpcounter has terminated.  Any problems encountered during operation will be noted in the ion.log log file.

       1   ltpcounter was unable to start, because it could not attach to the LTP protocol on the local node or could not open access to client
	   service clientId.

	   In the former case, run ltpadmin to start LTP and try again.

	   In the latter case, some other client service task has already opened access to client service clientId.  If no such task is currently
	   running (e.g., it crashed while holding the client service open), use ltpadmin to stop and restart the LTP protocol.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       Diagnostic messages produced by ltpcounter are written to the ION log file ion.log.

       ltpcounter can't initialize LTP.
	   ltpadmin has not yet initialized LTP protocol operations.

       ltpcounter can't open client access.
	   Another task has opened access to service client clientId and has not yet relinquished it.

       Can't get LTP notice.
	   LTP system error.  Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       ltpadmin(1), ltpdriver(1), ltp(3)

perl v5.14.2							    2012-05-25							     LTPCOUNTER(1)

Linux and UNIX Man Pages

udplso(1) [debian man page]

Check Out this Related Man Page