Node Upgrade Guide: Isilon NL400
Node Upgrade Guide: Isilon NL400
Isilon
NL400
Upgrade a node
May 2017
l Upgrading nodes.....................................................................................................2
l Preparing for the upgrade.......................................................................................3
l Performing the upgrade......................................................................................... 11
l Reviewing the upgrade......................................................................................... 26
l Roll back a failed upgrade..................................................................................... 28
l Where to go for support....................................................................................... 29
Node Upgrade Guide
Upgrading nodes
You can upgrade the drives, memory, and NICs in most EMC Isilon nodes.
The process to upgrade nodes in a cluster consists of three stages.
Preparing for the upgrade
An upgrade procedure requires significant planning and preparation. Steps in the
process, such as smartfailing drives from multiple nodes, can take several weeks to
complete. Before the actual maintenance window, you must also obtain a hardware
upgrade package for each node you plan to upgrade. It is important that you
understand this procedure and communicate its full impact to everyone who might be
affected.
Performing the upgrade
After you prepare the cluster for work, you must upgrade the nodes during the agreed
upon maintenance window. A maintenance window is necessary, because full cluster
availability during the upgrade procedure is not guaranteed. You must adhere to all
EMC Isilon safety and quality guidelines as you perform each step of the procedures
for removing and installing node components.
Reviewing the upgrade
After nodes are upgraded, you must review the status of the cluster and confirm that
all configuration changes were successful and that all new storage pools are
established and healthy.
Downgrading a node
You can downgrade configure-to-order (CTO) components in a node.
The procedure to perform a downgrade is exactly the same as the procedure to
perform an upgrade. Follow the steps to prepare, perform, and review all changes to
the node configuration.
However, if you are on the sudoers list, the following command succeeds:
Compliance mode commands that require changes beyond the sudo prefix are noted
in the procedure steps.
For more information on the sudo program and compliance mode commands, see the
OneFS CLI Administration Guide.
3. Request a download link for the hardware upgrade package from the Isilon
Verification Team by sending the information you gathered in previous steps to
[email protected].
Requests for download links can take approximately 7 business days. These
requests must be made before you begin the upgrade process.
Note
EMC Isilon Technical Support cannot help with the creation or correction of
hardware upgrade packages, or changes to receipts. For these requests,
contact the Isilon Verification Team.
3. Place the hardware upgrade package on the cluster through a network drop, or
by asking someone at the cluster site to place the package for you. If neither of
these options is available to you, contact Isilon Technical Support for
assistance.
If the node does not perform as expected, contact Isilon Technical Support.
5. Repeat these steps for each node that you are upgrading.
Note
Your Isilon Account Team will generate an individual upgrade package for each
node you are upgrading. Make sure to install the correct upgrade package on
each node.
cd /var/crash/cto/hwPackages/IsiHW_Package_<order-number>_
<node-serial-number>_<date-time-stamp>
./isi_cto_upgrade --overview
Note
Note
You can execute this command in advance of the upgrade engagement. This
command will not make changes to the node.
The command output will confirm verification of the package integrity, node
configure-to-order (CTO) capability, chassis VPD, and the node serial number.
The output will also display the receipt that was generated before the upgrade
next to the receipt that was generated after the upgrade.
Note
You might see some noncritical error messages as part of the output. If you are
not sure whether it is safe to continue, contact EMC Isilon Technical Support.
3. Compare the command output of the receipt that was generated before the
upgrade to the command output of the receipt that was generated after the
upgrade.
The content of the receipt will be similar to the following example:
<receipt
receiptFileName="30301230_SX4001013160081.xml"
receiptFormatVersion="1.2" date="2014-01-23T01:40:03Z">
<bom>
<sbb qty="1" desc="SBB, BASE, DDR, X400" part="610-0005-03"/>
<sbb qty="1" desc="SBB, 3.5" 66TB HDD / 1.2TB SSD EMLC"
part="611-0075-02"/>
<sbb qty="1" desc="SBB, Memory, 48GB DDR3, 12x4G"
part="612-0006-01"/>
<sbb qty="1" desc="SBB, 10GbE, Dual-port, SFP+, without Optics"
part="613-0002-01"/>
</bom>
</receipt>
Results
If the receipt from before the upgrade is not consistent with the receipt from after the
upgrade, or if neither are consistent with the defined upgrade path and the hardware
order, contact your Account Team and request a corrected upgrade package.
If you have issues that are not related to the receipt, contact EMC Isilon Technical
Support.
If the nodes that you are adding to the cluster have the hardware configuration that
the existing nodes will have following the upgrade, add the new nodes to the cluster
only after you upgrade the existing nodes and confirm that the cluster is healthy.
Following these guidelines will prevent OneFS from creating new node pools before
the hardware upgrade is completed, which will reduce the complexity of the
environment.
Gather logs
Before you begin any maintenance on a cluster, gather cluster logs.
You must collect cluster logs before all maintenance procedures. Cluster logs provide
snapshots of the cluster, which you can review to make sure that maintenance is
successful.
Procedure
1. Open a secure shell (SSH) connection to any node in the cluster and log in.
2. Gather cluster logs by running the following command:
isi_gather_info
cd /var/crash/cto/hwPackages/IsiHW_Package_<order-number>_
<node-serial-number>_<date-time-stamp>
./isi_cto_upgrade --overview
Note
3. Confirm that the current amount of installed RAM matches the hardware
upgrade receipt, and that all DIMMs are healthy.
4. Confirm that the installed drives match the hardware upgrade receipt, and that
there are no failed drives.
5. Confirm that the installed network interfaces match the hardware upgrade
receipt, and that all NICs are healthy.
Note
You should not arrive for a drive upgrade engagement until all the drives that you are
going to upgrade, in all nodes, are smartfailed.
Before you smartfail multiple drives, check the amount of free space available on the
cluster. Follow best practices related to available space and protection levels on the
cluster.
Refer to the following documentation for more information:
l Best practice guide for maintaining enough free space on Isilon clusters and pools
l How to determine if an isilon cluster is in a window of risk for data loss
If you are upgrading to SSDs, smartfail drives in the lowest drive bay numbers. For
example, if you are adding two SSDs to each node, smartfail the drives in bays one and
two.
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
17 18 19 20
21 22 23 24
GHE-000066
25 26 27 28
29 30 31 32
33 34 35 36
GHE-000067
Smartfail all the drives that will be upgraded, one node at a time. Wait for the smartfail
process to complete on one node, then proceed to the next node.
Procedure
1. Open a secure shell (SSH) connection to the node that contains the drive you
want to remove. Type the command:
ssh <cluster-name>-<node-number>
2. Confirm the node number and bay number of the drive you want to remove.
Depending on your version of OneFS, type one of the following commands:
OneFS 8.0 or later
isi devices drive list
Note
Note the node number and bay number of the drive you want to remove. If the
drive you need to remove has already been smartfailed automatically, you can
skip the next step. A smartfailed drive will display a status of REPLACE or, if the
node was restarted after the smartfail, a status of EMPTY. A smartfailed SED
drive might display a status of ERASE. This status also indicates the node is
ready to be replaced.
3. Using the node number and bay number of the drive, smartfail the drive by
typing one of the following commands:
OneFS 8.0 or later
isi devices drive smartfail <bay-number> --node-lnn <node-
number>
Earlier than OneFS 8.0
isi devices -a smartfail -d <node-number>:bay<bay-number>
If the drive does not respond to the smartfail command, do not remove it from
the node. Contact Isilon Technical Support.
CAUTION
Do not replace the drive until you have confirmed that the smartfail
process is complete.
Results
Repeat this procedure for every drive, in every node that you are upgrading.
The length of time that it takes for the smartfail process to complete depends on the
size of the cluster, drive capacity, and the cluster workflow.
Note
See the Considerations for installing the latest drive support package section in
order to select the appropriate variant of the package. If you are unable to
download the package, contact EMC Isilon Technical Support for assistance.
3. Open a secure shell (SSH) connection to any node in the cluster and log in.
4. Create or check for the availability of the directory structure /ifs/data/
Isilon_Support/dsp.
5. Copy the downloaded file to the dsp directory through SCP, FTP, SMB, NFS,
or any other supported data-access protocols.
6. Unpack the file by running the tar command.
For example, based on the variant selected for the drive support package,
unpack the package by running one of the following commands:
For example, based on the variant selected for the drive support package, install
the package by running one of the following commands:
isi_dsp_install Drive_Support_<version>.tar
isi_dsp_install Drive_Support_<version>_No_SSD.tar
Note
l You must run the isi_dsp_install command to install the drive support
package. Do not use the isi pkg command.
l Running isi_dsp_install will install the drive support package on the
entire cluster.
l The installation process takes care of installing all the necessary files from
the drive support package followed by the uninstallation of the package. You
do not need to delete the package after its installation or prior to installing a
later version.
Note
Although rebooting the cluster can help avoid certain issues, taking this step might not
be possible in your environment. And, although this step is recommended, it is
optional.
Procedure
1. Reboot the cluster according to EMC Isilon best practices for restarting entire
clusters.
CAUTION
Perform the upgrade procedure on only one node at a time. Working on multiple
nodes in parallel might lower the protection level of the cluster, put data at risk,
and lead to the interruption of client workflows.
cd /var/crash/cto/hwPackages/IsiHW_Package_<order-number>_
<node-serial-number>_<date-time-stamp>
./isi_cto_upgrade --pre
Note
Success
...
Note
The upgrade script displays a list of missing and found components. The missing
component list contains the new parts that you will add to the node. The found
component list contains the parts that you will remove. You must accept this
message to continue. You might see non-critical error messages as part of the
output. If you do not feel that it is safe to continue, contact EMC Isilon
Technical Support.
3. Once the pre-upgrade script concludes, you are prompted to power down the
node:
Upgrading a drive
If you are upgrading drives as part of an upgrade engagement, remove the smartfailed
drives.
Remove the old drives only. Do not install the new drives until you have powered the
node back up.
1. Front panel
Upgrading a drive 13
Node Upgrade Guide
2. To access drives at the back of the node, remove the rear EMI shield.
There is a vertical handle at each end of the shield. To remove the shield, press
the handles toward the center of the shield while pulling away from the node.
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
17 18 19 20
21 22 23 24
GHE-000066
25 26 27 28
29 30 31 32
33 34 35 36
GHE-000067
Procedure
1. To remove a drive, pull the locking handle on the drive toward you.
The drive releases from the node.
Note
DANGER
Slide the node out from the rack slowly. Do not extend the rails completely
until you confirm that the node is latched and safely secured to the rails.
WARNING
Procedure
1. Loosen the captive screw that secures the node top panel.
2. Slide the top panel toward the rear of the node, and then lift the top panel to
access the node interior.
2. Remove the cross bracket by pressing on the side of the node chassis where
the cross bracket is connected. Unhook the cross bracket from the chassis,
then lift straight up to unhook the other side of the bracket.
2. Raise the front end of the air baffle, unhook the tabs at the back end of the
baffle, and then lift the baffle out of the node.
Upgrading DIMMs
If you are upgrading DIMMs as part of an upgrade engagement, remove the old
DIMMs and replace them with the new DIMMs.
If you are installing a different amount of DIMMs than you are removing, make sure
that the new DIMMs are installed in the same color slots and in the same bank from
which the old DIMMs were removed.
CAUTION
If you are replacing a DIMM in slot P2 DIMM 3A or P2 DIMM 3B, remove the
network interface card (NIC) to allow enough space to remove the DIMM
without damaging the NIC.
1. DIMM
Note
Install the new DIMM in the empty slot that used to hold the old DIMM. A DIMM
that is installed in another open slot runs the risk of not being recognized by the
system.
Upgrading a NIC
If you are upgrading the NIC as part of an upgrade engagement, remove the NIC and
replace it with the new card.
WARNING
The cross bracket sits directly above the boot drives. Use caution when installing
the cross bracket so that the boot drives are not dislodged or damaged.
WARNING
The chassis intrusion switch can be damaged if the top panel is slid too far
back on the node.
2. Tighten the captive top panel screw to secure the top panel to the node.
WARNING
Slide the node slowly so you do not slam the node into the rack and damage
the node.
2. Reconnect the ethernet, InfiniBand, and power cables to the back of the node.
3. Secure the node to the rack cabinet.
4. Replace the node front panel.
Note
If errors are present following a reboot, do not continue. Contact EMC Isilon
Technical Support.
OneFS 8.0
isi devices drive add <bay-number> --node-lnn <node-number>
4. After the new drive has been installed, replace the front panel on the node by
aligning the panel with the front of the node and pressing the panel until it clicks
onto the node.
If you replaced a drive in the rear of the node, replace the EMI shield.
cd /var/crash/cto/hwPackages/IsiHW_Package_<order-number>_
<node-serial-number>_<date-time-stamp>
./isi_cto_upgrade --post
Note
2. To delete the upgrade package from a node, use the information in the name of
your hardware package type the following command:
isi pkg delete --forced_local IsiHW_Package_ <order-number> _
<node-serial-number> _ <date-time-stamp>
Note
Do not restart or power off nodes while drive firmware is being updated on the cluster.
Procedure
1. Open a secure shell (SSH) connection to any node in the cluster and log in.
2. Depending on your version of OneFS, run one of the following commands to
update the drive firmware for your cluster:
OneFS 8.0 or later
To update the drive firmware for your entire cluster, run the following
command:
isi devices drive firmware update start all --node-lnn
all
To update the drive firmware for a specific node only, run the following
command:
isi devices drive firmware update start all --node-lnn
<node-number>
OneFS 7.1.1 - OneFS 8.0
For OneFS versions between 7.1.1 - 8.0 you will need to run the following
command on each node that requires drive firmware:
isi devices -a fwupdate
CAUTION
You must wait for one node to finish updating before you initiate an update
on the next node. To confirm that a node has finished updating, run the
following command:
isi devices -d <node-number>
A drive that is still updating will display a status of FWUPDATE.
isi devices
isi devices
Note
After you upgrade all the nodes in a node pool, the nodes should become part of
a new pool. It is possible that the old node pool will remain visible with no nodes
in it. If you see this issue, contact EMC Isilon Technical Support for assistance.
6. Confirm that the receipt was installed by running the following command:
isi_inventory_tool --display --itemType=receipt
7. Verify and upload the as-built record by running the following command:
isi_cto_update --abr
Gather logs
After you complete maintenance on a cluster, gather cluster logs.
You must collect cluster logs after all maintenance. Cluster logs provide snapshots of
the cluster that you can review to make sure that maintenance is successful.
Procedure
1. Gather cluster logs by typing the command:
isi_gather_info
CAUTION
You can attempt to roll back an upgrade only if the upgrade package is still
installed. If you have already uninstalled the upgrade package, you cannot roll
back the upgrade.
Procedure
1. Change directory to the location of the upgrade package by running the
following command:
cd /var/crash/cto/hwPackages/IsiHW_Package_<order-number>_
<node-serial-number>_<date-time-stamp>
./isi_cto_upgrade --rollback
Note
At the end of the command output, you are prompted to power down the node.
Help with Online For questions specific to EMC Online Support registration or
Support access, email [email protected].
Isilon Info Hubs For the list of Isilon info hubs, see the page on the EMC Isilon
Community Network, EMC Isilon Community Network. Isilon info
hubs organize Isilon documentation, videos, blogs, and user-
contributed content into topic areas, making it easy to find
content about subjects that interest you.
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH
RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION
REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.