PowerScale+Implementation+ +Participant+Guide

POWERSCALE
IMPLEMENTATION
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Table of Contents
PowerScale Implementation ..................................................................................... 1

Rebranding - Isilon is now PowerScale ................................................................................ 2
PowerScale Solutions Certification Journey Map ................................................................. 3
Prerequisite Skills ................................................................................................................ 4
Course Objectives................................................................................................................ 5
Creating a New Cluster .............................................................................................. 6

Module Objectives ............................................................................................................... 7
Implementation Phases........................................................................................................ 8
Pre Engagement Questionnaire ........................................................................................... 9
Connecting Via Serial Port ................................................................................................. 10
Creating a Cluster .............................................................................................................. 11
Joining Nodes to Existing Cluster .......................................................................... 12

Module Objectives ............................................................................................................. 13
Verifying Version and Adding a Node................................................................................. 14
SmartFail: Remove a Node from Cluster ............................................................................ 16
Reformat a Node................................................................................................................ 18
Reimage a Node ................................................................................................................ 20
Reimage Use Case ............................................................................................................ 21
Completing Initial Configuration............................................................................. 22

Update Install Database ..................................................................................................... 24
Connectivity Tests.............................................................................................................. 25
Other Configuration Options .................................................................................. 26

SmartLock Compliance Mode ............................................................................................ 28
Secure Remote Services (SRS) ......................................................................................... 30
Hadoop Overview .............................................................................................................. 33
PowerScale Implementation
Page ii © Copyright 2020 Dell Inc.

Hadoop with PowerScale ................................................................................................... 35
Configuring Hadoop ........................................................................................................... 36
Upgrades and Updates ...................................................................................................... 38
OneFS Version Numbering ................................................................................................ 39
Upgrades ........................................................................................................................... 40
Upgrade Pause and Resume ............................................................................................. 41
Support Upgrade Paths to OneFS 8.1 (OneFS 8.2) ........................................................... 42
Patches and Firmware ....................................................................................................... 44
Automatic Replacement Recognition ................................................................................. 47
isi_upgrade_helper .................................................................................................... 48
isi_upgrade_helper Default ........................................................................................ 49
Release Notes ................................................................................................................... 50
Course Summary ..................................................................................................... 52

Course Summary ............................................................................................................... 53
© Copyright 2020 Dell Inc. Page iii

© Copyright 2020 Dell Inc. Page 1

Rebranding - Isilon is now PowerScale
Important: In mid-2020 Isilon launched a new hardware platform, the

F200 and F600 branded as Dell EMC PowerScale. Over time the
Isilon brand will convert to the new platforms PowerScale branding. In
the meantime, you will continue to see Isilon and PowerScale used
interchangeably, including within this course and any lab activities.
OneFS CLI isi commands, command syntax, and man pages may
have instances of "Isilon".
Videos associated with the course may still use the "Isilon" brand.
Resources such as white papers, troubleshooting guides, other
technical documentation, community pages, blog posts, and others
will continue to use the "Isilon" brand.
The rebranding initiative is an iterative process and rebranding all
instances of "Isilon" to "PowerScale" may take some time.
Page 2 © Copyright 2020 Dell Inc.

PowerScale Solutions Certification Journey Map
The graphic shows the PowerScale Solutions Expert certification track. You can
leverage the Dell Technologies Proven Professional program to realize your full
potential. A combination of technology-focused and role-based training and exams
to cover concepts and principles as well as the full range of Dell Technologies'
hardware, software, and solutions. You can accelerate your career and your
organization’s capabilities.
PowerScale Solutions
A. PowerScale Advanced Administration (C, VC)
B. PowerScale Advanced Disaster Recovery (C, VC)
(Knowledge and Experience based Exam)
Implementation Specialist, PowerScale Technology Architect Specialist, Platform Engineer, PowerScale

PowerScale
A. PowerScale Concepts (ODC)

A. PowerScale Concepts (ODC) A. PowerScale Concepts (ODC) B. PowerScale Hardware Concepts (ODC)
C. PowerScale Hardware Installation (ODC)
B. PowerScale Administration (C,VC,ODC) B. PowerScale Solution Design (ODC) D. PowerScale Hardware Maintenance
(ODC)
E. PowerScale Implementation (ODC)
Information Storage and Management
Information Storage and Management (C, VC, ODC)
(C) - Classroom
(VC) - Virtual Classroom
(ODC) - On Demand Course
For more information, visit: http://dell.com/certification

Prerequisite Skills
To understand the content and successfully complete this course, a student must
have a suitable knowledge base or skill set. The student must have an
understanding of:
• Current PowerScale hardware portfolio and the OneFS operating system
• PowerScale Concepts

Course Objectives
After completion of this course, you will be able to:

→ Create a new cluster.
→ Join a node to an existing cluster.
→ Complete the initial configuration.
→ Complete other configuration options.

Creating a New Cluster

Module Objectives
After completing this module, you will be able to:

• Describe how to connect to Node 1.
• Run the Configuration Wizard.
• Create the cluster.

Implementation Phases
The typical PowerScale installation consists of three phases: Planning,

Implementation, and Documentation, functional overview, and acceptance.
Each phase is divided into multiple tasks that the various members of the project
team handle.
1: The first phase is planning. During this phase, gather all required information for
the installation. A Pre- Engagement Questionnaire (PEQ) document outlines all the
information to gather. The customer completes the document and returns it to Dell
EMC before the installation date. The document ensures that the project team has
the required information for the design, installation, and configuration of the
PowerScale cluster.
2: The second phase of the project is the implementation and testing phase. During
this phase, the physical installation and initial configuration of the PowerScale
cluster is carried out and remote support configuration is done. Now, the testing
and verification of the cluster is performed to ensure that the cluster is ready for
use. In addition, the cluster is ready for advanced software installation and
configuration.
3: Phase three of the project consists of documenting the installation, providing a

functional overview of the cluster to the customer, and closing out the
implementation.

Pre-Engagement Questionnaire (PEQ)
The PowerScale PEQ is the replacement for the Configuration Guide. The PEQ
defines the Professional Services project installation parameters and facilitates the
communication between the responsible resources. For this scenario, the required
information is in the Hardware tab.
Double-click images for enlarged view.

Connecting Via Serial Port
To configure a PowerScale cluster for the first time, access the CLI by establishing
a serial connection to the node designated as node 1. The serial console gives
serial access when you cannot use the network. Other reasons for accessing using
a serial connection may be for troubleshooting, site rules, a network outage, and so
on. The serial port is usually a male DB9 connector. This port is called the service
port1.
Configure the terminal emulator utility to use the following settings:
1 Connect a serial null modem cable between a local system, such as a laptop, and
the service port on the node designated as node 1. As most laptops today no
longer have serial ports, you must use a USB-to-serial converter, available at many
online retailers. On the local system, launch a serial terminal emulator such as
mRemoteNG.

Creating a Cluster
This video demonstrates creating a new cluster.
Movie:
The web version of this content contains a movie.
Link:
https://edutube.emc.com/Player.aspx?vno=zyK3csP1f1h6F0cke3Ivog==&autoplay
=true

Joining Nodes to Existing Cluster

Module Objectives

• Verify the OneFS version.
• Add a node to an existing cluster.
• Remove a node from a cluster.
• Reformat and reimage a node.

Verifying Version and Adding a Node
Movie:
Script:
The first step before adding a node to a cluster is to verify which OneFS version is
running. Methods to check that the version include the front panel display, CLI, and
WebUI. Let us start with the CLI. As shown here, I am logged into the cluster. Run
the isi version command. Next, we can use the WebUI. Here I am logging in. The
version is shown in the upper right side of the browser. If the new node is
compatible with the OneFS version on the existing cluster you are joining, there is
no need to reimage the new node or nodes. The node downloads the correct
version of OneFS from the cluster during the join process and reimages
automatically. In this demonstration, a new cluster was created.
There are several ways to add a node to a cluster. You can use the node front
panel display, the Configuration Wizard, or the WebUI. We show adding a node
using the Configuration Wizard and then another node using the WebUI.
Here I have established a serial connection the node I want to add. At the
Configuration Wizard prompt, type 2 and press ENTER to join the node to an
existing cluster. Type the number of the cluster you want to add the node to, and
press ENTER. In this example, I have only one cluster that is indexed as 1. The
node obtains the proper version of OneFS from the cluster if its version of OneFS
differs from that of the cluster. If a reimage is needed, allow the operation to
complete before attempting to add additional nodes.
If the addition is successful, the node boots to a login prompt. Log in as root and
run isi status to verify cluster membership and health. If there are additional nodes
to add, wait 5 minutes between node additions to allow the cluster time to stabilize
and incorporate the newly joined nodes.
Next let us add the third node to the cluster using the WebUI. Here I am logging in
as root. On the Dashboard page, we can see that there are only two nodes in this
cluster. Remember that Gen 5 must have a minimum of three nodes and Gen 6
needs four nodes to form a cluster. Navigate to Cluster Management, Hardware
Configuration. Here we see one available node. Select the Add node in the Actions

column. Once it is finished working, let us navigate back to Dashboard, Cluster

Overview. The table indicates that the third node is recognized. After a minute, the
node is booted and part of the cluster.
We saw how to check the OneFS version and how to add nodes to a cluster using
the Configuration Wizard and the WebUI. This concludes the demo.
isi devices node add <serial-number> command is used to join an

available node to the cluster through CLI.

SmartFail: Remove a Node from Cluster
Movie:
The video shows how to remove a node from the cluster using the WebUI.
The SmartFail function removes a node from the cluster.
• SmartFail manually removes2 one node at a time from the cluster.

• The nodes are removed from the cluster node list when the process completes3.
• Once the node has been reformatted, it can be added back4 into the cluster or
into another cluster if wanted.
2Before smart failing multiple nodes, consider whether the cluster has enough free
space to maintain protection on the data in the cluster. Removing too many nodes
causes the cluster to lose quorum. Data is restriped to other nodes in the cluster as
part of the process.
3If the node is still connected to the back-end network when the process
completes, it automatically initiates a reformat - otherwise, it can be reformatted
manually.
4The use cases are to remove older nodes during a life-cycle technology refresh.
First, to move a node from one cluster to another cluster. Second, if PowerScale
Support has identified a critical hardware failure.

• isi devices node stopfail command is used to discontinue the smartfail

process on a node.
• To modify the logical node number (LNN) of a node run isi config command
followed by the command Innset.
Script:
We start by logging into the WebUI. For this demonstration, I am smartfailing node
ID 3 shown on the dashboard. Navigate to Cluster Management, Hardware
Configuration. Select the Remove Nodes tab. Select Node 3 and then Submit.
Next, I will Confirm the smartfail. Back on the Dashboard, we can see the node
status in the process of smartfailing. After several minutes, the Dashboard updates
showing the node is no longer a member of the cluster.

Reformat a Node
Reformatting a node is the quickest way to return a node to an unconfigured state.

Reformatting does not remove the node from the cluster completely unless
SmartFail has run over the node. Reformatting retains the current OneFS version
that is installed on the node.
Movie:
The video shows the reboot option.
All data and configuration information is destroyed when reformatting. Do not

reformat unless you are certain it should be run, the node contains no data, or the
data can be destroyed without issues. For example, because the node has been
successfully smart failed.
Use case5.
Script:
5 The use case for reformatting a node is when resetting or repurposing nodes, for
example, the case of testing cluster nodes. This performs the reset quickly so the
nodes can be used for other testing. Another use case example is when destroying
a cluster to reset it to prepare a SyncIQ failback for SmartLock or WORM
directories. WORM directories cannot be overwritten, they can only be removed by
reformatting the cluster. This also applies to enterprise SmartLock directories and
compliance SmartLock directories. If SyncIQ has not been configured, these
considerations do not apply.

I am connected to the node using the console port. You can also connect using an
SSH session to the node. I begin by logging in as root. Here I use the
isi_reformat_node --reboot command and typing yes to understand I am sure I
want to reformat. Typing yes again. The node reboots and as seen here, the
Configuration Wizard displays.

Reimage a Node
SolVe Online is used to view the latest procedures.
Reimaging a node performs the same node reset functionality as reformatting the
node. The difference is that the OneFS operating system is reinstalled during the
process. Connect to the reimaging node over the console port or an SSH session.
Reimaging a node can be done using a USB flash drive or by copying the OneFS
install file locally on the node. If reimaging using a USB flash drive containing the
OneFS image, a limited number of USB flash drives are supported.
Copy the OneFS install file to the node and run the isi_reimage command to
reimage a node without using a flash drive.
Caution: Only perform this procedure on a node that is not a member

of a cluster. Reimaging includes a node requiring a new installation of
OneFS or a node that has run SmartFail completely over it and was
removed from an active cluster. Like when reformatting, reimaging a
node erases all data.

Reimage Use Case
The use case is to install a new OneFS image on the cluster. In certain
circumstances, nodes with a OneFS version that is installed from the factory may
differ from the OneFS version on the cluster. Do not always upgrade or downgrade
automatically when the node is added to the cluster. In this case, the nodes must
be reimaged to match the cluster OneFS version.
Company Model Name Model Number Size
SanDisk Cruzer SDCZ36-08G 8 GB
SDCZ36-16G 16 GB
SDCZ36-32G 32 GB
Kingston DataTraveler DT101G2/8GBZ 8 GB

Technology 101(G2)
DT101G2/16GBZ 16 GB
DT101G2/32GBZ 32 GB

Completing Initial Configuration

Module Objectives

• Update the install database.
• Perform connectivity tests.

Update Install Database
After completing the installation, update the install database. Browse to the Dell
EMC Product Registration and Install Base Maintenance service portal at the URL
shown in the browser. Select the Product Registration and Install Base
Maintenance option and then select the IB Status Change option to open the form.
Next complete the form and then submit. Shown in the graphic are sources for
PowerScale technical support.
The graphic shows sources for PowerScale technical support.

Connectivity Tests
The final step of the initial configuration process is to perform connectivity tests.
The four tests - WebUI, HTTP, DNS, and client are performed from a client that is
connected over Ethernet to the cluster.
 The first test, PowerScale WebUI test, can be done by launching the browser6
to the cluster from the client.
 The other two tests, DNS, and client are performed post implementation7.
6Depending on the browser, you may be prompted with security information. Log in
over the administration interface to complete the test.
7Once the cluster is configured for DNS, you can test by pinging the cluster by
name. This is also true for the HTTP test, use a browser and the URL of the Fully
Qualified Domain Name and path. For example,
https://clustername.company.com/IFS. The client test can check access and
authorization. From a Windows client, map a drive to a share on the cluster. Then
drag and drop a file from the client to the mapped drive. Ensure that the transfer
completes successfully. From an NFS client, mount the export directory that is
presented from the cluster. Then copy a file from the client to the NFS mount point
and ensure that the transfer completes successfully.

Other Configuration Options

Module Objectives

• Configure a node or cluster in SmartLock Compliance mode.
• Configure Secure Remote Services (SRS).
• Identify how PowerScale works with Hadoop.
• Explain upgrades, updates, and release notes.

SmartLock Compliance Mode
Compliance mode enables cost-effective and efficient protection against accidental,

premature, or malicious deletion or modification of data. SmartLock provides
WORM, or Write-Once, or Read-Many status on files. In a WORM committed state,
files can be read but not deleted. This is in compliance with the regulations that the
U.S. Securities and Exchange Commission rule 17a-4f defines.
Movie:
Script:
This demonstration shows how to create a compliance mode cluster. You can
configure a node or cluster in Compliance mode by selecting the SmartLock
Compliance mode option in the Configuration Wizard. Here I am connected to the
node designated as node 1 with the node that is booted to the Configuration
Wizard. A compliance mode cluster must be created during the initial cluster
configuration process. Once you set a cluster to Compliance mode, you have to
reformat the node in order to return it to a standard cluster mode. If there is data on
the node, returning to standard cluster mode without data loss requires a
Professional Services engagement.
The first step is to select option 4, to reboot the node into SmartLock Compliance
mode. Next type yes to verify the option and understand that root access to the
node will be disabled. I press enter, and the node reboots.
The node boots back to the Configuration Wizard. Note the new wording on option
4, Disable SmartLock Compliance mode, indicating the node is in compliance
mode. This is the last opportunity to back out of compliance mode configuration
without reformatting the node.
Here I enter 1, to create a cluster. We are asked for a SmartLock license. I enter
that.
Accept the EULA, and then we set the password for compadmin and admin. The
rest of the configuration is no different than the standard cluster mode installs.
Remember to see the Configuration Guide for the information to enter. For this

demonstration, I am not going to step through each step. Here I am going to

commit the changes and the node reboot.
At the login prompt, let us go ahead and login as compadmin. I run the isi status
command.
As part of this demonstration lets,’s sees how to add a node to a compliant cluster.
I am connected serially to the node I want to join. Once again, select option 4 to
reboot in SmartLock Compliance mode. Once the boot completes, select option 2
in the Configuration Wizard.
This demonstration that is covered creating a SmartLock compliant cluster and

adding a node to the cluster. This concludes the demonstration.

Secure Remote Services (SRS)
The web version of this content contains an interactive activity.
Note: Secure Remote Services (SRS) is the replacement for EMC

Secure Remote Support (ESRS).
The exercise has audio.
EMC Secure Remote Support (or ESRS) is a two-way, secure, IP-based customer
service remote support system that allows 24x7 remote monitoring of EMC
products. ESRS replaced SupportIQ as the PowerScale remote support system.
So, let us see what the ESRS environment looks like. I start with the customer side.
Here I show a heterogeneous Dell EMC environment as ESRS is the tool that
many Dell EMC platforms use. I add the virtual edition of ESRS. This is the
gateway and at least one ESRS gateway server must be installed and configured.
The gateway server acts as the single point of entry and exit for IP-based remote
support activities and monitoring notifications. ESRS can be configured for
redundancy with more than one ESRS instance installed, allowing reports through
ESRS if hardware or partial data environment failure.
The environment has some firewalls. A few notes about the optional policy
manager. You need the Policy Manager if fulfilling requirements for authentication,
authorization, and auditing. By implementing the Policy Manager, you can enable
monitoring on a node-by-node basis, allow or deny remote support sessions, and

review remote customer service activities. The Policy Manager enables

permissions to be set for ESRS-managed devices.
Next I draw out the other half of the ESRS, the Dell EMC environment. Now, ESRS
functions as a communications Broker agent between the managed devices, the
Policy Manager, and Dell EMC. Dell EMC does not establish inbound network
communications to the systems. This is a security measure, benefiting customers
in secure sites while permitting limited, controlled outbound communications.
When the ESRS server retrieves a remote access request from the EMC
Enterprise, the policies that are configured on the Policy Manager access the
request and the ESRS server enforces these requests.
Communications between the customer site and Dell EMC support flow over an
encrypted HTTPS connection, which means that sensitive information does not
traverse the Internet unprotected.
On the Dell EMC support side, only authorized support representatives have
access to the customer systems or their information at all. All communication with
Dell EMC initiates from ESRS on port 443 or 8443 outbound from the customer site
to Dell EMC support services.
Enabling ESRS:

Before enabling and configuring ESRS, you must ensure the OneFS software has
a signed license and an ESRS gateway server is installed and configured. The IP
address pools that handle gateway connections must exist in system and must
belong to a subnet under groupnet0, which is the default system groupnet. Shown
is the OneFS 8.0 WebUI, Cluster Management, General Settings, ESRS page.
Later OneFS versions may prompt to update the license. Select Enable ESRS
Gateway Support, complete the fields, and Save Changes.
ESRS Documentation:
The ESRS Planning Guide has a complete description of gateway server

requirements, installation, and configuration. This guide provides component
requirements, configurations, and preparation for site installation. The EMC Secure
Remote Services Installation and Operations Guide provides a complete
description of the ESRS tool. Use this guide when implementing ESRS. Most
notably, the guide covers the installation and provisioning of ESRS. The EMC
Secure Remote Services Technical Description document provides a complete
description of ESRS features and functionality. This document includes Policy
Manager specifications and the Virtual Edition application.
These documents and others about ESRS can be found on the EMC Online
Support site (support.emc.com) and you can use the SolVe Desktop to download
documents. Remember to always check for the latest updates and Release Notes.

Hadoop Overview
Hadoop enables the distributed processing of large datasets across clusters of

commodity servers. It is designed to scale up from a single server to thousands of
servers dynamically, scaling up, or down based on resources and required service
levels8.
Holistic view of a Hadoop solution.
4 5
1
2 6
1: In a traditional Hadoop cluster, the data exists in silos. Production data is

maintained on production servers and then copied in some way to a Landing Zone
Server. Then it imports or ingests the data into Hadoop/HDFS (Hadoop Distributed
File System), making three copies of all data. Note that the data on HDFS is not
production data. It is copied from another source, and a process must be in place
to update the HDFS data periodically with the production data information.
8 Though Hadoop has emerged as a tool of choice for big data analytics, there are
also reasons to use it in typical enterprise environments. To analyze existing data
for improving processes and performance depending on your business model.

2: Hadoop has two core components: HDFS and MapReduce. HDFS is a scalable
file system that is used in the Hadoop cluster. MapReduce is the compute
algorithm that analyzes the data and collects the answers from the query.
3: NameNode:
• Holds the location information for every file in the cluster. The file system metes
data.
Secondary NameNode:
• Backup NameNode, a passive node that requires the administrator to intervene

to bring it up to primary NameNode.
4: Where the data resides, spread across cluster nodes, 3x mirrored.
5: Map Step:
• The primary node takes the input, divides it into smaller subproblems, and
distributes them to worker nodes. The worker node processes the smaller
problem and passes the answer back to its primary node.
Reduce Step:
• The primary node then collects the answers to all the subproblems and
combines them in some way to form the output. The answer to the problem it
was originally trying to solve.
6: Task Tracker:
• A node in the cluster that accepts tasks - Map, Reduce, and Shuffle operations
from a Job Tracker

Hadoop with PowerScale
Scale out NAS platform of PowerScale provides native support for the HDFS
protocol.
1: The NameNode on the PowerScale cluster gives the solution a complete and
automated failover process. If the node running as the NameNode fails, another
PowerScale node immediately picks up the function of the NameNode. No data or
metadata would be lost since the distributed nature of PowerScale spreads the
metadata across the cluster. There is no downtime if a failure occurs and most
importantly there is no need for administrative intervention to failover the
NameNode.
2: With PowerScale in a Hadoop solution, all production data resides on the

PowerScale cluster. It is unnecessary to export it out of the production applications
and import it elsewhere, the way a traditional Hadoop environment does. The
MapReduce algorithm runs on dedicated Hadoop compute nodes, which are
required to do the data analysis. The Hadoop data is held on PowerScale so that it
can be manipulated, whether by Hadoop or by using various protocols,
applications, or clients.

Configuring Hadoop
There are the five major steps to configure HDFS for a Hadoop solution.
1: First, you have to validate the OneFS version and license activation. This can be
verified from the WebUI by going to the Cluster Management, Licensing page.
Consult the PEQ for the license key.
Double-click the image for enlarged view.
2: Next you prepare the cluster which includes configuring DNS, SmartConnect,
and Access Zones to allow for the Hadoop cluster to connect to the PowerScale
OneFS cluster.
3: When preparing your Hadoop distribution (that is, Cloudera), do NOT select
HDFS service. PowerScale is used as storage and the native HDFS service is no
longer needed.
4: When configuring your Hadoop distribution (that is, Cloudera), refer to the
PowerScale OneFS installation guide to configure the Hadoop cluster elements, to
use the PowerScale cluster as its HDFS clients, and then tweak the HDFS

configuration of OneFS. Leave the PowerScale role as default during the role
assignment process.
5: Finally, verify your PowerScale-Hadoop implementation with native Hadoop

commands (that is, hadoop fs -ls /). To enable HDFS, from the WebUI, go to the
Protocols, Hadoop (HDFS), Settings page.

Upgrades and Updates
The terms “upgrade” and “update” are often used interchangeably. They describe
the process of changing to a newer version of the OneFS operating system (OS) or
changing to newer node or disk firmware versions. However, the terms “upgrade”
and “update” do not mean the same thing.
Upgrade is used when the OneFS operating system version changes. Upgrades
apply code fixes, new operating system features, and functionality. Often times an
upgrade changes the underlying structure or operations of the OneFS file system. It
marks a strategic step forward for the product and for the functionality that it offers
to production clusters.
Update is used when new firmware versions are installed on the nodes or on the
disk drives. Firmware updates are applied to fix (patch) firmware code issues and
to standardize all the nodes or disks onto the same firmware9 code level.
9 Often when receiving a new node or a new drive, the firmware that is shipped on
the new hardware is a different version than the firmware running on the production
cluster. Newer firmware versions add or change cluster functionality, sometimes
they are used to apply code fixes and add support for new hardware.

OneFS Version Numbering
Customers may ask about the OneFS version and an understanding of the version
identifiers. OneFS versions are broken down in the significance of the changes that
are made to the release. A change to the first and second numbers of the release
code identifies the major upgrades.
• First digit changes indicate major changes and potential core modifications to
the underlying operating system and data structures.
• The second digit indicates significant changes or enhancements, but usually do
not involve the core structure. Typically, significant features changes or
additions are in these releases.
• The last two numbers indicate minor releases.
− The third digit indicates smaller or less impactful feature enhancements. The
support of new nodes can be in the third digit release.
− The fourth digit denotes minor functionality and is used for issue fixes.

Upgrades
There are four phases to an upgrade:
• Phase 1 - Planning for an Upgrade

• Phase 2 - Pre-upgrade tasks
• Phase 3 - Performing the upgrade process
• Phase 4 - Post-upgrade tasks
Rolling Upgrade
A rolling upgrade is a per-node operation, upgrading and rebooting cluster nodes

one at a time. Only one node is offline at a time. Rolling upgrades are nondisruptive
to clients that can seamlessly failover their connections between nodes such as
NFSv3, and SMB 3.0’s continuous availability clients. Stateful protocols, such as
SMB 2.0, do not support transparent failover of their connections and have a brief
disruption when a node is rebooted into new code.
Simultaneous Upgrade
Simultaneous upgrades are faster than rolling upgrades, but reboot all nodes at the
same time, thus incurring an interruption in data access.
Resource: See the OneFS Upgrades - PowerScale Info page to get

documents and information regarding upgrades.

Upgrade Pause and Resume
OneFS 8.2.0 enables the pausing and resuming of a OneFS upgrade. Pause and
resume are useful when the maintenance window ends. The upgrade can be
paused, and then resumed in a later window. The commands are isi upgrade
pause and isi upgrade resume.
Pausing is not immediate. Upgrade is in a pausing state until the current upgrading
node completes. Other nodes do not upgrade until the upgrade is resumed.
Pausing state can be viewed with isi upgrade view, or
isi_upgrade_status, or viewing the pause file data.

Support Upgrade Paths to OneFS 8.1 (OneFS 8.2)
Below are the supported upgrade paths to OneFS 8.1 and OneFS 8.2. Upgrades
from versions earlier than OneFS 8.0 are simultaneous. Upgrading from OneFS 8.0
to OneFS 8.1 can be a rolling or simultaneous upgrade.
Supported Upgrade Paths to OneFS 8.1 (OneFS 8.2)
OneFS 7.2.0.4 - OneFS 8.1 (OneFS 8.2)
OneFS 7.2.0.2 - OneFS 8.1 (OneFS 8.2)

OneFS 8.0 - OneFS 8.1 (OneFS 8.2)
Resource: PowerScale Support and Compatibility Guide

Patches and Firmware
A standard part in each node installation or change activity is to bring the node up
to a minimum level. If required or requested to correct any significant issues,
OneFS patches can be applied. For the nodes, it includes bringing the node
firmware and drive firmware up to the latest version.
More information10.
Patches
A patch is a software update that addresses known issues before those updates
are incorporated into a maintenance release (MR)11.
10 For OneFS versions (OneFS 7.1.1 and above), it may include installing the drive
support package (DSP) to automate and simplify drive firmware updates. For all
drives to be on the same firmware version within each node. If possible, all nodes
should use the same firmware versions. When nodes run the latest version and all
drives are on the same version, customers experience fewer issues and there is a
reduction in future downtime or node outages.
11 To emphasize the importance, let us take an environment running many NFSv2

clients. If you failed to read the release notes stating NFSv2 was no longer
supported in OneFS 7.2, after upgrading to the new version, many NFSv2 clients
would no longer function. You must immediately determine and implement a
resolution to get those clients up and running again. The information in the release
notes would have helped you prepare for this change in advance.

The isi upgrade patches command syntax.
There are two types of patches, standard patch and rollup patch.
• A standard patch addresses one or more known issues for a major, minor, or
MR release of OneFS. Some patches contain minor enhancements or
additional logging functionality that can help Dell EMC Technical Support
troubleshoot issues with the cluster.
• Rollup patches address multiple issues that are related to one component of
OneFS functionality, such as SMB. It might also contain fixes from previous,
standard patches that addressed issues that are related to that component.
Firmware
Firmware is the software code that makes hardware components12 contained within
the node work. Updates are used to manage the code versions13 applied to each of
12Included are components such as the drives, the motherboard bios, the disk
controller, the InfiniBand adapter and the network adapters. The firmware is stored
on, and runs inside, the individual hardware components.

the hardware components. Firmware updates are performed across the cluster to
standardize all node components on the same version to eliminate potential
incompatibility issues and simplify support.
The isi devices drive firmware command to view and update firmware.
Firmware updates should be performed as part of a regular cluster maintenance

process. This applies equally to the node firmware and to the firmware of the
various node components.
More Information14.
13Code versions are updated to reflect code fixes or code enhancements for
additional stability.
14 Firmware updates are recommended as part of the process for new cluster
installations. The commands and process used to perform firmware updates are
different from the commands and process used for upgrades. When upgrading

Automatic Replacement Recognition
Disable to add
drives manually
Enabled by default
The graphic shows the WebUI Cluster management, Automatic Replacement Recognition page.
When replacing a drive in a node, OneFS automatically formats the drive, adds it to
the cluster, and updates the drive firmware. The new drive firmware matches the
current drive support package that is installed on the cluster. The drive firmware is
not updated for the entire cluster, only for the new drive. If you prefer to format and
add drives manually, disable Automatic Replacement Recognition.
firmware, each node is updated individually and is automatically restarted if needed

when the update is complete. Node firmware updates will require a reboot, but
drive firmware packages do not require a reboot

isi_upgrade_helper
The isi_upgrade_helper has two functions. First, it analyzes cluster

configuration and recommends a set of nodes for a simultaneous firmware
upgrade. Second, it gathers cluster configuration to assist with the identification of
features that are affected by upgrading firmware on a subset of nodes.
The isi_upgrade_helper command accepts three display options, default, -

-summary, and --verbose. The --include and --exclude options serve an
identical purpose to the upgrade framework arguments of the same name.

isi_upgrade_helper Default
The graphic shows the output of the isi_upgrade_helper command with no

options. The output shows three upgrade options. Use option 2 for clusters with
customer data. Use option 3 for clusters without customer data. Gen 6 nodes
without redundant power are not part of recommendation.
The isi_upgrade_helper --summary command extends the default helper

output by adding a cluster configuration table that is associated with each node.
Using isi_upgrade_helper --verbose extends the --summary option,
displaying several categories of cluster configuration that may affect node selection
for simultaneous firmware upgrade.
If a node fails after the initial isi_upgrade_helper, rerun

isi_upgrade_helper to get a revised recommended upgrade list. Failed nodes
are not in the upgrade list.
isi_upgrade_helper
1 - Rolling
2 - Simultaneous - minimize DU - node

lists avoid node peers and max of 1
node per disk pool
3 - Simultaneous - avoid DL - no node

pairs

Release Notes
Release notes contain installation instructions for drive and node firmware
upgrades and patches. Reading them carefully is an essential step in determining
whether your business benefits from the new features and functionality 15 of a new
OneFS version.
The release notes help you determine if the upgrade has an impact and if so,
provide a solution if needed. The contents of the release notes are similar across
releases - they provide release and upgrade information, new features,
modifications and enhancements, resolved issues, known issues and installation
instructions.
15 To emphasize the importance, let us take an environment running many NFSv2

clients. If you failed to read the release notes indicating that NFSv2 was no longer
supported in OneFS 7.2, after the upgrade to the new version, many NFSv2 clients
would no longer function. You must immediately determine and implement a
resolution to get those clients up and running again. The information in the release
notes would have helped you prepare for this change in advance.

Shown are the OneFS 8.2.0 Release Notes.
Resource: Isilon OneFS 8.2.0 Release Notes

Course Summary
Course Summary

Course Summary
Course Summary
Now that you have completed this course, you should be able to:
→ Create a new cluster.
→ Join a node to an existing cluster.
→ Complete a configuration.
→ Complete other configuration options.


PowerScale+Implementation+ +Participant+Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PowerScale+Implementation+ +Participant+Guide

Uploaded by

Copyright:

Available Formats

POWERSCALE

PowerScale Implementation ..................................................................................... 1

Creating a New Cluster .............................................................................................. 6

Joining Nodes to Existing Cluster .......................................................................... 12

Completing Initial Configuration............................................................................. 22

Other Configuration Options .................................................................................. 26

Page ii © Copyright 2020 Dell Inc.

Course Summary ..................................................................................................... 52

© Copyright 2020 Dell Inc. Page iii

© Copyright 2020 Dell Inc. Page 1

Rebranding - Isilon is now PowerScale

Important: In mid-2020 Isilon launched a new hardware platform, the

Page 2 © Copyright 2020 Dell Inc.

PowerScale Solutions Certification Journey Map

A. PowerScale Advanced Administration (C, VC)

B. PowerScale Advanced Disaster Recovery (C, VC)

(Knowledge and Experience based Exam)

Implementation Specialist, PowerScale Technology Architect Specialist, Platform Engineer, PowerScale

A. PowerScale Concepts (ODC)

Information Storage and Management

Information Storage and Management (C, VC, ODC)

(VC) - Virtual Classroom

(ODC) - On Demand Course

For more information, visit: http://dell.com/certification

© Copyright 2020 Dell Inc. Page 3

Page 4 © Copyright 2020 Dell Inc.

After completion of this course, you will be able to:

© Copyright 2020 Dell Inc. Page 5

Creating a New Cluster

Page 6 © Copyright 2020 Dell Inc.

After completing this module, you will be able to:

© Copyright 2020 Dell Inc. Page 7

The typical PowerScale installation consists of three phases: Planning,

3: Phase three of the project consists of documenting the installation, providing a

Page 8 © Copyright 2020 Dell Inc.

Pre-Engagement Questionnaire (PEQ)

Double-click images for enlarged view.

© Copyright 2020 Dell Inc. Page 9

Connecting Via Serial Port

Configure the terminal emulator utility to use the following settings:

Page 10 © Copyright 2020 Dell Inc.

This video demonstrates creating a new cluster.

The web version of this content contains a movie.

© Copyright 2020 Dell Inc. Page 11

Joining Nodes to Existing Cluster

Page 12 © Copyright 2020 Dell Inc.

After completing this module, you will be able to:

© Copyright 2020 Dell Inc. Page 13

Verifying Version and Adding a Node

The web version of this content contains a movie.

Page 14 © Copyright 2020 Dell Inc.

column. Once it is finished working, let us navigate back to Dashboard, Cluster

isi devices node add <serial-number> command is used to join an

© Copyright 2020 Dell Inc. Page 15

SmartFail: Remove a Node from Cluster

The web version of this content contains a movie.

The SmartFail function removes a node from the cluster.

• SmartFail manually removes2 one node at a time from the cluster.

Page 16 © Copyright 2020 Dell Inc.

• isi devices node stopfail command is used to discontinue the smartfail

© Copyright 2020 Dell Inc. Page 17

Reformatting a node is the quickest way to return a node to an unconfigured state.

The web version of this content contains a movie.

The video shows the reboot option.