Feature Configuration
To configure this feature and to enable the system fault recovery, use the following sample configuration:
config
system-diagnostics { gtp | pfcp | service | sgw-service }
fault
action { abort | cleanup { file-detail | interval | num | skip { ims | emergency | wps } } | graceful-Reload | reload }
end
NOTES:
-
system-diagnostics { gtp | pfcp | service | sgw-service } —Specify the required type of service pods for system diagnostics. The available pod options are gtp, pfcp, smf-service, and sgw-service.
-
fault —Enables fault recovery while processing sessions.
-
action { abort | cleanup | graceful-Reload | reload } —Specify one of the following actions to take on fault occurrence. The default action is reload.
-
abort —Deletes the faulty transaction and clears its session cache. The database doesn't get cleared.
NoteIt's an exclusive option to the smf-service pod.
-
cleanup { file-detail | interval | num | skip } —Enable the cleanup activity. It has the following selections to mitigate the fault action:
-
file-detail —Lists the file names with line numbers. It excludes the file name details from the recovery.
-
interval —Specifies the duration of the interval in minutes. This duration specifies the permissible interval within which it allows the maximum number of faults. Must be an integer in the range 1–3600.
-
num —Specifies the maximum number of tolerable faults in an interval. Must be an integer in the range 0–50.
-
skip { ims | emergency | wps } —Enable the skip cleanup of a subscriber session for an active voice call, or the WPS, or an emergency call.
-
To detect the active voice calls, use the following command:
profile dnn dnn_name ims mark qci qos_class_id
-
When you enable the skip cleanup configuration, the SMF deletes the faulty transaction, and clears its session cache.
-
When a fault occurs during the session setup or the release state, the SMF performs the following:
– Deletes the transactions on the session end.
– Overrides the configured fault action during these states.
– Clears the session cache and database entries for the faulty transaction.
-
It allows the dynamic configuration change.
-
NoteIt's an exclusive option to smf-service and sgw-service pods.
-
-
graceful-Reload —Specify the option to gracefully reload the pod. The protocol pod handles fault signals to clean up resources like the keepalive port and continues with crash processing (pod restart processing).
NoteIt's an exclusive option to gtpc-ep and protocol service pods.
-
reload —Reloads the pod, when it crashes due to a faulty behavior. It's an option applicable to all the service pods. It’s also the default option.
-