Search

Rollback EFA

Initiate a rollback when there is a deployment failure.

Procedure

  1. Unwind the partial installation or undeploy the failed EFA instance. 
    no efa deploy
  2. Copy the EFA instance. 
    efa deploy
  3. Restore EFA database. 
    efa system restore
  4. Use the system backups available in the /apps/efa_logs/backup/ directory or copy the required backup files to the /apps/efa_logs/backup/ directory. 
    extreme@tpvm1:~$ scp root@10.20.48.170:/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.
root@10.20.48.170's password:
EFA-3.1.0-GA-2022-10-20T07-08-43.921.tar                                      100%  732KB  18.6MB/s   00:00
extreme@tpvm-71:~$
  5. Login as an 'extreme' user to the EFA system.
  6. Restore the EFA configuration. 
    efa system restore -–backup-tar <file_name>
  7. Post EFA rollback, if you see any devices in cfg refresh error state when you run the efa fabric show command, run the efa inventory device update --ip <device_ip> command to correct it.
9037627-00 Rev AA