> - Downloads
> - Configuring Connections to RKSs
> - Related Topics
> - Modifying the JPS Configuration (C-Web Interface)
> - Configuring RKS Pairs (C-Web Interface)
> - Specifying Connections to the Application Managers
> - Viewing JPS RKS Statistics with the C-Web Interface

> # Configuring Connections to RKSs

> To configure connections to RKSs:

> 1. Specifying Connections to RKSs
> 2. Configuring RKS Pairs

> ## 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 ).

> 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:

> 1. From configuration mode, access the configuration statement that configures the policy server-to-RKS interface.
>    `
>    user@host# edit slot 0 jps rks-interface
>    `
> 2. ier for RKS event origin.
>    `
>    [edit slot 0 jps rks-interface]
>    user@host# set element-id element-id
>    `
> 3. (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-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.

> 4. (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
>    `
> 5. (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-interval
>    `

>    The JPS keeps sending packets until either the RKS acknowledges the packet or the maximum timeout is reached.

> 6. (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
>    `
> 7. (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
>    `
> 8. (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
>    `
> 9. (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
>    `
> 10. (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
>     `
> 11. (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-age
>     `

>     The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.

> 12. (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
>     `
> 13. (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-age
>     `

>     The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.

> 14. (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
>     `
> 15. (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
>     `
> 16. (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
>     `
> 17. (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.

> | 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:

> 1. 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
>    `
> 2. 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-address
>    `

>    If no value is specified, the RKS pair is not defined.

> 3. (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
>    `
> 4. (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
>    `
> 5. (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
>    `
> 6. (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;

> #### Published: 2009-09-23

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.