Configure UCT-V in Azure

Notes:

You can deploy UCT-Vs using a third-party orchestrator on Linux and Windows platforms. For details, refer to Linux UCT-V Installation and Windows UCT-V Installation.
You can configure more than one UCT-V Controller for a UCT-V. If one UCT-V Controller goes down, the UCT-V registration happens through another active UCT-V Controller.

To register UCT-V after launching a Virtual Machine using a configuration file, follow these steps:

Install the UCT-V on the Linux or Windows platform. For detailed instructions, refer to Linux UCT-V Installation and Windows UCT-V Installation.
Log in to the UCT-V. For details, refer to Default Login Credentials.

Create a local configuration file and enter the following custom data.

/etc/gigamon-cloud.conf is the local configuration file on the Linux platform.
C:\ProgramData\uctv\gigamon-cloud.conf is the local configuration file on the Windows platform.

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)

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 that fails, then GigaVUE‑FM unregisters UCT-V and it is removed from GigaVUE‑FM.