[Contents] [Prev] [Next] [Index] [Report an Error]

## Fault Recovery

If the SAE cannot reach SRC ACP, the SAE will deny all service activation requests. As soon as it reaches SRC ACP, the SAE again sends authorization requests to SRC ACP.

SRC ACP keeps the state of the congestion points in persistent storage, and if SRC ACP becomes unavailable, the service authorization can continue in the correct state. Because service activation requests are automatically denied when the SAE cannot reach SRC ACP, SRC ACP does not miss any active service sessions. The SAE will resend all service deactivation requests after SRC ACP is reachable again.

SRC ACP monitors SAE synchronization events for information about VR availability and SAE availability. If a VR reboots or an SAE becomes unavailable, SRC ACP updates the states of congestion points associated with those devices accordingly.

If the SAE becomes unavailable, the router will automatically reestablish connection to either the redundant SAE or, if a redundant SAE is not available, to the original SAE when it again becomes available. The new SAE notifies SRC ACP that the original SAE failed and specifies which subscriber and service sessions were logged during this time. SRC ACP uses this information to update its state.

#### Related Topics

- Overview of SRC ACP
- Interactions Between SRC ACP and Other Components
- Allocating Bandwidth to Applications Not Controlled by SRC ACP
- Use of Multiple SRC ACPs

[Contents] [Prev] [Next] [Index] [Report an Error]