This screen provides settings related to the external network and internal network interfaces. Some important points to note about interfaces are listed below:

  • A Virtual Service can only be added to a known network or subnet. A network or subnet is considered known if there is an interface that has an IP address in that range.

  • You cannot have two interfaces on the same subnet because this can cause routing problems.

  • Do not use the same IP address on an interface and a Virtual Service. There is one exception to this rule - when using a LoadMaster on Azure.

The screen has the same information for the eth0 and eth1 Ethernet ports. The example above is for eth0 on a non–HA (High Availability) unit.

Interface Address

Within the Interface Address (address[/prefix]) text box you can specify the Internet address of this interface. When Allow Multi Interface Access is enabled in Certificates & Security > Remote Access, and you set an IP address on another interface (other than eth0), a pop-up appears asking "Would you like to enable admin WUI access for this interface?". Click OK to enable the Allow Administrative WUI Access check box. If you click Cancel, the Allow Administrative WUI Access check box remains disabled and WUI access is not granted on that interface until that option gets enabled.

Note: If Allow Multi Interface Access option is enabled and the Admin WUI interface has been changed, a restart of web access is required to detect the change of interface. To restart the web server, login to the admin console (lsetup) as bal. Navigate to the Local Admin > Web Address and select the Immediately Stop Web Server Access option and click Ok. When the page refreshes, select the Immediately Start Web Server Access option. To exit, select the return to previous menu and then select the Exit Configuration.

Cluster Shared IP address

Specify the shared IP address which can be used to access the cluster. This is also used as the default source address when using Server NAT.

Note: The clustering options are only available on LoadMasters which have a clustering license and where clustering has been configured. To add the clustering feature to your license, please contact a Progress Kemp representative. For further information on clustering, refer to the LoadMaster Clustering, Feature Description.

Use for Cluster checks

Use this option to enable cluster health checking between the nodes. At least one interface must be enabled.

Use for Cluster Updates

Select this option to use this interface to synchronize the configuration with all of the other nodes in the cluster.

Speed

By default, the Speed of the link is automatically detected. In certain configurations, this speed is incorrect and must be forced to a specific value.

Note: On AWS Elastic Network Adapter (ENA) interfaces, no speed is displayed when it cannot be read from the interface.
Note: For ENA driver interfaces, the speed displayed behaves similar to bonded interfaces in that the speed of the overall interface is the aggregate of the number of separate logical interfaces that have been defined on that interface is displayed.

Use for Default Gateway

The Use for Default Gateway check box is only available if the Enable Alternate GW support is selected in the Network Options screen. If the settings being viewed are for the default interface this option is grayed out and selected. To enable this option on another interface, go to the other interface by clicking it in the main menu on the left. Then this option is available to select. Once you select this option, the Default Gateway screen appears. Set the new default gateway. A notification displays to inform you that the default gateway has changed.

Note: If you reboot before setting the new default gateway, the gateway is removed from the configuration.

Allow Administrative WUI Access

This option is only available when the Allow Multi Interface Access check box is enabled in Certificates & Security > Remote Access.

When both of these options are enabled, the WUI can be accessed from the IP address of the relevant interface, and any Additional addresses set up for that interface.

Note: There is only one interface attached to all of these addresses so there may be issues with this unless the certificate used is a wildcard certificate. For more information on certificates, refer to the SSL Accelerated Services Feature Description.
Note: There is a maximum of 64 network interfaces that can be tracked and a maximum of 1024 total addresses where the system will listen on.

Use for GEO Responses and Requests

By default, only the default gateway interface is used to listen for and respond to DNS requests. This field gives you the option to listen on additional interfaces.

Note: This option cannot be disabled on the interface containing the default gateway. By default, this is eth0.

When this option is enabled, GEO also listens on any Additional addresses that are configured for the interface.

Export of Network Telemetry

This indicates if network telemetry monitoring is enabled or disabled for this interface (depending on what interfaces are selected on the Network Telemetry screen). For further details, refer to the Network Telemetry section.

MTU

Within the MTU field you can specify the maximum size of Ethernet frames that will be sent from this interface. The valid range is 512 - 9216.

Note: The valid range of 512 - 9216 may not apply to VLMs as the range will be dependent on the hardware the VLM is running on. It is advised to check your hardware restrictions.

Additional addresses

Using the Additional addresses field allows the LoadMaster to give multiple addresses to each interface, as aliases. This is sometimes referred to as a “router on a stick”. It allows both IPv4 and IPv6 addresses in standard IP+CIDR format, so this can also be used to do a mixed mode of IPv4 and IPv6 addresses on the same interface. Any of the subnets that are added here will be available for both virtual IPs and real server IPs.

HA

If the unit is part of a HA configuration, the following screen will be displayed when one of the interfaces is clicked.

This screen tells the user:

  • This is the Activemachine of the pair (top-right of the screen)
  • This LoadMaster is up and the paired machine is down (green and red icons)
  • The IP address of this LoadMaster
  • The HA Shared IP address. This is the IP address used to configure the pair.
  • The IP address of the paired machine
  • This interface is enabled for HA health checking
  • This interface is used as the Default Gateway
  • The speed of the link is automatically detected
  • Any alternate addresses on this interface

Creating a Bond/Team

Before creating a bonded interface please note the following:

  • You can only bond interfaces higher than the parent, so if you choose to start with eth1, you can then bond eth2, eth3 and above, but you cannot bond eth0 (unless you start with eth0)

  • Bond links first if you need VLAN tagging then add VLANs after the bond has been configured

  • To add a link to a bonded interface, any IP addressing must first be removed from the link to be added

  • Enabling the Active-Backup mode generally does not require switch intervention

  • Bonding eth0 with eth1 can lead to serious issues and is not allowed to occur

Click Interface Bonding to request the bond.

Confirm the bond creation by clicking Create a bonded interface.

Acknowledge the warning dialogs.

Using the Web User Interface (WUI) select the System Configuration > Interfaces > bndx menu option.

If you do not see the bndX interface, refresh your browser, then select the bonded interface and click the Bonded Devices button.

Select the desired bonding mode.

Add the additional interfaces to this bond.

Configure the IP and Subnet Mask on the bonded interface.

Removing a Bond/Team

Remove all VLANs on the bonded interface first; if you do not remove them they will automatically be assigned to the physical port at which the bond started.

Select the System Configuration > Interfaces > bndx menu option. If you do not see the bndX interface refresh your browser, then select the bonded interface, then click the Bonded Devices button.

Unbind each port by clicking Unbind Port, repeat until all ports have been removed from bond.

Once all child ports have been unbounded, you can unbond the parent port by clicking Unbond this interface button.

Adding a VLAN

Select the interface and then select the VLAN Configuration button.

Add the VLAN Id value and select the Add New VLAN menu option.

Repeat as needed. To view the VLANs, select the System Configuration > Network Setup menu option and expand the drop-down list.

Removing a VLAN

Note: Before removing a VLAN, please ensure that the interface is not being used for other purposes, for example as a multicast interface, WUI interface, SSH interface or a GEO interface.

To remove a VLAN select the System Configuration > Network Setup menu option and select the appropriate VLAN ID from the drop-down list.

Once selected, delete the IP and then click Set Address. Once the IP has been removed you will have the option to delete the VLAN, by clicking the Delete this VLAN button.

Repeat as needed. To view the VLANs select the System Configuration > Interfaces menu option and select the appropriate VLAN ID from the drop-down list.

Adding a VXLAN

Select the relevant interface and then click the VXLAN Configuration button.

Enter a new VXLAN Network Identifier (VNI) in the VNI text box. Enter the multicast group or remote address in the Group or Remote address text box. Click Add New VXLAN.

To modify the VXLAN, go to System Configuration > Interfaces and select the VXLAN from the drop-down list.

On this screen, the interface address of the VXLAN can be specified. The VXLAN can also be deleted from this screen.

If HA is enabled, HA parameters can be set in the VXLAN:

  • The HA Shared IP address. This is the IP address used to configure the HA pair.
  • The IP address of the partner machine
  • Specify whether or not this interface is used for HA health checking