DESCRIPTIONstcpclo 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.
- 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.
- 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.
FILESNo configuration files are needed.
ENVIRONMENTNo environment variables apply.
DIAGNOSTICSThe 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.