| 1–99 |
Normal state or upgrade is in progress. |
No action needed. |
N/A |
| 100,102 |
Upgrade failed. |
|
Contact Support (Cisco TAC). |
| 101 |
Secure Access will automatically attempt the upgrade again. |
Monitor to ensure successful retry. |
Contact Support (Cisco TAC). |
| 200 |
Docker login authentication failure. Check docker login credentials for container. |
For VM, monitor to ensure successful retry. |
Contact Support (Cisco TAC) to provide guidance when setting up the Docker account. |
| 201–204 |
Secure Access will automatically attempt the upgrade again. |
Monitor to ensure successful retry. |
Contact Support (Cisco TAC). |
| 204 |
Issue may be self-repairing. |
Monitor to ensure successful upgrade. |
Contact Support (Cisco TAC). |
| 206 |
Upgrade failed. |
Check for full disk. |
Contact Support (Cisco TAC). |
| 207,208 |
Upgrade failed. |
To get more information, run the techsupport diagnostic command. |
Contact Support (Cisco TAC). |
| 210 |
Upgrade failed. |
Secure Access will automatically attempt the upgrade again. Check for disk issue. Monitor to ensure successful retry. |
Contact Support (Cisco TAC). |
| 211 |
Secure Access will automatically attempt the upgrade again. |
Monitor to ensure successful retry. |
Contact Support (Cisco TAC). |
| 217 |
Docker hub download failed due to rate limiting. |
Authenticate with docker, using docker login. |
Contact Support (Cisco TAC) to provide guidance when setting up the Docker account. |
| 219 |
Host does not have sufficient disk space. |
Free up at least 2G of disk space in host to ensure this auto recovers. |
Contact Support (Cisco TAC). |
