Beam Remote Site

Analyze centrally. Test directly at the site.

A test from the central network cannot always see what a branch office is actually experiencing. Beam runs service checks, AP SSH, captures, and tech dumps where the problem occurs and brings the results back into Control.

Beam architecture with remote sites, local agents, and outbound HTTPS
Central Control core · local Beam Agents · outbound HTTPS connection · evidence on demand
LOCAL CONTEXT

The site tests itself.

DNS, DHCP, NTP, gateway, RADIUS, AP CLI, and local network paths are tested from the network where the issue actually occurs.

OUTBOUND HTTPS

No inbound VPN access required.

Beam initiates an outbound connection to Control. Remote sites remain accessible without requiring additional inbound firewall rules.

LOCAL STORAGE

Large evidence files remain on site.

Captures, tech dumps, diagnostic artifacts, and monitor samples are retained locally and retrieved centrally only when needed.

Local execution

Diagnostics from the network where the problem occurs.

  • AP SSH and CLI jobs
  • DHCP, DNS, gateway, NTP, and RADIUS tests
  • Remote sniffer and captures
  • Tech dumps and diagnostic artifacts
  • Monitor and usage samples
  • Evidence storage and controlled retrieval
Control Beam status for remote agents
Heartbeat, site assignment, job status, and results in the central Control context.

Raw data on demand

Large raw data stays local until it is needed.

This reduces WAN load and keeps large evidence close to where it was created. It is retrieved centrally when needed without turning every remote site into a separate tool environment.