The basic layout of the topology table is shown in the following table. However, when the GUI actually draws the topology table, it puts check boxes next to all of the interconnects and CF devices as shown in the following table.
FUJI | Full interconnects | Partial interconnects | Unconnected devices | ||
|---|---|---|---|---|---|
Int 1 | Int 2 | Int 3 | Int 4 | ||
fuji2 | eth0 eth2 | eth1 | eth3 | eth5 | eth4 eth6 |
fuji3 | eth0 | eth2 | missing | eth1 | |
fuji4 | eth1 | eth2 | eth3 | missing | eth4 |
The check boxes show which of the devices were selected for use in the CF configuration. (In the actual topology table, check marks appear instead of x's.)
When the topology table is used outside of the CF Wizard, these check boxes are read-only. They show what devices were previously selected for the configuration. In addition, the unchecked boxes (representing devices which were not configured for CF) will not be seen for nodes where -L was used to load CF.
When the topology table is used within the CF Wizard, then the check boxes may be used to select which devices will be included in the CF configuration. Clicking on the check box in an Int number heading will automatically select all devices attached to that interconnect. However, if a node has multiple devices connected to a single interconnect, then only one of the devices will be selected.
For example, in Table 5, fuji2 has both eth0 and eth2 attached to Interconnect 1. A valid CF configuration allows a given node to have only one CF device configured per interconnect. Thus, in the CF Wizard, the topology table will only allow eth0 or eth2 to be selected for fuji2. In the above example, if eth2 were selected for fuji2, then eth0 would automatically be unchecked.
If the CF Wizard is used to add a new node to an existing cluster, then the devices already configured in the running cluster will be displayed as read-only in the topology table. These existing devices may not be changed without unconfiguring CF on their respective nodes.
For how to delete the CF configuration, see "4.12 Unconfigure CF."
