UCT and GigaVUE‑FM Interaction

Following are the interactions between UCT and GigaVUE‑FM:

• UCT Registration
• UCT Deregistration
• UCT Heartbeats
• Monitoring Domain and Traffic Policy

UCT Registration

When UCT comes up in the Kubernetes environment, UCT registers itself with GigaVUE‑FM. When GigaVUE‑FM is unreachable, UCT tries to reconnect infinite times. If the GigaVUE‑FM is unreachable even after the retries, Kubernetes deployment of UCT fails. UCT only supports IPv4 protocol. For more information, refer to Deploy UCT in Kubernetes

UCT Deregistration

When UCT is terminated normally, UCT sends the deregistration message to GigaVUE-FM. If UCT goes down abnormally, it will get deregistered when the GigaVUE-FM misses to receive couple of heartbeats.

UCT Heartbeats

Periodically, UCT sends heartbeats to GigaVUE-FM. By default, the status of UCT is marked as Connected. The following are the various scenarios where the UCT status changes:

• If 3 consecutive heartbeats are missed, GigaVUE-FM marks the status as Disconnected.
• If 2 consecutive heartbeats are missed, GigaVUE-FM marks the status as Pending.
• GigaVUE‑FM purges disconnected or terminated UCT taps after 30 days.

Monitoring Domain and Traffic Policy

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

Refer to the GigaVUE API Reference for detailed information on the REST APIs of UCT.