Configuring NRF Failover Option
The NRF Failover feature enables the user to configure the retry actions for every error code, which occurs during the NRF interactions with SMF and other NFs.
After trying all the hosts or endpoints, the next action is decided based on the failover options, which are configured for the error codes.
To configure the NRF failover functionality, use the following sample configuration:
config
profile nf-client-failure nrf
profile failure-handling failure_handling_name
service name type nrf-nfm
message type { Heartbeat [ re-registration-enabled { false | true } ] | NFUpdate [ failover-enabled { false | true } ] | NRFRegistration [ failover-enabled { false | true } ] }
status-code httpv2 status_code action { retry | retry-next }
end
NOTES:
-
message type { Heartbeat [ re-registration-enabled { false | true } ] | NFUpdate [ failover-enabled { false | true } ] | NRFRegistration [ failover-enabled { false | true } ] } : Specify the NRF message type and enable failover functionality.
The failover options for the NRF messages are as follows:
-
NRFRegistration or NFUpdate
-
true—After trying all the hosts or endpoints in an NRF, the system selects the next available NRF.
-
false—After trying all the hosts or endpoints in an NRF, the system does not select the next available NRF.
Spawning of backup routine is only available for those NRFs in which the endpoints have been tried.
-
-
Heartbeat
-
true—After trying all the hosts or endpoints in an NRF, if the start reregistration option is enabled, then the system starts the reregistration process for the NF clients.
-
false—After trying all the hosts or endpoints in an NRF, the system continues the heart beat routine with the same registered NRF.
-
-
-
status-code httpv2 status_code action { retry | retry-next } : Specify the status code and retry action for the NRF service. Currently only "http" status code is provided. status_code must be an integer in the range of 0–599.
-
retry—The system attempts one more retry to the same endpoint or host.
-
retry-next—The system does not retry the same endpoint or host, but it attempts the retry action to the next available endpoint or host.
-
-
The error handling for NF Registration, NF Heartbeat, and NF Update is based on status codes. This functionality is not available for subscription and NF Deregister messages. The user can configure the max retry-count for the subscription and NF Deregister messages by using the endpoint configuration available in the group nrf management CLI. The system attempts the retry action based on that configuration.
-
The failover-enabled option is applicable for the NF Registration and NF Update messages.
-
The reregistration-enabled option is applicable for the NF Heartbeat message.
-
The failover-enabled or reregistration-enabled options are not applicable for the NF Deregister message.
-
The failover and reregistration options are enabled by default.