Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Connections to RKSs (SRC CLI)

 

Specifying Connections to RKSs (SRC CLI)

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 (SRC CLI)) and their associated application managers (see Configuring RKS Pairs for Associated Application Managers (SRC CLI)).

Use the following configuration statement to configure the policy server-to-RKS interface:

To configure the policy server-to-RKS interface:

  1. From configuration mode, access the configuration statement that configures the policy server-to-RKS interface.

  2. ier for RKS event origin.

  3. (Optional) Specify the source IP address that the plug-in uses to communicate with the RKS.

    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.

  5. (Optional) Specify the time the JPS waits for a response from an RKS before it resends the packet.

    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.

  7. (Optional) Specify the MSO-defined data in the financial entity ID (FEID) attribute, which is included in event messages.

  8. (Optional) Specify the MSO domain name in the FEID attribute that uniquely identifies the MSO for billing and settlement purposes.

  9. (Optional) Specify the default RKS pair that the JPS uses unless an RKS pair is configured for a given application manager.

  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.

  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.

    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.

  13. (Optional) Specify the oldest age of outstanding Gate-Info requests.

    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.

  15. (Optional) Specify the oldest age of billing correlation ID (BCID) in cache.

  16. (Optional) Specify whether the default RKS pair is used when an application manager requests the use of an unconfigured RKS pair.

  17. (Optional) Verify your configuration.

Configuring RKS Pairs (SRC CLI)

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:

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.

  2. Specify the IP address of the primary RKS for this RKS pair.

    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.

  4. (Optional) Specify the IP address of the secondary RKS for this RKS pair.

  5. (Optional) Specify the UDP port on the secondary RKS to which the JPS sends events.

  6. (Optional) Verify your configuration.