Information Requirements for Sub-Domain Routing
You must configure addresses and ports for sub-domain routing in environments with multiple customer sub-domains. Address and port information must be provided for interfaces that enable route-cache-processing communication across MATRIXX components including the Traffic Routing Agent as a sub-domain router (TRA-RT-(SI/DR)), the Route Cache Controller (RCC) service, the Route Cache Proxy (RCP) service (if in peer-to-peer or dual network mode), and MATRIXX Engine. If Network Enabler is also installed, it uses the same route-cache processing configurations for performing sub-domain routing as the TRA-RT-(SI/DR).
Required Information for TRA-RT-(SI/DR) Configuration
TRA-RT-(SI/DR) Configuration Information Required lists the information that you must obtain in advance to configure the RCC and the RCP when deploying a TRA-RT-(SI/DR) HA pair that performs sub-domain routing.
| Item | Description |
|---|---|
| Information for configuring the TRA-RT-(SI/DR) | The IP address to be used for sub-domain-site-independent Diameter service and
sub-domain-site-independent SubMan MDC service. This IP address applies to the TRA-RT-(SI/DR) virtual servers that handle sub-domain routing. |
| Information for configuring the TRA-RT-(SI/DR) | The IP address the TRA-RT-(SI/DR) service uses for sending messages to the RCC. When running the RCC as a redundant pair, the IP address is set to the RCC-service VIP (the VIP used for high availability of the RCC service). To view an example of where you configure the VIP address/port connection information in both the RCC setup and the TRA-RT-(SI/DR) setup, see the discussion about VIP setup for RCC configuration in the reference architecture documentation in Installation and Configuration. |
Required Information for RCC Configuration
You will need to obtain the following information in advance in preparation for configuring a RCC in an environment where sub-domain routing is performed.
Required Information for RCC Configuration lists the information that you must obtain in advance to configure the RCC to communicate with the RCP using its main Route Cache Agent (RCA). The RCC main RCA communicates with the RCP upstream RCA.
| Item | Description |
|---|---|
| Information for configuring the Route Cache. | The size to set (maximum number of entries)
for your
sessions and
subscribers route-cache tables (per your
estimations for how large the tables must be for your business and subscriber
base).
|
Information for configuring the RCC main RCA. |
For the RCA instance on the RCC that handles its main processing (main
RCA), its:
|
Information for configuring the RCC standby RCA. |
(Required for local redundancy) The local IP address and the local server port of the RCA
instance on the RCC that handles pointing to its local (same site)
peer. A |
Information for configuring the RCC intersite RCA. |
(Required for inter-site redundancy) The local IP address and the local server port of
the RCA instance on the RCC that handles pointing to its inter-site
peer. An |
Information for configuring the RCC l1 RCA. |
(Required for deployments using RCC-L1s) The local IP address and the local server
port of the RCA instance on the RCC-L1. You must set the RCC
network mode for the service to
|
| Information for configuring the RCC. | The RCC network mode. When sub-domain routing is in peer-to-peer network mode, this
must be |
| Information for configuring the RCC. | When in client-server mode the VIP address and port number of the TRA-RT external route cache virtual server. |
| Information for configuring the RCC. | The IP address of the RCP upstream RCA, for each RCP that the RCC is to serve. When running the RCP as a redundant pair, this is the virtual-server/IP (VIP) address that is provisioned for the RCP upstream RCA. |
Required Information for RCP Configuration
Required Information for RCP Configuration lists the information that you need to obtain in advance to configure an RCP that communicates with the RCC and MATRIXX Engine.
In peer-to-peer network mode, the RCP communicates with the RCC using its upstream RCA, and communicates with the Engine processing blades using its downstream RCA. Each Engine processing blade in an engine communicates with the RCP using its own RCA.
| Item | Description |
|---|---|
| Information for configuring the RCP | The local IP address of the RCP upstream RCA. |
| Information for configuring the RCP | The local server port of the RCP upstream RCA. |
| Information for configuring the RCP | (If applicable) The virtual-server/IP (VIP) address that is provisioned for the RCP
upstream RCA. When running the RCP as a redundant pair, a VIP must be provisioned for high availability of the RCP service. |
| Information for configuring the RCP | The local IP address of the RCP downstream RCA. |
| Information for configuring the RCP | The local server port of the RCP downstream RCA. |
| Information for configuring the RCP | (If applicable) The virtual-server/IP (VIP) address that is provisioned for the RCP
downstream RCA. When running the RCP as a redundant pair, a VIP must be provisioned for high availability of the RCP service. |
| Information for configuring the RCC | The IP address of the RCC main RCA, or if applicable, the virtual-server/IP (VIP) address that is provisioned for the RCC main RCA. |
| Information for configuring the RCC | The server port of the RCC main RCA. |
| Information for configuring MATRIXX Engine | For each processing blade in the engine that the RCP is to serve, the IP address of the
processing blade RCA. This is the network interface on the processing blade that handles its RCA traffic. create_config.info question:
|
| Information for configuring MATRIXX Engine | The listening port of the RCA on each processing blade. The same port is used on all
processing blades in all engines.
create_config.info question:
|
Required Information for MATRIXX Engine Configuration
Required Information for Engine Configuration lists the information you must obtain in advance to configure a MATRIXX Engine in an environment where sub-domain routing is performed.
Each engine processing blade in an engine communicates with the RCP using its own RCA. The RCP communicates with the Engine processing blades using its downstream RCA.
| Information Item | Description |
|---|---|
| RCP downstream RCA listening port. | The listening port of the RCP downstream RCA. create_config.info
question: |
| Information for configuring the Engine | The route cache network mode. create_config.info question:
|
| Information for configuring the Engine | The port on which the route cache agent listens in peer-to-peer network
mode. create_config.info question:
|
| Information for configuring the Engine | The port on which the route cache agent listens in server network
mode. create_config.info question:
|
| Information for configuring the Engine | For each processing blade in the engine, the IP address of the processing blade RCA.
This is the network interface on the processing blade that handles its RCA traffic. create_config.info question:
|
| Information for configuring the Engine | The local listening port of the RCA on each processing blade. The same port is used on
all processing blades in all engines.
create_config.info question:
|
| Information for configuring the Engine | For each engine, the IP address the processing blades use for sending messages to the
RCP. When running the RCP as a redundant pair, this is the VIP for high availability of the RCP service. If the RCP and the processing blades are collocated, this is the virtual-server/IP (VIP) address that is provisioned for the RCP downstream RCA. Each processing-blade RCA uses this VIP to communicate with the RCP. create_config.info question:
When not running the RCP as a redundant pair, this is the regular IP address on the RCP. |
The following questions are prompted when running the create_config.py script
on the engine that is associated with sub-domain route processing. The questions
shown are for an example environment that has three engines communicating with a RCC
in peer-to-peer network mode.
Do you want to use a Traffic Routing Agent (TRA) for sub-domain routing (y/n)?y
TRA_RouteCacheController 1:What is the listener's port?4090
What is the engines' route-cache network mode?p2p
What port number do you want to use for the Route Cache Agent P2P listener that runs on a logical blade?4090
Site Main:Server 1:What is the local IP address of the data network plane?10.10.174.53
Site Main:Server 2:What is the local IP address of the data network plane?10.10.174.54
Site Main:Server 9:What is the local IP address of the data network plane?10.10.174.61
Site Dr:Server 1:What is the local IP address of the data network plane?10.10.184.53
Site Dr:Server 2:What is the local IP address of the data network plane?10.10.184.54
Site Dr:Server 9:What is the local IP address of the data network plane?10.10.184.61
Site THIRD:Server 1:What is the local IP address of the data network plane?10.10.126.81
Site THIRD:Server 2:What is the local IP address of the data network plane?10.10.126.82
Site THIRD:Server 3:What is the local IP address of the data network plane?10.10.126.83
Engine 1:What is the VIP address used by this engine's blades to communicate with the Route Cache Controller (RCC)?10.10.174.120
Engine 2:What is the VIP address used by this engine's blades to communicate with the Route Cache Controller (RCC)?10.10.189.120
Engine 5:What is the VIP address used by this engine's blades to communicate with the Route Cache Controller (RCC)?10.20.189.121
What port number do you want to use for the Route Cache Agent listener that runs on a logical blade?4090