Create Monitoring Domain
You must establish a connection between GigaVUE‑FM and your Azure environment before you can perform the configuration steps. Creating a monitoring domain in GigaVUE-FM allows you to establish a connection between your Azure environment and GigaVUE-FM. After establishing a connection, you will be able to use GigaVUE‑FM to specify a launch configuration for the G-vTAP Controllers, GigaVUE V Series Proxy, and GigaVUE V Series Nodes in the specified VNet and Resource Groups. GigaVUE‑FM connects to Azure using either an Application ID with the client secret or the MSI method of authentication. After the connection establishment, GigaVUE‑FM launches the G-vTAP Controller, GigaVUE V Series Proxy, and GigaVUE V Series 2 Node.
To create an Azure monitoring domain in GigaVUE‑FM:
- From the left navigation pane, select Inventory > VIRTUAL > Azure > Monitoring Domain. The Monitoring Domain page appears.
- In the Monitoring Domain page, click New. The Azure Monitoring Domain Configuration wizard appears.
- Enter or select the appropriate information for the monitoring domain as described in the following table.
An alias used to identify the monitoring domain.
Use V Series 2
Select Yes for V Series 2 configuration.
Traffic Acquisition Method
Select a Tapping method. The available options are:
G-vTAP: If you select G-vTAP as the tapping method, the traffic is acquired from the G-vTAP Agents installed on your standard VMs in the Resource Group or in the Scale Sets. Then the acquired traffic is forwarded to the GigaVUE V Series nodes. You must configure the G-vTAP Controller to monitor the G-vTAP Agents. None: If you use select None as the tapping method, you can select the tunnel as a source where the traffic is directly tunneled to GigaVUE V Series nodes without deploying G-vTAP Agents or G-vTAP controllers.
Note: Select the Traffic Acquisition Method as None if you wish to use Observability Gateway (
Traffic Acquisition Tunnel MTU
The Maximum Transmission Unit (MTU) is the maximum size of each packet that the tunnel endpoint can carry from the G-vTAP Agent to the GigaVUE V Series node.
For VXLAN, the default value is 1450. The G-vTAP Agent tunnel MTU should be 50 bytes less than the agent's destination interface MTU size.
Use FM to Launch Fabric
Note: You can add multiple connections in a monitoring domain. Refer to Create Azure Credentials for more information on adding multiple Application ID with Client Secret authentication credentials.
An alias used to identify the connection.
Select an Azure credential. For detailed information, refer to Create Azure Credentials.
A unique alphanumeric string that identifies your Azure subscription.
Azure region for the monitoring domain. For example, West India.
Select the Resource Groups of the corresponding VMs to monitor.
Note: This field is only available if you select G-vTAP as the Traffic Acquisition Method.
- Click Save and the Azure Fabric Launch Configuration wizard appears.