Solace Community is getting a facelift!

On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.

We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!

upgrade procedure of monitoring node

kiakia
kiakia Member Posts: 6 ✭
in General Discussions #1

Hi experts,

I have a redundancy env including two msg-routing nodes and one monitoring node as Active/Standby, and want to confirm upgrade procedure(s) of the monitoring node, which is not mentioned in the doc below.

https://docs.solace.com/Solace-Appliance-Upgrade/Upgrade-Redundant-Appliances.htm#With

Could anyone help me guide a document link or something, which would make me clear everything?

Many thanks in advance,
Kia

Comments

  • kiakia
    kiakia Member Posts: 6 ✭
    #2

    In addition, "show disk" command doesn't work and it looks like the CLI does NOT have it.
    Is there any information such as release notes that describes the command is not available in version 9.3?

    Thx,
    Kia

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 973 admin
    #3

    Hi @kiakia,

    Since you have a monitoring node I think you probably have software brokers. The link that you included in your first post is for our hardware appliances and the upgrade procedure would be different. Can you start with the upgrade procedures for software and see if that is more clear for you? https://docs.solace.com/Solace-SW-Broker-Upgrade/SW-Broker-Upgrade.htm

    Hope that helps!

  • kiakia
    kiakia Member Posts: 6 ✭
    edited October 2021 #4

    Hi @marc,

    Thank you very much for an update.

    Yes, you are right that we have software brokers!
    Now we can proceed furher. :)

    One more quick question.
    Is there any best practice to recover from corrupted environment when upgrade script fails?
    For example, we have to run the script again with older version tar ball for downgrading? or there's something where we can save as a backup for such unexpected upgrade results?

    Regards,
    Kia

Categories

This Month's Leaders

This Week's Leaders