...
| HTTP Error | errorCode | errorMessage | Details |
|---|---|---|---|
| 202 Accepted | 510 | No E2T Instance available. | The existing RAN can't associated with any available E2T Instance. When E2T will be identified, this RAN will be served. |
| 511 | No Routing Manager Available | Currently there is connectivity to the Routing Manager. E2M will try later. | |
| 400 Bad Request | 401 | corrupted json | Can't parse the payload of the body |
| 402 | validation error | E.G: Mandatory fields are missing or invalid (The value isn't according expected); | |
| 403 | Activity <activity name> rejected. RAN current state <state> does not allow its execution | E.G: Reset request is sent when state isn't Connected | |
| 404 | RAN already exist. | Add eNB to existing RAN | |
| 405 | command already in progress | E.G: 2 parallel Red Button were sent | |
404 Not Found | If the resource name doesn't exist (e.g.: nodec instead of nodeb) - the system returns HTTP Error 404 with "404 page not found" text. | ||
| 404 | resource not found | The classic 404 - Resource ID doesn't exist in the system | |
| 406 | No RAN in Connected State | e.g.: RAN Health Check and no one in Connected | |
| 415 Unsupported Media Type | 415 | Header validation error | In case there is a body and header application/json is missing - error. |
500 Internal Server Error | 500 | RNIB error | |
| 501 | Internal Server Error. Please try again later | ||
| 502 | RMR error | ||
| 503 Service Unavailable | 510 | No E2T Instance available. | The New RAN can't be added, please try later. |
| 511 | No Routing Manager Available | The New RAN can't be added, please try later. |
...