Documentation on this here. I believe that during major upgrades, that 24 hour is extended to 48 or 72 hours, but can't find the number quickly.
------------------------------
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:
Sent: Aug 24, 2023 04:48 AM
From: ariyap
Subject: Subscriber node disabled
this is the correct behaviour.
The subscriber will go to OUT OF SYNC state for up to 24 hours before it is treated as disabled from the publisher. After 24 hours in which the publisher is unable to communicate with the subscriber it will mark the node as DISABLED. From the subscribers point of view it would just show OUT OF SYNC.
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
Original Message:
Sent: Aug 24, 2023 04:18 AM
From: peter.elms
Subject: Subscriber node disabled
hello Airheads,
quick question.
Customer is running 6.11.4 Clearpass.
1 x PUB and 3 x SUBS
Customer powered down 2 SUBS over the weekend but when they powered them back up again they were "node disabled" on the PUB.
It was quite straightforward to get them back into the cluster but they are asking "is this expected behaviour" ?
is there a timeout value that can be altered ?
just wondering how to respond to customer.
cheers
Pete