rmcctrl Command

Purpose

Manages the resource monitoring and control (RMC) subsystem.

Syntax

rmcctrl { -a │ -A │ -d │ -k │ -K │ -m {R │ E │ D} │ -M {R │ E │ D} │ -p │ -P │ -q │ -Q │ -s │ -t n │ -T │ -u n │ -U │ -v n │ -V │ -w n │ -W │ -x │ -X │ -z │ -h }

Description

The rmcctrl command controls the operation of the resource monitoring and control (RMC) subsystem. The subsystem is under the control of the system resource controller (SRC) with a subsystem name of ctrmc and a subsystem group name of rsct. The RMC subsystem definition is added to the subsystem object class and then started when Reliable Scalable Cluster Technology (RSCT) is installed. In addition, an entry is made in the /etc/inittab file so that the RMC subsystem is started automatically when the system is booted up.

Note: While the RMC subsystem can be stopped and started by using the stopsrc and startsrc commands, it is recommended that the rmcctrl command be used to perform these functions.

Flags

-a

Adds the RMC subsystem to the subsystem object class and places an entry at the end of the /etc/inittab file.

-A

Adds and starts the RMC subsystem.

-d

Deletes the RMC subsystem from the subsystem object class and removes the RMC entry from the /etc/inittab file.

-k

Stops the RMC subsystem.

-K

Stops the RMC subsystem and all resource managers.

-m

Specifies the RMC subsystem client message policy. This policy applies to messages sent between the RMC subsystem and any command listed in the RSCT: Technical Reference, when the command is run on a different node than the RMC subsystem (in other words, the CT_CONTACT environment variable is set). These messages are sent using TCP/IP.

This flag is supported on RSCT version 2.3.1.0 or later. The "Enabled" policy must be used if the commands are from an earlier version of RSCT.

R: Indicates that the client message policy is "Required". "Required" means that the connection remains open only if message authentication can (and will) be used.
E: Indicates that the client message policy is "Enabled". "Enabled" is the default; message authentication is used if both sides of the connection support it.
D: Indicates that the client message policy is "Disabled". "Disabled" means that message authentication is not used.

-M

Specifies the RMC subsystem daemon message policy. This policy applies to messages sent between the RMC subsystem daemons within a management domain cluster. These messages are sent using the User Datagram Protocol (UDP).

This flag is supported on RSCT release 2.4.1.0 or later. When specified, the indicated message policy takes effect the next time the RMC subsystem is started.

R: Indicates that the daemon message policy is "Required". "Required" means that two daemons communicate only if message authentication can (and will) be used.
E: Indicates that the daemon message policy is "Enabled". "Enabled" is the default; message authentication is used if the sending and receiving daemons support it.
D: Indicates that the daemon message policy is "Disabled". "Disabled" means that message authentication is not used. Disabling message authentication may result in the loss of function if all of the nodes in the cluster are not configured the same.

-p

Enables remote client connections.

-P

Disables remote client connections.

-q

Enables remote client connections the next time the RMC subsystem is started.

-Q

Disables remote client connections the next time the RMC subsystem is started.

-s

Starts the RMC subsystem.

-t n

Sets the client message timeout value to n seconds. Within this amount of time:

The first message of the start session protocol must arrive after the RMC subsystem accepts a client connection
Any complete client message must be received by the RMC subsystem, once the beginning of the message has been received

If either of these time limits is exceeded, the client session is closed. The minimum acceptable value is 10; the maximum is 86400.