2.
Using the token acquired in Step 1, view the team configuration as follows:
curl --noproxy team-ip --header "X-Auth-Token:auth_token" --fail -ksSfL --request GET --url
https://team-ip:8443/sdn/v2.0/team
Example command
curl --noproxy 192.0.2.100
--header "X-Auth-Token:<auth_token>"
--fail -ksSfL --request GET
--url https://192.0.2.100:8443/sdn/v2.0/team
Example response
{
"team": {
"ip": "192.0.2.100",
"revision":0
"members": [
{
"ip": "192.0.2.119"
},
{
"ip": "192.0.2.125"
},
{
"ip": "192.0.2.127"
}
]
}
}
Creating regions using curl
To support High Availability (HA) for controllers to OpenFlow switches, create region configurations
in the controllers using the REST APIs provided by the Device Owner Service.
A region groups devices together with their controllers. Every region has a unique identifier (UID)
assigned upon creation. Some REST commands will require that UID to manage the region. A
region must have three controllers which must be specified in priority order for all devices within
the region (master, primary slave, secondary slave). Devices in a region can be expressed as a
list of individual IPv4 addresses, a list of IPv4 ranges, or a combination of both.
The Device Owner Service provides high availability between devices and controllers and ensures
the availability of a controller to the devices. The Device Owner Service also provides a measure
of security; only devices explicitly included in a region can connect to the region’s controllers;
thus if no regions are defined for the teamed controllers, then no devices will be able to connect
to the controllers.
Putting the region configurations in place for a controller team ensures seamless failover and
failback among the configured controllers for the specified network devices in a region. That is,
when a controller experiences a fault, the Device Owner Service ensures that a slave controller
immediately assumes the master role over the group of network devices for which the failed
controller was master. Once the failed controller recovers and rejoins the team, the Device Owner
Service ensures restoration of this controller’s role; that is, the rejoining controller takes back the
role for which it was configured with respect to the other network devices. If the controller was
configured to operate as the master in a region, then it would be restored to the master role. If
it was configured to operate in the slave role, it would resume operation in the slave role.
Once the region definition(s) are in place, the Device Owner Service ensures that a master
controller is always available to the respective network element(s) even if the configured master
fails or there is a disruption of the communication channel between the controller and the network
device(s).
188
curl commands