Standardized Deployment Protocol
STATION Network
INSTALL GUIDE
Covers full deployment of the Responders First Ubiquiti/Starlink stack at LAFD fire stations — from site survey through UniFi controller configuration and sign-off.
3
Stations Deployed
6
Core Components
4
Install Phases
Install Checklist
0 / 0
01
Network Topology
Starlink Dish
Standard or Mini · WAN uplink
——→
Ethernet
Cloud Gateway Max
Router · Firewall · Controller
├─
Cat 6e + PoE+
U7 Pro (Indoor AP)
WiFi 6E · Mesh root · 1× per zone
– – →
Wireless mesh
U6 Outdoor AP
WiFi 6 · Wireless uplink from U7
└─
Optional · P2P bridge
NanoBeam Pair
Isolated wings · Apparatus bay
Mesh backhaul note: The U7 Pro uses its 6 GHz radio as a dedicated wireless backhaul channel to the U6 Outdoor. This keeps 2.4 GHz and 5 GHz bands free for client devices. Confirm this is set correctly in UniFi controller during Phase 3 configuration.
02
Hardware List
| Component | Role |
|---|---|
Starlink Standard / Mini |
WAN internet uplink · dish + router |
Ubiquiti Cloud Gateway Max 512GB |
Core router · firewall · UniFi controller · NVR |
Ubiquiti UniFi U7 Pro |
Indoor WiFi 6E AP · wired to gateway · mesh root for outdoor |
Ubiquiti UniFi U6 Outdoor |
Exterior WiFi 6 AP · wireless mesh uplink to U7 Pro |
Cat 6e Cable |
Wired runs from gateway to each U7 Pro; carries PoE power |
PoE+ Injector (802.3at) |
Powers U7 Pro over Cat 6e · one per AP |
5-Port Network Switch |
Expands LAN ports at patch panel or remote distribution point · essential for larger stations with multiple AP runs or NanoBeam endpoints · optional |
Ubiquiti NanoBeam (Pair) |
Point-to-point wireless bridge · isolated wings or apparatus bay · optional |
Pre-stage kit: Pack all components in a labeled Pelican case before arriving on site. Confirm serial numbers match the UniFi inventory list before leaving RF office.
03
Phase 1 — Pre-Install Survey
Pre-Install
Complete Before Arrival On Site
-
Confirm Starlink dish clear sky viewUse the Starlink app obstruction tool to verify the installation address has unobstructed southern sky view. Identify the optimal roof or wall-mount location before ordering hardware.
-
Walk the station — identify Gateway locationCloud Gateway Max should sit in a secure, ventilated interior space — captain’s office, IT closet, or server rack. Needs AC power and proximity to the Starlink router Ethernet output.
-
Map U7 Pro placement zonesIdentify 1–2 interior zones with good RF path toward exterior walls. U7 Pro must have line-of-sight or near-LOS through a window or exterior wall toward the planned U6 Outdoor mount point. Mark on station floor plan.
-
Identify U6 Outdoor mount pointExterior eave, wall bracket, or soffit. Must have clear path back to the nearest U7 Pro through structure. Confirm no apparatus bay steel doors, thick masonry, or RF-blocking HVAC units between the two units.
-
Plan Cat 6e cable routesTrace routes from Gateway to each U7 Pro. Note wall penetration points, conduit availability, and whether runs pass through apparatus bay (heat/flex conduit required). Measure and document run lengths — max recommended 328 ft (100m) per run.
-
Assess NanoBeam needIf any coverage area (rear lot, apparatus bay, adjacent dormitory building) cannot be reached by U6 Outdoor mesh, flag for NanoBeam pair deployment. Document the two endpoints and line-of-sight path.
-
Check for existing Patch PanelInspect the IT closet, server rack, or comms room for an existing patch panel. A patch panel centralizes all Cat 6e runs into a single distribution point, significantly improving network signal distribution and organization across the station. If found, document port count, label layout, and location — this will determine whether a 5-port switch or direct Cloud Gateway Max connection is used. Flag stations with a patch panel for the optional Patch Panel Integration phase.
-
Confirm station captain coordinationSchedule install during a shift when the captain or designee is on-site. Confirm access to all areas including roof. Note any station-specific constraints (drill schedules, active incidents, restricted areas).
04
Phase 2 — Physical Installation
On Site
Hardware Mounting & Cable Runs
-
Mount and aim Starlink dishMount per Starlink instructions. Run Starlink Ethernet cable to the Cloud Gateway Max WAN port. Do not use the Starlink router in bridge mode unless the station needs it — the Cloud Gateway Max handles routing.
-
Rack or mount Cloud Gateway MaxMount in identified secure location. Connect power. Connect Starlink Ethernet to
WANport. Leave LAN ports ready for Cat 6e runs to U7 Pros. -
Run Cat 6e to each U7 Pro locationPull Cat 6e from Gateway to each U7 Pro mounting point. Use conduit through apparatus bay. Terminate with RJ-45 connectors and test continuity before mounting APs. Label both ends of each run.
-
Install PoE+ injectors and mount U7 ProsConnect Cat 6e run to PoE+ injector
DATA INport; run short patch fromDATA+POWER OUTto U7 Pro. Mount U7 Pro to ceiling or wall — orient so the antenna face points toward the exterior wall where U6 Outdoor will mount. -
Mount U6 Outdoor unitsMount at planned exterior location. No cable run required — the U6 Outdoor receives its uplink wirelessly from the nearest U7 Pro. Ensure the AP face has clear RF path back to the U7 Pro inside. Use weatherproof mounting hardware and outdoor-rated cable for any secondary power runs.
-
Install NanoBeam pairs (if applicable)Mount NanoBeam units at both endpoints. Use the NanoBeam’s built-in alignment tool (LED indicators or airOS signal bar) to achieve tight point-to-point alignment. Run Cat 6e from each NanoBeam to the nearest switch port or AP.
-
Power-on sequencePower on in order: (1) Cloud Gateway Max → (2) PoE+ injectors → (3) U7 Pros → (4) U6 Outdoors. Allow 3–5 minutes between each stage for devices to initialize before proceeding to configuration.
05
Phase 2b — Patch Panel Integration
Optional phase — complete only if a patch panel was found during Phase 1 survey. A patch panel centralizes all structured cabling into a single distribution point, reducing cable clutter and improving signal distribution across large stations.
On Site
Patch Panel Connection Options
-
Identify patch panel port layout and available portsDocument the patch panel’s port count, which ports are active, and which are free. Trace existing runs to confirm which rooms or zones are already wired. Free ports can be used for new U7 Pro or switch connections without pulling new cable.
-
Option A — Connect patch panel directly to Cloud Gateway MaxIf the Cloud Gateway Max has sufficient LAN ports, run a Cat 6e patch cable from each active patch panel port directly to a LAN port on the Gateway. Best for smaller stations with fewer than 5 total device runs. Label each port clearly at both ends.
-
Option B — Connect patch panel via 5-port switchFor stations with more device runs than available Gateway ports, connect the patch panel to a 5-port switch, then run a single uplink cable from the switch to the Cloud Gateway Max LAN port. This expands capacity for U7 Pros, NanoBeam endpoints, and additional devices without requiring a full managed switch. Confirm the 5-port switch is PoE-capable if powering APs directly from it.
-
Terminate and label all patch panel connectionsPunch down or connect all Cat 6e runs to the patch panel ports. Label every port at the panel and at the device end — use the station number and zone (e.g.,
FS-51-AP1,FS-51-NANO-A). Test continuity on each run before powering devices. -
Verify full connectivity through patch panelWith the Gateway, switch, and patch panel connected, confirm each downstream device (U7 Pros, NanoBeam units) receives a link light and appears in UniFi before closing up the rack. A device not appearing in UniFi after 3 minutes indicates a cable, port, or PoE issue at the patch panel.
06
Phase 3 — UniFi Configuration
Configuration
UniFi Controller Setup
-
Access UniFi controller on Cloud Gateway MaxConnect a laptop to the Gateway LAN port or via Wi-Fi. Navigate to
unifi.ui.comor the local Gateway IP (default192.168.1.1). Log in with the RF master UniFi account credentials. -
Adopt all devices into the siteIn UniFi → Devices, confirm Gateway, U7 Pros, and U6 Outdoor units all appear as Pending Adoption. Adopt each device into the station’s site. Name each device clearly: e.g.,
FS-[StationNum]-U7-1,FS-[StationNum]-U6-EXT. -
Configure wireless mesh backhaul on U7 ProIn UniFi → Devices → U7 Pro → Config → Wireless Uplink: confirm the U6 Outdoor is connecting via wireless mesh. Verify the backhaul is running on 6 GHz band to keep 2.4/5 GHz free for clients. Check signal strength of mesh link — target –65 dBm or better.
-
Create SSIDsCreate two SSIDs minimum:
RF-[StationNum]-OPS(WPA3, for station personnel devices) andRF-[StationNum]-MGMT(isolated management network, for RF/Joseph remote access). Apply consistent RF naming convention across all stations. -
Set transmission power and channel planSet 2.4 GHz to Auto or Medium power (avoid high in dense station environments). Set 5 GHz and 6 GHz to High. Let UniFi auto-select channels initially; adjust if neighboring AP interference is detected post-install.
-
Configure remote management accessEnable UniFi remote access on the Gateway so Joseph can monitor and manage the site from
unifi.ui.comwithout needing a VPN. Confirm the Gateway is registered to the RF UniFi account. -
Configure NanoBeam bridge (if applicable)Access each NanoBeam via its management IP. Set one as Access Point mode and the other as Station mode. Confirm link is established and passing traffic. Note management IPs in the station’s network record.
07
Phase 4 — Verify & Sign-Off
Sign-Off
Functional Tests Before Leaving Site
-
Run speed test from each SSIDConnect to
RF-[StationNum]-OPSand runfast.comorspeedtest.net. Document results. Minimum acceptable: 25 Mbps down / 5 Mbps up on the operational SSID from any point in the station. -
Walk the station — verify full coverageWalk every room, corridor, bunk area, apparatus bay, and exterior apron with a phone connected to the OPS SSID. Confirm no dead zones. If signal drops below –75 dBm in any occupied area, reposition or add AP before sign-off.
-
Verify U6 Outdoor mesh link qualityIn UniFi → Devices → U6 Outdoor, confirm wireless uplink status shows Connected and mesh link RSSI is –65 dBm or better. If marginal, adjust U7 Pro or U6 Outdoor position before finalizing mount.
-
Confirm remote management is liveHave Joseph log into
unifi.ui.comfrom the RF office and confirm the new station site is visible and all devices show as Connected. Verify he can reboot an AP remotely as a test. -
Document and photograph the installPhotograph: dish mount, Gateway install location, each U7 Pro and U6 Outdoor, cable routes. Log serial numbers, device IPs, and SSID credentials in the Grant Tracker Starlinks sheet. Note any station-specific deviations from standard config.
-
Brief station captain on daily useWalk the captain through: SSID names and passwords, who to contact for issues (RF ops: starlink@respondersfirst.la), and monthly reimbursement process. Leave the Starlink One-Pager printed at the station.
08
Troubleshooting Reference
| Symptom | Likely Cause | Fix |
|---|---|---|
| U6 Outdoor not meshing | Structural obstruction between U7 and U6; wrong band config | Check RF path — reposition U7 Pro closer to exterior wall. Confirm 6 GHz backhaul is enabled in UniFi. Try forgetting and re-adopting the U6 Outdoor. |
| Slow speeds despite good signal | Mesh backhaul consuming airtime on client band; channel interference | Verify backhaul is on 6 GHz only. Run UniFi RF scan to check for channel overlap from neighboring networks. Switch to less congested channels manually. |
| U7 Pro not getting PoE power | Injector not seated; cable fault; wrong PoE standard | Reseat Cat 6e at injector. Test cable continuity. Confirm injector is PoE+ (802.3at) — U7 Pro requires PoE+, not standard PoE. |
| Starlink showing high latency or dropout | Dish obstruction; satellite handoff; physical cable issue at dish | Check Starlink app obstruction view. Inspect dish cable and connector. Reboot dish via Starlink app. If persistent, check for new physical obstructions (trees, equipment). |
| Devices not appearing in UniFi | Device on different VLAN; firmware mismatch; not factory reset | Confirm all devices are on the same Layer 2 network as the Gateway. Factory reset the device and re-adopt. Update UniFi controller firmware before adopting new hardware. |
| NanoBeam link unstable | Misalignment; interference; physical vibration from apparatus | Re-align using airOS signal strength display — aim for CCQ above 90%. Add vibration-dampening mount if near apparatus bay. Check for new interference sources on the 5 GHz link frequency. |
| Remote management offline | Gateway not linked to RF UniFi account; Starlink offline | Verify Gateway is registered under the RF UniFi account at unifi.ui.com. Check Starlink service status. Reboot Gateway. Confirm remote access toggle is enabled in Gateway settings. |
09
Field Notes
Apparatus bay interference: Steel apparatus bay doors are the single most common cause of poor U6 Outdoor mesh link quality in station environments. Survey with doors both open and closed. If signal drops significantly when doors close, the U6 Outdoor mount point needs adjustment or a NanoBeam bridge is required for that coverage zone.
Naming convention matters: Consistent device naming (
FS-[StationNum]-[DeviceType]-[Index]) across all stations makes remote management and troubleshooting significantly faster for Joseph when managing the fleet from the RF office.Mesh root placement: The U7 Pro’s position is the most consequential decision on any station install. A well-placed U7 Pro — near an exterior wall with clean LOS to the U6 Outdoor and central to the main interior coverage zone — makes everything else straightforward.
Starlink Standby Mode: Fixed station units (Starlink Standard) can be toggled to Standby ($5/month) during low-demand periods via starlink.com. BC Mini units on Roam ($165/month) should remain on full service at all times — Standby disables connectivity when the vehicle is in motion. See the Starlink Standby One-Pager for full billing details.
