NF Discovery Failure Handling
Discovery NRF endpoint configuration sample is shown below.
product smf# show running-config profile nf-pair nf-type UDM
profile nf-pair nf-type UDM
nrf-discovery-group others_group
locality client LOC1
exit
product smf# show running-config group nrf discovery others_group
group nrf discovery others_group
service type nrf nnrf-disc
endpoint-profile ep1
capacity 30
priority 50
uri-scheme http
endpoint-name ED1
priority 56
primary ip-address ipv4 110.105.227.219
primary ip-address port 8082
secondary ip-address ipv4 110.105.227.220
secondary ip-address port 8082
exit
endpoint-name ED2
priority 10
primary ip-address ipv4 110.1.227.21
primary ip-address port 8082
secondary ip-address ipv4 110.1.227.22
secondary ip-address port 8082
exit
exit
exit
exit
product smf#
In the sample configuration, ED1 has the higher priority endpoint name as its priority is lesser than ED2 (2 against 10). So, whenever there is a NRF discovery required primary ip:port of ED1 [110.105.227.219:8082] is attempted. SMF uses secondary ip:port of ED1 if primary is down. SMF failovers to ED2 only if all ip:port of ED1 is down. There is no state maintained regarding NRF discovery failure with any NRF endpoint. Every time SMF needs to send NRF discovery, SMF starts with ED1 primary and failovers to ED1 secondary in case of failure, followed by ED2 primary and so on.