Configure GigaVUE‑FM High Availability in OpenStack Environment

GigaVUE-FM High Availability group can be configured in an OpenStack Environment in which the three GigaVUE-FM instances are launched and deployed in the OpenStack environment. Refer to the GigaVUE Cloud Suite for OpenStack guide for details on how to deploy GigaVUE‑FM in OpenStack.

Before configuring HA in OpenStack, you must ensure the following:

  • The three GigaVUE‑FM instances must be in the same OpenStack environment and must be reachable to each other.
  • The internal and external IP addresses of GigaVUE‑FM must be assigned at the time of configuring GigaVUE-FM in OpenStack:
    • Internal IP Address (Private/Local IP): Reachable only within the private Network.
    • External IP Address (Public/Floating IP): Reachable from the user network.

The process of configuring a High Availability group in OpenStack environment is similar to the existing configuration steps described in GigaVUE‑FM High Availability. When configuring GigaVUE‑FM HA group in OpenStack:

  • 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:   The DNS egress port 53 in the OpenStack security group must be opened while creating FMHA.

Note:  Use of Virtual IP address is not supported in GigaVUE‑FM HA in OpenStack.

Disassemble GigaVUE-FM Instances in OpenStack Environment

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 Monitoring Session, Monitoring Domain and its associated fabric components launched by GigaVUE‑FM on the respective tenants.

Third Party Orchestration Support for GigaVUE-FM High Availability in OpenStack

In the OpenStack platform, you can register GigaVUE V Series Node, GigaVUE V Series Proxy, UCT-V, and UCT-V Controller using Third Party Orchestrated registration. You can register multiple (three) GigaVUE-FM IPs (comma separated without space) that are part of GigaVUE-FM HA in the configuration file used for Third Party Orchestration.

Refer to the following registration steps to register using a configuration file:

1.   Log in to the GigaVUE V Series Node or GigaVUE V Series Proxy or UCT-V Controller.
2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data.
Copy 
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <Connection Name/Alias>
    user: <Username>
    password: <Password>
    remoteIP: <IP address of the GigaVUE-FM>
    remotePort: 443

Note:  The IP addresses could be in any sequence in terms of active and standby instances.

If one of the IPs becomes unreachable because a GigaVUE-FM instance is down, GigaVUE V Series Node, GigaVUE V Series Proxy, or UCT-V Controller will register with the next available IP. GigaVUE-FM will then redirect the calls to the new active GigaVUE-FM instance, ensuring that the node registration is successfully completed with the new active instance.

GigaVUE-FM configures a notification target in the V Series Node and UCT-V Controller which includes GigaVUE-FM's IP address for RMQ communication with GigaVUE-FM. In the case of GigaVUE-FM High Availability, the active GigaVUE-FM's IP address is configured. When a switchover event occurs, the IP address of the new active GigaVUE-FM is updated in the notification target.