Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Adding an MX Series Router as a PTSP Network Device (SRC CLI)

    You can configure the service activation engine (SAE) to manage a packet-triggered subscribers and policy control (PTSP) network device on an MX Series router.

    Use the following configuration statements to configure the network device:

    shared network device name { device-type (junose | junos-ise | junos-ptsp | junos | pcmm | thirdparty);origin-host origin-host;peers [peers...];}
    shared network device name virtual-router name { sae-connection [sae-connection...];user-tracking-plug-in user-tracking-plug-in ...];authentication-plug-in [authentication-plug-in...];vpn-id vpn-id;}

    To configure an MX Series router as a PTSP network device so that the router can be managed by the SAE:

    1. From configuration mode, access the statements that configure network devices. This sample procedure uses mx-name as the name of the router.
      user@host# edit shared network device mx-name
    2. Set the type of device to junos-ptsp.
      [edit shared network device mx-name] user@host# set device-type junos-ptsp
    3. (Optional) Specify the origin hostname of the MX Series router. This example procedure uses mx-origin-host as the origin hostname. The active SAE registers events from the router based on the configured origin host attribute (mx-origin-host in the example). If the origin host is not configured, SAE uses the device name (mx-name in the example) instead.
      user@host# edit shared network origin-host mx-origin-host
    4. Specify the configured peers associated with the device. See Configuring Diameter Peers (SRC CLI).
      [edit shared network device mx-name] user@host# set peers [peers...]

      Note: MX Series routers support only a single peer connection.

    5. From configuration mode, access the statements for virtual routers. The name you specify must match the PTSP partition configured on the MX Series router, which is configured within the logical system:routing instance context. This sample procedure uses the name * for the virtual router.
      [edit shared network device mx-name] user@host# edit virtual-router *

      where * matches any PTSP partition. You can also specify that the PTSP partition be configured in a logical system or in a logical system and routing instance. By default, logical system default and routing instance master are used.

    6. Specify the SAEs that can manage this router.
      [edit shared network device mx-name virtual-router default]user@host# set sae-connection [sae-connection...]
    7. (Optional) Specify a single tracking plug-in or a list of tracking plug-ins used to track subscriber sessions associated with this virtual router.
      [edit shared network device mx-name virtual-router default] user@host# set user-tracking-plug-in [user-tracking-plug-in...]

      Set the user-tracking-plug-in option to the name of the configuration plug-in you configured with the edit shared sae configuration plug-ins name name ssr-writer statement.

    8. (Optional) Specify the plug-ins that authenticate subscribers who log in through this virtual router.
      [edit shared network device mx-name virtual-router default]user@host# set authentication-plug-in [authentication-plug-in...]
    9. (Optional) Specify the VPN identifier used by this virtual router. You can specify VRF instead of a string to use the VRF instance reported by the device as the VPN identifier. In this case, the VPN identifier is the name of the routing instance.
      [edit shared network device mx-name virtual-router default]user@host# set vpn-id (vpn-id | VRF)
    10. (Optional) Verify your configuration.
      [edit shared network device mx-name] 
      user@host# show 
      
      device-type junos-ptsp;
      interface-classifier { 
        rule rule-1 {
          condition {
            interfaceName=*;
          }
          target /lib/default;
        }
      }
      origin-host bng-srcmx480b;
      peers bng-srcmx480b;
      virtual-router * {
        authentication-plug-in ldap-auth;
        sae-connection 10.212.10.2;
        user-tracking-plug-in fileAuth;
        vpn-id 123;
      }
      

    Modified: 2016-04-27