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

UTM Slave node got unlicensed because of left "reserved"?

Hi,

running an a/p cluster of two SG 135. Some time ago we performed an update to 9.702-1 and left one node "reserved". Unfortunately we left him in this state for a couple of days.

Today at midnight, slave went to "DEAD". Today is the end of a license that has been renewed but I guess due to the fact that the slave was reserved there was no replication anymore. And no replication of the renewed license. And the slave got unlicensed and turned to death state.

How to get the slave back to the licensed cluster?

Thanks for any advice.

Cheers

Philipp

This thread was automatically locked due to age.

Parents

0 Alexander Busch over 4 years ago

Hey Philipp,

I would try to reset / remove the dead node and then get the node back in the cluster via auto configuration.
That can be done without any downtime. Until the end of the process I would detach all Ethernet cables except eth3 from the dead node.

Best regards

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Philipp Thielke1 over 4 years ago in reply to Alexander Busch

Hey Alex,

thanks for your advice. Do you think that this will work even the dead slave node isn‘t on the same firmware release as the current master?

Regards,

Philipp
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 4 years ago in reply to Philipp Thielke1

Yes, the ‘new’ node will do the Up2date while getting part of the cluster. I already considered that.

Best regards

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Philipp Thielke1 over 4 years ago in reply to Alexander Busch

Perfect! I‘ll try that asap and keep you tuned. Many thanks.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Philipp Thielke1 over 4 years ago in reply to Alexander Busch

Perfect! I‘ll try that asap and keep you tuned. Many thanks.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data