The network telemetry feature can be used in LoadMaster High Availability (HA) mode. Before configuring the network telemetry feature in a HA pair, ensure that both LoadMasters are using the same firmware version (7.2.53 or above).

It is recommended to configure network telemetry over the LoadMaster HA shared IP address after the two LoadMasters have been placed into HA mode.

Note: The communication of flow data only occurs between the active LoadMaster of the HA pair and the configured Collector IP. The LoadMaster determines which interface to use to communicate with the Collector IP using the same process it uses for any outbound connection it originates. This is usually going to be the network interface whose subnet is a match for the collector IP, but could also be another interface if, for example, static routes are used.

To configure the network telemetry feature in HA mode, follow the steps below:

  1. Configure the two LoadMasters into HA mode. If already in HA mode, ignore this step.

    Note: For more information on how to configure the LoadMaster in HA mode, refer to the High Availablility (HA) Feature Description.

  2. If the add-on package is already installed on both the LoadMasters then:

    • Ensure that the Collector Endpoint field is empty.
    • Expand the Activate Export of Application Flow Data Per Interface section at the bottom of the page and disable all currently enabled interfaces.
    Note: While upgrading the LoadMaster firmware from version 7.2.52 or below to a newer firmware version, ensure to install the network telemetry feature. To install the network telemetry feature, go to Network Telemetry and click Install.

  3. Open the LoadMaster UI using the HA shared IP address (defined during HA configuration) and navigate to the System Configuration > Miscellaneous Options > Network Options.

  4. Disable the Enable Server NAT option. By default this option is enabled and must be disabled when using network telemetry in HA mode. Making this change on the HA shared IP address makes the change on both HA LoadMasters.

  5. Click Network Telemetry in the main menu and do the following:

    • Enter the IP address of the Collector Endpoint and click the Set Remote Address.

    • Expand the Activate Export of Application Flow Data Per Interface section and select the network interface check box for which you want to collect the flow data.

    Note: The Network Telemetry settings are propagated to both LoadMasters.

  6. Open the Collector UI and navigate to the Monitoring Center. The All Sources profile is opened by default on that screen. In few minutes, the collector starts receiving the traffic from the active LoadMaster interface IP.

    In the example screenshot below – 192.168.1.123 is the interface address of active unit of the LoadMaster HA pair.

  7. Open the active LoadMaster UI of HA pair and click the System Configuration > System Administration > System Reboot > Reboot to reboot the active LoadMaster. This moves all traffic to the standby LoadMaster which then becomes the active LoadMaster.

  8. Go back to the Collector UI and navigate to the Monitoring Center. The screen now represents the initial standby unit as an active unit. You should see the appropriate interface IP of the former standby (now active) LoadMaster appear in all sources graph in the collector Monitoring Center page.

Flowmon Collector Dashboard in LoadMaster HA mode

The Collector starts receiving the data from a LoadMaster in the HA pair. The LoadMaster is represented as a Source of Monitoring center and is named using the LoadMaster IP address from which Collector is receiving the flow data. The Collector organizes its Sources into a single Profile named All Souces. Profiles contain Channels that are used to build Chapters which are further used to build Dashboard Widgets:

Profiles > Channels > Chapters > Dashboard Widgets

As each LoadMaster is communicating with the Collector using its unique interface IP, a separate Channel for each LoadMaster is defined with in Profiles > All Sources. In comparison, if the shared IP were used, just one channel would be created.

This provides single flexibility when building Report Chapters - the building blocks for Dashboard Widgets:

  • The data set used by a Chapter is derived from a single Profile. The scope of the Chapter can be the entire Profile data set (all Channels) or can be reduced by selecting a subset of the Channels defined.

  • Because both LoadMasters are represented by their own Channels within Profiles > All Sources, a Chapter can be built using only one of the LoadMaster HA pair channels, or both depending on the user monitoring and analysis goals.