HP VAN SDN Controller Administrator Guide v3
-ksSfL --request DELETE --url
https://<member-ip>:8443/sdn/v2.0/team
The resulting output includes the following:
{
"success": [
{"ip":"192.168.56.19"},
{"ip":"192.168.56.25"},
{"ip":"192.168.56.25"}]}
6.5 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 at least two controllers in the
team become active, team operation resumes, with one of the controllers operating as the team
leader.
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.)
6.6 Error Messages for Team Configuration
DescriptionMessage
Not all systems on the team have the same controller build
version. Update the team as needed to have the same build
version.
Build version not consistent on all the systems.
There has been a team configuration storage failure on a
persistence storage (hard disc).
Failed to cache team configuration.
Deletion of a team configuration from a persistent storage
device has failed.
Failed to delete the cached team configuration.
An attempt to read the team configuration from persistent
storage has failed.
Failed to read cache.
The team configuration JSON is not valid.Invalid team configuration. <Message>.
See Team Alias Note.Programming team alias < ip-address > failed
A team delete has failed on a quorum number of systems.Team delete failed, as delete failed on quorum number of
systems
Teaming is already running on the system.Teaming already configured on this system.
Teaming bootstrap is already running.Teaming bootstrap is in progress, cannot configure team.
An attempt has been made on a standalone controller to
disband a team.
Teaming not configured on this system.
Team leader election has been triggered while the teaming
service is still coming up.
TeamingService not found.
6.5 Controller Fault Tolerance 87