Choose the product family before choosing the command. UniFi consoles, adopted APs and switches, legacy USG devices and EdgeRouter systems do not expose one universal Ubiquiti CLI. These references keep access methods, credentials and command context visible.
8 references
Read-only results link to an individual observation command. Other commands on the same page can have different effects.
No matching references. Try a task such as packet capture, route lookup, BGP or interface errors.
How to use these references
For UniFi, start with the SSH and diagnostic-access reference, then choose a useful packet-capture point. The management-port reference separates device communication from administrator access. The backup and support-file guide explains which file supports recovery and which file supports an investigation.
For EdgeRouter, use the EdgeOS references. Begin with operational and configuration modes if you need to understand commit, save or commit-confirm. The other pages inspect routes and BGP, interfaces and ARP evidence, and firewall or NAT counters. A confirmation timer is not a substitute for understanding what a device will do when it expires.
For a particular UniFi symptom, continue to the existing adoption, VLAN, PoE, mDNS or switching guides. These references provide the evidence-gathering steps that complement those task-specific fixes.
Understand key UniFi management ports by endpoint and purpose. Separate device communication, browser access and discovery before changing firewall rules.
Understand EdgeOS operational and configuration modes. Preview changes and use commit-confirm correctly, including its reboot and saved-config behavior.
Inspect EdgeOS interfaces and interface MAC addresses, then capture ARP on the correct LAN. Separate a physical port from its VLAN or switch interface.
Read EdgeOS firewall and NAT counters without clearing sessions. Check interface attachment, WAN_IN versus WAN_LOCAL, rule order and a fresh test connection.