airFiber - Troubleshooting an Inaccessible Device


Overview


This article guides the reader through the most common issues that can cause access to an airFiber device to be lost.


Steps to Troubleshoot


Back to Top

Please check each of the following items:

1. In-Band Management versus Out-of-Band Management

  • If you are using the Management port, make sure that the airFiber is configured with the correct subnet for the interface the Management Port is plugged into.
  • The Management Port is not bridged to the Data interface. Management frames will not traverse the wireless link.
    • If you plan to use Out-of-Band Management, you will need a cable plugged into the Management Port of each airFiber.
  • If you are using In-Band Management, make sure to leave In-Band Management enabled during the initial configuration.
    ATTENTION: If there is no cable running to the Management Port and In-Band Management is disabled, there will be no way to gain access to the device without factory resetting or running a cable to the Management Port.

2. Are you using a Management VLAN?

  • Make sure that you have your router and switch ports configured correctly, tagging the interface that the airFiber is plugged into.

3. Service Ports

  • Is there a firewall between you and the unreachable device?
    • Allow or forward ports:
      • SSH: 22.
      • Web UI: 80, 443.
      • Telnet: 23.
  • Did you configure a non-standard port for the services?
    • For Web UI: Append :<port> to the URL.
      • For example if the Web Server port is configured as 8080: https://203.0.113.20:8080
    • For SSH: Append -p <port> to your command line.
      • For example if the SSH Server port is configured as 2022: ssh -l ubnt -p 2022 203.0.113.20
    • For Telnet: Append <port> to your command line.
      • For example if the Telnet Server port is configured as 2323: telnet 203.0.113.20 2323

4. IP Conflict

  • Ensure no other device on the network is sharing the same IP address.

5. Subnet

  • Ensure your current device is routed to the subnet that the inaccessible device is configured in.

6. DHCP

  • Was the device configured to receive a DHCP address?
    • Ensure the DHCP server successfully leased an IP address.
    • Try to access the device through the DHCP fallback address. 

7. Discovery Tool

  • The Ubiquiti Discovery Tool may be helpful to find the correct IP address.
  • Ensure port 10001 is not blocked in the network.

Related Articles


Back to Top

EdgeRouter - Configure DHCP Server on EdgeRouter

airMAX - Device Discovery Tool Introduction

Intro to Networking - IPv4 Addressing & Subnets

airFiber - Ethernet Negotiation Issues


We're sorry to hear that!