UCT-C Solution (Controller and TAP) and GigaVUE‑FM Interaction

The following are the interactions between the UCT-C solution and GigaVUE‑FM:

• UCT-C Controller and TAP Registration
• UCT-C Controller and TAP Deregistration
• UCT-C Controller and TAP Heartbeats
• UCT-C Controller Connectivity
• Monitoring Domain and Traffic Policy

UCT-C Controller and TAP Registration

When a UCT-C Controller and TAP come up in the Kubernetes environment, it registers itself with GigaVUE‑FM.

Check the network requirements for the registration to be successful. For more information, refer to Network Firewall Requirements.

UCT-C supports IPv4 and IPv6 protocols. For more information, refer to Deploy UCT-C Controller and TAP in Kubernetes.

UCT-C Controller and TAP Deregistration

When UCT-C Controller and TAP is terminated normally, it sends the deregistration message to GigaVUE-FM. If UCT-C Controller and TAP goes down abnormally and GigaVUE-FM fails to receive a couple of heartbeats, it will get disconnected.

UCT-C Controller and TAP Heartbeats

GigaVUE-FM marks the heartbeat status of UCT-C Controller and TAP as Connected when it gets registered. After successful registration, UCT-C Controller and TAP sends heartbeats to GigaVUE-FM every 30 seconds. GigaVUE-FM scans the last received heartbeat of the registered UCT-C Controller and TAP pods and marks the heartbeat status periodically (1 minute). The following are the various scenarios where the heartbeat status changes:

• If 2 consecutive heartbeats are missed, GigaVUE-FM marks the status as Pending.
• If 3 consecutive heartbeats are missed, GigaVUE-FM marks the status as Disconnected.
• GigaVUE-FM purges disconnected or terminated UCT-C Controllers and TAPs after 7 days.

Note:  GigaVUE-FM generates an alarm for the disconnected UCT-C when three consecutive heartbeats are missed. Refer to Alarmsfor detailed information on Alarms.

UCT-C Controller Connectivity

After successful registration of UCT-C Controller, GigaVUE-FM periodically checks connectivity to Controller. The following are the various scenarios where the UCT-C Controller connectivity changes:

• If GigaVUE-FM can connect with the UCT-C Controller, the connectivity status will be marked as Reachable.
• If GigaVUE-FM cannot connect with the UCT-C Controller, the connectivity status will be marked as Unreachable.

Note:  You should ensure that the UCT-C Controller connectivity is Reachable before doing any configurations. If the connectivity shown for a UCT-C controller in a cluster is not reachable, the deployment for that cluster will not go through.

Monitoring Domain and Traffic Policy

You can configure and manage the Monitoring Domains, Clusters, Source Inventories, and Traffic Policies of UCT-C in GigaVUE-FM. For more information, refer to Configure UCT-C Controller and TAP through GigaVUE-FM.