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

Configuring the SAE to Manage JUNOS Routing Platforms

A JUNOS routing platform interacts with the SAE by using a JUNOS software 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:

shared sae configuration driver junos {
beep-server-port beep-server-port ;
tls-beep-server-port tls-beep-server-port ;
connection-attempts connection-attempts ;
keepalive-interval keepalive-interval ;
message-timeout message-timeout ;
batch-size batch-size ;
transaction-batch-time transaction-batch-time ;
sdx-group-name sdx-group-name ;
sdx-session-group-name sdx-session-group-name ;
send-commit-check send-commit-check ;
}

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.
  2. Specify the TCP port number that is used to communicate with the sdxd process on JUNOS routing platforms. 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.

  3. Specify the TLS port number that is used for TLS connections to the JUNOS routing platform.

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

  4. Specify the number of outstanding connection attempts before new connection attempts are dropped.
  5. Specify the interval between keepalive messages sent from the router.
  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.

  7. Specify the minimum number of service configuration transactions that are committed at the same time
  8. Specify the maximum time to collect configuration transactions in a batch.
  9. Specify the name of a session group on the JUNOS routing platform in which provisioning objects are stored.
  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.
  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 Topics


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