Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 4043 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

9.405-5 HA broken. New slave stays in Up2Date mode

MikeHollenbeck

Did the up2date installation. Took a long time for the new Master to come on line.

The new slave stays in Up2Date status and it's been 2 days. 

2x SG330 in Hot standby mode. 

Nervous about rebooting the slave when it is stuck in Up2date mode. Any comments?



This thread was automatically locked due to age.
Parents
  • 0

    Hi, Mike.

    What version did you up2date from? What version is showing in master and slave now?

    Most of the time, rebooting the slave will solve this kind of issue. If all goes wrong (which is highly unlikely), you can always kick your slave out of the cluster, reimage it to the same version of the master and rejoin it to the cluster. There's no risk of losing anything here.

    Regards - Giovani

  • 0 in reply to giomoda

    Upgraded from 9.404-5. Kind of what I thought with the reboot.

    I will give that a try in the morning.

Reply Children
  • 0 in reply to MikeHollenbeck

    Well that (finally) worked.

    I rebooted the slave and when it came back on line, it showed the current FW release. The unit seemed to be stuck in "syncing" mode.

    RTW from the weekend and the slave was still syncing.

    Rebooted the slave a second time and within minutes the two were synced and working properly.

    Solved.

Unfiltered HTML