When the LoadMaster is deployed in two or more networks, it is important to keep routing correct. This section contains some tips on best practices to ensure the LoadMaster is routing accurately.

The LoadMaster's User Interface (UI) is the central point of administration. If needed, you can change the UI interface. Often, customers set the UI to a management-specific subnet. You can configure this in Certificates & Security > Remote Access. Before setting the Allow Web Administrative Access option, ensure to set the Admin Default Gateway for the subnet that the UI is being moved to.

Note: It is critical to the security of your appliance that you use a dedicated network interface for management traffic; refer to the LoadMaster Hardening Technical Note for further details.

Changing the LoadMaster's default gateway to a different interface may be required at some point. Often using the DMZ-facing interface is the best way to configure the LoadMaster. To accomplish this, first select the Enable Alternate GW support check box in System Configuration > Miscellaneous Options > Network Options.

Once Enable Alternate GW support is enabled, you can select the appropriate interface and Use for Default Gateway can be selected. When you select this option, you are automatically redirected to a page to update the default gateway IP address.

Each Virtual Service can also be configured with its own gateway. You can do this in the Advanced Properties section of the Virtual Service modify screen. This means you can send Virtual Service responses through a gateway specific to each Virtual Service. Ensure that the gateway is within the same subnet as your Virtual Service.

In addition to configuring a gateway for each of the Virtual Services, ensure that responses are sent out on the correct interface. Enabling the Use Default Route Only check box will accomplish this. This option is also located in System Configuration > Miscellaneous Options > Network Options.

Without forcing the use of the Use Default Route Only option, this scenario can result in asymmetrical routing, which may affect users on networks directly connected to the LoadMaster who can access Virtual Services located on a different interface of the LoadMaster (particularly where a stateful firewall is used).

After you configure all of these settings and features, the LoadMaster should be able to route all traffic appropriately.