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

Prerequisites

  • Create or update Security Group policies of GigaVUE Cloud Suite components. Refer to Network Security Groupstopic for detailed information.

Points to Note:

  • Azure only supports North-South traffic monitoring with Gateway Load Balancer.

Perform the following steps to configure a gateway load balancer in Azure:

  1. Create a Gateway Load Balancer
  2. Create a Virtual Machine Scale Set for Inline GigaVUE V Series Node
  3. Create a Public Load Balancer
  4. Create a Virtual Machine Scale Set for Out-of-Band GigaVUE V Series Node

Create a Gateway Load Balancer

Enter or select the following details as mentioned in the table to create a gateway load balancer in Azure.

Parameters

Instructions

Reference

Mandatory field

Basics

Region

Select the region.

Create a Gateway Load Balancer

 

 

 

Yes

SKU

Select Gateway.

Yes

Type

Select Internal.

Yes

Tier

Select Regional.

Yes

FrontEnd IP Configuration

IP Version

Select based on the requirement.

 

Create a Gateway Load Balancer

 

Yes

Virtual Network

Select your virtual network.

Yes

Subnet and IP Assignment

Select your subnet and choose Dynamic for assignment.

Yes

Backend Pool

Backend Pool Configuration

Select NIC.

Create a Gateway Load Balancer

 

 

 

 

 

 

Yes

Type

Choose Internal and External.

Yes

Internal and External Ports

Use default values.

Note:  If you change the port values here, update the same ports in the Custom data and cloud-init field when creating the Virtual Machine Scale Set.

Yes

VMSS Selection

Select the VMSS as part of IP configuration. Choose the data NIC of the VMSS.

Yes

Load Balancing Rules

Yes

Frontend IP Address, Backend Pool

Select the already created ones.

Yes

Session Persistence

Select None.

Yes

Health Checks

Protocol

Select TCP as the protocol.

  

Yes

Port

Enter 8889 as the port.

Yes

Interval

Enter 5 seconds as the approximate amount of time, in seconds.

Yes

Create a Virtual Machine Scale Set for Inline GigaVUE V Series Node

Enter or select the following details as mentioned in the table to create a VMSS in Azure.

Parameters

Instructions

Reference

Mandatory field

Orchestration

Orchestration Mode

Select Uniform as the orchestration mode.

Create a Virtual Machine Scale Set

Yes

Scaling Mode

Choose Autoscaling.

Yes

Availability Zones

Choose if you want to use zones for high availability.

No

Scaling Configuration

Default Instance Count

Enter the Initial Instance Count as 0.

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.

  

Autoscale Virtual Machine Scale Sets in the Azure portal.

  

Condition

Choose a metric-based scaling condition (e.g., CPU usage, network traffic).

Yes

Metric Source

Select the metric (e.g., Average CPU Percentage).

Yes

Scale out

Set conditions like greater than 70% for scaling up.

Yes

Scale in

Set conditions like less than 20%.

 

Cooldown Period

Set a cooldown period to prevent rapid scaling.

Yes

Instance Details

   

Instance Type

Choose Standard_DS4_v4 as the VM size.

Create a Virtual Machine Scale Set

 

Image

Select the GigaVUE V Series Node image.

  

Authentication Type

Choose SSH public key.

  

Username

Enter a user name. Do not use admin or gigamon.

  

Networking

Virtual Network

Select the required VNET.

Networking for Azure Virtual Machine Scale Sets

 

Yes

Subnet Selection

Choose the appropriate subnet for NVAs.

Yes

NIC Configuration

GigaVUE V Series Node requires two NICs. One for Mgmt and one for Data, ensure to add the second NIC.

Enable Accelerated Networking for the second NIC (Data Interface).

Yes

Upgrade Mode

Choose Automatic.

  

Gateway Load Balancer Integration

Backend Pool

Add VMSS to the Backend Pool in Gateway Load Balancer (GWLB).

Networking for Azure Virtual Machine Scale Sets

Yes

Advanced

Custom data and cloud init

Enter the Custom 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 Monitoring Domain>
        subGroupName:  <Enter a name for Connection>
        remoteIP: <IP address of GigaVUE-FM>
        remotePort: 443
        token: <Token generated in GigaVUE-FM>
  - path: /etc/vseries-inline.conf
    owner: root:root
    permissions: '0644'
    content: ""

Custom Data with Internal and External Ports

If you have modified the internal and external port values in the Gateway Load Balancer, use the following custom data:

Copy 
#cloud-config
write_files:
  - path: /etc/gigamon-cloud.conf
    owner: root:root
    permissions: '0644'
    content: |
      Registration:
        groupName: <Enter a name for Monitoring Domain>
        subGroupName:  <Enter a name for Connection>
        remoteIP: <IP address of GigaVUE-FM>
        remotePort: 443
        token: <Token generated in GigaVUE-FM>
  - path: /etc/vseries-inline.conf
    owner: root:root
    permissions: '0644'
    content: |
      tunnel: vxlan
      external_port : <Enter the port value>
      external_vni  : <Enter the port value>
      internal_port : <Enter the port value>
      internal_vni  : <Enter the port value>
  

Yes

Create a Public Load Balancer

Enter or select the following details as mentioned in the table to create a public load balancer in Azure.

Parameters

Instructions

Reference

Mandatory field

Basics

Region

Select the region.

Create a Public Gateway Load Balancer

 

 

 

Yes

SKU

Select Standard.

Yes

Type

Select Public.

Yes

Tier

Select Regional.

Yes

FrontEnd IP Configuration

IP Type

Select IP Address as the IP type.

Create a Public Gateway Load Balancer

 

 

 

Yes

Public IP address

Select the public IP address from the drop-down list.

Yes

Gateway Load Balancer

Select the Load balancer created in the previous step.

Yes

Backend Pool

Backend Pool Configuration

Select IP Address.

Create a Public Gateway Load Balancer

 

 

 

Yes

IP Address

Specify the private IP address of the VM .

  

Load Balancing Rules

Yes

Frontend IP Address, Backend Pool

Select the already created ones.

Yes

Protocol

Select TCP as the protocol.

  

Port

Enter 80 as the port.

  

Health Probe

Create a new Health Probe with TCP Protocol, Port 22, and 5-second attempt interval.

Yes

Session Persistence

Select None.

Yes

(Optional) After creating the Public Load balancer, you can create outbound rules in Azure. Refer to Outbound rules Azure Load Balancer section in Azure Documentation.

Create a Virtual Machine Scale Set for Out-of-Band GigaVUE V Series Node

This step is optional. You can create a VMSS for Out of Band GigaVUE V Series Node if you wish to send to process the acquired traffic.

Enter or select the following details as mentioned in the table to create VMSS in Azure.

Parameters

Description

Reference

Mandatory field

Orchestration

Orchestration Mode

Select Uniform as the orchestration mode.

Create a Virtual Machine Scale Set

Yes

Scaling Mode

Choose Autoscaling.

Yes

Availability Zones

Choose if you want to use zones for high availability.

No

Scaling Configuration

Default Instance Count

Enter the Initial Instance Count as 0.

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.

  

Autoscale Virtual Machine Scale Sets in the Azure portal.

  

Condition

Choose a metric-based scaling condition (e.g., CPU usage, network traffic).

Yes

Metric Source

Select the metric (e.g., Average CPU Percentage).

Yes

Scale out

Set conditions like greater than 70% for scaling up.

Yes

Scale in

Set conditions like less than 20%.

 

Cooldown Period

Set a cooldown period to prevent rapid scaling.

Yes

Instance Details

   

Instance Type

Choose Standard_DS4_v4 as the VM size.

Create a Virtual Machine Scale Set

 

Image

Select the GigaVUE V Series Node image.

  

Authentication Type

Choose SSH public key.

  

Username

Enter a user name. Do not use admin.

    

Networking

Virtual Network

Select the required VNET.

Networking for Azure Virtual Machine Scale Sets

 

Yes

Subnet Selection

Choose the appropriate subnet for NVAs.

Yes

NIC Configuration

GigaVUE V Series Node requires two NICs. One for Mgmt and one for Data, ensure to add the second NIC.

Enable Accelerated Networking for the second NIC (Data Interface).

Yes

Upgrade Mode

Choose Automatic.

    

Advanced

Custom data and cloud init

Enter the Custom 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 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 Monitoring Domain>
        subGroupName: <Enter a name for Connection>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443
        token: <token>    
  

Yes

What to do Next

After configuring the gateway load balancer in Azure, 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 Azure accounts with Gatewayload balancer configured.