Initiate a rollback when there is a deployment failure.
Unwind the partial installation
or undeploy the failed EFA instance.
no efa deploy
Copy the EFA instance.
Restore EFA database.
efa system restore
Use the system backups available
/apps/efa_logs/backup/directory or copy the required backup files to the
extreme@tpvm1:~$ scp firstname.lastname@example.org:/home/user/EFA-3.1.0-GA-2022-10-20T07-08-43.921.tar /apps/efa_logs/backup/ The authenticity of host '10.20.48.170 (10.20.48.170)' can't be established. ECDSA key fingerprint is SHA256:rQYa5NjeFWtLvCCUzjELs+9jd/6E+hBeEeHIYdFBs2I. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.20.48.170' (ECDSA) to the list of known hosts. email@example.com's password: EFA-3.1.0-GA-2022-10-20T07-08-43.921.tar 100% 732KB 18.6MB/s 00:00 extreme@tpvm-71:~$
- Login as an 'extreme' user to the EFA system.
Restore the EFA configuration.
efa system restore -–backup-tar <file_name>
Post EFA rollback, if you see any devices in
cfg refresh errorstate when you run the efa fabric show command, run the efa inventory device update --ip <device_ip> command to correct it.