startrpnode Command

Purpose

Brings one or more nodes online to a peer domain.

Syntax

startrpnode [-h] [-TV] node_name1 [node_name2 ...]

startrpnode -f │ -F { file_name │ "–" } [-h] [-TV]

Description

The startrpnode command brings one or more offline nodes online to a peer domain. The peer domain is determined by the online peer domain where the command is run. The command must be run from a node that is online to the desired peer domain.

The node that is being brought online must have already been defined to be in this peer domain using the addrpnode command or the mkrpdomain command. The node must not be online to any other peer domain.

Flags

-f | -F { file_name | "–" }

Reads a list of node names from file_name. Each line of the file is scanned for one node name. The pound sign (#) indicates that the remainder of the line (or the entire line if the # is in column 1) is a comment.

Use -f "-" or -F "-" to specify STDIN as the input file.

-h

Writes the command's usage statement to standard output.

-T

Writes the command's trace messages to standard error. For your software service organization's use only.

-V

Writes the command's verbose messages to standard output.

Parameters

node_name1 [node_name2 ...]

Specifies the peer domain node names of the nodes to be brought online to the peer domain. You can bring one or more nodes online using the startrpnode command. You must specify the node names in exactly the same format as they were specified with the addrpnode command or the mkrpdomain command. To list the peer domain node names, run the lsrpnode command.

Security

The user of the startrpnode command needs write permission for the IBM.PeerNode resource class on each node that is to be started in the peer domain. By default, root on any node in the peer domain has read and write access to this resource class through the configuration resource manager.

Exit Status

0

The command ran successfully.

1

An error occurred with RMC.

2

An error occurred with a command-line interface script.

3

An incorrect flag was entered on the command line.

4

An incorrect parameter was entered on the command line.

5

An error occurred that was based on incorrect command-line input.

Environment Variables

CT_CONTACT

Determines the system where the session with the resource monitoring and control (RMC) daemon occurs. When CT_CONTACT is set to a host name or IP address, the command contacts the RMC daemon on the specified host. If CT_CONTACT is not set, the command contacts the RMC daemon on the local system where the command is being run. The target of the RMC daemon session and the management scope determine the resource classes or resources that are processed.

CT_IP_AUTHENT

When the CT_IP_AUTHENT environment variable exists, the RMC daemon uses IP-based network authentication to contact the RMC daemon on the system that is specified by the IP address to which the CT_CONTACT environment variable is set. CT_IP_AUTHENT only has meaning if CT_CONTACT is set to an IP address; it does not rely on the domain name system (DNS) service.

Restrictions

This command must be run from a node that is online to the peer domain. The node that is to be brought online must be offline to the peer domain, must not be online to any other peer domain, and must be reachable from where the command is run.

Implementation Specifics

This command is part of the Reliable Scalable Cluster Technology (RSCT) fileset for AIX®.

Standard Input

When the -f "-" or -F "-" flag is specified, this command reads one or more node names from standard input.

Standard Output

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

Standard Error

All trace messages are written to standard error.

Examples

startrpnode nodeB

Location

/usr/sbin/rsct/bin/startrpnode