How to test Ubiquiti UniFi APs after installation in offices

Products Available

Ubiquiti Point-to-Point Wireless Solutions in Kenya

Ubiquiti LOCO-5AC

KES 6300.00

Ubiquiti Point-to-Point Wireless Solutions in Kenya

Ubiquiti loco M5

KES 9000.00

Ubiquiti Point-to-Point Wireless Solutions in Kenya

Ubiquiti loco M2

KES 6500.00

Ubiquiti Point-to-Point Wireless Solutions in Kenya

Ubiquiti LBE-M5-23

KES 6500.00

How to test Ubiquiti UniFi APs after installation in offices

How to test Ubiquiti UniFi APs after installation in offices: A Kenyan Technical Guide from Orbitlink Solutions

Verify adoption and software state

Confirm every AP is adopted by the intended UniFi Network application, has the expected name and site, reports no adoption loop and runs an approved firmware release. Do not update all production APs blindly during acceptance testing. Record controller backup and device inventory first. Record the initial state, configuration, test instrument or client used, time and result. Repeat the same procedure after correction. This makes the decision auditable and prevents a coincidental improvement from being accepted as proof. At the office Wi-Fi deployment, this decision shares ports, pathways, power or policy with other systems. Survey-led where to place tenda wi-fi routers in schools reduce dead zones without raising transmit power blindly or hiding a router in a cabinet.

Inspect power and uplink negotiation

Check that the exact AP receives a supported PoE mode and sufficient power from the switch. Verify Ethernet speed, duplex and error counters. A radio test cannot compensate for a damaged cable or an uplink that negotiated below design. Read the label and full product code, then match it to the current official data sheet and administration guide. Hardware revisions can change ports, radio capability, PoE, licences or firmware, so a family name is not sufficient evidence. At the office Wi-Fi deployment, this decision shares ports, pathways, power or policy with other systems. A port and power schedule for how to connect cameras and aps to d-link switches in hotels makes CCTV, guest Wi-Fi and uplink dependencies traceable during an incident.

Confirm mounting and radio assumptions

Compare installed ceiling or wall orientation with the model's official mounting guidance and radiation pattern. Note nearby metal, lift shafts, glass and shelving. Use the RF environment seen after furniture and occupants arrive, not only the empty-office survey. Inspect the actual cabinet, room, power source, heat, dust, cable pathway and working hours. Nairobi office assumptions may not fit a coastal hotel, rural school or hot warehouse, and the design must remain maintainable locally. At the office Wi-Fi deployment, this decision shares ports, pathways, power or policy with other systems. Tested guest network setup with tp-link wi-fi routers for shops keep customers away from payment, surveillance and administration systems while protecting business traffic.

Test SSID and VLAN mapping

Join every staff, voice, device and guest SSID with an appropriate test client. Confirm DHCP, DNS, gateway, VLAN and policy assignment. Prove isolation by attempting permitted and forbidden destinations rather than assuming the SSID name enforces a boundary. Ask what happens when this component, link or power source fails. Where the consequence includes lost payments, lessons, surveillance or customer service, provide a tested fallback and assign responsibility for responding to alarms. At the office Wi-Fi deployment, this decision shares ports, pathways, power or policy with other systems. A documented policy for when to replace ageing ip cctv cameras in warehouses preserves evidence quality and removes unsupported devices before failures become routine.

Observe a representative busy period, record peaks and explain the engineering margin used for growth. For test ssid and vlan mapping, the acceptance record should explicitly address join every staff, voice, device and guest ssid with an appropriate test client, confirm dhcp, dns, gateway, vlan and policy assignment. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes test ssid and vlan mapping maintainable after the original installer has left.

Measure coverage systematically

Use a repeatable floor plan and test points in meeting rooms, desks, corridors and service spaces. Record signal, noise, channel, band and negotiated rate; WiFiman can assist measurement, but interpret results with the client model and controller telemetry. Limit management access to named administrators, use unique credentials, maintain supported software and retain configuration backups. Verify boundaries by attempting prohibited access from a realistic endpoint rather than trusting a checkbox.

Schedule hazardous or disruptive work for an approved window and use qualified trades for regulated tasks. For measure coverage systematically, the acceptance record should explicitly address use a repeatable floor plan and test points in meeting rooms, desks, corridors and service spaces, record signal, noise, channel, band and negotiated rate. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes measure coverage systematically maintainable after the original installer has left.

Test roaming during real traffic

Walk the expected route while maintaining a voice or video call and record roam events, packet loss and audible disruption. Test with representative corporate devices because roaming decisions are largely client controlled. Do not claim seamless roaming from controller settings alone. Measure present demand during a representative busy period and forecast documented growth. Keep engineering headroom, but do not buy from an unexplained multiplier; state the workload, packet or radio conditions behind every capacity conclusion.

Give support staff a port map, a fault-isolation sequence and evidence they can compare after a change. For test roaming during real traffic, the acceptance record should explicitly address walk the expected route while maintaining a voice or video call and record roam events, packet loss and audible disruption, test with representative corporate devices because roaming decisions are largely client controlled. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes test roaming during real traffic maintainable after the original installer has left.

Assess channel use and interference

Review channel width, channel reuse, utilisation, retries and neighbouring networks on both bands. Wide channels can reduce capacity in a dense office. Automatic settings need observation over busy hours before they are accepted as optimal. Use qualified personnel for mains power, work at height, fire stopping and lightning protection. Isolate equipment before handling conductors, keep exits clear and follow manufacturer instructions; network uptime never justifies unsafe work.

Exercise the function with the oldest and newest representative endpoints rather than one installer laptop. For assess channel use and interference, the acceptance record should explicitly address review channel width, channel reuse, utilisation, retries and neighbouring networks on both bands, wide channels can reduce capacity in a dense office. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes assess channel use and interference maintainable after the original installer has left.

Run throughput tests correctly

Place a capable test server on the wired LAN so an internet service does not become the bottleneck. Test upload and download with one client, then controlled concurrent clients. Document device capabilities and avoid presenting PHY rate as application throughput. Give the support team labels, diagrams, backups, warranty details and a concise fault procedure. A design that only its installer understands becomes expensive when a port fails during a weekend or school examination.

Change one variable, repeat the baseline and retain a tested rollback before applying the change elsewhere. For run throughput tests correctly, the acceptance record should explicitly address place a capable test server on the wired lan so an internet service does not become the bottleneck, test upload and download with one client, then controlled concurrent clients. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes run throughput tests correctly maintainable after the original installer has left.

Check application experience

Make Teams or Zoom calls, use the corporate VPN, print, access local systems and exercise voice handsets where relevant. Monitor latency, jitter and packet loss. A speed test alone misses multicast, DNS, firewall and roaming faults. Test with the endpoints and applications people actually use. A technician's modern laptop can conceal a roaming, driver or compatibility problem that affects tills, pupil tablets, cameras or older office handsets.

Set a review date tied to software support, component condition, demand growth and availability of spares. For check application experience, the acceptance record should explicitly address make teams or zoom calls, use the corporate vpn, print, access local systems and exercise voice handsets where relevant, monitor latency, jitter and packet loss. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes check application experience maintainable after the original installer has left.

Validate guest controls and security

Confirm guest isolation, captive portal behaviour if used, session expiry, rate policies and management-plane restrictions. Verify WPA mode against the supported client fleet. Remove temporary installer accounts and change shared credentials before handover. Make one controlled change at a time, preserve a rollback configuration and retest affected services. Bulk changes without baselines make it difficult to distinguish a cabling problem from policy, software or capacity.

Turn the requirement into a labelled inspection sheet and capture the starting condition before work begins. For validate guest controls and security, the acceptance record should explicitly address confirm guest isolation, captive portal behaviour if used, session expiry, rate policies and management-plane restrictions, verify wpa mode against the supported client fleet. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes validate guest controls and security maintainable after the original installer has left.

Soak test and acceptance record

Observe the system through a working day, review disconnected clients, retries and AP load distribution, then investigate outliers. Issue an AP-by-AP record with location, cable test, switch port, channel plan and measured results. Record installation date, software support status, spare availability and review date. Replacement planning should happen before an unsupported device or unavailable power supply turns a manageable fault into an emergency.

Match every stated limit to the full product code, current document revision and installed operating mode. For soak test and acceptance record, the acceptance record should explicitly address observe the system through a working day, review disconnected clients, retries and ap load distribution, then investigate outliers, issue an ap-by-ap record with location, cable test, switch port, channel plan and measured results. The reviewer should identify who authorises the result and an observable pass criterion for the office Wi-Fi deployment. Normal operation is only half the test: introduce a controlled failure or boundary check that reflects the consequence described in the design. When distance, power, throughput, client count, optical loss, storage or price matters, cite the governing standard, current manufacturer document, calibrated reading or dated quotation beside the value. Preserve the result under an identifier visible at the device, explain deviations, and state who must review them. That evidence makes soak test and acceptance record maintainable after the original installer has left.

Turning the assessment into an approved design

Bring the technical owner, facilities representative and operational user together before purchase or change. Walk through verify adoption and software state inspect power and uplink negotiation confirm mounting and radio assumptions test ssid and vlan mapping, then write the agreed scope, exclusions and acceptance tests. The approver should be able to trace every material choice to a requirement, official model document, standard, measurement or current quotation. This prevents a familiar procurement failure in which products are compared by brand while labour, licences, cabling, power, migration and support are omitted.

Create a small pilot where failure would be contained, test it during representative activity and keep the previous configuration available for rollback. Record faults rather than hiding them with repeated restarts. Once the pilot passes, use the same labels, templates and test method for the remaining locations. The handover should state who monitors the system, how an incident is escalated, where configuration backups are held and when capacity and support status will next be reviewed.

Acceptance record

A signed record does not make a weak design correct, but it exposes missing evidence before the installer leaves. Keep editable source files as well as a PDF or printed copy, protect credentials separately, and update the record whenever ports, firmware, addressing, cabling or policy changes.

Questions for the installer and supplier

• Which exact model and hardware revision is quoted?
• Which official standard, manual or data sheet supports each limit?
• What is included, excluded, licensed separately or dependent on another device?
• How will power, security, failure and representative load be tested?
• Which files, labels, backups and support contacts form the handover?

Answers should be specific enough for another competent technician to repeat the test. Words such as enterprise, high speed, long range or future-proof are not acceptance evidence unless they are tied to the stated workload and an observable result.