Components of GigaVUE Cloud Suite for AWS
GigaVUE Cloud Suite for AWS includes the following components:
- GigaVUE® Fabric Manager (GigaVUE-FM) is a web-based fabric management interface that provides a single pane of glass visibility and management of both the physical and virtual traffic that forms the GigaVUE Cloud for AWS.GigaVUE-FM can be installed on-premises or launched as an Amazon Machine Image (AMI) in AWS. GigaVUE-FM manages the configuration of the following components in your Amazon Virtual Private Clouds (VPC):
- G-vTAP Controller (only if you are using G-vTAP Agent as the traffic acquisition method)
- GigaVUE V Series® 2 Node
- GigaVUE V Series® Proxy
- G-vTAP Agent is an agent that is installed in the VM instance. This agent mirrors the selected traffic from the instances (virtual machines) to the GigaVUE V Series Node. The G-vTAP Agent is offered as a Debian (.deb) or Redhat Package Manager (.rpm) package. For more information on installing the G-vTAP Agent see, Install G-vTAP Agents.
- G-vTAP Controller manages multiple G-vTAP Agents and orchestrates the flow of mirrored traffic to GigaVUE V Series nodes. GigaVUE-FM uses one or more G-vTAP Controllers to communicate with the G-vTAP Agents. A G-vTAP Controller can only manage G-vTAP Agents that has the same version. For example, the G-vTAP Controller v1.7 can only manage G-vTAP Agents v1.7. So, if you have G-vTAP Agents v1.6 still deployed in the EC2 instances, you must configure both G-vTAP Controller v1.6 and v1.7. 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. The tunnel type can be L2GRE or VXLAN.
- GigaVUE® V Series Node is a visibility node that aggregates mirrored traffic. It applies filters, manipulates the packets using GigaSMART applications, and distributes the optimized traffic to cloud-based tools or backhaul to on premise device or tools. GigaVUE Cloud Suite for AWS uses the standard IP GRE or VXLAN tunnels to deliver traffic to tool endpoints. GigaVUE V Series nodes can be successfully launched only after GigaVUE V Series Proxy is fully initialized and the status is displayed as OK.
Note: With G-vTAP Agents, IPSec can be used to establish a secure tunnel between G-vTAP Agents and GigaVUE V Series nodes, especially in a centralized controller and GigaVUE V Series node configuration where cross VPC tunneling may be required to be encrypted.
- GigaVUE V Series Proxy manages multiple GigaVUE V Series nodes and orchestrates the flow of traffic from GigaVUE V Series nodes to the monitoring tools. GigaVUE-FM uses one or more GigaVUE V Series Proxies to communicate with the GigaVUE V Series nodes.
Note: A single G-vTAP Controller can manage up to 1000 G-vTAP Agents.
For GigaVUE V Series configuration, you can configure the GigaVUE fabric components in a Centralized VPC only. In case of a shared VPC, you must select a VPC as your Centralized VPC for fabric configuration.
Following table describes the components that are required for the traffic acquisition methods
Traffic Acquisition Method |
GigaVUE Fabric Components |
||||||||||||
G-vTAP |
|
||||||||||||
VPC Traffic Mirroring without Load Balancer |
|
||||||||||||
VPC Traffic Mirroring with Load Balancer |
|
||||||||||||
Tunnel as a Source (TaaS) |
|