Configure UCT-V Controller in Azure

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

To register UCT-V Controller in Azure Portal, use any one of the following methods.

• Register UCT-V Controller during Virtual Machine Launch
• Register UCT-V Controller after Virtual Machine Launch

Register UCT-V Controller during Virtual Machine Launch

In your Azure portal, to launch the UCT-V Controller init virtual machine and register UCT-V Controller using custom data, follow the steps given below:

1. In the Virtual machines page of the Azure Portal, select Create then Virtual machine. Then Create a Virtual Machine Page appears. For detailed information, refer to Create virtual machine topic in Azure Documentation.
   On the Advanced tab, enter the Custom Data as text in the following format and deploy the virtual machine. Enter the monitoring domain name and the connection name of the monitoring domain created earlier as the groupName and the subGroupName in the Custom Data. The UCT-V Controller uses this custom data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM. You can also install custom certificates to GigaVUE V Series Node or Proxy, refer to the below table for details:

   Field	User Data
   User data without custom certificate	Copy #cloud-config  write_files:  - path: /etc/gigamon-cloud.conf    owner: root:root    permissions: '0644'    content: |      Registration:         groupName: <Monitoring Domain Name>         subGroupName: <Connection Name>         user: <Username>         password: <Password>         remoteIP: <IP address of the GigaVUE-FM>         sourceIP: <IP address of UCT-V Controller> (Optional Field)         remotePort: 443
   User data with custom certificate	Copy #cloud-config  write_files:  - path: /etc/cntlr-cert.conf    owner: root:root    permissions: "0644"    content: |       -----BEGIN CERTIFICATE-----       <certificate content>       -----END CERTIFICATE-----  - path: /etc/cntlr-key.conf    owner: root:root    permissions: "400"    content: |       -----BEGIN PRIVATE KEY-----       <private key content>       -----END PRIVATE KEY-----  - path: /etc/gigamon-cloud.conf    owner: root:root    permissions: '0644'    content: |      Registration:          groupName: <Monitoring Domain Name>          subGroupName: <Connection Name>          user: <Username>          password: <Password>          remoteIP: <IP address of the GigaVUE-FM>          sourceIP: <IP address of UCT-V Controller> (Optional Field)          remotePort: 443

   Note:  User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the Userame and Password created in the Add Users Section.

The UCT-V Controller deployed in your Azure portal appears on the Monitoring Domain page of GigaVUE-FM.

 

Register UCT-V Controller after Virtual Machine Launch

To register UCT-V Controller after launching a Virtual Machine using a configuration file, follow the steps given below:

1. Log in to the UCT-V Controller.
2. Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following custom data.
   
   Copy

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

   Note:  User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.

3. Restart the UCT-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. If you wish to assign a static IP address, follow the steps below:

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

   network:
           version: 2
           renderer: networkd
           ethernets:
                   ens3:
                           addresses:
                                   - <IP address>
                           gateway: <IP address>
                   ens4:
                           addresses:
                                   - <IP address>
                           gateway: <IP address>
                   ens5:
                           addresses:
                                   - <IP address>
                           gateway: <IP address>

4. Save the file.
5. Restart theUCT-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 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the UCT-V Controller and if that fails as well then GigaVUE‑FM unregisters the UCT-V Controller and it will be removed from GigaVUE‑FM.