dtn2adminep(1) [debian man page]

DTN2ADMINEP(1)							  BP executables						    DTN2ADMINEP(1)

NAME

       dtn2adminep - administrative endpoint task for the "dtn" scheme

SYNOPSIS

       dtn2adminep

DESCRIPTION

       dtn2adminep is a background "daemon" task that receives and processes administrative bundles (all custody signals and, nominally, all
       bundle status reports) that are sent to the "dtn"-scheme administrative endpoint on the local ION node, if and only if such an endpoint was
       established by bpadmin.	It is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of Bundle
       Protocol on the local ION node, and it is terminated by bpadmin in response to an 'x' (STOP) command.  dtn2adminep can also be spawned and
       terminated in response to START and STOP commands that pertain specifically to the "dtn" scheme.

       dtn2adminep responds to custody signals as specified in the Bundle Protocol specification, RFC 5050.  It responds to bundle status reports
       by logging ASCII text messages describing the reported activity.

EXIT STATUS

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

       1   dtn2adminep was unable to attach to Bundle Protocol operations or was unable to load the "dtn" scheme database, probably because
	   bpadmin 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:

       dtn2adminep can't attach to BP.
	   bpadmin has not yet initialized BP operations.

       dtn2adminep can't load routing database.
	   dtn2admin has not yet initialized the "dtn" scheme.

       dtn2adminep can't get admin EID.
	   dtn2admin has not yet initialized the "dtn" scheme.

       dtn2adminep crashed.
	   An unrecoverable database error was encountered.  dtn2adminep terminates.

BUGS

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

SEE ALSO

       bpadmin(1), dtn2admin(1).

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

STCPCLO(1)							  BP executables							STCPCLO(1)

NAME

       stcpclo - DTN simple TCP convergence layer adapter output task

SYNOPSIS

       stcpclo remote_hostname[:remote_port_nbr]

DESCRIPTION

       stcpclo is a background "daemon" task that connects to a remote node's TCP socket at remote_hostname and remote_port_nbr.  It then begins
       extracting bundles from the queues of bundles ready for transmission via TCP to this remote bundle protocol agent and transmitting those
       bundles over the connected socket to that node.	Each transmitted bundle is preceded by a 32-bit integer in network byte order indicating
       the length of the bundle.

       If not specified, remote_port_nbr defaults to 4556.

       Note that stcpclo is not a "promiscuous" convergence layer daemon: it can transmit bundles only to the node to which it is connected, so
       scheme configuration directives that cite this outduct need only provide the protocol name and the outduct name as specified on the command
       line when stcpclo is started.

       stcpclo 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.  stcpclo can also be spawned and terminated in response to START and STOP
       commands that pertain specifically to the STCP convergence layer protocol.

EXIT STATUS

       0   stcpclo 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 STCP protocol.

       1   stcpclo 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 STCP 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:

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

       No such stcp duct.
	   No STCP outduct with duct name matching remote_hostname and remote_port_nbr has been added to the BP database.  Use bpadmin to stop the
	   STCP convergence-layer protocol, add the outduct, and then restart the STCP protocol.

       CLO task is already started for this duct.
	   Redundant initiation of stcpclo.

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

BUGS

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

SEE ALSO

       bpadmin(1), bprc(5), stcpcli(1)

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