4/5/2023 0 Comments Set up kjams local network![]() ![]() For more information on Interface & WUI Migration, please see this Knowledge Base document: Migrating The WUI And Interfaces This option may be required if a migration of interfaces is desired, especially involving the migration of the management interface, where the current Global Default Gateway resides. Please see this document for allowing Administrative WUI Access over multiple interfaces: Allow Administrative WUI Access Local access (using a Client on the new interface's network, to connect to the new interface's IP directly, with no need to be routed over a Gateway) may be required. On older firmware versions, you may lose WUI access if the appropriate routing to the new interface is not pre-configured on the network level. Once you select a new interface as the Default Gateway, you will be automatically directed (as of firmware version 7.2.41.1 and greater) to configure an new Default Gateway IP Address for the new interface network. After enabling this option, you will now see the Use for Default Gateway checkbox appear on all interfaces on your LoadMaster: To allow another interface to be used as the Default Gateway, the global option (Enabled Alternate GW support) needs to be enabled first. When disabled, the Global Default Gateway will be set to eth0 by default. Enabling Non-Local Real Servers prevents the need to configure multiple local interfaces on the LoadMaster, for the respective Real Server networks. When adding a Non-Local Real Server to a Virtual Service, you will now see a checkbox labelled Allow Remote Addresses:Įnable this checkbox first, and then proceed to add your Non-Local Real Server IP Address as normal. Hence, the appropriate routing between the LoadMaster's Global Gateway and the Real Server's network must be in place beforehand. The LoadMaster will use its Global Default Gateway to communicate with the Non-Local Real Server instead. This is a Non-Local Real Server and will require the global Enable Non-Local Real Servers option to be enabled.Ī Non-Local Real Server is one that resides on a network that is not local to the LoadMaster, when the LoadMaster does not have an arm/network interface configured in the Real Server's network. When adding a Real Server to a Virtual Service and you receive the error message " Real Server not on available network", this means that the Real Server IP you are trying to add does not belong to a network that has been configured on one of the LoadMaster's interfaces. It may be required for Idle connections to remain active, without closing for some services such as Remote Desktop or Web services with payment checkouts for example. The reason for altering this option is to change the default Idle Connection Timeout for Virtual Services: The value set globally will not override any pre-existing, manually configured Idle Connection Timeout values, that were set under Standard Options on individual Virtual Services. By default, this is set to 660 seconds, while setting the value of 0, will default back to 660 seconds. This is independent from the Persistence Timeout value set on the Virtual Service, when Persistence is enabled. Sets the time (seconds) that a connection can be idle before it is closed. This option is most useful for services such as SMTP, when the LoadMaster is in a public domain and when the service requires a reverse DNS check to see if the Source IP Address sent from the LoadMaster is the same as the Mail Exchange (MX) record of the sender. If the same Real Servers are configured on multiple Virtual Services, with Server NAT enabled, then connections to that respective Virtual Service will be NATed based on the destination port, to that Virtual Service's IP Address. If using HA, the Shared IP of the interface facing the Internet will be the NATed IP Address. After setting Enabled Server NAT globally, the Use Address for Server NAT checkbox will appear on each Virtual Service under Standard Options:īy default, the LoadMaster will NAT Real Server connections to the IP of the interface designated to reach the Internet. This option allows the LoadMaster to NAT connections sourcing from the Real Servers, on route to the Internet. The described options are located on the WUI via System Configuration > Miscellaneous Options > Network Options: The purpose of this document is to outline the Global Network Options available on the LoadMaster's Web User Interface (WUI), and why you would need to change or enable these options. How to configure Kemp LoadMaster Global Network Options ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |