Technical overview and key features
To put it short: Radiator Load Balancer’s main function is to distribute the incoming load to the worker components of VNF. It is the primary entry point for the incoming RADIUS and Diameter messages, for which we have independent load balancers.
|Loab balancers in Radiator VNF architecture|
Our Diameter load balancer supports multicore processor architecture that makes it very effective to use. The load balancer can utilise multiple threads for processing the incoming requests concurrently. The worker thread count is configurable for the best possible performance.
Diameter load balancer has an extensive support for logging. By default, it can produce JSON and plain text log files. The JSON logs can be further integrated to Elasticsearch or other log collecting systems. These systems provide possibilities to create graphical presentations of the system data – both performance counters and log files.
Loadbalancer is very flexible, you can configure several different features, such as routing, initiator support, responder support, TCP and SCTP support, timeout, logging, and many, many more.
You can redirect the messages with Diameter Loadbalancer and use dynamic routing tables. For example, from VNF point of view, HSS can specify which server handles particular traffic. The worker then instructs the load balancer to forward traffic to the indicated server, and the load balancer modifies its dynamic routing tables to perform the forwarding. In addition, to avoid redirect loops, Radiator Loadbalancer has a detector that recognises and prevents them.
The routing decisions are based on matching the dynamic routing table against the Diameter AVPs:
Loadbalancer has a comprehensive support for failover. It prefers the active peers by default and retransmits the messages to alternative peers if one peer does not respond.
Interested to know more about Radiator Load Balancer?
If you are interested to know more about Radiator Load Balancer and Radiator VNF in general, you can contact our sales and support team at firstname.lastname@example.org . We are happy to provide more detailed information for your infrastructure.