Configure GigaVUE‑FM High Availability in VMware NSX-T Manager

GigaVUE-FM High Availability group can be configured in VMware NSX-T Manager in which a minimum of three GigaVUE-FM instances are launched and deployed in the VMware ESXi and managed by VMware NSX-T Manager. Refer to the GigaVUE Cloud Suite for VMware—GigaVUE V Series Guide for details on how to deploy GigaVUE‑FM in VMware NSX-T.

Before configuring HA in VMware NSX-T Manager, you must ensure the following:

  • The three GigaVUE‑FM instances must be in the same VMware NSX-T Manager and must be reachable to each other.
  • GigaVUE-FM has two interfaces, one is for VMware ESXi and the other one is for VMware NSX-T. The internal address of GigaVUE‑FM must be assigned at the time of configuring GigaVUE-FM in VMware NSX-T Manager and the external address of GigaVUE-FM must be assigned at the time of configuring GigaVUE-FM in VMware ESXi platform:
    • Internal IP Address (Private/Local IP): Reachable only within the private Network.
    • External IP Address (Public/Floating IP): Reachable from user network.

Note:  External IP address is optional. If the internal IP address is accessible from the user network, then you can exclude the external IP address.

The process of configuring a High Availability group in VMware NSX-T Manager is similar to the existing configuration steps described in GigaVUE‑FM High Availability. When configuring FM HA group in VMware NSX-T Manager:

  • Use the internal IP address for communication between the GigaVUE-FMs and to configure the HA.
  • Use the external IP address for accessing the GigaVUE-FM HA from outside the internal network.

Note:  Use of Virtual IP address and IPv6 address is not supported in GigaVUE‑FM HA in VMware NSX-T Manager.

Disassemble GigaVUE-FM Instances in VMware NSX-T Manager

To disassemble the GigaVUE-FM instances in a High Availability group, refer to the Disassemble GigaVUE‑FM High Availability Group section for details.

After the GigaVUE‑FM instances in the High Availability group are disassembled, the GigaVUE‑FM instances will be restored to the default configuration. However, you must ensure to delete the fabric nodes on the monitoring domains launched by GigaVUE‑FM on the respective tenants.