Configure GigaVUE Fabric Components in Azure

This section provides information on how to register GigaVUE fabric components using Azure Portal or a configuration file.

Overview of Third-Party Orchestration

You can use your own Azure Orchestrator to deploy the GigaVUE fabric components instead of using GigaVUE‑FM to deploy your fabric components.

The third-party orchestration feature allows you to deploy GigaVUE fabric components using your own Azure orchestration system. These fabric components register themselves with GigaVUE‑FM with user information. Once the nodes are registered with GigaVUE‑FM, you can configure monitoring sessions and related services in GigaVUE‑FM.

You can deploy the fabric components using one of the following options:

• Manually using a configuration file.

• Use the Azure portal to launch the instances and deploy the fabric components using Custom data. Using your Custom data, the fabric components register themselves with the GigaVUE‑FM. Based on the group name and the subgroup name details provided in the Custom data, GigaVUE‑FM groups these fabric components under their respective monitoring domain and connection name.

  The heartbeat messages sent from the respective nodes help GigaVUE‑FM determine the health status of the registered nodes.

For details, refer to the following sections:

• Prerequisites
• Disable GigaVUE-FM Orchestration in Monitoring Domain
• Configure UCT-V Controller in Azure
• Configure UCT-V in Azure
• Configure GigaVUE V Series Node and GigaVUE V Series Proxy in Azure