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 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:

  • Create service segments in VMware NSX-T Manager and attach it to UCT-V and GigaVUE V Series Nodes. Refer to Create a Service Segment in VMware NSX-T for more detailed information on how to create service segments in VMware NSX-T.

  • 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.

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>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443
  3. When using multiple interfaces or Static IP address, update the 50-cloud-init.yaml file in the /etc/netplan/ directory and save the file. Use the following command to apply the changes.
    • $ sudo netplan apply
  4. 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 node 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

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>
        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.

  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 V Series Nodes 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 node 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.