H4000 Essential H4000 Quick Start Instructions

Ensure that your ethernet network meets the network requirements for the H4000 Essential. See the following:]

Note: The following links open in a new browser tab.

Refer to the following Site Planning pages:

• Site Planning > Installation Site Prerequisites > Network and switch requirements > General Requirements
• Site Planning > Installation Site Prerequisites > Network and switch requirements > Management network connection requirements
• Site Planning > Installation Site Prerequisites > Network and switch requirements > 100 GbE Connections

• Site Planning > Installation Site Prerequisites > Network and switch requirements > General Requirements
• Site Planning > Installation Site Prerequisites > Network and switch requirements > Management network connection requirements
• Site Planning > Installation Site Prerequisites > Network and switch requirements >100 GbE Connections

1. Click Close.

It may take a couple minutes to enable the network connection.

1. Access the Network Connections dialog:
   • For Windows 10 (method 1), right-click the Start menu icon, click Network Connections and click Change Adapter Options in the right pane of the dialog.
   • For Windows 10 (method 2), open the Cortana search, and enter View network status and tasks, and click Change adapter settings in the left pane of the dialog.
   • From older Windows versions, click the Start menu, search for and open the View Network Connections dialog.
2. Right-click the network connection that corresponds to the Ethernet port on the laptop being used, something like Ethernet or Local Area Connection, and select Properties:



3. From the list of connections, select Internet Protocol Version 4 (TCP/IPv4), and then click Properties to display the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box.

Pro Tip!

Quantum recommends that you record the settings in this dialog box before you change them. You can refer to this information later when you set the settings back to their original values — after you are finished using this network connection



4. Select Use the following IP address and then enter the following information:

5. Click OK.
6. Close the Network dialog.

It may take a couple minutes to enable the network connection.

You can either direct-connect the Eth port labeled as "2" m1p2 port on both controllers to each other, or connect both m1p2 ports to an Ethernet network switch.

Note: If connected to a switch:

Either direct-connect an Ethernet cable from m1p2 (10 GbE port) on Controller A to m1p2 (10 GbE port) on Controller B, or to a 10 GbE network switch that will be configured to access the StorNext metadata network:

Direct-connected m1p2 cabling:

Ethernet switch-connected m1p2 cabling:

If you will not be using the physical m1p2 connection for metadata, do one of the following:

• Direct-connect two Ethernet ports for the same network card to one another

• Connect the same port on both controllers to a switch.

Note: If connected to a switch:

• Use a network switch rated for the speed of your network port connection. If you are using a 10 GbE port, use a 10 GbE switch. Otherwise, the system will not support optimal data throughput.

• Zone two ports on the switch for the network connections to a single netmask used for metadata traffic for this system, to isolate that zone from other data for the system.

The H4000 Essential 100 GbE model comes with two 100 GbE ports on each controller. The recommended (and only supported) configuration for using all ports is to establish a dual-subnet storage network. If a single subnet is used, only one interface should be connected and configured.

Note: Each of the two ports on the 100 GbE card on both controllers use a PCIe gen 3 x16 connection to the host server. This connection limits the aggregate throughput of those two ports to a maximum of 16 GB/sec. A single port (i.e., on a single-subnet configuration) is limited (by 100 Gbps Ethernet) to a maximum of 12.5 GB/sec.

Pro Tip! Use IP addresses that are unique and are NOT currently in use in your environment, or that have been assigned to other components configured within the H-Series UI.

Option 1: Configure an ethernet storage network with DHCP

Pro Tip! If configuring this system with DHCP, make sure the DHCP server has adequate IP addresses for all the network connections needed on this system and other network connections already in use in your environment.

1. If needed, change the network type Disable (DHCP), or Single-subnet(item 1 above).

Note: When the setting is selected for one controller, the setting for the other controller (item 2 above) changes to the same network type.

2. When DHCP is selected, the IP interface values, including IPv4 Address, Netmask, and MTU for Controller A and for Controller B, is auto-filled and can not be configured.

Caution: Quantum recommends leaving the storage configuration unchanged after initial configuration. ONLY change this if absolutely necessary (such as if settings change within your network ecosystem). The system was optimized during initial configuration for your network and storage environment. You could adversely affect efficiency of the H4000 Essential if these settings are changed incorrectly.

3. Click NEXT (item 3 above).

Option 2: Configure an ethernet storage network with a single subnet

If you connected only 1 cable to the 100 GbE card on both controllers when cabling the H4000 Essential, then you will need to configure the system with 1 subnet.

Note: Make sure all network cables have been connected to the H4000 Essential before changing these settings.

Pro Tip! Use IP addresses that are unique and are NOT currently in use in your environment, or that have been assigned to other components configured within the H-Series UI.

1. Click CONFIGURATION in the topnav (item 1 above).
2. In the left nav, click Storage Network (item 2 above).
3. If needed, change the network type to Single-subnet(item 3 above).

Note: When the setting is selected for one controller, the setting for the other controller (item 7 above) changes to the same network type.

4. Make changes necessary to the IP interface information: IPv4 Address, Netmask, and MTU for Controller A (items 4-6 above) and for Controller B (items 8-10 above), for single-subnet configurations. All fields marked "Required" must be set before the Apply button is enabled (blue).

Caution: Quantum recommends leaving the storage configuration unchanged after initial configuration. ONLY change this if absolutely necessary (such as if settings change within your network ecosystem). The system was optimized during initial configuration for your network and storage environment. You could adversely affect efficiency of the H4000 Essential if these settings are changed incorrectly.

5. Click Apply (item 11 above).

Option 3: Configure an ethernet storage network with dual subnets

If you connected 2 cables to the 100 GbE card on each controller when cabling the H4000 Essential, you will need to configure the system with dual subnets.

Note: Dual-subnet configuration requires 2 network port connections for each controller, each with its own unique IP address. Make sure all network cables have been connected to the H4000 Essential before changing these settings.

Pro Tip! Use IP addresses that are unique and are NOT currently in use in your environment, or that have been assigned to other components configured within the H-Series UI.

1. Click CONFIGURATION in the topnav (item 1 above).
2. In the left nav, click Storage Network (item 2 above).
3. If needed, change the network type to Dual-Subnet (item 3 above).

Note: When the setting is selected for one controller, the setting for the other controller (item 10 above) changes to the same network type.

4. Make changes necessary to the IP interface information: IPv4 address, Netmask, and MTU for Controller A (items 4-9) and for Controller B (items 11-16 above). All fields marked "Required" must be set before the APPLY button is enabled (blue).

Caution: Quantum recommends leaving the storage configuration unchanged after initial configuration. ONLY change this if absolutely necessary (such as if settings change within your network ecosystem). The system was optimized during initial configuration for your network and storage environment. You could adversely affect efficiency of the H4000 Essential if these settings are changed incorrectly.

5. Click APPLY (item 17 above).

Both StorNext VMs WILL reboot after you click Apply on NETWORK and DATE & TIME pages!

Because a change to either the NETWORK tab or the DATE & TIME tab will reboot both StorNext VMs, try to complete the settings for BOTH the NETWORK and DATE & TIME tabs before you click APPLY, so a reboot is only required once.

Note: StorNext VM reboots can take up to 15 minutes to complete, so be patient during the reboot. StorNext settings are applied during the StorNext VM reboot, and the StorNext services are running.

Note: Large changes to settings on these screens may also require you to log out of the H-Series UI and log back in after the StorNext VMs reboot, before the changes are displayed.

StorNext System > STORNEXT NETWORK > StorNext Network Settings

(Previously called "StorNext General Settings")

Pro Tip! Use IP addresses that are unique and are NOT currently in use in your environment, or that have been assigned to other components configured within the H-Series UI.

Note: Even if values have been pre-populated on this page (these are pre-applied to the system for new manufactured systems), you will still need to enter the unique values for your system.

1. In the top nav select CONFIGURATION (item 1 above). This opens the StorNext System page (item 2 above) and the NETWORK tab (item 3 above).
2. Enter the Controller A StorNext Hostname for its StorNext VM (item 4a above). You can also use the small "auto-generate hostname/car" button (item 4b above) to have the system automatically create a unique hostname for you.

Note: If you manually enter a hostname in this field, or used the "auto-generate hostname/car" button previously, the button is no longer available and you can no longer auto-generate a new hostname.

3. Enter the Controller B StorNext Hostname for its StorNext VM (item 5a above). The first time you configure the StorNext settings, you can also use the small "autogenerate hostname/car" button (item 5b above) to have the system automatically create a unique hostname for you.

Note: If you manually enter a hostname in this field, or used the "auto-generate hostname/car" button previously, the button is no longer available and you can no longer auto-generate a new hostname.

4. Enter the DNS Domain name for the management connection for the StorNext VMs (optional; item 6 above).
5. Enter the Default IP Gateway IP for the management connection for the StorNext VMs (item 7 above).
6. Enter the Primary DNS Server IP for the management connection for the StorNext VMs (item 8 above).
7. Enter the Alternate DNS Server IP (if used) for a second management DNS for the StorNext VMs (optional; item 9 above).
8. Enter the Alternate DNS Server IP (if used) for a third management DNS for the StorNext VMs (optional; item 10 above).

StorNext System > STORNEXT NETWORK > StorNext Interface Configuration

(previously called "Configuration")

Skip StorNext Routing Configuration

You have now finished configuring the required information on the StorNext System > NETWORK tab. Continue to configure items on the DATE & TIME tab, and set time zone to UTC (required). You do not need to enter any information in the StorNext Routing Configuration of this tab, so skip this section:

Note: If you need to re-enter multiple entries, click RESET to get back to the default configuration settings. However, even if you are done with these settings, DO NOT click APPLY at this time. Wait until you have completed configuring settings on the DATE & TIME tab.

Before you click APPLY, see Pro Tips: StorNext System Configuration. After you click APPLY, be patient StorNext VMs will reboot and will take a while to come back fully online before the system is again available for use or additional configuration.

StorNext System > STORNEXT NETWORK > StorNext Interface Status

At any time, during configuration or after, you can use this option to review the settings assigned to the network interfaces used for the StorNext network. The following are shown in this section of the page and shown in the example image below:

Interface name (item 1), maximum interface speed (item 2), current operating speed of the interface on Controller A (item 3), if the interface IP is currently UP or DOWN on Controller A (item 4), if the interface link is currently UP or DOWN on Controller A (item 5), on Controller B (item 6), if the interface IP is currently UP or DOWN on Controller B (item 7), and if the interface link is currently UP or DOWN on Controller B (item 8).

1. From the StorNext System > NETWORK tab, click the DATE & TIME tab (item 1 above).
2. Click Network Time Protocol (NTP) Server (Recomended) (item 2above).
3. Select one of the NTP time server Selection Modes to use (item 3 above).
4. Enter an address for the NTP Timeserver Pool (item 4 above).
5. Click the System Timezone drop-down and enter UTC for the System Timezone(required for CatDV; item 5 above).

Note: This time and date should be set to those used for the H4000 Essential Time setting (found on the Time page; select CONFIGURATION > Time) for accurate timestamps across the different system interfaces and data.

Note: Before you click APPLY, and to determine when StorNext will once again available, review the following about applying StorNext configuration settings.

Pro Tips: Be patient during StorNext Configuration Changes

Pro Tip #1! Expect a delay after you click APPLY - reboot required for both StorNext VMs

Because a change to either the NETWORK tab or the DATE & TIME tab will reboot both StorNext VMs, try to complete the settings for BOTH the NETWORK and DATE & TIME tabs before you click APPLY, so a reboot is only required once.

Note: StorNext VM reboots can take up to 15 minutes to complete, so be patient during the reboot. StorNext settings are applied during the StorNext VM reboot, and the StorNext services are running.

Note: Large changes to settings on these screens may also require you to log out of the H-Series UI and log back in after the StorNext VMs reboot, before the changes are displayed.

Pro Tip #2! Verify StorNext VMs are fully functional after they reboot

In the top navigation, click CLUSTER and verify the status of the StorNext links on in the top navigation of the StorNext VMs as follows:

Determine the operating state of both StorNext VMs

With H-Series UI 1.6.0 or later, you can now quickly determine if the StorNext VM is operating as primary and secondary:

Note: If server icons are orange or red, or if both are green but they are both "secondary", wait until they are both green and on has become "primary" before performing additional configuration tasks.

Make sure both StorNext VMs are green, in the "Running" condition, and one is "primary" and one is "secondary".

StorNext VM "primary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon with the plus "+" sign, you will see a popup indicating that this StorNext VM is "primary".



StorNext VM "secondary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon without a plus "+" sign, you will see a popup indicating that this StorNext VM is "secondary".



6. Click APPLY (item 6 above) to apply the new settings.

Note: Apply the settings and wait for StorNext to complete applying the configuration (see ) before attempting to test NTP configuration. NTP first has to be applied to the system before it can be tested. The TEST NTP button (item 7 above) will only be functional after the StorNext VMs have rebooted and StorNext is again fully functional.

1. From the StorNext System > NETWORK tab, click the DATE & TIME tab (item 1 above).
2. Select Manual Date & Time Settings (item 2 above).
3. Enter a New System Date for the StorNext VM (item 3 above).
4. Enter a New System Time for the StorNext VM time (item 4 above).
5. Click the System Timezone drop-down and enter UTC (required for CatDV; item 5 above).

Note: These time and date settings should be set to those used for the H4000 Essential Time setting (found on the Time page; select CONFIGURATION > Time) for accurate timestamps across the different system interfaces and data.

Note: Before you click APPLY, and to determine when StorNext will once again available, review the following about applying StorNext configuration settings:

Pro Tips: Be patient during StorNext Configuration Changes

Pro Tip #1! Expect a delay after you click APPLY - reboot required for both StorNext VMs

Because a change to either the NETWORK tab or the DATE & TIME tab will reboot both StorNext VMs, try to complete the settings for BOTH the NETWORK and DATE & TIME tabs before you click APPLY, so a reboot is only required once.

Note: StorNext VM reboots can take up to 15 minutes to complete, so be patient during the reboot. StorNext settings are applied during the StorNext VM reboot, and the StorNext services are running.

Note: Large changes to settings on these screens may also require you to log out of the H-Series UI and log back in after the StorNext VMs reboot, before the changes are displayed.

Pro Tip #2! Verify StorNext VMs are fully functional after they reboot

In the top navigation, click CLUSTER and verify the status of the StorNext links on in the top navigation of the StorNext VMs as follows:

Determine the operating state of both StorNext VMs

With H-Series UI 1.6.0 or later, you can now quickly determine if the StorNext VM is operating as primary and secondary:

Note: If server icons are orange or red, or if both are green but they are both "secondary", wait until they are both green and on has become "primary" before performing additional configuration tasks.

Make sure both StorNext VMs are green, in the "Running" condition, and one is "primary" and one is "secondary".

StorNext VM "primary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon with the plus "+" sign, you will see a popup indicating that this StorNext VM is "primary".



StorNext VM "secondary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon without a plus "+" sign, you will see a popup indicating that this StorNext VM is "secondary".



6. Click APPLY (item 6 above).

Determine the operating state of both StorNext VMs

With H-Series UI 1.6.0 or later, you can now quickly determine if the StorNext VM is operating as primary and secondary:

Note: If server icons are orange or red, or if both are green but they are both "secondary", wait until they are both green and on has become "primary" before performing additional configuration tasks.

Make sure both StorNext VMs are green, in the "Running" condition, and one is "primary" and one is "secondary".

StorNext VM "primary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon with the plus "+" sign, you will see a popup indicating that this StorNext VM is "primary".

StorNext VM "secondary state" icon:

Notice that StorNext is "Running" (green), and if you move your mouse cursor and hover over the icon without a plus "+" sign, you will see a popup indicating that this StorNext VM is "secondary".

1. Select Configuration in the top navigation menu (item 1 above).
2. Select Time in the left navigation menu (item 2 above).
3. Click the Enable Network Time Protocol (NTP) slider to enable NTP (item 3 above). The slider will move to the right and turn blue (enabled).
4. Select either to use an NTP Hostname, or IP Address (item 4 above).
5. Enter the NTP Hostname or IP address to use in the NTP Server field (item 5 above).

Another example:

time.nist.gov

6. Click the Timezone drop-down and enter UTC (required for CatDV; item 6 above).
7. Click Apply to confirm the change (item 7 above).

1. Select Configuration in the top navigation menu (item 1 above).
2. Select Time in the left navigation menu (item 2 above).
3. If NTP is enabled, click the Enable Network Time Protocol (NTP) slider to disable NTP (item 3 above). The slider will move to the left and turn gray (disabled).
4. Enter the Date from the calender widget (item 4 above).
5. Manually enter the Time in hh:mm:ss format in the Time field (item 5 above).
6. Click the Timezone drop-down and enter UTC (required for CatDV; item 6 above).
7. Click Apply to confirm the change (item 7 above).

1. Stop and restart the CatDV VM:
1. From the H-Series UI, scroll down to the CatDV VM section of the page.
2. Click the Stop/Start CatDV VM icon in the Controller A panel:

3. Click Stop CatDV.
4. Click STOP to confirm stopping the CatDV VM. A task to stop the CatDV VM will display and the CatDV VM will stop.
5. Verify the CatDV VM is fully stopped. It should look like this:

6. When the CatDV VM is in a "stopped" state, click the Stop/Start CatDV VM icon:

7. Click Start CatDV.
8. Click START to confirm starting the CatDV VM. A task to start the CatDV VM will display and the CatDV VM will start.
9. Verify the CatDV is in a "Running" state once again. Make sure both items under CatDV are "Running":

2. Change the H4000 Essential system password:
1. Click the Profile/Logout button:

2. Click Change Password:

3. Enter the existing password, enter a new password, and enter the new password a second time to confirm.
4. Click Apply.

Since you have now changed the password for the H4000 Essential, make sure you update the H4000 Essential Pre-Install Network Worksheet for your system, so the correct password is included there. Ensure you retain a paper or online version of the H4000 Essential Pre-Install Network Worksheet per your company's data security/retention requirements.

At this point the workaround is complete. Log in to the CatDV UI.

Note: Examples below for Mojave (OSX). The instructions for other MacOS versions may differ.

1. From the MacOS desktop, click Go > Connect to Server (or Command + K)



(click image to enlarge)

2. Enter the CatDV NAS VIP (IPv4) address in the first file of the Connect to Server dialog and click Connect:
smb://<NAS VIP address>

Example:

smb://10.20.223.215



(click image to enlarge)

The system will begin to connect to the share:



3. Connect to the server using one of the CatDV user accounts you created in CatDV. Enter the user Name, Password, click the checkbox next to "Remember this password..." (optional), and click Connect:



A window will open to the NAS share similar to this:



(click image to enlarge)

Also, a new StorNext icon for the NAS share used in CatDV will be added to your desktop:

Note: Example below for Windows 10. The instructions for other Windows versions may differ.

1. From the Windows desktop, open File Explorer (click the Windows key + E on your keyboard).
2. In the left File Explorer pane, right-click on This PC.
3. Click Map Network Drive from the menu.



(click image to enlarge)

4. Select the drive letter on your Windows system that you would like to assign to the CatDV share:



(click image to enlarge)

5. Add the NAS VIP (IPv4) address or nameserver (DNS required) in the Folder box:



(click image to enlarge)

Make sure the checkboxes next to Reconnect at sign-in, and Connect using different credentials are selected:



(click image to enlarge)

6. Click Browse:



(click image to enlarge)

7. Click on the NAS VIP and click OK:



8. Enter the user name for a user you added to CatDV:



9. Enter the password for the CatDV user:



10. Click the Remember my credentials checkbox and click OK:



11. Select the StorNext directory on the network server:



12. Click OK:



13. Enter your password for the share again if required. Click the Remember my credentials checkbox and click OK:



14. Click Finish to complete creating the Windows network drive map:



(click image to enlarge)

At this point mapping the drive in Windows is complete. The directory you mapped will open on your Windows desktop.

Example:



(click image to enlarge)

1. If currently open, close FinalCut ProX.
2. Open Downloads folder in Finder, and look for the CatDVFCPXPlugin0.02.dmg file.
3. Drag and drop the .dmg file to the Applications folder.
4. Double-click the .dmg file to install the plugin.
5. The installation will create a new CatDV Search icon in your Applications folder:



If you double-click the icon, the CatDV Search app will open:



(click image to enlarge)

6. Launch FinalCut ProX.
7. Load the CatDV Search panel.
8. The first time you load the panel, you will be prompted to enter the CatDV Server Address. Enter the NAS VIP address in this field and click Connect:



(click image to enlarge)

The CatDV Search Plugin will open:



(click image to enlarge)

The StorNext VM button for Controller B:



StorNext VM button for Controller A:



1. Enter the username and password for StorNext (default user name is "admin"; and password is "password". If required, enter a new password for the admin account.

Note: Be patient: it may take a while for the StorNext UI to display. Only click the Login button or press the "Enter" key once.

2. Complete the Configuration Wizard in the primary StorNext VM.
3. Create the file systems you need on the array in StorNext. See All Tasks > Administer > File System Tasks > Add a File System in the StorNext 7 Documentation Center.

Note: The default chunk size, which might also be known as cluster size, or allocation unit size, used for the file system on the H-Series storage, as configured from the factory, is 256KiB. Quantum recommends you use this.

Note: The HA shared file system (hafs) is already configured on the system. You do not need to create or configure the hafs.

Use this procedure to update your H4000 Essential software if your system HAS an active internet connection.

Note: You will update Controller A from the user interface on Controller B, and update Controller B from the user interface on Controller A.

Quantum recommends you update the system to the latest version of H4000 Essential software. Note the following:

Updates to QBSP 2.0.2 and later software are supported from:

• QBSP 2.0.1
• H-Series 1.6.1
• H-Series 1.6.0
• H-Series 1.5.3
• H-Series 1.5.2

For 1.5.1 and earlier systems, review the following update steps:

Update overview (1.5.1 and earlier to 2.0.2)

1. Update to H-Series 1.5.2 (see the update steps below).
2. Update NVD firmware to 081321V1 Contact Quantum support or your Quantum Service Provider to update the NVD firmware to 081321V1 if this has not yet been done. For Quantum support or your Quantum Service Providers, see Update H-Series NVD Firmware to 081321V1 (requires CSWeb log in).
3. Update to QBSP 2.0.2 (see the update steps below).
4. After you update the H4000 Essential to 2.0.2, update the NVD firmware to 011222V1:

• For H4000 Essential, see Update NVD firmware

Update the software

1. Verify which version of software is running on the system.
To verify software version on the system

1. From the H4000 Essential UI, click the 3 dot icon at the upper right-hand corner:



2. Click About.

The controller software version is shown on the first line of the About page.

Example (H4000 Essential version 1.5.0 is installed):



2. To update to a newer version the software:



3. Click CONFIGURATION in the top navigation (item 1 above).
4. Click Update Platform in the left navigation (item 2 above).
5. Make sure the radio button next to Remote Repository in the Source section is selected (item 3 above).
6. Click CHECK FOR UPDATE (item 4 above).

You will see a confirmation that the system is checking the online repository for an update:

 



If the latest version of the software is not currently installed, and an update is available from the online repository, you will see a confirmation that it can be updated, and the update version that is available for download to the system.

Note: The UPDATE NOW button for the controller you are logged into will be grayed-out and not functional, while the controller you are not logged into will allow you to update it.

Example (Controller A):



Example (Controller B):



If the latest software is installed, you will see an indication similar to one of the following messages, the UPDATE NOW button is gray (disabled). Skip the remainder of these update steps, since you cannot, and do not need to update the H4000 Essential software.

For Controller A:



For Controller B:



7. Click UPDATE NOW for the controller whose user interface you are NOT logged into:
Example (Controller A):



The software will download to the controller, and update the software.

What is shown in the H4000 Essential UIs (user interfaces) while the software is updating?

When the software is being updated, the metadata arrays on both boot drives are recovered. Because of this:

1. Controller A UI will present degraded and rebuilding drive alert tickets similar to the following:



These types of alerts are expected and can be ignored during the software update, and can be deleted after the update is complete.

2. The Controller B UI will display degraded RAID device health similar to the following:



The system should return to a healthy state after the software update is complete.

3. Before the controllers have finished updating the H4000 Essential software and rebuilding drives, you may not be able to log into the UI on either controller.

Wait until the H4000 Essential software update has finished, and log in again.

Note: It may take up to 20 minutes to download the update file, so be patient while the software downloads.

The H4000 Essential software will begin the update process. While you will see the following confirmation indicating that the update was successful, it's just confirming that the update is valid and can begin. At this point, the update process is not 100% finished, see note below:



Note: The update will reboot the controller, and will also require an additional 15-30 more minutes before the update of this controller can be initiated from the other controller's user interface. If you initiate an update before the first controller update is complete, that update will fail and you will see a failure notification.

Also, make sure the status of the StorNext VM on the other controller is "running" after the reboot of the controller that was just updated. Do this before initiating the update of this controller from the user interface of the other controller:

Verify the StorNext VM is running on a specific controller

1. In the H4000 Essential UI, click on the "information" icon for the StorNext VM running on Controller B :

Example 1 (for the StorNext VM running on Controller B)



(click image to enlarge)

2. Look for the text that indicates the "State" of the StorNext VM on Controller B is "running".

Example 1 output (dialog that is displayed when the information icon is clicked for the StorNext VM running on Controller B):



(click image to enlarge)

3. For the StorNext VM running on Controller A, click on the "information" icon for the StorNext VM running on Controller A.

Example 2 (for the StorNext VM running on Controller A)



(click image to enlarge)

4. Look for the text that indicates the "State" of the StorNext VM on Controller A is "running".

Example 2 output (dialog that is displayed when the information icon is clicked for the StorNext VM running on Controller A):



(click image to enlarge)

Once the update of the other controller is complete, it will take about 10 min for both controllers to sync.

8. If you have not yet updated the controller you are logged into, launch the user interface of the other controller:

To launch the Controller A user interface, when logged into the Controller B user interface, click this, in the panel for Controller A:



To launch the Controller B user interface, when logged into the Controller A user interface, click this, in the panel for Controller B:



9. Log in to the user interface of the other controller:



1. Enter admin for the user, and the password for the admin user.

Note: The admin user is currently the only user account in the H-Series UI.

2. Click LOGIN.

10. Complete steps 6-10 from the other controller to update this controller.

The platform software update is complete.

11. After you update the H4000 Essential to 2.0.2, update the NVD firmware to 011222V1:

For NVD firmware updates to 011222V1:

Note: If you have already updated your system to 2.0.1, and NVD firmware has already been updated to 011222V1, you DO NOT need to update the NVD firmware again. Your system is already running the latest NVD firmware.

Once 2.0.2 is installed, complete the steps to update the NVD firmware to 011222V1:

• For H4000 Essential, see Update NVD firmware

For NVD firmware updates to 081321V1:

The NVD firmware update to 081321V1 requires Quantum Support or your Quantum service partner, who must complete the steps to Update NVD firmware to 081321V1 (requires CSWeb login).

Use this procedure to update your H4000 Essential if your system DOES NOT HAVE an active internet connection. This would typically be used for updates at "dark sites" (such as a secure data centers). In this case, download the update file, move it to the /mnt/data/scratch/ directory on the H4000 Essential, and transfer the update file manually to the system over SCP from the command line using a Terminal (MacOS) or PuTTY (Windows) console, and then use the UI to update the system using the "Update Platform Software" page using the "Local File" option as the update "Source":

Quantum recommends you update the system to the latest version of H4000 Essential software. Note the following:

Note: You will update Controller A from the user interface on Controller B, and update Controller B from the user interface on Controller A.

Updates to QBSP 2.0.2 and later software are supported from:

• QBSP 2.0.1
• H-Series 1.6.1
• H-Series 1.6.0
• H-Series 1.5.3
• H-Series 1.5.2

For 1.5.1 and earlier systems, review the following update steps:

Update overview (1.5.1 and earlier to 2.0.2)

1. Update to H-Series 1.5.2 (see the update steps below).
2. Update NVD firmware to 081321V1 Contact Quantum support or your Quantum Service Provider to update the NVD firmware to 081321V1 if this has not yet been done. For Quantum support or your Quantum Service Providers, see Update H-Series NVD Firmware to 081321V1 (requires CSWeb log in).
3. Update to QBSP 2.0.2 (see the update steps below).
4. After you update the H4000 Essential to 2.0.2, update the NVD firmware to 011222V1:

• For H4000 Essential, see Update NVD firmware

1. Verify which version of software is running on the system:
To verify the software version installed on the system

1. Log in to the H-Series UI.
2. Click the 3-dot icon on the upper right-hand corner of the CLUSTER page:



3. Click About:



4. View the "About" page and look for the software version currently running on the controllers:



Leave your browser open.

1. Open a browser tab.
2. Navigate to the online form:

https://mysoftware.quantum.com/forms/h4000essential

https://mysoftware.quantum.com/forms/f2200

The H4000 Essential software update form



3. Fill out the form and click Submit to access the software update downloads for your H4000 Essential.

4. After you submit the form, you will receive an email with a link to the update download page for the H4000 Essential.

The software update page

The following is an example of the software download page, (update link highlighted):



The following is an example of the software download page (conversion link highlighted):



2. Click Download for the H4000 Essential <software version> update package:



The file will be downloaded to the system your browser is running on. The file name will be similar to qcsp-2.x-upgrade.tar.

Note: Download time depends on the speed of your internet connection, but the file size is about 2 GB.

3. Transfer the file to both controllers:

SCP the file to the system From the laptop you downloaded the file to, use SCP to copy the file to Controller A and Controller B. Use the management IP address of the controller, the admin user name, and the password for the admin account in the file transfer utility.

Note: Use either a drag-and-drop SCP or FTP utility (like Transmit or Filezilla for MacOS, or WinSCP or Filezilla for Windows), or a command-line utility (like Terminal for MacOS, or the Windows 10 or later command prompt or PuTTYSCP.exe for Windows) to manually copy the files.

Example: macOS Terminal scp file transfer

1. Open a terminal window.
2. scp the file from your local download location to the /mnt/data/scratch/ directory on Controller A.

Example:

scp qcsp-2.x-update.tar admin@10.20.223.218:/mnt/data/scratch/

OR (for conversion/updates) from 1.x software:

scp qcspconv-vsxx.tar admin@10.20.223.218:/mnt/data/scratch/

3. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):

qcsp-2.x-update.tar    80%    651MB    482.0KB/s    05:27 ETA

OR (for conversion/updates) from 1.x software:

qcspconv-vsxx.tar 80% 651MB 482.0KB/s 05:27 ETA

Example: Windows 10 command prompt scp file transfer

1. Open a Windows command prompt.
2. scp the file from your local download location to the /mnt/data/scratch/ directory on Controller A.

Example:

C:\Users\<user name>\Downloads>scp qcsp-2.x-update.tar admin@10.20.223.218:/mnt/data/scratch/

OR (for conversion/updates from 1.x software):

C:\Users\<user name>\Downloads>scp qcspconv-vsxx.tar admin@10.20.223.218:/mnt/data/scratch/

3. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):

qcsp-2.x-update.tar    80%    651MB    482.0KB/s    05:27 ETA

OR (for conversion/updates) from 1.x software:

qcspconv-vsxx.tar    80%    651MB    482.0KB/s    05:27 ETA

4. Log in to the H-Series UI:
1. Open a browser and access the H-Series UI log in page using the management IP address for the controller you want to log in to (you can log in to either controller's UI):


2. Enter admin for the user, and the password for the admin user.

Note: The admin user is currently the only user account in the H-Series UI.

3. Click LOGIN.



5. From the browser for the H-Series UI on Controller Node A, click CONFIGURATION in the top navigation (item 1 above).
6. Click Update Platform Software in the left navigation (item 2 above).
7. Click the radio button next to Local File in the Source section (item 3 above).



8. Enter /mnt/data/scratch/ and complete file name in the Path field (item 1 above).

Example:

/mnt/data/scratch/
9. Click CHECK FOR UPDATE (item 2 above).
10. Once the local update file is confirmed, click UPDATE NOW:

The H4000 Essential software will begin the update process. While you will see the following confirmation indicating that the update was successful, it's just confirming that the update is valid and can begin. At this point, the update process is not 100% finished, see note below:



Note: The update will reboot the controller, and will also require an additional 15-30 more minutes before the update of this controller can be initiated from the other controller's user interface. If you initiate an update before the first controller update is complete, that update will fail and you will see a failure notification.

Also, make sure the status of the StorNext VM on the other controller is "running" after the reboot of the controller that was just updated. Do this before initiating the update of this controller from the user interface of the other controller:

Verify the StorNext VM is running on a specific controller

1. In the H4000 Essential UI, click on the "information" icon for the StorNext VM running on Controller B :

Example 1 (for the StorNext VM running on Controller B)



(click image to enlarge)

2. Look for the text that indicates the "State" of the StorNext VM on Controller B is "running".

Example 1 output (dialog that is displayed when the information icon is clicked for the StorNext VM running on Controller B):



(click image to enlarge)

3. For the StorNext VM running on Controller A, click on the "information" icon for the StorNext VM running on Controller A.

Example 2 (for the StorNext VM running on Controller A)



(click image to enlarge)

4. Look for the text that indicates the "State" of the StorNext VM on Controller A is "running".

Example 2 output (dialog that is displayed when the information icon is clicked for the StorNext VM running on Controller A):



(click image to enlarge)

Once the update of the other controller is complete, it will take about 10 min for both controllers to sync.

11. If you have not yet updated the controller you are logged into, launch the user interface of the other controller:

To launch the Controller A user interface, when logged into the Controller B user interface, click this, in the panel for Controller A:



To launch the Controller B user interface, when logged into the Controller A user interface, click this, in the panel for Controller B:



12. Log in to the user interface of the other controller:



1. Enter admin for the user, and the password for the admin user.

Note: The admin user is currently the only user account in the H-Series UI.

2. Click LOGIN.

13. Complete Step 4 through Step 10 for the other controller.

When finished updating Controller Node A and Controller Node B, determine if you need to repeat this procedure to update to a more recent version of H4000 Essential software. If your system is now running the latest software available, the H4000 Essential software update is complete.

After you update the H4000 Essential to 2.0.2, update NVD firmware to 011222V1, If your system NVD software has not yet been updated to 011222V1:

For NVD firmware updates to 011222V1:

Note: If you have already updated your system to 2.0.1, and NVD firmware has already been updated to 011222V1, you DO NOT need to update the NVD firmware again. Your system is already running the latest NVD firmware.

Once 2.0.2 is installed, complete the steps to update the NVD firmware to 011222V1:

• For H4000 Essential, see Update NVD firmware

For NVD firmware updates to 081321V1:

The NVD firmware update to 081321V1 requires Quantum Support or your Quantum service partner, who must complete the steps to Update NVD firmware to 081321V1 (requires CSWeb login).

Note: If you have already updated your system to 2.0.1, and NVD firmware has already been updated to 011222V1, you DO NOT need to update the NVD firmware again. Your system is already running the latest NVD firmware.

If you have an internet connection from the system:

1. Using an SSH utility (like Terminal for the MacOS or PuTTY for Windows), log in to the CLI of the StorNext VM running on Controller Node B as the stornext user and the password for the stornext user account.

2. Log in as the rootsh user from within the stornext user account. Enter:
sudo rootsh
3. Enter the password for the stornext user account again.
4. Run the UUI update command. Enter:
/opt/quantum/uui-common/bin/uui upgrade

The update will download from the Quantum online YUM repository and update to the latest StorNext Unified UI software.

5. When the update is complete, log out of the SSH utility. Enter the word exit twice to close the console.

If you don't have an internet connection from the system, download the upgrade bundle file and upgrade the StorNext VM running the StorNext UUI on Controller node B.

1. Navigate to the myStorNext web site at: https://mystornext.quantum.com/ and log in using your myStorNext email and password.



2. In the left navigation, click UUI Downloads.



3. The Release Build Downloads section describes the file available for download. See the image below as an example:

   

   • If you are performing an upgrade of the UUI package on a StorNext appliance, then click on a link labeled Combined Package...Updates Only that corresponds with the version of StorNext installed on your system.

   • If you are performing a new install of the UUI on your own hardware (non-StorNext appliance), then click on a link labeled RYO Install Package...New Install that corresponds with the version of StorNext installed on your system.

   • If you are performing an upgrade of the UUI on your own hardware (non-StorNext appliance), then click on a link labeled RYO Install Package...New Install/Upgrade that corresponds with the version of StorNext installed on your system.

   Example (for a download link called):

   

   The downloaded file name will be similar to:

   uuiryo-install-pkgs-v702RC1-2021-12-07.tar.gz

   (where: green indicates the StorNext version, and blue is the build date)

4. Use scp to copy the . tar.gz upgrade file to the /home/stornext directory using the IP address of the StorNext VM running on Controller Node B. See Pro Tip! Determine the Primary and Secondary StorNext VMs and their IP addresses.

   Note: Use either a drag-and-drop SCP or FTP utility (like Transmit or Filezilla for MacOS, or WinSCP or Filezilla for Windows), or a command-line utility (like Terminal for MacOS, or the Windows 10 or later command prompt or PuTTYSCP.exe for Windows) to manually copy the files.

5. Log in to the command line of the StorNext VM running on Controller Node B as the stornext user and the password for the stornext user account.

6. Log in as the rootsh user. Enter:
sudo rootsh
7. Enter the password for the stornext user account again.
8. Move the .. tar.gz file to the /scratch/ directory on the StorNext VM:

Example (StorNext Unified UI update 6):

mv /home/stornext/stornext-uui-v701-update6-rc1-2021-06-10.tar.gz /scratch/
9. Extract the file in /scratch/:

Example (StorNext Unified UI update 6):

tar xvzf /scratch/stornext-uui-v701-update6-rc1-2021-06-10.tar.gz
10. Change to the extracted directory:

Example (StorNext Unified UI update 6):

cd /scratch/stornext-uui-v701-update6-rc1-2021-06-10
11. Install the StorNext Unified UI update. Enter:
./uui-update.sh
1. Log out of the StorNext Unified UI, if open.
2. Clear your browser cache.
3. Log in to the StorNext Unified UI, if needed. See Access the StorNext User Interface (new UI introduced in StorNext 7.0.1).

Note: You only need to upgrade the StorNext VM from a single controller, either Controller A or Controller B. Both StorNext VMs are upgraded in the steps included here.

1. Click CONFIGURATION in the top navigation (item 1 above).
2. Click Upgrade StorNext in the left navigation (item 2 above).
3. Make sure the radio button next to Quantum Remote Repository in the Source section is selected (item 3 above).
4. Click CHECK FOR UPGRADE (item 4 above).

UI Update Feedback

You will see a confirmation that the system is checking the online repository for an update/tmp/ for the update file:

 



If an update is available from the online repositoryon /tmp/, you will be moved to the next step, to "Download Update Files", with a confirmation that it can be updated, the update version available, and a DOWNLOAD FILES button.



5. Click DOWNLOAD FILES (item 5 above). You will see a confirmation that the update is downloading from the online repositoryto the StorNext VM:



(click image to enlarge)

Note: Download time depends on the speed of your internet connection, but it may take 30 minutes to 1 hour to download the update file It will take about ten minutes to "download"/move the update file to the StorNext VM from the H4000 system, so be patient while the software downloads. The update file size is about 6 GB.

When the files have finished downloading, you will be moved to the next step "Verify Files", and see the two files available to verify.

6. Click VERIFY FILE on one of the update files:



(click image to enlarge)

The file contents will begin to be verified.

Note: It may take up to 10 minutes to verify the downloaded update file, so be patient while the software is verified.



(click image to enlarge)

When the file has been verified, you will see a confirmation like this and the VERIFY FILE button will be disabled:



7. Click VERIFY FILE on the other update file:



(click image to enlarge)

Note: It may take up to 10 minutes to verify the downloaded update file, so be patient while the software is verified.

IMPORTANT! If you are running the StorNext VMs as a NAS cluster, you will see an error message at the top of the H-Series UI when the file is verified. Do the following:

Update the Appliance Controller software for NAS-clustered systems

If you have not already done so, for systems configured as a NAS cluster, you must update the Appliance Controller software running on the StorNext VM running on on the system to 3.1.0 or later before the StorNext 7.0.2 or later software update will complete.

For systems configured as a NAS cluster, the StorNext update will fail. While the verification step indicates the verification step was successful, the installation process will stall at that point and will not continue without intervention. Here's the error message you will see at the top of the Update StorNext page



1. Update the Appliance Controller software:

Go to the Appliance Controller update instructions page

Update notes:

• Open an SSH session and connect using the management IP address for the StorNext VM that is operating as the NAS cluster "master" node.
• If you do not have an active internet connection, perform the update using the instructions for NAS-clustered systems that state you "CAN" access the online update repository).
• If you do not have an active internet connection (for dark site installations), perform the update using the instructions for NAS-clustered systems that state you "CAN NOT" access the online update repository).
• Perform the following steps: "Pre-upgrade...", "Upgrade...", and "After you Upgrade".

2. Go back to the H-Series UI StorNext update page. Click the VERIFY FILE button to verify the first update file (item 3 above).
3. Click the VERIFY FILE button to verify the second update file (item 4 above).

The verification step for the update files should complete without error, and the update should continue.

When both files have been verified, the Update from Files section will open.

8. Click UPDATE FROM FILES:



(click image to enlarge)

You will see the update beginning, along with a notification of time elapsed, and a task ID, and a status of "PENDING":



(click image to enlarge)

Note: Be patient during the update, since it will take a while to update the software and reboot both StorNext VMs.

Eventually, the Monitor Update section will open showing progress logs for the updates on both controllers and the software will begin updating. In this screenshot, the StorNext VM on Controller Node A is "Complete", and Controller B is just beginning the update:



(click image to enlarge)

9. When finished upgrading the StorNext VM on Controller Node A and Controller Node B, you will see both logs with green steps indicating all steps completed, and gray for those not needed, and a state at the bottom of both panels of "Platform Update Complete", indicating that the StorNext VMs have both been updated to the latest available StorNext VM software:



(click image to enlarge)

When the update is finished for both StorNext VMs, this procedure is complete.

Use this procedure to update to a newer version of StorNext running on the StorNext VMs if your system DOES NOT have an active internet connection. This would typically be used for updates at "dark sites" (such as a secure data centers). In this case, you will need to download the update files, move them to the H4000 Essential and update the system manually from the command line using a Terminal (MacOS) or PuTTY (Windows) console.

Update the Appliance Controller software for NAS-clustered systems

If you have not already done so, for systems configured as a NAS cluster, you must update the Appliance Controller software running on the StorNext VM running on on the system to 3.1.0 or later before the StorNext 7.0.2 or later software update will complete.

For systems configured as a NAS cluster, the StorNext update will fail. While the verification step indicates the verification step was successful, the installation process will stall at that point and will not continue without intervention. Here's the error message you will see at the top of the Update StorNext page

1. Update the Appliance Controller software:

Go to the Appliance Controller update instructions page

Update notes:

• Open an SSH session and connect using the management IP address for the StorNext VM that is operating as the NAS cluster "master" node.
• If you do not have an active internet connection, perform the update using the instructions for NAS-clustered systems that state you "CAN" access the online update repository).
• If you do not have an active internet connection (for dark site installations), perform the update using the instructions for NAS-clustered systems that state you "CAN NOT" access the online update repository).
• Perform the following steps: "Pre-upgrade...", "Upgrade...", and "After you Upgrade".

2. Go back to the H-Series UI StorNext update page. Click the VERIFY FILE button to verify the first update file (item 3 above).
3. Click the VERIFY FILE button to verify the second update file (item 4 above).

The verification step for the update files should complete without error, and the update should continue.

Note: You only need to update the StorNext VM from a single controller, either Controller A or Controller B.

If you use this procedure inside secure location:

1. Download the update file from outside the secure location.
To download the file:

1. Open a browser tab.
2. Navigate to the online form:

https://mysoftware.quantum.com/forms/h4000essential

https://mysoftware.quantum.com/forms/f2200

The H4000 Essential software update form



3. Fill out the form and click Submit to access the software update downloads for your H4000 Essential.

4. After you submit the form, you will receive an email with a link to the update download page for the H4000 Essential.

The software update page

The following is an example of the software download page, (update link highlighted):



The following is an example of the software download page (conversion link highlighted):



2. Click Download for the H4000 Essential <software version> StorNext VM update package.

Example (the 7.0.3 StorNext VM update package for H4000 Essential):



The file will be downloaded to the system your browser is running on. The file name will be similar to quantum-SNA-7.0.3.OS7-23559-106862E-2.0.1-103-upgrade.tar.

Note: Download time depends on the speed of your internet connection, but the file size is about 6 GB.

3. Transfer the file:
• From the laptop you will use to upload the file to the H4000 Essential, use scp or ftp to move the file to the H4000 Essential. scp the update file to the /tmp/ directory on one of the controller nodes. Use the management IP address of the controller, the admin user name, and the password for the admin account in the file transfer utility.

Note: Use either a drag-and-drop SCP or FTP utility (like Transmit or Filezilla for MacOS, or WinSCP or Filezilla for Windows), or a command-line utility (like Terminal for MacOS, or the Windows 10 or later command prompt or PuTTYSCP.exe for Windows) to manually copy the files.

• Transfer the file manually to the /tmp/ directory:
• Example: macOS Terminal scp file transfer

  1. Open a terminal window.
  2. Open the directory on your system where you downloaded the update file.
  3. scp the file from your local download location to the /tmp directory on Controller A.

  Example:

  scp quantum-SNA-7.0.3.OS7-23559-106862E-2.0.1-103-upgrade.tar admin@10.20.223.218:/tmp

  4. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):

  quantum-SNA-7.0.3.OS7-23559-106862E-2.0.1-103-upgrade.tar    80%    8.57GB    482.0KB/s    05:27 ETA

• Example: Windows 10 command prompt scp file transfer

  1. Open a Windows command prompt.
  2. scp the file from your local download location to the /tmp directory on Controller A.

  Example:

  C:\Users\<user name>\Downloads>scp quantum-SNA-7.0.3.OS7-23559-106862E-2.0.1-103-upgrade.tar admin@10.20.223.218:/tmp

  3. Enter the admin account password. You will see the file begin to transfer to the system, with an estimate of the percent of the file transferred (in green for clarification):

  quantum-SNA-7.0.3.OS7-23559-106862E-2.0.1-103-upgrade.tar    80%    8.57GB    482.0KB/s    05:27 ETA

4. Repeat the last step to transfer the file to the other controller using the values for that controller.
5. Log in to the H-Series UI:
1. Open a browser and access the H-Series UI log in page using the management IP address for the controller you want to log in to (you can log in to either controller's UI):


2. Enter admin for the user, and the password for the admin user.

Note: The admin user is currently the only user account in the H-Series UI.

3. Click LOGIN.



6. Click CONFIGURATION in the top navigation (item 1 above).
7. Click Update StorNext in the left navigation (item 2 above).
8. Make sure the radio button next to Local StorNext Update File Path... in the Source section is selected (item 3 above).
9. Enter /tmp/ for the update file location on the Controller for the interface you are logged into (item 4 above).
10. Click CHECK FOR UPDATE (item 4 above).

UI Update Feedback

You will see a confirmation that the system is checking the online repository for an update/tmp/ for the update file:

 



If an update is available from the online repositoryon /tmp/, you will be moved to the next step, to "Download Update Files", with a confirmation that it can be updated, the update version available, and a DOWNLOAD FILES button.



11. Click DOWNLOAD FILES (item 5 above). You will see a confirmation that the update is downloading from the online repositoryto the StorNext VM:



(click image to enlarge)

Note: Download time depends on the speed of your internet connection, but it may take 30 minutes to 1 hour to download the update file It will take about ten minutes to "download"/move the update file to the StorNext VM from the H4000 system, so be patient while the software downloads. The update file size is about 6 GB.

When the files have finished downloading, you will be moved to the next step "Verify Files", and see the two files available to verify.

12. Click VERIFY FILE on one of the update files:



(click image to enlarge)

The file contents will begin to be verified.

Note: It may take up to 10 minutes to verify the downloaded update file, so be patient while the software is verified.



(click image to enlarge)

When the file has been verified, you will see a confirmation like this and the VERIFY FILE button will be disabled:



13. Click VERIFY FILE on the other update file:



(click image to enlarge)

Note: It may take up to 10 minutes to verify the downloaded update file, so be patient while the software is verified.

IMPORTANT! If you are running the StorNext VMs as a NAS cluster, you will see an error message at the top of the H-Series UI when the file is verified. Do the following:

Update the Appliance Controller software for NAS-clustered systems

If you have not already done so, for systems configured as a NAS cluster, you must update the Appliance Controller software running on the StorNext VM running on on the system to 3.1.0 or later before the StorNext 7.0.2 or later software update will complete.

For systems configured as a NAS cluster, the StorNext update will fail. While the verification step indicates the verification step was successful, the installation process will stall at that point and will not continue without intervention. Here's the error message you will see at the top of the Update StorNext page



1. Update the Appliance Controller software:

Go to the Appliance Controller update instructions page

Update notes:

• Open an SSH session and connect using the management IP address for the StorNext VM that is operating as the NAS cluster "master" node.
• If you do not have an active internet connection, perform the update using the instructions for NAS-clustered systems that state you "CAN" access the online update repository).
• If you do not have an active internet connection (for dark site installations), perform the update using the instructions for NAS-clustered systems that state you "CAN NOT" access the online update repository).
• Perform the following steps: "Pre-upgrade...", "Upgrade...", and "After you Upgrade".

2. Go back to the H-Series UI StorNext update page. Click the VERIFY FILE button to verify the first update file (item 3 above).
3. Click the VERIFY FILE button to verify the second update file (item 4 above).

The verification step for the update files should complete without error, and the update should continue.

When both files have been verified, the Update from Files section will open.

14. Click UPDATE FROM FILES:



(click image to enlarge)

You will see the update beginning, along with a notification of time elapsed, and a task ID, and a status of "PENDING":



(click image to enlarge)

Note: Be patient during the update, since it will take a while to update the software and reboot both StorNext VMs.

Eventually, the Monitor Update section will open showing progress logs for the updates on both controllers and the software will begin updating. In this screenshot, the StorNext VM on Controller Node A is "Complete", and Controller B is just beginning the update:



(click image to enlarge)

15. When finished upgrading the StorNext VM on Controller Node A and Controller Node B, you will see both logs with green steps indicating all steps completed, and gray for those not needed, and a state at the bottom of both panels of "Platform Update Complete", indicating that the StorNext VMs have both been updated to the latest available StorNext VM software:



(click image to enlarge)

When the update is finished for both StorNext VMs, this procedure is complete.