Configure a Gateway Load Balancer in AWS for Inline V Series Solution

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.
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.
You must create a Gateway Load Balancer endpoint. For more information, see Create a Gateway Load Balancer endpoint.
Create a routing table. For more information, see Amazon documentation.

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 a gateway load balancer for Inline V Series Solution in AWS:

Create a Target Group
Create a Gateway Load Balancer
Create a Launch Template for Inline GigaVUE V Series Node
Create an Auto Scaling group using a Launch Template for Inline GigaVUE V Series Node
Create a Launch Template for Out of Band GigaVUE V Series Node
Create an Auto Scaling group using a Launch Template for Out of Band GigaVUE V Series Node

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 Instance 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 5 seconds as the approximate amount of time.		Yes
HealthyThresholdCount	Enter 2 as the threshold count value.
UnhealthyThresholdCount	Enter 2 as the threshold value.
HealthCheckTimeoutSeconds	Enter 2 seconds as the timeout.

After configuring the target group, update the following attributes to enable traffic rebalancing when a V Series Node becomes unhealthy:

Target failover – Turn this On to rebalance existing traffic flows. Refer to Target failover section in AWS Documentation for details.
Deregistration delay – Adjust as needed to ensure seamless transition of traffic. Refer to Deregistration delay section in AWS Documentation for details.

Create a Gateway Load Balancer

Enter or select the following details as mentioned in the table to configure a gateway 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

After configuring the Gateway Load balancer, configure Cross-zone load balancing to balance traffic flows between the GigaVUE V Series Nodes deployed across multiple availability zones. Refer to Cross-zone load balancing section in AWS Documentation for more details.

Create a Launch Template for Inline GigaVUE V Series Node

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 for the data interface and 1 for the mgmt interface. Select the appropriate security group 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 files (/etc/gigamon-cloud.conf and /etc/vseries-inline.conf) and register with GigaVUE-FM using Third Party Orchestration. Note: Token must be configured in the User Management page. Refer to Configure Tokens for Third Party Orchestration for more detailed information. Copy #cloud-config write_files: - path: /etc/gigamon-cloud.conf owner: root:root permissions: '0644' content: \| Registration: groupName: <Monitoring Domain Name> subGroupName: <VPC Name> token: <token> remoteIP: <IP address of the GigaVUE-FM> remotePort: 443 - path: /etc/vseries-inline.conf owner: root:root permissions: '0644' content: ""	Create a launch template using advanced settings	Yes

Create an Auto Scaling group using a Launch Template for Inline GigaVUE V Series Node

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
Choose launch template or configuration
Launch template	Choose the Launch Template created for Inline GigaVUE V Series Node	Creating an Auto Scaling group using a launch template	Yes
Integrate with other services
Load balancing	Choose Attach to an existing load balancer option.	Creating an Auto Scaling group using a launch template
Attach to an existing load balancer	Select the Choose from your load balancer target groups option.	Creating an Auto Scaling group using a launch template	Yes
Existing load balancer target groups	Select the Target Group created above.
Configure group size and scaling
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	Create a target tracking scaling policy	Yes
Add tag	Provide Key as GigamonNode and Value as VSeriesNode for each tag.	Tag Auto Scaling groups and instances	No

Create a Launch Template for Out of Band GigaVUE V Series Node

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. Note: Token must be configured in the User Management page. Refer to Configure Tokens for Third Party Orchestration for more detailed information. Copy `#cloud-config write_files: - path: /etc/gigamon-cloud.conf owner: root:root permissions: '0644' content: \| Registration: groupName: <Monitoring Domain Name> subGroupName: <VPC Name> token: <Token> 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 for Out of Band GigaVUE V Series Node

You can configure multiple auto-scaling groups based on the number of node groups or tiers you need to set up.

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
Choose launch template or configuration
Launch template	Choose the Launch Template created for Out-of-Band GigaVUE V Series Node	Creating an Auto Scaling group using a launch template	Yes
Configure group size and scaling
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 Key as GigamonNode and Value as VSeriesNode 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 GigaVUE V Series Nodes for Inline V Series Solution section for more detailed information on how to deploy the GigaVUE V Series Node across the AWS accounts with Network load balancer configured.