Public Guide · UniFi · Fundamentals

Understanding the UniFi Ecosystem

Jump to verification

What you will learn

  • Identify the roles of UniFi gateways, consoles, switches, access points, Protect, and Access
  • Understand which components can be combined and which remain separate
  • Map a business requirement to the correct UniFi application

When this procedure applies

Use this before selecting UniFi equipment or inheriting an unfamiliar UniFi site.

Prerequisites and required tools

  • Current site diagram or floor plan
  • Device inventory
  • Current Ubiquiti product and application documentation
Safety and access warning: Confirm authorization, service impact, electrical and optical hazards, required PPE, and rollback procedures before touching production infrastructure. Stop when conditions exceed your training or test equipment.

Concept explanation

UniFi is an ecosystem of applications and managed devices. The console hosts management applications; the gateway routes and enforces policy; switches provide wired connectivity and PoE; access points provide wireless service; Protect manages video; Access manages controlled doors. A design should begin with operational requirements, not a product list.

DIAGRAM: UniFi ecosystem roles and data flow — 1600×900Replace this placeholder with original, cleared FryAVSI media.

Step-by-step procedure

  1. List required services: routing, switching, Wi-Fi, video, doors, voice, and remote access.
  2. Identify the console and management ownership model.
  3. Map every endpoint to a switch port, PoE requirement, network, and application.
  4. Confirm storage, uplink, UPS, and growth requirements.
  5. Document administrator ownership, backups, updates, and recovery.

How to verify the result

  • Every device has an identified role and owner
  • PoE and storage calculations include headroom
  • The design still operates if internet access is unavailable

Common mistakes

  • Treating the gateway and console as interchangeable
  • Ignoring Protect storage write load
  • Buying access points before studying coverage and capacity
Troubleshooting and escalation

Return to the last known-good state. Separate physical, addressing, configuration, application, and documentation issues. Capture evidence before resetting or replacing equipment. Escalate when safety, life-safety service, regulated systems, unsupported hardware, or an unknown production dependency is involved.

VIDEO: Walkthrough of a small complete UniFi deployment — 1920×1080, 16:9Use an annotated photo, diagram, or short demonstration with identifying information removed.

Field notes from FryAVSI

Record what was found, what changed, the exact test method, test limits, results, exceptions, and the person responsible for follow-up. A technically correct repair without usable documentation creates the next avoidable outage.

Short knowledge check

Can you explain what the selected test proves, what it does not prove, and what evidence must be retained before the system is returned to service?

Related lessons

Browse the Learning Center for prerequisite concepts, adjacent procedures, and advanced troubleshooting.

Revision: July 2026 · Review before use against current manufacturer documentation, standards, software versions, project specifications, and site policy.