Configuring the JPS
You can configure and manage the JPS by using the SRC CLI that runs on Solaris platforms and the C-series platforms. See Chapter 12, Configuring the JPS with the SRC CLI.
The tasks to configure the JPS for a cable network environment are:
In addition to configuring the JPS, you might need to perform these tasks:
You can also use SRC configuration applications to perform this task. See Configuring the SAE to Interact with the JPS on Solaris Platforms.
Configuring the SAE to Interact with the JPS on Solaris Platforms
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
- Specifying Application Manager Identifiers for Policy Servers
- Adding Objects for Policy Servers to the Directory
- Configuring Initialization Scripts
- Enabling State Synchronization
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:
The New ApplicationManagerGroup dialog box appears.
- 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.
![]()
Description
- Specifies information about the SAE community; keywords that the SDX Admin find utility uses.
- Value—Text string
- Default—No value
Application Manager Tag
- Unique identifier within the domain of the service provider for the application manager that handles the service session; used to specify the application manager identifier (AMID) that is included in all messages sent to and from the policy server.
- Value—2-byte unsigned integer
- Guidelines—This property is required.
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
- SAEs that are connected to the specified policy server group (PDP Group). This list becomes the community of SAEs.
- Value—IP address or hostname
- Guidelines—This property is required. When you modify a community, wait for passive session stores of the new community members to be updated before you shut down the current active SAE. Otherwise, a failover from the current active SAE to the new member is triggered immediately, and the new member's session store may not have received all data from the active SAE's session store.
- Default—No value
PDP Type
- Type of device that this directory object will be used to manage.
- Value—For the JPS, enter the value PCMM.
If you do not fill in this field, the device driver ignores this application manager group.
PDP Group
- Name of the policy server group associated with this SAE community.
- Value—Text string
- Guidelines—This property is required.
- Default—No value
Local Address Pools
- List of IP address pools that the specified PDP group currently manages and stores. You must configure a local address pool if you are using the NIC so that the NIC can resolve the IP-to-SAE mapping. See Using the NIC Resolver.
- Value—List of IP address pools. You can specify an unlimited number of IP address pools. You can specify either the first and last addresses in a range, or you can specify a subnet address, a subnet mask, and a list of addresses to exclude from the subnet.
The IP pool syntax has the following format:
([<ipAddressStart> <ipAddressEnd>] |
{<ipBaseAddress>/(<mask> | <digitNumber>)(,<ipAddressExclude>)*})
- <ipAddressStart>—First IP address (version 4 or 6) in a range
- <ipAddressEnd>—Last IP address (version 4 or 6) in a range
- <ipBaseAddress>—Network base address
- <mask>—Subnet mask
- <digitNumber>—Integer specifying the length of the subnet mask
- <ipAddressExclude>—List of IP addresses to be excluded from the subnet
- |—Choice of expression; choose either the expression to the left or the expression to the right of this symbol
- *—Zero or more instances of the preceding group
You can use spaces in the syntax only to separate the first and last explicit IP addresses in a range.
Managing SAE IOR
- Common Object Request Broker Architecture (CORBA) reference for the SAE managing this policy server group.
- Value—One of the following items:
- The actual CORBA reference for the SAE
- The absolute path to the interoperable object reference (IOR) file
- A corbaloc URL in the form corbaloc::<host>:8801/SAE
- Guidelines—The amIorPublisher script provides this information when the SAE connects to the policy server. If you do not select this script when configuring initialization scripts, enter a value in this field. For information about configuring initialization scripts, see Configuring Initialization Scripts.
- Default—No value
- Example—One of the following items:
- Absolute path— /opt/UMC/sae/var/run/sae.ior
- corbaloc URL—boston:8801/sae
- Actual IOR— IOR:000000000000002438444C3A736D67742E6A756E697...
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 services. For more information about configuring services, see SRC-PE Services and Policies Guide, Chapter 2, Managing Services on a Solaris Platform.
PCMM Application Type
- Unique identifier within the domain of the service provider for the application associated with a gate; used to specify the AMID that is included in all messages sent to and from the policy server.
- Value—2-byte unsigned integer
The SAE constructs the AMID value by concatenating two fields: Application Manager Tag and PCMM Application Type. For more information 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 SRC network must appear in the directory as a policy decision point object.
To add a policy server to the directory with SDX Admin:
The New PolicyDecisionPoint dialog box appears.
The name of the policy server appears in the navigation pane, and information about the policy server appears in the PolicyDecisionPoint pane.
![]()
- Set the parameters in the Main tab of the PolicyDecisionPoint pane.
- Click Save in the PolicyDecisionPoint pane.
- Create an SAE community for the policy servers. See Specifying Application Managers for the Policy Server.
Description
- Information about this policy server; keywords that the SDX Admin find utility uses.
- Value—Text string
- Default—No value
PDP Address
- IP address of the policy server. The SAE uses this address to establish a COPS connection with the policy server.
- Value—IP address
- Guidelines—This property is required.
- Default—No value
PDP Type
- Type of device that this directory object will be used to manage.
- Value—For the JPS, enter the value PCMM.
If you do not fill in this field, the device driver ignores this policy server.
PDP Group
- Name of the policy server group.
- Value—Text string
- Guidelines—This property is required.
- Default—No value
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:
- In the navigation pane, select the SAE object for which you want to configure an initialization script.
- Select the Router tab.
- In the Router Scripts area of the Router pane, enter the name of the initialization script in the PCMM Script property.
PCMM Script
- Initialization script for a PCMM environment. The script is run when the connection between a policy server and the SAE is established and again when the connection is dropped.
- Value—Name of a script
- Default—amIorPublisher
- Property name—Router.script.pcmm
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
- When the SAE is deployed with PCMM policy servers, specifies whether state synchronization with the PCMM policy servers is enabled or disabled.
- Value
- Guidelines—When using other PCMM-compliant policy servers (instead of the JPS), we recommend setting this value to true.
- Default—false
- Property name—Router.pcmm.disableStateSync
Disable I03 Policy
- When the SAE is deployed with pre-PCMM I03 CMTS devices, disable the PCMM I03 policies by setting this property to true.
- Value
- Guidelines—When there are pre-PCMM I03 CMTS devices in the network, you must set this value to true.
- Default—true
- Property name—Router.pcmm.disableI03policy
Session Recovery Retry Interval
- Time interval between attempts by the SAE to restore service sessions that are still being recovered in the background when state synchronization completes with a state-data-incomplete error. The SAE attempts to restore a service session if it receives a service modification or deactivation request for an unrecovered service session before the next interval.
- Value—Number of milliseconds in the range 0-2147483647
- Guidelines—We recommend setting this value to 3600000 (1 hour) or longer.
- Default—3600000
- Property name—Router.pcmm.backgroundSessionRecovery.retryInterval