Configure GigaVUE Fabric Components in Azure

This section provides step-by-step 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 nodes 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 using the information provided by the user. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM.

You can either manually deploy the fabric nodes using a configuration file or you can use the Azure portal to launch the instances and deploy the fabric nodes using Custom data. Using the Custom data provided by you, the fabric nodes register itself with the GigaVUE‑FM. Based on the group name and the sub group name details provided in the Custom data, GigaVUE‑FM groups these fabric nodes under their respective monitoring domain and connection name. Health status of the registered nodes is determined by the heartbeat messages sent from the respective nodes.

Prerequisites

GigaVUE V Series Node must have a minimum of two Networks Interfaces (NIC) attached to it, a management NIC and a data NIC with Accelerated Networking enabled.

When creating a virtual machine for GigaVUE V Series Node using CLI, Management NIC and Data NIC can be attached at the time of the virtual machine creation. However, if you are using Azure GUI to create the virtual machine for GigaVUE V Series Node, then the data NIC can only be attached after creating the virtual machine. Refer to the following topics for more detailed information on how to create GigaVUE V Series Node with Management and Data NIC Attached using CLI or Azure GUI:

Create GigaVUE V Series Node with Management and Data NIC Attached using CLI

Create management NIC: 

az network nic create -g <resource group> --vnet-name <VNet Name> --subnet <Subnet name> -n <Mangement NIC Name>

Create data NIC with Accelerated Networking enabled: 

az network nic create <resource group> --vnet-name <VNet> --subnet <Subnet> -n <Data NIC> --accelerated-networking true

Create GigaVUE V Series Node virtual machine using the above NICS:

az vm create --resource-group <Resource group> --size <Standard_D4s_v4/Standard_D8S_V4> --name <GigaVUE V Series Node> --admin-username gigamon --generate-ssh-keys --image gigamon-inc:gigamon-gigavue-cloud-suite:vseries-node:5.16 --plan-name vseries-node --plan-product gigamon-gigavue-cloud-suite --plan-publisher gigamon-inc --nics <Management NIC and Data NIC>

Create GigaVUE V Series Node with Management and Data NIC Attached using Azure GUI

Enable Management NIC when creating the GigaVUE V Series Node virtual machine. Refer to Create virtual machine topic in Azure Documentation for more detailed information on how to create a virtual machine. Follow the steps given below to attach the data NIC:

  1. Select the GigaVUE V Series Node virtual machine from the Resources Page.
  2. Stop the Virtual Machine using the Stop button.
  3. Navigate to Setting > Networking from the left navigation pane. The Networking page appears.
  4. In the Networking page, click Attach network interface. Select an existing network interface for Data NIC and click OK.
  5. To enable accelerated networking, refer to Manage Accelerated Networking through the portal.
  6. Start the Virtual Machine.

Getting Started

GigaVUE fabric components deployed through a third-party orchestrator, can be registered under GigaVUE‑FM in two ways.

  • Register under Azure Monitoring Domain
  • Register under AnyCloud Monitoring Domain
  • Deployment of G-vTAP Controller, GigaVUE V Series Node, and GigaVUE V Series Proxy through a third-party orchestrator is supported only on Linux platform.
  • Deployment of G-vTAP Agent through a third-party orchestrator is supported on Linux and Windows platforms. Refer to Linux G-vTAP Agent Installation and Windows G-vTAP Agent Installation for detailed information.

To register fabric nodes under Azure monitoring domain:

  1. Create a monitoring domain in GigaVUE-FM. Refer to Create a Monitoring Domain for detailed instructions.

  2. In the Azure Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you are going to configure the fabric components in Azure Orchestrator.

    • When configuring G-vTAP Controller, select G-vTAP as the Traffic Acquisition Method.
    • When you select Tunnel as your Traffic Acquisition Method, G-vTAP Agent and G-vTAP Controller registration are not applicable.
    • When you deploy GigaVUE V Series Nodes or G-vTAP Controllers using 3rd party orchestration, you cannot delete the monitoring domain without unregistering the GigaVUE V Series Nodes or G-vTAP Controllers.
  3. After creating your monitoring domain, you can deploy your fabric components through Azure Portal.

To register fabric nodes under AnyCloud monitoring domain:

  1. If you don't create a monitoring domain in GigaVUE‑FM with the same monitoring domain name and connection name as given in your custom data, then GigaVUE‑FM automatically creates a monitoring domain under AnyCloud and your fabric components get deployed under that monitoring domain.
    • In this case, the Traffic Acquisition Tunnel MTU is set to the default value of 1500. To edit the Traffic Acquisition Tunnel MTU, select the monitoring domain and click on the Edit Monitoring Domain option. Enter the Traffic Acquisition Tunnel MTU value and click Save.
    • Before deploying the monitoring session ensure that the appropriate Traffic Acquisition Tunnel MTU value is set. Otherwise, the monitoring session must be un-deployed and deployed again.

In your Azure Portal, you can configure the following GigaVUE fabric components:

Configure G-vTAP Controller in Azure

You can configure more than one G-vTAP Controller in a monitoring domain.

To register G-vTAP Controller in Azure Portal, use any one of the following methods.

Register G-vTAP Controller during Virtual Machine Launch

In your Azure portal, to launch the G-vTAP Controller init virtual machine and register G-vTAP Controller using custom data, follow the steps given below:

  1. In the Virtual machines page of the Azure Portal, select Create then Virtual machine. Then Create a Virtual Machine Page appears. For detailed information, refer to Create virtual machine topic in Azure Documentation.
  2. On the Advanced tab, enter the Custom Data as text in the following format and deploy the virtual machine. The G-vTAP Controller uses this custom data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM.
    #cloud-config
    write_files:
     - path: /etc/gigamon-cloud.conf
     owner: root:root
     permissions: '0644'
     content:
         Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the GigaVUE-FM>
    	remotePort: 443

The G-vTAP Controller deployed in your Azure portal appears on the Monitoring Domain page of GigaVUE-FM.

 

Register G-vTAP Controller after Virtual Machine Launch

To register G-vTAP Controller after launching a Virtual Machine using a configuration file, follow the steps given below:

  1. Log in to the G-vTAP Controller.
  2. Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following custom data.
    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the GigaVUE-FM>
    	remotePort: 443
  3. Restart the G-vTAP Controller service.
    $ sudo service gvtap-cntlr restart

The deployed G-vTAP Controller registers with the GigaVUE-FM. After successful registration, the G-vTAP Controller sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, the fabric node status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the G-vTAP Controller and if that fails as well then GigaVUE‑FM unregisters the G-vTAP Controller and it will be removed from GigaVUE‑FM.

Configure G-vTAP Agent in Azure

G-vTAP Agent should be registered via the registered G-vTAP Controller and communicates through PORT 8891.

Note:  Deployment of G-vTAP Agents through third-party orchestrator is supported on both Linux and Windows platforms. Refer to Linux G-vTAP Agent Installation and Windows Agent Installation for detailed information.

To register G-vTAP Agent in Azure Portal, use any one of the following methods.

Register G-vTAP Agent during Virtual Machine Launch

Note:  Registering G-vTAP Agent during Virtual Machine Launch is not applicable for Windows Agents. You can register your Windows Agents after launching the Virtual machine, using a configuration file.

In your Azure portal, to launch the G-vTAP Agent init virtual machine and register the G-vTAP Agent using custom data, follow the steps given below:

  1. In the Virtual machines page of the Azure Portal, select Create then Virtual machine. Then Create a Virtual Machine Page appears. For detailed information, refer to Create virtual machine topic in Azure Documentation.
  2. On the Advanced tab, enter the Custom Data as text in the following format and deploy the virtual machine. The G-vTAP Agent uses this custom data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM.
    #cloud-config
    write_files:
     - path: /etc/gigamon-cloud.conf
     owner: root:root
     permissions: '0644'
     content:
         Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the G-vTAP Controller 1>, 
		   <IP address of the G-vTAP Controller 2>
    	remotePort: 8891


Register G-vTAP Agent after Virtual Machine Launch

Note:  You can configure more than one G-vTAP Controller for a G-vTAP Agent, so that if one G-vTAP Controller goes down, the G-vTAP Agent registration will happen through another Controller that is active.

To register G-vTAP Agent after launching a Virtual Machine using a configuration file, follow the steps given below:

  1. Install the G-vTAP Agent in the Linux or Windows platform. For detailed instructions, refer to Linux G-vTAP Agent Installation and Windows G-vTAP Agent Installation.

  2. Log in to the G-vTAP Agent.
  3. Edit the local configuration file and enter the following custom data.
    • /etc/gigamon-cloud.conf is the local configuration file in Linux platform.
    • C:\ProgramData\gvtap-agent\gigamon-cloud.conf is the local configuration file in Windows platform.

    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the G-vTAP Controller 1>, 
		   <IP address of the G-vTAP Controller 2>
    	remotePort: 8891
  4. Restart the G-vTAP Agent service.
    • Linux platform: 
      $ sudo service gvtap-agent restart
    • Windows platform: Restart from the Task Manager.

The deployed G-vTAP Agent registers with the GigaVUE-FM through the G-vTAP Controller. After successful registration, the G-vTAP Agent sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, G-vTAP Agent status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the G-vTAP Agent and if that fails as well then GigaVUE‑FM unregisters the G-vTAP Agent and it will be removed from GigaVUE‑FM.

Configure GigaVUE V Series Node and GigaVUE V Series Proxy in Azure

Note:  It is not mandatory to register GigaVUE V Series Nodes via V Series proxy however, if there is a large number of nodes connected to GigaVUE-FM or if the user does not wish to reveal the IP addresses of the nodes, then you can register your nodes using GigaVUE V Series Proxy. In this case, GigaVUE-FM communicates with GigaVUE V Series Proxy to manage the GigaVUE V Series Nodes.

To register GigaVUE V Series Node and GigaVUE V Series Proxy in Azure Portal, use any one of the following methods.

Register GigaVUE V Series Node and GigaVUE V Series Proxy during Virtual Machine Launch

To register GigaVUE V Series Node and GigaVUE V Series Proxy using the custom data in Azure Portal, follow the steps given below:

  1. In the Virtual machines page of the Azure Portal, select Create then Virtual machine. Then Create a Virtual Machine Page appears. For detailed information, refer to Create virtual machine topic in Azure Documentation.
  2. On the Advanced tab, enter the Custom Data as text in the following format and deploy the virtual machine. The GigaVUE V Series Node and GigaVUE V Series Proxy uses this custom data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM.
    #cloud-config
    write_files:
     - path: /etc/gigamon-cloud.conf
     owner: root:root
     permissions: '0644'
     content:
         Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the GigaVUE-FM> or 
                      <IP address of the Proxy>
    	remotePort: 443
    • You can register your GigaVUE V Series Node directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series node with GigaVUE‑FM. If you wish to register GigaVUE V Series node directly, enter the remotePort value as 443 and the remoteIP as <IP address of the GigaVUE‑FM> or if you wish to deploy GigaVUE V Series node using GigaVUE V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.
    • Use only the default user and password details given in the custom data.


 

Register GigaVUE V Series Proxy after Virtual Machine Launch

To register GigaVUE V SeriesProxy after launching the virtual machine using a configuration file, follow the steps given below:

  1. Log in to theGigaVUE V SeriesProxy.
  2. Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following custom data.
    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the GigaVUE-FM> or 
                      <IP address of the Proxy>
    	remotePort: 443
    • You can register your GigaVUE V Series directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series with GigaVUE‑FM. If you wish to register GigaVUE V Series directly, enter the remotePort value as 443 and the remoteIP as <IP address of the GigaVUE‑FM> or if you wish to deploy GigaVUE V Series using V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.
    • Use only the default user and password details given in the custom data.
  3. Restart the GigaVUE V Series proxy service. 
    • GigaVUE V Series node: 
      $ sudo service vseries-node restart
    • GigaVUE V Series proxy: 
      $ sudo service vps restart

The deployed GigaVUE V Series proxy registers with the GigaVUE-FM. After successful registration, the GigaVUE V Series proxy sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, the fabric node status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach theGigaVUE V Series proxy and if that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series proxy and it will be removed from GigaVUE‑FM.

Refer Deploying GigaVUE Cloud Suite for Azure using Customer Orchestration for more detailed information.