Configure a Gateway Load Balancer

Prerequisites

Create or update Security Group policies of GigaVUE Cloud Suite components. Refer to Security Group topic for detailed information.
Create or update routes in various VPCs across participating mirrored AWS accounts so that all mirrored account VPCs can connect to the target account VPC where the AWS Gateway Load Balancer is deployed. Refer to Amazon VPC for more information.
Create or update existing IAM role for GigaVUE-FM in the centralized VPC. Additionally trust relationship needs to be created between the mirrored and the target account for GigaVUE-FM to execute the above permissions at the IAM role level. Refer to AMI and Permissions section for detailed information.
For more information on AWS recommended design for Gateway Load Balancer implementation with inline services, such as firewall. see Getting started with Gateway Load Balancers - Elastic Load Balancing (amazon.com)
You must create a VPC endpoint and endpoint service. For more information, see Create endpoint service
Create a routing table. For more information, see Amazon documentation.
User and Password provided in the registration data must be configured in the User Management page for deploying GigaVUE V Series Node using Third Party Orchestration. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information.

Points to Note:

When configuring Gateway Load Balancer, the GigaVUE V Series Nodes must be deployed using Third Party Orchestration.

Perform the following steps to configure an external load balancer in AWS:

Create a Target Group
Create a Load Balancer
Create a Launch Template for Auto Scaling group
Create an Auto Scaling group using a Launch Template

Create a Target Group

Enter or select the following details as mentioned in the table to configure target groups in AWS.

Parameters	Description	Reference	Mandatory field
Basic Configuration
Choose a target type	Select IP address as the target type	Create a target group for your Gateway Load Balancer	Yes
Protocol	Verify that Protocol is GENEVE		Yes
Port	Verify that the port value is 6081		Yes
Health Checks
HealthCheckProtocol	Select TCP as the protocol.	Health checks for Gateway Load Balancer target groups	Yes
HealthCheckPort	Enter 8889 as the port.		Yes
HealthCheckIntervalSeconds	Enter 10 seconds as the approximate amount of time, in seconds.		Yes

Create a Load Balancer

Enter or select the following details as mentioned in the table to configure a load balancer in AWS.

Parameters	Description	Reference	Mandatory field
Network Mapping
VPC	Select the VPC for your targets (GigaVUE V Series Node)	Create a Gateway Load Balancer	Yes
IP Listener routing
Default action	Select the target group to receive traffic. If you don't have a target group, choose Create target group.	Create a target group	Yes

Create a Launch Template for Auto Scaling group

Enter or select the following details to create a launch template for auto scaling groups in AWS.

Parameters	Description	Reference	Mandatory field
Launch Template contents
Application and OS Images (Amazon Machine Image)	Select the AMI of the GigaVUE V Series Node.	Create a launch template for an Auto Scaling group	Yes
Instance type	Select c5n.xlarge as the instance type.		Yes
Key pair name	Select a Key pair for the instance.		Yes
Network Settings
Device Index	Add 2 Network Interfaces for the GigaVUE V Series Node with device index as 0 and 1 (mgmt and data interface respectively) and for the interfaces,	Create a launch template for an Auto Scaling group	Yes
Firewall (security groups)	Keep this blank and configure one or more security groups as part of the network interface.	Security Group	Yes
Advanced Settings
Advanced details	Enter the User data as text in the following format and deploy the instance. The GigaVUE V Series Nodes uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM using Third Party Orchestration. Copy `#cloud-config write_files: - path: /etc/gigamon-cloud.conf owner: root:root permissions: '0644' content: \| Registration: groupName: <Monitoring Domain Name> subGroupName: <VPC Name> user: <Username> password: <Password> remoteIP: <IP address of the GigaVUE-FM> remotePort: 443`	Create a launch template using advanced settings	Yes

Create an Auto Scaling group using a Launch Template

Enter or select the following details to create an auto scaling group and launch the fabric components using the launch template in AWS.

Parameters	Description	Reference	Mandatory field
Configure group size and scaling policies
Group Size	Enter the Desired capacity as 0. The Desired capacity value must be less that the Maximum Capacity value. Note: Once the monitoring Domain and connection is configured, edit this value to the number of GigaVUE V Series Node that needs to be deployed in this Monitoring Domain.	Creating an Auto Scaling group using a launch template	Yes
Automatic Scaling	Select Target tracking scaling policy and enter the following details to define a policy: Metric Type: 1000000000 (bytes) Instance warmup: 300 seconds	Create a target tracking scaling policy	Yes
Add tag	Provide a tag key and value for each tag.	Tag Auto Scaling groups and instances	No

In the Instances page, you can view the GigaVUE V Series Node instance deployed by the load balancer.

After configuring the network load balancer in AWS, you must register the GigaVUE V Series Node with GigaVUE-FM. Refer to Deploy Visibility Fabric with Gateway Load Balancer section for more detailed information on how to deploy the GigaVUE V Series Node across the AWS accounts with Network load balancer configured.