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)

LTPCLOCK(1)							  LTP executables						       LTPCLOCK(1)

NAME

       ltpclock - LTP daemon task for managing scheduled events

SYNOPSIS

       ltpclock

DESCRIPTION

       ltpclock is a background "daemon" task that periodically performs scheduled LTP activities.  It is spawned automatically by ltpadmin in
       response to the 's' command that starts operation of the LTP protocol, and it is terminated by ltpadmin in response to an 'x' (STOP)
       command.

       Once per second, ltpclock takes the following action:

	   First it manages the current state of all links ("spans").  In particular, it checks the age of the currently buffered session block
	   for each span and, if that age exceeds the span's configured aggregation time limit, gives the "buffer full" semaphore for that span to
	   initiate block segmentation and transmission by ltpmeter.

	   In so doing, it also infers link state changes ("link cues") from data rate changes as noted in the RFX database by rfxclock:

	       If the rate of transmission to a neighbor was zero but is now non-zero, then transmission to that neighbor is unblocked.  The
	       applicable "buffer empty" semaphore is given if no outbound block is being constructed (enabling start of a new transmission
	       session) and the "segments ready" semaphore is given if the outbound segment queue is non-empty (enabling transmission of segments
	       by the link service output task).

	       If the rate of transmission to a neighbor was non-zero but is now zero, then transmission to that neighbor is blocked -- i.e., the
	       semaphores triggering transmission will no longer be given.

	       If the imputed rate of transmission from a neighbor was non-zero but is now zero, then all timers affecting segment retransmission
	       to that neighbor are suspended.	This has the effect of extending the interval of each affected timer by the length of time that
	       the timers remain suspended.

	       If the imputed rate of transmission from a neighbor was zero but is now non-zero, then all timers affecting segment retransmission
	       to that neighbor are resumed.

	   Then ltpclock retransmits all unacknowledged checkpoint segments, report segments, and cancellation segments whose computed timeout
	   intervals have expired.

EXIT STATUS

       0   ltpclock terminated, 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 ltpclock.

       1   ltpclock was unable to attach to LTP protocol operations, probably because ltpadmin has not yet been run.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

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

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

       Can't dispatch events.
	   An unrecoverable database error was encountered.  ltpclock terminates.

       Can't manage links.
	   An unrecoverable database error was encountered.  ltpclock terminates.

BUGS

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

SEE ALSO

       ltpadmin(1), ltpmeter(1), rfxclock(1)

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