Skip to main content
Solved

Expansion of one HSX node to existing HSX environment

  • February 3, 2022
  • 3 replies
  • 299 views

karthik S U
Vaulter
Forum|alt.badge.img+1

Hi team,

 

we are in  a process of adding one more node and new node is imaged with 2.2 version where as existing three nodes are in HSX 2.1 version.

which option would be perfect,

1.do we need to downgrade new node to hsx 2.1 or

2. upgrade existing nodes from 2.1 to 2.2.  if yes, is it ok to just hedvig os upgrade to latest version using below cmd or is there any other procedure to follow.

 

a. cvupgradeos.py -upgrade_hedvig_only
b. cvupgradeos.py

Best answer by karthik S U

 

@R Anwar

 

thanks for the info.

action taken on this case.

upgraded hedvig to 4.5.3 

there was some issue while adding one node, however 11.24.30 Update on existing nodes fix the issues.

 

closing the thread.

View original
Did this answer your question?
If you have a question or comment, please create a topic

3 replies

karthik S U
Vaulter
Forum|alt.badge.img+1
  • Author
  • Vaulter
  • 2 replies
  • February 3, 2022

R Anwar
Vaulter
Forum|alt.badge.img+10
  • Vaulter
  • 114 replies
  • February 3, 2022

Hi @karthik S U 

2.x represent the CV & CDS version included with the ISO.

2.1 - SP20+CDS 4.2.3

2.2 - SP24+CDS 4.4
 

So if the older nodes are lower that 4.4, you need to upgrade. Also, if you run cvupgradesos-py -upgrade_hedvig_only, you would be upgrading to CDS 4.5.3

Post that you can run add nodes, which should first update the CDS rpm’s as well prior to adding nodes.


karthik S U
Vaulter
Forum|alt.badge.img+1
  • Author
  • Vaulter
  • 2 replies
  • Answer
  • February 10, 2022

 

@R Anwar

 

thanks for the info.

action taken on this case.

upgraded hedvig to 4.5.3 

there was some issue while adding one node, however 11.24.30 Update on existing nodes fix the issues.

 

closing the thread.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings