Command example
curl --noproxy 192.0.2.119 -X POST --fail -ksSfL
--url "https://192.0.2.119:8443/sdn/v2.0/auth"
-H "Content-Type: application/json"
--data-binary '{"login": {"domain": "sdn","user": "myname","password": "mypass"}}'
Command response
{"record":{"token":"10f728e477cb4612b07069f339d0ca29","expiration":
1381119301000,"expirationDate":2013-12-06 21-15-01-0700",
"userId":"51802e12d16345fe9a4389290c1a04e2","username":"sdn","domainId":
"d45eca9bde1b4dc78bd7dff69ee9440d","domainName":"sdn"}}
2.
Configure the controller team by using the team values and token from step 1:
curl -m 240 --noproxy 192.0.2.119 --header X-Auth-Token:
10f728e477cb4612b07069f339d0ca29 --fail -ksS --request POST
--url https://192.0.2.119:8443/sdn/v2.0/team
--data-binary '{"team":{"ip":"192.0.2.100","members":
[{"ip":"192.0.2.119"},
{"ip":"192.0.2.125"},
{"ip":"192.0.2.127"}]}}'
Since team creation is asynchronous, the response is always 202 unless the team configuration
(JSON) is not valid or there is a problem configuring the local controller. Possible codes are:
202 Accepted
400 Bad request
401 Unauthorized
503 Service unavailable
In case the team is not created in a quorum or if the team is partially created, an alert is posted.
Example of an alert for a team partially created
Team partially created: [Successes: 192.168.1.1, 192.168.1.2], [Failures: 192.168.1.3]
The alert does not include the error description, however, the error description is added to the
log files. Review the log files to get the cause of the partial team creation.
Example of an alert for a team creation that failed in a quorum
Team could not be created on a quorum
If a team cannot be created in a quorum, delete the team and create it again.
Error log for team configuration
Table 5 Error log for team configuration
Description
Log message
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.
The team configuration JSON is not valid.
Invalid configuration.
If the members list from the JSON configuration does not
include the system where the team is being created (The
local system).
Local member must be part of the team configuration.
HPE VAN SDN Controller 2.5 only supports a team of 3
controllers.
Team size must be greater than zero.
Teaming is already running on the system.
A team has already been created.
Team configuration has failed on a majority of systems.
For example, a team of three systems has experienced
failures on two systems.
Team could not be created on a quorum.
A team delete has failed on a quorum number of systems.
Team could not be deleted on a quorum.
184
curl commands