Download Configuration and Administration Guide

dtcpadmin -c config_file
Administering with the CLI
Makes the local node a database node. The
node needs to be inactive. The first node called
with this command reads the contents of the
file, configures, and starts SIS on the local
node. Additional nodes called with this
command option need a valid config_file to
prevent a syntax error; however, the configuration data are ignored and SIS is started on
the local node as a backup database node.
This command needs to be executed on at
least one node.
I To make SIS highly available, it is
25. November 2003 Stand 16:31.14
Pfad: C:\Documents and Settings\bhodgson\My Documents\working\Solaris and Linux\4.1A20\SIS41A20\no
changebars\SIS41A20.k06
Administration
strongly recommended that you have at
least one backup database node;
however, at times it may be more convenient to use the dtcpadmin -b
command since it does not require a
syntactically correct configuration file.
dtcpadmin -b node
Sets the given active node as a backup
database node. If no node name is given, it sets
the local node as the backup database node.
The node needs to be active. If the node is
already a backup database node, no changes
to the node are made.
Dokuschablonen (OECBook) V1.0
by S. Thums OEC MW SQ PS © Siemens Nixdorf Informationssysteme AG 1997
dtcpadmin -g gateway_node Changes the gateway node for the VIP address
vip_address
vip_address to the gateway node gateway_node.
dtcpadmin -f
Pauses SIS on all nodes (freeze).
When dtcpadmin -f is executed, all incoming
packets are ignored. This can lead to dropped
connections.
dtcpadmin -w
Resumes a paused SIS program (warm up).
dtcpadmin -n
Displays the SIS configuration of the local
node.
dtcpadmin -p
Displays the current SIS configuration in a
parsable format.
U42120-J-Z100-3-76
119