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

## BEEP Connection Between JUNOS Routing Platforms and the SAE

For information about which JUNOS routing platforms and releases a particular SRC release supports, see the SRC Release Notes.

The SAE interacts with a JUNOS software process, referred to as the SRC software process in this documentation, on the JUNOS routing platform. The SAE and the SRC software process communicate using the Blocks Extensible Exchange Protocol (BEEP). You can secure the BEEP connection by using Transport Layer Security (TLS).

When the SRC software process establishes a BEEP session for the SAE, the SAE configures an interface on the JUNOS routing platform. The SAE builds the configuration for an interface using the policies stored in the directory. If the policies are subsequently modified, the SAE builds a new configuration and reconfigures the interface on the JUNOS routing platform. The JUNOS routing platform stores data about interfaces and services that the SAE manages in a configuration group called sdx. You must create this configuration group on the JUNOS routing platform.

#### Related Topics

- Adding Operative JUNOS Routing Platforms
- Configuring the SAE to Manage JUNOS Routing Platforms
- Configuring Secure Connections Between the SAE and JUNOS Routing Platforms

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