NOTE: In teamed controller operation, maintaining the integrity of the controller state information requires that a minimum of two controllers in a team of three must be active at all times. The failure of all but one of the controllers places the entire team in a SUSPEND state, and the domain serviced by the team becomes unmanaged. (The remaining teamed controller does not operate in standalone mode.)
A controller may also transition to Suspended state because of healthy reasons. The following summarizes the controller states:
•Active: The controller is healthy and part of a cluster with quorum (At least two controllers in a team of three).
•Suspended: The controller is unhealthy or part of cluster with no quorum (at most one controller in a team of three).
•Unreachable: If the connection between two controllers is broken then they see each other as unreachable.
Considerations:
•A system never sees itself as unreachable. Unreachable is a state for the remote controllers.
•Health does not affect cluster quorum. If in a team of three controllers two are unhealthy, as long as there is a link between controllers the third one will be active. A controller transitions to suspended state if quorum is lost to protect data consistency.
7.8Error log for team configuration
Table 4 Error log for team configuration
Log message | Description |
|
|
Build version not consistent on all the systems. | Not all systems on the team have the same controller build |
| version. Update the team as needed to have the same build |
| version. |
|
|
Invalid configuration. | The team configuration JSON is not valid. |
|
|
Local member must be part of the team configuration. | If the members list from the JSON configuration does not |
| include the system where the team is being created (The |
| local system). |
|
|
Team size must be greater than zero. |
|
|
|
A team has already been created. | Teaming is already running on the system. |
|
|
Team could not be created on a quorum. | Team configuration has failed on a majority of systems. |
| e.g. a team of three systems has experienced failures on |
| two systems. |
|
|
Team could not be deleted on a quorum. | A team delete has failed on a quorum number of systems. |
|
|
Team not configured on this system. | An attempt has been made on a standalone controller to |
| disband a team. |
|
|
Programming team alias | |
|
|
Unprogramming team alias | |
|
|
Recovering from Partial Team Creation | In case the team is not successfully created in all controllers, |
| it is not possible to fix the failed controllers without |
| disbanding the team. To recover from this failure it is |
| recommended to delete the team, fix the problem in the |
| controllers where the create operation failed, and try again. |
|
|
Recovering from Partial Team Deletion | If the team is not successfully deleted in all controllers, the |
| failed controllers might go to suspended mode because |
| they might not have quorum – they won’t be able to connect |
|
|
86 Team configuration