To configure 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:
- user@host# edit slot 0 jps rks-interface
- [edit slot 0 jps rks-interface]
- user@host# set element-id element-id
- [edit slot 0 jps rks-interface]
- user@host# set local-address local-address
If 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.
- [edit slot 0 jps rks-interface]
- user@host# set local-port local-port
- [edit slot 0 jps rks-interface]
- user@host# set retry-interval retry-interval
The JPS keeps sending packets until either the RKS acknowledges the packet or the maximum timeout is reached.
- [edit slot 0 jps rks-interface]
- user@host# set local-timeout local-timeout
- [edit slot 0 jps rks-interface]
- user@host# set mso-data mso-data
- [edit slot 0 jps rks-interface]
- user@host# set mso-domain-name mso-domain-name
- [edit slot 0 jps rks-interface]
- user@host# set default-rks-pair default-rks-pair
- [edit slot 0 jps rks-interface]
- user@host# set pending-rks-event-max-size pending-rks-event-max-size
- [edit slot 0 jps rks-interface]
- user@host# set pending-rks-event-max-age pending-rks-event-max-age
The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.
- [edit slot 0 jps rks-interface]
- user@host# set held-decs-max-size held-decs-max-size
- [edit slot 0 jps rks-interface]
- user@host# set held-decs-max-age held-decs-max-age
The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.
- [edit slot 0 jps rks-interface]
- user@host# set bcid-cache-size bcid-cache-size
- [edit slot 0 jps rks-interface]
- user@host# set bcid-cache-age bcid-cache-age
- [edit slot 0 jps rks-interface]
- user@host# set use-default-when-am-requests-unconfigured-rks
[edit slot 0 jps rks-interface] user@host# show
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.
![]() |
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). |
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;
- }
To configure the RKS pair:
- user@host# edit slot 0 jps rks-interface rks-pair
pair1
- [edit slot 0 jps rks-interface rks-pair pair1]
- user@host# set primary-address primary-address
If no value is specified, the RKS pair is not defined.
- [edit slot 0 jps rks-interface rks-pair pair1]
- user@host# set primary-port primary-port
- [edit slot 0 jps rks-interface rks-pair pair1]
- user@host# set secondary-address secondary-address
- [edit slot 0 jps rks-interface rks-pair pair1]
- user@host# set secondary-port secondary-port
[edit slot 0 jps rks-interface rks-pair pair1] user@host# show primary-address ; primary-port 1813; secondary-address ; secondary-port 1813;