Configure GigaVUE Fabric Components using Third Party Orchestration on NSX-T Federation Environment

This section provides step-by-step instructions on how to deploy the fabric components for VMware NSX-T federated environment.

GigaVUE Cloud Suite for VMware uses service insertion as the traffic acquisition method. However, service insertion is not supported for VMware NSX-T federated environment. 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.

GigaVUE-FM and the fabric components are deployed on the VMware NSX-T local segments or between the stretch segments across multiple sites. The fabric components are deployed using third party orchestration.

Prerequisites:

  • User and Password provided in the registration data must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.

  • Upload OVF file and VMDK files on vCenter 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

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:

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
  1. Save the file.
  2. 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, 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

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 will happen through another Controller that is active.

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>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the UCT-V Controller 1>, <IP address of the UCT-V Controller 2>
        sourceIP: <IP address of UCT-V> (Optional Field)
        remotePort: 8891
    • User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.
    • If you are using multiple interface in UCT-V and UCT-V Controller is not connected to the primary interface, then add the following to the above registration data:
      localInterface:<Interface to which UCT-V Controller is connected>
  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

Refer to Configure GigaVUE Fabric Components using VMware ESXi topic for step-by-step instructions on how to deploy GigaVUE V Series Node on VMware ESXi host.

The deployed GigaVUE V Series Node registers with the GigaVUE-FM. After successful registration the GigaVUE V Series Node 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 Node and if that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series Node and it will be removed from GigaVUE‑FM.