Configure UCT-V Controller in AWS

You can deploy UCT-V Controller in AWS using any of the following methods: 

Register UCT-V Controller using User Data

To register UCT-V Controller 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 UCT-V Controller.

Launch an instance using defined parameters

 

 

Yes

Instance Type

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

Yes

Advanced Details

 

Metadata Version

Select V2 only (token required) as the version.

Yes

User Data

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: <VPC Name>
        token: <Token>
        remoteIP: <IP address of the GigaVUE-FM>
        sourceIP: <IP address of UCT-V Controller> (Optional Field)
        remotePort: 443

 

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

Register UCT-V Controller using a Configuration File

To register UCT-V Controller using a configuration file:

  1. Log in to the UCT-V Controller.
  2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to UCT-V Controller, 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>
       sourceIP: <IP address of UCT-V Controller> (Optional Field)
       remotePort: 443
  3. Restart the UCT-V Controller service.
    $ sudo service uctv-cntlr restart

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

1.   Navigate to /etc/netplan/ directory.
2. Create a new .yaml file.

Note:  Do not use the default 50-cloud-init.yaml file.

3. Update the file as shown in the following sample:
Copy 
network:
  version: 2
  renderer: NetworkManager
  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: NetworkManager
  ethernets:
    ens3:
      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
4. Save the file.
5. Apply the configuration. 
$ sudo netplan apply