Here is Your Customized Document

Your Configuration is:

DME - Add a Data Mover (blade) Ultraflex I/O module

Model - VNX5300
Storage Type - VNX for File (NAS)
Document ID - 1487081732919

Reporting Problems

To send comments or report errors regarding this document,

please email: mydocs@emc.com.
For Issues not related to this document, contact your service provider.
Refer to Document ID:
1487081732919
Content Creation Date February 14, 2017
EMC VNX Series

Adding an I/O Module to a Data Mover

May, 2014

This procedure explains how to add EMC I/O modules to the Data Movers (DMs) in a
VNX5300 system. The resulting Data Mover I/O module configuration must be uniform
across each Data Mover in the system or failover group, therefore you must add the same
I/O module to each Data Mover in the system or the failover group.

CAUTION

Electrostatic discharge (ESD) can damage equipment and impair electrical circuitry.
Always follow ESD prevention procedures when removing and replacing I/O modules.

Note

This procedure uses the terms blade and Data Mover interchangeably to refer to the same
logical hardware component composed of a CPU module, power/cooling modules, and I/O
modules.

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.
l Before you begin........................................................................................................ 2
l Preparing your site for an upgrade..............................................................................6
l Installing the upgrade.............................................................................................. 13
l Finishing up............................................................................................................. 20
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 2
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

2
 Adding an I/O Module to a Data Mover

l When you remove a unit from the antistatic bag, avoid touching any electronic
components and circuits on it.
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.

Upgrade overview
Review the requirements and prerequisites that must be met before adding and
configuring additional I/O modules to the Data Movers.
In this upgrade procedure you will add one or more I/O module to each of the system
Data Movers.
l All hardware and software components in the VNX system must be installed,
configured, and operating properly prior to initiating the upgrade tasks. If any faults
are present, work to correct those issues.
l All new I/O modules to be installed during this upgrade must be available for
installation.

Upgrade overview 3
 l Each Data Mover in the system will be upgraded during this procedure, one at a time.

Note

If one or more Data Movers do not participate in the failover group, you are not
required to add an I/O module to these Data Movers. Be aware that a Data Mover
cannot enter into a primary/standby relationship with a peer Data Mover that does
not share its I/O module configuration.

Refer to Identifying available Data Mover I/O module slots on page 4 to verify valid I/O
module types.

Note

Do not use this procedure to replace or swap I/O modules that are already present.

Refer to the Parts Location Guides for the VNX Series systems on the Related Documents
page on https://mydocs.emc.com/VNX/. These guides include details about each I/O
module type, their part numbers, and part number locations.

Identifying available Data Mover I/O module slots

Table 1 on page 4 displays the maximum number of I/O module slots within each VNX
series system Data Mover.

Table 1 Number of supported I/O modules per Data Mover

Total number of I/O Breakdown of required and optional I/O modules

modules allowed per Data
Mover

Number Data Mover Number required Data Mover Number optional Data Mover slots
supported slots per Data Mover slot per Data Mover
Storage per Data
system Mover
VNX5300 3 slot 0 - slot 2 1 slot 0 2 slot 1 - slot 2

Note

Always install I/O modules in sets within a system or failover group. All Data Movers in a
system or failover group must have the same type of I/O modules in the same slots. Slot
0 in each Data Mover is reserved for connections to the storage array and for optional
tape backup devices. The other available slots can contain any type of network I/O
module that is supported for the system.

The following types of optional network I/O modules, shown in Figure 1 on page 5, are
available for Data Mover enclosure upgrades:

Note

If your are attempting to add an I/O module that requires a minimum VNX OE version
higher than the current version on your VNX, you must upgrade the VNX OE prior to
attempting the upgrade. For additional information on updating system software, go to
https://mydocs.emc.com/VNX/. Under VNX tasks, select Update VNX software. Select
appropriate settings for your configuration to generate a customized procedure to update
the VNX OE for your system.

4
 Adding an I/O Module to a Data Mover

l 1-Gb/s Ethernet with two 10/100/1000 copper ports and two optical ports; labeled 1
GbE on the latch handle
l 1-Gb/s Ethernet module with four 10/100/1000 copper ports; labeled 1 GbE on the
latch handle
l 10-Gb/s Ethernet module with two RJ-45 ports; labeled 10 GbE BaseT on the latch
handle

Note

10-Gb/s Ethernet RJ-45 module requires VNX OE for File version 7.1 or greater.
l 10-Gb/s Ethernet module with two optical/Active Twin-Ax ports; labeled 10 GbE v3 on
the latch handle

Note

10-Gb/s Ethernet optical/Active Twin-Ax module requires VNX OE for File version 7.1
or greater.

Table 2 on page 5 lists the I/O modules available for the system and the number of
each module that is standard and/or optional.
Figure 1 Data Mover network I/O modules

cge-x-3 fxg-x-1 fge-x-3

3

1
cge-x-2 fge-x-2
2

cge-x-1 cge-x-1
1

fxg-x-0
cge-x-0 cge-x-0
0
0

Table 2 I/O modules limits per Data Mover

Number of modules per Data Mover in a

VNX5300

Module type Standard Optional

8 Gb FC module: 1 0

2 BE ports (0, 1) and 2 AUX ports (2, 3)

10 GbE optical or Twin Ax module: 0 2

2 optical/Twin Ax ports (0, 1)

1 GbE optical and RJ-45 module: 0 2

Upgrade overview 5
 Table 2 I/O modules limits per Data Mover (continued)

Number of modules per Data Mover in a

VNX5300

Module type Standard Optional

2 optical ports (0, 1) and two RJ-45 ports

(2, 3)

1 GbE RJ-45 module: 0 2

4 RJ-45 ports (0, 1, 2, 3)

10 GbE RJ-45 module: 0 2

Note

Requires VNX OE for File 7.1 or greater.

2 RJ-45 ports (0, 1)

10 GbE optical or Twin-Ax module: 0 2

Note

Requires VNX OE for File 7.1 or greater.

2 optical/Twin Ax ports (0, 1)

Preparing your site for an upgrade

Before installing the upgrade, it is important to prepare for installation by:
l Site planning
l Review the upgrade procedure
l Unpack and inspect the upgrade
l Assemble required tools and equipment
l Open a terminal logging session with the Control Station
l Record the network configuration
Take a moment to become familiar with these tasks. If you have any questions, contact
your authorized support provider before you begin the upgrade.

Disabling Connect Home and email notifications

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

6
 Adding an I/O Module to a Data Mover

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 2 on
page 7).
Figure 2 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

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

Disabling Connect Home and email notifications 7

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

Determining failover status of the Data Movers

Before you begin
If the system is a single-Data Mover system, skip to the next task.
If the system is in a multi-Data Mover system, you must determine the failover status of
the Data Movers before continuing this procedure. If no failover relationships are
configured, skip to the next task.
Verify that the Data Movers are not in either of the following conditions:
l A primary Data Mover is in a failed over state
l A standby Data Mover is acting as a primary Data Mover

Note

If you are still logged in as root, go to step 2.

Perform the following steps to determine the failover status of the Data Movers:
Procedure
1. Log in to CS 0 as nasadmin. Change to the root user by entering the following
command:
su root

2. Enter the following command to determine the Data Mover failover status:
# /nas/bin/nas_server -info -all

Sample output:

id = 1
name = server_2.faulted.server_3
acl = 0
type = standby
slot = 2
member_of =
standbyfor= server_2
status :
defined = out_of_service
actual = online, ready
id = 2
name = server_2
acl = 0
type = nas
slot = 3
member_of =
standby = server_2.faulted.server_3, policy=manual
status :
defined = enabled
actual = online, ready

8
 Adding an I/O Module to a Data Mover

Note

If the type field is listed as nas, the Data Mover is a primary Data Mover. If the type
field is listed as standby, the Data Mover is a standby Data Mover. The standby field
lists which Data Mover is the standby for the primary Data Mover. The standbyfor
field lists the primary Data Mover for which the Data Mover is the standby.

3. If the name field indicates that a primary Data Mover is faulted and has failed over to
its standby, you will need to perform a restore on that primary Data Mover. Enter the
following command:
# /nas/bin/server_standby<server_name> -restore mover

Where <server_name> is the name of the faulted Data Mover.

Sample output:

# /nas/bin/server_standby server_4 restore mover

server_4.faulted.server_5 : reboot in progress........

server_4 : going standby
server_4.faulted.server_5 : going active
replace in progress ...done
failover activity complete
commit in progress (not interruptible)...done
server_4 : renamed as server_5
server_4.faulted.server_5 : renamed as server_4

4. Record the failover configuration in Table 3 on page 9. You will need this
information to recreate the failover relationships at the end of the upgrade.

Table 3 Data Mover failover relationships

Data Mover Type Standby (if Standby for (if

name primary) standby)
server_2

server_3

Note

If the system has fewer Data Movers that the maximum number allowed, you will not
use all the rows in this table.

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.

Determining failover status of the Data Movers 9

 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.

Halting the secondary Control Station

If your system is a dual Control Station system, the secondary CS (CS 1) must be stopped
before NAS services on the primary CS are stopped; otherwise, the secondary CS will
takeover. If your system does not have dual Control Stations (CS 0 and CS 1), skip to the
next section.
Before you begin
Ensure that you are currently logged into the primary Control Station using a terminal
emulation program (for example, HyperTerminal or PuTTy). If you are not yet logged in to
CS 0, do so prior to beginning this process.

Note

If the secondary CS is currently acting as the primary CS, you will need to failback and
then continue to power down the secondary CS.

To halt the secondary Control Station:

Procedure
1. From the open terminal logging session on the primary CS, SSH into the secondary
Control Station (CS):
# ssh 128.221.253.101

Note

The above command assumes that the system uses the default values for its internal
networking. If the system uses non-default values in its internal networking, use the
non-default internal IP address for CS 1 in the SSH command.

2. Log in to the secondary CS using the root user password.

3. Halt the secondary CS:
# /sbin/halt

4. Exit the SSH session with CS1 to return to the session on CS0:
# exit

Note

If you do not exit the SSH session on CS1 before it powers down the SSH session will
become unresponsive. Close the terminal emulator program and reopen a connection
with the primary CS using the settings provided earlier in the procedure.

5. Verify that the secondary CS has powered off by monitoring the system reason codes:
# watch /nasmcd/getreason

10
 Adding an I/O Module to a Data Mover

Note

Use Ctrl + c to end the monitoring.

Expect output for a two Control Station and two Data Mover system with CS1 powered
off:

10 - slot_0 primary control station

0 - slot_1 reset
5 - slot_2 contacted
5 - slot_3 contacted

6. After the secondary CS powers down, disconnect its power cable from the power
distribution panel (PDP).
Results
The secondary CS has been halted and powered off. Continue to the next section.

Preparing the system for upgrade

Prepare the system for the upgrade by:
l removing any established failover relationships

Note

You will manually recreate the failover relationships using the configuration
information recorded in Table 3 on page 9 after installing and configuring the new I/O
modules.
l stopping NAS services
l editing the DM 2 slicsignature (only required when upgrading a single-Data Mover
VNX)

Note

For single-Data Mover systems, skip steps 1-2.

To prepare the system for an upgrade:

Procedure
1. If no failover relationships are configured, skip to step 3. Otherwise, run the following
command to delete a Data Mover failover relationship:
# /nas/bin/server_standby <primary_server_name> -delete
mover=<standby_server_name>

Where <primary_server_name>is the primary Data Mover and <standby_server_name> is

the designated standby Data Mover.

Sample Output:

# /nas/bin/server_standby server_2 -delete mover=server_3

server_2 : done

2. Repeat step 1 on page 11 for each failover relationship that needs to be deleted.

Preparing the system for upgrade 11

 3. As root, run the following command to stop NAS services:

Note

If upgrading an I/O module in a single Data Mover system, prior to stopping NAS
service, run:
# /nas/bin/server_cpu <server_name> -q now

# /sbin/service nas stop

CAUTION

Stopping the NAS service will disrupt service on the system. Any process initiated by
the Control Station or any commands run from the /nas directory will be inhibited. Do
not to attempt to run this command while working in the /nas directory. Additionally,
after stopping NAS service, Unisphere and its alerts will be disabled until NAS service
is enabled later in this procedure.

Note

This command can take several minutes to complete. Wait until it completes before
proceeding to the next step.

4. After stopping NAS services, mount the following:

# mount /nas
# mount /nbsnas
# mount /nas/dos

5. For single-Data Mover systems only, remove the I/O module signature used for
validation when the Data Mover boots:
a. Edit /nas/server/slot _2/device file and remove the line starting with
"slicsignature validate=....... Save the edited file.
Example Device File:
In the example below, remove the line

slicsignature validate=132613

and save the file.

device isa isa-0

device pci pci-0
dskdumpconfig full slot=2
pciautoconfig
el3config tier2-aui
slicsignature validate=132613

b. Enter:
# export NAS_DB=/nas

c. Enter:
# /nas/sbin/build_config /nas/server/slot_2 /nas/dos/slot_2

12
 Adding an I/O Module to a Data Mover

d. Verify that the slicsignature line is gone by entering:

# grep slicsignature /nas/dos/slot_2/boot.cfg
The command should return nothing.

Installing the upgrade

Before you begin
Ensure that you have completed all of the preparation tasks presented earlier in this
procedure.

Upgrading Data Mover I/O modules

Beginning with the highest-numbered Data Mover, follow the process below to complete
the Data Mover I/O module upgrade on the initial Data Mover. You will perform this
upgrade on only one Data Mover at a time. After completely upgrading the initial Data
Mover, repeat the I/O module upgrade process on the next highest-numbered remaining
Data Mover until all system Data Movers have been upgraded.

Removing an I/O filler module

Procedure
1. Pull the latch handle on the filler module handle and gently pull the module from the
chassis (Figure 3 on page 13).
Figure 3 Removing a filler module

10/1
00/1
000
3
2
1
0

2. Place the I/O filler module on an antistatic surface.

Installing an I/O Module

To continue the upgrade of the current Data Mover, install the new I/O module:
Procedure
1. Remove the new I/O module from its antistatic packaging.
2. Carefully align the I/O module with the appropriate Data Mover slot and slide it in.
3. Push and release the small button on the latch handle (Figure 4 on page 14)

Installing the upgrade 13

 Figure 4 Installing an I/O module in the Data Mover

1
0

0
10/100/1000

10/100/1000
Once the button remains in, the I/O module is fully seated.
If the button springs back, gently push the module farther into the Data Mover, then
push the button again. If the button still does not rest flush with its handle, remove
the module and repeat steps 2 on page 13 and 3 on page 13 to install the module.

4. Repeat steps 1 on page 13 and 3 on page 13 for any other new I/O modules to be
installed into this Data Mover. Do not add new I/O modules to any other system Data
Movers at this time.
5. Run the following command to reboot the Data Mover:
# /nas/bin/server_cpu <server_name> -reboot now

Where <server_name> is the name of the Data Mover where the new I/O module is
installed.
If you deleted a failover relationships earlier, the Data Mover will reboot to Reason
Code 14. If no failover were removed, the Data Mover will reboot to Reason Code 4.
For single-Data Mover systems only, the Data Mover will reboot to Reason Code 4, not
14.

6. Run the following command to determine the Data Mover status:

Note

For multi-Data Mover systems with failover configured, when the Reason Code for Data
Mover reaches 14, use ctrl + c to end the getreason monitoring. This will take
approximately 4-7 minutes.

# watch /nasmcd/sbin/getreason

Sample Output:

6- slot_0 primary control station

14
 Adding an I/O Module to a Data Mover

5- slot_2 contacted
14- slot_3 hardware misconfigured

For a single-Data Mover system, the output may look like:

6- slot_0 primary control station

4- slot_2 contacted

7. Run the following command to configure the Data Mover:

# /nasmcd/sbin/setup_slot -i <slot_number>

where <slot_number> is the Data Mover to be configured. This command can take up to
20 minutes per Data Mover to complete.
For example:
# /nasmcd/sbin/setup_slot -i 3
8. Run the following command to verify that the new I/O modules are listed in the
system inventory:
# /nasmcd/sbin/t2vpd -s <slot_number>

Where <slot_number> is the Data Mover to be checked.

Sample Output:
# /nasmcd/sbin/t2vpd -s 3

SLOT_3 RESUME_INFORMATION_IO_MODULE_1:
EMC_PART_NUMBER="303-081-103B "
EMC_ARTWORK_REVISION=" "
EMC_ASSEMBLY_REVISION="B08"
EMC_SERIAL_NUMBER="CF2C6092400023 "
VENDOR_NAME=" "
LOCATION_OF_MANUFACTURE="HOPKINTON, MA,
USA "
YEAR_OF_MANUFACTURE="2009"
MONTH_OF_MANUFACTURE="7 "
DAY_OF_MONTH_OF_MANUFACTURE="21"
ASSEMBLY_NAME="10GBE 2-PORT OPTICAL SLIC "

Repeat I/O module upgrade on remaining Data Movers

To complete the I/O module upgrade on the remaining system Data Movers:
Procedure
1. On the remaining highest numbered Data Mover in the system, repeat Removing an
I/O filler module on page 13 and Installing an I/O Module on page 13.
2. Repeat 1 on page 15 for each remaining Data Mover undergoing the upgrade.
3. After you have completed the I/O module upgrade on each Data Mover in the system,
start NAS services:
# /sbin/service nas start

Note

It will take about 10 minutes for NAS services to finish starting.

Upgrading Data Mover I/O modules 15

 4. Verify that NAS services are available:

Note

Use ctrl + c to end the getreason monitoring.

# watch /nasmcd/sbin/getreason

Sample Output:

10- slot_0 primary control station

5- slot_2 configured
5- slot_3 configured

Connecting public LAN cables

The customer-supplied external network (public LAN) cables connect clients of the VNX
system to the I/O modules in the Data Movers.
To connect the public LAN cables to the newly available ports on the Data Mover:
Procedure
1. Locate the public network Ethernet cables, copper or optical.

Note

These non-EMC supplied public Ethernet cables should be hanging loose in the
cabinet. The other ends of these cables connect to the public network.

2. Connect the public LAN cables to the appropriate ports on the newly installed I/O
modules within the Data Mover.

Note

For successful Data Mover failover, you must establish identical network connections
for the primary and secondary Data Movers within a failover group.

Restoring the failover relationships

If you have a multi-Data Mover system and you deleted failover relationships earlier in
this procedure, restore the Data Mover failover relationships using the procedure below.
Skip to the next task if no failover relationships need to be recreated or if the system is a
single Data Mover configuration.
Refer to the recorded failover configuration to re-apply the Data Mover failover
configurations back to the pre-upgrade settings.
To restore the failover relationships:
Procedure
1. Run the following command to create a failover relationship:
# /nas/bin/server_standby <primary_Data_Mover> -c mover=
<standby_Data_Mover> -policy <policy_type>

Where <primary_Data_Mover> is the primary Data Mover and <standby_Data_Mover> is its

standby Data Mover , and <policy_Data_Mover> is auto or retry.

16
 Adding an I/O Module to a Data Mover

Sample Output:

# /nas/bin/server_standby server_2 -c mover=server_3 -policy

auto

server_2 : done

2. Verify that the Data Mover shows Reason Code 5, which indicates that the reboot is
complete:
# /nasmcd/sbin/getreason -s <slot_number>

Where <slot_number> is the slot number of the rebooting Data Mover .

3. Repeat 1 on page 16 and 2 on page 17 to re-create all the original failover
relationships.
4. Verify that the standby relationships have been created by using the following
command:
# /nas/bin/nas_server -info -all

Each Data Mover designated as standby will display their type as standby.

Results
The failover configuration has been restored. Go to the next task.

Powering up CS 1
If this is a dual-Control Station system, power up the secondary Control Station.
Otherwise, skip to the next task.
Procedure
1. Locate and re-connect the power cable of CS 1 to the PDP.
Figure 5 Location of CS Power Socket
Power socket

2. From CS 0, verify that CS 1, slot_1, is at Reason Code 11 before continuing to the next
step:
# watch /nasmcd/sbin/getreason

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.

Powering up CS 1 17
 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.

CRU failures
If the nas_checkup command returned a failed component, or the fault LED on the
component or DME is still lit, do the following:
Procedure
1. Wait one minute to see if the fault LED turns off. The component may take a few
seconds to turn off the LED.
2. If the fault LED remains lit, check that the component is properly inserted.
3. Open Unisphere using the following URL:
https://<control_station>

Where <control_station> is the hostname or IP address of the CS.

Log in with a unified global account. For example, the sysadmin global account can be
used.

4. Use the drop-down list at the top left of the Dashboard to select the system.
5. Select System > Hardware > Hardware for File to view information about the hardware
components.
6. Check the system inventory for faulted hardware components.
7. Check the /nas/log/sys_log file using the following command to identify if the
CRU error is cleared and the LED has not turned off yet.

Note

Logging is only active when NAS service is running. If the NAS service is stopped the
following will be displayed as the last line in the log file:

PLATFORM:MasterControl:WARNING:1:::::Terminating the Master Control

Application.

Note

The sys_log file will contain error messages that relate to the CRU.

Example:

# /nas/bin/nas_logviewer -t /nas/log/sys_log |tail -50

Jul 31 09:44:17 2008 78928309797::Enclosure 0 power supply B has

been removed
Jul 31 09:44:23 2008 94108478982::Enclosure 0 power supply B has
been detected

18
 Adding an I/O Module to a Data Mover

Note

If the variable after the argument -tail in this command is blank, the output will
stream by quickly causing you to miss any error messages.

8. Search for any Data Mover enclosure failures by entering:

# /nas/sbin/enclosure_status -v -e <DM_enclosure_id> | grep -i fail

where <DM_enclosure_id> is the ID number of the DME containing the new component.

Example:

# /nas/sbin/enclosure_status -v -e 0 | grep -i fail

Failed Fan Tach B Error Failed

Failed CRU Blower Mod B Failed

9. If you cannot identify the reason the CRU was unsuccessful, go to Support.emc.com >
Support > Service Center to get help. From Service Center, select one of the presented
options to request support.

Note

In all situations, you must have a valid login ID and password. If you do not have one,
you will need to register for one.

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

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

Enabling ConnectHome and email notifications 19

 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

Finishing up
Cable management is the most visual aspect of a hardware procedure. However, cable
management is often overlooked because it can be time consuming.
All Data Mover cables should be properly dressed so as not to interfere with each other or
other pieces of equipment. Use local practices to ensure that the cables attached to your
Data Mover are properly dressed.
To finish up:
Procedure
1. Dress and secure all cables so as to not disturb the cabling of other components when
you remove a replaceable unit (CRU or FRU).

Note

Typically, all cables come with the cable label clips attached to the cable. If the cables
do not have the cable label clips, attach them now.

2. Close out the terminal logging session and disconnect the management console from
the primary CS.

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.

20
 Adding an I/O Module to a Data Mover

Please send your opinion of this document to:

techpubcomments@EMC.com

Your comments 21
Copyright 2011-2014 EMC Corporation . All rights reserved. Published in USA.

Published May, 2014

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).

22