Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Related Documentation

Configuration Tasks for Integrating Third-Party Network Devices (SRC CLI)

To integrate third-party devices into your SRC network, complete the following tasks:

  • Write a script and add a script service that references the script.

    See Setting Up Script Services.

  • Add objects for the devices.

    See Adding Objects for Network Devices (SRC CLI).

  • Configure an SAE community.

    See Setting Up SAE Communities (SRC CLI).

  • (Optional) Configure SAE properties for the Event Notification API if you are using the event notification method to log in subscribers.

    See Configuring SAE Properties for the Event Notification API (SRC CLI).

  • (Optional) Specify whether to prefer the second user session for an existing IP address upon receiving an ipUp event if the first and second sessions have different session IDs. If set, the first user session is terminated.
    [edit shared sae configuration driver third-party] user@host# set prefer-second-user-session
  • Configure the session store.

    See Storing Subscriber and Service Session Data.

  • If you are using the event notification method to log in subscribers, integrate the SAE with an IP address manager. There are two ways to do so:
    • Use the event notification API to create an application that notifies the SAE when events occur between the DHCP server and the network device.

      See the event notification API documentation in the SAE CORBA remote API documentation on the Juniper Networks website at

    • Use Monitoring Agent, a sample application that was created with the event notification API and that monitors DHCP or RADIUS messages for DHCP or RADIUS servers.

      See the SRC PE Sample Applications Guide.

Related Documentation

Modified: 2017-08-03