[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]

SDX 6.4.x Solutions Guide > Using PCMM Policy Servers > Configuring the JPS

Configuring the JPS

You can modify the JPS configuration by using JPS Administration or by editing the configuration files. With either method, any configuration changes will be applied within 15 seconds.

You can configure the logging destinations and JPS interfaces on the JPS Configuration page of JPS Administration or in the etc/config.properties file. We recommend using JPS Administration unless you need to configure more than the default number of logging destinations or RKS pairs and their associated application managers (see Modifying the JPS Configuration Using the Configuration File).

You can configure the subscriber configuration, which maps a subscriber address to the CMTS address, on the Subscriber Configuration page of JPS Administration or in the etc/cmtsIpAddresses.txt file, We recommend using JPS Administration.

The tasks to configure the JPS for a cable network environment are:

  1. Modifying the JPS Configuration
  2. Modifying the Subscriber Configuration

In addition to configuring the JPS, you might need to perform these tasks:

  1. Configuring the SAE to Interact with the JPS
  2. Using the NIC Resolver

Modifying the JPS Configuration

To modify the JPS configuration:

  1. Start JPS Administration (see Accessing JPS Administration).
  2. In the navigation pane, expand Configuration, and click JPS.

The JPS Configuration page appears.
  1. Change the current JPS configuration using the parameter descriptions in the following sections:
  1. Click Apply at the bottom of the page.

You must edit the etc/config.properties file to configure more than the default number of logging destinations or RKS pairs and their associated application managers (as part of the policy server to RKS interface configuration). See Modifying the JPS Configuration Using the Configuration File.

Specifying Policy Server Identifiers in Messages

To configure the policy server identifier so that the JPS can be identified in messages sent to CMTS devices, modify the policyServerId parameter on the JPS Configuration page. To configure the JPS so that the policy server identifier is specified in messages sent to the RKS, modify the usePsIdInGateCmds parameter on the JPS Configuration page.

policyServerId

usePsIdInGateCmds

Configuring Logging Destinations

By default, the JPS has four logging destinations. To configure the logging destinations, modify the following parameters in the Logging section of the JPS Configuration page, where <loggerName> is a string that groups parameters for the logging destination. To configure more than four logging destinations, you must edit the etc/config.properties file (see Modifying the JPS Configuration Using the Configuration File).

For more information about logging, see SDX Monitoring and Troubleshooting Guide, Chapter 2, Configuring Logging for SDX Components.

Logger.<loggerName>.class

If you do not fill in this field, the logging destination is disabled, and no logging is performed.

Logger.<loggerName>.filter

For more information about defining filters, see Specifying Categories and Severity Levels for Event Messages in the SDX Monitoring and Troubleshooting Guide, Chapter 2, Configuring Logging for SDX Components.

Logger.<loggerName>.filename

Logger.<loggerName>.maxsize

Logger.<loggerName>.altfile

Logger.<loggerName>.stream

Logger.<loggerName>.hostname

Logger.<loggerName>.facility

Logger.<loggerName>.format

The fields available for events are:

Specifying Connections to the Application Managers

To configure the application manager-to-policy server interface (PKT-MM3) so that the policy server can communicate with application managers, modify the following parameters in the Application Manager Interface section of the JPS Configuration page.

pepId

listenAddress

Specifying Connections to RKSs

To configure the policy server-to-RKS interface (PKT-MM4) so that policy events can be sent to the RKS, modify the following parameters in the RKS Interface section of the JPS Configuration page. As part of the configuration, you can configure RKS pairs (see Configuring RKS Pairs) and their associated application managers (see Configuring RKS Pairs for Associated Application Managers).

elementId

Plugin.radius.local.address

Plugin.radius.local.port

Plugin.radius.local.retryInterval

Plugin.radius.local.timeout

Plugin.radius.feid.msoData

Plugin.radius.feid.msoDomainName

Configuring RKS Pairs

By default, the JPS has four RKS pairs. To configure the RKS pair, modify the following parameters, where <rksPairName> is a string that identifies the RKS pair. All parameters that share the same <rksPairName> configure the connection to that RKS pair. Any configured RKS pair can be used as the value for the Plugin.radius.defaultRksPair or the Am.<amName>.rksPair parameters. To configure more than four RKS pairs, you must edit the etc/config.properties file (see Modifying the JPS Configuration Using the Configuration File).

NOTE: When running more than one JPS in a group to provide redundancy, all the JPSs in that group must have same RKS pair configuration (including the default RKS pair and any configured RKS pairs associated with a specific application manager).


Plugin.radius.defaultRksPair

RksPair.<rksPairName>.primary.address

RksPair.<rksPairName>.primary.port

RksPair.<rksPairName>.secondary.address

RksPair.<rksPairName>.secondary.port

Configuring RKS Pairs for Associated Application Managers

By default, the JPS has four associated application managers. To configure the associated application manager, modify the following parameters, where <amName> is a string that groups parameters for the associated application manager. All parameters that share the same <amName> configure the RKS pair to which events associated with a specific application manager are sent. To configure more than four associated application managers, you must edit the etc/config.properties file (see Modifying the JPS Configuration Using the Configuration File).

Am.<amName>.id

Am.<amName>.rksPair

Am.<amName>.trusted

If an application manager is trusted by the JPS and it specifies an RKS pair as part of a gate-set message, the JPS uses the RKS pair supplied by the application manager instead of using the one specified by the Am.<amName>.rksPair parameter (which might not be defined in the JPS configuration).

However, the RKS pair specified by the application manager is used only if the RKS pair exists in the JPS configuration. If the application manager specifies an RKS pair that does not exist in the JPS configuration, the default RKS pair (specified by the Plugin.radius.defaultRksPair parameter) is used.

Specifying Connections to CMTS Devices

To configure the policy server-to-CMTS interface (PKT-MM2) so that the policy server can communicate with CMTS devices, modify the following parameters in the CMTS Interface section of the JPS Configuration page.

localAddress

pepIpAddresses

keepAliveInterval

syncDespiteUnreachablePep

syncDespitePreI03Pep

useSsqSscWithPreI03Peps

Modifying the JPS Configuration Using the Configuration File

You can modify the general JPS configuration using either JPS Administration or the /opt/UMC/jps/etc/config.properties file. However, you must use the config.properties file to configure more than the default number of logging destinations, RKS pairs, or associated application managers.

To configure the JPS using the configuration file:

  1. On the server host, log in as root or as an authorized nonroot admin user.
  2. With a text editor, edit the etc/config.properties file.

See Configuring Logging Destinations for parameter descriptions.

See Configuring RKS Pairs for parameter descriptions.

See Configuring RKS Pairs for Associated Application Managers for parameter descriptions.

  1. Save the file.

Any configuration changes made in the etc/config.properties file will appear in JPS Administration.

Modifying the Subscriber Configuration

To locate the CMTS device associated with a subscriber, the JPS maps the subscriber IP address in a message to the CMTS IP address to which the message must be delivered.

This mapping is obtained from the local configuration file (etc/cmtsIpAddresses.txt) and specifies the subscriber IP pools associated with CMTS devices.

You can modify the subscriber configuration by:

We recommend using JPS Administration.

Using JPS Administration

To modify the subscriber configuration using JPS Administration:

  1. Start JPS Administration (see Accessing JPS Administration).
  2. In the navigation pane, expand Configuration, and click Subscriber.

The Subscriber Configuration page appears.
  1. You can add, modify, or delete the CMTS device.
  1. To add a CMTS device, click Add CMTS.

The Create Subscriber IP Pools pane appears.

Edit the values in the fields on the Create Subscriber IP Pools pane. See Subscriber IP Pool Fields.

Click Add after entering the subscriber IP pool information.

Click Save Changes at the bottom of the page.

  1. To modify a CMTS device, click Edit in the row for the CMTS device.

The Edit Subscriber IP Pools pane appears.

Click Add after entering the subscriber IP pool information. Edit or accept the values in the fields on the Edit Subscriber IP Pools pane. See Subscriber IP Pool Fields.

Click Delete to remove existing subscriber IP pool information. The subscriber IP pool is removed without confirmation.

Click Save Changes at the bottom of the page.

  1. To delete a CMTS device, click Delete in the row for the CMTS device.

The CMTS device is removed without confirmation.

Subscriber IP Pool Fields

You can modify these fields for the subscriber IP pool information.

CMTS Name

CMTS IP Address

Start IP Address

End IP Address

Network Address

Mask Length

Subnet IPs Excluded From Pool

Using the Configuration File

To modify the subscriber configuration using the configuration file:

  1. On the server host, log in as root or as an authorized nonroot admin user.
  2. With a text editor, edit the /opt/UMC/jps/etc/cmtsIpAddresses.txt file by adding, modifying, or deleting lines.

Each line contains the mapping for a CMTS device to which the JPS can connect, in the format <cmts> = <subscriber IP pools>.

For example, a CMTS with an IP address of 10.10.10.10 that is used by subscribers whose IP addresses are in the 24-bit subnet 192.168.1.0/24 or in the IP address range starting with 192.168.3.1 and ending with 192.168.3.254 would have the following line in the etc/cmtsIpAddresses.txt file: 

10.10.10.10 = ({192.168.1.0/24}[192.168.3.1 192.168.3.254])

We recommend prepending a comment that identifies the CMTS device name in the format:

# cmts.name = <cmts name>

For example: 

# cmts.name = example1 

10.10.10.10 = ({192.168.1.0/24}[192.168.3.1 192.168.3.254])

If you do not provide the CMTS name as a comment in the configuration file, JPS Administration leaves the CMTS Name field blank. However, JPS Administration will prompt you for the CMTS name if you modify this CMTS device.

  1. Save the file.

Any configuration changes made in the etc/cmtsIpAddresses.txt file will appear in JPS Administration.

Configuring the SAE to Interact with the JPS

You must configure the SAE as an application manager to allow it to interact with PCMM-compliant policy servers. The policy server acts as a policy decision point that manages the relationships between application managers and CMTS devices. Policy servers that manage the same group of CMTS devices are grouped together and are simultaneously active. The policy server group provides a way for the SAE to communicate with any CMTS device that is managed by a policy server in the policy server group. To provide redundancy, the SAEs are grouped in an SAE community that connects to a policy server group. Only one of the SAEs in the SAE community is active. The active SAE establishes connections to all the policy servers in the policy server group. The active SAE will fail over to a redundant SAE only when it loses the connection to all the policy servers in the policy server group. State synchronization enables the SAE to synchronize its state with all the CMTS devices connected to a policy server group.

The tasks to configure the SAE as an application manager are:

Specifying Application Managers for the Policy Server

To specify the SAE community that connects to a policy server group, you need to add an application manager group object to the directory.

To add an application manager group with SDX Admin:

  1. In the navigation pane, highlight o=Network, and right-click.
  2. Select New > ApplicationManagerGroup.

The New ApplicationManagerGroup dialog box appears.

  1. In the New ApplicationManagerGroup dialog box, enter the name of the application manager group, and click OK.

The name of the group appears in the navigation pane, and information about the group appears in the ApplicationManagerGroup pane.
  1. Configure the parameters in the Main Tab.
  2. Click Save in the ApplicationManagerGroup pane.

Description

Application Manager Tag

The SAE constructs the AMID value by concatenating two fields: Application Manager Tag and Application Type. The Application Type value is obtained from a service during activation. For more information about the Application Type field, see Specifying Application Manager Identifiers for Policy Servers.

Connected SAE

PDP Type

If you do not fill in this field, the device driver ignores this application manager group.

PDP Group

Local Address Pools

The IP pool syntax has the following format:

([<ipAddressStart> <ipAddressEnd>] |
{<ipBaseAddress>/(<mask> | <digitNumber>)(,<ipAddressExclude>)*})

You can use spaces in the syntax only to separate the first and last explicit IP addresses in a range.

Managing SAE IOR

Specifying Application Manager Identifiers for Policy Servers

To configure the AMID so that the application manager (such as the SAE) can be identified in messages sent to and from the policy server, the SAE constructs the AMID value by concatenating two fields: Application Manager Tag and Application Type. The Application Manager Tag value is obtained from the specification of application managers for policy servers. The Application Type value is obtained during service activation from the specification of the PCMM Application Type value when you configure normal value-added services. For more information about configuring services, see Adding a Normal Value-Added Service in SDX Services and Policies Guide, Chapter 1, Managing Services.

PCMM Application Type

The SAE constructs the AMID value by concatenating two fields: Application Manager Tag and PCMM Application Type. For more infomation about the Application Manager Tag field, see Specifying Application Managers for the Policy Server.

Adding Objects for Policy Servers to the Directory

To communicate with policy servers, the SAE creates and manages pseudointerfaces that it associates with a policy decision point object in the directory. Each policy server in the SDX network must appear in the directory as a policy decision point object.

To add a policy server to the directory with SDX Admin:

  1. In the navigation pane, select o=Network, and right-click.
  2. Select New > PolicyDecisionPoint.

The New PolicyDecisionPoint dialog box appears.

  1. In the New PolicyDecisionPoint dialog box, enter the name of the policy server, and click OK.

The name of the policy server appears in the navigation pane, and information about the policy server appears in the PolicyDecisionPoint pane.
  1. Set the parameters in the Main tab of the PolicyDecisionPoint pane.
  2. Click Save in the PolicyDecisionPoint pane.
  3. Create an SAE community for the policy servers. See Specifying Application Managers for the Policy Server.

Description

PDP Address

PDP Type

If you do not fill in this field, the device driver ignores this policy server.

PDP Group

Configuring Initialization Scripts

When the SAE establishes a connection with a policy server, it runs an initialization script to customize the setup of the connection.

To use SDX Configuration Editor to configure initialization scripts for the SAE:

  1. In the navigation pane, select the SAE object for which you want to configure an initialization script.
  2. Select the Router tab.

The Router pane appears.

  1. In the Router Scripts area of the Router pane, enter the name of the initialization script in the PCMM Script property.

PCMM Script

Enabling State Synchronization

State synchronization is achieved when the SAE is required to communicate with the policy server over the COPS connection. To enable state synchronization with policy servers, you can specify these properties for the PCMM device driver in the Router tab of SDX Configuration Editor.

Disable Full Sync

Disable I03 Policy

Session Recovery Retry Interval

Using the NIC Resolver

If you are using the NIC to map the subscriber IP address to the SAE, you need to configure a NIC host. The NIC system uses IP address pools to map IP addresses to SAEs. You configure the local address pools in the application manager configuration for a policy server group. These pools are published in the NIC. The NIC maps subscriber IP addresses in requests received through the portal or Advanced Services Gateway to the policy server group that currently manages that CMTS device. For information about configuring the SAE for policy servers, see Specifying Application Managers for the Policy Server.

The OnePopPcmm sample configuration data supports this scenario for a PCMM environment in which you use the assigned IP subscriber method to log in subscribers and in which you use the NIC to determine the subscriber's SAE. The OnePopPcmm configuration supports one point of presence (POP). NIC replication can be used to provide high availability. The realm for this configuration accommodates the situation in which IP pools are configured locally on each application manager group object.

The resolution process takes a subscriber's IP address as the key and returns a reference to the SAE managing this subscriber as the value.

The following agents collect information for resolvers in this realm:

You can access the OnePopPcmm configuration in either SDX Admin or SDX Configuration Editor.

For more information about configuring the NIC, see SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 5, Locating Subscriber Information.

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]