Route Cache Controller Configuration Example
When deploying Network Enablers in an environment that uses multiple sub-domains, you must confgure a Route Cache Controller (RCC) on the NE pods. The RCC maintains the local Route Cache that is used for sub-domain routing.
You configure the RCC in the rcc_base.cfg configuration file using a side loader. For information about RCC configuration properties, see the discussion about sub-domain routing in MATRIXX Installation and Upgrade.
The following example shows the minimum configuration required in the
rcc_base.cfg
file.
# Basic properties file used as input to the route-cache config generator
# utility
#
# This properties file is a starting point for Route-Cache Controller
# service configuration in client mode in Kubernetes environment.
# Some configuration parameters must be fixed in Kubernetes environment and
# marked DO NOT SET
#
# Usage instructions:
# The file consists of configuration sections specified by '[section-name]',
# key-value pairs specified by 'key = value', and comments such as this (line
# starts with '#')
# Go over the different sections, follow the instructions and set the
# appropriate parameters.
#------------------------------------------------------------------------------
# route-cache service configuration
#------------------------------------------------------------------------------
[service]
type = rcc
network_mode = client
#------------------------------------------------------------------------------
# route-cache table configuration
#------------------------------------------------------------------------------
[routecache]
# set the capacity in terms of number of records
sessions.capacity = 50000
subscribers.capacity = 10000
# if managing subscribers directly/administratively, set the following:
# admin_subscribers.capacity =
# session and subscriber identifiers maximum length in bytes
sessions.max_key_length = 128
subscribers.max_key_length = 128
# if managing subscribers directly/administratively, set the following:
# admin_subscribers.max_key_length =
# maximum route-cache checkpoint age in minutes.
# setting this to a positive value enables checkpoint age check.
# if enabled and a checkpoint's age exceeds the set value the checkpoint is
# considered invalid and will eventually get discarded
checkpoint.max_age = 0
# NOTE: This path MUST match the Persistent Volume mount path
# DO NOT SET
checkpoint.base_directory = /var/tra/rcc_data
# NOTE: This path MUST match the Persistent Volume mount path
# DO NOT SET
admin_checkpoint.base_directory = /var/tra/rcc_data
#------------------------------------------------------------------------------
# main processing Route-Cache-Agent configuration
#------------------------------------------------------------------------------
[main]
# set the local IP address of the main RCA (can be empty).
# empty address means bind-to-any
rca.address =
# set the local server port of the main RCA
rca.port = 4091
# if virtual-server/IP (VIP) is provisioned for the main RCA set the following
rca.vs.address =
# configure at least one remote peer/agent, it is tra rt's ingress IP/DNS
rca.remote.1.address = tra-ag1.matrixx.svc.cluster.local
rca.remote.1.port = 4090