Skip to main content
mbrowndcm
mbrowndcm
New Member
April 16, 2012
Question

Triggering an HA failover?

  • April 16, 2012
  • 8 replies
  • 21302 views
Hello, How does one go about trigger an HA failover from the CLI? Specifically, how does one go about trigger a failback to the cluster member with the highest weight? Thanks, Matt

    8 replies

    Austin_M
    Austin_M
    New Member
    April 22, 2012
    to triiger a HA failover shutdown the monitored interface from the CLI and use ha override option so that a particular cluster member always becomes the master device .
    mbrowndcm
    mbrowndcmAuthor
    New Member
    April 23, 2012
    Thanks for your reply, Austin. What do you mean " shut down the monitored interface from the CLI" ? Do you mean the heartbeat interface? Support simply told me to run the following: 
      diag sys ha reset-uptime
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    April 23, 2012
    The diag command will simply eliminate the age of the cluster members as a criterion for choosing the primary unit. To shut down an interface via CLI would mean to put it ' administratively down' . If you' re in a test environment that might work. Pulling the cable is quicker though.
    mbrowndcm
    mbrowndcmAuthor
    New Member
    April 23, 2012
    Thanks Ede. I am not in a test environment. Therefore, I will simply use diag sys ha reset-uptime.
    Carl_Wallmark
    Carl_Wallmark
    New Member
    April 23, 2012
    another way to force HA-failover is to change the priority of the slave to a higher value then the master.
    mbrowndcm
    mbrowndcmAuthor
    New Member
    April 23, 2012
    Thanks Selective. How would I cause a fail back to the highest weighted member using this method?
    Matthijs
    Matthijs
    New Member
    April 23, 2012
      config sys ha  set override enable  end
    Carl_Wallmark
    Carl_Wallmark
    New Member
    April 23, 2012
    You can type this: execute manage ha <slave number> config system ha set priority <priority number> end
    Prab
    Prab
    New Member
    January 10, 2020

    Triggering a failover depends upon how you have configured the failover in first place. Assuming that you have the default setup. The selection is done in a sequence:

    Failed Monitored interfaces > Age >Device Priority > Serial number

     

    There are following ways to trigger the failover:

    1. Resetting one of the monitored interface on the primary unit. (Unplugging the cable or administratively shutdown the interface)

    2. Resetting the age of the primary unit (diagnose sys ha reset-uptime)

    3. Changing the device priority (this will not trigger the failover, you still need to trigger the failover afterwards)

    4. Using diagnose sys ha set-as-master enable command on an unit will make it the primary unit until it is rebooted. (Not a recommended method & not supported by all models!)

     

    Cheers,

    Prab

    Terms & ConditionsAccessibility statement