Configure GigaVUE Fabric Components in OpenStack

You can use your own OpenStack orchestration system to deploy GigaVUE fabric nodes and use GigaVUE-FM to configure the advanced features supported by these nodes. These nodes register themselves with GigaVUE-FM using the information provided by your OpenStack orchestration system. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM. Health status of the registered nodes are determined by the heartbeat messages sent from the respective nodes.

Recommended Instance Type

Fabric Component Machine type
GigaVUE V Series Node

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

Keep in mind the following when deploying the fabric components using third party orchestration in integrated mode:

  • In the above mentioned case, the Traffic Acquisition Tunnel MTU is set to the default value 1500. 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 and click Save.
  • When you deploy the fabric components using 3rd party orchestration, you cannot delete the monitoring domain without unregistering the registered fabric components.
  • You can use OpenStack Orchestrator for GigaVUE fabric node configuration only using V Series 2 nodes.

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

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. Refer to Create Monitoring Domain for detailed instructions.

  2. In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you are going to 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 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.

    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
  • You can register your V Series node directly with GigaVUE‑FM or you can use V Series proxy to register your V Series node with GigaVUE‑FM. If you wish to register V Series node directly, enter the remotePort value as 443 or if you wish to deploy V Series node using V Series proxy then, enter the remotePort value as 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.

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>
        user: orchestration
        password: orchestration123A!
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443

    Note:  If you wish to register V Series node using V Series proxy then, enter the remotePort value as 8891.

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

    The deployed V Series node or V Series proxy registers with the GigaVUE-FM. After successful registration the V Series node or proxy 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 V Series node or proxy and if that fails as well then GigaVUE‑FM unregisters the V Series node or proxy and it will be removed 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, you must create a monitoring domain in GigaVUE-FM. While creating the monitoring domain, select UCT-V as the Traffic Acquisition Method. Refer to Create Monitoring Domain for detailed instructions.
  2. In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you are going 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, click 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 customization script 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>
              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>
               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>
          user: <Username>
          password: <Password>
          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. 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 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.

Configure UCT-V in OpenStack

UCT-V should be registered via the registered UCT-V Controller and communicates through PORT 8891.

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

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. 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, follow the steps given below:
      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>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the UCT-V Controller 1>, 
               <IP address of the UCT-V Controller 2>
        remotePort: 8891

    Note:  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.
    • 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 will happen 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, 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.

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

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