D.2 Recovery of NRF

This section provides the procedure to bring back NRF by scaling up the replica count for the NRF microservices.

Note:

The replica count is noted down before running graceful shutdown. For more details, see Manual Shutdown of NRF.

1. Run the following command to restore the Ingress Gateway replicaSet value:

   kubectl -n <NRF Namespace> get deployments | egrep 'ingressgateway' | awk '{print $1}' | xargs -L1 -r kubectl -n <NRF Namespace> scale deployment --replicas=<Replicas count before ingress gateway was scaled down>

   For example:

   kubectl -n usw2az1001np-ns-or-nrf-001 get deployments | egrep 'ingressgateway' | awk '{print $1}' | xargs -L1 -r kubectl -n usw2az1001np-ns-or-nrf-001 scale deployment --replicas=1

2. Run the following command to restore the Egress Gateway replicaSet value:

   kubectl -n <NRF Namespace> get deployments | egrep 'egressgateway' | awk '{print $1}' | xargs -L1 -r kubectl -n <NRF Namespace> scale deployment --replicas=<Replicas count before egress gateway was scaled down>

   For example:

   kubectl -n usw2az1001np-ns-or-nrf-001 get deployments | egrep 'egressgateway' | awk '{print $1}' | xargs -L1 -r kubectl -n usw2az1001np-ns-or-nrf-001 scale deployment --replicas=1

3. Run the following command to verify that the Ingress Gateway and Egress Gateway replicas mentioned in above command are running:

   kubectl -n <NRF Namespace> get deployments 

   For example:

   kubectl -n usw2az1001np-ns-or-nrf-001 get deployments

   Sample output:

   NAME                                                     READY  UP-TO-DATE AVAILABLE   AGE
   deployment.apps/or-nrf001c-use1az2n01p-appinfo            1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-egressgateway      1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-ingressgateway     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfdiscovery        1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfregistration     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfsubscription     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nrfauditor         0/0    0         0           36h
   deployment.apps/or-nrf001c-use1az2n01p-nrfconfiguration   1/1    1         1           36h
   

4. Wait for Maximum HB value configured at NRF (default 5 mins) * 3, that is, 15 minutes default.

   See maxHbTimer attribute value configured NF Management Options API section from Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

5. Run the following command to restore the NRFAuditor replicaSet value:

   kubectl -n <NRF Namespace> get deployments | egrep 'nrfauditor' | awk '{print $1}' | xargs -L1 -r kubectl -n <NRF Namespace> scale deployment --replicas=<Replicas count before NRF auditor was scaled down>

   Sample command:

   kubectl -n <NRF Namespace> get deployments | egrep 'nrfauditor' | awk '{print $1}' | xargs -L1 -r kubectl -n <NRF Namespace> scale deployment --replicas=<Replicas count before NRF auditor was scaled down>

6. Run the following command to verify that the NRFAuditor replicas mentioned in above command are running:

   kubectl -n <NRF Namespace> get deployments

   Sample command:

   kubectl -n usw2az1001np-ns-or-nrf-001 get deployments

   Sample output:

   NAME                                                     READY  UP-TO-DATE AVAILABLE   AGE
   deployment.apps/or-nrf001c-use1az2n01p-appinfo            1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-egressgateway      1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-ingressgateway     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfdiscovery        1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfregistration     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nfsubscription     1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nrfauditor         1/1    1         1           36h
   deployment.apps/or-nrf001c-use1az2n01p-nrfconfiguration   1/1    1         1           36h