Configure GigaVUE Fabric Components using Nutanix

This section provides step-by-step information 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

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

  • Ensure that the Traffic Acquisition Tunnel MTU is set to thedefault value of 1250 when using IPv4 tunnels or 1230 when using IPv6 tunnels. To edit the Traffic Acquisition Tunnel MTU, select the monitoring domain and click on the Edit Monitoring Domain option. Enter the Traffic Acquisition Tunnel MTU value and click Save.
  • Before deploying the monitoring session ensure that the appropriate Traffic Acquisition Tunnel MTU value is set. Otherwise, the monitoring session must be un-deployed and deployed again.
  • 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.
  • 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. Refer to Create Monitoring Domain for more detailed information on how to create monitoring domain under third party orchestration.
  • When you deploy the fabric components using third party orchestration, you cannot delete the monitoring domain without unregistering the registered fabric components.
  • You can also upload custom certificates to GigaVUE V Series Nodes, , GigaVUE V Series Proxy, and UCT-V Controller using your own cloud platform when deploying the fabric components. Refer to Install Custom Certificate for more detailed information.

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 any one of the following methods:

Register UCT-V Controller during Instance Launch

In the Nutanix Prism Central, to 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 more information, 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.

    Field

    		User Data

    User data without custom certificate

    Copy
    #cloud-config
     write_files:
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <Connection Name>
            user: <Username>
            password: <Password>
            remoteIP: <IP address of the GigaVUE-FM>
            sourceIP: <IP address of UCT-V Controller> (Optional Field)
            remotePort: 443

    User data with custom certificate

    Copy
    #cloud-config
     write_files:
     - path: /etc/cntlr-cert.conf
       owner: root:root
       permissions: "0644"
       content: |
          -----BEGIN CERTIFICATE-----
          <certificate content>
          -----END CERTIFICATE-----
     - path: /etc/cntlr-key.conf
       owner: root:root
       permissions: "400"
       content: |
          -----BEGIN PRIVATE KEY-----
          <private key content>
          -----END PRIVATE KEY-----
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
             groupName: <Monitoring Domain Name>
             subGroupName: <Connection Name>
             user: <Username>
             password: <Password>
             remoteIP: <IP address of the GigaVUE-FM>
             sourceIP: <IP address of UCT-V Controller> (Optional Field)
             remotePort: 443

    Note:  The minimum value for the authentication key encryption length provided during the key generation is 2048.

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>
        user: <Username>
        password: <Password>
        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. 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:
                    ens3:
                            addresses:
                                    - <IP address>
                            gateway: <IP address>
                    ens4:
                            addresses:
                                    - <IP address>
                            gateway: <IP address>
                    ens5:
                            addresses:
                                    - <IP address>
                            gateway: <IP address>
  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.

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. Refer to Linux UCT-V Installation and Windows UCT-V Installation for detailed information.

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

To register UCT-V in Nutanix, you can use any 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, to 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 detailed information, 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 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>
             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>

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.

    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.
    • 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, GigaVUE‑FM tries to reach the UCT-V and if that fails as well then GigaVUE‑FM unregisters the UCT-V and it will be removed from GigaVUE‑FM.

Configure GigaVUE V Series Nodes and V Series Proxy in Nutanix

Note:  It is not mandatory to register GigaVUE V Series Nodes using the V Series proxy. However, if there are large number of nodes 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 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 Nutanix support site.

To register GigaVUE V Series Node and GigaVUE V Series Proxy in Nutanix, you can use any 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 click Create VM. The Create VM dialogue box appears. For detailed information, 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.

    Field

    		User Data

    User data without custom certificate

    Copy
    #cloud-config
     write_files:
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <Connection Name>
            user: <Username>
            password: <Password>
            remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
            remotePort: 443

    User data with custom certificate

    Copy
    #cloud-config
     write_files:
     - path: /etc/cntlr-cert.conf
       owner: root:root
       permissions: "0644"
       content: |
          -----BEGIN CERTIFICATE-----
          <certificate content>
          -----END CERTIFICATE-----
     - path: /etc/cntlr-key.conf
       owner: root:root
       permissions: "400"
       content: |
          -----BEGIN PRIVATE KEY-----
          <private key content>
          -----END PRIVATE KEY-----
     - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content: |
         Registration:
             groupName: <Monitoring Domain Name>
             subGroupName: <Connection Name>
             user: <Username>
             password: <Password>
             remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
             remotePort: 443

    Note:  The minimum value for the authentication key encryption length provided during the key generation is 2048.

    • 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

To register 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>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
        remotePort: 443
    • 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 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 and if that fails as well then GigaVUE‑FM unregisters theGigaVUE V Series proxy and it will be removed from GigaVUE‑FM.

Keep in mind the following when upgrading the GigaVUE-FM to 6.1.00 or higher version (when using third party orchestration to deploy fabric components):

When upgrading GigaVUE-FM to any version higher than 6.0.00 and if the GigaVUE V Series Nodes version deployed in that GigaVUE-FM is lower than or equal to 6.0.00, then for the seamless flow of traffic, GigaVUE-FM automatically creates Users and Roles in GigaVUE-FM with the required permission. The username would be orchestration, and the password would be orchestration123A! for the user created in GigaVUE-FM. Ensure there is no existing user in GigaVUE-FM, with the username orchestration.

Once the upgrade is complete, it is recommended that the password be changed on the Users page. Refer to Configure Role-Based Access for Third Party Orchestration for detailed steps on how to change password in the user page.

Limitations

IPv6 is not supported by Nutanix for the current release of GigaVUE Cloud Suite.