R12.1 JA-2025July15
Error Code Definition
The following table outlines the error codes used for log standardization and troubleshooting purposes.
| # | Category | Error Code | Error Message | Root Cause/Description |
| 1 | Discovery Failure
| IAM-001-001 | Insufficient IAM Role Or Permissions | Required permission is missing. |
| 2 | AUTH-002-001 | Login And Get Token Failed | The client secret is expired. | |
| 3 | LICN-003-001 | Exceed The License Limit | The license is not enough. | |
| 4 | API-004-001 | Front Server is not configured | Front Server is not configured for API server. | |
| API-004-002 | Duplicate API servers exist | |||
| API-004-003 | Proxy Error / API Endpoint Cannot be Reached | |||
| API-004-004 | Front Server cannot reach the Microsoft Azure Server Endpoints | |||
| API-004-005 | Insufficient authentication scopes | |||
| 5 | Topo Issue
| NM-005-001 | Azure Node Is Missing | 1. IAM permission issue. 2. Code bug. 3. Azure API logic flow change. |
| 6 | IM-006-001 | Azure Interface Is Missing | 1. IAM permission issue. 2. Code bug. 3. Azure API logic flow change. | |
| 7 | Path Failure
| PF-007-001 | Python Error | 1. VRT/Path code bug. 2. New user case which is not supported yet. 3. Azure API format change. |
| 8 | NF-008-001 | Find Next Hop Failed | 1. VRT/Path code bug. 2. New user case which is not supported yet. 3. Azure API format change. | |
| 9 | Path Slowness | OM-009-001 | Lack of Out Interface In Route Table | Lack of out interface in VRT or Effective Route Table. |
| 10 | NCT Retrieve Failure | IAM-001-001 | Insufficient IAM Role Or Permissions | Missing permission required. |