Upgrade to 3.1.0

• Make sure your system supports upgrades to this Appliance Controller release. For detailed compatibility information, see Compatibility.
• Backup any files you have modified since the last Appliance Controller upgrade.

Note: You will lose any modifications you have made to Appliance Controller files. If you have made modifications to any Appliance Controller files, you will have to re-apply those modifications again after you upgrade.

• Verify which version of Appliance Controller is running on the system. Here's how:

  Determine Which Software Versions the System is Running

  To see your current versions of StorNext and the Appliance Controller / StorNext NAS:

  1. Log in to the Appliance Controller CLI.
  2. Enter system show version.

     Example:

     > system show version

     You will see this (click to enlarge):

     

• Verify that all nodes being upgraded are healthy, including:
  • If you just recently upgraded firmware on the appliance, did the upgrade complete successfully?
  • Are all the nodes running as expected?
  • Are all the controller services running?

  • Is the /var/upgrade directory empty on all the nodes?

    Caution: If you attempted to upgrade StorNext on the system (the system firmware) and the upgrade did not complete, it might have pre-staged the Appliance Controller upgrade RPM file into the /var/upgrade directory. You must remove all contents of the /var/upgrade directory before you proceed with the upgrade process.

    Determine if the /var/upgrade directory is not empty

    Open an SSH connection to the server and use the IP address used to access the server on the Management (public) or LAN Client (private) network:

    1. Log in to the command line using the following credentials:
       • User name: stornext
       • Password: <stornext user account password>

         Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.

    Note: If the password for the stornext user account was changed after installation, use the current password.

    4. Change to the /var/upgrade directory:

    > cd /var/upgrade

    5. List the directory contents:

    > ls

    If the directory is not empty, run the following to remove the contents:

    > rm –rf *

• Obtain the upgrade file and move to the correct directory for the upgrade. Here's how:

  Download and move the upgrade file to the correct directory

  1. Obtain the System Serial Number for the system and then go to the Appliance Controller Downloads page.
  2. Click the Download button in the appropriate section of the page for the version of Appliance Controller you need to download.

  Note: You may need to provide your serial number and accept the EULA (End-User License Agreement) in order to download the upgrade.

  3. In the Quantum Downloads window, enter your appliance serial number, select the "I accept" check box, and click Accept. Download the upgrade file to your system.

  Examples:

  Note: File names differ depending on the version of Appliance Controller upgrade and CentOS.

  • CentOS 7 (identified as "el7") upgrade for Appliance Controller 3.1.0 (or later):

    (xxxxx indicates the build number of that software version)

    quantum-appliance-controller-3.1.0-xxxxx.el7.x86_64.bin
  4. Move the upgrade file to the system. If you have direct access to the system command line through the Service Port, you can move the files to the server that way. For remote system connections, move the file with an scp utility, as described here:

  Transfer the files with SCP:

  Prerequisites
  Before beginning an SCP file transfer, you will need the following:
  1. An SCP (Secure Copy) client must be installed on the system you plan to use remote access and configured the software for binary scp file transfers.
  Examples: Windows SCP clients
  • WinSCP - Windows-based SCP client with GUI, and drag-and-drop file transfer.
  Enable binary file transfers
  1. Open WinSCP, choose the Stored sessions option and select the session used for connecting to the MDC server node.
  2. Click Edit > SCP in the Protocol > File protocol section.
  3. Click Preferences > Preferences > Transfer and select the option for Binary (archives, doc,...) in the Transfer Mode section of the dialog.
  4. Click OK, then click Save.
  • PuTTY pscp.exe - Command-line based SCP client
  Example: macOS SCP
  • Terminal - Command-line based SCP client; included in macOS.
  2. The required file(s) have been acquired and are available on the laptop you will use to remotely access the system. This can include .iso image files.
  3. Login credentials to access the system.
  SCP file transfer to the system

  Before a file can be used on the system, you must first move it to a directory accessible via an SCP connection on the system. Do the following to move a file to a temporary location on the server.

  Example (PuTTY SCP on Windows):

  1. Open a command prompt (in Windows, click the Windows Start Menu, type cmd in the search field and click Enter).

  2. Enter the following (the default installation location for PuTTY pscp.exe is used in the first argument):

     "C:\<path to pscp.exe>\pscp.exe" C:\<local directory to copy file(s) from>\* stornext@<host server>:/home/stornext

  Example:

  "C:\Program Files (x86)\PuTTY\pscp.exe" C:\temp\* stornext@suppgate2.dnw.quantum.com:/home/stornext

  3. When prompted, enter the password for the stornext user account on the system.

  Example:

  stornext@suppgate2.dnw.quantum.com's password:

  Extract the contents of the upgrade .bin file

  If you are not logged in to the system, do the following:

  Open an SSH connection to the server and use the IP address used to access the server on the Management (public) or LAN Client (private) network:

  1. Log in to the command line using the following credentials:
     • User name: stornext
     • Password: <stornext user account password>

       Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

  2. Enter sudo rootsh to gain root user access.
  3. Enter the password for the stornext user account again.

  Note: If the password for the stornext user account was changed after installation, use the current password.

  If you are already logged into the command line of the appliance, do the following:

  1. Change to /home/stornext (or the location where the upgrade .bin file was copied to).

  2. Run the following to make the binary file executable:

     chmod 755 /tmp/quantum-appliance-controller-3.1.0-xxxxx.el7.x86_64.bin

  3. Execute the binary file:

     ./quantum-appliance-controller-3.1.0-xxxxx.el7.x86_64.bin

  4. When you are presented with the End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA, press y to accept the EULA, or enter any other key to decline. After you accept the EULA, the archive is extracted to /var/upgrade. For example:

     Press Enter to view the End User License Agreement
     ******************************************************
                                   Quantum Corporation
     
                                End User License Agreement
     
        This End User License Agreement ("EULA") defines the terms and conditions
        of the license between Quantum Corporation, a Delaware corporation with
        offices located in San Jose, CA ("Quantum") and the Licensee (as defined
        below) for use of Quantum's Software and Documentation. Any Software or
        Documentation provided to Licensee by Quantum will be subject to the terms
        and conditions of this EULA, and by downloading, installing, or using the
        Software or Documentation; Licensee signifies its agreement with this
        EULA. If Licensee does not agree to all of the terms of this EULA, then
        Licensee must not download, install, or use the Software or Documentation.
     
        1. DEFINITIONS
     
        a. "Designated System" means the specific hardware, workstations, servers,
        and/or devices enabled by one instance or copy of Software that is
        specified by Quantum at the time the Software is licensed.
     
        b. "Documentation" means the manufacturer's published specifications
        accompanying Software or made generally available online at Quantum's
        website, (as applicable) and any updates thereto, in any form or media
        provided.
     
        c. "License" is the license granted to Licensee by Quantum to use the
        Software and the Documentation, as further described herein, and shall
        mean "Perpetual Software License" and "Software License Subscription,"
     After End User License Agreement is accepted,
     the installer files will be extracted to /var/upgrade
     Do you accept the End User License Agreement? (y/n): y
     Extracting archive.................................
     Files extracted to /var/upgrade

1. Log in to the Appliance Controller CLI.

2. Verify the status of the port used for the iSCSI connection (the iSCSI target interface). Enter:

   iscsiadm show status

3. Verify the output shown for all initiators’ subnet_a and subnet_b target portals are similar to the following (items in green). Example output:

   "subnet_a": [

   {

   "portal": {

   "ip_state": "Accessible",

   "ipaddress": "192.168.0.10",

   "session_state": "logged in"

   }

   },

Note: If all the ip_state are Accessible and/or all the session_state are logged in, continue with the Appliance Controller upgrade. If not, DO NOT continue with the software upgrade. First, make sure the cable used for the port is connected and you can ping the IP address on the network. Fix your iSCSI target network connection before applying the Appliance Controller upgrade.

Upgrade NAS clusters from a master node and CAN access the online upgrade repository (it has an active internet connection)

This procedure upgrades all nodes in the NAS cluster from a NAS master node over an internet connection.

Caution: Before you continue with an upgrade, see Prerequisites.

Note: For online upgrades ,you must have internet access; if a firewall is in place, you must configure your firewall to allow access to quantum.com.

1. Log in to the Appliance Controller CLI on the master node.
2. Execute the system upgrade command from the master node ONLY, and enter yes to confirm:

Example output:

> system upgrade

The following Packages will be upgraded:

------------------------------------------------------------

<packages_available_for_upgrade>

------------------------------------------------------------

*** During system upgrade, filesystem access will be interrupted. Continue (yes/No)? yes

Working... this may take some time...

 

Verifying NAS Cluster upgrade state for local packages ...

Sending nascluster_upgrade_check to node 10.65.191.32

Waiting for nascluster_upgrade_check to complete on node 10.65.191.132

[10.65.191.132]: Verifying NAS Cluster upgrade state for local packages ...

3. Execute the nascluster show command to verify the system is operating properly after the upgrade. In this case, the example below shows the output from a NAS master node after an upgrade has completed. The green highlighted text shows the node is a master node, both nodes are joined to the NAS cluster, and is operational ("active").

Example output:

> nascluster show

NAS Cluster IP: 10.40.195.136/em2, Master: Yes, SNFS Root: /stornext/laguna_FS01, Joined: Yes

ID: 0

Cluster Hostname:

DNS Enabled:

No Load balancing: Proxy-Disabled

NFS-HA: Disabled

Master IP: 10.40.195.136

laguna-a.test.com

VIP: 10.40.195.165 (active, node:master) lagun-vip.test.com Nodes: 2

1: 10.40.195.137 (Joined, MDC) laguna-b.test.com

2: 10.40.195.136 (Joined, MDC) laguna-a.test.com

4. Execute the system status all command. The green highlighted text which shows the Appliance Controller is currently operational after the upgrade.

Example output:

> system status all

snnas_controller: running

sssd: running

ctdb: running

smbd: running

winbind: running

nfs: running

haproxy: disabled

keepalived: running

snmpd: disabled

5. Execute the system show version command. See the green highlighted text below which shows the system is running Appliance Controller 3.1.0 after the upgrade.

Example output:

(xxxxx indicates the build number of that software version)

> system show version

Quantum BHM Appliance Controller 3.1.0-xxxxx, Platform 7.0.x.OS7-xxxxx, OS 7.x.xxxx

Upgrade NAS clusters from a master node but CAN NOT access the online upgrade repository (does not have an active internet connection)

This procedure upgrades all nodes in the NAS cluster from a NAS master node with upgrade files located in the /var/upgrade directory.

Caution: Before you continue with an upgrade, see Prerequisites.

1. When the upgrade file has been moved to /var/upgrade, execute the system upgrade local command from the master node ONLY, and enter yes to confirm:

Example output:

> system upgrade local

The following Packages will be upgraded:

------------------------------------------------------------

<packages_available_for_upgrade>

------------------------------------------------------------

*** During system upgrade, filesystem access will be interrupted. Continue (yes/No)? yes

Working... this may take some time...

 

Verifying NAS Cluster upgrade state for local packages ...

Sending nascluster_upgrade_check to node 10.65.191.32

Waiting for nascluster_upgrade_check to complete on node 10.65.191.132

[10.65.191.132]: Verifying NAS Cluster upgrade state for local packages ...

2. Execute the nascluster show command to verify the upgrade was successful.

Example output:

> nascluster show

NAS Cluster IP: 10.40.195.136/em2, Master: Yes, SNFS Root: /stornext/laguna_FS01, Joined: Yes

ID: 0

Cluster Hostname:

DNS Enabled:

No Load balancing: Proxy-Disabled

NFS-HA: Disabled

Master IP: 10.40.195.136

laguna-a.test.com

VIP: 10.40.195.165 (active, node:master) lagun-vip.test.com Nodes: 2

1: 10.40.195.137 (Joined, MDC) laguna-b.test.com

2: 10.40.195.136 (Joined, MDC) laguna-a.test.com

3. Execute the system status all command. The green highlighted text which shows the Appliance Controller is currently operational after the upgrade.

Example output:

> system status all

snnas_controller: running

sssd: running

ctdb: running

smbd: running

winbind: running

nfs: running

haproxy: disabled

keepalived: running

snmpd: disabled

4. Execute the system show version command. See the green highlighted text below which shows the system is running Appliance Controller 3.1.0 after the upgrade.

Example output:

(xxxxx indicates the build number of that software version)

> system show version

Quantum BHM Appliance Controller 3.1.0-xxxxx, Platform 7.0.x.OS7-xxxxx, OS 7.x.xxxx

Upgrade a server that is not part of a NAS cluster and CAN access the online upgrade repository (has an active internet connection)

This procedure upgrades a single node over an internet connection.

Caution: Before you continue with an upgrade, see Prerequisites.

Note: For online upgrades ,you must have internet access; if a firewall is in place, you must configure your firewall to allow access to quantum.com.

1. Execute the system upgrade command, and enter yes to confirm:

Example output:

> system upgrade

The following Packages will be upgraded:

------------------------------------------------------------

<packages_available_for_upgrade>

------------------------------------------------------------

*** During system upgrade, filesystem access will be interrupted. Continue (yes/No)? yes

Working... this may take some time...

 

Verifying NAS Cluster upgrade state for local packages ...

Sending nascluster_upgrade_check to node 10.65.191.32

Waiting for nascluster_upgrade_check to complete on node 10.65.191.132

[10.65.191.132]: Verifying NAS Cluster upgrade state for local packages ...

2. Execute the system status all command. The green highlighted text which shows the Appliance Controller is currently operational after the upgrade.

Example output:

> system status all

snnas_controller: running

sssd: running

ctdb: disabled

smbd: running

winbind: running

nfs: running

haproxy: disabled

keepalived: disabled

snmpd: disabled

3. Execute the system show version command. See the green highlighted text below which shows the system is running Appliance Controller 3.1.0 after the upgrade.

Example output:

(xxxxx indicates the build number of that software version)

> system show version

Quantum BHM Appliance Controller 3.1.0-xxxxx, Platform 7.0.x.OS7-xxxxx, OS 7.x.xxxx

If the appliance is not part of a NAS cluster that CAN NOT upgrade online (does not have an active internet connection)

This procedure upgrades a single node offline with upgrade files located in the /var/upgrade directory.

Caution: Before you continue with an upgrade, see Prerequisites.

1. When the upgrade file has been moved to /var/upgrade, execute the system upgrade local command, and enter yes to confirm:

> system upgrade local

The following Packages will be upgraded:

------------------------------------------------------------

<packages_available_for_upgrade>

------------------------------------------------------------

*** During system upgrade, filesystem access will be interrupted. Continue (yes/No)? yes

Working... this may take some time...

 

Verifying NAS Cluster upgrade state for local packages ...

Sending nascluster_upgrade_check to node 10.65.191.32

Waiting for nascluster_upgrade_check to complete on node 10.65.191.132

[10.65.191.132]: Verifying NAS Cluster upgrade state for local packages ...

2. Execute the system status all command. The green highlighted text which shows the Appliance Controller is currently operational after the upgrade.

Example output:

> system status all

snnas_controller: running

sssd: running

ctdb: disabled

smbd: running

winbind: running

nfs: running

haproxy: disabled

keepalived: disabled

snmpd: disabled

3. Execute the system show version command. In the example output below, the green highlighted text below which shows the system is running Appliance Controller 3.0.1 after the upgrade.

Example output:

(xxxxx indicates the build number of that software version)

> system show version

Quantum BHM Appliance Controller 3.1.0-xxxxx, Platform 7.0.x.OS7-xxxxx, OS 7.x.xxxx

Note: If you have other nodes that are running Appliance Controller and need to be upgraded at this time, run the appropriate upgrade process for all additional server nodes.

Run an iscsiadm Command to Initiate the Upgrade to iSCSI v3

After you upgrade to Appliance Controller 3.1.0, on each node run the iscsiadm command below to upgrade to iSCSI v3.

1. Log in to the Appliance Controller CLI.

2. Enter:

   iscsiadm show status

   The output of the command displays the converted iSCSI configuration to version 3; with no subnet_a/subnet_b names, but instead a list of subnets and subnet interfaces having virtual names iscsia and iscsib, and the target portals accessible and logged into, as in the example below:

   

   

Re-apply modifications to Appliance Controller files

Note: If you have made modifications to any Appliance Controller files, you will have to re-apply those modifications again after you upgrade.

SMB Share Changes from Appliance Controller Version Prior to 2.x

Permission changes for SMB shares are different from what was supported in Appliance Controller versions prior to 2.x. Review After upgrading to Appliance Controller 2.x, why am I getting access-denied errors from an SMB share after creating or adding shares?, so that you are aware of the changes, and how to address them.

NAS Cluster Rejoins

After an upgrade, background processes may continue to run, in turn delaying nodes in rejoining the NAS cluster. After all upgrade background processes complete, the nodes will be rejoined to the NAS cluster.

NFS Failover

The updated NFS failover functionality first introduced in Appliance Controller 2.0 requires that each NFS share has a unique StorNext File System ID (fsid) value. Earlier versions of the Appliance Controller and StorNext NAS did not enforce fsid values being assigned to NFS shares. If you are upgrading to Appliance Controller 2.x from earlier versions, you will have NFS shares that do not have an fsid value or NFS shares that have colliding fsid values after the upgrade.

To repair these NFS shares without fsid values or with colliding fsid values, you must disable and then re-enable NFS failover using the nascluster set nfs-ha (yes | no) [force] command. For instructions to disable and re-enable NFS failover for both NFSv3 and NFSv4, see 3. Enable NFSv4 Failover.