Upgrade a Client

Upgrading a Debian Linux client requires installing these quantum-supplied packages:

• zeromq
• protobuf

These packages are used by StorNext and are bundled with the StorNext .bin file.

Note: When upgrading RedHat and SUSE Linux clients, the snupdate service installs these packages.

Upgrading Redhat and SUSE mover clients requires installing these additional quantum-supplied DDM packages:

• quantum_curl
• quantum_openssl
• snfs-mover
• quantum_unixODBC
• snltfs

Note: Upgrading these packages might require using the --force option.

The snupdate service allows you to manage StorNext software packages by providing the ability to install, upgrade, remove, and rollback StorNext software packages. The snupdate service works with supported clients listed in the StorNext Compatibility Guide, such as:

• RedHat

• CentOS

• SUSE

• Debian

• Ubuntu

Packages can be applied immediately, or they can be staged and updated at a later time. The snupdate service is a boot time script that starts before cvfs. It checks to see if there are staged updates available. If an update has been staged, the snupdate service will apply that update.

The snupdate service, located in the /etc/init.d/ directory, calls the snupdate utility (/opt/quantum/snupdate/bin/snupdate) which performs the actions and manages the snupdate repository (/opt/quantum/snupdate/var).

The snupdate repository consists of a set of packages. These packages are the contents of the extracted StorNext .bin archives. The snupdate has the ability to install, update, and remove a package that is copied into the repository. It also has the ability to rollback a package to a previous version, provided that the package supports the ability to downgrade its version.

The snupdate utilty can stage an install, upgrade, or rollback (if the package supports rollback) by marking in the repository the next version that the package should be updated to. The staged action is applied at a later time by the snupdate apply command.

Multiple versions of a package can be copied into the snupdate repository. The snupdate utility will determine which version of a package is currently installed and keep track of the previously installed version for the purpose of rollback. It can also detect if there is a newer version in the repository for upgrades.

Note: You must use the latest version of snupdate when you install or upgrade StorNext.

There are three types of client packages available (for more information, see Download the StorNext Client Software).

The snupdate utiltiy supports an interactive help system. Running /opt/quantum/snupdate/bin/snupdate help will provide a list of available snupdate commands. The table below lists the available commands.

The help system syntax is:

To get additional information on a command, type:

Note: You must use the latest available version of snupdate when you install StorNext.

To install or upgrade the snupdate service, complete the following:

1. Run the StorNext .bin command to extract a StorNext package. The snupdate package is bundled with the StorNext .bin file.

   Note: The StorNext package will extract into /tmp/stornext directory by default. If this directory exists, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, for example:

   # ./<archive name> -d <dir>

   where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files.

   
   

2. Change to the directory where you extracted the contents of the .bin file.
3. Install the snupdate service by running this command:

   • On RedHat or SUSE Linux execute:

     # rpm -Uvh snupdate-<version>.rpm

     Example for Linux:

     # rpm -Uvh snupdate-1.0.9-730.1.x86_64.rpm

     Verifying... ################################# [100%]

     Preparing... ################################# [100%]

     Updating / installing...

     1:snupdate-1.0.9-730.1 ################################# [100%]

     Created symlink /etc/systemd/system/multi-user.target.wants/snupdate.service → /usr/lib/systemd/system/snupdate.service.

     Example for SUSE:

     # rpm -Uvh snupdate-1.0.9-730.1.x86_64.rpm

     Preparing... ################################# [100%]

     Updating / installing...

     1:snupdate-1.0.9-730.1 ################################# [100%]

   • On Debian or Ubuntu Linux execute:

     # dpkg --install snupdate-<version>.deb

4. Run the following command to check the installed version of snupdate:

   • On RedHat or SUSE Linux execute:

     # rpm -q snupdate

   • On Debian or Ubuntu Linux execute:

     # dpkg --list snupdate

To import a StorNext package into an snupdate repository, complete the following:

1. Import the /tmp/stornext package into the snupdate repository. The snupdate tool determines the package name and version of the package and copy the package into /opt/quantum/snupdate/var/PACKAGE/VERSION, for example:

   # /opt/quantum/snupdate/bin/snupdate import /tmp/stornext/

   Checking for new packages in /tmp/stornext

   Copying 6.0.0-38570/ to /opt/quantum/snupdate/var/<snfs client package>/6.0.0-38570

   If you extracted the .bin file into another directory, such as /tmp/stornext6/, then import the contents of the directory to the snupdate repository.

   # /opt/quantum/snupdate/bin/snupdate import /tmp/stornext6/

   Checking for new packages in /tmp/stornext6

   Copying 6.0.0-38570/ to /opt/quantum/snupdate/var/<snfs client package>/6.0.0-38570

2. Run the show versions command to ensure the package was imported:

   # /opt/quantum/snupdate/bin/snupdate show versions

   package: snfs_client

   version: 5.0.0-38570 (Current)

   version: 6.0.0-38570

   package: snfs_full

   version: (none)

   package: stornext_full

   version: (none)

To immediately upgrade a package, complete the following:

1. Upgrade to the latest version of the client package that is available in the /opt/quantum/snupdate/var repository:

   #/opt/quantum/snupdate/bin/snupdate upgrade <snfs client package>

   Upgrading <snfs client package> /opt/quantum/snupdate/var/<snfs client package>/6.0.0-38570...

   Preparing... ######################################## snfs-common ######################################## <snfs client package> ########################################

   CC [M] /usr/cvfs/install/linuxif_fs.o

   CC [M] /usr/cvfs/install/linuxif_fs_common.o

   CC [M] /usr/cvfs/install/linuxif_fsctl.o

   LD [M] /usr/cvfs/install/cvfs.o

   Building modules, stage 2.

   MODPOST 1 modules

   CC /usr/cvfs/install/cvfs.mod.o

   LD [M] /usr/cvfs/install/cvfs.ko.unsigned

   NO SIGN [M] /usr/cvfs/install/cvfs.ko

   INSTALL /usr/cvfs/install/cvfs.ko

   DEPMOD 2.6.32-279.el6.x86_64

2. Restart the cvfs service:

   • On Linux execute:

     /usr/cvfs/bin/DSM_control start

3. Run the show versions command to verify the installed version. The output will show a status of Current, as shown:

   #/opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Previous)

   version: 6.0.0-38570 (Current)

To stage an upgrade of the package to another version, complete the following:

1. Assuming the packages have been imported as shown in the previous procedure, list the available versions.

   # /opt/quantum/snupdate/bin/snupdate show versions snfs_client

   package: snfs_client

   version: 5.0.0-38570 (Current)

   version: 6.0.0-38570

2. Verify that the package update is available:

   # /opt/quantum/snupdate/bin/snupdate status

   Upgrade available for package: <snfs client package> (6.0.0-38570)

3. Stage the upgrade using the snupdate stage command:

   #/opt/quantum/snupdate/bin/snupdate stage upgrade <snfs client package>

   Staging upgrade of <snfs client package> to version 6.0.0-38570

4. Check on the status of snfs_client package to see that it has been marked to be updated:

   #/opt/quantum/snupdate/bin/snupdate status

   Staged upgrade scheduled for package: <snfs client package> (6.0.0-38570)

   You could also verify the updates by running the snupdate service command:

   # snupdate service status

   Staged upgrade scheduled for package: <snfs client package> (6.0.0-38570)

5. Verify the new update has been staged by running the show versions command:

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Current)

   version: 6.0.0-38570 (StagedUpgrade)

1. Verify that a staged update is available.

   # /opt/quantum/snupdate/bin/snupdate status

   Staged upgrade scheduled for package: <snfs client package> (6.0.0-38570)

2. The cvfs service wil need to be stopped and unloaded prior to starting the snupdate service.

   • On Linux execute:

     /usr/cvfs/bin/DSM_control fullstop

3. Staged updates are applied on the next reboot. Alternatively, you can apply a staged update manually.

   # /opt/quantum/snupdate/bin/snupdate apply

   Checking for new packages in /tmp/stornext package /opt/quantum/snupdate/var/<snfs client package>/6.0.0-38570 is already up to date

   Staged upgrade scheduled for package: <snfs client package> (6.0.0-38570)

   Upgrading snfs_client package /opt/quantum/snupdate/var/<snfs client package>/5.0.0-38570...

   Preparing... ######################################## quantum_zeromq ##################################### quantum_protobuf #####################################

   snfs-common ######################################## snfs-client ########################################

   CLEAN /usr/cvfs/install/.tmp_versions

   CLEAN /usr/cvfs/install/Module.symvers /usr/cvfs/install/modules.order

   CC [M] /usr/cvfs/install/linuxif_fs.o

   CC [M] /usr/cvfs/install/linuxif_fs_common.o

   CC [M] /usr/cvfs/install/linuxif_fsctl.o

   LD [M] /usr/cvfs/install/cvfs.o

   Building modules, stage 2.

   MODPOST 1 modules

   CC /usr/cvfs/install/cvfs.mod.o

   LD [M] /usr/cvfs/install/cvfs.ko.unsigned

   NO SIGN [M] /usr/cvfs/install/cvfs.ko

   INSTALL /usr/cvfs/install/cvfs.ko

   DEPMOD 2.6.32-131.0.15.el6.x86_64

   No staged action defined for snfs_full

   No staged action defined for stornext_full

4. After running snupdate to upgrade, rollback, or apply a staged operation, the cvfs service will need to be restarted:

   • On Linux execute:

     /usr/cvfs/bin/DSM_control start

   If you configured your system to use the StorNext File System Pooling feature, then you must execute the command below to restart the primary file system pooling service:

   sntier service --enable

   • Verify sntier is enabled:

     sntier service

     Tiering service is enabled.

To rollback to the previously installed version, complete the following:

1. Identify the versions currently in the repository using the show versions option, for example:

   #/opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Previous)

   version: 6.0.0-38570 (Current)

2. Stage a rollback to a previously installed version by using the stage rollback option. You can also use a specific version to rollback to a different version instead of the last installed version:

   #/opt/quantum/snupdate/bin/snupdate stage rollback \ <snfs client package> 5.0.0-38570

   Staging rollback of <snfs client package> to version 5.0.0-38570

3. Use the option, show versions, to list the current versions of a package and the intended states.

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Previous,StagedRollback)

   version: 6.0.0-38570 (Current)

4. Use the snupdate apply command or the service snupdate start command to make the StorNext software update take effect.

   # /opt/quantum/snupdate/bin/snupdate apply <snfs client package>

   Rolling back <snfs client package> to /opt/quantum/snupdate/var/<snfs client package>/5.0.0-38570...

   CLEAN /usr/cvfs/install/.tmp_versions

   CLEAN /usr/cvfs/install/Module.symvers /usr/cvfs/install/modules.order

   Preparing... ########################################

   snfs-common ######################################## snfs-client ########################################

   CC [M] /usr/cvfs/install/linuxif_fs.o

   CC [M] /usr/cvfs/install/linuxif_fs_common.o

   CC [M] /usr/cvfs/install/linuxif_fsctl.o

   LD [M] /usr/cvfs/install/cvfs.o

   Building modules, stage 2.

   MODPOST 1 modules

   CC /usr/cvfs/install/cvfs.mod.o

   LD [M] /usr/cvfs/install/cvfs.ko.unsigned

   NO SIGN [M] /usr/cvfs/install/cvfs.ko

   INSTALL /usr/cvfs/install/cvfs.ko

   DEPMOD 2.6.32-279.el6.x86_64

5. Use the show versions to show that rollback succeeded.

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Current)

   version: 6.0.0-38570 (Previous)

A staged update operation may be canceled using the snupdate cancel command. To cancel a staged update, complete the following:

1. Use the snupdate show versions command to list the available versions:

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Previous,StagedRollback)

   version: 6.0.0-38570 (Current)

2. Use the snupdate cancel command to cancel the pending staged update for a package:

   # /opt/quantum/snupdate/bin/snupdate cancel <snfs client package>

   package: <snfs client package>

   Canceling staged rollback for package <snfs client package>

3. Verify that the staged update has been canceled using the show versions command:

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570(Previous)

   version: 6.0.0-38570 (Current)

Use the snupdate clean command to clear stale versions from the snupdate repository. Complete the following:

1. List the current packages using the show versions command.

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 5.0.0-38570 (Previous)

   version: 6.0.0-38570 (Current)

2. Delete the stale StorNext packages from the repository in the /opt/quantum/snupdate/var directory using the clean command. The clean command requires both a package name and a version:

   # /opt/quantum/snupdate/bin/snupdate clean <snfs client package> 5.0.0-38570

   Removing /opt/quantum/snupdate/var/<snfs client package>/5.0.0-38570 from repository

3. Verify the package has been removed from the repository using the show versions command:

   # /opt/quantum/snupdate/bin/snupdate show versions <snfs client package>

   package: <snfs client package>

   version: 6.0.0-38570 (Current)

Follow these steps to upgrade a Debian Linux client.

1. Log on to the StorNext client system as root.
2. Change to the directory where the client software archive file you downloaded is located.

3. Extract the Debian client package (for example, snfs_client_Debian8_x86_64.bin). When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA, type y to accept the EULA, or enter any other key to decline. After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location).

   Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command:

   # ./<archive name> -d <dir>

   where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files.

   Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command:

   # ./<archive name> -d <dir>

   where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files. It is NOT recommended that you force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

4. From the /tmp/stornext directory, install the required SNFS packages first, and then install the client and common software packages. For example:

   dpkg -i quantum-protobuf_<version>.deb

   dpkg -i quantum-zeromq_<version>.deb

   dpkg -i snfs-common-<version>.deb

   dpkg -i snfs-client-<version>.deb

5. Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC to which the StorNext client will connect. The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it.

   Note: The fsnameservers file needs to contain only the IP address of the MDC.

6. If this is a SAN client, check to make sure LUNs are visible. At the command prompt, type:

   /usr/cvfs/bin/cvlabel -l

7. Create a mount point. For example:

   /stornext/<snfs1>

   Where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system.

8. Edit the /etc/fstab to add the client mount options. For example:

   <snfs1> /stornext/snfs1 cvfs rw,noauto 0 0

   Where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system.

9. Start the file system service. At the command prompt, type:

   service cvfs start
10. Verify file systems are mounted.