How it Works

This section describes how you can use the fault recovery framework to define actions for the crash. The framework allows you to define any of the following actions:

  • Terminate—When a fault occurs, this action terminates the faulty transactions, and clears the subscriber session cache. It’s applicable for smf-service and sgw-service pods.

    Note

    The pod doesn't get restarted. The database doesn't get cleared during this action.

  • Cleanup—When a fault occurs, this action clears the faulty subscriber session and releases the call. It’s applicable for smf-service and sgw-service pods.

  • Graceful reload—When a fault occurs, this action restarts the pod. It’s applicable for gtpc-ep, protocol, and diameter-ep pods. It handles the fault signals to clean up resources, such as the keepalive port and closes it early. It also allows the checkport script to detect the pod state and initiates the VIP switch processing for the corresponding pods.

  • Reload—When the pod crashes, it initiates the reloading activity. It’s a default setting or value applicable for all the pods.