The Find All Systems step enables PUT to determine how many systems are selected and which nodes belong in each system. Several PUT operations allow multiple systems to be selected. Since many of the steps that PUT performs are done at the system level, it is important that the correct nodes are handled together. For example, rebooting a system requires that PUT reboot only the nodes in that system. Operations that do not allow multiple systems to be selected enforce that restriction outside of the Find All Systems step. For example, the Configure Teradata Vantage operation never allows multiple systems to be selected.
Node Grouping Rules
Nodes are grouped together into systems by matching or grouping information returned to the plugin by the FindSystemsJob. The exact information returned by the job depends on node type (for example, TPA, Hadoop, BAR). Every node that returns the exact same grouping information is placed in the same system. The following table lists the currently supported methods for grouping nodes into systems.
| Grouping Rule | Description |
|---|---|
| Byn0 connectivity (default) | The default method for grouping nodes into systems. Any node type that is NOT handled by any of the other grouping rules falls into this category. Bynet subnet 0 connectivity means that all nodes that see each other on the same byn0 subnet are grouped into the same system. All Teradata TPA nodes and any TMS node that has Teradata installed are grouped using this rule. |
| Hadoop configuration information | Hadoop nodes use configuration information provided by the hcli command to group nodes together. The FindSystemsJob runs the hcli command and returns the output to the plugin. All Hadoop nodes with the same configuration information are grouped together into the same system. |
| Unknown node type | All nodes for which PUT cannot determine a node type are assigned a node type of unknown. All unknown nodes are always grouped together into a single system. |
| BAR/DSA | All BAR, DSADSC, and DSAMS nodes are grouped together into a single system. This grouping is done based on node type only. Multiple BAR/DSA systems cannot reside on the same network subnet.
|
| Single node system type | Any node type that is a single node system is placed into its own system. Currently the Aster Backup Manager node type is the only node type handled this way. |
System Information Summary Screen
The following information is displayed by the Find All Systems step. This example is from the Install Upgrade Software operation with three different systems selected.
| System-Level Information | Description |
|---|---|
| System (ID) | Each system is assigned a unique system ID Number beginning with a zero. |
| System Name | When every node in a system reports the same system name, that name is displayed in this field. When a common name is not found across all nodes, the default system name format, System#, is used, where # represents the system ID. |
| Node-Specific Information | Description |
|---|---|
| Node Name | The node name on the selected subnet or IP address if a name cannot be resolved. |
| PMAID | A system wide unique identifier for a node. |
| IP Address | The IP address on a selected subnet. |
| Node Types | One or more node types describing what the node is or does. |
System Information Warning Screen
The System Information Warning screen appears when warning conditions are detected, regardless of which mode (typical or custom) is selected. Warning messages appear on screen following the system-level information.
In this example, the user selected only one of the two nodes in system 0. The warning message indicates that the selection of two nodes was expected for that system. Because all nodes in a system are typically upgraded at the same time, the selection of only one of two nodes triggered a warning condition.
