DA Topology Configuration

DA topology can be configured on the Distributed Architecture page in the Units tab. Below the Settings panel, there is a set of tables used for topology configuration. They are described in the following chapters. Every operation over DA topology is checked on the TPM and the TPM tries to lock all relevant Master and Proxy Units. If it is successful, the success is confirmed and you can continue working. Meanwhile, the operation is being distributed in an asynchronous manner to other units in topology. The result of the asynchronous part of the operation can be checked in Action Log.

If you cannot perform the topology operation due to a check error, you can select the Force option for the second try.

DA Topology Configuration - Master Units

Master units

All Master Units are listed in this table.

In the HWID column, the HWID of the unit is displayed. To show the full HWID, hover over the HWID.

Hovering the mouse over the status icon will display details about the unit status. The status is divided into these sections:

• Unit availability status - Indicates if the unit is reachable within the network.

• Unit topology status - Indicates whether the unit is correctly embedded in the distributed architecture topology and whether it can use all its functionalities, or whether its functionalities are limited.

• XML configuration status - Indicates if the configuration of the unit is consistent with the TPM.

• Installed packages' status - Indicates if the unit has installed packages with the same versions as the TPM.

In the Action column, there is a button Edit unit. This button opens the Master Unit configuration form.

In this form, the following items are present:

• Update HWID - Each unit in DA is uniquely defined by its HWID. In the unlikely event of unit failure resulting in its complete replacement, the unit HWID in DA topology must be replaced too. In this case, it is necessary to check this option and click SAVE. Then the new HWID is detected and the unit is fully initialized with the original unit’s configuration.

• Name - User-defined name of the unit. Can be set to any value.

• IP address - IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by the Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by Master Units.

• Swap priority with - Each Master Unit has a defined priority and this option can be used for swapping priority between two Master units. If the priority is swapped with the current TPM, then the second Master unit becomes a TPM after the priority swap.

The next button in the Action column opens the Remote Configuration Center (RCC). Then you can configure the particular Master unit. In its RCC, the Local configuration can be changed. Global and Master group configuration settings can be viewed but cannot be changed.

The last button in the Action column removes the role assignment from the unit so it turns the Master Unit into the Unassigned Unit.

DA Topology Configuration - Source Groups

Source groups table

In this table, all Source Groups are listed. Each Source Group can be expanded to display all contained Proxy Groups or Standalone Slave Units. In the case of Proxy Group, this can be expanded too to display its Slave Units.

Hovering the mouse over the status icon will display details about unit status. The status is divided into these sections:

• Unit availability status - Indicates if the unit is reachable within the network.

• Unit topology status - Indicates if the unit is correctly embedded in the distributed architecture topology and if it can utilize all its functionalities, or if its functionalities are limited.

• XML configuration status - Indicates if the configuration of the unit is consistent with the TPM.

• Installed packages' status - Indicates if the unit has installed packages with the same versions as the TPM.

Status icon for a source group aggregates status information from all its proxy and slave units.

In the Source groups table, there is an Action column containing several buttons. One of them is the

Assign slave units button. This button opens the Assign slave units to the source group form.

In this form, Slave Units can be assigned to all Proxy Groups in this Source Group. It is restricted that the same amount of Slave Units must be assigned to every Proxy Group. All Proxy Groups in the same Source Group must have the same number of Slave Units all the time.

Selected Slave Units can be assigned to the selected proxy group by clicking on the ASSIGN button. When the same number of Slave Units is assigned to all Proxy Groups, the new configuration can be applied by clicking on the SAVE button.

The next button in the Action column is the Assign proxy groups or Standalone slaves button. This button opens a new form Assign proxy groups or standalone slaves to the source group where new proxy groups or Standalone Slave units can be added to the Source Group. Only Proxy Groups with the same number of Slave Units can be contained in the Source Group.

The next button in the Action column is the Edit source group button. This button opens a new form Edit source group.

In this form, the Name of the Source Group can be set together with Proxy mode which can be set to Round-robin or Flow-source related. If Flow-source related mode is selected, then it is necessary to assign every flow source to a specific Slave Unit (multiple flow sources can be assigned to the same Slave Unit). The flows from the particular flow source will be exported to the selected Slave Unit. For Round-robin mode, flows from all flow sources are distributed to all Slave Units equally.

The next button in the Action column opens the Remote Configuration Center (RCC) where you can configure the particular Source Group. In its RCC, the Source group configuration can be changed. Global configuration settings can be viewed but cannot be changed.

The last button in the Action column deletes the Source Group. The Source Group must be empty before it can be deleted.

Proxy groups and standalone slaves table

If the Source Group table is expanded, then the table of Proxy groups and standalone slaves is displayed showing all Proxy Groups assigned to the Source Group. Each Proxy Group can be expanded to display its Slave Units.

In the Proxy groups and standalone slaves table, there is a HWID column, where the HWID of the unit is displayed. To show the full HWID, hover over the the HWID.

Hovering the mouse over the status icon will display details about unit status. The status is divided into these sections:

• Unit availability status - Indicates if the unit is reachable within the network.

• Unit topology status - Indicates if the unit is correctly embedded in the distributed architecture topology and if it can utilize all its functionalities, or if its functionalities are limited.

• XML configuration status - Indicates if the configuration of the unit is consistent with the TPM.

• Installed packages' status - Indicates if the unit has installed packages with the same versions as the TPM.

In the Action column, there is a button Edit unit. This button opens the Unit configuration form.

In this form, the following items are present:

• Update HWID - Each unit in DA is uniquely defined by its HWID. In the unlikely event of unit failure resulting in its complete replacement, the unit HWID in DA topology must be replaced too. In this case, it is necessary to check this option and click SAVE. Then the new HWID is detected and the unit is fully initialized with the original unit’s configuration.

• Name - The user-defined name of the unit. This can be set to any value.

• IP address - The IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by the Master Units.

• Swap priority with - Each Proxy Unit or Standalone Slave has defined priority in the scope of its Source Group. This option can be used for swapping priority between two Proxy Groups or Standalone Slaves in the same Source Group.

The next button in the Action column opens the Remote Configuration Center (RCC) where you can configure the particular Proxy or Standalone Slave unit. In its RCC, the Local configuration can be changed. Global and Source group configuration settings can be viewed but cannot be changed.

The last button in the Action column removes the Proxy Group or Standalone Slave from the Source Group.

Slave units table

If the Proxy groups and standalone slaves table is expanded, then the table of Slave units is displayed showing all Slave Units assigned to the Proxy Group.

In the Slave units table, there is a HWID column, where the HWID of the unit is displayed. To show the full HWID, hover over the HWID.

In Status column, the current status is displayed. The status can be set as follows:

• OK - Slave Unit is working properly

• Init - Slave Unit has been recently assigned a new role and is being initialized

• Resync - Slave Unit is not in a consistent state. This is a faulty state and should be fixed automatically in a few minutes. If this state persists, contact support at https://support.flowmon.com

In the Action column, there is an Edit unit button.

This button opens the Slave Unit configuration form. In this form, the following items are present:

• Update HWID - Each unit in DA is uniquely defined by its HWID. In the unlikely event of unit failure resulting in its complete replacement, the unit HWID in DA topology must be replaced too. In this case, it is necessary to check this option and click SAVE. Then the new HWID is detected and the unit is fully initialized with the original unit’s configuration.

• Name - The user-defined name of the unit. This can be set to any value.

• IP address - The IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by the Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by the Master Units.

The next button in the Action column opens the Remote Configuration Center (RCC) where you can configure the particular Slave Unit. In its RCC, the Local configuration can be changed. Global and Source group configuration settings can be viewed but cannot be changed.

The last button in the Action column removes the Slave Unit from the Proxy Group.

The add new source group button

This button opens a new form for adding a new Source Group. In this form, the name of the Source Group and Proxy mode must be defined. The Proxy mode can be set to Round-robin or Flow-source related. If Flow-source related mode is selected, then as soon as flow sources are detected in the Source Group it is necessary to assign every flow source to a specific Slave Unit using the Source Group Edit button (multiple flow sources can be assigned to the same Slave Unit). The flows from the particular flow source will be exported to the selected Slave Unit. For Round-robin mode, flows from all flow sources are distributed to all Slave Units equally.

DA Topology Configuration - Unassigned Units

Here there are two tables listing Unassigned Proxy groups and standalone slaves and Units with no role.

Proxy groups and standalone slaves

The Proxy groups and standalone slaves table shows all Proxy Groups and Standalone Slaves which are not assigned to any Source Group.

In this table, there is a HWID column, where the HWID of the unit is displayed. To show the full HWID, hover over the HWID.

Next, there is a Number of Slaves column, where the number of Slave Units in the Proxy Group is displayed. For Standalone Slaves, no number is displayed.

In the Status column, the current status is displayed. The status can be set as follows:

• Ok - Unit is working properly

• Init - Unit has been recently assigned with a new role and is being initialized

• Resync - The unit is not in a consistent state. This is a faulty state and should be fixed automatically in a few minutes. If this state persists, contact support at https://support.flowmon.com

In the Action column, there is an Assign to the source group button. This button opens a new form. In this form, you can select the Source Group and confirm by clicking SAVE.

The next button in the Action column is Edit unit. This button opens the Proxy Unit or Standalone Slave Unit configuration form.

In this form, the following items are present:

• Update HWID - Each unit in DA is uniquely defined by its HWID. In the unlikely event of unit failure resulting in its complete replacement, the unit HWID in DA topology must be replaced too. In this case, it is necessary to check this option and click SAVE. Then the new HWID is detected and the unit is fully initialized with the original unit’s configuration.

• Name - User-defined name of the unit. This can be set to any value.

• IP address - The IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by the Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by the Master Units.

The next button in the Action column opens the Remote Configuration Center (RCC) where you can configure the particular Unit. In its RCC, the Local configuration can be changed. Global configuration settings can be viewed but cannot be changed.

The last button in the Action column removes the role assignment from the unit so it turns the Unit into an Unassigned Unit.

Units

The Units table shows all units registered on the TPM that are not assigned to any role (that is, they are neither Master, Proxy, nor Slave Unit).

In this table, there is a HWID column, where the HWID of the unit is displayed. To show the full HWID, hover over the HWID.

The next button in the Action column is Edit unit. This button opens the Unit configuration form.

In this form, the following items are present:

• Update HWID - Each unit in DA is uniquely defined by its HWID. In the unlikely event of unit failure resulting in its complete replacement, the unit HWID in DA topology must be replaced too. In this case, you must check this option and click SAVE. Then, the new HWID is detected and the unit is fully initialized with the original unit’s configuration.

• Name - The user-defined name of the unit. This can be set to any value.

• IP address - The IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by the Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by Master Units.

• Role - A new role can be assigned to the unit.

The last button in the Action column deletes the unit from DA completely.

The Add new unit button

This button opens the New unit form.

In this form, the following items are present:

• Autodetect HWID - Each unit in the DA is uniquely defined by its HWID. For a new unit, it can be either provided by the user or autodetected from the new unit. In case of autodetection, the unit must be reachable from the TPM unit or using the next hop Proxy (if the new unit is configured as a Slave Unit).

• Name - The user-defined name of the unit. This can be set to any value.

• IP address - IP address of the unit. For the Master Unit, this IP address must be reachable by users and all Master Units. For the Proxy Unit, this IP address must be reachable by all Master Units. For the Slave Unit, this IP address must be reachable by the Proxy Unit from the same Proxy Group. For Unassigned Units, the IP address must be reachable by Master Units.

• Role - A new role can be assigned to the unit.

Action Log

In the Action Log tab, you can review all topology operations and check their results.

Operations on remote units can be performed asynchronously. You can check their results in this log when the particular event is expanded by using the expand button.