ltpcli(1) [debian man page]

LTPCLI(1)							  BP executables							 LTPCLI(1)

NAME

       ltpcli - LTP-based BP convergence layer input task

SYNOPSIS

       ltpcli local_node_nbr

DESCRIPTION

       ltpcli is a background "daemon" task that receives LTP data transmission blocks, extracts bundles from the received blocks, and passes them
       to the bundle protocol agent on the local ION node.

       ltpcli is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol; the text of
       the command that is used to spawn the task must be provided at the time the "ltp" convergence layer protocol is added to the BP database.
       The convergence layer input task is terminated by bpadmin in response to an 'x' (STOP) command.	ltpcli can also be spawned and terminated
       in response to START and STOP commands that pertain specifically to the LTP convergence layer protocol.

EXIT STATUS

       0   ltpcli 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 bpadmin to restart ltpcli.

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

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

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

       ltpcli can't attach to BP.
	   bpadmin has not yet initialized Bundle Protocol operations.

       No such ltp duct.
	   No LTP induct matching local_node_nbr has been added to the BP database.  Use bpadmin to stop the LTP convergence-layer protocol, add
	   the induct, and then restart the LTP protocol.

       CLI task is already started for this duct.
	   Redundant initiation of ltpcli.

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

       ltpcli can't open client access.
	   Another task has already opened the client service for BP over LTP.

       ltpcli can't create receiver thread
	   Operating system error.  Check errtext, correct problem, and restart LTP.

BUGS

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

SEE ALSO

       bpadmin(1), bprc(5), ltpadmin(1), ltprc(5), ltpclo(1)

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

DCCPCLI(1)							  BP executables							DCCPCLI(1)

NAME

       dccpcli - DCCP-based BP convergence layer input task

SYNOPSIS

       dccpcli local_hostname[:local_port_nbr]

DESCRIPTION

       dccpcli is a background "daemon" task that receives DCCP datagrams via a DCCP socket bound to local_hostname and local_port_nbr, extracts
       bundles from those datagrams, and passes them to the bundle protocol agent on the local ION node.

       If not specified, port number defaults to 4556.

       Note that dccpcli has no fragmentation support at all. Therefore, the largest bundle that can be sent via this convergence layer is limited
       to just under the link's MTU (typically 1500 bytes).

       The convergence layer input task is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the
       Bundle Protocol; the text of the command that is used to spawn the task must be provided at the time the "dccp" convergence layer protocol
       is added to the BP database.  The convergence layer input task is terminated by bpadmin in response to an 'x' (STOP) command.  dccpcli can
       also be spawned and terminated in response to START and STOP commands that pertain specifically to the DCCP convergence layer protocol.

EXIT STATUS

       0   dccpcli 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 bpadmin to restart dccpcli.

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

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

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

       dccpcli can't attach to BP.
	   bpadmin has not yet initialized Bundle Protocol operations.

       No such dccp duct.
	   No DCCP induct matching local_hostname and local_port_nbr has been added to the BP database.  Use bpadmin to stop the DCCP convergence-
	   layer protocol, add the induct, and then restart the DCCP protocol.

       CLI task is already started for this duct.
	   Redundant initiation of dccpcli.

       dccpcli can't get IP address for host.
	   Operating system error.  Check errtext, correct problem, and restart dccpcli.

       CLI can't open DCCP socket. This probably means DCCP is not supported on your system.
	   Operating system error. This probably means that you are not using an operating system that supports DCCP. Make sure that you are using
	   a current Linux kernel and that the DCCP modules are being compiled. Check errtext, correct problem, and restart dccpcli.

       CLI can't initialize socket.
	   Operating system error.  Check errtext, correct problem, and restart dccpcli.

       dccpcli can't get acquisition work area.
	   ION system error.  Check errtext, correct problem, and restart dccpcli.

       dccpcli can't create new thread.
	   Operating system error.  Check errtext, correct problem, and restart dccpcli.

BUGS

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

SEE ALSO

       bpadmin(1), bprc(5), dccpclo(1)

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