OneFS 6.5 Upgrade - Isilon Info Hub

For general information about upgrades, or about another specific upgrade, see OneFS Upgrades - Isilon Info Hub.

 

Welcome to the EMC Isilon OneFS 6.5 Upgrade Information Hub. OneFS 6.5 reached the end of its service life on June 30, 2015. We encourage customers who are running OneFS 6.5 to upgrade to a supported version of OneFS. After June 30, if you call Support to open a case, you will be directed to upgrade to a supported code family. Support might still triage your issue, but will do so only on a limited basis and no patches will be offered or available. For a list of recommended OneFS versions and release notes, see the Current Isilon Software Releases document.


The following sections provide information and guidance to help you upgrade your OneFS 6.5 environment to a supported version of OneFS, such as the Target Code OneFS 7.1.1.x. The content is grouped by task. To successfully complete the upgrade, be sure to perform each task in the order specified, and do not skip any steps.

 

You can perform the upgrade yourself, or you can engage the EMC Remote Proactive team to perform the upgrade for you by contacting EMC Online Support (requires login) and submitting a Service Request. For more information, contact your account team.

 

If you choose not to request this service, you must follow all of the procedures detailed in the following sections and in the OneFS Upgrade Planning and Process Guide.


Note: Some content requires a login to EMC Online Support.


The OneFS 6.5 upgrade consists of the following phases.

 

Planning for the upgrade

 

This section will help you to learn about the upgrade process and the tasks that you must complete before you upgrade.


The upgrade from OneFS 6.5.x to a supported version of OneFS is a simultaneous upgrade process. We recommend that you make a full backup of data before you start and, if needed, mirror your business critical data to a second site. Prepare your users for the cluster unavailability. Client applications may require restarting after the OneFS upgrade, and you might have to refresh mounts and shares.


 

Back to top

 

Evaluating the health of your cluster

 

We recommend that you run the pre-upgrade check as far in advance of the upgrade as possible so that you'll have sufficient time to address any emerging issues.

 

Important: Before you upgrade OneFS 6.5, you should evaluate the health of your cluster to verify that it is in a supportable and operational condition. This will help to prevent upgrade issues. Some specific conditions to check:

  • Capacity level for drives, /ifs, and local partitions (see How to keep your EMC Isilon cluster from reaching capacity - ISI Knowledge)
  • Health status for drives, disk pools, and nodes (see article 16497,How to determine why a node is in an attention state)
  • Authentication provider status (for information about authentication and access control, see the OneFS Online Help)
  • GNA enabled (see article 90371,Upgrade to OneFS 7.0.1.2 and later is halted if Global Namespace Acceleration is enabled and SSD storage is less than the enforced minimum of 1.5 percent of total storage)
  • Failed jobs, running jobs, and paused jobs (for information about jobs, see the OneFS Online Help)
  • Critical events (see the OneFS Event Reference)


If you have questions about the health of your cluster, contact your account team for assistance.

 

Back to top

 

Completing pre-upgrade tasks

 

Before you upgrade OneFS 6.5, you must complete several pre-upgrade tasks to help ensure the success of your upgrade. If you don't complete these tasks, there is an increased risk of an upgrade failure. Make sure that you allocate sufficient time to complete the upgrade tasks and to resolve any issues that they reveal.

  • If you are upgrading to OneFS 8.0.0.0 and your cluster meets the following criteria, see article 480672 for information about avoiding a potential issue in which clients cannot connect to your cluster after the upgrade.
    • The cluster was running OneFS 6.5.5.x at one time.
    • When it was running OneFS 6.5.5.x, the cluster was configured with Kerberos authentication.
    • The cluster is currently configured with Kerberos authentication.
  • Assess your environment.
    • Check cluster readiness
    • Verify configuration settings
    • Perform an upgrade compatibility check

If you are upgrading from OneFS 6.5.4 or from OneFS releases 6.5.5.0 through 6.5.5.9, you must install a patch in order to run the pre-upgrade check utility. See article 89311, Patch to provide pre-upgrade configuration check for OneFS 6.5.5.

  • Assess the need for firmware updates.

Upgrade your firmware first, and OneFS last, to make sure that your data is continuously protected.

  • Set up IP pools for dynamic failover for NFS clients.
  • Set up SMB clients on static pools.
  • Back up any custom Job Engine settings, then change those settings to their default values. After upgrade completes, ensure that the value for the Job Engine parameter max_workers_per_storage_unit  is greater than the value of min_workers_per_cluster.  See article 204923, After upgrade from 6.5.5.x or 7.0.x to 7.1.x or 7.1.1.x or 7.2.x, job engine cores and jobs fail due to customized max_workers_per_storage_unit configuration.
  • Make sure that all Job Engine jobs priorities are set to Low.
  • Make sure that the File Pool Policies - Stop Processing More Rules setting is checked.
  • To avoid an issue where protection settings are changed to Managed by SmartPools after upgrade regardless of their settings in 6.5, disable the SmartPools job so that it does not start immediately after the upgrade. After the upgrade completes, disable the SmartPools "Manage requested protection levels" setting in the WebUI, then re-enable the SmartPools job. See article 480443, Protection settings are set back to Managed by SmartPools after upgrade from 6.5 to 7.x.
  • Back up your data
  • Complete or stop jobs in progress
  • Disconnect client connections

 

The following resources can help with pre-upgrade planning.

  • OneFS Upgrade Planning and Process Guide (read and follow the steps in chapter 3, "Completing pre-upgrade tasks")
  • Article 89232, Configuring sysctls and making sysctl changes persist through node and cluster reboots and upgrades
  • Article 480443, Protection settings are set back to Managed by SmartPools after upgrade from 6.5 to 7.x
  • Article 88766, Patches to provide pre-upgrade configuration checks for OneFS 6.5.4 and 6.5.5.0 - 6.5.5.9 upgrades to OneFS 7.0 or 7.1
  • Article 187717, How to upgrade OneFS on a compliance mode cluster
  • Article 89525, OneFS 7.0 and 7.1 Pre-Upgrade Check utility
  • Article 481150, After upgrading to OneFS 8.0.0.0, clients that rely on Kerberos authentication cannot be authenticated to the cluster.

 

Back to top

 

Performing the upgrade

    1. Download the OneFS image (requires login to EMC Online Support)
    2. Perform the upgrade. See the OneFS Upgrade Planning and Process Guide. Read and follow the steps in the section "Completing a simultaneous upgrade of OneFS".
    3. Verify the installation.
      1. Confirm that the health of all the nodes in the cluster is OK by running the following command:

        isi stat

    4. Remove the installation files from the /ifs/data directory by running the following command, where <onefs-version> is the four-digit OneFS version number:

      rm /ifs/data/onefs_v<onefs-version>_install.tar.gz

    5. Collect information about the cluster by running the following command:

      isi_gather_info

Back to top

Performing post-upgrade tasks

After the upgrade, you must complete certain restoration and change management tasks to help ensure that your cluster performs and behaves as expected.

      • Install patches
      • Review access control level (ACL) settings and re-establish user privileges
      • Restore client connections and custom settings
      • Configure base directories for access zones
      • Reconfigure SMB shares, home directory templates, and HDFS settings within access zones
      • Verify Kerberos migration
      • Update SMB auditing
      • The gcc compiler is no longer available in 7.0 and later releases.
      • Re-install Aspera if it was installed before the upgrade
      • Update custom scripts

 

Back to top

 

If you need assistance at any point in the upgrade, contact EMC Technical Support or your account team.