Configure the GigaVUE V Series Node
GigaVUE® V Series node is a visibility node that aggregates mirrored traffic from multiple G-vTAP agents. It applies filters, manipulates the packets using GigaSMART applications, and distributes the optimized traffic to cloud-based tools or backhaul to GigaVUE Cloud using the standard IP GRE tunnels.
GigaVUE V Series nodes can be successfully launched only after GigaVUE V Series Controller is fully initialized and the status is displayed as OK.
The V Series Node Configuration page defines the parameters for a GigaVUE V Series node. Creating a GigaVUE V Series node profile automatically launches the V Series node.
To configure a GigaVUE V Series node profile:
1. | Click Cloud from the GigaVUE-FM top navigation. |
2. | Go to OpenStack > Configuration > V Series Nodes.The V Series Node configuration page appears. In the V Series Node configuration page: |
a. | Click New to create a new V Series node configuration. |
b. | Click the check box of a configuration and click Edit to edit an existing configuration. |
3. | Complete the fields in the GigaVUE V Series Node Configuration page to create or edit the node's configuration settings. |
Refer to Configure the G-vTAP Controllers for the common fields. For additional configuration settings, refer to the following table.
Parameter |
Description |
||||||
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. |
||||||
Data Network |
Network 1 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. IP Address Type The type of IP address GigaVUE-FM needs to communicate with G-vTAP or G-vTAP-OVS controllers:
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. |
||||||
Min Instances to Launch |
The minimum number of GigaVUE V Series nodes to be launched in OpenStack. The minimum number can be 0.
Note: GigaVUE-FM will delete the nodes if they are idle for over 15 minutes. |
||||||
Max Instances to Launch |
The maximum number of GigaVUE V Series nodes that can be launched in OpenStack. |
||||||
Tunnel MTU (Maximum Transmission Unit) |
The Maximum Transmission Unit (MTU) is applied on the outgoing tunnel endpoints of the GigaVUE V Series node when a monitoring session is deployed. The default value is 1450. |
||||||
Shared |
Only one V Series node configuration can be shared in a monitoring domain. Note: Not used for OpenStack configurations. |
4. | Click Save to save the configuration. |
Verify the V Series Node Instance
After creating or editing the V Series Node Controller, verify the instance is running:
1. | Log in to OpenStack Horizon and view the compute instances for the project to verify the launch of the V Series Node .![]() |
Note: The above screen is an example only. It is not a GigaVUE-FM screen and is subject to change without notice. Refer to OpenStack documentation for how to use the OpenStack interface.
2. | In GigaVUE-FM, select OpenStack > Visibility Fabric > V Series Node to verify the launch of the GigaVUE V Series node. The V Series Node Controller is displayed with the status as OK. |
Note: The launch of the V Series Controller is also displayed in Cloud > Audit Logs.