Configure GigaVUE Fabric Components using VMware vCenter

This section provides step-by-step instructions on how to deploy the fabric components using VMware vCenter.

GigaVUE Cloud Suite for VMware ESXi uses port mirroring for traffic acquisition method. However you can also use UCT-V for traffic acquisition. The traffic from the workload virtual machines can be acquired using UCT-V. The traffic acquired from the workload VMs is sent to the GigaVUE V Series Nodes for processing.

Note:  When GigaVUE-FM 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 more details, refer to the Configure Role-Based Access for Third-Party Orchestration section in the 6.9 Documentation.

Prerequisite

Create tokens in the User Management page in GigaVUE-FM. Refer to Configure Tokens for Third Party Orchestration for more detailed information.

Recommended Instance Type

The following table lists the recommended instance type for deploying the fabric components:

Compute Instances

vCPU

Memory

Disk Space

GigaVUE V Series Node

4vCPU

8GB

8GB

UCT-V Controller

2vCPU

4GB

8GB

Refer to the following topics for more details on how to register the fabric components with GigaVUE-FM after deploying the fabric components using VMware vCenter on the host server:

Register UCT-V Controller

Deploy UCT-V Controller through VMware vCenter on the host server.

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

  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. When using Static IP configuration or multiple interfaces with Static IP configuration, create a new .yaml file in /etc/netplan/ directory. Update the file and save it.
  4. Restart the UCT-V Controller service.
    $ sudo service uctv-cntlr restart

Assign Static IP address for UCT-V Controller

By default, the UCT-V Controller gets assigned an IP address using DHCP. If you wish to assign a static IP address, follow the steps below:

  1. Navigate to /etc/netplan/ directory.
  2. Create a new .yaml file. (Other than the default 50-cloud-init.yaml file)
  3. Update the file as shown in the following sample:
    Copy
    network:
      version: 2
      renderer: networkd
      ethernets:
        <interface>:                # Replace with your actual interface name (e.g., eth0)
          dhcp4: no
          dhcp6: no
          addresses:
            - <IPV4/24>             # e.g., 192.168.1.10/24
            - <IPV6/64>             # e.g., 2001:db8:abcd:0012::1/64
          nameservers:
            addresses:
              - <DNS_IPV4>          # e.g., 8.8.8.8
              - <DNS_IPV6>          # e.g., 2001:4860:4860::8888
          routes:
            - to: 0.0.0.0/0
              via: <IPV4_GW>        # e.g., 192.168.1.1
            - to: ::/0
              via: <IPV6_GW>        # e.g., 2001:db8:abcd:0012::fffe
                            
    Example netplan config:

    network:
      version: 2
      renderer: networkd
      ethernets:
        ens3:
          addresses:
             -192.168.1.10/24
             -2001:db8:1::10/64
          nameservers:
            addresses:
              -8.8.8.8
              -2001:4860:4860::8888
          routes:
            -to: 0.0.0.0/0
              via: 192.168.1.1
              metric: 100
            -to: ::/0
               via: 2001:db8:1::1
              metric: 100
  4. Save the file.
  5. Restart theUCT-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, GigaVUE‑FM tries to reach the UCT-V Controller and if that fails as well then GigaVUE‑FM unregisters the UCT-V Controller and it will be removed from GigaVUE‑FM.

Register UCT-V

To register UCT-V after launching a Virtual Machine using a configuration file, follow the steps given below:

  1. Install the UCT-V in the Linux or Windows platform. For detailed instructions, 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.
    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.

    Note:  Before restarting the UCT-V service, update the /etc/uctv/uctv.conf file with network interface information to tap traffic and outgoing interface of tapped traffic.

    • Linux platform: 
      $ sudo service uctv restart
    • Windows platform: Restart from the Task Manager.

Register GigaVUE V Series Node

Note:  When registering GigaVUE V Series Nodes in GigaVUE‑FM, the connection name under each monitoring domain must be unique.

  1. Log in to the VMware vCenter web interface.
  2. Right-click the ESXi Host, Cluster, or data center on which you want to deploy the GigaVUE V Series Node and then select Deploy OVF Template.
  3. Provide a name for the Virtual machine. Upload OVF file and VMDK files based on the below table.

    File Name

    		Form Factor

    Comments

    Supported Ports

    vseries-node-file1.ovf

    Small (2vCPU, 4GB Memory, and 8GB Disk space)

    Use these files when deploying GigaVUE V Series Node via VMware vCenter.

    Mgmt Port, Tool Port, and 8 Network Ports

    vseries-node-file2.ovf

    Medium (4vCPU, 8GB Memory, and 8GB Disk space)

    vseries-node-file3.ovf

    Large (8vCPU, 16GB Memory, and 8GB Disk space)

    vseries-node-file4.ovf

    Small (2vCPU, 4GB Memory, and 8GB Disk space)

    Use these when deploying GigaVUE V Series Node via VMware NSX-T Manager.

    Mgmt Port , Data Port, and Tool Port

    vseries-node-file5.ovf

    Medium (4vCPU, 8GB Memory, and 8GB Disk space)

    vseries-node-file6.ovf

    Large (8vCPU, 16GB Memory, and 8GB Disk space)

    vseries-node-file7.ovf

    Small (2vCPU, 4GB Memory, and 8GB Disk space)

    Use these files when deploying GigaVUE V Series Node via VMware ESXi without vCenter.

    Mgmt Port, Tool Port, and 8 Network Ports

    vseries-node-file8.ovf

    Medium (4vCPU, 8GB Memory, and 8GB Disk space)

    vseries-node-file9.ovf

    Large (8vCPU, 16GB Memory, and 8GB Disk space)

    vseries-node-file12.ovf

    Larger (8vCPU, 16GB Memory, and 80GB Disk space)

    Use these files when deploying GigaVUE V Series Node via VMware vCenter and if you wish to configure AMX application.

    Mgmt Port , Data Port, and Tool Port

    vseries-node-file15.ovf

    Larger (8vCPU, 16GB Memory, and 80GB Disk space)

    Use these files when deploying GigaVUE V Series Node via VMware ESXi without vCenter and if you wish to configure AMX application

    Mgmt Port , Data Port, and Tool Port

    vseries-node-file16.ovf

     

    minipc - Virtual Small Form Factor

    Mgmt Port, Tool Port, and 2 Network Ports

  4. Click Next and complete the Virtual machine launch. Refer VMware Documentation for more detailed information.

  5. Log in to the GigaVUE V Series Node.
  6. 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
  7. Restart the GigaVUE V Series Node service. 
    • GigaVUE V Series node: 
      $ sudo service vseries-node restart

  8. Review the setting selection in the Ready to Complete page, then click Finish.

The GigaVUE V Series Node deployed in VMware vCenter host appears in Third-party Orchestration Monitoring Domain page of GigaVUE‑FM.