Configure GigaVUE Fabric Components using Nutanix

This topic provides instructions on how to register GigaVUE fabric components using a configuration file.

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

4 vCPU

8GB

10GB

GigaVUE V Series Proxy

1 vCPU

4GB

8GB

UCT-V

1 vCPU

4GB

8GB

UCT-V Controller

1 vCPU

2GB

4GB

Deployment Guidelines

Keep in mind the following when deploying the fabric components using generic mode:

  • Set the correct MTU for tunnels: Use 1350 for IPv4 tunnels and 1330 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.

Note:  Set the correct MTU before deploying the Monitoring Session. If not, you must undeploy and redeploy the session after updating the MTU.

  • Create tokens in the User Management page in GigaVUE-FM. For details, refer to Configure Tokens.
  • 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 you deploy the fabric components using third party orchestration, you cannot delete the monitoring domain without unregistering the registered fabric components.
  • 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 Nutanix Prism Central, you can configure the following GigaVUE fabric components:

Configure UCT-V Controller in Nutanix

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

To register the UCT-V Controller in Nutanix, you can use one of the following methods:

Register UCT-V Controller during Instance Launch

In the Nutanix Prism Central, you can launch the UCT-V Controller instance and register the UCT-V Controller using user data.

Perform the following steps:

  1. On the Prism Central, go to the List tab and click Create VM. The Create VM dialogue box appears. For details, refer to Creating a VM through Prism Central (AHV) topic in the Nutanix documentation.
  2. On the Step 3:Management tab, in the Guest Customization field, select Cloud-init (Linux). Enter the registration data in the text box and deploy the instance. The UCT-V Controller uses the user data to generate the config file (/etc/gigamon-cloud.conf) that is 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>
            sourceIP: <IP address of UCT-V Controller> (Optional Field)
            remotePort: 443

The UCT-V Controller deployed in Nutanix appears on the Monitoring Domain page of GigaVUE‑FM.

Register UCT-V Controller after Instance Launch

To 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>
        sourceIP: <IP address of UCT-V Controller> (Optional Field)
        remotePort: 443
  3. 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.

To assign a static IP address, perform the following steps:

  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 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 Unhealth. If more than five heartbeats fail to reach GigaVUE‑FM, GigaVUE‑FM tries to reach the UCT-V Controller. If that fails as well then GigaVUE‑FM unregisters the UCT-V Controller and removes from GigaVUE‑FM.

Note:  When you deploy GigaVUE V Series Nodes or UCT-V Controllers using 3rd party orchestration, you cannot delete the monitoring domain without unregistering the GigaVUE V Series Nodes or UCT-V Controllers.

Configure UCT-V in Nutanix

Note:  Deployment of GigaVUE fabric components through a third-party orchestrator is supported on Linux and Windows platforms. For details, refer to Linux UCT-V Installation and Windows UCT-V Installation

UCT-V should be registered using the registered UCT-V Controller. It uses PORT 8891.

To register UCT-V in Nutanix, you can use one of the following methods.

Register UCT-V during Instance Launch

Note:  Registering UCT-V during Virtual Machine Launch is not applicable for Windows Agents. You can register the Windows Agent after launching the Virtual machine using a configuration file. The configuration file is located in C:\ProgramData\uctv\gigamon-cloud.conf

In Nutanix Prism Central, you can launch the UCT-V instance and register the UCT-V using user data.

Perform the following steps:

  1. On the Prism Central, go to the List tab and click Create VM. The Create VM dialogue box appears. For details, refer to Creating a VM through Prism Central (AHV) topic in the Nutanix documentation.
  2. On the Step 3:Management tab, in the Guest Customization field, select Cloud-init (Linux). Enter the registration data in the text box and deploy the instance. The UCT-V uses this user data 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>
             sourceIP: <IP address of UCT-V> (Optional Field)

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

Register UCT-V after Instance Launch

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, perform the following steps:

  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.
    • 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>
        sourceIP: <IP address of UCT-V> (Optional Field)

    NOTE: 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.
    • 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 Nutanix

It is not mandatory to register GigaVUE V Series Nodes using the V Series proxy. However, if a large number of nodes are connected to GigaVUE‑FM or if you want to hide the IP addresses of the nodes, then you can register the nodes using GigaVUE V Series Proxy. In this case, GigaVUE‑FM communicates with GigaVUE V Series Proxy to manage the GigaVUE V Series Nodes.

Note:  Before deploying GigaVUE V Series Node, enable the Multi Queue. For more information on enabling the multi-queue, refer to the Nutanix KB article How to change number of vNIC queues and enable RSS virtio-net Multi-Queue for AHV VMs. You can enable the Multi Queue using the Nutanix REST APIs. For more infomation on Nutanix APIs, refer to the Nutanix support site.

To register GigaVUE V Series Node and GigaVUE V Series Proxy in Nutanix, you can use one of the following methods.

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

  1. On the Prism Central, go to the List tab and select Create VM. The Create VM dialogue box appears. For details, refer to Creating a VM through Prism Central (AHV) topic in Nutanix Documentation.
  2. On the Step 3:Management tab, in the Guest Customization field, select Cloud-init (Linux). enter the registration data in the text box and deploy the instance. The GigaVUE V Series Nodes or V Series proxy uses this user data 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 GigaVUE 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 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 canregister GigaVUE V Series Node and GigaVUE V Series Proxy after launching the virtual machine using a configuration file.

Perform the following steps:

  1. Log in to the GigaVUE V Series Node or Proxy.
  2. Edit the 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 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, the GigaVUE 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, then GigaVUE‑FM tries to reach theGigaVUE V Series Proxy. If that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series proxy and it is removed from GigaVUE‑FM.

Limitations

Nutanix does not support IPv6 for the current release of GigaVUE Cloud Suite.