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:

  1. Create a Target Group
  2. Create a Gateway Load Balancer
  3. Create a Launch Template for Inline GigaVUE V Series Node
  4. Create an Auto Scaling group using a Launch Template for Inline GigaVUE V Series Node
  5. Create a Launch Template for Out of Band GigaVUE V Series Node
  6. 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 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

Port

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.

 

Unhealthy threshold

Enter 2 as the threshold value.

  

Timeout

Enter 2 seconds as the timeout.

  

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.

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)

Create a Gateway Load Balancer

Yes

Availability Zone and subnets

Select the zones and the corresponding subnets where you want to launch the 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

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'll have to delete and recreate the load balancer.

After creating 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

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.

Create a launch template for an Auto Scaling group

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.

Security Group

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

Create a launch template for an Auto Scaling group

Yes

Subnet

The subnet is automatically assigned by AWS.

 

Security Group

Choose the security group.

  

Network interface 2 - Management Interface

Device Index

Enter the device index as 1 for the mgmt interface

Create a launch template for an Auto Scaling group

Yes

Subnet

Select the subnet.

 

Security Group

Select the same security group.

    

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 
#cloud-config
write_files:
  - path: /etc/gigamon-cloud.conf
    owner: root:root
    permissions: '0644'
    content: |
      Registration:
        groupName: <Enter a name for the Monitoring Domain>
        subGroupName: <Enter the VPC Name>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443
        token: <token>
- 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

Instructions

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

Choose launch template or configuration

 

VPC

Select the VPC for your targets (GigaVUE V Series Node)

  

Availability Zone and subnets

Select the zones and the corresponding subnets where you want to launch the GigaVUE V Series Node.

  

Integrate with other services

Load balancing

Choose Attach to an existing load balancer option.

  

Creating an Auto Scaling group using a launch template

  

Existing load balancer target groups

Select the Target Group created above.

  

Attach to an existing load balancer

Choose the Choose from your load balancer target groups option.

Yes

Configure group size and scaling

Group Size

Enter the Min 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 tags

Tags

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

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,

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 more detailed information.

Copy 
#cloud-config
write_files:
  - path: /etc/gigamon-cloud.conf
    owner: root:root
    permissions: '0644'
    content: |
      Registration:
        groupName: <Enter a name for the Monitoring Domain>
        subGroupName: <Enter the VPC Name>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443
        token: <token>

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

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.

Parameters

Instructions

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.

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.

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.