Sites with Multiple AP's across core and remote switches - if devices aren't appearing in the list when OvrC Hub scans

Sites with Multiple AP's across core and remote switches - if devices aren't appearing in the list when OvrC Hub scans

Scenario: 24 port switch in the rack with AP(s) cabled to it, plus cable to a 5port switch with PoE passthrough providing data and power to a remote AP.

Issue: OvrC hub did site scan but was not listing all devices on site, took a couple of scans and a reboot to get the whole site referenced

Araknis support response:

There should not an issue with WAPs being remote to the core switch, however there are a few things I would want to look at:
  • Is STP enabled, with the priority lowered to 4096 on the core switch (AN-210-SW-R-24-POE).
    Make sure the Root Address and Bridge Address are matching to ensure proper network traffic flow


  • Have you ran a site survey on the Access Points to make sure they are not interfering with each other
    • Look for anything that says D4:6A:91:XX:XX:XX (our mac address scheme) and make sure  the signal is between -68 to -78
    • Also choose a channel (1, 6, or 11) that is not saturated.
    • In the example below, there is only 1 AP in the system but this should give you an idea If there are other factors causing the AP not receive packets


 


    • Related Articles

    • Araknis/OvrC devices cant be reached via dashboard when using ISP router

      A new installation of an OvrC hub and 4x AP's on a site with latest SkyQ hub, OvrC dashboard works fine but you cant connect to Araknis devices in the device list you get the following error message the ports required to be opened are 53, 443
    • Accessing Rako Hub on OvrC

      To access a Rako Hub on OvrC, you need to set the port scan for HTTP to other. Its been reported that a Rako hub will only show an available SSH connection. This is because port 80 gets redirected to a secure page sub domain which OvrC cant scan.  ...
    • Accessing Telnet Devices in OvrC

      There is a bug in OvrC were Telnet doesn't connect to devices via OvrC. Here is a workaround In OvrC, go to the site in question and navigate to Site Settings Click on Network Ports Scanned Change the Telnet default port scan (Port 23) to, 'Other'. ...
    • Using Traceroute on OvrC hub to identify network issues

      If a client is experiencing unusual network behaviour or devices dropping off the hub, running a traceroute may help identify issues, specifically how many node hops are happening,  Once you login to the OvrC Hub (default credentials are user: ovrc, ...
    • Adding a Luma NVR to OvrC

      Please be advised when adding the NVR to OvrC it is required to use the Mac address and the Serial number.   The ST number is NOT the serial number of the unit.   Please use the Luma utility or login to the unit to find the serial.   This is done for ...