Here is Your Customized Document

Your Configuration is:

SP - Replace a storage processor Ultraflex I/O module

Model - VNX5700
Storage Type - Unified (NAS and SAN)
Document ID - 1439937016275

Reporting Problems

To send comments or report errors regarding this document,

please email: [email protected].
For Issues not related to this document, contact your service provider.
Refer to Document ID:
1439937016275
Content Creation Date August 18, 2015
EMC® VNX® Series

Replacing a storage processor Ultraflex I/O

module

August, 2015

This document describes how to replace a storage processor I/O module in the EMC®
VNX5700.

WARNING

Never remove a powered on I/O module, whether faulted or functional, from its slot in the
storage processor. You must first prepare the storage processor for the removal of the I/O
module. Removing a powered on I/O module initiates an immediate reboot of the storage
processor, causing data unavailability and likely data loss. During this procedure you will
be directed to power down the SP associated with the broken component. Take the
appropriate steps to ensure that your system can sustain the power down on one of the
two system storage processors (fault alerts, CallHomes, I/O failover, etc). This procedure
will guide you through only the necessary steps to power down the SP.
Note

Always replace an I/O module with one that is the exact same type. Verify the type
by reading the label on the I/O module handle.

Topics include:
l Before you begin............................................................................................. 3
l Preparing the system.......................................................................................5
l Replacing the faulted hardware component.....................................................7
l Finishing up.................................................................................................. 12
Before you begin
Before you begin this maintenance activity, refer to the component handling instructions.
You should also review the entire procedure prior to beginning any maintenance activity
on the system.

Handling replaceable units

This section describes the precautions that you must take and the general procedures
that you must follow when removing, installing, and storing any replaceable unit. The
procedures in this section apply to replaceable unit handling during hardware upgrades
as well as during general replacement.

Avoiding electrostatic discharge (ESD) damage

When replacing or installing hardware units, you can inadvertently damage the sensitive
electronic circuits in the equipment by simply touching them. Electrostatic charge that
has accumulated on your body discharges through the circuits.
Read and understand the following instructions:
l Provide enough room to work on the equipment.
l Clear the work site of any unnecessary materials or materials that naturally build up
electrostatic charge, such as foam packaging, foam cups, cellophane wrappers, and
similar items.
l Do not remove replacement or upgrade units from their antistatic packaging until you
are ready to install them.
l Gather the ESD kit and all other materials before servicing any units.
l After servicing begins, avoid moving away from the work site; otherwise, you might
build up an electrostatic charge.
l Use the ESD kit when handling any units.
l If an emergency arises and the ESD kit is not available, follow the procedures in
Emergency procedures (without an ESD kit) on page 3
l Use the ESD wristband that is supplied with the server.
l To use it, attach the clip of the ESD wristband (strap) to any bare (unpainted) metal
on the cabinet or enclosure, and then put the wristband around your wrist with the
metal button against your skin.

Emergency procedures (without an ESD kit)

In an emergency when an ESD kit is not available, use the following procedures to reduce
the possibility of an electrostatic discharge by ensuring that your body and the
subassembly are at the same electrostatic potential.

CAUTION

These procedures are not a substitute for the use of an ESD kit. Follow them only in the
event of an emergency.
l Before touching any unit, touch a bare (unpainted) metal surface of the enclosure.
l Before removing any unit from its antistatic bag, place one hand firmly on a bare
metal surface of the enclosure, and at the same time, pick up the unit while it is still
sealed in the antistatic bag. Once you have done this, do not move around the room
or touch other furnishings, personnel, or surfaces until you have installed the unit
l When you remove a unit from the antistatic bag, avoid touching any electronic
components and circuits on it.

Replacing a storage processor Ultraflex I/O module 3

 l If you must move around the room or touch other surfaces before installing a unit,
first place the unit back in the antistatic bag. When you are ready again to install the
unit, repeat these procedures.

Removing, installing, or storing CRUs

Use the following precautions when removing, handling, or storing CRUs:
l Do not remove a faulty CRU from the cabinet until you have the replacement
available.
l Handle a CRU only when wearing an ESD wristband (strap).
n Attach the clip of the ESD wristband to the ESD bracket or bare metal on a cabinet
enclosure.
n Wrap the ESD wristband around your wrist with the metal button against your
skin.
l Handle a CRU gently. A sudden jar, drop, or vibration can permanently damage some
CRUs.
l Never use excessive force to remove or install a CRU. Take time to read the
instructions carefully.

CAUTION

For a module that must be installed into a slot in an enclosure, examine the rear
connectors on the module for any damage before attempting its installation.
l Store a CRU in the antistatic bag and the specially designed shipping container in
which you received it. Use the antistatic bag and special shipping container when you
need to return the CRU.

CAUTION

A sudden jar, drop, or even a moderate vibration can permanently damage some
sensitive FRUs.

CAUTION

Some CRUs have the majority of their weight in the rear of the component. Ensure that
the back end of the CRU is supported while installing or removing it. Dropping a CRU
could result in personal injury or damage to the equipment.

Summary of tasks for replacing an I/O module

To replace an I/O module in a storage processor you must complete the tasks below in
the order in which they appear. This document provides instructions for completing each
task.

Note

Do not completely remove assembly- or enclosure-level hardware from the system or rack
unless specifically directed. Figures in this procedure depict hardware completely
removed to increase their clarity.

For additional details on the locations of orderable parts, and their part number labels,
refer to the parts location guide for your specific VNX model. EMC posts and maintains
parts location guides online on the Related Documents section of https://
mydocs.emc.com/VNX. On the Related Documents page, under the VNX Hardware Parts
heading, click on the desired guide.

4
 Replacing a storage processor Ultraflex I/O module

1. Disabling notifications.
2. Identify the faulted I/O module.
3. Shut down the SP assembly with the faulted I/O module.
4. Remove the faulted I/O module.
5. Install the replacement I/O module.
6. Reboot the SP assembly with the replacement I/O module.
7. Verify the operation of the replacement I/O module.
8. Restoring trespassed LUNs.
9. Checking system for faulted hardware.
10. Enabling notifications.
11. Return failed part.

Preparing the system

Take the following actions to prepare the system for this maintenance activity.

Disabling Connect Home and email notifications

Use the following steps to disable Connect Home and email notification.

Opening a serial connection with CS 0

Procedure
1. At the rear of the cabinet, connect the null modem cable from the serial port on the
management console to the serial port on the primary Control Station (Figure 1 on
page 5).
Figure 1 Control station serial connection

Serial port

2. Open a terminal emulation program (For example, HyperTerminal or PuTTy) and use
the following settings to create a serial connection to CS 0:
l Bits per second: 19200
l Data bits: 8
l Parity: None
l Stop bits: 1
l Flow control: None
l Emulation: Auto Detect
l Telnet terminal ID: ANSI

Preparing the system 5

 3. Login as nasadmin.
4. Become the root user:
$ su root
Password:

Disable Connect Home and email notification

Use the open console session to disable Connect Home:
Procedure
1. As the root user, disable Connect Home:
# /nas/sbin/nas_connecthome -service stop

2. Disable the email notification service:

# /nas/bin/nas_emailuser -modify -enabled no

3. Verify that the email notification service has stopped (is not enabled):
# /nas/bin/nas_emailuser -info

Results
Connect Home and email notifications are now disabled. After completing the procedure,
be sure to enable Connect Home and email notifications.

Checking the system for faulted hardware

Follow the steps below to verify the status of the system's hardware components.

Diagnosing faulted storage system hardware components

Use this procedure to log in to EMC® Unisphere™ and check for any faulted hardware
components in the storage system.
Procedure
1. Start Unisphere for the storage system by entering the primary Control Station IP
address in a browser window.
2. In the system drop-down list on the menu bar, select the system in which you may
have a faulted hardware component.
3. Select System > Hardware > Storage Hardware.
4. Check for any faulted storage hardware components.

6
 Replacing a storage processor Ultraflex I/O module

Locate a storage processor I/O module

Locate the faulted I/O module using the descriptions that follow.
Locations of the I/O modules in the SPE
Figure 2 Location and naming of SPE I/O modules
B-side I/O modules A-side I/O modules

33

33
3
3

3
3

22

22
2
2

2
2

11

11

1
1

1
1

00

00

0
0

0
0

0
SP B SP A

The storage processor enclosure (SPE) in your VNX system contains ten I/O module slots,
five I/O module slots per storage processor.
The System > Hardware > Storage Hardware page in Unisphere refers to the I/O module
slots on the A-side of the DPE as I/O module Slot A0 through Slot A4, and the I/O module
slots on the B-side of the DPE as I/O module Slot B0 through Slot B4.

Running the Verify Storage System wizard

Use the Verify Storage System wizard to perform a health check on the storage system.
Procedure
1. Start the Unisphere Service Manager by doing either one of the following:
l Click the Unisphere Service Manager icon on your desktop
l Select Start > All Programs or Start > Programs, then select EMC > Unisphere
Service Manager > Unisphere Service Manager
l From the System screen in Unisphere, click Launch USM in the right-hand taskbar
located under Service Tasks

2. Log in to your system.

3. From the System screen, select Diagnostics > Verify Storage System to run the storage
system health check wizard.

Replacing the faulted hardware component

Take the following actions to remove the faulted hardware part and install the
replacement hardware part into the system.

Power down the Storage Processor

Before you power down the storage processor, EMC requires that you have properly
prepared the failover software for target SP power down or trespass the LUNs off the
target SP at this time.
1. Using the open terminal emulator session, determine the current VNX OE for Block
version operating on the storage array.

Replacing the faulted hardware component 7

 # /nas/sbin/naviseccli -h <SPA_IP_address> -user <name> -password
<password> -scope 0 getagent
2. Depending on the system configuration, complete the tasks below to power down the
Storage Processor. If the VNX OE for Block version is:
l R31.008 or lower, you are required to complete the following tasks:
n Disable the system write cache on page 8
n Shut down power to the VNX SP on page 8
l R31.011 or higher, continue to Shut down power to the VNX SP on page 8.

Disable the system write cache

This task is required only if you determined the storage array is operating with VNX OE for
Block version R31.008 or lower.
To disable the system write cache:
Procedure
1. Display and record the current write cache settings:
# /nas/sbin/naviseccli -h <IP_address> -user <name> -password
<password> -scope 0 getcache |grep "Cache Size"

2. Disable and zero out the system write cache:

# /nas/sbin/naviseccli -h <IP_address> -user <name> -password
<password> -scope 0 setcache -wsz 0 -wc 0

Shut down power to the VNX SP

Complete the following steps to shut down power to the SP related to the faulted
component:
Procedure
1. Shut down power to the Storage Processor to which the faulted component is related:

Note

This command is intended to shutdown the SP related to the faulted component. Use
the IP address of the peer SP not related to the faulted component.
For example, if the faulted component was in SPA, use the IP address of SPB when
issuing the shutdownpeerSP command.

# /nas/sbin/naviseccli -h <SP_IP_address> -user <name> -password

<password> -scope 0 shutdownpeerSP

2. Verify that the SP related to the faulted component has been shut down by testing the
IP address of the powered down Storage Processor:
# ping <SP_IP_address>

Removing an I/O module

Note

A faulted I/O module displays an amber LED on its handle.

8
 Replacing a storage processor Ultraflex I/O module

Procedure
1. Remove the cables connected to the I/O module.
If the cables are not already labeled, label them clearly for reinstallation later.
2. Pull the trigger mechanism on the I/O module handle to release it (Figure 3 on page
9).
3. Gently pull the module from the chassis (Figure 3 on page 9).
Figure 3 Removing an I/O module

1
0
10/100/1000
3
2
1
0

1
010/100/1000
CL3956

Unpacking a part
Procedure
1. Wear ESD gloves or attach an ESD wristband to your wrist and the enclosure in which
you are installing the part.
2. Unpack the part and place it on a static-free surface.
3. If the part is a replacement for a faulted part, save the packing material to return the
faulted part.

Installing an I/O module

Note

You must install a replacement I/O module in the same slot from which you removed the
faulted I/O module and a new I/O module in the same slot from which you removed the
I/O filler module.

Procedure
1. Align the module with the empty slot (Figure 4 on page 10).
2. When the I/O module appears seated, push and release the small button on the
handle (Figure 4 on page 10).

Unpacking a part 9
 l If the button remains in, the module is fully seated .
l If the button springs back, gently push the module further into the chassis, then
push it again.
l If the button still does not rest flush with its handle, remove the module and
repeat steps 1 and 2.
Figure 4 Installing an I/O module

1
0
10/100/1000
3
2
1
0

1
0
10/100/1000
CL3956

3. If the I/O module you installed is a replacement for a faulted I/O module, attach the
cables to the replacement I/O module in the exact same locations that they were
attached in the faulted I/O module.

Power up the Storage Processor

After completing the replacement of the faulted SP component, power up the SP.
Depending on the system configuration, complete the tasks below to power up the
Storage Processor. If the system's VNX OE for Block version is:
l R31.008 or lower,
1. Restore power to the VNX SP on page 10
2. Verify SP LEDs on page 11
3. Enable the system write cache on page 11
l R31.011 or higher,
1. Restore power to the VNX SP on page 10
2. Verify SP LEDs on page 11. Then go to Verifying the operation of a new or
replacement part with Unisphere on page 12, you do not need to manage the
system's write cache.

Restore power to the VNX SP

To restore power to the powered down SP:

10
 Replacing a storage processor Ultraflex I/O module

Procedure
1. Run the following naviseccli command to restore power to the SP:
# /nas/sbin/naviseccli -h <IP address> -user <name> -password
<password> -scope 0 rebootpeerSP

Note

This command will reboot the SP you powered down earlier. Use the IP address of the
SP not currently powered down.

2. Verify that power has been restored to the SP.

Verify SP LEDs
Before you continue, verify that the Storage Processor fault LED is unlit and its power LED
is steady green. (Figure 5 on page 11)
Figure 5 SP power and fault LEDs
CPU fault LED

CPU power LED CPU unsafe to

remove LED

AC AC AC AC

CNS-001669

It will take approximately 10 minutes for the SP to boot completely. Do not continue until
the SP fault LED is off and the power LED is green.

Note

After verifying the power up of the SP, restore the LUNs, which were previously
trespassed to the peer SP, back to the target SP that underwent the maintenance activity.

Enable the system write cache

This task is required only if you determined the storage array is operating with VNX OE for
Block version R31.008 or lower and you disabled the write cache earlier in this
procedure.
To re-apply the write cache settings and enable write cache:
Procedure
1. Using the open terminal emulator l session, set the write cache size to match the
previous setting determined in Disable the system write cache on page 8:
# /nas/sbin/naviseccli -h <IP_address> -user <name> -password
<password> -scope 0 setcache -wsz <write_cache_size>

Power up the Storage Processor 11

 2. Enable the write cache:
# /nas/sbin/naviseccli -h <IP_address> -user <name> -password
<password> -scope 0 setcache -wc 1

Restoring trespassed LUNs

When a backend FRU/CRU component fails, the LUNs assigned to that storage processor
trespass to the other storage processor. This keeps the data available to the clients. After
replacing the failed backend FRU/CRU component you need to restore the LUNs to their
original storage processor.
Procedure
l Using Unisphere, do the following:
a. In Unisphere, use the drop-down list at the top left of the Dashboard to select the
system.
b. Select Storage.
c. On the right side pane under File Storage, select Restore LUN Ownership for File.
d. Trespass failed over LUNs as necessary.
l Using the CLI, do the following:
a. Log in to the primary Control Station as nasadmin and change to the root user:
$ su root

b. Determine the storage-system serial number (storage-system ID):

# /nas/bin/nas_storage -list

c. Restore the LUNs to the correct SP:

# /nas/bin/nas_storage –failback <storage-system-id>
For example:

# /nas/bin/nas_storage -failback APM00070300923

id = 1
serial_number = APM00070300923
name = APM00070300923
acl = 0
done

Finishing up
After completing the maintenance activity, follow the tasks in this section to return the
system to production ready.

Verifying the operation of a new or replacement part with Unisphere

Procedure
1. Start EMC® Unisphere for the storage system by entering the IP address in a browser
window.
2. In the system drop-down list on the menu bar, select the system in which you
installed or replaced the part.

12
 Replacing a storage processor Ultraflex I/O module

3. Select System > Hardware > Storage Hardware.

4. Expand the enclosure in which you installed or replaced the part, and navigate to the
part.
5. Verify that the part is in the enclosure and that it is not faulted.

Checking the system for faulted hardware

Follow the steps below to verify the status of the system's hardware components.

Checking system status

From the open terminal emulation session, view the system state:
# /nas/bin/nas_checkup
The nas_checkup command runs health checks on the File components as well as the
storage system. If the output of the nas_checkup command indicates any Errors (for
example, if a check does not pass), correct the error, following the instructions provided,
and then re-run the command before continuing.

Note

It is not required that you correct the Warnings or Information notifications at this time,
though it is recommended that these notifications be reviewed.

Running the Verify Storage System wizard

Use the Verify Storage System wizard to perform a health check on the storage system.
Procedure
1. Start the Unisphere Service Manager by doing either one of the following:
l Click the Unisphere Service Manager icon on your desktop
l Select Start > All Programs or Start > Programs, then select EMC > Unisphere
Service Manager > Unisphere Service Manager
l From the System screen in Unisphere, click Launch USM in the right-hand taskbar
located under Service Tasks

2. Log in to your system.

3. From the System screen, select Diagnostics > Verify Storage System to run the storage
system health check wizard.

Enabling ConnectHome and email notifications

Results
Use the procedure in the section that follows to enable ConnectHome and email
notification.

Re-enable Connect Home and email notification

Use the open console session with the primary CS to re-enable Connect Home and email
notification:
Procedure
1. As the root user, clear any existing Connect Home files and enable Connect Home:
# /nas/sbin/nas_connecthome -service start -clear

Checking the system for faulted hardware 13

 2. From the Connect Home configuration, determine the connections that are enabled:
# /nas/sbin/nas_connecthome -i

3. Verify that Connect Home works with the /nas/sbin/nas_connecthome -test

<connection_name> command for each enabled connection.
For example:

# /nas/sbin/nas_connecthome -t -email_1

or

# /nas/sbin/nas_connecthome -t -email_2

or

# /nas/sbin/nas_connecthome -t -https

or

# /nas/sbin/nas_connecthome -t -modem_1
4. Verify email notifications is configured:
# /nas/bin/nas_emailuser -info
If the Recipient Address(es) field is empty, email notifications has not been
configured and does not need to be enabled. If you want to configure email
notifications, use the /nas/bin/nas_emailuser command or Unisphere to
configure it.
If the Recipient Address(es) field is populated, email notifications was enabled. Re-
enable email notifications:

a. Enable email notifications:

# /nas/bin/nas_emailuser -modify -enabled yes

b. Verify that email notification works:

# /nas/bin/nas_emailuser -info

c. Test the configuration and verify that the configured Recipient Address(es)
received the test email:
# /nas/bin/nas_emailuser -test

Returning the failed part

Ship the failed part to your service provider as described in the instructions that were
included with the replacement part.

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.
Please send your opinion of this document to:

[email protected]

14
 Replacing a storage processor Ultraflex I/O module

Copyright © 2011-2015 EMC Corporation . All rights reserved. Published in USA.

Published August, 2015

EMC 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. EMC Corporation 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 EMC software described in this publication requires an applicable software
license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

Returning the failed part 15