D Error Code Dictionary
Table D-1 Error Code Dictionary for BSF Management
| Application Error ID | Reason | Cause | Action |
|---|---|---|---|
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-01-400-00005-NA-02 | The GET request to BSF failed with a 400 status code and cause MANDATORY_QUERY_PARAM_INCORRECT. | The error appears whenever the Binding Request Query contains multiple UE Addresses (for example, a MAC-48 Address and an IPv4 Address), or the mandatory query parameters have an incorrect format. | Check the error details. Based on the error details, Verify that only either UE Address type IPV4 address, or IPv6 Prefix, or MAC-48 Address is sent. Ensure that each mandatory parameter is present and formatted correctly. Correct any errors and resend the request. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-01-400-00006-NA-02 | The GET request to BSF failed with a 400 status code and cause OPTIONAL_QUERY_PARAM_INCORRECT. | The error appears whenever the Binding Request optional query parameters has an incorrect format or value. | Check the error details. Based on the error details, review the optional query parameters (such as DNN and SNSSAI) for correct format. Update any values that do not comply before resubmitting the discovery request. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-01-400-00007-NA-02 | The GET request to BSF failed with a 400 status code and cause MANDATORY_QUERY_PARAM_MISSING. |
The error appears whenever the Binding Request Query does not contain a mandatory parameter. Mandatory parameters are the following:
|
Verify that all mandatory parameters are included in the Binding Request: ensure the UE Address is specified, and at least one valid identifier (IPv4 Address, IPv6 Prefix, or MAC-48 Address) is provided. |
| EC-OBSF-BSF_MGMT-INTRNL-EI-05-02-500-00000-01-02 | The POST request to BSF failed with a 500 status code and cause INTERNAL_SERVER_ERROR. | The error appears whenever an internal error occurs on BSF Management Service while trying to register. | Retry the request. If the error persists, collect logs and contact your system administrator or Oracle Support for further assistance. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00003-01-02 | The POST request to BSF failed with a 400 status code and cause INVALID_MSG_FORMAT. | The error appears whenever the Binding Data from the Binding Request contains multiple UE Addresses (For example, a MAC-48 Address and an IPv4 Address and/or IPV6 prefic), or the IP Address is missing its IPv4 Address or IPV6 Prefix or ipDomain is present without IPV4 Address | Ensure that the Binding Data includes only one type of UE Address per request (either MAC-48 Address or IP Address, not both), and if using IP Address, the IPv4 Address or IPV6 prefix must be specified. Ensure IPDomain is present only when IPV4 address is available. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00008-01-02 | The POST register request to BSF failed with a 400 status code and cause MANDATORY_IE_INCORRECT. | The error appears whenever a mandatory IE in the Binding Data from the Binding Request has an incorrect format. | Check all mandatory fields (IPv4, IPv6, MAC-48, SNSSAI, DNN) in the request for correct formatting and valid values. Correct any invalid entries and retry the request. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00009-01-02 |
The POST request to BSF failed with a 400 status code and cause OPTIONAL_IE_INCORRECT |
The error appears whenever the Binding Request optional query parameters has an incorrect format or value. | Review all optional fields (SUPI, GPSI, PCF FQDN, PCF Diameter Realm) for correct format according to the specified patterns defined in the cause column. Update any invalid values and resubmit the request. |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00010-01-02 | The POST register request to BSF failed with a 400 status code and cause MANDATORY_IE_MISSING. |
The error appears whenever a mandatory IE is missing in the Binding Data from the Binding Request. Mandatory IE are the following:
|
Verify that all required mandatory Information Elements (IE) are present in the request:
Add any missing values and resend the request. |
| EC-OBSF-BSF_MGMT-INTRNL-EI-05-04-500-00056-01-02 | The DELETE deregister request to BSF failed with a 500 status code and cause INTERNAL_SERVER_ERROR | The error appears whenever an internal error occurs on BSF Management Service while trying to deregister. | Retry the deregister request. If the issue continues, gather logs and escalate to your system administrator or Oracle Support. |
| EC-OBSF-BSF_MGMT-SIG-EI-05-04-404-00060-01-02 | The DELETE deregister request to BSF failed with a 404 and cause NOT_FOUND | The error appears whenever there is no resource to delete with the provided bindingID. | Validate that the bindingID that is trying to be deleted is in fact correct, and retry. If the 404 is still obtained, it means that the resource is no longer there and no further action is needed. |
Table D-2 Error Code Dictionary for Ingress Gateway
| Application Error Code ID | Reason | Cause | Action |
|---|---|---|---|
| OBSF-IGW-E002 |
REQUEST_TIMEOUT This error code indicates that request processing takes more time than the configured request timeout at ingress-gateway. |
A successful TCP connection was established but no response was received within the expected time frame. | To resolve this issue, consider increasing the request timeout setting on the ingress gateway or optimizing the backend services to handle the request faster. |
| OBSF-IGW-E054 |
INTERNAL_ERROR This error code indicates that some unknown internal error occurred in ingress-gateway while processing the request. |
Internal Errors, occur when there's an issue with improper configurations, mismatch in helm charts and versions. | Identify the cause from the error message sent back in the response and refer to the documentation for the specific feature that is being used and re verify all the configurations. Helm Charts and respective versions can also be checked |
| OBSF-IGW-E102 |
LATE_ARRIVAL_EXCEPTION This error code indicates that late arrival exception occurred at ingress-gateway as the request has already expired as part of SbiTimer feature. |
Timezone mismatch (or) 12H/24H time format mismatch leading to some time in the past in SBI Timer Header for SBI Timer Feature (or) Header of MaxRspTime might have been configured with the wrong value (or) the calculated request timeout value based on SBI Timer Headers is less than the configured requiredTime value at route level | Make sure the timestamp and max response time attached in the header, are of the correct time with respect to the time zone and not a time in the past. Verify if the requiredTime is accommodating to the calculated timeout value from SBI Timer Header values. |
| OBSF-IGW-E122 |
GRACEFUL_SHUTDOWN This error code indicates that requests received at ingress-gateway rejected gracefully during the ingress-gateway shutdown. |
This indicates that the service/pod is shutting down and responses sent include this Error Response | (Re) Deploy IGW, or prevent shutdown |
| OBSF-IGW-E162 |
XFCC_HEADER_VALIDATION_FAILURE This error code indicates that validation of XFCC header failed at ingress-gateway. |
Indicates that the XFCC Header in the request is in the correct format but is not validated as it is the wrong value for the request. | Verify if the right value is updated in the XFCC Header based on the IGW Deployment configuration. |
| OBSF-IGW-E163 |
XFCC_HEADER_NOT_PRESENT_OR_EMPTY This error code indicates that request received at ingress gateway with no XFCC header or empty XFCC header. |
XFCC Header is not present | Include the XFCC Header in the Request |
| OBSF-IGW-E164 |
XFCC_MATCHCERTCOUNT_GREATER_THAN_CERTS_IN_HEADER This error code indicates that XFCC header validation failed due to XFCC certificate count miss match in ingress-gateway. |
IGW Configuration requires more certs than the number of certs sent in the request | Check the number of certificates in the request sent and attach the certificates matching the configuration set for IGW |
| OBSF-IGW-E165 |
XFCC_HEADER_INVALID This error code indicates that invalid XFCC header received at ingress-gateway. |
XFCC Header present in request is not of the right format. | Fix the XFCC Header of the request and send. |
| OBSF-IGW-E174 |
OAUTH_PRODUCER_SCOPE_NOT_PRESENT This error code indicates that producer scope not present in the OAuth token received at ingress-gateway. |
Producer Scope is not present in the token of the request | Check for Producer Scope value in the token used in the request |
| OBSF-IGW-E175 |
OAUTH_PRODUCER_SCOPE_MISMATCH This error code indicates that producer scope present in the OAuth token miss match with producer scope configured in ingress gateway. |
Producer Scope sent through the token either has wrong format, has been used incorrectly, or incorrect value is present. | Verify the Producer Scope Attribute of the token sent through the request |
| OBSF-IGW-E179 |
OAUTH_TOKEN_INVALID This error code indicates that invalid OAuth token received at ingress-gateway. |
Indicates that the OAuth Token received at IGW is not valid, i.e., not in the correct format. | Verify if the OAuth Token is in the right format and configured with the right set of values with respect to the configuration at the gateway. |
| OBSF-IGW-E180 |
OAUTH_TOKEN_ABSENCE This error code indicates that request received at ingress gateway with no OAuth token or empty OAuth token |
OAuth Token is missing in the request | Include the OAuth Token in the request |
| OBSF-IGW-E192 |
PARTIAL_SHUTDOWN This error code indicates that requests are being discarded partially at ingress-gateway when Control shutdown feature enabled. |
Behaviour is observed when ControlledShutdown is enabled | Disable ControlledShutdown |
| OBSF-IGW-E193 |
COMPLETE_SHUTDOWN This error code indicates that requests are being discarded completely at ingress-gateway when Control shutdown feature enabled. |
Behaviour is observed when ControlledShutdown is enabled | Disable ControlledShutdown |
| OBSF-IGW-E201 |
IGW_OVERLOAD_CONTROL_PERCENTAGE_DISCARD This error code indicates that requests are being rejected when load level matches with configured percentage in discard policy mapping of overload control feature. |
The number of requests have reached the configured percentage for OverloadControl. When this value has reached, the respective Error Code is displayed | Change the percentage value to accommodate more requests and not to display the error code. |
| OBSF-IGW-E202 |
IGW_OVERLOAD_CONTROL_PRIORITY_DISCARD This error code indicates that requests with sbi-priority header with value greater than configured number of discarded load level matches in discard policy mapping of overload control feature. |
The number of requests have reached the configured priority for OverloadControl. When this value has reached, the respective Error Code is displayed | Change the priority value to accommodate more requests and not to display the error code. |