Reset Search
 

 

Article

Troubleshooting - ATOM AP30

« Go Back

Information

 
TitleTroubleshooting - ATOM AP30
Symptoms
ATOM AP30 won't connect to ExtremeCloud IQ (XIQ) successfully
ATOM AP30 was connected to ExtremeCloud IQ (XIQ) and disconnected
Environment
ExtremeCloud IQ (XIQ)
Cause
Generally, XIQ APs will on-board to XIQ via their Eth backhaul port when they are deployed for the first time. An ATOM AP will act as a Remote Mesh point with a default, out-of-the-box configuration; and will connect to a nearby available portal AP to on-board automatically. For full instructions on how to connect an ATOM AP to your XIQ instance, go to the following link: How to connect your ATOM AP30 to ExtremeCloud IQ (XIQ) via CAPWAP/Back Haul Mesh
Resolution
If an ATOM loses its connection after the original connection takes place, it will trigger ACSP failover. The steps of an ACSP failover are listed below:
  1. ACSP Failover Triggers:
  • Ethernet interface down (2s)
  • Portal AP down (unreachable) (30s)
  1. The Mesh Point will check the ACSP neighbor list to see whether it has an available portal or not. If ‘Yes’, skip to step 4; otherwise it will start the ACSP scan.
  2. ACSP Scan (in order):
  • 2.4G band (25s)
  • 5G with DFS disabled (25s)
  • 5G with DFS enable(50s)
  1. Calculating, the Mesh Point will select a channel (less than 1s)
  2. DFS CAC (Channel Available Check), this is only available for DFS channel
  • Normal DFS channel (60s)
  • European Weather DFS channel (600s)
  1. Establishes a mesh link, creates a L2 route, and gets an IP address via DHCP (10s)
 
Note: We need about 40s for ACSP failover in a best case scenario, and about 11 minutes at worst.

LED stuck on solid Amber
  • First time deployment:
    • Make sure we are on running XIQ version 8.3r1 or later (if it is on a different version, it can only onboard with a physical Ethernet connection).
    • Confirm there is nothing connected on the Eth0 port
    • Confirm it is using factory default settings
    • Physical reset
    • Confirm there is at least one portal AP with at least one Radio set to backhaul/dual mode.
    • Confirm the portal AP and the ATOM AP (after initial configuration) are using the same hive profile.
  • Was working previously
    • SSH in to the portal AP this ATOM would be connecting to (if you are unsure which one the ATOM should connect to, we must check all possible portal APs).
      • Run commands
        •  “show hive <hive name> neighbor
        • Show amrp neighbor
          • These commands will show you if the portal AP can see the ATOM at all.
LED stuck on flashing White for more than 10 minutes
  • This means that the ATOM cannot find an available portal AP
  • Confirm we have added the ATOM serial number to the device inventory in XIQ.
  • Confirm there is at least one portal AP with at least one radio set to backhaul/dual mode near the ATOM AP, and that mesh-join response is enabled.
LED stuck on slow blinking Amber
  • SSH in to the portal AP this ATOM would be connecting to (if you are unsure which one the ATOM should connect to, we must check all possible portal APs).
    • Run commands
      • Show hive <hive name> neighbor
      • Show amrp neighbor
        • These commands will show you if the portal AP can see the ATOM at all.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255