Purpose
Takes an online peer domain offline.
Syntax
stoprpdomain [-f]
[-h] [-TV] peer_domain
Description
The stoprpdomain command
takes all of the nodes that are currently online in the peer domain
offline. The peer domain definition is not removed from the nodes.
The
command must be run on a node that is online in the peer domain. If
the command is run on a node that is offline to the peer domain, no
action is performed.
If a Cluster-Aware AIX® (CAA) cluster is configured, no action is
performed because a peer domain operation in a CAA environment exists
and is online for the life of the CAA cluster.
The -f flag
must be used to override a subsystems rejection of the request to
take the peer domain offline. A subsystem may reject the request if
a peer domain resource is busy, such as in the case of a shared disk.
Specifying the -f flag in this situation
indicates to the subsystems that the peer domain must be brought offline
regardless of the resource state.
Flags
- -f
- Forces the subsystems to accept the stop request when it otherwise
would not.
- -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
- peer_domain
- Specifies the name of the online peer domain that is to be brought
offline.
Security
The user of the stoprpdomain command
needs write permission for the IBM.PeerDomain resource
class on each node that is defined to 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.
- 6
- The peer domain definition does not exist.
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 on
a node that is online in the peer domain.
Implementation Specifics
This command is
part of the rsct.basic.rte 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
In these examples,
nodeA is
one of the nodes defined and is online to
ApplDomain.
- To take ApplDomain offline, run this
command on nodeA:
stoprpdomain ApplDomain
- To take ApplDomain offline while making
sure the stop request will not be rejected by any subsystem, run this
command on nodeA:
stoprpdomain -f ApplDomain
Location
- /usr/sbin/rsct/bin/stoprpdomain