VNX VNX 5300 Procedures-Replacing The Storage Processor (SP) in DPE
VNX VNX 5300 Procedures-Replacing The Storage Processor (SP) in DPE
Topic
VNX 5300 Procedures
Selections
VNX5300 Activity Type: Hardware Replacements
Prevent possible DU-DL situation. Do you have the Service LAN Connection procedure?: No - Include
the Service LAN Connection procedure
Disk Processor Enclosure (DPE): Storage Processor
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved.
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.
Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.
Page 1 of 32
Contents
Preliminary Activity Tasks ...................................................................................................4
Read, understand, and perform these tasks.................................................................................................4
Page 2 of 32
Task 8: Removing a memory module .........................................................................................19
Installing a memory module...................................................................................................................20
Task 9: Installing a power supply ................................................................................................21
Transferring the I/O modules and I/O filler modules ..............................................................................22
Removing an I/O module or an I/O filler module....................................................................................22
Task 10: Installing I/O modules or I/O filler modules.....................................................................23
Task 11: Installing a storage processor (SP) assembly ................................................................23
Task 12: Reconnecting cables to the back of the SP assembly ...................................................24
Verify SP LEDs ....................................................................................................................24
Enable Write Cache.............................................................................................................25
Task 13: Enable the system write cache.......................................................................................25
Task 14: Verifying the operation of a new or replacement part with Unisphere............................25
Task 15: Checking the system for faulted hardware .....................................................................26
Task 16: Running the Verify Storage System wizard....................................................................26
Enabling Connect Home.....................................................................................................26
Enabling call home for a block system........................................................................................................26
Enable ESRS device client on control station.............................................................................................27
Enabling Connect Home and email notification for a file/unified system ....................................................27
Appendix A: Using the Install Base Group (IBG) Business Services Portal ..............28
Page 3 of 32
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity
301857: Do not perform a VNX OE NDU on any VNX Storage Processors connected to a VPLEX
running any VPLEX GeoSynchrony version. Do not perform a proactive Storage Processor reboot on
any VNX Storage Processors connected to a VPLEX running any VPLEX GeoSynchrony version.
Refer to ETA 182792, ETA 193541, and ETA 197315
2. [ ] Table 2 lists the top 10 trending service topics related to this product. This is a proactive attempt
to make you aware of any KB articles that may apply to your activity, or at the very least inform you of
issues that may be associated with this product.
Page 4 of 32
Handling Field Replaceable Units (FRUs)
WARNING: The weight of some FRU assemblies is not evenly distributed. To prevent personal
injury or equipment damage when handling FRU assemblies, make sure you provide extra support
at the heavy end of a FRU assembly.
This section describes precautions you must take and general procedures you must follow when
removing, installing, or storing field-replaceable units (FRUs). The procedures in this section apply to FRU
handling during hardware upgrades as well as during general replacement.
CAUTION: When you want to power down a storage processor enclosure (SPE), turn off the
power switch on the enclosure’s standby power supply (SPS). Never turn off the SPE’s power
supply switches. Turning off the SPE power supply switches instead of the SPS power switch
shuts down the storage processors before they have enough time to save the write-cache data to
the vault drives. This causes data loss.
If write-cache data is not saved, the storage processor log displays an error message similar to the
following:
Enclosure 0 Disk 5 0x90a (Can’t Assign - Cache Dirty) 0 0xafb40 0x14362c.
If you see this error message, contact Customer Service immediately.
Page 5 of 32
If an emergency arises and the ESD kit is not available, follow the procedures in the section
Emergency procedures (without an ESD kit).
Use the ESD wristband that is supplied with your system.
To use it, attach the clip of the ESD wristband (strap) to any bare (unpainted) metal on the cabinet
enclosure; then secure the wristband around your wrist with the metal button against your skin.
IMPORTANT: These procedures are not a substitute for the use of an ESD kit. You should follow them
only in the event of an emergency.
Before touching any FRU, touch a bare (unpainted) metal surface of the enclosure.
Before removing any FRU from its antistatic bag, place one hand firmly on a bare metal surface of the
enclosure, and at the same time, pick up the FRU while it is still sealed in the antistatic bag. Once you
have done this, do not move around the room or contact other furnishings, personnel, or surfaces
until you have installed the FRU.
When you remove a FRU from the antistatic bag, avoid touching any electronic components and
circuits on it.
If you must move around the room or touch other surfaces before installing a FRU, first place the
FRU back in the antistatic bag. When you are ready again to install the FRU, repeat these
procedures.
Page 6 of 32
When removing a disk module, pull the module part way out of the slot, then wait 30 seconds for the
drive to spin down before removing it.
When installing multiple disks in a powered-up system, wait at least 10 seconds before sliding the
second and each subsequent disk into the system.
Place a disk module on a soft, antistatic surface, such as an industry-standard antistatic foam pad or
the container used to ship the module. Never place a disk module directly on a hard surface.
Note: The procedure below details how to disable call home using Unisphere. As an alternative you can
use naviseccli on a Windows management client to disable call home:
naviseccli eventmonitor -monitor -disableresponse -user <username> -password
<password> -scope 0 -server <serverIPaddr> -time <min>
1. [ ] Log in to the storage system or the Unisphere domain that contains the storage system.
2. [ ] From Unisphere, select System > Monitoring and Alerts > Notification and select the
Distributed Monitors tab.
3. [ ] Right click on the name of SP A in the list of distributed monitors for the storage system on which
you are disabling call home and select Disable/Enable Responses.
The Disable/Enable Responses dialog box appears.
4. [ ] Select the Disable Responses check box and set a time period during which responses will be
disabled for the anticipated maintenance activity. Then click OK.
In the popup that appears, click Yes to confirm.
5. [ ] Repeat these steps for SP B.
Note: You MUST disable responses on BOTH SP A and SP B to disable the storage system call
home responses.
Page 7 of 32
Note: Disable/Enable Responses (quiet mode) feature will automatically re-enable call home when the
timer you set to disable call home expires. Network connectivity between the storage system and the call
home monitoring station is required for the Software Assistant to automatically enable call home and
verify the call home rules.
2. [ ] Open a terminal emulation program (For example, HyperTerminal or PuTTy) and use the
following settings to create a serial connection to CS 0:
Bits per second: 19200
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Emulation: Auto Detect
Telnet terminal ID: ANSI
3. [ ] Login as nasadmin.
4. [ ] Become the root user:
$ su root
Password:
5. [ ] As the root user, disable Connect Home:
# /nas/sbin/nas_connecthome -service stop
6. [ ] Disable the email notification service:
# /nas/bin/nas_emailuser -modify -enabled no
7. [ ] Verify that the email notification service has stopped (is not enabled):
# /nas/bin/nas_emailuser -info
8. [ ] Check if ESRS client is enabled. Record if ESRS is enabled. If a control station is replaced or re-
imaged ESRS must be re-provisioned.
Page 8 of 32
# /nas/sbin/nas_connecthome –i
ESRS :
Priority = Disabled or Enabled
9. [ ] If ESRS client is enabled run the following command and record the ESRS configuration data.
# /celerra/esrs2/Configurators/esrs_client_configurator --show-esrs-
configuration
ESRS DC is connected to esrs3-corestg.isus.emc.com on port 443
Policy Manager is disabled
Proxy Server is disabled
IMPORTANT: The VNX Storage Processor’s Service LAN ports are not always connected to an internal
switch. The VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600 and VNX8000
Service LAN ports are internally switched, but the VNX5100, 5300 and 5500 are not internally switched.
IMPORTANT: See the CAUTION below before attaching any cables to the Service LAN ports.
The Service LAN of the two SPs in every VNX series storage system has the following factory-set IP
addresses:
SP-A: 128.221.1.250 (Service LAN port on SP-A SAN Management Module)
SP-B: 128.221.1.251 (Service LAN port on SP-B SAN Management Module)
Note: The storage system’s internal network (Service LAN) is mutually exclusive from the customer’s
main management ports on the Storage Processor (SP).
2. [ ] Navigate to your Network Connections and select your Local Area Connection (Figure 2), the
physical LAN cable port on your laptop.
3. [ ] On the TCP/IP Properties page, click the Use the following IP address radio button.
4. [ ] Set your laptop’s TCP/IP properties to the following IPs:
IP address: 128.221.1.249
Subnet mask 255.255.255.248
Default Gateway – 128.221.1.1 leave blank if you get an “out of IP range” error (INC6049148)
Page 9 of 32
Note: 128.221.1.254 can also be used to set your laptop IP address.
Note: The VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600 and VNX8000
Service LAN ports are internally switched. A single connection to one SP will allow communication to
both SPs.
Page 10 of 32
CAUTION: Never connect a switch or hub between the two Service LAN Ports on any
VNX5200, VNX5400, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600 and VNX8000 storage
system. Use a single cable for a connection with a hub or a direct connection from your laptop
to the Service LAN port. Connecting 2 cables with a Hub to both Service LAN ports will cause
a network storm and panic the array. If this problem occurs, promptly remove the Ethernet
cables. Reseat the Management Module if the port appears not to function. The Management
Modules are hot-swappable and may be removed and reseated without affecting the array’s
operation. Refer to Primus emc199379.
To the Service
To a single
LAN ports
Service LAN port
Laptop
Laptop
Page 11 of 32
Figure 4 VNX5700 and VNX7500 Service LAN Port Location
1. [ ] Connect the laptop network cable through a switch or hub to the Service LAN ports on the
VNX5100, VNX5300 or VNX5500 as shown in Figure 3 (left-side).
This Service LAN Interface connects to both SPA or SPB. The SP Service LAN port (RJ-45 with
wrench) location is shown in Figure 5.
2. [ ] Ping both SPs to verify connectivity.
Page 12 of 32
1. [ ] To run Unisphere Manager, open a browser and type in 128.221.1.250 for a connection to
SPA or 128.221.1.251 for a connection to SPB.
2. [ ] Answer Yes to the Security Alert if necessary.
3. [ ] The Navisphere Login screen will appear.
4. [ ] Enter the user name and password.
5. [ ] Enter the NAT IP address to add the peer SPs IP address.
1. [ ] Navigate to: Start/ Programs/ EMC/ Unisphere/ Unisphere Client and open the Off Array
“Unisphere Client”. It is usually located here: C:\Program Files\EMC\UIClient
2. [ ] If JAVA scripts are disabled on your browser and you receive the message:
To help protect your security, Internet Explorer has restricted this file from
showing Active content that could access your computer. Click here for options -
and select Allow Blocked Content.
3. [ ] Your browser will then change and show “Start a new Unisphere Session”.
4. [ ] Click on Start.
5. [ ] You may get another request to “Allow Blocked Content”
6. [ ] Click to allow blocked content.
7. [ ] Accept any Certificate requests.
8. [ ] When requested, enter the IP address, user name and password.
9. [ ] Enter the NAT IP address when prompted.
1. [ ] Disabling notification (Connect Home, Call Home, email notifications, and so forth).
2. [ ] Identify the faulted SP assembly.
3. [ ] Shut down power to the faulted SP assembly.
4. [ ] Replace the faulted SP assembly
Disconnect the cables from the faulted SP assembly.
Remove the faulted SP assembly.
Page 13 of 32
Transfer reusable components from the vaulted SP assembly to the replacement SP assembly:
1. [ ] Start Unisphere for the storage system by entering the storage processor 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.
1. [ ] Start the Unisphere Service Manager by doing either one of the following:
Click the Unisphere Service Manager icon on your desktop
Select Start > All Programs or Start > Programs, then select EMC > Unisphere Service
Manager > Unisphere Service Manager
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.
Page 14 of 32
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 Navisphere CLI, determine the current VNX OE for Block version operating on the storage
array.
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:
R31.008 or lower, you are required to complete the following tasks:
Disable the system write cache
Shut down power to the VNX SP
R31.011 or higher, continue to Shut down power to the VNX SP.
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.
Page 15 of 32
Replacing a SP assembly
Note: From the rear of the system, SP A is on the right side and SP B is on the left side. The images
used in the following tasks are examples illustrating the replacement of SP A.
2. [ ] Label and disconnect the SPS sense cable from the SP.
3. [ ] Label and disconnect the LAN cable from the management port.
4. [ ] Label each SAS back-end cable and disconnect it from the SP.
To disconnect a SAS cable, pull back the orange release tab and then pull the cable connector from
the port (Disconnecting a SAS cable).
Page 16 of 32
Figure 7 Disconnecting a SAS cable
5. [ ] Label each front-end I/O cable with the SP (A or B), slot number, and the number of the port to
which it is connected and then disconnect it.
1. [ ] Locate the two orange release levers on the bottom rear of the SP assembly.
2. [ ] On each lever, squeeze the latch knobs together to release the latches and then pull the latches
outward.
3. [ ] Pull out the latches until they are fully extended and the SP assembly is released from its
enclosure.
4. [ ] Use the latches to partially slide the assembly from its enclosure, and then use both hands to
support the assembly and draw it completely out of the DPE.
Page 17 of 32
Figure 8 Removing an SP assembly from the DPE
1. [ ] Squeeze the black and orange trigger on the back of the power supply (Removing a power
supply).
2. [ ] Pull the latch toward you until it is fully extended and the power supply is released from the SP
assembly (Removing a power supply).
3. [ ] Slide the power supply from the enclosure and place it aside on a clean, static-free surface.
Page 18 of 32
Figure 9 Removing a power supply
1. [ ] Pull the trigger latches down on the memory module to release the module from its connector
(Removing a memory module).
2. [ ] Carefully pull the memory module straight up from its connector.
Page 19 of 32
Figure 10 Removing a memory module
Page 20 of 32
Figure 11 Installing a memory module
1. [ ] Slide the power supply into the empty slot in the SP assembly until the latch engages and begins
to close.
2. [ ] Press the black knob in until the latch catches and the supply is seated and secure within the SP
assembly.
An audible click indicates that the latch is in place.
The latch assembly includes a yellow warning marker. If the marker is visible, the latch is not fully
closed.
Page 21 of 32
Figure 12 Installing a power supply (AC supply shown)
Page 22 of 32
Task 10: Installing I/O modules or I/O filler modules
To install an I/O module or I/O filler module:
1. [ ] Slide the module into the vacant slot until it is firmly seated in the enclosure (Installing a module).
2. [ ] When the module appears seated, push and release the small button on the handle (Installing a
module).
If the button remains in, the module is fully seated. If the button springs back, gently push the module
further into the chassis, then push the button again. If the button still does not rest flush with its
handle, remove the module and repeat step 2.
Page 23 of 32
Figure 15 Installing an SP assembly
1. [ ] Reconnect each front-end I/O cable to the I/O module port from which you removed it.
2. [ ] Reconnect each SAS cable to the SP.
3. [ ] Reconnect the LAN cable to the management port.
4. [ ] Reconnect the SPS sense cable to the SP.
If the system has only one SPS, then only SP A has an SPS sense cable connected to it.
5. [ ] Reconnect the AC power cord to the power supply.
Verify SP LEDs
Before you continue, verify that the Storage Processor fault LED is unlit and its power LED is steady
green. (SP power and fault LEDs)
Page 24 of 32
Figure 16 SP power and fault LEDs
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.
1. [ ] Using Navisphere CLI, set the write cache size to match the previous setting determined in
Disable the system write cache:
naviseccli -h <IP_address> -user <name> -password <password> -scope 0
setcache -wsz <write_cache_size>
2. [ ] Enable the write cache:
naviseccli -h <IP_address> -user <name> -password <password> -scope 0
setcache -wc 1
Task 14: Verifying the operation of a new or replacement part with Unisphere
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.
3. [ ] Select System > Hardware > Storage Hardware.
Page 25 of 32
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.
1. [ ] Start the Unisphere Service Manager by doing either one of the following:
Click the Unisphere Service Manager icon on your desktop
Select Start > All Programs or Start > Programs, then select EMC > Unisphere Service
Manager > Unisphere Service Manager
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.
Use Unisphere or naviseccli to enable call home for the storage system following this maintenance
activity.
Note: The procedure below details how to enable call home using Unisphere. As an alternative you can
use naviseccli on a Windows management client to enable call home:
naviseccli eventmonitor -monitor -enableresponse -user <username> -password
<password> -scope 0 -server <serverIPaddr>
1. [ ] Log in to the storage system or the Unisphere domain that contains the storage system.
2. [ ] From Unisphere, select System > Monitoring and Alerts > Notification and select the
Distributed Monitors tab.
3. [ ] Right click on the name of SP A in the list of distributed monitors for the storage system on which
you are enabling call home and select Disable/Enable Responses.
The Disable/Enable Responses dialog box appears.
4. [ ] De-select the Disable Responses check box and click OK.
5. [ ] Repeat these steps for SP B.
Page 26 of 32
Note: You MUST enable responses on BOTH SP A and SP B to enable the storage system call
home.
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
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:
Page 27 of 32
Appendix A: Using the Install Base Group (IBG) Business Services
Portal
Note: This procedure is only valid for EMC employees. EMC Service Partners should continue using the
Partner Notification Tool (PNT) or the Storage System Registration Utility (also known as ARU) to update
the EMC Install Base.
Business Services Portal: Provides a centralized location for users to submit requests directly to the
Install Base Group. The Portal is accessible outside the EMC network.
IMPORTANT: Completion of this activity is a mandatory requirement to closing a CSI Service Request.
6. [ ] On the Business Services Portal home page, navigate to the Post Sales section and click on
‘Install Base Group’ (Figure 2).
7. [ ] This will bring you to the Install Base Group case creation page. Make sure to choose the
specific Case sub-type for your request from the dropdown menu (Figure 3):
Note: If entering extra data not included in the chosen Case sub-type, enter the extra data in the
Description field or attach a document with the extra data.
Page 28 of 32
Figure 3 Case Sub-Type Selection
Sub-Type Selections:
d. IB Status Change - Update the status in the Oracle Install Base
e. PDR Update - Add or change Preferred Dispatch Resource on a TLA
f. Move or Party Change - Move or change what customer a TLA is located at
g. Upgrade/Conversion - Updating a product to the latest version based on a Sales Order Shipment
h. Debrief - Part Usage on the different task types in Oracle
i. Model Quantity Update - Changing the quantity on a Model in the IB
j. Secure Credentials - SP Upgrades and enabling the field to obtain secure credentials
k. Other - All other requests that don’t fit into categories
l. Model Separation - Splitting multiple models into single instances
m. Microcode Update - Updating the microcode to the desired version
Note: Once a sub-type is chosen, click on the ‘Select’ button which will populate the form with all the
relevant fields for your specific service request
8. [ ] Populate your contact name, e-mail address, phone and theatre (Figure 4).
You can also include the e-mail addresses of any other users that you would like to include on this
request in the ‘Additional Notification Email’ fields.
9. [ ] In the Case Details section, populate the ‘Subject’ and ‘Description’ fields to provide details on
the type of support needed (Figure 5).
Page 29 of 32
Figure 5 Case Details
Note: If this is a Federal request, make sure to check the “Federal Case’ check box. If not, do not
make a Federal Case out of it.
10. [ ] Select the corresponding Product Families that apply to your request (Figure 6).
Note: Family is the TLA/Model product family for your request. If you have multiple product families in
your request and one of them is listed here, choose that family; otherwise choose “All Other
Families”.
11. [ ] Fill out the additional fields that are relevant to your specific Case sub-type (Figure 6)
12. [ ] If you need to include additional documents with your request, navigate to the Upload
Attachments section and click on ‘Choose file’. Provide details on the file selected in the ‘Description’
field (Figure 7).
13. [ ] Once you have provided all the relevant information and included any necessary attachments,
click on the ‘Submit’ button (Figure 8).
Page 30 of 32
Figure 8 Submit
14. [ ] This will send the request to the Install Base Group for their review. You will receive automated
e-mail notifications to stay up-to-date on the progress of your request (Figure 9).
Figure 9 Done
15. [ ] Upon completion of this service activity, update the CSI database with the new VNX system
information for this site. Standard Global Services discipline requests you to register this service
activity in CSI, particularly for an Install or an Upgrade. You can use CRM or MS Outlook IB Database
email form in accordance with your team's reporting policy. Verify that all the customer site
information is correct (Table 1).
Page 31 of 32
Table 1 Site Information for CSI
Page 32 of 32