Managing an SBR Reconfiguration Plan

The SBR Database Reconfiguration Status screen allows Reconfiguration Plans to be managed and monitored. As soon as a Reconfiguration Plan is successfully configured, it appears on the SBR Database Reconfiguration Status screen in the Planned administrative state. From this point onwards until the reconfiguration plan is completed, the SBR Database Reconfiguration Status screen is used to control and monitor the migration.

The basic steps for any Reconfiguration Plan are as follows:

Prepare the Reconfiguration Plan
Start the Reconfiguration Plan
Monitor the progress of Reconfiguration Plan
Complete the Reconfiguration Plan

Note: If a problem arises with the basic steps after starting a Reconfiguration Plan, there is an option to Abort the plan. By aborting the plan, the Reconfiguration Plan is returned to the Planned administrative state where records are read from and written to the Initial Resource Domain or SBR Database only. If a Reconfiguration is aborted, already migrated session or binding records (those which are stored in the Target Resource Domain or SBR Database) are scheduled for removal by the SBR audit such that the corresponding Diameter Sessions get re-established and stored in the Initial Resource Domain or SBR Database.

All rows of the SBR Database Reconfiguration Status screen are automatically refreshed every 10 seconds. The automatic refresh can be paused by clicking the Pause Updates checkbox. The screen can also be refreshed manually by navigating away from the SBR Database Reconfiguration Status screen, then returning.

The six buttons on the screen are disabled unless a row is selected in the Reconfiguration Status pane. If a button is clicked when the row is not in the appropriate state for that button, an error message is displayed indicating why the button is not valid for the row. For example, a Reconfiguration Plan cannot be Started unless it has been Prepared first.

The NOAM knows from configuration data and the Reconfiguration Plan Administrative State which servers are resource users and resource providers for a given Reconfiguration Plan. If the NOAM detects missing merge data from any of the expected resource users or resource providers, the NOAM server reports these servers as Unknown because the status of the servers is not known. Server merge data can be missing at the NOAM if there is a problem with the server itself, or if there is a problem with the merge data communication between the MP server and the NOAM server.

Each Reconfiguration Plan starts out in the Planned Administrative State with Progress indicating Not Started. The Operational status is Ready if all resource users have received notification from all relevant resource providers that the resource provider is available. If any resource user has not received a notification that its resource providers are available (for example, due to problems with the resource provider, or to ComAgent connection problems), the Operational Status is Not Ready.

Reconfiguration Plans in the Planned Administrative State have Resource User and Resource Provider Operational Reason values that correspond to the information seen on the SBR Database Status screen for the SBR Database of a Resizing Plan, or the Initial SBR Database for a Data Migration Plan. These values because only the status of the initial resource is examined when in the Planned State.

As long as a Reconfiguration Plan is in the Planned Administrative State, the Reconfiguration Plan may be deleted or changed. Deletion of a Reconfiguration Plan causes the row for that plan to disappear from the SBR Database Reconfiguration Status screen. Changing a Reconfiguration Plan has no effect until the plan is prepared for execution again.