Configure UCT-V in Azure

UCT-V should be registered via the registered UCT-V Controller and communicates through PORT 8891.

Note: Deployment of UCT-Vs through third-party orchestrator is supported on both Linux and Windows platforms. Refer to Linux UCT-V Installation and Windows UCT-V Installation Using MSI Package for detailed information.

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

Register UCT-V during Virtual Machine Launch

Note: Registering UCT-V during Virtual Machine Launch is not applicable for Windows Agents. You can register your Windows Agents after launching the Virtual machine, using a configuration file.

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

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. The UCT-V uses this custom 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>
        user: <Username>
        password: <Password>
        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)
        remotePort: 8891

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.
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>
```

Register UCT-V after Virtual Machine Launch

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 after launching a Virtual Machine using a configuration file, follow the steps given below:

Install the UCT-V in 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. Refer to Default Login Credentials for UCT-V Controller default login credentials.
Create a local configuration file and enter the following custom 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.
Copy
```
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <Connection Name>
    user: <Username>
    password: <Password>
    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)
    remotePort: 8891
```
- 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.
- 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, GigaVUE‑FM tries to reach the UCT-V and if that fails as well then GigaVUE‑FM unregisters the UCT-V and it will be removed from GigaVUE‑FM.