Modifying the JPS Configuration
To modify the current JPS configuration:
- Configure general properties for the JPS, including Java heap memory, maximum number of buffered messages for CMTS and application manager destinations, and policy server identifiers.
See Configuring General Properties for the JPS.
See Specifying Policy Server Identifiers in Messages.
See Configuring Logging Destinations for the JPS.
See Specifying Connections to the Application Managers.
See Specifying Connections to RKSs.
See Specifying Connections to CMTS Devices.
Configuring General Properties for the JPS
Use the following configuration statements to configure general properties for the JPS:
slot number jps {java-heap-size java-heap-size;snmp-agent;cmts-message-buffer-size cmts-message-buffer-size;am-message-buffer-size am-message-buffer-size;}To configure general properties for the JPS:
- From configuration mode, access the configuration statement that configures the general properties.
user@host# edit slot 0 jps- (Optional) Specify the maximum amount of memory available to the Java Runtime Environment (JRE).
[edit slot 0 jps]user@host# set java-heap-size java-heap-size- (Optional) Enable the JPS to communicate with the SNMP agent.
[edit slot 0 jps]user@host# set snmp-agent- (Optional) Specify the maximum number of messages buffered for each CMTS destination.
[edit slot 0 jps]user@host# set cmts-message-buffer-size cmts-message-buffer-size- (Optional) Specify the maximum number of messages buffered for each application manager destination.
[edit slot 0 jps]user@host# set am-message-buffer-size am-message-buffer-size- (Optional) Verify your configuration.
[edit slot 0 jps]user@host#show
Specifying Policy Server Identifiers in Messages
Use the following configuration statements to configure policy server identifiers for the JPS:
slot number jps {policy-server-id policy-server-id;use-psid-in-gate-commands;}To configure policy server identifiers for the JPS:
- From configuration mode, access the configuration statement that configures the policy server identifiers.
user@host# edit slot 0 jps- (Optional) Specify the policy server identifier so that the JPS can be identified in messages sent to CMTS devices.
[edit slot 0 jps]user@host# set policy-server-id policy-server-id- (Optional) Configure the JPS so that the policy server identifier is specified in messages sent to the RKS.
[edit slot 0 jps]user@host# set use-psid-in-gate-commandsWhen the JPS is communicating only with PCMM I03 CMTS devices, the value must be true. When the JPS is communicating with any pre-PCMM I03 CMTS devices, the value must be false.
Configuring Logging Destinations for the JPS
By default, the JPS has four logging destinations.
Use the following configuration statements to configure logging destinations for the JPS:
slot number jps logger name ...slot number jps logger name file {filter filter;filename filename;rollover-filename rollover-filename;maximum-file-size maximum-file-size;}slot number jps logger name syslog {filter filter;host host;facility facility;format format;}Configuring Logging Destinations to Store Messages in a File
To configure logging destinations to store log messages in a file:
- From configuration mode, access the configuration statement that configures the name and type of logging destination. In this sample procedure, the logging destination called log2 is configured.
user@host# edit slot 0 jps logger log2 file- Specify the properties for the logging destination.
[edit slot 0 jps logger log2 file]user@host# set ?For more information about configuring properties for the logging destination, see SRC-PE Monitoring and Troubleshooting Guide, Chapter 3, Configuring Logging for SRC Components with the CLI.
- (Optional) Verify your configuration.
[edit slot 0 jps logger log2]user@host#show
file {filter !NoAckRksEvent,/info-;filename var/log/jps_info.log;rollover-filename var/log/jps_info.alt;maximum-file-size 2000000000;}Configuring Logging Destinations to Send Messages to System Logging Facility
To configure logging destinations to send log messages to the system logging facility:
- From configuration mode, access the configuration statement that configures the name and type of logging destination. In this sample procedure, the logging destination called log5 is configured.
user@host# edit slot 0 jps logger log5 syslog- Specify the properties for the logging destination.
[edit slot 0 jps logger log5 syslog]user@host# set ?For more information about configuring properties for the logging destination, see SRC-PE Monitoring and Troubleshooting Guide, Chapter 3, Configuring Logging for SRC Components with the CLI.
Specifying Connections to the Application Managers
Use the following configuration statement to configure the application manager-to-policy server interface (PKT-MM3) so that the policy server can communicate with application managers:
slot number jps am-interface {pep-id pep-id;listening-address listening-address;validate-pcmm-objects;message-max-length message-max-length;message-read-buffer-size message-read-buffer-size;message-write-buffer-size message-write-buffer-size;open-connection-timeout open-connection-timeout;}To configure the connections to the application managers:
- From configuration mode, access the configuration statement that configures the application manager-to-policy server interface.
user@host# edit slot 0 jps am-interface- (Optional) Specify the network-wide unique identifier for this JPS instance.
[edit slot 0 jps am-interface]user@host# set pep-id pep-idChanges apply only to COPS connections that are established after you make the change.
- (Optional) Specify the local IP address on which the JPS listens for incoming connections from application managers.
[edit slot 0 jps am-interface]user@host# set listening-address listening-addressChanges take effect only after you restart the JPS (see Restarting the JPS).
- (Optional) Specify whether to validate PCMM objects received from PDPs.
[edit slot 0 jps am-interface]user@host# set validate-pcmm-objects- (Optional) Specify the maximum length of incoming messages.
[edit slot 0 jps am-interface]user@host# set message-max-length message-max-length- (Optional) Specify the size of message read buffer.
[edit slot 0 jps am-interface]user@host# set message-read-buffer-size message-read-buffer-size- (Optional) Specify the size of message write buffer.
[edit slot 0 jps am-interface]user@host# set message-write-buffer-size message-write-buffer-size- (Optional) Specify the maximum time to wait for the initial PCMM messages to be exchanged after a TCP connection is established.
[edit slot 0 jps am-interface]user@host# set open-connection-timeout open-connection-timeoutThe connection is dropped when initial PCMM messages are not exchanged within this time period.
- (Optional) Verify your configuration.
[edit slot 0 jps am-interface]user@host#show
pep-id SDX-JPS;listening-address ;validate-pcmm-objects;message-max-length 204800;message-read-buffer-size 1000000;message-write-buffer-size 1000000;open-connection-timeout 5;Specifying Connections to RKSs
To configure the policy server-to-RKS interface (PKT-MM4) so that policy events can be sent to the RKS, you can configure RKS pairs (see Configuring RKS Pairs) and their associated application managers (see Configuring RKS Pairs for Associated Application Managers).
Use the following configuration statement to configure the policy server-to-RKS interface:
slot number jps rks-interface {element-id element-id;local-address local-address;local-port local-port;retry-interval retry-interval;local-timeout local-timeout;mso-data mso-data;mso-domain-name mso-domain-name;default-rks-pair default-rks-pair;pending-rks-event-max-size pending-rks-event-max-size;pending-rks-event-max-age pending-rks-event-max-age;held-decs-max-size held-decs-max-size;held-decs-max-age held-decs-max-age;bcid-cache-size bcid-cache-size;bcid-cache-age bcid-cache-age;use-default-when-am-requests-unconfigured-rks;}To configure the policy server-to-RKS interface:
- From configuration mode, access the configuration statement that configures the policy server-to-RKS interface.
user@host# edit slot 0 jps rks-interface- Specify the network-wide unique identifier for RKS event origin.
[edit slot 0 jps rks-interface]user@host# set element-id element-id- (Optional) Specify the source IP address that the plug-in uses to communicate with the RKS.
[edit slot 0 jps rks-interface]user@host# set local-address local-addressIf no value is specified and there is more than one local address, the JPS randomly selects a local address to be used as the source address.
- (Optional) Specify the source UDP port or a pool of ports that the plug-in uses to communicate with the RKS.
[edit slot 0 jps rks-interface]user@host# set local-port local-port- (Optional) Specify the time the JPS waits for a response from an RKS before it resends the packet.
[edit slot 0 jps rks-interface]user@host# set retry-interval retry-intervalThe JPS keeps sending packets until either the RKS acknowledges the packet or the maximum timeout is reached.
- (Optional) Specify the maximum time the JPS waits for a response from an RKS.
[edit slot 0 jps rks-interface]user@host# set local-timeout local-timeout- (Optional) Specify the MSO-defined data in the financial entity ID (FEID) attribute, which is included in event messages.
[edit slot 0 jps rks-interface]user@host# set mso-data mso-data- (Optional) Specify the MSO domain name in the FEID attribute that uniquely identifies the MSO for billing and settlement purposes.
[edit slot 0 jps rks-interface]user@host# set mso-domain-name mso-domain-name- (Optional) Specify the default RKS pair that the JPS uses unless an RKS pair is configured for a given application manager.
[edit slot 0 jps rks-interface]user@host# set default-rks-pair default-rks-pair- (Optional) Specify the maximum number of RKS events waiting for Gate-Set-Ack, Gate-Set-Err, Gate-Del-Ack, and Gate-Del-Err messages.
[edit slot 0 jps rks-interface]user@host# set pending-rks-event-max-size pending-rks-event-max-size- (Optional) Specify the oldest age of RKS events waiting for Gate-Set-Ack, Gate-Set-Err, Gate-Del-Ack, and Gate-Del-Err messages.
[edit slot 0 jps rks-interface]user@host# set pending-rks-event-max-age pending-rks-event-max-ageThe maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.
- (Optional) Specify the maximum number of outstanding Gate-Info requests.
[edit slot 0 jps rks-interface]user@host# set held-decs-max-size held-decs-max-size- (Optional) Specify the oldest age of outstanding Gate-Info requests.
[edit slot 0 jps rks-interface]user@host# set held-decs-max-age held-decs-max-ageThe maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.
- (Optional) Specify the size of billing correlation ID (BCID) cache.
[edit slot 0 jps rks-interface]user@host# set bcid-cache-size bcid-cache-size- (Optional) Specify the oldest age of billing correlation ID (BCID) in cache.
[edit slot 0 jps rks-interface]user@host# set bcid-cache-age bcid-cache-age- (Optional) Specify whether the default RKS pair is used when an application manager requests the use of an unconfigured RKS pair.
[edit slot 0 jps rks-interface]user@host# set use-default-when-am-requests-unconfigured-rks- (Optional) Verify your configuration.
[edit slot 0 jps rks-interface]user@host#show
Configuring RKS Pairs
By default, the JPS has four RKS pairs. All parameters that share the same RKS pair name configure the connection to that RKS pair. Any configured RKS pair can be used as the value for the default RKS pair or the RKS pair associated with a specific application manager.
Use the following configuration statement to configure the RKS pair:
slot number jps rks-interface rks-pair rks-pair-name {primary-address primary-address;primary-port primary-port;secondary-address secondary-address;secondary-port secondary-port;}
- From configuration mode, access the configuration statement that configures the RKS pair. In this sample procedure, the RKS pair called pair1 is configured.
user@host# edit slot 0 jps rks-interface rks-pair pair1- Specify the IP address of the primary RKS for this RKS pair.
[edit slot 0 jps rks-interface rks-pair pair1]user@host# set primary-address primary-addressIf no value is specified, the RKS pair is not defined.
- (Optional) Specify the UDP port on the primary RKS to which the JPS sends events.
[edit slot 0 jps rks-interface rks-pair pair1]user@host# set primary-port primary-port- (Optional) Specify the IP address of the secondary RKS for this RKS pair.
[edit slot 0 jps rks-interface rks-pair pair1]user@host# set secondary-address secondary-address- (Optional) Specify the UDP port on the secondary RKS to which the JPS sends events.
[edit slot 0 jps rks-interface rks-pair pair1]user@host# set secondary-port secondary-port- (Optional) Verify your configuration.
[edit slot 0 jps rks-interface rks-pair pair1]user@host#show
primary-address ;primary-port 1813;secondary-address ;secondary-port 1813;Configuring RKS Pairs for Associated Application Managers
By default, the JPS has four associated application managers. All parameters that share the same application manager name configure the RKS pair to which events associated with a specific application manager are sent.
Use the following configuration statement to configure the associated application manager:
slot number jps rks-interface am am-name {am-id am-id;rks-pair-name rks-pair-name;trusted;}To configure the associated application manager:
- From configuration mode, access the configuration statement that configures the RKS pair for the associated application manager. In this sample procedure, the application manager name called 1 is configured.
user@host# edit slot 0 jps rks-interface am 1- Specify the identifier of the application manager.
[edit slot 0 jps rks-interface am 1]user@host# set am-id am-idIf no value is specified, the RKS pair configuration is not defined for this application manager. If you must set trusted to true without defining the RKS pair configuration, you must specify a value for am-id and not specify a value for rks-pair-name.
- (Optional) Specify the RKS pair that the JPS will send events to when those events are triggered by gate transitions associated with the application manager specified by am-id with the same application manager name (am-name).
[edit slot 0 jps rks-interface am 1]user@host# set rks-pair rks-pair-nameIf no value is specified, the RKS pair configuration is not defined for this application manager. Use when you must set trusted to true without defining the RKS pair configuration.
- (Optional) Specify whether this application manager is a trusted network element to the JPS.
[edit slot 0 jps rks-interface am 1]user@host# set trusted- (Optional) Verify your configuration.
[edit slot 0 jps rks-interface am 1]user@host#show
Specifying Connections to CMTS Devices
Use the following configuration statement to configure the policy server-to-CMTS interface (PKT-MM2) so that the policy server can communicate with CMTS devices:
slot number jps cmts-interface {cmts-addresses [cmts-addresses...];keepalive-interval keepalive-interval;synch-despite-unreachable-pep;synch-despite-pre-i03-pep;use-ssq-ssc-with-pre-i03-pep;local-address local-address;message-max-length message-max-length;message-read-buffer-size message-read-buffer-size;message-write-buffer-size message-write-buffer-size;open-connection-timeout open-connection-timeout;connection-open-retry-interval connection-open-retry-interval;sent-message-timeout sent-message-timeout;validate-pcmm-objects;}To configure the policy server-to-CMTS interface:
- From configuration mode, access the configuration statement that configures the policy server-to-CMTS interface.
user@host# edit slot 0 jps cmts-interface- Specify the IP addresses of all the CMTS devices to which the JPS will try to connect.
[edit slot 0 jps cmts-interface]user@host# set cmts-addresses [cmts-addresses...]- (Optional) Specify the interval between keepalive messages sent from the COPS client (CMTS device) to the COPS server (the JPS). Changes apply only to COPS connections that are established after you make the change.
[edit slot 0 jps cmts-interface]user@host# set keepalive-interval keepalive-intervalA value of 0 means that no keepalive messages will be exchanged between the CMTS device and the JPS.
- (Optional) Specify whether synchronization proceeds when the JPS receives a synchronization request from an application manager (such as the SAE) and the JPS is not connected to a CMTS device to which it should be connected.
[edit slot 0 jps cmts-interface]user@host# set synch-despite-unreachable-pep- (Optional) Specify whether synchronization proceeds when the JPS receives a synchronization request from an application manager (such as the SAE) and the JPS is connected to a pre-PCMM I03 CMTS device.
[edit slot 0 jps cmts-interface]user@host# set synch-despite-pre-i03-pep- (Optional) Specify whether synchronization includes both pre-PCMM I03 and PCMM I03 CMTS devices when the JPS receives a synchronization request from an application manager (such as the SAE) and the JPS is connected to a pre-PCMM I03 CMTS device. Relevant only when at least one pre-PCMM I03 CMTS device is connected and sync-despite-pre-i03-pep is specified as true.
[edit slot 0 jps cmts-interface]user@host# set use-ssq-ssc-with-pre-i03-pep- (Optional) Specify the source IP address that the JPS uses to communicate with CMTS devices.
[edit slot 0 jps cmts-interface]user@host# set local-address local-addressIf no value is specified and there is more than one local address, a random local address is used as the source address.
- (Optional) Specify the maximum length of incoming messages.
[edit slot 0 jps cmts-interface]user@host# set message-max-length message-max-length- (Optional) Specify the size of message read buffer.
[edit slot 0 jps cmts-interface]user@host# set message-read-buffer-size message-read-buffer-size- (Optional) Specify the size of message write buffer.
[edit slot 0 jps cmts-interface]user@host# set message-write-buffer-size message-write-buffer-size- (Optional) Specify the maximum time to wait for the initial PCMM messages to be exchanged after a TCP connection is established.
[edit slot 0 jps cmts-interface]user@host# set open-connection-timeout open-connection-timeoutThe connection is dropped when initial PCMM messages are not exchanged within this time period.
- (Optional) Specify the time to wait before the JPS tries to reconnect to CMTS devices.
[edit slot 0 jps cmts-interface]user@host# set connection-open-retry-interval connection-open-retry-interval- (Optional) Specify the maximum time to wait for the sent messages to be exchanged after a TCP connection is established.
[edit slot 0 jps cmts-interface]user@host# set sent-message-timeout sent-message-timeoutThis value must be less than the held-decs-max-age and pending-rks-event-max-age values for the corresponding RKS interface.
- (Optional) Specify whether to validate PCMM objects received from PDPs.
[edit slot 0 jps cmts-interface]user@host# set validate-pcmm-objects- (Optional) Verify your configuration.
[edit slot 0 jps cmts-interface]user@host#show
cmts-addresses ;keepalive-interval 60;synch-despite-unreachable-pep;synch-despite-pre-i03-pep;local-address ;message-max-length 204800;message-read-buffer-size 1000000;message-write-buffer-size 1000000;open-connection-timeout 5;connection-open-retry-interval 60;sent-message-timeout 60;validate-pcmm-objects;