When Subnet Originating Requests is enabled, the Real Server sees traffic originating from 10.20.20.21 (LoadMaster eth1 address) and responds correctly in most scenarios. In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B, Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup. In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed.

It is best practice to enable the Subnet Originating Requests option globally. 4.1 Enable Subnet Originating Requests Globally Refer to the sections below for details on some recommended global settings. Site Servers can be leveraged when multiple site reliability is required as illustrated in the diagram. PaperCut consists of several print server roles including an Application Server, Print Server, and Site Server. If needed, you can make changes to any of the VS settings after using the template.ĭownload released templates from the following page: LoadMaster Templates.įor more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the Kemp Documentation page. You can remove templates after use and this will not affect deployed services. These steps are covered in the document, if needed. For some workloads, additional manual steps may be required such as assigning a certificate or applying port following. You can use the template to easily create the required VSs with the recommended settings. You can install this template to help create Virtual Services (VSs) because it automatically populates the settings. Kemp has developed a template containing our recommended settings for this workload. This document is intended to be read by anyone who is interested in configuring the LoadMaster to optimize PaperCut. The Kemp Support team is available to provide solutions for scenarios not explicitly defined. This document provides the recommended LoadMaster settings used when load balancing PaperCut. The Kemp LoadMaster delivers an exceptional, cost effective, and easy to use solution which by employing High Availability (HA), Global Server Load Balancing (GSLB), intelligent load balancing, and intelligent server health checking can support an always-on application experience. With a portfolio of products such as PaperCut NG, PaperCut MF, PaperCut Hive, and PaperCut Pocket, organizations can finally take full control of all the printing infrastructure. PaperCut is a full print management solution providing simplicity, visibility, and availability. PaperCut Application Server - HTTPS 9192 Virtual Service Recommended API Settings (optional).PaperCut Application Server - HTTP 9191 Virtual Service Recommended API Settings (optional).Create the PaperCut Application Server Virtual Services.PaperCut Mobility mDNS Virtual Service Recommended API Settings (optional).Create the PaperCut Mobility mDNS Virtual Services.PaperCut Mobility DNS UDP Virtual Service Recommended API Settings (optional).PaperCut Mobility DNS TCP Virtual Service Recommended API Settings (optional).

Create the PaperCut Mobility DNS Offloaded Virtual Services.PaperCut Mobility Print - HTTP 9164 Virtual Service Recommended API Settings (optional).

PaperCut Mobility Print - HTTP 9163 Virtual Service Recommended API Settings (optional).

Create the PaperCut Mobility Virtual Services.

PaperCut Print Provider Virtual Service Recommended API Settings (optional).

Create the PaperCut Microsoft Print Server Virtual Service.

Enable Subnet Originating Requests Globally.

Papercut ng user interface