Configure a Gateway Load Balancer in AWS for Inline V Series Solution
Points to Note:
- When configuring Gateway Load Balancer, the GigaVUE V Series Nodes must be deployed using Third Party Orchestration.
- Inline V Series solution requires a dedicated Gateway Load Balancer deployed in your VPC.
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 Endpoint Service
- Create VPC Endpoint
Create a Target Group
Enter or select the following details as mentioned in the table to create a target groups in AWS.
Parameters |
Instructions |
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 |
|
VPC |
Select the VPC where you want to create the Gateway Load balancer and the target group. |
Yes |
|
Health Checks |
|||
Health check protocol |
Select TCP as the protocol. |
Health checks for Gateway Load Balancer target groups
|
Yes |
Health check port |
Select the option to Override the port and enter 8889 as the port value. |
Yes |
|
Healthy threshold |
Enter 2 as the threshold count value. |
Yes |
|
Unhealthy threshold |
Enter 2 as the threshold value. |
Yes |
|
Timeout |
Enter 2 seconds as the timeout. |
Yes |
|
Interval |
Enter 5 seconds as the approximate amount of time. |
Yes |
Once the target group details are configured and saved, you will be prompted to select targets. Skip this step and click Create target group to finalize the configuration.
Additional Configurations
After configuring the target group, you can edit the target group to update the following attributes to enable traffic rebalancing when a GigaVUE V Series Node becomes unhealthy.
Edit Target Group
Parameters |
Instructions |
Reference |
Mandatory field |
---|---|---|---|
Edit Attributes |
|||
Target failover1 |
Turn this on to rebalance existing traffic flows. |
|
No |
Deregistration delay2 |
Adjust as needed to ensure seamless transition of traffic. The recommended value is 0. |
No |
Create a Gateway Load Balancer
Enter or select the following details as mentioned in the table to create a gateway load balancer in AWS.
Parameters |
Instructions |
Reference |
Mandatory field |
---|---|---|---|
Network Mapping |
|||
VPC |
Select the VPC for your targets (GigaVUE V Series Node) |
Yes |
|
Availability Zone and subnets |
Select the zones and the corresponding subnets where you want to launch the GigaVUE V Series Node. Note: If your source VMs or VPC endpoints spans multiple Availability Zones, the gateway load balancer must be associated the same Availability Zones. |
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. |
Yes |
Note: Once the Gateway Load Balancer is created and associated with subnets and Availability Zones, these settings cannot be modified. If you need to make changes later, you have to delete and recreate the load balancer.
(Optional) After creating the Gateway Load balancer, you can 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 |
Instructions |
Reference |
Mandatory field |
---|---|---|---|
Launch Template contents |
|||
Application and OS Images (Amazon Machine Image) |
Select the AMI of the GigaVUE V Series Node. From the AWS Marketplace AMIs. Search Gigamon and choose the GigaVUE Cloud Suite V Series Image. Subscribe to it. |
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 |
|||
Subnet |
Select Don't include in launch template option. |
Yes |
|
Firewall (security groups) |
Choose Select existing security group option. Keep the security group blank and configure one or more security groups as part of the network interface as mentioned in the following steps. |
Yes |
|
Advanced Network configurations GigaVUE V Series Node requires a minimum of 2 Network Interfaces one for data and other one for mgmt. Add 2 Network Interfaces. |
|||
Network interface 1 - Data Interface |
|||
Device Index |
Enter the device index as 0 for the data interface. Note: When you configure a Gateway Load Balancer (GWLB) and associate a GigaVUE V Series Node (VSN) with the target group, the load balancer automatically forwards traffic to interface 0 |
Yes |
|
Subnet |
The subnet is automatically assigned by AWS. |
Yes |
|
Security Group |
Choose the security group. |
Yes |
|
Network interface 2 - Management Interface |
|||
Device Index |
Enter the device index as 1 for the mgmt interface |
Yes |
|
Subnet |
Select the subnet. |
Yes |
|
Security Group |
Select the same 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 more detailed information. Copy
|
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.
Create a Launch Template for Out of Band GigaVUE V Series Node
This step is optional. You can create a launch template for Out of Band GigaVUE V Series Node if you wish to send to process the acquired traffic.
Enter or select the following details to create a launch template for auto scaling groups in AWS.
Parameters |
Instructions |
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. |
Yes |
|
Firewall (security groups) |
Keep this blank and configure one or more security groups as part of the network interface. |
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 more detailed information. Copy
|
Yes |
Create an Auto Scaling group using a Launch Template for Out of Band GigaVUE V Series Node
This step is optional. You can create a auto scaling groups for Out of Band GigaVUE V Series Node if you wish to send to process the acquired traffic. 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.
In the Instances page, you can view the GigaVUE V Series Node instance deployed by the load balancer.
Create Endpoint Service
Enter or select the following details to create a endpoint service.
Parameters |
Instructions |
Reference |
Mandatory field |
---|---|---|---|
Endpoint service settings |
|||
Load Balancer Type |
Choose Gateway. |
Yes |
|
Available load balancers |
Select the gateway load balancer created. |
Yes |
|
Additional Settings |
|||
Supported IP address types |
Select both IPv4 and IPv6. |
Yes |
|
Tags |
Provide Key and Value for each tag. |
No |
Copy the end point service name.
Create VPC Endpoint
Enter or select the following details to create a VPC endpoint.
Parameters |
Instructions |
Reference |
Mandatory field |
---|---|---|---|
Endpoint settings |
|||
Type |
Choose Endpoint servies that use NLBs and GWLBs. |
Yes |
|
Service Settings |
|
||
Service name |
Paste the end point service name. |
Yes |
|
Network Settings |
|||
VPC |
Select the VPC |
Yes |
|
Availability Zone and subnets |
Select the zones and the corresponding subnets to which the VPC end point should be associated. VPC Endpoint uses this subnet to create a private link with the gateway load balancer. |
Yes |
|
IP Address Type |
Select Dual Stack. |
Yes |
After creating the endpoint, go to the service. Select the endpoint and click Actions > Accept endpoint connection request.
What to do Next
After creating load balancer and autoscaling groups, you must create a Monitoring Domain and launch the GigaVUE V Series Node in GigaVUE-FM. Refer to Deploy GigaVUE V Series Nodes for Inline V Series Solution.