Cloud Managed Networks

 View Only

  • 1.  AP Auto Restart

    Posted Jan 29, 2024 12:26 PM

    Hi ,

    Please help.

    Why Aruba auto restart. 

    here i attach my log.

    *********************************************************************************************************
 1/29/2024 16:29:07 PM    Target: 18:64:72:c1:d2:3e    Command: show log system 
*********************************************************************************************************

Jan 28 03:12:28  syslog: <341005> <ERRS> |AP 18:64:72:c1:d2:3e: |  open core directory failed
Jan 28 03:12:28  syslog: <341005> <ERRS> |AP 18:64:72:c1:d2:3e: |  terminal access is enabled but sshd is not running, starting
Jan 28 03:12:28  KERNEL(18:64:72:c1:d2:3e@10.40.1.70): ip_time_handler: Got ip and packets on bond0 Started master election 1524-0, rand 34
Jan 28 03:12:31  nanny[2183]: <303022> <WARN> |AP 18:64:72:c1:d2:3e: |  Reboot Reason: No reboot message found.
Jan 28 03:12:46  nanny[2183]: <303074> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Process /aruba/bin/radiusd [pid 2305] died: exited with 0x1
Jan 28 03:12:46  nanny[2183]: <303079> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Restarted process /aruba/bin/radiusd, new pid 2365
Jan 28 03:12:55  cli[2224]: <341317> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Regulatory table file init at version 1.0_88140, build Oct 6,2023.
Jan 28 03:12:55  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Extended ssid enabled
Jan 28 03:12:55  cli[2224]: <341207> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP support up to 16 SSID.
Jan 28 03:12:56  cli[2224]: <341172> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Find enet0 name bond0.
Jan 28 03:12:56  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  CLI to PAPI port 8359 communication code 1
Jan 28 03:12:56  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  cli_choose_eth_uplink:eth current uplink set to DHCP
Jan 28 03:12:56  cli[2224]: <341169> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Add uplink Ethernet 0.
Jan 28 03:12:56  cli[2224]: <341167> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Uplink bond0 type Ethernet, state INIT->LOAD.
Jan 28 03:12:56  cli[2224]: <341169> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Add uplink Wifi-sta 6.
Jan 28 03:12:56  cli[2224]: <341169> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Add uplink 3G/4G 7.
Jan 28 03:12:56  cli[2224]: <341167> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Uplink  type Dummy, state INIT->LOAD.
Jan 28 03:12:56  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  release eth1 from bond0
Jan 28 03:12:56  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  after check,default cert exist
Jan 28 03:12:57  KERNEL(18:64:72:c1:d2:3e@10.40.1.70): (03:12:56) !!! Init ---> Master
Jan 28 03:12:57  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  recv non-3g setup_uplink finished from sapd
Jan 28 03:12:57  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  receive sapd hello for process recovery
Jan 28 03:12:58  cli[2224]: <341174> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  No current uplink, pick the highest one - Ethernet bond0.
Jan 28 03:12:58  cli[2224]: <341263> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  enable uplink bond0.
Jan 28 03:12:58  cli[2224]: <341167> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Uplink bond0 type Ethernet, state LOAD->PROBE.
Jan 28 03:12:58  cli[2224]: <341265> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  enable ethernet uplink bond0.
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  the ethernet uplink inuse in first time, get ip address.
Jan 28 03:12:58  cli[2224]: <341167> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Uplink bond0 type Ethernet, state PROBE->UP.
Jan 28 03:12:58  cli[2224]: <341185> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Retrieving ip address from br0, ip 10.40.1.70, mask 255.255.252.0.
Jan 28 03:12:58  cli[2224]: <341274> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Update election ip from br0, election ip 10.40.1.70/255.255.252.0.
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  build_my_ip_address: update old election ip with new ip
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  build_my_ip_address: old ip and new ip same; skipping
Jan 28 03:12:58  cli[2224]: <341006> <CRIT> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Sending uplink_up msg to sapd


Jan 28 03:12:58  cli[2224]: <341006> <CRIT> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  trap uplink info.
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  last uplink is null, it's the first uplink, ignore this trap.
Jan 28 03:12:58  cli[2224]: <341173> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Current uplink set to Ethernet, state UP.
Jan 28 03:12:58  cli[2224]: <341135> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Master Changed - new 127.0.0.1 old 0.0.0.0 current swarm state 0.
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Swarm State Change from Startup to Found
Jan 28 03:12:58  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  recv non-3g setup_uplink finished from sapd
Jan 28 03:12:59  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Swarm State Change from Startup to Found
Jan 28 03:13:02  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  CLI to PAPI port 8504 communication code 1
Jan 28 03:13:02  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Swarm State Change from Found to Image-ok
Jan 28 03:13:03  nanny[2183]: <303074> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Process /aruba/bin/radiusd [pid 2365] died: exited with 0x1
Jan 28 03:13:03  nanny[2183]: <303079> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Restarted process /aruba/bin/radiusd, new pid 2488
Jan 28 03:13:07  cli[2224]: <341194> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Loading configuration, func swarm_timer_handler, line 12278.
Jan 28 03:13:08  cli[2224]: <341101> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Execute command-configure terminal.
Jan 28 03:13:22  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Do CLI wlan factory
Jan 28 03:13:23  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  Swarm State Change from Image-ok to Complete
Jan 28 03:16:24  nanny[2183]: <303074> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Process /aruba/bin/rngd [pid 2272] died: exited with 0x0
Jan 28 03:16:24  nanny[2183]: <303076> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 nanny|  Non re-startable process /aruba/bin/rngd [pid 2272] has terminated
Jan 28 22:30:26  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP 10.40.1.70: Client 28:16:7f:e8:de:09 authenticate fail because integrity check failure in encrypted message
Jan 28 23:50:34  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP 10.40.1.70: Client 18:54:cf:2e:f1:bf authenticate fail because integrity check failure in encrypted message
Jan 29 00:06:39  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP 10.40.1.70: Client f6:fc:95:5c:f4:18 authenticate fail because integrity check failure in encrypted message
Jan 29 03:23:09  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP 10.40.1.70: Client 18:54:cf:2e:f1:bf authenticate fail because integrity check failure in encrypted message
Jan 29 03:35:12  cli[2224]: <341004> <WARN> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  AP 10.40.1.70: Client 18:54:cf:2e:f1:bf authenticate fail because integrity check failure in encrypted message
Jan 29 08:18:26  cli[2224]: <341092> <ERRS> |AP 18:64:72:c1:d2:3e@10.40.1.70 cli|  get_version_and_url_for_multi_class_image_upgrade: 5424: Parse error in payload.


  • 2.  RE: AP Auto Restart

    Posted Feb 12, 2024 10:58 AM

    What is your deployment? AP types? Firmware version? Instant/Controller/Central?

    From 

    Reboot Reason: No reboot message found.

    it seems there is no specific reason for the reboot.

    From: 

    get_version_and_url_for_multi_class_image_upgrade: 5424: Parse error in payload.

    it suggests that you have an Instant cluster running multiple AP models (type) and for some of the models there is no firmware available. That can be because you upgraded to a version that is not supported on all of your APs, or that you upgraded and later added another AP model to the cluster.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: AP Auto Restart

    Posted Feb 12, 2024 08:30 PM
    Greetings,

    My Aruba Access Point is 115
    6.5.4.27_88283(digitally signed - production build)
    instant type

    Thanks in advance.
    --



    Mohd Shahreen Bin Mohd Soffi




    Original Message


  • 4.  RE: AP Auto Restart

    Posted Feb 12, 2024 08:42 PM
    PLUS

    I already updated both my access points to the latest firmware.
    aruba prod.pngaruba office.png
    --



    Mohd Shahreen Bin Mohd Soffi




    Original Message


  • 5.  RE: AP Auto Restart

    Posted Feb 13, 2024 03:27 AM

    Do you have 2x AP-115? Are these on different locations?

    Instant APs should connect together in a cluster if they are in the same network. If you really want to keep configs separate, it may help to change the APs to Standalone mode (under the 'Convert' tab in your screenshot). In standalone mode the APs will not try to cluster or take firmware from another AP.

    Otherwise, please check that the management VLAN for both APs is native/untagged on the switch ports and it's the same VLAN. APs, when in swarm-mode (default) will connect together and form a cluster of 2 (or more) APs with a single management.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------

    Original Message


  • 6.  RE: AP Auto Restart

    Posted Feb 15, 2024 04:40 AM
    Greetings,

    Noted.

    One more thing, may i know what will happen if i change to standalone mode.

    PLease advise.

    Thank you.




    Original Message


Related Content