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:
Note that it is not possible to check the consistency of individual objects that the SAE provisions Therefore, modifications to a provisioning object while the SAE is disconnected from the router cannot be detected.
Use the following configuration statements to configure the SAE to periodically check the configuration of the JUNOS routing platform:
- shared sae configuration driver junos configuration-checking
- configuration-checking-schedule configuration-checking-schedule ;
- configuration-checking-action (enforce | synchronize |
detect);
To configure the SAE to periodically check the configuration of the JUNOS routing platform:
- user@host# edit shared sae configuration driver
junos configuration-checking
- [edit shared sae configuration driver junos configuration-checking]
-
user@host# set configuration-checking-schedule configuration-checking-schedule
- [edit shared sae configuration driver junos configuration-checking]
-
user@host# set configuration-checking-action enforce | synchronize | detect
[edit shared sae configuration driver junos configuration-checking] user@host# show configuration-checking-schedule "0 0 * * * * *"; configuration-checking-action synchronize;