Configure GigaVUE Fabric Components using OpenStack

This section provides information on how to register GigaVUE fabric components using OpenStack or a configuration file.

Recommended Instance Type

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

Fabric Component Machine type
GigaVUE V Series Node

m1.medium
GigaVUE V Series Proxy m1.small
UCT-V Controller m1.small

Deployment Best Practices

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

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

  • 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.
  • GigaVUE V Series Node must have a minimum of two Networks Interfaces (NIC) attached to it, a management NIC and a data NIC. You can add both these interfaces when deploying the GigaVUE V Series Node in OpenStack.
  • Create tokens in the User Management page in GigaVUE-FM. For details, refer to Configure Tokens.
  • 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 details, refer to the Configure Role-Based Access for Third-Party Orchestration section in the 6.9 Documentation.

In your OpenStack Dashboard, you can configure the following GigaVUE fabric components:

Configure UCT-V Controller in OpenStack

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

To register UCT-V Controller in OpenStack, use one of the following methods:

Register UCT-V Controller during Instance Launch

In your OpenStack dashboard, you can launch the UCT-V Controller and register UCT-V Controller using Customization Script.

perform the following steps:

  1. On the Instance page of OpenStack dashboard, select Launch instance. The Launch Instance wizard appears. For detailed information, refer to Launch and Manage Instances topic in OpenStack Documentation.
  2. On the Configuration tab, enter the Customization Script as text in the following format and deploy the instance. The UCT-V Controller uses this registration 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>
            remotePort: 443

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

Register UCT-V Controller 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 Instance 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 Customization Script:
    Copy
    Registration:
        groupName: <Monitoring Domain Name>
        subGroupName: <Connection Name>
        token: <Token>
        remoteIP: <IP address of the GigaVUE-FM>
        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 Third Party orchestration, you cannot delete the monitoring domain without unregistering the V Series Nodes or UCT-V Controllers.

Configure UCT-V in OpenStack

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 takes place through another active Controller.

To register UCT-V using a configuration file:

  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. Edit the local configuration file and enter the following Customization Script.
    • /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, click 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>

    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-agent 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 OpenStack

Note:  It is not mandatory to register GigaVUE V Series Nodes via V Series proxy however, if there is a large number of nodes connected to GigaVUE‑FM or if the user does not wish to reveal the IP addresses of the nodes, then you can register your nodes using GigaVUE V Series Proxy. In this case, GigaVUE‑FM communicates with GigaVUE V Series Proxy to manage the GigaVUE V Series Nodes.

To register GigaVUE V Series Node and GigaVUE V Series Proxy in OpenStack, use one of the following methods:

Register V Series Nodes or V Series Proxy during Instance Launch

To register V Series nodes or proxy using the Customization Script in OpenStack GUI:

  1. On the Instance page of OpenStack dashboard, select Launch instance. The Launch Instance wizard appears. For detailed information, refer to Launch and Manage Instances topic in OpenStack Documentation.
  2. On the Configuration tab, enter the Customization Script as text in the following format and deploy the instance. The V Series nodes or V Series proxy uses this customization script 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 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 V Series Node or V Series Proxy after Instance Launch

To register V Series node or proxy using a configuration file:

  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 customization script:
    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. 
    • GigaVUE V Series Node: 
      $ sudo service vseries-node restart
    • GigaVUE 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

    Note:  When the GigaVUE V Series Node is stopped or terminated from the OpenStack, it does not send any unregistration request and GigaVUE‑FM unregisters the V Series Node soon after.