HP HPE VAN SDN Controller 2.7 Administrator's Manual page 139

"https://controller_ip:8443/sdn/v2.0/auth"
-H "Content-Type: application/json" --data-binary '{"login": {"domain": "domain","user": "user","password":
"password"}}'
CAUTION: Credential information (user name, password, domain, and authentication
tokens) used in curl commands might be saved in the command history. For security reasons,
Hewlett Packard Enterprise recommends that you disable command history prior to executing
commands containing credential information.
5. Acquire the controller uid:
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token"
--fail -ksSfL --request GET
--url "https://controller_ip:8443/sdn/v2.0/systems"
6. Use the following curl command to set the IP address:
curl --noproxy controller_ip --header "X-Auth-Token:auth_token"
--fail -ksSfL --request PUT
"https://controller_ip:8443/sdn/v2.0/systems/controller_uid"
--data-binary '{"system":{"ip":"controller_ip"}}'
7. Perform a single controller restore onto each controller needing restoration.
a. Upload the backup files that will be restored:
curl --noproxy controller_ip -X POST --fail -ksSfL
--url "https://controller_ip:8443/sdn/v2.0/restore/backup"
-H "X-Auth-Token:auth_token" --data-binary @path-and-file-name.zip"
where path-and-file-name is the full path to the file and the filename. The filename
MUST match the name you used during the backup.
b. Initiate the restore:
curl --noproxy controller_ip --header "X-Auth-Token:auth_token"
--fail -ksS --request POST --url
"https://controller_ip:8443/sdn/v2.0/restore"
8. For a controller team, wait for HA synchronization to complete to all the controllers and wait
for the team to become connected. The team can take a few minutes to come back up. Be
sure to verify that team status has all controllers as active and one of the team members is
a leader.
curl --noproxy controller_ip
--header "X-Auth-Token:auth_token" --fail -ksSfL --request GET
--url "https://controller_ip:8443/sdn/v2.0/systems"
If less than a quorum of controllers are restored, then those controllers are updated to
the latest state of the running team via HA synchronization. (A quorum is n/2+1 where
n is the total number of controllers in a team. In a three-controller team, a quorum is
two controllers.)
If the entire team is restored, then each controller is reset to the previous backed-up
state.
9. After the controller restore is complete, change the value of CTL_RESTORE_INSTALL_MODE
to false in the ~/.sdn_install_options file on each controller so that it does not
impact a future installation. This is because a future installation of the controller might not
involve starting in recovery mode. (This is the opposite of step 2 of
from a backup " (page
10. It is possible to query the restore status by using the get command at v2.0/restore/
status. Since the restore is not hitless, the REST query will fail until the controller has
successfully restarted.
137).)
"Restoring a controller
Restoring a controller from a backup 139