StorNext Gateway Appliances: Upgrade StorNext Software/System Firmware

1. Log in to the server node:
1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.
Service Port IP addresses:

• Node 1 : 10.17.21.1 (dual-server node systems)
• Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

2. Initiate an ssh session to the system using Terminal or PuTTY:
To ssh into the system
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.

2. Open the Service Menu:

   1. Launch the Service Menu. Enter:

   sh /opt/DXi/scripts/service.sh -admin

   The Service Menu displays.

3. Navigate to Hardware Configuration > Setup IPMI > Reboot IPMI.

4. At the prompt to reboot the IPMI controller, press y (yes).

5. The iDRAC/IPMI will reboot.

For single-server node systems, the procedure is complete.

6. For dual-server node systems, reboot the iDRAC on the other server node using the steps you just completed on this server node.

System firmware updates for the BIOS, iDRAC, and peripheral cards are upgraded as part of the system updates. The system applies updates to these if needed on the next server boot. Applying the firmware updates may require two or three extra reboots depending on the firmware versions that are currently installed. The firmware updates can take up to 30-40 minutes to apply, plus the time it takes to reboot the system.

Deferring these updates will still apply the StorNext software update, but will take less time since it skips the firmware updates. You can still apply the firmware updates at a later time.

Contact Quantum Support for help setting up firmware deferrals. Reference Defer Appliance Firmware Updates (access requires CSWeb login).

Note: Always upgrade the Appliance Controller software before you upgrade StorNext, especially for StorNext NAS-clustered systems. See How to Upgrade on the Appliance Controller Documentation Center.

Caution: A system running StorNext 6.0.6 or later with a clustered NAS environment should not run NAS/Appliance Controller 1.3.0 or earlier. Running these configurations may produce unpredictable results.

To find the current Release Notes for your system, locate your system type on the Identify My StorNext Appliance, and Access Training and Documentation page and expand that section. You will find links to the Release Notes for your specific appliance.

Before beginning an upgrade, do the following:

1. * Check that the date and time (NTP) on both server nodes to make sure the time is synced.

Note: If you run the validation process before you click Activate, you have a greater assurance that the system is in a proper state for a successful upgrade. If desired, upload the .fw (firmware) files and validate them prior to a planned maintenance window for the system's upgrade. You can upload and validate files at any time before you click Activate.

Pre-Upgrade checks for upgrades on systems running StorNext 6.2.0 and later

Once a system is upgraded to StorNext 6.2.0 or later, the Validate button on the StorNext GUI Firmware Upgrade page performs a much more extensive upgrade validation check than in previous releases. The complete set of pre-upgrade checks that used to run only when you clicked Activate, are now run. These checks include a checksum and version verification against the upgrade files, and also include a complete check of RPM dependencies as well as potential conflicts on the system which could cause an upgrade to fail. There are also more extensive version checks for StorNext and other packages.

Beginning with StorNext 7.2.0, the validation process also checks for RPM files that cannot be upgraded. Upon validation failure, an Admin Alert containing a list of RPMs found that are not expected on the node(s), is generated. You must manually remove these RPMs from the node(s) before you activate the upgrade.


Pre-Upgrade checks for upgrades on systems running StorNext versions earlier than 6.2.0

If you click the "Validate" button on the StorNext GUI Firmware Upgrade page, this will verify the uploaded .fw files against a checksum for those files. The validate also performs some basic version checking to make sure the uploaded files are valid for the running system.

Errors reported from the validation check are reported back to the user in a context sensitive pop-up window explaining what failed in the validation check as well as an Admin Alert is generated with similar detailed information about the failure.

2. Collect a DSET and StorNext snapshot from both servers (for dual-node [HA] systems only) before starting the upgrade.
3. Check the /etc/hosts files to verify that no manual modifications have been made, and that the entries are correct. If there are, make a backup of those files to refer to after the upgrade is complete.

* For appliances except Xcellis Workflow Extender and G300 systems.

StorNext compatibility

Not all StorNext releases upgrade directly to another StorNext release. As a result, an upgrade to the current version of StorNext may require multiple, incremental upgrades, depending on the version of StorNext currently installed. Consider the following:

• For information about supported upgrade paths for StorNext 7.x, consult the StorNext 7 Compatibility Guide in the Compatibility Guides section of the PDFs page of the StorNext 7 Documentation Center. If your system is running an earlier StorNext release, consult an earlier version of the StorNext Compatibility Guide that applies to the release your system is running.
• For information about supported upgrade paths and dependencies for StorNext 6.x, consult the StorNext 6 Compatibility Guide in the Compatibility Guides section of the PDFs page of the StorNext 6 Documentation Center. If your system is running an earlier StorNext release, consult an earlier version of the StorNext Compatibility Guide that applies to the release your system is running.
• For information about supported upgrade paths and dependencies for StorNext 5.x, consult the StorNext 5 Compatibility Guide in the Compatibility Guides section of the StorNext 5 Documentation Center. If your system is running an earlier StorNext release, consult an earlier version of the StorNext Compatibility Guide that applies to the release your system is running.
• If your system is running a StorNext release prior to the supported upgrade releases for a given StorNext release, consult an earlier version of the StorNext Compatibility Guide that applies to your specific upgrade.

StorNext appliance (MDC) vs. client dependencies

Within your StorNext network/cluster, StorNext appliances operating as StorNext MDCs (or customer-supplied MDCs) must be running the same StorNext release or higher than StorNext clients. In other words, StorNext clients cannot be running a later StorNext release than a StorNext MDC in the network/cluster.

Note: The following appliances operate asStorNext MDCs: Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, Artico, Pro Foundation, M660, and M440 systems. The following appliances DO NOT operate as StorNext MDCs, but as StorNext clients only: Xcellis Workflow Extender, aiWARE for Xcellis Standard and High Performance, and G300 systems

Note: The following StorNext releases are supported on the system. These tables represent only which StorNext releases are supported on the system, but not compatibility. See also StorNext compatibilityand StorNext appliance (MDC) vs. client dependencies.

Supported StorNext 7 releases

StorNext 7 Releases
System	Release
	7.0.1	7.0.2	7.0.3	7.1
Xcellis Workflow Director (Gen 2)	✓	✓	✓	✓
Xcellis Workflow Director (Gen2/R630)	✓	✓	✓	✓
Xcellis Workflow Extender (Gen 2)	✓	✓	✓	✓
Xcellis Workflow Extender (Gen2/R630)	✓	✓	✓	✓
Xcellis Foundation	✓	✓	✓	✓
Artico (R630)	✓	✓	✓	✓

Supported StorNext 6 releases

StorNext 6 Releases
	Release
System	6.0b	6.0.1b	6.0.1.1a, b	6.0.5b	6.0.5.1b	6.0.6b	6.0.6.1b	6.1.0c	6.1.1c	6.2.0 , 6.2.1, 6.3.0 and 6.3.1d	6.3.1.1d	6.4
Xcellis Workflow Director (Gen 2)	X	X	X	X	X	X	X	✓	✓	X	✓	✓
Xcellis Workflow Extender (Gen 2)	X	X	X	X	X	X	X	✓	✓	X	✓	✓
Xcellis Workflow Director (R630)	✓	✓	✓	✓	✓	✓	✓	✓	✓	X	✓	✓
Xcellis Workflow Extender (R630)	✓	✓	✓	✓	✓	✓	✓	✓	✓	X	✓	✓
Xcellis Workflow Extender (R520)	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
XcellisFoundation	X	X	✓	✓	✓	✓	✓	✓	✓	X	✓	✓
aiWARE for Xcellis	X	✓	✓	✓	✓	✓	✓	✓	✓	X	✓	✓
Artico (R630)	✓	✓	✓	✓	✓	✓	✓	✓	✓	X	✓	✓
Artico (R520)	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
Pro Foundation	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
StorNext M440	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
StorNext M660	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
StorNext G300	✓	✓	X	✓	✓	✓	✓	✓	✓	X	✓	✓
a* The StorNext 6.0.1.1 release only applied to R630 server models (which run on CentOS7), and not R520 server models (which run on CentOS6).
bStorNext 6.0.6.1 replaced previous 6.x StorNext releases, and firmware upgrade files will only be provided for StorNext 6.0.6.1 or later.
cStorNext 6.1.1 replaces StorNext 6.1.0, and includes all fixes issues and enhancements completed for StorNext 6.1.0, including the Spectre and Meltdown vulnerabilities addressed in that release. StorNext 6.1.0 firmware upgrade files are no longer available.
dStorNext 6.3.1.1 supersedes and replaces 6.2.0, 6.2.1, 6.3.0, and 6.3.1, and includes all fixes issues and enhancements completed for those releases. Firmware upgrade files for these releases are no longer available.

About specific StorNext 6.x upgrades:

• 6.0.5 or later – Upgrade the system firmware to StorNext 5.3.0 or later prior to upgrading to 6.0.5 or later.

• 6.0.1.1 – upgrade the system firmware to StorNext 6.0.1 prior to upgrading to 6.0.1.1.

Note: Firmware files are large - over 12 GB (or larger) for releases where both files are required (typical), so plan time to download the file(s) required for the upgrade. The /scratch file system requires at least 20 GB of free space available before you perform the upgrade.

Firmware request pre-requisites

In order to receive a firmware file, you will need one of the following:

• The System Serial Number
About the System Serial Number and how to locate it

System serial numbers and StorNext software serial numbers are alphanumeric. The table below provides examples of serial numbers.

Type of Serial Number	Example(s) of Serial Number(s)
System Serial Number	AV1607CKH12345 CX1306CKB12345 EW1450CKD12345
StorNext Software Serial Number	SN12345

• The StorNext Serial Number.
About the StorNext Serial Number and how to locate it

You can find the StorNext Serial Number in the license.dat file. The license.dat file can be found on the server node at /usr/cvfs/config/license.dat. Open the license.dat file and locate the Serial Number.

Example:

# Serial Number: Q8675309

• The cvfsid string.

Example:

ECF4BCEECC0E linux 0 xcellis13

How to Generate a cvfsid String
Open an SSH connection to the server
Using the IP address assigned to the server on the StorNext management/public 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.
Generate the cvfsid
1. Enter the cvfsid command.

The system returns the following information:

<server_MAC_address> <server_OS> <server_name>

Example:

ECF4BCDECC0E linux 0 xcellis13

2. Close the SSH session for the node. Repeat for the other node.

Firmware request

If you need firmware upgrade files to upgrade your system:

1. Fill out the following form, here:

StorNext 7 Upgrade

The form looks like:



(click to enlarge)

2. Click the box to agree and confirm that you have read and accepted the EULA, Privacy Policy and Terms of Use.
3. Click Submit.
4. After Quantum receives your information, you will receive an email from "Quantum Software Downloads" to the email address you entered on the form linked above.

The email will look similar to:



(click to enlarge)

5. Click the "here" link in the email to access the "mySoftware" page containing the Appliance Upgrade file(s) available for your system.

The page will look similar to:



(click to enlarge)

6. Click the Download button next to the firmware file(s) for the version of StorNext you wish to update to.

Note: Most StorNext versions include both a "(1 of 2)" and a "(2 of 2)" file. Download both files.

Where to put the files once downloaded

• If you will be directly connecting to the system, move the files to a USB thumb drive or DVDs for use by the firmware upgrade process for the upgrade using the Service Menu.
• If you will be remotely connecting to the system, you don't need to move the file(s) from the temporary location where you have placed them. You will manually transfer the files to the required directory.

There are two types of upgrades that are currently supported:

1. A full appliance upgrade (includes StorNext software, CentOS updates, and any additional firmware upgrades for server hardware). There are two ways to perform this type of upgrade:
Method 1: Upgrade the system while connected to the Service Port

Use this procedure when connecting directly to the Service Port on the back of the system, and using a USB thumb drive or DVD containing the firmware upgrade file(s) and upgrading the system from the Service Menu.

Prerequisites

• The required firmware file(s) have been downloaded for the StorNext release needed and have been moved to a USB thumb drive or DVD.
• You have the login credentials to access the system.

Connect to the system Service Port

Note: You don't need to connect to the Service Port if you will be accessing the system over an ethernet network. For connections over your network, connect to the system using an SSH client like PuTTY using the IP address for the server node over your normal network connection.

Each server node contains an integrated 1GbE Ethernet port that is used for initial system installations, but is also dedicated to Service access once the system is installed.

If you desire to directly connect to the system, connect an Ethernet cable from the Ethernet port of a service laptop to the Service Port on the rear of the Server Node you wish to access as shown below. Do this prior to accessing the command line.

Service Port - Gen 2 Systems



Service Port - R630 Systems



Figure 1: Service Port – R520 Systems (The appliance model and/or options shown below may differ from your system. No matter which model you are connecting to, the service port is located as shown here.)



Launch the Command Line

1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.
Service Port IP addresses:

• Node 1 : 10.17.21.1 (dual-server node systems)
• Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

2. Initiate an ssh session to the system using Terminal or PuTTY:
To ssh into the system
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.

Upgrade the system from USB/DVD media

1. Launch the Service Menu. Enter:

sh /opt/DXi/scripts/service.sh -admin

The Service Menu displays.

2. Insert the USB thumb drive or DVD containing the .fw file(s) into an available USB port or the DVD-ROM drive of the system.
3. From the Service Menu, select More Tools.
4. Select Upgrade Platform Software.
5. Select Upgrade from local media.
6. Select the option to choose files located on the DVD or USB drive.
7. When the Available platform upgrade files found menu displays, select the first file, containing the “1of2.fw” suffix in the file name. For single-file firmware upgrades, just select the file with the "1of1.fw" suffix in the filename.
8. When the Available platform upgrade files found menu displays again, enter “q” to quit the menu.
9. Press <ENTER> when prompted to continue.

For double firmware upgrade files only, do the following. For single-file firmware upgrades, continue to step 13.

10. Select Upgrade from local media a second time.
11. Select the option to choose files located on the DVD or USB drive.
12. When the Available platform upgrade files found menu displays, select the second file, containing the “2of2.fw” suffix in the file name.
13. When the Available platform upgrade files found menu displays again, enter “q” to quit the menu.
14. Press <ENTER> when prompted to continue.
15. Select Activate upgrade image.
16. The upgrade will begin, and will reboot the system, if needed.

Note: A reboot could take 15 minutes or more, so plan upgrade times accordingly. If the system does reboot, your SSH connection could timeout during the reboot, and you will have to wait for the upgrade to complete before connecting to the system via SSH again.

17. Shut down the SSH terminal.
18. Disconnect the network cable from the system.

The procedure is complete.

Method 2: Upgrade the system over a network connection

Use this procedure to move new firmware upgrade file(s) to the gateway system when connecting to the system remotely.

Prerequisites

• If there are manual entries in the /etc/fstab file (such as NAS mount points), copy the file before upgrading to 5.3. Restore the file after the upgrade, and then restart the StorNext services to restore mount points. See Bug 60482 in the Known Issues section of the Release Notes for your system.

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.

Transfer the upgrade files to the system

Before files can be applied to the system, they must first be transferred to correct location on the system. This is a 2-step process for remote connections to the system. The files must first be moved to a directory accessible via an SCP connection on the StorNext public network. Then, after logging in as the rootsh user, the files can be moved to the correct directory. The following is the first step in the procedure, to move the files to the interim location on the server.

Note: If you have a copy of WinSCP, or a similar Windows SCP client, you can copy files to the /scratch/tmp directory on the system using the options available in your client.

Note: The following procedure shows how to do this when PuTTY SCP is installed.

1. Open a command prompt (from 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 type or file to move> stornext@<host server>:/scratch/tmp

Example (This example shows moving all files from local directory. A specific file type or a specific file name could also be used.):

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

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

Example:

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

The file is transfer is complete.

Move firmware files to the upgrade directory

1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.
Service Port IP addresses:

• Node 1 : 10.17.21.1 (dual-server node systems)
• Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

2. Initiate an ssh session to the system using Terminal or PuTTY:
To ssh into the system
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.

3. Copy the .fw file(s) to the correct directory on the server:
cp /scratch/tmp/*.fw /scratch/upgrade
Or move the file(s):
mv /scratch/tmp/*.fw /scratch/upgrade

Upgrade StorNext/Firmware

1. Launch the Service Menu. Enter:

sh /opt/DXi/scripts/service.sh

The Service Menu displays.

1. From the Service Menu, select More Tools.
2. Select Upgrade Platform Software.
3. Select Activate upgrade image.
4. Select a firmware file (either one for 2-file firmware upgrades) and click Enter to begin the upgrade.

   The upgrade will begin, and will reboot the system, if needed.

Note: A reboot could take 15 minutes or more, so plan upgrade times accordingly. If the system does reboot, your SSH connection could timeout during the reboot, and you will have to wait for the upgrade to complete before connecting to the system via SSH again.

5. Shut down the SSH terminal.

   The procedure is complete.

2. A StorNext software-only upgrade, which uses StorNext software files from a host appliance (which only upgrades the system to the StorNext software release included in the firmware upgrade). There is only one way to perform this type of upgrade:
Upgrade the StorNext software from another appliance (MDC)

Use this procedure when you wish to upgrade the system from the Service Menu and using a .bin file from another , rather than downloading the system's upgrade files from Quantum.

Prerequisites:

Before using this procedure, make sure that connected clients do not have the system's StorNext file system (snfs)mounted, as described here:

1. On the command line of the system, run the following command (for Xcellis Workflow Extender [R630] systems):

   systemctl stop cvfs

   OR

   Run the following command (for Xcellis Workflow Director [R520] or G300 systems):

   service cvfs fullstop

2. If you do not see an error message that states “umount processes have failed!”, read the rest of the prerequisites, and continue to Upgrade the system using files from another StorNext system. However, if you see the error message, you can determine which user/system currently has mounted the system's snfs.

Example with error message:

Unmounting SNFS filesystems umount: /stornext/hydroxide01: device is busy.

(In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

[ OK ]

umount processes have failed!

In the example above, note that fuser(1) currently has mounted the server's file system, called /stornext/hydroxide01. fuser(1) must be in a state where the server's file system is not mounted.

Note: If you see the error message, it is most likely because a client system currently has a job being run and should not be interrupted.

Caution: Make sure all I/O job processes complete or are cleanly stopped before proceeding. If clients are stopped during active I/O operations, there is a potential for data loss.

3. Unmount the server's snfs file system on the client system with the mounted snfs. Do one of the following, depending on the client's Operating System:

   • On Linux client systems, execute the following :

   service cvfs fullstop

   • On Windows client systems, open the Windows Start Menu, select All Programs, select StorNext File System, and click Services Stop. Do one of the following:
   • On the client system, if you do not see the error message “umount processes have failed!”, read the rest of the prerequisites, and continue to Upgrade the system using files from another StorNext system.
   • On the client system, if see the error message “umount processes have failed!”, it may have a job currently in process, or there are open files from an interrupted I/O job.

Login to the system launch the Service Menu

To login to the system to access the command line and the Service Menu, do one of the following:

• Perform the steps in the Upgrade G300 Firmware with a Direct Connection section and then continue to Upgrade the system using files from another StorNext system.
• Perform the steps in the Upgrade G300 Firmware Remotely section and then continue to Upgrade the system using files from another StorNext system.

Upgrade the system using files from another StorNext system

To complete the StorNext software-only upgrade from files on an Xcellis Workflow Director, Artico, Pro Foundation or Metadata Appliance in the StorNext cluster:

1. From the Service Menu, select More Tools > Advanced Configuration > Update Gateway Software > Upload from Primary MDC.
2. Select the .bin file for the client file to copy to the system when you see the message:

************************************

*** Available client files found ***

************************************

Example file name (5.2.1 or later):

snfs_client_plus_mover_RedHat60AS_26x86_64.bin

Note: Because the system runs on CentOS, which is a Linux distribution compatible with Red Hat OS, select a .bin file which includes RedHat in the filename.

The file will be copied to /scratch/CLIENTS on the system.

3. Select the .bin file for the agent file to copy to the system when you see the message:

************************************

*** Available agent files found ***

************************************

Example file name (5.2.1 or later):

snfs_gateway-agent_RedHat60AS_26x86_64.bin

Note: Because the system runs on CentOS, which is a Linux distribution compatible with Red Hat OS, select a .bin file which includes RedHat in the filename.

The file will be copied to /scratch/AGENTS on the system, and the Upgrade Gateway Software menu is shown.

4. Select Install Upgrade.
5. Select the client .bin file you previously copied when you see the message:

************************************

*** Available client files found ***

************************************

Example file name:

snfs_client_plus_mover_RedHat60AS_26x86_64.bin

6. Press Enter.

The EULA (End User License Agreement) displays.

7. Choose “y” to accept the EULA. The installation begins.

When the client installation is complete, you will see the message:

8. ************************************

   *** Available agent files found ***

   ************************************

9. Select the agent .bin file you previously copied to install the agent on the system.

Example file name:

snfs_gateway-agent_RedHat60AS_26x86_64.bin

10. Press Enter.

The EULA (End User License Agreement) displays.

11. Choose “y” to accept the EULA. The installation begins.

When the Upgrade Gateway Software menu is displayed, the upgrade is complete.

12. Exit the Service Menu by clicking q and Enter repeatedly until the command line is displayed again.
13. Shut down the SSH terminal.
14. If directly-connected to the system, disconnect your network cable from the system.

The procedure is complete.