Checking Changes to the JUNOS Configuration
The SAE can check the configuration of a JUNOS routing platform under its control to detect whether the configuration has changed by a means other than through the SAE. If the SAE finds a disparity between the router and the SAE configurations, it can take several actions. The SAE checks the configuration installed on the router against the state of the SAE session layer (subscriber, service, and interface sessions). While the check is occurring, the SAE does not handle jobs from the router, and all provisioning activity is blocked, including event notifications.
The SAE can take the following actions if it finds a disparity between the router and SAE configurations:
- Remove the disparate sessions from the router. When the SAE removes a session, it generates Stop events for the session and removes the session from the session store and the SAE.
- Re-create the sessions that have been removed. Subscribers whose sessions have been removed need to log back in before they can activate services. During session re-creation, the SAE responds to event notifications and provisioning operations.
If the state of the router configuration is lost because of a failover or a restart, it is not possible to re-create the sessions.
The disparities are reported through the SAE router driver event trap called routerConfOutOfSynch and through the info log.
Note that it is not possible to check the consistency of individual provisioning objects. Therefore, modifications to a provisioning object while the SAE is disconnected from the router cannot be detected.
Setting Up Periodic Configuration Checking
To configure the SAE to periodically check the configuration of the JUNOS routing platform, See Chapter 7, Using JUNOS Routing Platforms in the SRC Network with the SRC CLI.