INSTALLER CENTRE

Troubleshooting Centre

Start at the layer where the evidence points. Change one variable at a time and leave a record of what you proved.

Copper link will not come up

  1. Check link state at both devices.
  2. Verify patching and correct ports.
  3. Run wiremap/continuity appropriate to the cabling.
  4. Check negotiated speed and device configuration.
  5. If physical-layer performance is suspect, use an appropriate qualification/certification test rather than guessing.

Link negotiates below expected speed

  1. Confirm both interfaces support the expected speed.
  2. Check configuration and auto-negotiation status.
  3. Substitute known-good patch cords.
  4. Test the installed link to the relevant performance requirement.
  5. Inspect error counters after restoring service.

PoE device does not power

  1. Confirm device PoE requirement.
  2. Confirm port capability and PoE configuration.
  3. Check available switch PoE budget and diagnostics.
  4. Check the cabling path.
  5. Compare against a known-good compatible source/device where appropriate.

Fibre link down

  1. Confirm the correct ports/modules and intended fibre path.
  2. Check polarity.
  3. Inspect connector end faces before repeated mating.
  4. Measure optical loss using the correct method.
  5. Use OTDR/event analysis when fault location is required.

Intermittent network fault

  1. Establish whether the failure is physical link, power, switching, routing or application level.
  2. Record timestamps.
  3. Check interface counters and logs around the event.
  4. Correlate with power and environmental events.
  5. Change one variable at a time.

WiFi complaint

  1. Define the complaint precisely: coverage, throughput, roaming, authentication or internet access.
  2. Separate WLAN performance from WAN/internet performance.
  3. Measure at the affected location.
  4. Check channel use and interference.
  5. Compare results with the project's design targets.
Troubleshooting discipline: do not replace three components at once and call the problem fixed. A repeatable fault-isolation process creates evidence and prevents the same problem returning.