PowerProtect Data Manager Appliance - Field - Service - Guide-DM5500 5.15.0.0 Reimage Procedures
PowerProtect Data Manager Appliance - Field - Service - Guide-DM5500 5.15.0.0 Reimage Procedures
PowerProtect Data Manager Appliance - Field - Service - Guide-DM5500 5.15.0.0 Reimage Procedures
SolVe Generator
Solution for Validating your engagement
Topic
Field_Service_Guide
Selections
Field Service Guide: DM5500 5.15.0.0 Reimage Procedures
DM5500 Reimage Procedures: DM5500 Reimage Procedure
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
Copyright © 2024 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell
EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be
trademarks of their respective owners.
The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable
software license.
This document may contain certain words that are not consistent with Dell's current language guidelines.
Dell plans to update the document over subsequent future releases to revise these words accordingly.
This document may contain language from third party content that is not under Dell's control and is not
consistent with Dell's current guidelines for Dell's own content. When such third party content is updated
by the relevant third parties, this document will be revised accordingly.
Page 1 of 77
Contents
Preliminary Activity Tasks .......................................................................................................5
Read, understand, and perform these tasks.................................................................................................5
Page 2 of 77
Postrequisites ........................................................................................................................................42
Appendix 3: Expansion card in slot 5....................................................................................44
Prerequisites..........................................................................................................................................44
Removing the expansion card in slot 5 from the system board .............................................................44
Installing the expansion card in slot 5 on the system board ..................................................................45
Postrequisites ........................................................................................................................................46
Appendix 4: Drives................................................................................................................48
Prerequisites..........................................................................................................................................48
Removing a drive carrier from slot 0, 1, 4, or 5......................................................................................51
Removing the drive from the drive carrier..............................................................................................52
Installing a drive into the drive carrier ....................................................................................................53
Installing a drive carrier in slot 0, 1, 4, or 5 ............................................................................................53
Postrequisites ........................................................................................................................................54
Appendix 5: Shutting down the DM5500...............................................................................54
Appendix 6: Disconnecting the power cables and I/O cables ...............................................56
Appendix 7: Opening the drive bays .....................................................................................56
Appendix 8: Removing the drive carrier................................................................................57
Appendix 9: Closing the drive bays.......................................................................................58
Appendix 10: Removing the power supply unit.....................................................................60
Appendix 11: Removing the DM5500 server from the rails...................................................60
Appendix 12: Removing the cover ........................................................................................61
Appendix 13: Removing the butterfly riser ............................................................................61
Appendix 14: Installing the butterfly riser ..............................................................................62
Appendix 15: Installing the cover ..........................................................................................63
Appendix 16: Installing the DM5500 server into the rack......................................................64
Appendix 17: Installing the drive carrier................................................................................66
Appendix 18: Installing the power supply unit.......................................................................66
Appendix 19: Power on the DM5500 ....................................................................................67
Power on the DM5500 using iDRAC .....................................................................................................67
Power on the DM5500 using the power button......................................................................................68
Appendix 20: Removing the air shroud.................................................................................68
Page 3 of 77
Appendix 21: Installing the air shroud...................................................................................69
Appendix 22: Need to know ..................................................................................................70
Servicing DM5500 components.............................................................................................................70
Thermal limit for drive bays in service position ......................................................................................70
Hard drive bay servicing limitations .......................................................................................................71
Cable chain assembly............................................................................................................................71
Chassis support rails .............................................................................................................................71
Internal PERC card removal ..................................................................................................................71
Drive bays closing issue ........................................................................................................................71
Drive installation order ...........................................................................................................................72
SAS cable connections..........................................................................................................................72
Appendix 23: Removing the front bezel ................................................................................76
Appendix 24: Installing the front bezel ..................................................................................76
Page 4 of 77
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
2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.
Note: There may not be any top trending service topics for this product at any given time.
Page 5 of 77
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you
how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
Safety instructions
Follow the safety precautions that are described in the following sections during an installation or a
disassembly/reassembly procedure:
• Use a wrist grounding strap and mat when working inside any system to avoid electrostatic
discharge (ESD) damage.
• After removing a system component, carefully place the removed component on an antistatic
mat.
• Wear shoes with nonconductive soles or rubber soles to help reduce the risk of electrical shock
or seriously injury in an electrical accident.
WARNING: When removing the DM5500 server or an expansion enclosure from the rack or
installing it into the rack, you must depopulate all the drives due to the weight of the system.
WARNING: Do not attempt to lift the system by yourself to avoid potential injury. The DM5500
server or an expansion enclosure requires two people to lift it into and out of the rack, even with all
drives depopulated. Do not apply uneven force to either end of the system to prevent the chassis
from distorting or bending. Keep the system parallel to the ground when lifting and moving it.
WARNING: Opening or removing the DM5500 server cover or the expansion enclosure cover while
the system is powered on may expose you to a risk of electric shock.
CAUTION: Do not operate the DM5500 server without the cover for a duration exceeding five
minutes. Operating the system without the system cover can result in component damage.
CAUTION: To ensure proper operation and cooling, all bays in the DM5500 and the DM5500 fans
must be always populated with a component or a blank.
WARNING: Always use a static mat and anti-static wristband while working on components inside
the system.
CAUTION: Keep hands clear off the rotating DM5500 fan blades of the high-performance fans, as it
may cause serious injury or cuts. Ensure that the DM5500 server is powered off before servicing.
Bonding
Bonding is a method of connecting two or more grounding conductors to the same electrical potential.
This method requires the Field Service ESD kit. When connecting a bonding wire, always ensure that it
Page 6 of 77
is connected to a bare metal system and never to a painted or nonmetal surface. The wrist strap should
be secured to your skin. Ensure that you remove all jewelry such as watches, bracelets, or rings before
bonding yourself and the equipment.
Electrostatic discharge
Electrostatic discharge (ESD) is a major concern when you handle sensitive components such as
expansion cards, processors, memory DIMMs, and system board. A slight charge can result in damaging
the circuits on these components causing intermittent problems or shortening the life span.
Due to the increased density of semiconductors that are used in recent Dell products, the sensitivity to
static damage is now higher than in earlier Dell products. For this reason, some previously approved
methods of handling parts are no longer applicable.
There are two recognized types of ESD damage: catastrophic and intermittent failures.
• Catastrophic—The damage causes an immediate and complete loss of device functionality. For
example, a memory DIMM that has received a static shock, immediately generates a No
POST/No Video symptom.
Intermittent or latent failures are difficult to identify and troubleshoot. The image shows an example of
damage to a memory module trace. Although the damage is complete, the symptoms may not become
an issue or cause permanent failure for some time after the damage occurs.
Page 7 of 77
Figure 2. Intermittent, latent damage to a wiring trace
NOTE: Wireless antistatic straps or touching the chassis is not recommended as they do not
provide adequate ESD protection.
• Handle all static-sensitive components in a static-safe area. If possible, use antistatic floor pads
and workbench pads.
• Grasp the static-sensitive components by the side and not the top.
• Avoid touching the pins and circuit boards.
• Do not remove components from the antistatic packing material until you are ready to install the
components. Before unwrapping the antistatic packaging, be sure to discharge static electricity
from your body.
Page 8 of 77
• Place the components in an antistatic container or packaging before transporting the
components.
• Antistatic mat
• Wrist strap
• Bonding wire
The antistatic mat is dissipative and must be used to safely place parts on during service procedures.
When using an antistatic mat, your wrist strap must be snug, connected to the mat, and to the bare-metal
on the system that is being worked on. After the mat and wrist strap are deployed properly, remove the
components to be serviced from the ESD bag and place them on the mat. Remember, the only safe
place for ESD-sensitive items is in your hand, on the ESD mat, in the system, or inside a bag.
Page 9 of 77
Figure 5. Antistatic mat
The wrist strap and bonding wire can be connected either to:
NOTE: The physical connection of the wrist strap and bonding wire between your skin, the ESD
mat, and the hardware is known as bonding.
NOTE: Use only Field Service kits with a wrist strap, mat, and bonding wire. Avoid using wireless
wrist straps.
The internal wires of a wrist strap are prone to damage from normal wear and tear, and must be checked
regularly with a wrist strap tester to avoid accidental ESD hardware damage. Dell Technologies
recommends to test the wrist strap and bonding wire regularly.
Insulator elements
Dell Technologies recommends to place ESD sensitive devices, such as plastic heat sink casings, away
from internal components that are insulators and highly charged.
Table 1. Placement of insulator elements The following shows unacceptable and acceptable placement
for insulator parts relative to ESD sensitive devices:
Page 10 of 77
Unacceptable placement Acceptable placement
Look for a large open flat work area that is free of clutter and large enough to deploy the ESD kit with
more space to accommodate the type of system that is being repaired. The workspace should also be
free of insulators that can cause an ESD event. On the work area, insulators such as Styrofoam and
other plastics must be moved at least 12-inches or 30 centimeters away from sensitive parts before
physically handling any hardware components.
ESD packaging
All ESD sensitive devices must be shipped and received in static-safe packaging. Preferably, metal,
static-shielded bags. Ensure that you return the damaged parts in the same ESD bag or packaging in
which the new part arrived in. The ESD bag should be folded over and taped shut, and the foam packing
material used in the original box must be used.
ESD sensitive devices should be removed from packaging only at an ESD protected work surface, and
parts should never be placed on top of the ESD bag because only the inside of the bag is shielded.
Always place parts in your hand, on the ESD mat, in the system, or inside an antistatic bag.
Page 11 of 77
Figure 7. ESD packaging
Lifting equipment
NOTE: Do not lift systems that are greater than 50 pounds. Always obtain assistance, or use a
mechanical lifting device.
Page 12 of 77
2. Bend your knees. Do not bend at the waist.
3. Tighten stomach muscles. Abdominal muscles support your spine when you lift, offsetting the
force of the load.
4. Lift with your legs, not your back.
5. Keep the load close. The closer it is to your spine, the less force it exerts on your back.
6. Keep your back upright, whether lifting or setting down the load. Do not add the weight of your
body to the load. Avoid twisting your body and back.
7. Follow the same techniques in reverse to set the load down.
Table 1. NIC indicator codes This table describes the NIC indicator codes.
Status Condition
Page 13 of 77
Link and activity indicators are off. The NIC is not connected to the network.
Link indicator is green, and activity The NIC is connected to a valid network at its maximum port speed,
indicator is blinking green. and data is being sent or received.
Link indicator is amber, and activity The NIC is connected to a valid network at less than its maximum
indicator is blinking green. port speed, and data is being sent or received.
Link indicator is green, and activity The NIC is connected to a valid network at its maximum port speed,
indicator is off. and data is not being sent or received.
Link indicator is amber, and activity The NIC is connected to a valid network at less than its maximum
indicator is off. port speed, and data is not being sent or received.
Link indicator is blinking green, and NIC identify is enabled through the NIC configuration utility.
activity indicator is off.
Table 1. AC PSU status indicator codes This table describes the DM5500 AC PSU status indicator codes.
Power Condition
indicator
codes
Green A valid power source is connected to the PSU, and the PSU is operational.
Page 14 of 77
Not Power is not connected to the PSU.
illuminated
Blinking green When the firmware of the PSU is being updated, the PSU handle blinks green.
CAUTION: Do not disconnect the power cable or unplug the PSU when updating
firmware. If the firmware update is interrupted, the PSUs do not function.
Blinking green When hot-plugging a PSU, the PSU handle blinks green five times at a rate of 4 Hz and
and turns off turns off. This indicates a PSU mismatch regarding efficiency, feature set, health status, or
supported voltage.
CAUTION: If two PSUs are installed, both the PSUs must have the same type of
label; for example, Extended Power Performance (EPP) label. Mixing PSUs from
previous generations of PowerEdge servers is not supported, even if the PSUs
have the same power rating. This results in a PSU mismatch condition or failure to
power on the system.
CAUTION: When correcting a PSU mismatch, replace only the PSU with the
blinking indicator. Swapping the PSU to make a matched pair can result in an error
condition and an unexpected system shutdown. To change from a high output
configuration to a low output configuration or vice versa, you must power off the
system.
CAUTION: AC PSUs support both 240 V and 120 V input voltages except for
titanium PSUs, which support only 240 V. When two identical PSUs receive
different input voltages, they can output different wattages, and trigger a mismatch.
CAUTION: If two PSUs are used, they must be of the same type and have the
same maximum output power.
Table 1. DM5500 storage configuration This table lists the required DM5500 storage configuration
settings.
SSDs in slots 0 0.96 RAID/Ready/Online VD01, For RAID 1 volumes for ESXi
and 1 TB VD02 boot disk and DDVE VM
PERC
H730P Mini SSD at slot 2 1.92 Non-RAID For DDVE cache tier
TB
SSD at slot 3
3.84
Page 15 of 77
TB
To configure the DM5500 disks to be RAID or non-RAID, perform the following steps.
Steps
You must create the three RAID volumes that are shown in the following table.
CAUTION: It is important that these three RAID volumes are created in the order that is listed in the
table. First create VD01, then VD02, then VD03.
Page 16 of 77
Table 1. RAID volume propertiesThis table lists the three RAID volumes that you must create in the order
that is listed in the table.
Steps
Page 17 of 77
11. Select Physical Disks and click Next.
12. Enter the proper capacity according to the above table and click Next.
Page 18 of 77
14. Click the Apply Now button.
• BIOS_FFW4K_WN64_2.18.1.EXE
• Firmware_60K1J_WN64_2.52_A00.EXE
• iDRAC-with-Lifecycle-Controller_Firmware_98R9V_WN64_6.10.80.202_A00.EXE
• Network_Firmware_230WD_WN64_22.21.07.80_01.EXE
• Network_Firmware_9NPPG_WN64_22.0.9_A00.EXE
• Network_Firmware_FF1WF_WN64_22.0.9_A00.EXE
• Network_Firmware_JFF2M_WN64_22.20.11.EXE
• SAS-Non-RAID_Firmware_4J15M_WN64_22.15.05.00_A00.EXE
• SAS-RAID_Firmware_700GG_WN64_25.5.9.0001_A17.EXE
• SAS-Drive_Firmware_4RR8F_WN64_NS10_A00.EXE
• SAS-Drive_Firmware_7DTJD_WN64_EI0D_A00.EXE
• SAS-Drive_Firmware_VTX9C_WN64_RSL5_A00.EXE
Page 19 of 77
However, only the six DM5500 5.15.0.0 firmware components that are listed in the following table require
an update.
Table 1. DM5500 5.15.0.0 required firmware component updates This table lists the DM5500 5.15.0.0
required firmware component updates.
This section describes how to update the iDRAC version and the firmware component versions using the
iDRAC UI.
CAUTION: You must upgrade the iDRAC firmware first and by itself (before the other firmware
components).
Otherwise, the updating of any drive firmware will fail, and you will have to start over and update the iDRAC firmware first,
then the drive firmware components.
Upgrading the iDRAC firmware first will reboot the iDRAC, and then you can reconnect back to the
iDRAC UI and upgrade the remaining firmware components together.
Update the firmware components in the following order:
Page 20 of 77
Prerequisites
Filename Content
Perform the following steps to update the iDRAC version using the iDRAC UI.
Steps
Page 21 of 77
obsolete after the read-only and operator role iDRAC users are created.
As an example, during the initial appliance configuration, if you created a read-only iDRAC user
with jsmith as the username and P@ssword4 as the password, the operator role iDRAC user
credentials that were internally created are:
o Username: jsmith-opr
o Password: P@ssword4<appliance_serial_number>
You would then use the username: jsmith-opr and password: P@ssword4DPDID220100130
credentials to log in to iDRAC.
4. Go to Maintenance >System Update.
The Firmware Update page appears.
5. On the Manual Update tab:
o In the Location Type drop-down box, select Local.
o Click Choose File and select the iDRAC firmware image from the extracted firmware
package.
6. After the upload is complete, the Update Details section displays the firmware file that is
uploaded to iDRAC and its status.
7. If the firmware image file is valid and was successfully uploaded, the Contents column displays a
+ icon next to the firmware image file name. Expand the name to view the Device Name,
Current, and Available firmware version information.
8. Select the iDRAC firmware file and click Install.
9. Upgrading the iDRAC firmware does not reboot the server; it resets the Lifecycle Controller.
After the Lifecycle Controller is reset, you can log back into iDRAC and continue upgrading the
remaining firmware if needed.
10. To display the Job Queue page, click Job Queue. Use this page to view and manage the staged
firmware update or click OK to refresh the current page and view the status of the firmware
update.
Perform the following steps to update the individual firmware components that are listed in Table 12
using the iDRAC UI.
Steps
Page 22 of 77
The Firmware Update page appears.
2. On the Manual Update tab, for each of the components to be upgraded:
o In the Location Type drop-down box, select Local.
o Click Choose File, select the firmware image file for the required component, and then
click Upload.
3. After the upload is complete, the Update Details section displays each firmware file that is
uploaded to iDRAC and its status.
4. If the firmware image file is valid and was successfully uploaded, the Contents column displays a
+ icon next to the firmware image file name. Expand the name to view the Device Name,
Current, and Available firmware version information.
5. Select all firmware file(s) required to be updated and click Install or Install and Reboot.
(The Install and Reboot option is only visible if any image requires a reboot; for example, BIOS.)
6. When you click Install, Install and Reboot, or Install Next Reboot, the Updating Job Queue
message appears.
NOTE: If you navigate away from the page without saving the updates, an error message appears,
and all the uploaded content is lost.
7. Click Job Queue to display the Job Queue page where you can view and manage the staged
firmware updates or click OK to refresh the current page and view the status of the firmware
update.
NOTE: The Lifecycle Controller logic will determine the correct order to apply the firmware
upgrades. Multiple component updates may require one or more reboots. Installing multiple
component updates together will minimize the number of required reboots.
After you complete the firmware update, you may see the RAC0508 error message. If this is the
case, wait for some time and refresh the browser; it will then redirect to the login page.
Page 23 of 77
NOTE: You may already have had this app automatically installed on your workstation by IT. If you
do not have BeyondTrust Privilege Management installed on your workstation, you can install it
from the Company Portal.
o 7-Zip (This is required to extract the dmas-install-usb-5.15.0.0-<xxxx>.jar file
on Windows systems.)
• Verify that the correct time is set in BIOS, otherwise the reimage installation may fail.
In the iDRAC web interface, go to iDRAC Settings >Settings >Time zone and NTP Settings and
verify that the Time Zone is set to UTC and the NTP Server Settings are Disabled.
NOTE: The DM5500 gets its time from the ESXi host, until the external NTP server is set during the
deployment. iDRAC does not use the external NTP server for its time, and it should stay at UTC.
• You must verify that the DM5500 hardware configuration settings have not been altered and
match what is shown in the following table. If the storage settings are different from what is
shown in the following table, you must perform the storage configuration steps as described in
Appendix A. Configure DM5500 storage settings.
Table 1. DM5500 storage configurationThis table shows the required DM5500 storage configuration
settings.
SSDs in slots 0 1.92 RAID/Ready/Online VD01, For RAID 1 volumes for ESXi
and 1 TB VD02 boot disk and DDVE VM
Page 24 of 77
slots 4 and 5
Steps
Length Name
------ ----
1,945,600 ddve.ova-00
1,945,600 ddve.ova-01
160,580 ddve.ova-02
1 ddve.ova.md5
o infra/
Length Name
------ ----
6 5b2nqmjzsrktd6cpugidyxocabr5uvjkecpz.srs
969 dd-tools-1.0.0-1.tar.gz
740,334 dpainfra-3.3.0.0-2.rpm
228,181 dpatools-3.3.0.0-2.rpm
410,764 IDPA-14G-ESXÍ-3.3.0.0-2.iso
2 IDPA-14G-ESXÍ-3.3.0.0-2-version.xml
1 infra.prop
1 interconnect.json
21 ithaca-r740-local.conf
22 ithaca-r740-network.conf
21,967 ovftool-4.4.1-16812187.tar.gz
1,945,600 VCSA-7.0.3.01600-21958406.ova-00
1,945,600 VCSA-7.0.3.01600-21958406.ova-01
1,945,600 VCSA-7.0.3.01600-21958406.ova-02
1,030,001 VCSA-7.0.3.01600-21958406.ova-03
1 VCSA-7.0.3.01600-21958406.ova.md5
o ppdm/
Length Name
------ ----
Page 25 of 77
1,945,600 ppdm.ova-00
1,945,600 ppdm.ova-0l
1,945,600 ppdm.ova-02
1,945,600 ppdm.ova-03
1,945,600 ppdm.ova-04
99,312 ppdm.ova-05
1 ppdm.ova.md5
o ppoe_core/
Length Name
------ ----
1 component_versions.prop
134 message_catalog_definition.yml
169 message_catalog_en-US.properties
1,945,600 ppoecore.ova-00
1,945,600 ppoecore.ova-0l
1,945,600 ppoecore.ova-02
1,945,600 ppoecore.ova-03
1,945,600 ppoecore.ova-04
1,945,600 ppoecore.ova-05
1,945,600 ppoecore.ova-06
1,945,600 ppoecore.ova-07
1,497,641 ppoecore.ova-08
1 ppoecore.ova.md5
o version.xml
NOTE: The .ova files are split into 2 GB files so they can be written to the USB drive.
3. Insert the USB drive into a USB port on your Windows workstation.
4. Format the USB drive to FAT32 with the Rufus tool.
NOTE: In this step you are only formatting the USB to FAT32, you are not booting the USB.
a. On your Windows workstation, download and install the free Rufus tool from this github
website and install Rufus version 3.13 (rufus-3.13.exe) or greater.
For example: the rufus-3.13.exe file available for download here.
Administrative privileges are required to install the rufus-3.13.exe or greater file.
You must have the BeyondTrust Privilege Management app installed on your Windows
workstation. You can install the BeyondTrust Privilege Management app from the
Company Portal.
b. Open the Rufus application.
c. In the Boot Selection field, choose Non bootable and click Select. Use the parameters
shown in the following screenshot.
Page 26 of 77
5. Click START to format the USB drive to FAT32.
6. Copy the four ddve, infra, ppdm, and ppoe_core directories and the version.xml file into
the root directory on the USB drive.
7. Eject the USB drive and install the operating system on the DM5500 using the iDRAC Virtual
Console.
Install the operating system on the DM5500 using the iDRAC Virtual Console
About this task
CAUTION: All user data will be wiped out with USB installation.
Steps
1. Log in to the iDRAC UI using the operator role iDRAC user credentials.
Page 27 of 77
The operator role iDRAC user credentials were internally created when you created the read-
only iDRAC user during the initial appliance configuration in the Data Manager Appliance
Configuration UI.
CAUTION: Using the iDRAC root user credentials to log in to iDRAC will not be successful; you
must use the operator role iDRAC user credentials. The iDRAC root user credentials become
obsolete after the read-only and operator role iDRAC users are created.
If you cannot log in to the iDRAC UI with the operator role iDRAC user credentials, go to step 2.
If you logged in to the iDRAC UI with the operator role iDRAC user credentials, go to step 5.
2. If you cannot log in to the iDRAC UI with the operator role iDRAC user credentials, you must
enable the iDRAC operator role in the Data Manager Appliance UI.
a. In the Data Manager Appliance UI, go to Administration >Access Control.
b. Click the iDRAC tab, and click Enable Access >Provide Security Officer credentials,
c. Click Verify.
If you cannot enable the iDRAC operator role, go to step 3.
If you enabled the iDRAC operator role, log in to the iDRAC UI using the operator role iDRAC
user credentials and go to step 5.
3. If you cannot enable the iDRAC operator role, you must reset the iDRAC root password using
ESXi.
To reset the iDRAC root password using ESXi:
a. Log in to ESXi with the following credentials:
Username: root
Password: <ESXi_root_password>
If you do not know the ESXi root password, you must retrieve it from the PPOE VM. Go
to step 3b.
If you know the ESXi root password, go to step 3c.
b. To retrieve the ESXi root password from the PPOE VM, you must perform the following
steps. .
i. Obtain the bash key.
ii. Enter the bash key at the admin@appliance> prompt.
iii. Run the following command and note the esxi_root_password=<KEY> in the
output.
cat /data02/config/secretsManagerMapping.properties |grep
password
Sample output:
keycloak_master_admin_password=5b8905ba-15e5-4f9c-9af2-7f8bc25c7a55
ppoe_root_password=a9abf3e3-efcf-4059-8179-633ebb5c8963
vcenter_root_password=12e07b9a-7ce1-4805-ba60-9f13e4a4db2f
Page 28 of 77
esxi_root_password=327e1b88-96a1-41d5-8bed-3aff2d5b4729
vc_localadmin_password=a6cb6f83-6bb8-4bf0-a91d-611978011618
dd_ppdm_password=c0f7d98a-daef-4a98-af44-aaf51c0feef5
crux.combind_password=4f17f332-47ba-4e28-a205-af002122269b
In the above output, the ESXi root password (KEY) is in boldface and is
327e1b88-96a1-41d5-8bed-3aff2d5b4729
iv. Copy the key into the following command after /secrets/:
Example:
Password: <password_from_step_3b>
d. Find the iDRAC root user ID by running the following command on ESXi (should be 2 for
root user).
[root@esx:~] ipmitool user list 1
Example:
Page 29 of 77
e. Reset the iDRAC root user password by running the following command on ESXi:
[root@esx:~] ipmitool user set password <root_user_ID> <password>
Example:
[root@esx:~] ipmitool user set password 2 Abcd!234
Page 30 of 77
ii. In the Boot Mode field, change UEFI to BIOS, as shown in the following
screenshot.
Page 31 of 77
c. Check the boot sequence.
i. Go to Configuration >BIOS Settings >Boot Settings >Bios Boot Settings.
The BIOS boot settings should look similar to the following screenshot.
7. Insert the USB drive into one of the two USB ports on the back of the DM5500.
Make sure the other USB port is unused.
See Figure 1 for the location of the USB ports.
Page 32 of 77
NOTE: The reimage process could take up to 4 hours.
8. In the Virtual Console, click Connect Virtual Media and click Virtual Media.
9. On the Virtual Media page, map the IDPA-14G-ESXi-3.2.0.0-5.iso file that you extracted
from the dmas-install-usb-5.14.0.0-1280.jar file in Copy the DM5500 operating
system files onto a USB drive.
a. In the Map CD/DVD area, in the Image File field, click Browse and navigate to the
IDPA-14G-ESXi-3.2.0.0-5.iso file.
b. Select the IDPA-14G-ESXi-3.2.0.0-5.iso file and click Map Device.
10. Click Boot.
The Boot Controls dialog appears.
11. Select Virtual CD/DVD/ISO, as shown in the following screenshot.
Page 33 of 77
The installation process is automatic from this point forward. The whole process may take
several hours.
CAUTION: Do not remove the USB drive.
You will see a black screen for a few minutes, followed by a reboot.
ESXi boots.
Page 34 of 77
a. The four ddve, infra, ppdm, and ppoe_core directories are copied into ESXi,
followed by another reboot.
b. When the upgrade process starts, file copy and check progress will be updated in
/vmfs/volumes/appliance-local-storage/usb_install.log.
If there is a fatal error during this phase, the word FATAL will appear in
usb_install.log.
c. After the file copy and check phase successfully completes, the system will start
deploying VMs.
You will be directed to monitor /vmfs/volumes/appliance-local-
storage/.bootsy/bootstrap.out.
In the unlikely event of an error during this process, the errors should appear in
bootstrap.out.
There will be at least one reboot during the install so you may need to re-log in.
NOTE: Allow up to four hours for the installation process to complete. Do not assume that the
process has failed unless none of the logs in the /vmfs/volumes/appliance-local-storage
or /vmfs/volumes/appliance-local-storage/.bootsy directory have been updated in at
least 30 minutes.
15. After the installation, log in to the ESXi shell from the iDRAC Virtual Console:
Page 35 of 77
a. Log in to the iDRAC UI and open the Virtual Console.
b. Press Alt-F1.
c. Log in to ESXi with the following credentials:
Username: root
Password: dm@<PSNT>
If you are unable to log in to ESXi that means the installation is still ongoing or the
installation has failed. For example, if you get a blank screen and no login prompt, you
can determine the status of the installation by using Putty to SSH to 192.168.100.101,
using these credentials:
Username: root
Password: Abcd!2345
ppoe_workflow.py: done
bootstrap.py: [ppoeWorkflow] 'pre' exited: 0
bootstrap.py: [ppoeWorkflow] 'payload: ppoeWorkflow' exited: 0
bootstrap.py: SUCCESS!
Page 36 of 77
Manager Appliance Configuration UI in the Dell PowerProtect Data Manager Appliance Installation Guide
for DM5500 for more information about how to complete the initial configuration.
Page 37 of 77
Appendix 1: Bash access
About this task
Some FRU procedures, such as replacing the QAT card in slot 2, replacing the SAS card in slot 5, and
replacing the drives in slots 0, 1, 4, or 5, require bash access. The following procedure describes how to
obtain the bash key.
Steps
The above command opens bash for 1 hour and prompts you for the bash key.
NOTE: The system bash enter storage command without the --timeout parameter opens
bash only for 10 minutes.
Use existing "Bash Key" or get "Bash Key" from Dell Support by providing the following
Bash Key signing request:"changeme,1661467033".
This value remains in effect for four hours after which a new Bash Key signing request
must be used.
Enter Bash Key:
*************************************************************************
**** WARNING ****
*************************************************************************
**** Unlocking 'bash' may compromise your data integrity ****
**** and void your support contract. ****
*************************************************************************
admin@appliance>
Log in to one of the following instances with your Dell CORP username/password to generate
the bash key. Only Dell users (usually Dell Support team members) can obtain the bash key.
o Cork instance 1
o Durham instance 1
o Durham instance 2
o Santa Clara instance 1
o Santa Clara instance 2
Page 38 of 77
Appendix 2: QAT card in slot 2
Prerequisites
1. Follow the safety instructions.
2. Identify the failed QAT card in slot 2 by checking the Alerts page in the Data Manager Appliance
UI.
If the QAT card has failed, you will see the EVT-ENVIRONMENT-00061: QAT device has
failed alert.
3. Using SSH, log in to the PPOE VM (the PPOE mini-shell) with your admin username and the
DM5500 password.
a. At the command line, type the # system showfru QAT command to confirm the QAT
card is in the system.
The screen displays that the system is collecting data. You should see something similar
to the following output.
Page 39 of 77
NOTE: Currently the output does not show the status of the QAT card in slot 2.
4. From the PowerProtect Data Manager Appliance UI, disable the file system.
a. From the left navigation pane, select Infrastructure >Storage.
b. On the Summary tab, in the File System section, click the three vertical dots.
c. Select Disable.
8. To test the QAT card and confirm that the test is FAILED, run the following command:
# qat_diag
When removing the butterfly riser, ensure that the PCIe card holder latches are closed.
Page 40 of 77
Figure 1. Removing the QAT card from the butterfly riser
Page 41 of 77
Figure 1. Installing the QAT card into the butterfly riser
Postrequisites
1. Install the butterfly riser.
2. Install the system cover.
3. Place the system into the rack.
4. Open the drive bays, install all drives, and then close the drive bays.
5. Install the power supply units.
6. Reconnect the peripherals and connect the system to the electrical outlet.
7. Power on the system.
8. Retrieve the ESXi root password from the PPOE VM.
You will need it in the next step to set the new QAT card to passthrough mode in the ESXi shell.
Sample output:
Page 42 of 77
keycloak_master_admin_password=5b8905ba-15e5-4f9c-9af2-7f8bc25c7a55
ppoe_root_password=a9abf3e3-efcf-4059-8179-633ebb5c8963
vcenter_root_password=12e07b9a-7ce1-4805-ba60-9f13e4a4db2f
esxi_root_password=327e1b88-96a1-41d5-8bed-3aff2d5b4729
vc_localadmin_password=a6cb6f83-6bb8-4bf0-a91d-611978011618
dd_ppdm_password=c0f7d98a-daef-4a98-af44-aaf51c0feef5
crux.combind_password=4f17f332-47ba-4e28-a205-af002122269b
In the above output, the ESXi root password (KEY) is in boldface and is 327e1b88-
96a1-41d5-8bed-3aff2d5b4729
Password: <password_from_step_8>
Page 43 of 77
Use your admin username and the DM5500 password.
b. At the command line, type the # system showfru QAT command to confirm the QAT
card is in the system.
The screen displays that the system is collecting data. You should see something similar
to the following output.
NOTE: At this time, the output does not show the status of the QAT card in slot 2.
• You are installing a SAS card into a DM5500 5.12.0.1 (R1) system.
• You are replacing a defective SAS card in a DM5500 system from any release.
Prerequisites
1. Follow the safety instructions.
2. In the Data Manager Appliance UI, identify the failed expansion card by checking the Alerts
page.
3. Power off the DM5500 and all attached peripherals.
4. Disconnect the DM5500 from the electrical outlet, and disconnect the peripherals.
5. Open the drive bays, remove all drives, and then close the drive bays.
6. Remove the power supply units.
7. Remove the system from the rack and place it on an ESD work bench.
8. Remove the system cover.
9. Remove the butterfly riser.
10. Remove the air shroud.
11. Disconnect any cables connected to the PCIe card.
Page 44 of 77
Steps
Page 45 of 77
Figure 1. Installing the expansion card on the system board
Postrequisites
1. Connect the required cables to the expansion card.
2. Install the air shroud.
3. Install the butterfly riser.
4. Install the system cover.
5. Place the system into the rack.
6. Open the drive bays, install all drives, and then close the drive bays.
7. Install the power supply units.
8. Reconnect the peripherals and connect the system to the electrical outlet.
9. Power on the system and verify that there are no hardware errors in the iDRAC UI.
10. In the Data Manager Appliance UI, on the Alerts page, verify that there are no alerts related to
the replaced component.
11. Retrieve the ESXi root password from the PPOE VM.
You will need it in the next step to set the new SAS HBA card to passthrough mode in the ESXi
shell.
a. Obtain the bash key.
b. Enter the bash key at the admin@appliance> prompt.
c. Run the following command and note the esxi_root_password=<KEY> in the output.
Page 46 of 77
cat /data02/config/secretsManagerMapping.properties |grep
password
Sample output:
keycloak_master_admin_password=5b8905ba-15e5-4f9c-9af2-7f8bc25c7a55
ppoe_root_password=a9abf3e3-efcf-4059-8179-633ebb5c8963
vcenter_root_password=12e07b9a-7ce1-4805-ba60-9f13e4a4db2f
esxi_root_password=327e1b88-96a1-41d5-8bed-3aff2d5b4729
vc_localadmin_password=a6cb6f83-6bb8-4bf0-a91d-611978011618
dd_ppdm_password=c0f7d98a-daef-4a98-af44-aaf51c0feef5
crux.combind_password=4f17f332-47ba-4e28-a205-af002122269b
In the above output, the ESXi root password (KEY) is in boldface and is 327e1b88-
96a1-41d5-8bed-3aff2d5b4729
Password: <password_from_step_11>
i. In the list of virtual machines, right-click DDVE and select Edit Settings.
Page 47 of 77
ii. Go to Virtual Hardware >Add other device >PCI device.
iii. In the New PCI device dropdown box, select Fusion-MPT 12GSAS/PCIe
Secure SAS38xx - 0000:18:00.0.
iv. Save the DDVE VM settings.
d. Reboot the appliance using one of the following two methods:
▪ In the ESXi shell, run the reboot command.
▪ In the iDRAC UI Dashboard, go to the Graceful Shutdown dropdown menu and
select Reset System(warm boot).
For information on how to connect the SAS card ports to the expansion enclosure(s), see SAS cable
connections.
Appendix 4: Drives
This section describes the FRU procedure for replacing the disks in slots 0, 1, 4, and 5.
Prerequisites
1. Follow the safety instructions.
2. Identify the failed drive in the PowerProtect Data Manager Appliance UI.
a. Check the alerts in the Alerts tab and note down the drive number.
CAUTION: In the UI, logical drive position numbering in the appliance starts at 1.1. Physical drive
positions start numbering at 0. It is important to know that faulted drive alerts in the PowerProtect
Data Manager Appliance UI do not contain the physical slot number of the drive, but the logical slot
number of the drive. Therefore, in order to replace the correct drive in the appliance, you must
make sure the alert text in the UI corresponds to the correct physical slot number as described in
the following table. For example, if the UI alert text shows a failed drive for Enclosure=1:Disk=7,
this corresponds to a failed drive in physical slot 6.
Table 1. Mapping of physical slot number to logical slot number for PowerProtect Data Manager
Appliance UI alertsThis table describes the mapping between physical and logical slot numbers for
PowerProtect Data Manager Appliance UI alerts.
Physical slot number in drive bay Logical slot number displayed in UI alerts
0 1
1 2
2 3
3 4
4 5
5 6
Page 48 of 77
6 7
7 8
8 9
9 10
10 11
11 12
12 13
13 14
14 15
15 16
16 17
17 18
18 19
19 20
20 21
21 22
22 23
23 24
b. Go to the Infrastructure >Storage >Disks tab and select the failed disk from the list of
disks.
c. To remove the disk drive, click the blue Remove button.
This will initiate a data transfer from the failed disk to the remaining disks in the DM5500.
The disk status will change to Absent or Not Installed.
d. To make the disk drive easier to locate in the appliance, click the blue Blink LED button.
The Blinking LED light for Disk: <drive bay number>.<drive number> dialog appears,
indicating that the LED light on the front of the drive in the server is blinking.
Page 49 of 77
3. Shut down the application software services.
a. Obtain the bash key.
b. Enter the bash key at the admin@appliance> prompt.
c. Get the access token using the following curl command and copy only the token from
the output.
You will use this access token to run the curl commands in the next step.
Sample output:
{"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIxMEtPNlg2NU
NIN29ITDFIX1IxbDVWX3FuZHF0UjB1THdORlk1ZzlmdTdFIn0.eyJleHAiOjE2Njc4MTEyODcsImlhd
CI6MTY2NzgwNDA4NywianRpIjoiMTUwMzgyODgtMTQxOC00Zjc5LThmZmEtNDM2NWVmMzNlYmFmIiwi
aXNzIjoiaHR0cHM6Ly8xOTIuMTY4LjEwMC4xMDA6OTAwMS9hdXRoL3JlYWxtcy9JQU0iLCJhdWQiOiJ
wcG9lLWNvbmZpZ3VyYXRpb24tc2VydmljZSIsInN1YiI6IjgzNTBiYTZiLTE3MjctNGVkYS1hZmRjLT
AzNWVmZjg3YzA4ZiIsInR5cCI6IkJlYXJlciIsImF6cCI6InBwb2UtY29uZmlndXJhdGlvbi1zZXJ2a
WNlIiwic2Vzc2lvbl9zdGF0ZSI6Ijc5NzdjYjkzLWEwNTUtNGVhOS05YjU3LWZmMGI2ZDNmYWM5MSIs
InNjb3BlIjoiSUFNU2NvcGUiLCJzaWQiOiI3OTc3Y2I5My1hMDU1LTRlYTktOWI1Ny1mZjBiNmQzZmF
jOTEiLCJjbGllbnRJZCI6InBwb2UtY29uZmlndXJhdGlvbi1zZXJ2aWNlIiwiY2xpZW50SG9zdCI6Ij
EwLjAuMC4yIiwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXBwb2UtY29uZmlnd
XJhdGlvbi1zZXJ2aWNlIiwiYWNjZXNzX2luZm8iOnsiY3JlYXRlX3RpbWUiOjE2NjU5NDE4NjkzMjgs
ImRvbWFpbiI6IklBTSIsInJvbGVzIjpbImNvbXBvbmVudF9hZG1pbiJdfSwiY2xpZW50QWRkcmVzcyI
6IjEwLjAuMC4yIn0.XejIZITcOwN2yV7388KkTsRMENdhZfE_7QF8FRyAodO1DEP8CHO2BlbPhe3DXu
mDQagMwNvXl-JuC-QTkT2-xMmahgt6iHZyo53JnBCD_AW-
hEW7aLES4PItRjI_jXcPZPjDtToKuSxhQYKwrCFdj01gShyuXB3bLDRqFNz_fo_r0bA1NWV0VSTsTx7
yOGal7o5W67lBNopgCK-XxyJ_dsssZkEZoh-
VPGa4p0F8VMyx0kxfX1WWoNZoMEAHA9gX0LQ3uAINHwY4xDCVF81Zjyvh6H7sK-
o_xck8wELY9LsrrdVnr78zmRDmgQNPVxkFQyiYJlfpRqr2T6R9NWOqRg","expires_in":7200,"re
fresh_expires_in":36000,"refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiAiSldUIi
wia2lkIiA6ICJjYThlNzFjZS0xNTMxLTQ2MzEtYjhkZi1iZTQ1Y2I0OGFlNDEifQ.eyJleHAiOjE2Nj
c4NDAwODcsImlhdCI6MTY2NzgwNDA4NywianRpIjoiMTk3OGUyZjQtYzVkMS00Zjc4LWE3MjYtZjU5Y
mE4YmFmOTNkIiwiaXNzIjoiaHR0cHM6Ly8xOTIuMTY4LjEwMC4xMDA6OTAwMS9hdXRoL3JlYWxtcy9J
QU0iLCJhdWQiOiJodHRwczovLzE5Mi4xNjguMTAwLjEwMDo5MDAxL2F1dGgvcmVhbG1zL0lBTSIsInN
1YiI6IjgzNTBiYTZiLTE3MjctNGVkYS1hZmRjLTAzNWVmZjg3YzA4ZiIsInR5cCI6IlJlZnJlc2giLC
JhenAiOiJwcG9lLWNvbmZpZ3VyYXRpb24tc2VydmljZSIsInNlc3Npb25fc3RhdGUiOiI3OTc3Y2I5M
y1hMDU1LTRlYTktOWI1Ny1mZjBiNmQzZmFjOTEiLCJzY29wZSI6IklBTVNjb3BlIiwic2lkIjoiNzk3
N2NiOTMtYTA1NS00ZWE5LTliNTctZmYwYjZkM2ZhYzkxIn0.nIW622zHTy7Sey_VOkhYQYtwWmb69_W
Page 50 of 77
1T16A8dqDFUA","token_type":"Bearer","not-before-
policy":0,"session_state":"7977cb93-a055-4ea9-9b57-
ff0b6d3fac91","scope":"IAMScope"}
In the above sample output, the text in bold is the access token.
d. Run the following curl commands to shut down the software services:
You must wait approximately 15 minutes for the appliance shutdown to complete.
1. Press the release button to open the drive carrier release handle.
2. Holding the handle, slide the drive carrier out of the drive slot.
Page 51 of 77
Figure 1. Removing a drive
1. Using a Phillips #1 screwdriver, remove the screws from the slide rails on the drive carrier.
2. Lift the drive out of the drive carrier.
Page 52 of 77
Installing a drive into the drive carrier
About this task
When installing a drive into the drive carrier, ensure that the screws are torqued to 4 inch-pounds.
Steps
1. Insert the drive into the drive carrier with the connector end of the drive towards the back of the
carrier.
2. Align the screw holes on the drive with the screws holes on the drive carrier.
3. Using a Phillips #1 screwdriver, replace the screws to secure the drive to the drive carrier.
1. Press the release button on the front of the drive carrier to open the release handle.
2. Insert and slide the drive carrier into the drive slot.
3. Close the drive carrier release handle until it clicks in place.
Page 53 of 77
Figure 1. Installing a drive
Postrequisites
1. Install the front bezel.
2. In the iDRAC UI, monitor the RAID 1 virtual disk rebuild progress under Storage, Virtual Disks.
For a hard drive in slot 4 or 5, the rebuild process takes approximately 18 hours.
3. When the RAID 1 virtual disk rebuild has completed, reboot the appliance in the PPOE mini-
shell:
a. Obtain the bash key.
b. Enter the bash key at the admin@appliance> prompt.
c. Reboot the appliance with the following command on the PPOE VM:
*curl -i -k -X POST -H 'Content-Type: application/json' -d
'{"request": {"TaskParameters": ["--action=reboot"]}}'
https://192.168.100.101:8086/api/PT/v1/agent/task/client_task_vm_
shutdown.py*
You must wait approximately 20-30 minutes for the appliance to come back online.
4. In the Data Manager Appliance UI, on the Alerts page, verify that there are no alerts related to
the replaced component.
Page 54 of 77
Prerequisites
Ensure that there are no Protect, Restore, Config, or Maintenance jobs running in the Jobs page of the
Data Manager Appliance UI. It is recommended that you wait for any jobs to complete. However, if you
must shut down the DM5500 immediately, you must log in to the Data Manager Appliance UI and cancel
the jobs that are in progress.
About this task
1. From a host that has network access to the appliance, use Google Chrome to connect to the
Data Manager Appliance UI:
https://<Management_IP_address >
The Data Manager Appliance UI appears.
2. Log in with the admin username and password credentials you set up during the initial
configuration of the DM5500.
3. In the blue task bar in the upper right corner of the UI, click the gear icon , and select
Shutdown.
The Appliance Shutdown dialog appears.
4. In the Appliance Shutdown dialog, enter the appliance password, and click Shutdown.
The Initiating Shutdown dialog appears and checks if any jobs are running in the background.
Option Description
If no jobs are running in The PowerProtect DM5500 Shutdown page appears and shows the progress
the background. of the shutdown.
If jobs are running in the A Warning dialog appears, and you can either click
background.
• Cancel Shutdown to shut down the jobs in the UI, or
• Continue to proceed with the shutdown. The PowerProtect DM5500
Shutdown page displays and shows the progress of the shutdown.
Option Description
If there are no A message appears that the shutdown process successfully completed.
errors.
If there are A message appears that the shutdown has failed. Click Export Logs to troubleshoot the
errors. issue, or click Retry. Contact Dell support if required.
Page 55 of 77
Appendix 6: Disconnecting the power cables and I/O cables
This procedure is used to disconnect the DM5500 from electrical power and disconnect the peripherals.
About this task
NOTE: Labeling each power cable and I/O cable prior to shutting down and powering off minimizes
downtime.
Steps
1. Before shutting down and powering off the DM5500, label each power cable and I/O cable so
you can easily identify them when you need to plug them in to restore the DM5500.
2. Unplug power cables from the power supplies from the DM5500.
3. Disconnect I/O cables to enable FRU replacement as necessary from the DM5500.
As you disconnect the cables, label the ports on the back of the server using painter's tape to
ensure that you plug the cables back into the correct ports later.
CAUTION: Drive bays should not be in service position for more than 5 minutes because of thermal
concerns. When the drive bay is open for more than five minutes, the cooling fans spin at a higher
speed to provide extra cooling to the system. Thus system health status changes from the normal
to critical state, and system event The BP1 drive bay is kept open for an extended
period of time is logged.
Steps
1. If locked, unlock the drive bay lock that is located above the left release latch, by pushing it up.
2. Open the release latches of drive bay 1 and pull the drive bays out.
Page 56 of 77
Figure 1. Opening the drive bays
1. Press the release button to open the drive carrier release handle.
2. Holding the handle, slide the drive carrier out of the drive slot.
Page 57 of 77
Figure 1. Removing a drive
1. Pull back the blue release tabs on both sides and slide the drive bays into the system, until both
the bays lock into place.
Page 58 of 77
Figure 1. Closing drive bays
2. If required, lock the drive bay lock that is located above left release latch, by pushing it down.
NOTE: In some circumstances, the drive bays may not close after fully opening, due to the sheet
metal on the rail bracket being bent and blocking the rail stop. To fix the issue, use a plastic scribe
to pry the sheet metal back to its default position and try closing the drive bays.
Page 59 of 77
Appendix 10: Removing the power supply unit
About this task
CAUTION: The DM5500 server needs one power supply unit (PSU) for normal operation. On
power-redundant systems, remove and replace only one PSU at a time in a DM5500 server that is
powered on. The DM5500 supports either 1100W PSUs or 1600W PSUs, depending on the country
or region where it is installed. When you are replacing a PSU, make sure that both PSUs are the
same wattage.
Steps
Press the release latch and slide the PSU out of the system by using the PSU handle.
CAUTION: The DM5500 server is heavy and should be removed from the rack by two people. (The
DM5500 server weighs approximately 95 lbs with all 24 drives populated, and under 50 lbs with all
drives depopulated.) To avoid personal injury and/or damage to the equipment, do not attempt to
remove the DM5500 server from the rack without a mechanical lift and/or help from another person.
Steps
1. In the back of the DM5500 server, remove the two chassis retention brackets that are located in
the two rack holes above each rail.
Using a Phillips #2 screwdriver, loosen the two screws on each retention bracket.
Page 60 of 77
2. Locate the lock levers on the sides of the inner rails. Unlock each lever by rotating it up to its
release position. Grasp the sides of the DM5500 server firmly and pull it forward until the
standoffs are at the front of the J-slots in the rails. Lift the DM5500 server up and away from the
rails.
3. Place the DM5500 server on a suitable work surface. Ensure that the work surface is capable of
supporting the weight.
1. Using a 1/4-inch flat head or Phillips #2 screwdriver, turn the lock counterclockwise to the unlock
position.
2. Press the release tabs on the system cover, and slide the cover towards the rear of the system.
3. Lift the cover from the system.
Loosen the captive screw on the butterfly riser and holding the touch points, lift the riser away from the
system.
Page 61 of 77
Figure 1. Removing the butterfly riser
1. If removed, install the QAT card (slot 2) and/or the expansion card (slot 3) into the butterfly riser.
2. Tighten the captive screw to firmly hold the riser to the system board.
Page 62 of 77
Figure 1. Installing the butterfly riser
1. Align the tabs on the system cover with the guide slots on the system.
2. Slide the cover towards the front of the system, until the system cover locks in place.
3. Using a 1/4 inch flat head or Phillips #2 screwdriver, turn the lock clockwise to the lock position.
Page 63 of 77
Figure 1. Installing system cover
WARNING: Do not attempt to lift the system by yourself to avoid potential injury. The DM5500
server requires two people to lift it into the rack, even with all drives depopulated. Do not apply
uneven force to either end of the system to prevent the chassis from distorting or bending. Keep the
system parallel to the ground when lifting and moving it.
Page 64 of 77
Figure 1. Diagram and description of installing the DM5500 server into the rack
The following steps are procedures to install the appliance into the rack:
Steps
• Insert two cage nuts in the two rack holes above each rail. You will use these to install the
chassis retention bracket after the appliance is installed.
NOTE: The cage nuts must be installed before installing the appliance in the rack.
• Remove the shipping screws from the sides of the DM5500 server, before installing it in the rack.
Page 65 of 77
NOTE: The chassis shown in the image is not representative of a specific system.
Next steps
1. Press the release button on the front of the drive carrier to open the release handle.
2. Insert and slide the drive carrier into the drive slot.
3. Close the drive carrier release handle until it clicks in place.
Ensure that both the PSUs are of the same type and have the same maximum output power.
NOTE: The maximum output power (shown in watts) is listed on the PSU label.
Steps
Slide the PSU into the PSU bay until the PSU is fully seated and the release latch snaps into place.
Page 66 of 77
Figure 1. Installing the power supply unit
1. Turn on the iDRAC and log in to iDRAC from its UI using the operator role iDRAC user
credentials that were internally created when you created the read-only iDRAC user during the
initial appliance configuration in the Data Manager Appliance Configuration UI.
CAUTION: Using the iDRAC root user credentials to log in to iDRAC will not be successful; you
must use the operator role iDRAC user credentials. The iDRAC root user credentials become
obsolete after the read-only and operator role iDRAC users are created.
As an example, during the initial appliance configuration, if you created a read-only iDRAC user
with jsmith as the username and P@ssword4 as the password, the operator role iDRAC user
credentials that were internally created are:
o username: jsmith-opr
o password: P@ssword4<appliance_serial_number>
You would then use the username: jsmith-opr and password: P@ssword4DPDID220100130
credentials to log in to iDRAC.
2. In the iDRAC Dashboard UI, click the Power On System button.
Page 67 of 77
In the bottom right region of the Dashboard page, you can monitor the appliance startup status in
the iDRAC Virtual Console.
Power on the DM5500 by pressing and holding the power button located in the front right corner of the
appliance.
The power icon on the button will light up green and the LED displays a solid blue line when the
DM5500 is powered on.
NOTE: Never operate the DM5500 server with the air shroud removed. The DM5500 server may
get overheated quickly, resulting in the shutdown of the system and loss of data.
Steps
Page 68 of 77
Figure 1. Removing air shroud
1. Align the slots on the air shroud with the guide pin on the system.
2. Lower the air shroud into the system until it is firmly seated.
Page 69 of 77
Figure 1. Installing air shroud
1. Remove all the drives. Temporarily label each drive with its corresponding slot number, so that
you can return them to their original drive slots.
2. Remove the power supply units.
Two people are required to remove the DM5500 server from the rack and reinstall it back into the rack.
Page 70 of 77
critical state and the system event - The BP1 drive bay is kept open for an extended
period of time is logged.
• Open the drive bays, remove the faulty drive, and close the drive bays.
• Replace the faulty drive in the carrier with the new drive.
• Open the drive bay, install the drive in its original slot, and then close the drive bays.
Page 71 of 77
Figure 1. Fixing the rail bracket bending issue
Page 72 of 77
in the DM5500 SAS card ports as shown in the following image.
Each expansion enclosure only supports redundant configurations. Both EMMs must be connected to
the DM5500 server for the enclosure to function properly. The following diagrams show how to connect
the SAS cables from the DM5500 server to one, two, or three enclosures. The SAS ports on each EMM
in an enclosure are labeled 1 and 2. Port 1 is the host port and port 2 is the expansion port.
Table 1. DM5500 with one enclosure cabling instructions This table provides cabling instructions for a
DM5500 with one enclosure.
Page 73 of 77
Figure 4. DM5500 with two enclosures cabling
Table 2. DM5500 with two enclosures cabling instructions This table provides cabling instructions for a
DM5500 with two enclosures.
Page 74 of 77
Figure 5. DM5500 with three enclosures cabling
Table 3. DM5500 with three enclosures: DM5500 to enclosure cabling instructions This table provides
DM5500 to enclosure cabling instructions for a DM5500 with three enclosures.
Table 4. DM5500 with three enclosures: enclosure to enclosure cabling instructions This table provides
enclosure to enclosure cabling instructions for a DM5500 with three enclosures.
Page 75 of 77
Appendix 23: Removing the front bezel
About this task
Before you install the bezel, locate and remove the bezel key.
Steps
1. Align and insert the tabs on the right end of the bezel into the slots on the system.
NOTE: Ensure that the drive bay is locked before installing the front bezel. If required, lock the drive
bay lock that is located above the left release button, by pushing it down.
Page 76 of 77
2. Fit the left end of the bezel onto the system and press the bezel until you hear the release button
click.
3. Lock the bezel.
Page 77 of 77