Configure GigaVUE Fabric Components using AWS

This section provides instructions on how to register GigaVUE fabric components using AWS EC2 or a configuration file.

Recommended Instance Type

The following table lists the recommended instance type for deploying the fabric components:

Fabric Component	Machine type
GigaVUE V Series Node	c5n.xlarge
UCT-V Controller	t2.medium

Deployment Guidelines

Points to remember before deploying the fabric components using generic mode:

Set the correct MTU for tunnels: Use 8950 for IPv4 tunnels and 8930 for IPv6. To update the Traffic Acquisition Tunnel MTU:
1. Select the monitoring domain.
2. Select the Edit Monitoring Domain option.
3. Enter the Traffic Acquisition Tunnel MTU value and select Save.

Note: Set the correct MTU before deploying the Monitoring Session. If not, you must undeploy and redeploy the session after updating the MTU.

When deploying the fabric components using generic mode, you must use subGroupName in the registration data as the connection name.
You can also create a Monitoring Domain under Third Party Orchestration and provide the monitoring domain name and the connection name as groupName and subGroupName in the registration data. For details, refer to Create Monitoring Domain.
You can use only UCT-V or Customer Orchestrated Source as the traffic acquisition method when using generic mode.
When you deploy the fabric components using Third Party Orchestration, you cannot delete the Monitoring Domain without unregistering the registered fabric components.
GigaVUE V Series Node must have a minimum of two Networks Interfaces (NIC) attached to it, a management NIC and a data NIC. You can add both these interfaces when deploying the GigaVUE V Series Node in AWS. For details, refer to the Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.
Create tokens in the User Management page in GigaVUE-FM. For details, refer to Configure Tokens .
When GigaVUE‑FM is 6.10.00 or above and the Fabric Components are on (n-1) or (n-2) versions, you must create a Username and Password instead of using tokens in the registration data. For details, refer to the Configure Role-Based Access for Third-Party Orchestration section in the v6.9 Documentation.

In your AWS EC2, you can configure the following GigaVUE fabric components:

Configure UCT-V Controller in AWS
Configure GigaVUE Fabric Components using AWS
Configure GigaVUE Fabric Components using AWS

Configure UCT-V Controller in AWS

You can configure more than one UCT-V Controller in a monitoring domain.

To register UCT-V Controller in AWS EC2, use any one of the following methods:

Register UCT-V Controller during Instance Launch
Configure GigaVUE Fabric Components using AWS

Register UCT-V Controller during Instance Launch

In your AWS EC2 portal, you can launch the UCT-V Controller AMI instance and register UCT-V Controller using user data.

Perform the following steps:

On the Instances page of AWS EC2, select Launch instances. The Launch Instance wizard appears. For details, refer to the Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.

On the Step 3: Configure Instance Details tab:

In the Advanced details section, select V2 only from the Metadata version drop-down list.

Enter the User data as text in the following format and deploy the instance. The UCT-V Controller 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: <Connection Name>
        token: <Token>
        remoteIP: <IP address of the GigaVUE-FM>
        sourceIP: <IP address of UCT-V Controller> (Optional Field)
        remotePort: 443

Go to Instances > Actions > Instance Settings > Edit user data and edit the user data.

The UCT-V Controller deployed in AWS EC2 appears on the Monitoring Domain page of GigaVUE‑FM.

Register UCT-V Controller after Instance Launch

To register UCT-V Controller after launching a Virtual Machine using a configuration file, perform the following steps:

Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following user data.

Copy

Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <Connection Name>
    token: <Token>
    remoteIP: <IP address of the GigaVUE-FM>
    sourceIP: <IP address of UCT-V Controller> (Optional Field)
    remotePort: 443

Restart theUCT-V Controller service.
```
$ sudo service uctv-cntlr restart
```

Assign Static IP address for UCT-V Controller

By default, the UCT-V Controller gets assigned an IP address using DHCP.

To assign a static IP address, perform the following steps:

Navigate to /etc/netplan/ directory.
Create a new .yaml file. (Other than the default 50-cloud-init.yaml file)
Update the file as shown in the following sample:

Copy

network:
  version: 2
  renderer: networkd
  ethernets:
    <interface>:                # Replace with your actual interface name (e.g., eth0)
      dhcp4: no
      dhcp6: no
      addresses:
        - <IPV4/24>             # e.g., 192.168.1.10/24
        - <IPV6/64>             # e.g., 2001:db8:abcd:0012::1/64
      nameservers:
        addresses:
          - <DNS_IPV4>          # e.g., 8.8.8.8
          - <DNS_IPV6>          # e.g., 2001:4860:4860::8888
      routes:
        - to: 0.0.0.0/0
          via: <IPV4_GW>        # e.g., 192.168.1.1
        - to: ::/0
          via: <IPV6_GW>        # e.g., 2001:db8:abcd:0012::fffe
                        
Example netplan config:

network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      addresses:
         -192.168.1.10/24
         -2001:db8:1::10/64
      nameservers:
        addresses:
          -8.8.8.8
          -2001:4860:4860::8888
      routes:
        -to: 0.0.0.0/0
          via: 192.168.1.1
          metric: 100
        -to: ::/0
           via: 2001:db8:1::1
          metric: 100

Save the file.
Restart the UCT-V Controller service.

$ sudo service uctv-cntlr restart

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

Configure UCT-V in AWS

Note: Deployment of GigaVUE fabric components through a third-party orchestrator is supported on Linux and Windows platforms. Refer to Linux UCT-V Installation andWindows UCT-V Installation for detailed information on Linux and Windows UCT-V.

You need to register UCT-V through the registered UCT-V Controller. It communicates through PORT 8891.

Note: You can configure more than one UCT-V Controller for a UCT-V, so that if one UCT-V Controller goes down, the UCT-V registration will happen through another Controller that is active.

To register UCT-V using a configuration file, follow the steps:

Install the UCT-V in the Linux or Windows platform. For details, refer to Linux UCT-V Installation and Windows UCT-V Installation.
Log in to the UCT-V.
Create a local configuration file and enter the following user data.
- /etc/gigamon-cloud.conf is the local configuration file in Linux platform.
- C:\ProgramData\uctv\gigamon-cloud.conf is the local configuration file in Windows platform.
- When creating C:\ProgramData\uctv\gigamon-cloud.conf file, ensure that the file name extension is .conf. To view the file name extension in Windows, follow the steps given below:
  1. Go to File Explorer and open the File Location.
  2. On the top navigation bar, click View.
  3. In the View tab, enable the File name extensions check box.
Copy
```
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <Connection Name>
    token: <Token>
    remoteIP: <IP address of the UCT-V Controller 1>, <IP address of the UCT-V Controller 2>
    sourceIP: <IP address of UCT-V> (Optional Field)
```
NOTE: If you are using multiple interface in UCT-V and UCT-V Controller is not connected to the primary interface, then add the following to the above registration data:
```
localInterface:<Interface to which UCT-V Controller is connected>
```
Restart the UCT-V service.
- Linux platform:
```
$ sudo service uctv restart
```
- Windows platform: Restart from the Task Manager.

The deployed UCT-V registers with the GigaVUE-FM through the UCT-V Controller. After successful registration the UCT-V sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, UCT-V status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE‑FM, then GigaVUE‑FM tries to reach the UCT-V. If the effort fails, then GigaVUE‑FM unregisters the UCT-V to remove it from GigaVUE‑FM.

Configure GigaVUE V Series Nodes and V Series Proxy in AWS

Note: It is not mandatory to register GigaVUE V Series Nodes via V Series proxy however, if there is a large number of nodes connected to GigaVUE-FM or if you do not wish to reveal the IP addresses of the GigaVUE V Series Nodes, then you can register your nodes using GigaVUE V Series Proxy. In this case, GigaVUE‑FM communicates with GigaVUE V Series Proxy to manage the GigaVUE V Series Nodes.

To register GigaVUE V Series Node and GigaVUE V Series Proxy in AWS EC2, use any one of the following methods.

Configure GigaVUE Fabric Components using AWS
Register GigaVUE V Series Node and GigaVUE V Series Proxy after Instance Launch

Register GigaVUE V Series Node and GigaVUE V Series Proxy during Instance Launch

On the Instances page of AWS EC2, select Launch instances. The Launch Instance wizard appears. For details, refer to Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.

On the Step 3: Configure Instance Details tab:

In the Advanced details section, select V2 only from the Metadata version drop-down list.

Enter the User data as text in the following format and deploy the instance. The GigaVUE V Series Nodes or 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: <Connection Name>
        token: <Token>
        remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
        remotePort: 443

NOTE: You can register your GigaVUE V Series Nodes directly with GigaVUE‑FM or you can use V Series Proxy to register your GigaVUE V Series Nodes with GigaVUE‑FM. If you wish to register GigaVUE V Series Nodes directly, enter the remotePort value as 443 and the remoteIP as <IP address of the GigaVUE‑FM> or if you wish to deploy GigaVUE V Series Nodes using V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.

You can navigate to Instances > Actions > Instance Settings > Edit user data and edit the user data.

Register GigaVUE V Series Node and GigaVUE V Series Proxy after Instance Launch

To register GigaVUE V Series Node and GigaVUE V Series Proxy after launching the virtual machine using a configuration file, follow the steps given below:

Log in to the GigaVUE V Series Node or Proxy.
Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following user data.
Copy
```
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <Connection Name>
    token: <Token>
    remoteIP: <IP address of the GigaVUE-FM> or <IP address of the proxy>
    remotePort: 443
```
NOTE: You can register your GigaVUE V Series Nodes directly with GigaVUE‑FM or you can use GigaVUE V Series proxy to register your GigaVUE V Series Nodes with GigaVUE‑FM. If you wish to register GigaVUE V Series Nodes directly, enter the remotePort value as 443 and the remoteIP as <IP address of the GigaVUE‑FM> or if you wish to deploy GigaVUE V Series Nodes using V Series proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.
Restart the GigaVUE V Series Node or Proxy service.
- V Series node:
```
$ sudo service vseries-node restart
```
- V Series proxy:
```
$ sudo service vps restart
```

The deployed GigaVUE V Series Proxy registers with the GigaVUE-FM. After successful registration the GigaVUE V Series Proxy sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, the fabric component status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the GigaVUE V Series proxy and if that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series proxy and it will be removed from GigaVUE‑FM.

Note: When the GigaVUE V Series Node is stopped or terminated from the AWS, it does not send any unregistration request and GigaVUE‑FM unregisters the GigaVUE V Series Node soon after.

Assign Static IP address for GigaVUE V Series

By default, the GigaVUE V Series gets assigned an IP address using DHCP.

To assign a static IP address, perform the following steps:

Navigate to /etc/netplan/ directory.
Create a new .yaml file. (Other than the default 50-cloud-init.yaml file)
Update the file as shown in the following sample:

Copy

network:
  version: 2
  renderer: networkd
  ethernets:
    <interface>:                # Replace with your actual interface name (e.g., eth0)
      dhcp4: no
      dhcp6: no
      addresses:
        - <IPV4/24>             # e.g., 192.168.1.10/24
        - <IPV6/64>             # e.g., 2001:db8:abcd:0012::1/64
      nameservers:
        addresses:
          - <DNS_IPV4>          # e.g., 8.8.8.8
          - <DNS_IPV6>          # e.g., 2001:4860:4860::8888
      routes:
        - to: 0.0.0.0/0
          via: <IPV4_GW>        # e.g., 192.168.1.1
        - to: ::/0
          via: <IPV6_GW>        # e.g., 2001:db8:abcd:0012::fffe
                        
Example netplan config:

network:
  version: 2
  renderer: networkd
  ethernets:
    ens160:
      addresses:
        - 10.114.53.24/21
      dhcp4: no
      dhcp6: no
      accept-ra: false
      routes:
        - to: 10.114.48.1/32
          scope: link
        - to: default
          via: 10.114.48.1

Save the file.
Restart the GigaVUE V Series service.

$ sudo service vseries-node restart

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