Configuring the SAE to Manage JUNOSe Routers
To set up the SAE to manage JUNOSe routers, you need to configure a router driver that specifies the COPS connection between the SAE COPS server and the COPS client in the JUNOSe router.
To use SDX Configuration Editor to configure a JUNOSe router driver:
- In the navigation pane, select a configuration file for the SAE that you want to configure.
- Select the Router tab, and expand the JUNOSe Router Driver section.
![]()
- Edit or accept the default values in the fields.
See JUNOSe Router Driver Fields.
See Storing Subscriber and Service Session Data.
- Select File > Save.
- Right-click the configuration file, select SDX System Configuration > Export to LDAP Directory.
JUNOSe Router Driver Fields
In SDX Configuration Editor, you can edit the following fields in the JUNOSe Router Driver section of the Router pane in an SAE configuration file.
COPS Server Port
- Port number of the SAE COPS server.
- Value—Port number that matches the configuration of the SDX client in the JUNOSe router
- Default—3288
- Property name—Router.junose.server_port
Backlog
- Number of connection attempts before connections are dropped.
- Value—Integer
- Default—50
- Property name—Router.junose.backlog_connections
Keepalive Interval [s]
- Interval between keepalive messages sent from the COPS client (the JUNOSe router). The COPS client monitors the COPS connection by sending keepalive messages at random intervals between one-fourth and three-fourths of the specified interval. If the client does not receive the expected keepalive answer within the specified timeout, the client terminates the connection.
- Value—Number of seconds in the range 0-32768. A value of 0 means that timeout is disabled.
- Guidelines—A short interval results in a high load on the COPS interface.
A long interval results in a long time before a COPS failure is detected.- Default—45
- Property name—Router.junose.keepalive
Message Timeout [ms]
- Timeout interval in which the COPS server waits for a response to COPS requests. Under a high load the router may not be able to respond fast enough to COPS requests. Change this value only if a high number of COPS timeout events appear in the error log.
- Value—Number of milliseconds
- Default—60000
- Property name—Router.junose.message_timeout
COPS Message Maximum Length [bytes]
- Maximum length of a COPS message.
- Value—Number of bytes in the range 4 bytes to 2 GB
- Guidelines—We recommend that you use the default setting.
- Default—200000
- Property name—Router.junose.message_max_length
COPS Message Read Buffer Size [bytes]
- Buffer size for receiving COPS messages from the JUNOSe client.
- Value—Number of bytes in the range 4 bytes to 2 GB
- Guidelines—We recommend that you use the default setting unless you are instructed to change it by Juniper Networks engineers.
- Default—30000
- Property name—Router.junose.message_read_buffer_size
COPS Message Write Buffer Size [bytes]
- Buffer size for sending COPS messages to the JUNOSe client.
- Value—Number of bytes in the range 4 bytes to 2 GB
- Guidelines—We recommend that you use the default setting unless you are instructed to change it by Juniper Networks engineers
- Default—30000
- Property name—Router.junose.message_write_buffer_size
Pending Address Timeout [ms]
- Maximum time that an address request remains pending.
- Value—Number of milliseconds
- Guidelines—Realistic values are in the range 1000-15000 (5 seconds to 15 seconds).
- Default—5000
- Property name—Router.junose.pending_address_timeout
Number of COPS Handler Threads
- Size of the thread pool for handling unsolicited messages. These threads are shared among all JUNOSe router drivers.
- Value—Number of threads
- Default—20
- Property name—Router.junose.handler_threads
Cache driver expiration
- Minimum amount of time to keep the state of a router driver after its COPS connection has been closed.
- Value—Number of seconds in the range 0-2147483647
- Default—600
- Property name—Router.junose.cachedDriverExpiration
Drop Unmanaged Interfaces for the JUNOSe XDR Driver