Fleet Management

Discover, pair, and manage multiple Exaviz boards from a single dashboard

Overview

Fleet management lets you monitor and control multiple Exaviz boards from a single dashboard. Boards on the same network discover each other automatically, and after a secure pairing process, you can view all your boards in one place.

How Discovery Works

Each board announces itself on the local network using mDNS (multicast DNS) on the _exaviz._tcp.local. service type. When you open the fleet view, any boards on the same network segment appear automatically in the discovery list.

Boards announce every 30 seconds. A board that has not been seen for 120 seconds is removed from the discovered list.

Each announcement includes:

  • Board serial number
  • Board type (Cruiser, Interceptor, etc.)
  • Firmware version
  • User-defined board name (if set)

Pairing Boards

Pairing establishes a secure trust relationship between two boards using Ed25519 cryptography. Both boards must confirm the pairing.

Step-by-Step

  1. Open the dashboard on Board A
  2. Switch to Fleet view (toggle in the header bar)
  3. Find Board B in the discovered boards list
  4. Click Pair next to Board B
  5. Both boards display a 6-digit confirmation code
  6. Verify the codes match on both screens (this prevents man-in-the-middle attacks)
  7. On Board A, click Confirm
  8. On Board B, a pairing notification appears. Click Accept

Trust is now mutual. Board A can see Board B’s status, and Board B can see Board A’s status.

Trust Rules

  • Trust is bilateral - each pairing connects exactly two boards
  • Trust is not transitive - if Board A pairs with B and C, Boards B and C do not automatically trust each other
  • For B to see C, B must pair with C directly
  • A full-mesh fleet of N boards requires N*(N-1)/2 pairings (3 pairings for 3 boards, 6 for 4 boards)

This is intentional. Non-transitive trust means compromising one board does not compromise the entire fleet.

Fleet Dashboard

Once boards are paired, the fleet view shows all trusted boards:

Grid View (Default)

Board cards in a 4-across grid. Each card shows:

  • Board name and serial number
  • Board type and firmware version
  • Online/offline status
  • Total PoE power draw
  • Number of active ports
  • CPU temperature and memory usage

Table View

Toggle to a comparative table with columns for serial, name, type, CPU temp, total power, memory, and status. Useful for quickly scanning a large fleet.

Quick Expand

Click a board card to expand it inline, showing a 2x2 grid of its PoE ports with real-time status. Lets you check port details without leaving the fleet view.

Drag-and-Drop Reorder

Drag board cards to arrange them in the order that makes sense for your deployment (e.g., by building, floor, or rack). The order is saved and persists across sessions.

Problematic Boards Float to Top

Boards with active alerts, PoE faults, or offline status automatically move to the top of the grid. This can be toggled on or off.

Fleet Status Bar

A summary bar at the top of the fleet view shows:

  • Total boards in the fleet
  • Number currently online
  • Total power draw across all boards
  • Total active PoE ports

Fleet-Wide Alerts

Alerts from all boards are aggregated. For example: “3 PoE faults across 2 boards” or “Board offline 5 minutes ago.”

Remote Operations

From the fleet view, you can perform operations on any paired board:

ActionDescription
RebootReboot an individual board (with confirmation dialog)
Enable all portsTurn on all PoE ports on a specific board
Disable all portsCut power to all PoE ports on a specific board
Reset all portsPower-cycle all PoE ports
Bulk fleet rebootReboot all boards (staggered timing to avoid power surges)

Removing a Paired Board

To unpair a board:

  1. Open the fleet view
  2. Find the board you want to remove
  3. Click the remove/unpair option
  4. Confirm

The trust relationship is removed from both boards. The board will still appear in the mDNS discovery list but will no longer share status data.

Network Requirements

  • Boards must be on the same network subnet for mDNS discovery
  • Port 5353 (UDP) must be open for mDNS multicast
  • HTTPS must be accessible between boards for status polling
  • Fleet polling occurs every 5 seconds via HTTPS with Ed25519 signature authentication

Last modified April 9, 2026