Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring JSRC Policies (SRC CLI)

 

Tasks to configure JSRC policies are:

Configuring JSRC Policy Lists

To configure policy lists:

  1. From configuration mode, create a policy list. For example, to create a policy list called l1 within a policy group called ise:
  2. Specify the type of policy list.
  3. Specify where the policy is applied on the device.

Configuring JSRC Policy Rules

To configure policy rules:

  1. From configuration mode, create a policy rule inside a policy list that has already been created and configured. For example, to create a policy rule called r1 within policy list l1:
  2. Specify the type of policy rule.

Configuring Dynamic Profile Actions

Use this action to install existing dynamic profiles. You can configure dynamic profile actions for devices such as the MX Series routers.

The profile name must match a dynamic profile configured on the device and the variable name must match a variable configured for the dynamic profile.

Use the following configuration statements to configure a dynamic profile action:

To configure a dynamic profile action:

  1. From configuration mode, enter the dynamic profile action configuration. In this sample procedure, dp is the name of the dynamic profile action.
  2. Enter the profile name to activate.
  3. (Optional) Enter a description for the dynamic profile action.
  4. From configuration mode, enter the parameters used by the profile.

    For example:

  5. (Optional) Configure the value for the variable.

    For example:

  6. (Optional) Configure the variable type. Variable types are mapped to parameter types.

    For example:

For more information about dynamic profiles and subscriber access, see the Junos OS Broadband Subscriber Management and Services Library.

Configuring Operation Script for Policy Provisioning (SRC CLI)

You can use operation scripts to support the policy provisioning for JSRC policy rules. The SRC software passes the operation script values configured by using the operation-script option under the [edit policies group name list name rule name] hierarchy level to the Extensible Subscriber Services Manager Daemon on the MX Series router. You can assign the operation script only to the rules for which the role of the policy list is set as junos-ise and the applicability is set as both.

Note
  • AA-Answer message can have both dynamic profile and operation script in the policy rule, whereas the Push-Profile-Request can have either dynamic profile or operation script in the policy rule.

  • In the policy rule configuration, the dynamic-profile and operation-script options are mutually exclusive.

Use the following configuration statements to configure an operation script for JSRC policy rules:

To configure an operation script for JSRC policy rules:

  1. From configuration mode, enter the operation script configuration.
  2. (Optional) Enter a description for the operation script.
  3. Enter a name for the operation script.
  4. Enter the operation script arguments.

    Use the format ‘$[arg1];$[arg2];$[arg3]’.

    For example: '$[user_ipAddress];[vlan]';

    Note
    • You must enclose the arguments in quotation marks.

    • The operation script argument name must match a variable name configured for policy provisioning.

  5. From configuration mode, enter the parameters used by the operation script for policy provisioning.
  6. (Optional) Configure a value for the variable.
  7. (Optional) Configure the variable type. Variable types are mapped to parameter types.
  8. (Optional) Verify the operation script configuration.