Starts the topology services subsystem.
topsvcsctrl { -a | -s | -k | -d | -c | -u | -t | -o | -r | -h }
The topsvcsctrl control script controls the operation of the topology services subsystem. The subsystem is under the control of the system resource controller (SRC) and belongs to a subsystem group called topsvcs. This script is normally started by the HACMP/ES startup process.
An instance of the topology services subsystem runs on every node of a cluster.
From an operational point of view, the topology services subsystem group is organized as follows:
The topsvcs subsystem is associated with the hatsd daemon and the topsvcs script. The topsvcs script configures and starts the hatsd daemon. The subsystem name on the nodes is topsvcs. There is one of each subsystem per node and it is associated with the cluster to which the node belongs.
Provides the topology services. The topsvcs script configures and starts the hatsd daemon.
The topsvcsctrl script is not normally executed from the command line. It is normally called by the HACMP/ES startup command.
The topsvcsctrl script provides a variety of controls for operating the topology services subsystems:
Before performing any of these functions, the script obtains the current cluster name (using the cllsclstr command) and the node number (using the clhandle command). If the node number is 0, the control script is running on the control workstation.
Except for the clean and unconfigure functions, all functions are performed within the scope of the current system partition.
Adding the subsystem: When the -a flag is specified, the control script uses the mkssys command to add the topology services subsystem to the SRC. The control script operates as follows:
Starting the subsystem: When the -s flag is specified, the control script uses the startsrc command to start the topology services subsystem, topsvcs.
Stopping the subsystem: When the -k flag is specified, the control script uses the stopsrc command to stop the topology services subsystem, topsvcs.
Deleting the subsystem: When the -d flag is specified, the control script uses the rmssys command to remove the topology services subsystem from the SRC. The control script operates as follows:
Cleaning up the subsystems: When the -c flag is specified, the control script stops and removes the topology services subsystems for all clusters partitions from the SRC. The control script operates as follows:
Turning tracing on: When the -t flag is specified, the control script turns tracing on for the hatsd daemon, using the traceson command.
Turning tracing off: When the -o flag is specified, the control script turns tracing off (returns it to its default level) for the hatsd daemon, using the tracesoff command.
Refreshing the subsystem: When the -r flag is specified, the control script refreshes the subsystem, using the topsvcs refresh command and the refresh command. It rebuilds the information about the node and adapter configuration in the global object data manager (ODM) and signals the daemon to read the rebuilt information.
Logging: While it is running, the topology services daemon (hatsd) provides information about its operation and errors by writing entries in a log file called /var/ha/log/topsvcs.cluster_name.
You must be running with an effective user ID of root to use this script.
This command is valid in an HACMP environment only.
Use this command only under the direction of the IBM Support Center.
When the -h flag is specified, this command's usage statement is written to standard output. All verbose messages are written to standard output.
This script writes error messages (as necessary) to standard error.
topsvcsctrl -a
topsvcsctrl -s
topsvcsctrl -k
topsvcsctrl -d
topsvcsctrl -c
topsvcsctrl -t
topsvcsctrl -o
Commands: lssrc, startsrc, stopsrc
Scripts: topsvcs