Configure GigaVUE Fabric Components

After configuring the Monitoring Domain, you will be navigated to the OpenStack Fabric Launch Configuration page. In the same OpenStack Fabric Launch Configuration page, you can configure the following fabric components:

In the OpenStack Fabric Launch Configuration page, enter or select the required information as described in the following table.

Fields

Description

SSH Key Pair

The SSH key pair for the G-vTAP Controller. For more information about SSH key pair, refer to Key Pairs.

Security Groups

The security group created for the G-vTAP Controller. For more information, refer to Security Group .

Select Yes to configure a V Series Proxy/Controller.

Configure G-vTAP Controller

A G-vTAP Controller manages multiple G-vTAP Agents and orchestrates the flow of mirrored traffic to GigaVUE V Series nodes. While configuring the G-vTAP Controllers, you can also specify the tunnel type to be used for carrying the mirrored traffic from the G-vTAP Agents to the GigaVUE V Series nodes.

  • Only if G-vTAP Agents are used for capturing traffic, then the G-vTAP Controllers must be configured in the OpenStack cloud.
  • A G-vTAP Controller can only manage G-vTAP Agents that have the same version.

Enter or select the required information in the G-vTAP Controller section as described in the following table.

Fields

Description

Controller Version(s)

The G-vTAP Controller version that you configure must always have the same version number as the G-vTAP Agents deployed in the instances. For more detailed information refer GigaVUE‑FM Version Compatibility Matrix.

Note:  If there is a version mismatch between the G-vTAP controllers and G-vTAP Agents, GigaVUE‑FM cannot detect the agents in the instances.

To add G-vTAP Controllers:

a. Under Controller Versions, click Add.
b. From the Image drop-down list, select a G-vTAP Controller image that matches with the version number of G-vTAP Agents installed in the instances.
c. From the Flavordrop-down list, select a size for the G-vTAP Controller.
d. In Number of Instances, specify the number of G-vTAP Controllers to launch. The minimum number you can specify is 1.

Management Network

 

This segment defines the management network that GigaVUE‑FM uses to communicate with G-vTAP Controllers, GigaVUE V Series Proxy/Controllers, and GigaVUE V Series Nodes.

Network - Select the management network ID.

IP Address Type

The type of IP address GigaVUE‑FM needs to communicate with G-vTAP controllers:

o Private—A private IP can be used when GigaVUE‑FM, the G-vTAP Controller, or the GigaVUE V Series Proxy/Controller reside inside the same project.
o Floating—A floating IP is needed only if GigaVUE‑FM is not in the same project in the cloud or is outside the cloud. GigaVUE‑FM needs a floating IP to communicate with the controllers from an external network.

Additional Network(s)

(Optional) If there are G-vTAP Agents on networks that are not IP routable from the management network, additional networks or subnets must be specified so that the G-vTAP Controller can communicate with all the G-vTAP Agents.

Click Add to specify additional networks (subnets), if needed. Also, make sure that you specify a list of security groups for each additional network.

Tag(s)

(Optional) The key name and value that helps to identify the G-vTAP Controller instances in your environment. For example, you might have G-vTAP Controllers deployed in many regions. To distinguish these G-vTAP Controllers based on the regions, you can provide a name (also known as a tag) that is easy to identify such as us-west-2-gvtap-controllers. There is a specific GvTAP Controller Version for OVS Mirroring and OVS Mirroring + DPDK.

To add a tag:

  1. Click Add.
  2. In the Key field, enter the key. For example, enter Name.
  3. In the Value field, enter the key value. For example, us-west-2-gvtap-controllers.
Cloud-Init User Data (Optional)Enter the cloud initialization user data in YAML, JSON, or Shell script.

Agent Tunnel Type

The type of tunnel used for sending the traffic from G-vTAP Agents to GigaVUE V Series nodes. The options are GRE or VXLAN tunnels.

Configure V Series Proxy/Controller

The fields in the V Series Proxy/Controller configuration section are the same as those on the G-vTAP Configuration page. Refer to Configure GigaVUE Fabric Components for the field descriptions.

Configure V Series Node

Note:  If you are using V Series 1.xx, GigaVUE V Series nodes can only be successfully launched after GigaVUE V Series Controller is fully initialized and the status is displayed as OK.

Creating a GigaVUE V Series node profile automatically launches the V Series node. Enter or select the required information in the V Series Node section as described in the following table.

Parameter

Description
Image Select the V Series node image file.
Flavor Select the form of the V Series node.

Management Network

For the V Series Node, the Management Network is what is used by the V Series Controller to communicate with the V Series Nodes. Select the management network ID.

Note:  When both IPv4 and IPv6 addresses are available, IPv6 address is preferred, however if IPv6 address is not reachable then IPv4 address is used.

Data Network

Click Add to add additional networks. This is the network that the GigaVUE V Series node uses to communicate with the monitoring tools. Multiple networks are supported.

  • Tool Subnet—Select a tool subnet, this is the default subnet that the GigaVUE-FM use to egress traffic to your tools. This subnet must have proper connectivity to your endpoint.
  • IP Address Type
    • Private—A private IP can be used when GigaVUE-FM, the G-vTAP Controller, or the GigaVUE V Series Proxy/Controller, or the V Series node 2 reside inside the same project.
    • Floating—A floating IP address specified here will be where V Series node 2x.x can be directly managed by GigaVUE-FM or can optionally managed by controllers. But for V Series node 1, a controller is mandatory.
  • Network 1—Select a network type.

Note:  For OVS Mirroring or OVS Mirroring + DPDK deployments, must select Floating in the Data Network section and then specify the IPs in the Floating IPs field. You can have multiple Floating IPs.

Note:   A provider network that is able to receive the monitored traffic may also be used here for OVS Mirroring and OVS Mirroring + DPDK. In this case, you would not need to provide a floating IP; but could select "private" and choose the provider network.

Tag(s)

(Optional) The key name and value that helps to identify the G-vTAP Controller instances in your environment. For example, you might have G-vTAP Controllers deployed in many regions. To distinguish these G-vTAP Controllers based on the regions, you can provide a name (also known as a tag) that is easy to identify such as us-west-2-gvtap-controllers.

To add a tag:

  1. Click Add.
  2. In the Key field, enter the key. For example, enter Name.
  3. In the Value field, enter the key value. For example, us-west-2-gvtap-controllers.
Cloud-Init User Data (Optional) Enter the cloud initialization user data in YAML, JSON, or Shell script.

Min Instances

The minimum number of GigaVUE V Series nodes to be launched in OpenStack. The minimum number can be 1.

● When you deploy an OVS Mirroring or OVS Mirroring + DPDK monitoring session, the V Series nodes will automatically be deployed based on the # of hypervisors being monitored.
● When you deploy a G-vTAP based monitoring session, the V Series nodes will automatically be deployed based on the # of VMs being monitored and the instance per V Series node ratio defined in the OpenStack Setttings page.

Note:  GigaVUE-FM will delete the nodes if they are idle for over 15 minutes.

Max Instances

The maximum number of GigaVUE V Series nodes that can be launched in OpenStack.

Note:  Max Instances is applicable only for V Series node 1 works with G-vTAP connections and OVS mirroring.

Tunnel MTU (Maximum Transmission Unit)

The Maximum Transmission Unit (MTU) is applied on the outgoing tunnel endpoints of the GigaVUE-FM V Series node when a monitoring session is deployed. The default value is 1450. The value must be 42 bytes less than the default MTU for GRE tunneling, or 50 bytes less than default MTU for VXLAN tunnels.

Click Save to save the OpenStack Fabric Launch Configuration.

To view the fabric launch configuration specification of a fabric node, click on a fabric node or controller/proxy, and a quick view of the Fabric Launch Configuration appears on the Monitoring Domain page.

To view the G-vTAP Agents of the selected monitoring domain, click on the G-vTAP Agents button. The G-vTAP Agents page appears. The IP address, Registration time, and Status of the G-vTAP Agents are displayed on this page.