Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Help with APIN0115: 5ghz and 2.4 ghz lights go down during the day and clients disconnect

This thread has been viewed 0 times

  • 1.  Help with APIN0115: 5ghz and 2.4 ghz lights go down during the day and clients disconnect

    Posted Jun 19, 2020 08:16 PM

    I am using APIN0115 for indoor use as a AP with the modem provided by the service provider.

    Everything seems fine except that sometimes 5ghz and 2.4 ghz lights go down during the day and clients disconnect. I dont know the reason and i am looking for help for ways i can debug this. I only have 10 -15 active clients at any given time

     

    The AP does not restart itself but only the led lights for the atennnas go down and then the clients disconnect and then after sometime they come back on

     

    1. Does anyone know the cause for this. 

    2. Are there any relvant logging that i can look at to see why this is happening. And what should i be looking for?

     

     

    Thanks in advance to anyone who can help

    Cheers!



  • 2.  RE: Help with APIN0115: 5ghz and 2.4 ghz lights go down during the day and clients disconnect

    EMPLOYEE
    Posted Jun 19, 2020 08:59 PM

    "show log system"



  • 3.  RE: Help with APIN0115: 5ghz and 2.4 ghz lights go down during the day and clients disconnect

    Posted Jun 20, 2020 01:59 PM

    here are the sample logs is see 

     

    It says 

     disable SSID[arb

    Jun 20 17:56:12 cli[2438]: <341271> <ERRS> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| ethernet uplink bond0 link down.
    Jun 20 17:56:12 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| stopping DHCP on bond0
    Jun 20 17:56:12 cli[2438]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Retrieving ip address from br0, ip 192.168.0.11, mask 255.255.255.0.
    Jun 20 17:56:12 cli[2438]: <341274> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Update election ip from br0, election ip 192.168.0.11/255.255.255.0.
    Jun 20 17:56:12 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| build_my_ip_address: old ip and new ip same; skipping
    Jun 20 17:56:12 cli[2438]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Uplink bond0 type Ethernet, state UP->DOWN.
    Jun 20 17:56:12 cli[2438]: <341177> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Try next uplink because current uplink is down - Ethernet.
    Jun 20 17:56:12 cli[2438]: <341263> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| enable uplink .
    Jun 20 17:56:12 cli[2438]: <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Uplink type Dummy, state DOWN->PROBE.
    Jun 20 17:56:12 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| enable dummy uplink
    Jun 20 17:56:12 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| disable SSID[arb
    Jun 20 17:56:13 cli[2438]: <341177> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Try next uplink because current uplink is down - Ethernet.


    : <341167> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Uplink type Dummy, state PROBE->UP.
    Jun 20 17:56:18 cli[2438]: <341181> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Uplink , setup ip for uplink - Dummy.
    Jun 20 17:56:18 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| /etc/setup_ip_swarm Dummy 1
    Jun 20 17:56:18 cli[2438]: <341166> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Get interface br0 ip: 192.168.0.11/255.255.255.0.
    Jun 20 17:56:18 cli[2438]: <341185> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| Retrieving ip address from dummy uplink, ip 192.168.0.11, mask 255.255.255.0.
    Jun 20 17:56:18 cli[2438]: <341004> <WARN> |AP ac:a3:1e:ca:b5:68@192.168.0.11 cli| build_my_ip_address_stage2:setting this as new IP address for swarm/clients
    Search