Configure GigaVUE Fabric Components in OpenStack

You can use your own OpenStack Orchestrator to deploy the GigaVUE fabric components instead of using GigaVUE‑FM to configure the advanced features supported by these nodes.

The third-party orchestration feature allows you to deploy GigaVUE fabric components using your own Azure orchestration system. These fabric components register themselves with GigaVUE‑FM with user information. Once the nodes are registered with GigaVUE‑FM, you can configure monitoring sessions and related services in GigaVUE‑FM.

The heartbeat messages sent from the respective nodes help GigaVUE‑FM determine the health status of the registered nodes.

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

Considerations when deploying the fabric components using third party orchestration in integrated mode

  • Traffic Acquisition Tunnel MTU is set to the default value of 1500. To edit the Traffic Acquisition Tunnel MTU,
    1. Select the monitoring domain and click on the Edit Monitoring Domain option.
    2. Enter the Traffic Acquisition Tunnel MTU and select Save.
  • When you deploy the fabric components using 3rd party orchestration, you cannot delete the monitoring domain without unregistering the registered fabric components.
  • 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, 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 V Series Nodes and Proxy in OpenStack

To configure V Series Nodes and V Series Proxy in OpenStack platform,

  1. Before configuring GigaVUE fabric components through OpenStack, you must create a monitoring domain in GigaVUE‑FM. For detailed instructions, refer to Create Monitoring Domain.

  2. In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you configure the fabric components in OpenStack Orchestrator.
  3. In your OpenStack environment, you can deploy V Series nodes or V Series proxy using the following methods:

Register V Series Nodes or V Series Proxy using OpenStack GUI

To register V Series nodes or proxy using the user data in OpenStack GUI,

  1. On the Instance page of OpenStack dashboard, click Launch instance. The Launch Instance wizard appears. For details, refer to Launch and Manage Instances topic in the OpenStack Documentation.
  2. On the Configuration tab, enter the Customization Script as text in the format given below 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
  • You can register your V Series node directly with GigaVUE-FM or use V Series Proxy. Enter the remotePort value as 443 to register V Series Node directly or enter 8891 to deploy V Series Node using V Series Proxy.

Register V Series Node or V Series Proxy using a configuration file

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

  1. Log in to the V Series Node or proxy.
  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

    Note:  To register V Series node using V Series proxy, enter the remotePort value as 8891.

  3. Restart the V Series node or proxy service using the following commands:
    • V Series node: 
      $ sudo service vseries-node restart
    • V Series proxy: 
      $ sudo service vps restart

    The deployed GigaVUE V Series Node or Proxy registers with the GigaVUE‑FM. After successful registration, the GigaVUE V Series Node or 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 Node or Proxy. If that fails, then GigaVUE‑FM unregisters the GigaVUE V Series Node or Proxy and removes it from GigaVUE‑FM.

Configure UCT-V Controller in OpenStack

To configure GigaVUE fabric components in OpenStack platform,

  1. Before configuring GigaVUE fabric components through OpenStack, create a monitoring domain in GigaVUE‑FM. While creating the monitoring domain, select UCT-V as the Traffic Acquisition Method. For instructions, refer to Create Monitoring Domain.
  2. In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field to configure the fabric components in OpenStack Dashboard.
  3. In your OpenStack environment, launch the UCT-V Controller using any of the following methods:

    Register UCT-V Controller using OpenStack GUI

    To register UCT-V Controller using the user data in OpenStack GUI,

    1. On the Instance page of OpenStack dashboard, select Launch instance. The Launch Instance wizard appears. For details, refer to Launch and Manage Instances topic in the OpenStack Documentation.
    2. On the Configuration tab, enter the Customization Script as text in the format given below and deploy the instance. The UCT-V Controller uses this customization script to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM. #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 OpenStack appears on the Monitoring Domain page of GigaVUE‑FM.

    Register UCT-V Controller using a configuration file

    To register UCT-V Controller using a configuration file,

    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.

Configure UCT-V in OpenStack

You need to register UCT-V via the registered UCT-V Controller and communicate through PORT 8891.

Note:  Deployment of UCT-V 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.

To register UCT-V using a configuration file,

  1. Install the UCT-V in the Linux or Windows platform. For details, 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>
        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)
        remotePort: 8891
    • 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.

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

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, then GigaVUE‑FM unregisters UCT-V and it is removed from GigaVUE‑FM.

Key Considerations for Upgrade

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

For the user created in GigaVUE‑FM,

  • Username: orchestration

  • Password: orchestration123A!.

    Verify that the username orchestration does not belong to another user in GigaVUE‑FM.

After the upgrade, we recommend changing the password on the Users page. For details, refer to Configure Role-Based Access for Third Party Orchestration.