Wireless Access

 View Only
  • 1.  Aruba AP Frequent reboot in VC

    Posted 25 days ago

     Hello Team,

    We are facing an issue frequent AP reboot in virtual controller environment. Below is AP logs.

    AP uptime is 2 days 19 hours 37 minutes 53 seconds Reboot Time and Cause: AP rebooted Sun Jan 12 15:50:46 UTC 2025; System cmd at uptime 16D 23H 44M 34S: Preempted by provisioned conductor (54:f0:b1:cd:49:e0 10.1.1.43) uptime from boot: 2 weeks 2 days 23 hours 44 minutes 32 seconds; uptime from being conductor: 23 seconds end of show version


  • 2.  RE: Aruba AP Frequent reboot in VC

    Posted 25 days ago

    Do you have a preferred conductor configured?  Is that preferred conductor an older model of AP than the one that is rebooting?



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 3.  RE: Aruba AP Frequent reboot in VC

    Posted 24 days ago

    Hello there,

    Can you give us some more information please?  Can you tell us what the model of AP you are experiencing the issues with and what controller/MM hardware you are using and what AOS version you are running please?

    Thanks




  • 4.  RE: Aruba AP Frequent reboot in VC

    Posted 24 days ago

    Hi Max,

    The model is HPE Aruba Networking 503 Series Campus Access Points. We have around 60-70 access points which are deployed in Virtual Controller itself and enabled preferred conductor.




  • 5.  RE: Aruba AP Frequent reboot in VC

    Posted 24 days ago

    As Carlson already wrote, check if you have Preferred Conductor enabled on one of the APs. And disable it. Usually you don't need it except in specific situations.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Guru 2024
    ------------------------------



  • 6.  RE: Aruba AP Frequent reboot in VC

    Posted 24 days ago

    In your setup (all APs of the same model) there is no need for preferred conductor. It will just reduce the flexibility of the whole configuration. Without it any AP can become VC if needed. If you have some bigger APs in the configuration (example have 1 AP635) then it would make some sense to setup preferred conductor to the fastest AP. This ensures that the fastest AP stay conductor when it return to the network.

    By my experience even without preferred conductor selected, fastest AP in the cluster will usually take conductor role when it is joined to cluster.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Guru 2024
    ------------------------------