Troubleshooting: SEMS Not Reachable

Deterministic first-access diagnostic path for a SEMS controller that cannot be reached from a browser.

Diagnostic flow

  1. Power — confirm the board is powered.
  2. Ethernet link — confirm the physical link is up.
  3. Addressing — verify DHCP/static expectations.
  4. IP discovery — identify the actual controller address.
  5. Subnet — confirm the laptop is in the same network path.
  6. Reachability — test local network reachability.
  7. Browser access — retry the SEMS web interface.
CyberSun SEMS login screen used for reachability troubleshooting
If browser access succeeds, the first visible proof is the local SEMS login page rather than the internal application dashboard.

If DHCP is expected

  • inspect the router lease table;
  • confirm the controller is connected to the intended LAN;
  • confirm the site switch/router is live.

If static addressing is expected

  • verify the intended static IP plan;
  • verify there is no duplicate IP conflict;
  • make sure the laptop uses a compatible local subnet during commissioning.

If the IP is still unknown

  • connect at the closest practical local network point;
  • review installation notes and board labeling;
  • escalate to the approved field support path rather than guessing hidden defaults.

Was this helpful?

Did this article answer your question?