Configure GigaVUE V Series Node and GigaVUE V Series Proxy in Azure

It is not mandatory to register GigaVUE V Series Nodes via GigaVUE V Series however, if there is a large number of nodes connected to GigaVUE-FM or if the user does not wish to reveal the IP addresses of the 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.
When deploying GigaVUE V Series Node using GigaVUE V Series Proxy, deploy the GigaVUE V Series Proxy first and provide the IP address of the proxy as the Remote IP of the GigaVUE V Series Node.

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

Register GigaVUE V Series Node and GigaVUE V Series Proxy during Virtual Machine Launch

To register GigaVUE V Series Node and GigaVUE V Series Proxy using the custom data in Azure Portal, 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. 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. he GigaVUE V Series Node and GigaVUE V Series Proxy 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> or <IP address of the Proxy>
        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> or <IP address of the Proxy>
         remotePort: 443

You can register your GigaVUE V Series Node directly with GigaVUE‑FM or you can use GigaVUE V Series Proxy to register your GigaVUE V Series Node with GigaVUE‑FM. If you wish to register GigaVUE V Series Node 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 Node using GigaVUE V Series Proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.
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.

Register GigaVUE V Series Node and GigaVUE V Series Proxy after Virtual Machine Launch

To register 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. Refer to Default Login Credentials for UCT-V Controller default login credentials.
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> or <IP address of the Proxy>
    remotePort: 443
```
- You can register your GigaVUE V Series Node directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series with GigaVUE‑FM. If you wish to register GigaVUE V Series Node 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 Node using GigaVUE V Series Proxy then, enter the remotePort value as 8891 and remoteIP as <IP address of the Proxy>.
- 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.
Restart the GigaVUE V Series Proxy service.
- GigaVUE V Series Node:
```
$ sudo service vseries-node restart
```
- GigaVUE V Series Proxy:
```
$ sudo service vps restart
```

The deployed GigaVUE V Series Node or Proxy registers with the GigaVUE-FM. After successful registration, the GigaVUE V Series Node or 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 Node or Proxy and if that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series Node or Proxy and it will be removed from GigaVUE‑FM.

If you are using Azure GUI to create the virtual machine for GigaVUE V Series Node then data NIC must be attached to GigaVUE V Series Node after creating the virtual machine. Refer to Create GigaVUE V Series Node with Management and Data NIC Attached using Azure GUI for more detailed information.