Scribd
Upload
2K views

SimpliVity CLI Upgrade Lab Guide

This document provides instructions for upgrading a SimpliVity OVC cluster. It outlines pre-upgrade checks that include migrating VMs, checking versions, and cluster health. Upgrade steps include uploading new software files, upgrading ESXi if needed, moving VMs, upgrading the arbiter and plugin, running the software upgrade command on each node while monitoring logs, and committing the upgrade after all nodes are complete. Post-upgrade checks validate the new version and cluster health.

Uploaded by

Balasubramanian Reguraman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2K views

SimpliVity CLI Upgrade Lab Guide

This document provides instructions for upgrading a SimpliVity OVC cluster. It outlines pre-upgrade checks that include migrating VMs, checking versions, and cluster health. Upgrade steps include uploading new software files, upgrading ESXi if needed, moving VMs, upgrading the arbiter and plugin, running the software upgrade command on each node while monitoring logs, and committing the upgrade after all nodes are complete. Post-upgrade checks validate the new version and cluster health.

Uploaded by

Balasubramanian Reguraman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

SimpliVity CLI Upgrade Lab Guide:

Lab 1: Pre-Checks before Proceeding for an Upgrade:

There are mandatory Pre-Checks which should be done before any upgrade of a SimpliVity OVC.
Otherwise the production environment will be at stake.

1. Migrate all the running VMs to another SVT Cluster which is not going for an upgrade as

of now.

2. Putty into the Omnistack Virtual Controller and login with vCenter Credentials.

3. In case the vCenter credentials do not work login with Username: svtcli and Password:

simplicity (Ask the customer about the CLI password)

4. Once logged in run the command svt-session-start and login with the vCenter

credentials.

5. Run the command svt-federation-show.

6. Ensure the SimpliVity version you are currently running and on the basis of that please

follow the Interoperability Guide and check the upgrade path.

7. Check with the Firmware version of current node at the iLo. Check if you need to do an

upgrade or not.

8. Check with the ESXI version that is running on the nodes. If necessary you might need to

upgrade the ESXI version of the SimpliVity nodes at the bare-metal level.
9. Check with the vCenter build. If there is a need for an upgrade of the vCenter please ask

the customer to keep it ready for the next call. All these information will be there in the

Interoperability Guide.

10. Ask the customer to download the necessary files required for the upgrade. You should

give the SAID and he can get it downloaded using the same.

Image of SVT Federation Show

Lab 2: Preparing Pre – Requisites for the Upgrade

1. If there is a need of ESXI upgrade, then it’s mandatory to upgrade the ESXI at the bare-

metal level of the nodes. If there is no need then proceed with the steps below.
2. At the Upgrade directory there will be 2 files. One will be SimpliVity Omicube Software

xxxxxxxx.tar and SimpliVity Omnicube Sofware xxxxxx.sha1. Make a new directory at

your SVT datastore and upload these 2 files there.

Image of SimpliVity Datastore Upgrade Files Uploaded

3. Check the Federation Health before proceeding for the upgrade. Only proceed if

everything node is healthy. If there are unhealthy nodes migrate all the VMs to the

healthy node in the other cluster which will go for upgrade after the former cluster is

upgraded. Shut down the OVC of the unhealthy node and put it under maintenance

mode. However it is best if you could see what is wrong in the node and try to fix it.

4. Use the SimpliVity move option to move all the important VMs running to the other

cluster which will not go for an upgrade as of now. (It will go for the upgrade after the

former cluster is upgraded). This is done so that production is not hampered.


5. Go to the Jump Server where initially the Arbiter was installed. Uninstall the old Arbiter

and install the new Arbiter compatible with the upgraded version of SimpliVity

OmniCube Software. Check if the Arbiter service is running or not at services.msc

6. Install the new SimpliVity Plugin after uninstalling the old plugin at the vCenter server.

Lab 3: Upgrade Steps

1. Login to the OVC of any SimpliVity node using vCenter credentials in a cluster which

needs to be upgraded. Please note that at one point of time a cluster as a whole gets

the upgrade.
2. Run the command df –h to know the path where the SVT Upgrade files reside. The SVT

upgrade files will be approximately 1.8GB. Please compare the file sizes.

Image of df –h output

This way it will be easy to identify where the upgrade file is located. Also note that the

upgrade files should be in the same directory.

3. Type in the command svt-software-upgrade –pkgpath - (Type in the path)

Example of Software Upgrade Path and Command


4. Run this command tail –f /var/log/svt-upgrade.log to tail with the log file and monitor

the upgrade process.

SVT Software Upgrade Log Command

5. Do the Upgrade for the other clusters using the same process. Make sure you migrate

all the Production VMs to the non-upgrading cluster.

6. After upgrade is complete there is still one task left. You need to commit the upgrade.

That will ensure that there would be no rollback chances and you will be able to use the

full functionalities of the new version of SimpliVity OmniCube. The command for the

same is svt-software-commit. (Only run this command when you have upgraded all the

Nodes in all the Clusters)

7. Once the commit process is completed do a svt-federation-show to check the SVT

Version.
8. Also check in the vCenter tasks. Once the commit is done you will see something like

this.

9. Do the post upgrade checks. This is similar to Pre-Deployment Checks and use the plugin

to ensure everything is alright.

Thank You!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy