rmcctrl Command

Edit online

Purpose

Manages the resource monitoring and control (RMC) subsystem.

Syntax

rmcctrl { -a │ -A │ -b ││ -B ││ -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 started.

Note: While the RMC subsystem can be stopped and started by using the stopsrc and startsrc commands, you can use the rmcctrl command 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.
-b
Sets the idle timeout for the RMC API client session to n seconds. If the RMC daemon finds no activity in the session for the last n seconds, it is closed.
-B
Sets the idle timeout for the RMC API client session to a default value of 0 seconds (that is it is disabled).
-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 that is 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 by 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 by 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 can 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. This timeout value must include the following actions:
  • Receiving the first message of the start session protocol after the RMC subsystem accepts a client connection.
  • Receiving the complete client message by the RMC subsystem, after the initial message is received
If either of these time limits is exceeded, the client session is closed. The minimum acceptable value is 10; the maximum is 86400.

When specified, this value takes effect the next time the RMC subsystem is started.

-T
Sets the client message timeout to the default value of 10 seconds.

When specified, this value takes effect the next time the RMC subsystem is started.

-u n
Sets the start session timeout value to n seconds. Within this amount of time, the start session processing must complete for a new client session; otherwise, the session is closed. The minimum acceptable value is 60; the maximum is 86400.

When specified, this value takes effect the next time the RMC subsystem is started.

-U
Sets the start session timeout value to the default value of 300 seconds.

When specified, this value takes effect the next time the RMC subsystem is started.

-v n
Sets the first command timeout value to n seconds. If a first command timer is set when a client session is established with the RMC subsystem, the first command must arrive within the specified number of seconds after the start session processing completes; otherwise, the session is closed. The minimum acceptable value is 10; the maximum is 86400.

When specified, this value takes effect the next time the RMC subsystem is started.

-V
Sets the first command timeout value to the default value of 10 seconds.

When specified, this value takes effect the next time the RMC subsystem is started.

-w n
Sets the first command threshold value to n client sessions. Once the number of client sessions exceeds this value, the RMC subsystem enables a first command timer on each new, unauthenticated session. If the threshold is set to 0, the first command timeout function is disabled. The maximum value is 150.

When specified, this value takes effect the next time the RMC subsystem is started.

-W
Sets the first command threshold value to the default value of 150 client sessions.

When specified, this value takes effect the next time the RMC subsystem is started.

-x
Enables first command timeouts for non-root authenticated client sessions and for unauthenticated client sessions.

When specified, this value takes effect the next time the RMC subsystem is started.

-X
Disables first command timeouts for non-root authenticated sessions.

When specified, this value takes effect the next time the RMC subsystem is started.

-z
Stops the RMC subsystem and all resource managers, but the command does not return until the RMC subsystem and the resource managers are stopped.
-h
Writes the command's usage statement to standard output.

Security

Privilege control: only the root user must run (x) access to this command.

Exit Status

0
The command is successful.
1
The command was not successful.

Standard Output

When the -h flag is specified, this command's usage statement is written to standard output.

Examples

  1. To add the RMC subsystem, enter: 
    rmcctrl -a
  2. To start the RMC subsystem, enter: 
    rmcctrl -s
  3. To stop the RMC subsystem, enter: 
    rmcctrl -k
  4. To delete the RMC subsystem, enter: 
    rmcctrl -d

Location

/opt/rsct/bin/rmcctrl