Topology

The sidebar calls it Topology; the page header says Network topology. Either way it answers one question: which of my clients are actually talking to their hub right now?

It’s worth opening once a client has connected at least once. Before that there’s nothing to see.

Hubs are grouped into clusters, worst first, with each client shown as a path beneath its hub.

What It Shows

Topology shows which clients are connected to which hub right now. Open it when a client is missing, quiet, or behaving unlike the others. It counts paths, one client’s connection to one hub, not clients. No live signal means the client is set up but nothing recent has been seen on that path. Topology doesn’t fix anything; it tells you whether to open Connections, Access rules, or Hubs.

How It Is Laid Out

The page counts paths, one client’s connection to one hub, rather than counting clients. A headline at the top says how many of them are connected, for example 0 of 13 paths connected.

Underneath, each hub is a cluster card carrying:

On the card	What it tells you
Live paths	Connected now, out of the total for that hub.
Attention	Paths with something wrong, as opposed to merely idle.
A 24-hour strip	When that hub last had traffic.
Client paths	One row per client, each with its own state.
Inspect	Opens that one hub without losing the overview.

Hubs are listed worst first, then by fleet size, so the one that needs you is at the top.

What The States Mean

Live

The client is connected and has recent signal.

Idle

Connected, with nothing happening. Normal for most of the day.

No live signal

The client exists and is set up, but nothing recent has been observed on this path.

No connected clients

The hub has client paths defined and none of them is connected.

Note

A brand-new connection shows No live signal for about ninety seconds while it reaches the hub. That’s expected, not a fault — see First Setup.

Finding One Thing

• Search by hub, client, or path when you know the name.
• Needs attention hides everything that’s behaving, which is the fastest way to read a large fleet. All brings it back.
• Clusters groups clients under their hub. Map draws the same information as a graph.
• Refresh re-reads live state before you act on something old.
• Inspect opens one hub’s detail without losing your place.

When Something Looks Wrong

If the page is empty, or a hub or client is not showing where you expected it, the filter is the usual culprit rather than the setup. A client that’s not showing at all has usually not been attached to this hub.

1. Clear the filter and refresh. Needs attention hiding the thing you are looking for is the most common false alarm.
2. Find the hub. Confirm it’s the hub you meant.
3. Read the client’s own state. Live, idle, and no-live-signal are three different situations.
4. Open the connection. Check it’s attached to this hub and its setup material was claimed — Connections.
5. Check its access rule if the connection is fine but behaving unexpectedly — Access rules.
6. Go back to Dashboard and confirm it tells the same story.

Tip

If several hubs and users are affected at once, check status.thalovant.com before recreating clients or editing access rules.

Topology Looks Right When

• every hub you expect is on the page;
• each client appears under the hub you attached it to;
• no filter is hiding the thing you came to look at;
• the live, idle and no-signal states match what the devices are really doing;
• Dashboard agrees.