Configure GigaVUE Fabric Components

You can use your own orchestration system to deploy the GigaVUE fabric components instead of using GigaVUE‑FM to deploy the fabric components.

The GigaVUE fabric components register themselves with GigaVUE-FM using the information provided by you. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM. After launching the fabric component images in your orchestration system use the registration data provided in the sections below to deploy your fabric components to GigaVUE-FM. Health status of the registered nodes is determined by the heartbeat messages sent from the respective nodes.

This section provides step-by-step information on how to register GigaVUE fabric components using your own orchestration system or a configuration file.

Configure UCT-V Controller

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

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

Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following custom data.

Registration:

	groupName: <Monitoring Domain Name>

	subGroupName: <VPC ID>

	user: orchestration

	password: orchestration123A!

	remoteIP: <IP address of the GigaVUE-FM>

	remotePort: 443

Restart the UCT-V Controller service.
```
$ sudo service uctv-cntlr restart
```

The deployed UCT-V Controller registers with the GigaVUE-FM.

Configure UCT-V

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

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 the instance using a configuration file, refer to Configure GigaVUE Fabric Components topic for more detailed information.

Configure GigaVUE V Series Node and GigaVUE V Series Proxy

Note: It is not mandatory to register GigaVUE V Series Nodes via V Series proxy however, if there are a large number of nodes connected to GigaVUE-FM or if you do 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.

To register GigaVUE V Series Proxy or node after launching the instance using a configuration file, follow the steps given below:

Log in to the GigaVUE V Series Proxy or Node.
Create a local configuration file (/etc/gigamon-cloud.conf) and enter the following custom data.
```
Registration:
```
```
	groupName: <Monitoring Domain Name>
```
```
	subGroupName: <VPC ID>
```
```
	user: orchestration
```
```
	password: orchestration123A!
```
```
	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 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>.
- Use only the default user and password details given in the custom data.
Restart the GigaVUE V Series proxy or node service.
- GigaVUE V Series node:
```
$ sudo service vseries-node restart
```
- GigaVUE V Series proxy:
```
$ sudo service vps restart
```

The deployed GigaVUE V Series proxy or node registers with the GigaVUE-FM.

After successful registration, the fabric components send heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, the visibility node status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the fabric components and if that fails GigaVUE‑FM unregisters the fabric component and it will be removed from GigaVUE‑FM.

In the monitoring domain page you can view all the deployed fabric components and UCT-Vs.