Configure GigaVUE Fabric Components using GCP

This section provides step-by-step information on how to register GigaVUE fabric components using Google Cloud Platform (GCP) or a configuration file.

Minimum Requirements

The following table lists the minimum requirements for deploying the fabric components:

Fabric Component Machine type
GigaVUE V Series Node
  • c2-standard-4 for 2 interfaces
  • c2-standard-8 for 3 interfaces
GigaVUE V Series Proxy e2-micro
UCT-V Controller e2-micro

Deployment Guideines

Keep in mind the following when deploying the fabric components using GCP:

  • Set the correct MTU for tunnels: With a default MTU of 1460 in GCP, use 1410 for IPv4 tunnels and 1390 for IPv6. To update the Traffic Acquisition Tunnel MTU:

    1. Select the monitoring domain.

    2. Select the Edit Monitoring Domain option.

    3. Enter the Traffic Acquisition Tunnel MTU value and select Save.

      For details, refer to Traffic Acquisition Tunnel MTU

  • For successful registration of fabric components, configure firewall rules to open ports.
  • When you deploy the fabric components using third party orchestration, you cannot delete the Monitoring Domain or change the MTU without unregistering the registered fabric components.
  • You can also create a monitoring domain under Third Party Orchestration and provide the monitoring domain name and the connection name as groupName and subGroupName in the registration data. For details, refer to Create Monitoring Domain.
  • When launching an instance, to access it using a private key, add the SSH key. The default password is gigamon.
  • Create tokens in the User Management page in GigaVUE-FM. For details, refer to Configure Tokens.
  • When GigaVUE‑FM version is 6.10.00 or above and the Fabric Components are on (n-1) or (n-2) versions, you must create a Username and Password instead of using tokens in the registration data. For details, refer to the Configure Role-Based Access for Third-Party Orchestration section in the v6.9 Documentation.

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

Configure UCT-V Controller in GCP

You can configure more than one UCT-V Controller in a monitoring domain.

To register UCT-V Controller in GCP, use one of the following methods:

Register UCT-V Controller during Instance Launch

In your GCP, you can launch the UCT-V Controller and to register UCT-V Controller using custom metadata.

Perform the following steps:

  1. On the VM instances page of GCP, select Create instances . For details, refer to Create and Start instance topic in the GCP documentation.
  2. Under the Metadata tab, enter the key as user-data and in the value field enter the below mentioned text in the following format and deploy the instance. The UCT-V Controller uses this Custom Metadata to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.
    Copy
    #cloud-config
     write_files:
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <Connection Name>
            token: <Token>
            remoteIP: <IP address of the GigaVUE-FM>
            remotePort: 443

Register UCT-V Controller after Instance Launch

You can register UCT-V Controller after launching a Virtual Machine using a configuration file.

Perform the following steps:

  1. Log in to the UCT-V Controller.
  2. Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following user data: 
     
    Copy
    Registration:
        groupName: <Monitoring Domain Name>
        subGroupName: <Connection Name>
        token: <Token>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443
  3. Restart the UCT-V Controller service.
    $ sudo service uctv-cntlr restart

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

The UCT-V Controller deployed in GCP appears on the Third Party Orchestration Monitoring Domain page of GigaVUE‑FM.

Configure UCT-V in GCP

Linux and Windows platforms support Deployment of GigaVUE fabric components through a third-party orchestrator.

Note:  You can configure more than one UCT-V Controller for a UCT-V, so that if one UCT-V Controller goes down, the UCT-V registration takes place through another active Controller.

Install the Windows UCT-V

Perform the following steps:

  1. Deploy Windows server in GCP. For details, refer to Create a Windows Server VM instance in Compute Engine topic in Google documentation.
  2. Follow the instruction in the Connect to the VM instance by using RDP section of Set up Chrome Remote Desktop for Windows on Compute Engine topic in the GCP documentation.
  3. Download UCT-V build in your desktop and copy it to the RDP session.
  4. Turn off the Windows Firewall Defender.
  5. Install the Windows UCT-V. For details, refer to Windows UCT-V Installation for step-by-step instructions on how to install Windows UCT-V.

To register UCT-V in GCP, use one of the following methods.

Register UCT-V during Instance Launch

You need to register UCT-V through the registered UCT-V Controller. It communicates through PORT 8891.

Note:  Registering UCT-V during Virtual Machine Launch is not applicable to Windows UCT-V. You can register your Windows UCT-V after launching the Virtual machine, using a configuration file.

In your GCP, to launch the instance and register the UCT-V using Custom Metadata, perform the following steps:

  1. On the VM instances page of GCP, select Create instances . For details, refer to Create and Start instance topic in the GCP documentation.
  2. Under the Metadata tab, enter the key as user-data and in the value field, enter the below mentioned text in the following format and deploy the instance. The UCT-V uses this Custom Metadata to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.
    Copy
    #cloud-config
     write_files:
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
             groupName: <Monitoring Domain Name>
             subGroupName: <Connection Name>
             token: <Token>
             remoteIP: <IP address of the UCT-V Controller 1>, <IP address of the UCT-V Controller 2>

Register UCT-V after Instance Launch

To register UCT-V after launching a Virtual Machine using a configuration file, perform the following steps:

  1. Install the UCT-V in the Linux or Windows platform. For details, refer to Linux UCT-V Installation and Windows UCT-V Installation.

  2. Log in to the UCT-V.
  3. Create a local configuration file and enter the following user data.
    • /etc/gigamon-cloud.conf is the local configuration file in Linux platform.
    • C:\ProgramData\uctv\gigamon-cloud.conf is the local configuration file in Windows platform.
    • When creating C:\ProgramData\uctv\gigamon-cloud.conf file, ensure that the file name extension is .conf. To view the file name extension in Windows, perform the following steps:
      1. Go to File Explorer and open the File Location.
      2. On the top navigation bar, select View.
      3. In the View tab, enable the File name extensions check box.

    Copy
    Registration:
        groupName: <Monitoring Domain Name>
        subGroupName: <Connection Name>
        token: <Token>
        remoteIP: <IP address of the UCT-V Controller 1>, <IP address of the UCT-V Controller 2>
  4. Restart the UCT-V service.
    • Linux platform: 
      $ sudo service uctv restart
    • Windows platform: Restart from the Task Manager.

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

Configure GigaVUE V Series Nodes and V Series Proxy in GCP

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 GCP, use one of the following methods.

Register GigaVUE V Series Node and GigaVUE V Series Proxy during Instance Launch

  1. On the VM instances page of GCP, select Create an instance . For details, refer to Create VMs with multiple network interfaces topic in tjhe GCP documentation.
  2. Under the Metadata tab, enter the key as user-data and in the value field, enter the below mentioned text in the following format and deploy the instance. The UCT-V uses this Custom Metadata to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.
    Copy
    #cloud-config
     write_files:
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <Connection Name>
            token: <Token>
            remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
            remotePort: 443

    NOTE: You can register your GigaVUE V Series Nodes directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series Nodes with GigaVUE‑FM. If you wish to register GigaVUE V Series Nodes 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 Nodes using GigaVUE V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.

Register GigaVUE V Series Node and GigaVUE V SeriesProxy after Instance Launch

You can register GigaVUE V Series Node and GigaVUE V Series Proxy after launching the virtual machine using a configuration file.

To register,

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

    NOTE: You can register your GigaVUE V Series Nodes directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series Nodes with GigaVUE‑FM. If you wish to register GigaVUE V Series Nodes 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 Nodes using GigaVUE V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.

  3. Restart the GigaVUE V Series node or proxy service. 
    • V Series node: 
      $ sudo service vseries-node restart
    • V Series proxy: 
      $ sudo service vps restart

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

Note:  When the GigaVUE V Series Node is stopped or terminated from the GCP, it does not send any unregistration request and GigaVUE‑FM unregisters the V Series Node soon after.