Load balancing for print release

In a highly available print release environment, the workflow is uninterrupted by having multiple DCEs distributed across different servers connected to a Network Load Balancer (NLB) to distribute the workload.

Network load balancing uses multiple independent servers that have the same setup, but do not work together as in a cluster setup. The NLB forwards requests to either one DCE server or another, but one server does not use the other server’s resources. Also, one resource does not share its state with other resources. In an NLB setup, all resources run at the same time, and a management layer distributes the workload across them. This process reduces the risk of any single server becoming overloaded.

The recommended load balancing method used is Layer 4 in a direct server return (DSR)/N-Path/direct routing configuration. Layer 4 load balancing uses information defined at the networking transport layer as the basis for deciding how to distribute client requests across a group of servers.

It is very important that the source IP Addresses are preserved. That is, the EQ DCE service must see the request originating from the individual MFP IP Address and not the NLB appliance.

Layer 4 load balancing forwards traffic to a specific server based upon the selected port or service. The NLB appliance sits between the MFP and the DCE server and on port 2939 for Ricoh and Lexmark for requests from the MFP, and then decides which server to send them on to.

The configuration for the NLB varies depending on the vendor and type of appliance, and must be managed by the end customer’s internal IT administrator. Refer to your the vendor’s documentation for specific NLB appliance requirements, and your Microsoft documentation for general NLB setup.