Possible responses
Since team deletion is asynchronous, the response is always 202 unless there is a problem configuring the local controller as standalone. Possible codes:
202Accepted
400Bad request
401Unauthorized
503Service unavailable
In case the team is not deleted in a quorum or if the team is partially deleted an alert will be posted.
Example of the alert description for team partially deleted
"Team partially deleted: [Successes: 192.168.1.1, 192.168.1.2], [Failures: 192.168.1.3]"
The error for failures is not part of the alert, however an entry to the log files will be added with such errors.
Example of the alert description for team deletion failed in a quorum
"Team could not be deleted on a quorum"
To fix the controllers where the delete operation failed, the user will have to execute the delete operation again on the failed controllers.
7.7 Controller fault tolerance
The threshold for controller fault tolerance is 2n+1, where n is the number of failed controllers allowed in an active team. HP VAN SDN Controller teaming supports a team of three controllers. In a team of three controllers, n = 1; one controller in a team of three can fail without suspending team operation. If one such controller does go down, a stateful failover occurs, in which the remaining two members resume together from the point of failure, and the team continues to operate. As long as any two of the teamed controllers in the network are active, the network remains in a managed state. If a second controller in the team fails, then n exceeds the maximum allowed, and the remaining controller transitions to a SUSPEND state. When a controller is suspended because it is in the minority, it will return a 503 error to any REST API calls. When at least two controllers in the team become active, a new team manager is elected and the team operation resumes.
7.7 Controller fault tolerance | 85 |