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 ip-address failed. | See “Team alias node”. |
Unprogramming team alias ip-address failed. | See “Team alias node”. |
| 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 to those controllers where the operation was a success. To recover from this failure it is recommended to delete the team on each failed controller so configuration files are removed and so the controllers transition to standalone mode. |
Success log
| Message | Description |
|---|---|
| Team created. | |
| Team created with the following configuration: [Team IP: <team ip>, [Members<member list>]. | |
| Team disbanded. | |
| Programmed Team alias: <team ip>. | |
| Unprogrammed Team alias: <team ip>. |
Team IP error log
| Message | Description |
|---|---|
| Exception while checking alias: <team ip>, <exception> | |
| Team alias: <team ip> already programmed | |
| Exception while programing alias: <team ip>, <exception> | |
| Exception while unprograming alias: <team ip>, <exception> |
An IP Address (North-Bound IP) alias is created on the node that is elected as team leader to allow a controller team to be accessible with a single IP Address no matter which controller is the leader. This IP Address is provided as part of the team configuration when creating a team. If the elected node stops being team leader, the team IP Address must be removed from the aliases because this address must be reassigned to the actual team leader. If assigning or removing an alias fails, one of the following messages appears in the Alert log:
In either of these instances, the condition is logged and the team continues to operate. In this case you can manually program the team alias using the following commands: