Configure GigaVUE V Series Nodes and GigaVUE V Series Proxy in AWS

You can deploy GigaVUE V Series Nodes and GigaVUE V Series Proxy in AWS using any of the following methods: 

Register GigaVUE V Series Node and GigaVUE V Series Proxy using User Data

This section provides information on how to register GigaVUE V Series and GigaVUE V Series Proxy (if used) when launching the virtual machine in AWS using user data. For details, refer to the following sections:

Register GigaVUE V Series Nodes without GigaVUE V Series Proxy using User Data

To register GigaVUE V Series Node using the user data in AWS GUI, enter or select the following details:

Parameters

Instructions

Reference

Mandatory field

Application and OS Images (Amazon Machine Image)

Select AMI of the GigaVUE V Series Node.

Launch an instance using defined parameters

 

 

Yes

Instance Type

Select an Instance Type from the drop-down list. The recommended instance type is c5n.xlarge.

Yes

Advanced Details

 

Metadata Version

Select V2 only (token required) as the version.

Yes

User Data

The GigaVUE V Series Node uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.

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

 

Register GigaVUE V Series Nodes with GigaVUE V Series Proxy using User Data

When deploying GigaVUE V Series Node with GigaVUE V Series Proxy, deploy the GigaVUE V Series Proxy first and then deploy the GigaVUE V Series Node.

Register GigaVUE V Series Proxy using User Data

To register GigaVUE V Series Proxy using the user data in AWS GUI, enter or select the following details:

Parameters

Description

Reference

Mandatory field

Application and OS Images (Amazon Machine Image)

Select AMI of the GigaVUE V Series Proxy.

Launch an instance using defined parameters

 

 

Yes

Instance Type

Select an Instance Type from the drop-down list.

Yes

Advanced Details

 

Metadata Version

Select V2 only (token required) as the version.

Yes

User Data

The GigaVUE V Series Proxy uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.

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

Yes

Register GigaVUE V Series Node when using GigaVUE V Series Proxy using User Data

To register GigaVUE V Series Node via GigaVUE V Series Proxy using the user data in AWS GUI, enter or select the following details:

Parameters

Instructions

Reference

Mandatory field

Application and OS Images (Amazon Machine Image)

Select AMI of the GigaVUE V Series Node.

Launch an instance using defined parameters

 

 

Yes

Instance Type

Select an Instance Type from the drop-down list. The recommended instance type is c5n.xlarge.

Yes

Advanced Details

 

Metadata Version

Select V2 only (token required) as the version.

Yes

User Data

The GigaVUE V Series Node uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE‑FM.

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 V Series Proxy>
        remotePort: 8891

Yes

Register GigaVUE V Series Node and Proxy using a Configuration File

This section provides information on how to register GigaVUE V Series Node and GigaVUE V Series Proxy (if used) using a configuration file after launching the virtual machine in AWS. For details, refer to the following sections:

Register GigaVUE V Series Nodes without GigaVUE V Series Proxy using a Configuration file

To register GigaVUE V Series Node using a configuration file,

  1. Log in to the GigaVUE V Series Node.
  2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to GigaVUE V Series Node, refer to the below table for details:
    Copy
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <VPC Name>
            token: <Token>
            remoteIP: <IP address of the GigaVUE-FM>
            remotePort: 443
  3. Restart the GigaVUE V Series Node service. 
    $ sudo service vseries-node restart

Register GigaVUE V Series Nodes with GigaVUE V Series Proxy using a Configuration file

When deploying GigaVUE V Series Node with GigaVUE V Series Proxy, deploy the GigaVUE V Series Proxy first and then deploy the GigaVUE V Series Node.

Register GigaVUE V Series Proxy using Configuration file:

  1. Log in to the GigaVUE V Series Node.
  2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to GigaVUE V Series Node. For details, refer to the below table.
    Copy
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <VPC Name>
            token: <Token>
            remoteIP: <IP address of the GigaVUE-FM>
            remotePort: 443
  3. Restart the GigaVUE V Series Proxy service. 
    $ sudo service vps restart

Register GigaVUE V Series Node when using GigaVUE V Series Proxy using Configuration File

To register GigaVUE V Series Node using a configuration file,

  1. Log in to the GigaVUE V Series Node.
  2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to GigaVUE V Series Node, refer to the below table for details:
    Copy
         Registration:
            groupName: <Monitoring Domain Name>
            subGroupName: <VPC Name>
            token: <Token>
            remoteIP: <IP address of the GigaVUE V Series Proxy>
            remotePort: 8891
  3. Restart the GigaVUE V Series Node service. 
    $ sudo service vseries-node restart

The deployed GigaVUE V Series node or proxy registers with GigaVUE‑FM. After successful registration, every 30 seconds the GigaVUE V Series node or proxy sends heartbeat messages to GigaVUE‑FM. If one heartbeat is missing ,the fabric components status appears as Unhealth'. If more than five heartbeats fail to reach GigaVUE‑FM, then GigaVUE‑FM tries to reach the GigaVUE V Series node or proxy. If that fails, then GigaVUE‑FM unregisters the GigaVUE V Series node or proxy and removes from GigaVUE‑FM.