Aborting an SBR Reconfiguration Plan

An ongoing SBR Reconfiguration can be aborted by clicking Abort. This action is an emergency back-out procedure and not recommended unless absolutely necessary. When an SBR Reconfiguration Plan enters the Abort state, the Target SBR Database (in case of a Data Migration type Reconfiguration Plan) or the Target Resource Domain of an SBR Database (in case of a Resizing type Reconfiguration Plan) is abandoned, meaning all Resource User servers stop creating and retrieving records in the target location. The SBR Audit then starts cleaning up the already migrated records. However, in the window where there exist some bound sessions in the target location that were created after the start of the SBR Reconfiguration, there are chances of split-bindings getting created if session creation messages arrive for those subscribers on binding capable Diameter interfaces. The length of this window depends on the number of sessions already migrated before the SBR Reconfiguration was aborted.

SBR Audit cleans up the migrated records by looking for records in the Target Location and sending Gx RAR messages including the Session-Release-Cause AVP. SBR Audit uses the Session Integrity Service module of PCA's Policy DRA function to schedule the sessions for removal. When the Policy Gateway receives the RAR message, it should follow it up with a Session Termination message and then re-establish the session for the subscriber. This new session is created in the Initial SBR database or Initial Resource Domain. All migrated sessions are thereby gradually moved from the Target Location to the Initial Location.

As soon as a Reconfiguration Plan is in the Abort Administrative State, the Progress cell of the row is updated to indicate x of y Records Remain To be Cleaned Up, where x is replaced by the number of recording remaining in the Target Resource Domain or Target SBR Database as the migration abort cleanup progresses, and y is replaced by the number of records that were in the Target Resource Domain or Target SBR database when the Reconfiguration Plan was aborted.

The progress numbers are refreshed by the SBR Audit at a statistically configured interval (defaulting to every ten seconds). These progress updates can be seen each time the SBR Database Reconfiguration Status screen is refreshed, allowing for monitoring for the progress of the Reconfiguration Plan clean up. The cleanup is complete when the Progress reads 0 of y Records Remain To Be Cleaned Up and the Operational Status is changed to Abort Completed - Click Complete to Finish.

If either the user does not wish to wait for the SBR Audit to clean up all migrated sessions (such as when the Policy Gateway does not initiate session tear-downs) or the user wants to avoid sending a large amount of (throttled) RAR traffic toward the PCEFs, then the user can choose to Force Complete the Abort Cleanup by clicking Complete.