D Error Code Dictionary
Table D-1 Error Code Dictionary for BSF Management
| App Error Id | Description | Cause | Action |
|---|---|---|---|
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-01-400-00005-NA-02 | The |
The previous error appears whenever the Binding Request Query contains multiple UE Addresses (e.g. a MAC-48 Address and an IPv4 Address), or the mandatory query parameters have an incorrect format. | NA |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-01-400-00006-NA-02 | The |
The previous error appears whenever the Binding Request optional query parameters has an incorrect format or value. | NA |
| 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
|
The previous error appears whenever the Binding Request Query does not contain a mandatory parameter. Mandatory parameters are the following:
|
NA |
| EC-OBSF-BSF_MGMT-INTRNL-EI-05-02-500-00000-01-02 | The |
The previous error appears whenever an internal error occurs on BSF Management Service while trying to register. | NA |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00003-01-02 | The |
The previous error appears whenever the Binding Data from the Binding Request contains multiple UE Addresses (e.g. a MAC-48 Address and an IPv4 Address), or the IP Address is missing its IPv4 Address. | NA |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00008-01-02 | The |
The previous error appears whenever a mandatory IE in the Binding Data from the Binding Request has an incorrect format. | NA |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00009-01-02 |
The
|
The previous error appears whenever the Binding Request optional query parameters has an incorrect format or value. | NA |
| EC-OBSF-BSF_MGMT-REQVLD-EI-05-02-400-00010-01-02 | The |
The previous error appears whenever a mandatory IE is missing in the Binding Data from the Binding Request. Mandatory IE are the following:
|
NA |
| EC-OBSF-BSF_MGMT-INTRNL-EI-05-04-500-00056-01-02 | The |
The previous error appears whenever an internal error occurs on BSF Management Service while trying to deregister. | NA |
Table D-2 Error Code Dictionary for Egress Gateway
| App Error Code | Error Type | Description | Cause | Action |
|---|---|---|---|---|
| E001 | CONNECTION_TIMEOUT | This error code indicates that egress-gateway is unable to establish the connection with peer NF in the configured connectionTimeout period. | The server is down or it takes too long to respond. | Increase the timeout value or check if the server is up and running |
| E002 | REQUEST_TIMEOUT | This error code indicates that request processing takes more time than the configured request timeout at egress-gateway. | A successful TCP connection was established but no response was received within the expected time frame. | Consider increasing the request timeout setting on the gateway or optimizing the backend services to handle the request faster. |
| E003 | UNKNOWN_HOST_EXCEPTION | This error code indicates that egress-gateway is unable to resolve the peer NF service host name. | The error message indicates that the ingress gateway is unable to resolve the configured backend service hostname. This could be due to several reasons such as incorrect DNS settings, network issues, or misconfigured hostnames. | Ensure that the hostname provided in the configuration file matches the actual hostname of the backend service. If necessary, update the DNS records or configure the gateway to use alternative routing service. |
| E004 | CONNECT_EXCEPTION | This error code indicates that egress-gateway is unable to establish the connection with peer NF service. | Peer/NF Service is refused due to incorrect network configuration, inactive service | Verify Peer/NF service availability, network routing, and ensuring the correct IP address and port are being used |
| E005 | INVALID_HTTP_REQUEST_EXCEPTION | This error code indicates exception occurred because HTTP1.1 is disabled but oc-http-version header has value http1. | enableOutgoingHttp1 flag of Egress Gateway is set to false. | Set enableOutgoingHTTP1 flag in EGW config to true. |
| E006 | CLOSED_CHANNEL_EXCEPTION | This error code indicates that closed channel exception has occurred as incoming TCP connection was abruptly terminated before egress gateway had send back the response. | Unexpected Behaviour within the Network | Capture network traces to identify the root cause of the abrubt connection termination . |
| E007 | SSL_HANDSHAKE_EXCEPTION | This error code indicates the ssl hand shake exception occurred in egress gateway. | Incorrect Certificates used for establishing the connection. Use of incorrect certificates or cipher suites mismatch or TLS Version incompatibility. | Cross Check Certificates used, Cipher suites and TLS Version match between the client and server. |
| E051 | REJECTED_EXECUTION_EXCEPTION | This error code indicates that RejectedExecutionException has occurred at egress-gateway as the incoming no. of requests are more than the queueCapacity configured in applicationThreadPoolConfig. | Value set for applicationThreadPoolConfig in configuration of EGW is low for incoming traffic | Increase the value of applicationThreadPoolConfig in EGW Configuration or reduce the number of requests flowing to EGW for incoming traffic |
| E052 | NOT_FOUND_EXCEPTION | This error code indicates that egress-gateway received request path with an endpoint that is not implemented in the peer NF service. | URI/Path of the request is incorrect or required path is not configured on Peers/NFs side. | Configure the required URI in routesConfig or correct the URI of the request |
| E054 | INTERNAL_ERROR | This error code indicates that some unknown internal error occurred in egress-gateway while processing the request. | NA | NA |
| E102 | LATE_ARRIVAL_EXCEPTION | This error code indicates that late arrival exception occurred at egress-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 accomodating to the calculated timeout value from SBI Timer Header values. |
| E112 | NOTIFICATION_RATE_LIMIT | This error code indicates that requests are being rejected after exceeding the bucketCapacity when notificationRateLimit feature is enabled. | Request Count is higher than the configured bucketCapacity at notificationRateLimit in EGW Configurations | Either increase the bucketCapacity or reduce the number requests |
| E122 | RETRY_AFTER_ERROR | This error code indicates that retry-after feature is enabled and producer fqdn is blacklisted and hence the request cannot be fulfilled. | RetryAfter Feature is enabled, and the blackListPeriod is completed for the peer. But when we access the peer while it is still blacklisted, we see this error. | If not the intended behaviour, disable RetryAfter Feature |
| E127 | GRACEFUL_SHUTDOWN | This error code indicates that the service shutdown is in progress. | During Normal Flow of requests, if the IP changes and DNS refresh occurs | Wait for the IP reset and DNS refresh to complete. After establishing connection to the service, then try sending the request again |
| E132 | VIRTUAL_HOST_RESOLUTION_ERROR | This error code indicates that the DNS resolution of virtual fqdn failed. | The vFQDN provided for the virtual host cannot be resolved by the DNS servers. | Verify that the vFQDN is correctly spelled and formatted (or) ensure that the DNS server is operational (or) confirm that the FQDN exists in the DNS records. |
| E152 | INVALID_OAUTH_TOKEN_REQUEST | This error code indicates the exception occurred because of bad AccessToken request received. | OAuth Token received might be of wrong format/value. | Check for the correct format/value on the basis of the configurations at EGW |
| E153 | OAUTH_INTERNAL_ERROR | This error code indicates that egress gateway is unable to send AccessToken request to NRF. | InternalServerError because of error while processing/sending the request to NRF | NA |
| E154 | OAUTH_TOKEN_RETRIEVAL_FAILURE | This error code indicates error in retrieving token from NRF. | Error while retrieving the token from Response received from NRF | NA |
| E155 | OAUTH_NRF_RESPONSE_FAILURE | This error code indicates response failure from NRF(invalid/bad response) while trying to fetch oauth token. | Error while processing the Response received from NRF | NA |
| E172 | EGRESS_RATE_LIMITING | This error code indicates that requests are being rejected after exceeding the bucketCapacity when egressRateLimiting feature is enabled. | Number of requests are exceeding the bucket size set in the configurations for EGW. | Edit bucket size in EGW configurations, or reduce the rate of request. |
| E182 | EGW_CUSTOM_EXCEPTION | This error code indicates custom exception occurred in some feature at egress gateway because some conditions failed to fulfill at runtime namely SbiRouting, SeppProxyFilter, PeerBlackListHelper, EgressGatewayFilter | NA | Identify the Error from the Response received, and cross verify with the respective documentaiton |
| E183 | RESPONSE_STATUS_EXCEPTION | This error code indicates that ResponseStatusException was created by Spring boot as egress gateway exception handler was not able to handle a exception. | NA | NA |
| E192 | PARTIAL_SHUTDOWN | This error code indicates that requests are being discarded partially at egress-gateway when Control shutdown feature enabled. | Behaviour is observed when ControlledShutdown is enabled | Disable ControlledShutdown |
| E193 | COMPLETE_SHUTDOWN | This error code indicates that requests are being discarded completely at egress-gateway when Control shutdown feature enabled. | Behaviour is observed when ControlledShutdown is enabled | Disable ControlledShutdown |
| E202 | INVALID_ROUTE_EXCEPTION | This error code indicates invalid route exception has occurred as invalidRouteFilter was configured in the routesConfiguration. | Invalid Route Exception is a filter enabled at route level in routesConfig. | If this is unexpected behaviour, check the path if that is the expected path that was supposed to be marked as an invalid route. |
| E206 | IP_TYPE_MISMATCH_EXCEPTION | This error code indicates that there is a mismatch in the configured EgressRoutingMode IP type and the DNS resolved IP type. | The type of IP resolved by DNS is differing from the IP Type configured at the EGW. | Verify if gateway is deployed in dual stack IP setup |
Table D-3 Error Code Dictionary for Ingress Gateway
| App Error Code | Error Type | Description | Cause | Action |
|---|---|---|---|---|
| E001 | CONNECTION_TIMEOUT | This error code indicates that ingress-gateway is unable to establish the connection with backend service in the configured connectionTimeout period. | The server is down or it takes too long to respond. | Increase the timeout value or check if the server is up and running |
| 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. |
| E003 | UNKNOWN_HOST_EXCEPTION | This error code indicates that ingress-gateway is unable to resolve the configured backend service host name. | The error message indicates that the ingress gateway is unable to resolve the configured backend service hostname. This could be due to several reasons such as incorrect DNS settings, network issues, or misconfigured hostnames. | Check if the FQDN of the backend service is correctly resolved from the ingress gateway's perspective. If necessary, update the DNS records or configure the ingress gateway to use alternative routing servers. Additionally, ensure that the hostname provided in the configuration file matches the actual hostname of the backend service. |
| E004 | CONNECT_EXCEPTION | This error code indicates that ingress-gateway is unable to establish the connection with backend service. | Peer/NF Service is refused due to incorrect network configuration, inactive service | Verify Peer/NF service availability, network routing, and ensuring the correct IP address and port are being used |
| E005 | BLACKLIST_IP_EXCEPTION | This error code indicates that BlackList IP exception has occurred while establishing new connection with blacklisted IP at ingress-gateway. IP would be blacklisted if TCP connection to this IP failed for more than 10 times. | Gateway is not able to establish TCP connection for more than 10 times | Verify why the IP is not accepting TCP Conneciton |
| E006 | CLOSED_CHANNEL_EXCEPTION | This error code indicates that closed channel exception has occurred as incoming TCP connection was abruptly terminated before ingress gateway had send back the response. | Unexpected Behaviour within the Network | Capture Network Traces to identify the root cause of why the connection terminated abrubtly |
| E051 | REJECTED_EXECUTION_EXCEPTION | This error code indicates that RejectedExecutionException has occurred at ingress-gateway as the incoming no. of requests are more than the queueCapacity configured in applicationThreadPoolConfig. | Value set for applicationThreadPoolConfig in configuration of IGW is low for incoming traffic | Increase the value of applicationThreadPoolConfig in IGW Configuration or reduce the number of requests flowing to IGW for incoming traffic |
| E052 | NOT_FOUND_EXCEPTION | This error code indicates that ingress-gateway received request path with an endpoint that is not implemented in the backend service. | URI of the Request has not been configured in the routesConfig for IGW. | Configure the required URI in routesConfig or correct the URI of the request |
| E053 | SOCKET_EXCEPTION | This error indicates that SocketException has occurred as ingress-gateway was unable to create TCP connection. | Network connectivity issues, network restrictions, or misconfigured endpoints | Verify if there are any network policies blocking the communication between the ingress gateway and the backend service. Confirm that the endpoint URL provided in the configuration file is correct and reachable from the ingress gateway |
| 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 |
| 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. |
| E112 | USERAGENT_VALIDATION_FAILURE_EXCEPTION | This error code indicates that validation of user-agent header failed at ingress-gateway. | The NF configured in the user-agent header of the request does not match with the configured NFs in the IGW | Either verify if the request has the correct NF Value configured, or if the intended NF as been added into the list of acceptable NFs at the IGW end. |
| 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 |
| E132 | GLOBAL_RATELIMIT | This error code indicates that requests are being rejected after exceeding the burstCapacity when global ratelimit feature enabled. | Number of requests are exceeding the bucket size set in the configurations for IGW, which is calculated on the basis of maxTokenRequest and burstCapacity. | Modify the globalIngressRateLimiting parameter of Gateway configurations to accommodate incoming requests. |
| E152 | RSS_BASED_RATELIMIT | This error code indicates that requests are being rejected after exceeding the burstCapacity when rss ratelimit feature enabled. | When egressrateLimitingConfigMap is configured with burstCapacity and ratelimiting enabled, this exception is thrown when the requests count exceeds this burstCapacity and it is also based on the MNC and MCC values. | If this is unexpected behaviour, change the values/attributes in egressrateLimitingConfigMap. |
| 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. |
| 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 |
| 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 |
| 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. |
| E171 | OAUTH_TOKEN_VALIDATION_FAILURE | This error code indicates that validation of OAuth token failed at ingress-gateway. | Oauth token passed with the request is enclosed with values which are incorrect with respect to the configuration present at the gateway. | Verify and include the Oauth Token with the correct set of values related to the deployed IGW config. |
| E172 | OAUTH_CERT_EXPIRED | This error code indicates that OAuth cert expired received at ingress-gateway. | Indicates that all the attributes are present and in the correct format, but the token has expired with respect to IGW's configuration | Attach an Oauth Token in the Request which hasn't expired |
| E173 | OAUTH_MISMATCH_IN_KID | This error code indicates that OAuth miss match in KID at ingress-gateway. | Incorrect issuer and incorrect KID Value is included in the request. | Check the issuer attribute and KID Value passsed in the request. |
| E173 | OAUTH_MISMATCH_IN_ALGORITHM_FOR_KID | This error code indicates that algorithm used while generating token is not matching with the configured algorithm when the oauthValidationMode is "KID_ONLY" | Algorithm used while generating token is not matching with the configured algorithm. | Correct the algorithm used. |
| 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 |
| 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 |
| E176 | OAUTH_MISMATCH_IN_NRF_INSTANCEID | This error code indicates that nrf instance id present in the OAuth token miss match with nrf instance id configured in ingress gateway. | Wrong issuer attribute is passed along with the access token. | Check the issue attribute attached along with the request |
| E176 | OAUTH_MISMATCH_IN_ALGORITHM | This error code indicates that algorithm used while generating token is not matching with the configured algorithm when the oauthValidationMode is "KID_PREFERRED" or "INSTANCEID_ONLY" | Algorithm used while generating token is not matching with the configured algorithm. | Correct the algorithm used. |
| E177 | OAUTH_PRODUCER_PLMNID_MISMATCH | This error code indicates that the received OAuth token miss match with producer plmn configured in ingress gateway. | Configured PLMN ID in IGW, is not matching with the PLMN ID received through the OAuth Token | Correct the PLMN ID in the configuration for IGW or correct the ID in the OAuth Token itself. |
| E178 | OAUTH_AUDIENCE_NOT_PRESENT_OR_INVALID | This error code indicates that the received OAuth token does not contain an audiance or invalid audiance at ingress gateway. | Token is passed with Audience parameter containing only correct nfType but in a different Case. An Audience Parameter with missing or wrong values for NfType and NfInstanceId can also raise this error | Verify and include the correct NfType or/and NfInstanceID in the request. |
| 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. |
| 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 |
| E182 | IGW_OVERLOAD_CONTROL_EXCEPTION | This error code indicates that overload control exception occurred at ingress-gateway. | Occurs when the feature OverloadControl is enabled and configured at the requests/second being sent. | Modify the Configuration for acceptable requests/second. |
| E183 | RESPONSE_STATUS_EXCEPTION | This error code indicates that ResponseStatusException was created by Spring boot as ingress gateway exception handler was not able to handle a exception. | NA | NA |
| E191 | CCA_HEADER_VALIDATION_FAILURE | This error code indicates that validation of CCA header failed at ingress-gateway. | CCA Header sent through the request, failed while validation. | Include the correct value for CCA Header in the request |
| 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 |
| 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 |
| E200 | IGW_TRAFFIC_REJECTION | This error code indicates all requests will rejected at ingress-gateway when traffic reject feature enabled. | trafficrejectmode has been enabled through REST configuration for IGW | Disbale trafficrejectmode through REST configuration for 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. |
| 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. |
| E211 | IGW_ROUTE_RATELIMITER_PRIORITY_DISCARD | This error code indicates that requests are being rejected when priority level matches with configured priority in discard policy mapping of route level ratelimiting feature. | Request is rejected because priority level set in the SBI header is greater than the configured priority in the route level rate limiting, discard policy mapping. | Increase the Priority in discard policy mapping for route level rate limiting, so requests with higher priority are accepted. |
| E220 | IGW_PLMN_EGRESS_RATELIMIT | This error code indicates that requests are being rejected after exceeding the burstCapacity when plmn egress ratelimit feature enabled | When egressrateLimitingConfigMap is configured with burstCapacity and ratelimiting enabled, this exception is thrown when the requests count exceeds this burstCapacity and it is also based on the MNC and MCC values. | If this is unexpected behaviour, change the values/attributes in egressrateLimitingConfigMap. |
| E221 | INVALID_ROUTE_EXCEPTION | This error code indicates invalid route exception has occurred as invalidRouteFilter was configured in the routesConfiguration. | Invalid Route Exception is a filter enabled at route level in routesConfig. | If this is unexpected behaviour, check the path if that is the expected path that was supposed to be marked as an invalid route. |
| E223 | OAUTH_ALGORITHM_INVALID | This error code indicates that the algorithm used while generating the token is not a valid algorithm. | Algorithm used while generating token is not a valid algorithm. | Provide the valid algorithm while generating the token. |
Table D-4 Error Code Dictionary for NRF Client
| App Error Code | Description | Cause | Action |
|---|---|---|---|
| E001 | This error code indicates that egress-gateway is unable to establish the connection with peer NF in the configured connectionTimeout period. | The server is down or it takes too long to respond. | Increase the timeout value or check if the server is up and running |
| NCMGMT-E001 | Service Unavailable error response | NF_CONGESTION | Cannot send NRF request since all NRFs are down |
| NfType-EGW-E002 | Timeout for discovery to NRF client | Request Timeout at EGW | Request Timeout |
| NC_MGMT-E002 | When error where no NRF are available for service | NO_AVAILABLE_NRF | No NRFs available for service |
| NC_MGMT-E007 | Uninstall or scale egress-getaway | UNKNOWN_HOST_EXCEPTION | UnknownHostException when communicating with NRF |
| NCMGMT-E512 | Request can not able to complete a request to NRF | SYSTEM_FAILURE | Invalid patch operation |
| NC_MGMT-E101 | Send a discoveryRequest with header OC-Force-Rediscovery with a value different than 0 or 1. | MANDATORY_QUERY_PARAM_INCORRECT | Invalid custom discovery header value for OC-Force-Rediscovery |
| NC_MGMT-E102 | Send a discoveryRequest with header OC-Retention-Period with a foobar as value. | MANDATORY_QUERY_PARAM_INCORRECT | Invalid custom discovery header value for OC-Retention-Period |
| NC_MGMT-E109 | Send a discovery request with missed parameter value | MANDATORY_QUERY_PARAM_INCORRECT | Missing name or value of a discovery parameter |
| NCMGMT-E110 | When send a discovery request with missed parameter value and using '&' | MANDATORY_QUERY_PARAM_INCORRECT | One or more discovery parameters are not valid |
| NCMGMT-E202 | When the notificationURI could be null | MANDATORY_IE_MISSING | Missing parameter notificationUri in subscription request |
| NCMGMT-E202 | Request to NrfRouteList Subscription with empty URI | MANDATORY_IE_MISSING | Missing parameter notificationUri in subscription request |
| NCMGMT-E203 | When the noticationUri could be invalid | MANDATORY_IE_INCORRECT | Invalid notificationUri for subscription request |
| NCMGMT-E203 | Request to NrfRouteList Subscription with wrongURI | MANDATORY_IE_INCORRECT | Invalid notificationUri for subscription request |
| NC_MGMT-E209 | POST request to /notifications/nrfRouteList" with an empty body | MISSING_PARAMETER | The entire request body is missing |
| NC_MGMT-E301 | When missed or not valid NFInstance for NF Profile | MISSING_PARAMETER | Missing parameter 'nfInstanceID' (uuid) |
| NC_MGMT-E302 | PUT request to "/nf-instances/{uuid}" with an null value for the profile in the request body | MISSING_PARAMETER | Missing parameter 'nfProfile' |
| NC_MGMT-E302 | PUT request to /nf-instances/{uuid}" with an empty bod | MISSING_PARAMETER | Missing parameter 'nfProfile' |
| NCMGMT-E309 | Registration without NF instance ID with invalid service status | MANDATORY_IE_INCORRECT | Semantic validation failed for received NfProfile |
| NC_MGMT-E033 | When bindingResult contains error | MANDATORY_IE_INCORRECT | Invalid attributes in request body |
| NC_MGMT-E033 | When Request goes with an empty body | INVALID_REQUEST_BODY | Invalid attributes in request body |
| NC_MGMT-E033 | PUT request to "/nf-instances/{uuid}" with an invalid value | INVALID_REQUEST_BODY | Invalid attributes in request body |
| NC_MGMT-E402 | invalid null SubcriptionId. | MISSING_PARAMETER | Missing parameter 'subscriptionID' |
| NC_MGMT-E403 | investigating | ||
| NC_MGMT-E411 | FAILED_CFG_ITEM_CREATION | FAILED_CFG_ITEM_CREATION | Failed config item creation for subscriptionData |
| NC_MGMT-E502 | POST request to "/nnrf-client/v1/notify" with an empty body | INVALID_PROFILE | Invalid attributes in notified NfProfile |
| NC_MGMT-E510 | invalid config item creation for the profile. | FAILED_CFG_ITEM_CREATION | Failed config item creation for profile from notificationData |