Understanding the node list facility
The node list facility can be used to invoke mmpmon on multiple nodes and gather data from other nodes in the cluster. The following table describes the nlist requests for the mmpmon command.
| Request | Description |
|---|---|
| nlist add name[ name...] | Add node names to a list of nodes for mmpmon processing |
| nlist del | Delete a node list |
| nlist new name[ name...] | Create a new node list |
| nlist s | Show the contents of the current node list |
| nlist sub name[ name...] | Delete node names from a list of nodes for mmpmon processing |
When specifying node names, keep these points in mind:
- A node name of '.' (dot) indicates the current node.
- A node name of '*' (asterisk) indicates all currently connected local cluster nodes.
- The nodes named in the node list must belong to the local cluster. Nodes in remote clusters are not supported.
- A node list can contain nodes that are currently down. When an inactive node comes up, mmpmon will attempt to gather data from it.
- If a node list contains an incorrect or unrecognized node name, all other entries in the list are processed. Suitable messages are issued for an incorrect node name.
- When mmpmon gathers responses from the nodes in a node list, the full response from one node is presented before the next node. Data is not interleaved. There is no guarantee of the order of node responses.
- The node that issues the mmpmon command need not appear in the node list. The case of this node serving only as a collection point for data from other nodes is a valid configuration.