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

Access points connected to A2400 restart every 24 hours more o less

This thread has been viewed 0 times

  • 1.  Access points connected to A2400 restart every 24 hours more o less

    Posted Jan 11, 2013 02:49 PM

    Hello.

     

    We have an Aruba A2400 with some AP-61 connected directly to the Aruba´s POE ports and other AP-61 connected to another POE switch. The second access points have been connected for many days, but the first ones restart every 24 hours more or less. Is there anything I can configure in the A2400 to avoid the restart?

     

    Regards.

     

     

     

    Alejandro



  • 2.  RE: Access points connected to A2400 restart every 24 hours more o less

    EMPLOYEE
    Posted Jan 12, 2013 06:54 AM

    They should not restart period.  Get on the console or open an SSH session to the controller and type "show log system all" to see why the access points are restarting.



  • 3.  RE: Access points connected to A2400 restart every 24 hours more o less

    Posted Jan 15, 2013 04:56 AM

    Thanks for your interest cjoseph.

     

    I cannot find the reason. Only in one occasion (failed to get master-ip). In the rest, there is no reason (No reboot message found).

     

    I attach the last days of the "show log system all".

     

     

     

    Alejandro

     

     

    Jan 14 09:06:01 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 09:06:09 :303022:  <WARN> |AP 00:0b:86:ca:ee:0f@192.168.1.37 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 09:06:14 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:33:03 :303022:  <WARN> |AP 00:0b:86:ca:3e:e6@192.168.1.39 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:33:10 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:33:17 :303022:  <WARN> |AP 00:1a:1e:c4:1d:fc@192.168.1.35 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:33:31 :303022:  <WARN> |AP 00:0b:86:ca:ee:0f@192.168.1.37 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:33:45 :303022:  <WARN> |AP 00:0b:86:ca:3d:2b@192.168.1.21 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 11:34:01 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 12:15:16 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 12:16:22 :303022:  <WARN> |AP 00:0b:86:ca:3d:2b@192.168.1.21 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 12:16:37 :303022:  <WARN> |AP 00:0b:86:ca:ee:0f@192.168.1.37 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 13:43:00 :303022:  <WARN> |AP 00:0b:86:ca:3e:e6@192.168.1.39 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 13:43:29 :303022:  <WARN> |AP 00:0b:86:ca:3d:2b@192.168.1.21 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 13:43:34 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 13:43:43 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 14:34:58 :303022:  <WARN> |AP 00:1a:1e:c4:1d:fc@192.168.1.35 nanny|  Rebo
    ot Reason: AP rebooted Fri Dec 31 16:01:54 PST 1999; failed to get master-ip
    Jan 14 16:05:32 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:06:00 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:06:11 :303022:  <WARN> |AP 00:1a:1e:c4:1d:fc@192.168.1.35 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:06:15 :303022:  <WARN> |AP 00:0b:86:ca:3e:e6@192.168.1.39 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:43:49 :303022:  <WARN> |AP 00:0b:86:ca:3d:2b@192.168.1.21 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:44:21 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:44:28 :303022:  <WARN> |AP 00:1a:1e:c4:1d:fc@192.168.1.35 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:44:32 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 14 16:44:40 :303022:  <WARN> |AP 00:0b:86:ca:3e:e6@192.168.1.39 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:00 :303022:  <WARN> |AP 00:0b:86:ca:b9:18@192.168.1.26 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:08 :303022:  <WARN> |AP 00:1a:1e:c4:1d:fc@192.168.1.35 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:16 :303022:  <WARN> |AP 00:0b:86:ca:ee:0f@192.168.1.37 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:38 :303022:  <WARN> |AP 00:1a:1e:cc:ff:5b@192.168.1.24 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:45 :303022:  <WARN> |AP 00:0b:86:ca:3e:e6@192.168.1.39 nanny|  Rebo
    ot Reason: No reboot message found.
    Jan 15 09:05:54 :303022:  <WARN> |AP 00:0b:86:ca:3d:2b@192.168.1.21 nanny|  Rebo
    ot Reason: No reboot message found.



  • 4.  RE: Access points connected to A2400 restart every 24 hours more o less

    EMPLOYEE
    Posted Jan 15, 2013 06:10 AM

    You should type "show poe" on the commandline to see if you are exceeding the power of the switch.  The message is what you would see if you suddenly interrupted the power to an access point.

     



  • 5.  RE: Access points connected to A2400 restart every 24 hours more o less

    Posted Jan 15, 2013 08:05 AM

    Thanks for your interest.

     

    The show command result is:

     

    PoE Status
    ----------
    Port     Status  Voltage(mV)  Current(mA)  Power (mW)
    ----     ------  -----------  -----------  ----------
    FE 1/0   On      47934        54           2710
    FE 1/1   On      47902        53           2707
    FE 1/2   On      47902        53           2634
    FE 1/3   On      47934        83           3063
    FE 1/4   On      47870        54           2750
    FE 1/5   Off     N/A          N/A          N/A
    FE 1/6   Off     N/A          N/A          N/A
    FE 1/7   On      47998        56           2721
    FE 1/8   Off     N/A          N/A          N/A
    FE 1/9   Off     N/A          N/A          N/A
    FE 1/10  Off     N/A          N/A          N/A
    FE 1/11  Off     N/A          N/A          N/A
    FE 1/12  Off     N/A          N/A          N/A
    FE 1/13  Off     N/A          N/A          N/A
    FE 1/14  Off     N/A          N/A          N/A
    FE 1/15  Off     N/A          N/A          N/A
    FE 1/16  Off     N/A          N/A          N/A
    FE 1/17  Off     N/A          N/A          N/A
    FE 1/18  Off     N/A          N/A          N/A
    FE 1/19  Off     N/A          N/A          N/A
    FE 1/20  Off     N/A          N/A          N/A
    FE 1/21  Off     N/A          N/A          N/A
    FE 1/22  Off     N/A          N/A          N/A
    FE 1/23  Off     N/A          N/A          N/A
    GE 1/24  Off     N/A          N/A          N/A
    GE 1/25  Off     N/A          N/A          N/A


    Total Power Usage: 16585 (mW)

     

    What is the maximum power?

     

    The access point at FE 1/3 has a higher consumption than the others. All of them are AP-61. Is it possible it has a bad functioning?

     

    Regards.