Configuring the SAE to Manage Devices Running Junos OS (SRC CLI)

A device running Junos OS interacts with the SAE by using a Junos OS process called sdxd. When the sdxd process establishes a TCP/IP connection to the SAE, the SAE begins to manage the router. The Junos router driver configuration defines parameters related to the interactions between the SAE and the sdxd process.

Use the following configuration statements to configure the Junos router driver:

To configure the Junos router driver:

1. From configuration mode, access the configuration statement that configures the Junos router driver. In this sample procedure, the Junos driver is configured in the west-region group.
   user@host# edit shared sae group west-region configuration driver junos
2. Specify the TCP port number that is used to communicate with the sdxd process on devices running Junos OS. This port number must match the port number configured in the sdxd process on the router.

   If you set this value to zero and the TLS BEEP server port is set, the SAE accepts only TLS connections.

   [edit shared sae group west-region configuration driver junos] user@host# set beep-server-port beep-server-port
3. Specify the TLS port number that is used for TLS connections to the device running Junos OS.

   If you set this value to zero, the SAE does not accept TLS connections.

   [edit shared sae group west-region configuration driver junos] user@host# set tls-beep-server-port tls-beep-server-port
4. Specify the number of outstanding connection attempts before new connection attempts are dropped.
   [edit shared sae group west-region configuration driver junos] user@host# set connection-attempts connection-attempts
5. Specify the interval between keepalive messages sent from the router.
   [edit shared sae group west-region configuration driver junos] user@host# set keepalive-interval keepalive-interval
6. Specify the amount of time that the router driver waits for a response from the sdxd process.

   Under a high load the router may not be able to respond fast enough to requests. Change this value only if a high number of timeout events appear in the error log.

   [edit shared sae group west-region configuration driver junos] user@host# set message-timeout message-timeout
7. Specify the minimum number of service configuration transactions that are committed at the same time
   [edit shared sae group west-region configuration driver junos] user@host# set batch-size batch-size
8. Specify the maximum time to collect configuration transactions in a batch.
   [edit shared sae group west-region configuration driver junos] user@host# set transaction-batch-time transaction-batch-time
9. Specify the name of a session group on the device running Junos OS in which provisioning objects are stored.
   [edit shared sae group west-region configuration driver junos] user@host# set sdx-session-group-name sdx-session-group-name
10. Enable or disable commit check. If enabled, a more detailed error message is logged if a batch fails, which lets you verify individual transactions in a batch.
    [edit shared sae group west-region configuration driver junos] user@host# set send-commit-check send-commit-check
11. (Optional) Verify your configuration.

    [edit shared sae group west-region configuration driver junos]
    user@host# show 
    beep-server-port 3333;
    tls-beep-server-port 0;
    connection-attempts 50;
    keepalive-interval 45;
    message-timeout 30000;
    batch-size 10;
    transaction-batch-time 2000;
    sdx-group-name sdx;
    sdx-session-group-name sdx-sessions;
    send-commit-check true;

Related Documentation

• Creating Grouped Configurations for the SAE (SRC CLI)
• Configuring the SAE to Manage Devices Running Junos OS (C-Web Interface)
• Configuring Secure Connections Between the SAE and Devices Running Junos OS
• Configuring Devices Running Junos OS to Interact with the SAE
• Monitoring Interactions Between the SAE and Devices Running Junos OS