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)
Check Out this Related Man Page
LTPCLO(1) BP executables LTPCLO(1) NAME
ltpclo - LTP-based BP convergence layer adapter output task SYNOPSIS
ltpclo [-]remote_node_nbr DESCRIPTION
ltpclo is a background "daemon" task that extracts bundles from the queues of segments ready for transmission via LTP to the remote bundle protocol agent identified by remote_node_nbr and passes them to the local LTP engine for aggregation, segmentation, and transmission to the remote node. If remote_node_nbr is preceded by a '-' character, then all LTP transmission performed by ltpclo will be "green" (unreliable) transmission, without acknowledgment and retransmission. Note that ltpclo is not a "promiscuous" convergence layer daemon: it can transmit bundles only to the node for which it is configured, so scheme configuration directives that cite this outduct need only provide the protocol name and the outduct name (the remote node number) as specified on the command line when ltpclo is started. ltpclo is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol, and it is terminated by bpadmin in response to an 'x' (STOP) command. ltpclo 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 ltpclo 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 the BRSC protocol. 1 ltpclo 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 the BRSC protocol. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: ltpclo can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such ltp duct. No LTP outduct with duct name matching remote_node_nbr has been added to the BP database. Use bpadmin to stop the LTP convergence- layer protocol, add the outduct, and then restart the LTP protocol. CLO task is already started for this duct. Redundant initiation of ltpclo. ltpclo can't initialize LTP. ltpadmin has not yet initialized LTP operations. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5), ltpadmin(1), ltprc(5), ltpcli(1) perl v5.14.2 2012-05-25 LTPCLO(1)