COPS Connection Between JunosE Routers and the SAE
Configuring the SRC client on a JunosE router opens a Common Open Policy Service (COPS) protocol layer connection to the SAE. When the SRC client software establishes a TCP/IP connection to the SAE, the SAE starts to manage the JunosE router. Subsequently, the SRC client sends configuration changes made on the JunosE router to the SAE, and the SAE updates SRC configurations for services and policies accordingly.
The SAE supports two versions of COPS:
COPS usage for policy provisioning (COPS-PR)
COPS External Data Representation Standard (COPS-XDR)
The version of COPS that you use depends on the version of COPS that your JunosE router supports. When you set up your JunosE router to work with the SAE, you enable either COPS-PR mode or COPS-XDR mode.
Highly Available Connections to JunosE Routers
JunosE routers maintain state information, a feature that allows an active, managing SAE to reconnect to a JunosE router without performing a data resynchronization in the following instances:
The network connection between the SAE and the JunosE router is disrupted, and the router reconnects to the SAE
For JunosE routers with high availability configured, when the secondary SRP takes control from a failed SRP it can reconnect to the SAE
To maintain highly available connections to JunosE routers, configure an SAE community and the session store by configuring SAE identifiers in the configuration for the shared network device virtual router. In the configuration, an exclamation point identifies standby SAEs.