rmrpdomain Command
Purpose
Removes a peer domain that has already been defined.
Syntax
rmrpdomain [-f] [-q] [-h] [-TV] peer_domain
Description
The rmrpdomain command removes the peer domain definition that is specified by the peer_domain parameter. The peer domain that is to be removed must already be defined. This command must be run on a node that is defined in the peer domain. When rmrpdomain is run on a node that is online to the peer domain, it removes the peer domain definition on all nodes defined to the peer domain that are reachable from that node. If a node defined to the peer domain is not reachable, that node's local peer domain definition is not removed. To remove the local peer domain definition when the peer domain is not online or when the node is not online to the peer domain, run the rmrpdomain command on that node and specify the -f flag.
The most efficient way to remove a peer domain definition is to make sure the peer domain is online. Then, from a node that is online to the peer domain, run the rmrpdomain command. If there are nodes that are not reachable from the node on which the rmrpdomain command was run, on each of those nodes, run the rmrpdomain command using the -f flag. This can be done at a later time if the node itself is not operational.
The -f flag must also be used to override a subsystem's rejection of the peer domain removal. A subsystem may reject the request if a peer domain resource is busy, for example. Specifying the -f flag in this situation indicates to the subsystems that the peer domain definition must be removed.
The rmrpdomain command does not require configuration quorum. Therefore, this command is still successful if it is issued to a minority subcluster. Later, the majority subcluster may become active. If so, the domain is still removed.
If a Cluster-Aware AIX® (CAA) cluster is configured and this peer domain is representing it, the rmrpdomain command removes the underlying CAA cluster as well.
Flags
- -f
- Forces the peer domain to be removed. The force flag is required
to remove a peer domain definition:
- from the local node when the node is not online to the peer domain.
- when a subsystem may reject the request, as when resources are allocated, for example.
- -q
- Specifies quiet mode. The command does not return an error if the peer domain does not exist.
- -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 defined peer domain that is to be removed.
Security
The user of the rmrpdomain command needs write permission to the IBM.PeerDomain resource class on each node that is to be 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
The node on which this command is run must be defined to the peer domain and should be able to reach all of the nodes that are defined to the peer domain. The node's local peer domain definition will not be removed if the node is not reachable.
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
- To remove the peer domain definition of ApplDomain where
nodeA, nodeB, and
nodeC are defined and online to ApplDomain, and
all are reachable to each other, run this command on nodeA,
nodeB, or nodeC:
rmrpdomain ApplDomain
- To remove the local peer domain definition of ApplDomain on
nodeD when nodeD is
not online to the peer domain, the peer domain is offline, or the
peer domain does not exist, run this command on nodeD:
rmrpdomain -f ApplDomain
- To remove the peer domain definition of ApplDomain where nodeA,
nodeB, and nodeC are
defined and online to ApplDomain, all are
reachable to each other, and to prevent a subsystem from rejecting
the request, run this command on nodeA, nodeB,
or nodeC:
rmrpdomain -f ApplDomain
Location
- /opt/rsct/bin/rmrpdomain
Files
The /etc/services file is modified.