
Workshop outcome
This chapter is intended to move beyond product awareness. It should help you plan the work, select the correct hardware class, execute or supervise the change, test the result and produce useful handover evidence.
DEEP TECHNICALFIELD WORKFLOWACCEPTANCE1. Confirm the path before mounting
Verify endpoints, distance, line of sight, obstructions and mounting height. Trees and future vegetation growth can matter even when the far roof is visible.
2. Confirm the radio pair
Both ends must support the intended band, channel width, regulatory region and link mode. Use the vendor link planner where available.
3. Mount for rigidity
A directional link that moves in wind can become unstable. Use appropriate brackets, pole diameter and fasteners for the site and equipment.
4. Protect the outdoor cable path
Use outdoor-rated cable/construction where required, drip loops, weatherproof entries and the manufacturer surge/earthing recommendations.
5. Coarse alignment
Aim both units using physical sighting or the vendor tool, then establish link before fine adjustment.
6. Fine alignment
Adjust one end in small increments while observing signal, noise and link quality, then repeat at the far end. Do not optimise only one side.
7. Check channel conditions
A strong signal on a busy/noisy channel can still perform poorly. Review channel utilisation/interference and select a legal channel appropriate to the environment.
8. Run bidirectional traffic tests
Measure throughput and loss in both directions over a useful period. Test the Ethernet interfaces too, not only the radio dashboard.
9. Handover
Photograph mounting, record coordinates/site names, radio models, channel, width, signal/noise metrics, firmware, IPs, PoE method and throughput baseline.
Worked field scenario
A link comes up at installation but throughput collapses in windy weather. The cause may be a flexible mount rather than RF configuration. A commissioning record that includes mount photographs, signal/noise and throughput gives evidence to distinguish alignment movement from interference.
Do not proceed from a product label alone. Convert the requirement into measurable compatibility, capacity, installation and acceptance checks.
Procurement questions before ordering
The ordering stage is where many field problems are created. Capture the following before selecting the exact product:
- Client device types and application requirements
- Floor/site plan and AP mounting constraints
- Regulatory domain and supported bands
- PoE and wired uplink capability
- Pre-install or validation survey plan
Where a manufacturer compatibility list, rail matrix, supported-optics table or battery cartridge reference exists, record the exact source used for the decision. That gives the later installer evidence rather than a verbal assumption.
Fault-finding decision path
Separate RF from IP. Confirm the client can see and join the intended SSID, then examine RSSI/SNR, channel utilisation, retries and roaming behaviour before moving to DHCP, DNS, gateway and application tests. Compare a failing client with a known-good client at the same location.
Keep a simple change log while troubleshooting: observation, action, result. If a change does not alter the symptom, put the system back unless there is a documented reason to retain it. This prevents troubleshooting from becoming an uncontrolled configuration drift.
Common mistakes that create repeat faults
Do not fix coverage complaints by setting every AP to maximum power. Do not choose AP count from an advertised square-metre number alone. Do not change channels, widths, power and minimum rates simultaneously because you will not know which change helped or hurt.
A technically successful installation can still be a poor operational result if the next technician cannot identify what was installed, why it was selected, or how it was tested. Serviceability is part of infrastructure quality.
Acceptance and handover evidence
Keep the final AP map, channel/width/power state, switch port and PoE mapping, post-install survey evidence and representative client tests. Record deliberate exceptions so the next administrator does not undo them thinking they are mistakes.
Use filenames, labels and port/bay identifiers that match the physical installation. Handover evidence should let someone who was not present at the installation verify the final state and repeat the important tests later.
RELATED HARDWARE
Apply the lesson to Server Warehouse
These are educational category relationships. Always verify exact model compatibility, firmware, electrical limits, supported media and manufacturer requirements before ordering.
Technical references
Manufacturer documentation and the project specification remain authoritative for model-specific limits, procedures and safety requirements.