Managing Dynamic Policy Changes on MX Series Routers Using the Diameter Application
You can use the policy manager in the SRC software to dynamically manage subscriber level policy changes on MX Series routers. The PTSP device driver in the SRC software and the PTSP in the MX Series router are peers that communicate using a Diameter application. Information about subscriber policy changes is communicated between the PTSP and PTSP device driver using Diameter messages.
The SRC software includes a Diameter server process that forwards AAR, ACR, SRQ, and STR messages from PTSP to the PTSP device driver in the SAE, and that forwards PPR and ASR messages from the PTSP device driver to PTSP. These Diameter messages perform these functions:
AA-Answer (AAA)—Sent in response to the AAR message for confirmation of the result of QoS provisioning.
AA-Request (AAR)—Attaches the subscriber to the access network.
Accounting-Request (ACR)—Provides accounting information.
Abort-Session-Request (ASR)—Disconnects the subscriber.
Push-Profile-Request (PPR)—Starts, modifies, or stops a service session.
Session-Resource-Query (SRQ)—Initiates synchronization.
Session-Termination-Request (STR)—Detaches the subscriber from the access network.
In the SRC software, you configure the Diameter peer (the MX Series router) and a device type (junos-ptsp) for each device managed by the SAE. The Diameter server process in the SRC software searches all devices of device type junos-ptsp for virtual routers that include the local host in their SAE connections. For these devices, the Diameter server process establishes a logical connection with the peers (in this case the MX Series router PTSP) referenced in the device configuration.