HP HPE VAN SDN Controller 2.7 - Failback Behavior Within a Region

"dataPaths":[
{
"dpid":"00:1e:00:9c:02:e0:e4:00",
"owningControllerIp":"172.17.6.71"
}
]
}
]
}
]
}
Failback behavior within a region
When the configured master recovers from a failure and rejoins the team, or when the connection
from the disconnected device(s) with the original master is resumed, Device Owner Service
initiates a failback operation in which the master role is restored to the configured master as
defined in the region definition.
In this example, the configured master controller 172.17.6.70 recovers from failure and is
active again. The controller 172.17.6.71 returns back to being a primary slave and all 5
devices 192.168.1.101–105 belong to the configured master controller 172.17.6.70.
Example command
curl --noproxy teamIp --header "X-Auth-Token:token" -ksS --request GET --url
https://teamIp>:8443/sdn/v2.0/owners/region-uid/state?dataPathDetails=yes
Example output
{
"regions":[
{
"uid":"713def9a-4f96-485f-990c-8924bc06c8d8",
"name":"Region-Red",
"prioritizedControllerIps":[
"172.17.6.70",
"172.17.6.71",
"172.17.6.72"
],
"devices":[
{
"deviceIp":"192.168.1.101",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:01:44:31:92:5c:af:86",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.102",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:1e:c8:cb:b8:dd:f0:c0",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.103",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
Team configuration using curl commands 191