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
- 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.
Use the following configuration statements to specify the application manager for the policy server:
shared network application-manager-group name {description description;application-manager-id application-manager-id;connected-sae [connected-sae...];pdp-group pdp-group;local-address-pools [local-address-pools...];managing-sae-ior managing-sae-ior;}To add an application manager group:
- From configuration mode, access the configuration statement that specifies the application managers.
user@host# edit shared network application-manager-group name- (Optional) Specify information about the SAE community.
[edit shared network application-manager-group name]user@host# set description description- (Optional) Specify the unique identifier within the domain of the service provider for the application manager that handles the service session (Application Manager Tag) as a 2-byte unsigned integer.
[edit shared network application-manager-group name]user@host# set application-manager-id application-manager-id- (Optional) Specify the SAEs that are connected to the specified policy server group. This list becomes the community of SAEs.
[edit shared network application-manager-group name]user@host# set connected-sae [connected-sae...]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.
- (Optional) Specify the name of the policy server group associated with this SAE community.
[edit shared network application-manager-group name]user@host# set pdp-group pdp-group- (Optional) Specify the list of IP address pools that the specified PDP group currently manages and stores.
[edit shared network application-manager-group name]user@host# set local-address-pools local-address-poolsYou 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.
- (Optional) Specify the Common Object Request Broker Architecture (CORBA) reference for the SAE managing this policy server group.
[edit shared network application-manager-group name]user@host# set managing-sae-ior managing-sae-iorThe 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. For information about configuring initialization scripts, see Configuring Initialization Scripts.
Specifying Application Manager Identifiers for Policy Servers
The application manager identifier (AMID) identifies the application manager (such as the SAE) 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. See Specifying Application Managers for the Policy Server.
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 1, Managing Services with the SRC CLI.
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.
Use the following configuration statements to specify the policy server as a policy decision point:
shared network policy-decision-point name {description description;pdp-address pdp-address;pdp-group pdp-group;}To add a policy server to the directory with the SRC CLI:
- From configuration mode, access the configuration statement that configures the policy decision point.
user@host# edit shared network policy-decision-point name- (Optional) Specify information about the policy server.
[edit shared network policy-decision-point name]user@host# set description description- (Optional) Specify the IP address of the policy server. The SAE uses this address to establish a COPS connection with the policy server.
[edit shared network policy-decision-point name]user@host# set pdp-address pdp-address- (Optional) Specify the name of the policy server group.
[edit shared network policy-decision-point name]user@host# set pdp-group pdp-group- Create an SAE community for the policy servers. See Specifying Application Managers for the Policy Server.
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.
Use the following configuration statement to configure the initialization script:
shared sae configuration driver scripts {pcmm pcmm;}To configure initialization scripts for the SAE:
- From configuration mode, access the configuration statement that configures the initialization scripts.
user@host# edit shared sae configuration driver scripts- Specify the initialization script for a PCMM environment.
[edit shared sae configuration driver scripts]user@host# set pcmm pcmmThe script is run when the connection between a policy server and the SAE is established and again when the connection is dropped. For the JPS, we recommend setting this value to amIorPublisher.
Enabling State Synchronization
State synchronization is achieved when the SAE is required to communicate with the policy server over the COPS connection.
Use the following configuration statement to configure state synchronization:
shared sae configuration driver pcmm {disable-full-sync;disable-pcmm-i03-policy;session-recovery-retry-interval session-recovery-retry-interval;}To enable state synchronization with policy servers:
- From configuration mode, access the configuration statement that configures the PCMM device driver.
user@host# edit shared sae configuration driver pcmm- Specify whether state synchronization with the PCMM policy servers is disabled.
[edit shared sae configuration driver pcmm]user@host# set disable-full-syncWhen using other PCMM-compliant policy servers (instead of the JPS), we recommend setting this value to true.
- Specify whether PCMM I03 policies are disabled when the SAE is deployed with pre-PCMM I03 CMTS devices.
[edit shared sae configuration driver pcmm]user@host# set disable-pcmm-i03-policyWhen there are pre-PCMM I03 CMTS devices in the network, you must set this value to true.
- Specify the 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.
[edit shared sae configuration driver pcmm]user@host# set session-recovery-retry-interval session-recovery-retry-intervalWe recommend setting this value to 3600000 (1 hour) or longer.