Configure GigaVUE Fabric Components
After configuring the Monitoring Domain, you will be navigated to the AWS Fabric Launch Configuration page.
In the same AWS Fabric Launch Configuration page, you can configure the following fabric components:
In the AWS Fabric Launch Configuration page, enter or select the required information as described in the following table.
Fields |
Description |
|||||||||
Centralized VPC |
Alias of the centralized VPC in which the G-vTAP Controllers, V Series Proxies and the GigaVUE V Series Nodes are launched. |
|||||||||
EBS Volume Type |
The Elastic Block Store (EBS) volume that you can attach to the fabric components. The available options are:
|
|||||||||
SSH Key Pair |
The SSH key pair for the GigaVUE fabric nodes. For more information on Key Pairs, refer to Key Pair. |
|||||||||
Management Subnet |
The subnet that is used for communication between the controllers and the nodes, as well as to communicate with GigaVUE-FM. This is a required field. |
|||||||||
Security Groups |
The security group created for the GigaVUE fabric nodes. For more information on security groups, refer to Security Group |
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.
Note: A G-vTAP Controller can only manage G-vTAP Agents of the same version.
Select Yes for the Configure a G-vTAP Controller field.
Enter or select the required information in the G-vTAP Controller section as described in the following table.
Configure GigaVUE V Series Controller
Select Yes for the Configure a V Series Controller field.
Enter or select the appropriate information as described in the following table for GigaVUE V Series Controller Configuration.
Fields | Description | |||||||||
Version | GigaVUE V Series Controller version. | |||||||||
Instance Type | Instance type for the GigaVUE V Series Controller. The recommended minimum instance type is t2.micro. | |||||||||
Number of Instances | Number of GigaVUE V Series Controller to deploy in the monitoring domain. | |||||||||
Set Management Subnet | Use the toggle button to select a management subnet.
| |||||||||
Set Security Groups | Toggle option to Yes to set the security group that is created for the GigaVUE V Series Controller. Refer to Security Group for more details. | |||||||||
IP Address Type | Select one of the following IP address types:
The elastic IP address does not change when you stop or start the instance. | |||||||||
Additional Subnets | (Optional) If there are GigaVUE V Series Nodes on subnets that are not IP routable from the management subnet, additional subnets must be specified so that the GigaVUE V Series Controller can communicate with all the GigaVUE V Series Nodes. Click Add to specify additional subnets, if needed. Also, make sure that you specify a list of security groups for each additional subnet. | |||||||||
Tags | (Optional) The key name and value that helps to identify the GigaVUE V Series Controller instances in your AWS environment. |
Configure GigaVUE V Series Node
Note: If you are using V Series 1, GigaVUE V Series Nodes can only be successfully launched after GigaVUE V Series Proxy is fully initialized and the status is displayed as OK.
Enter or select appropriate information as described in the following table for GigaVUE V Series Node Configuration.
Fields | Description |
Version | GigaVUE V Series Node version. |
Instance Type | The instance type for the GigaVUE V Series Node. The default instance type is nitro-based t3a.xlarge. The recommended instance type is c5n.xlarge for 4vcpu and c5n.2xlarge for 8vcpu. |
Min Number of Instances | The minimum number of GigaVUE V Series Nodes that must be deployed in the monitoring domain. The minimum number of instances must be 1. When 0 is entered, no GigaVUE V Series Node is launched. Note: If the minimum number of instances is set as ‘0’, then the nodes will be launched when a monitoring session is deployed if GigaVUE-FM discovers some targets to monitor. |
Max Number of Instances | The maximum number of GigaVUE V Series Nodes that can be deployed in the monitoring domain. |
Data Subnets | The subnet that receives the mirrored GRE or VXLAN tunnel traffic from the G-vTAP Agents. Note: Using the Tool Subnet checkbox you can indicate the subnets to be used by theGigaVUE V Series to egress the aggregated/manipulated traffic to the tools. |
Tags | (Optional) The key name and value that helps to identify the GigaVUE V Series Node instances in your AWS environment. For example, you might have GigaVUE V Series Node deployed in many regions. To distinguish these GigaVUE V Series Node based on the regions, you can provide a name that is easy to identify such as us-west-2-vseries. To add a tag:
|
Click Save to save the AWS Fabric Launch Configuration.
To view the fabric launch configuration specification of a fabric node, click on a fabric node or controller, 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.