NetApp

1. Ocwen Financial Corporation
NetApp Failed Disk Replacement
Process
Document Owner: ETIS Storage & Backup Support Team
Approved:
Approved by:
Reference #:
NetApp Failed Disk Replacement Process

2. NetApp Failed Disk Replacement Process
TABLE OF CONTENTS
I. PURPOSE OF THIS PROCEDURE
II. SCOPE OF THIS PROCEDURE
III. ROLES AND RESPONSIBILITIES
IV. DOCUMENT PROCEDURE
V. PROCEDURE OWNERAND PARTICIPANTS
VI. PROCEDURES
VII. RELATED POICIESAND PPROCEDURES

3. NetApp Failed Disk Replacement Process
I. PURPOSE OF THIS PROCEDURE
The purpose of this procedure is to document Ocwen’s processes andactivities related to NetApp
disk replacement process.
II. SCOPE OF THIS PROCEDURE
This Procedure applies to all Ocwen personnel and contractors involved in the processes and
activities documented therein. For questions regarding the scope of this Procedure, always
consult the Document Owner.
III.ROLES AND RESPONSIBILITIES
The Storage Department implements, maintains and administers this Procedure. Senior
management of each affected department or Business Unit (“BU”) is responsible for enforcing the
standards and practices under this Procedure, including communicating compliance
expectations, throughout the BU. Whenapplicable, Corporate Compliance oversees and monitors
adherence to the requirements set in this Procedure. For questions regarding the responsibilities
for this Procedure, always consult the Document Owner.
IV. DOCUMENT PROCEDURE
This document outlines the standard expectation regarding Daily system support and monitoring
for the Storage & Backup Team.
V. PROCEDURE OWNER AND PARTICIPANTS
OWNER: Storage and Backup Team
PARTICIPANTS: Storage and Backup Team
NOC Team
DC Support Group

4. NetApp Failed Disk Replacement Process
VI. PROCEDURE
Email Alert Monitoring
Check out for an email alert from Netapp that describes a disk has failed.
1. Verifying Disk failure in NetApp.
a. Log into the NetApp CLI via the local IP address (10.75.248.20) and verify if the
NetApp (GAATLNAPSTG01-06) Disk which you have noted from Email Alert is disk
has failed in the console.
b. Run the below commands to view the failed disk on node wise.
cluster1::> nod run -node * -command vol status -f
or you can run the below command for view the failed disk state on the console.
cluster1::> storage disk show -broken

5. NetApp Failed Disk Replacement Process
2. Logging a ticket
 Create a ticket in SNOW assigned to Storage and Backup team.
3. Disk replacement process
 Open ticket with Park Place. below are the details for the Park Place.
https://centralpark.parkplacetechnologies.com
 Inform Park Place support that that disk has failed and request a disk for
replacement to be delivered to the QTS. Ask for the FedEx reference number for
tracking purposes.

6. NetApp Failed Disk Replacement Process
 Once Park Place engineer view the logged ticket they will send mail to us for the
communication.
4. Dispatching an Engineer for disk replacement
If the part is already delivered and ready to replace the failed disk,
a. Log a QTS Request in SNOW. If you are not a part of the DC Ops Team, drop an
email to Infrastructure Solutions – Datacenter Operations
InfrastructureSolutionsDatacenterOperations@ocwen.com with the details of the

7. NetApp Failed Disk Replacement Process
failed disk (NetApp Node Name, Hard Disk number, Cabinet number). Include
also the screenshot of the failed disk and the step-by-step procedure that the
engineer will follow.
b. The steps to be followed by QTS engineer should be verified steps
Sample example of the below mail
NetApp-
Replacement of failed disk on GAATLNAPSTG01-06 .msg
5. Replacing the disk / Removing Disks (To be followed by QTS Engineer)
 Gently remove the bezel from the front of the system.
 Identify the failed disk drive from the system console warning message and the
illuminated fault LED on the disk drive.
 Press the release button on the disk drive face.
I. Depending on the storage system, the disk drives have the release button
located at the top or on the left of the disk drive face.
II. The cam handle on the disk drive springs open partially and the disk drive
releases from the midplane.
 Pull the cam handle to its fully open position to unseat the disk drive from the midplane.

8. NetApp Failed Disk Replacement Process
 Slide out the disk drive slightly and allow the disk to safely spin down, which can take
less than one minute, and then, using both hands, remove the disk drive from the disk
shelf.
 With the cam handle in the open position, insert the replacement disk drive into the disk
shelf slot, firmly pushing until the disk drive stops.
Note1: Wait a minimum of 10 seconds before inserting a new disk drive. This
allows the system to recognize that a disk drive was removed.
Note2: Use two hands when inserting the disk drive, but do not place hands on the disk drive
boards that are exposed on the underside of the disk carrier.
 Close the cam handle so that the disk drive is fully seated into the midplane and the
handle clicks into place. Be sure to close the cam handle slowly so that it aligns correctly
with the face of the disk drive.
 Reinstall the bezel.
 Return the failed part to NetApp, as described in the RMA instructions shipped with the
kit.
6. Post replace the disk need to assign to Node on NetApp level. (In case automatic
assignment does not happen)
 Check if there is any un-assigned disk on array.
cluster1::> node run -node * -command disk show -n
 The storage disk assign command is used to assign ownership of an unowned
disk to a specific node. You can also use this command to change the ownership
of a disk to another node.
 Disks must be owned by a node before they can be used in an aggregate. If your
cluster is not configured to use automatic disk ownership assignment, you must
assign ownership manually
cluster1::> storage disk assign -disk disk-name -owner node-name

9. NetApp Failed Disk Replacement Process
7. Update and close the tickets in SNOW.
8. Send an email to the team and Update QTS engineer to close the REQ on their
side.
VII.RELATED POLICIES AND PROCEDURES
Click “Links & Attachments” in the upper right-hand corner of the PolicyTech document. Select
“Insert Link to Existing Document”. In the Choose a Document window, use the Search field to
locate the document you want to link to and then click the document title. Click “Add Another,” to
link another document or select “Done” to complete this task and return to the Policy.
APPENDIX A– TITLE OF APPENDIX A
For multiple appendices, repeat/insert Appendix heading and number Appendix A, Appendix B,
etc.
CHANGE RECORD
Date Author Version Change Reference
06/07/2019 Pokuri Srikanth
REVIEWERS
Date Name Position
MM/DD/YYYY Prashant Acharya Sr. Manager
DISTRIBUTION
No Name Location
1

10. NetApp Failed Disk Replacement Process
No Name Location
2
APPROVERS
Date Name Version Sign Off