Dell PowerVault ME5 Series Owner's Manual
  1. Manuals
  2. Brands
  3. Dell Manuals
  4. Storage
  5. PowerVault ME5 Series
  6. Owner's manual

Dell PowerVault ME5 Series Owner's Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Dell PowerVault ME5 Series Storage System
Owner's Manual
April 2022
Rev. A01

Advertisement

Table of Contents
loading

Related Manuals for Dell PowerVault ME5 Series

Summary of Contents for Dell PowerVault ME5 Series

  • Page 1 Dell PowerVault ME5 Series Storage System Owner’s Manual April 2022 Rev. A01...
  • Page 2 A WARNING indicates a potential for property damage, personal injury, or death. © 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

  • Page 3: Table Of Contents

    Contents About this guide..........................5 Chapter 1: Storage system hardware..................... 6 Locate the service tag............................... 6 Enclosure configurations..............................6 Upgrading to dual-controller configuration......................7 Removing the second controller..........................7 Enclosure management..............................7 Operation....................................8 Enclosure variants................................10 2U enclosure core product............................... 11 2U enclosure front panel............................
  • Page 4 ME5084 DDIC LEDs..............................36 5U84 controller module and IOM LEDs .........................37 Initial start-up problems..............................37 Troubleshooting 2U enclosures..........................37 Troubleshooting 5U enclosures..........................39 If the enclosure does not initialize...........................40 Correcting enclosure IDs............................40 Troubleshooting hardware faults..........................40 Chapter 3: Module removal and replacement................43 ESD precautions................................

  • Page 5: About This Guide

    The following documentation provides additional information about ME5 Series storage systems: ● Dell PowerVault ME5 Series Administrator's Guide ● Dell PowerVault ME5 Series ME5012 and ME5024 Getting Started Guide ● Dell PowerVault ME5 Series ME5084 Getting Started Guide ● Dell PowerVault ME5 Series Deployment Guide...

  • Page 6: Chapter 1: Storage System Hardware

    This document might contain third-party content that is not under the control of Dell. The language in the third-party content might be in inconsistent with the current guidelines for Dell content. Dell reserves the right to update this document after the content is updated by the relevant third parties.

  • Page 7: Upgrading To Dual-Controller Configuration

    controller module or a controller module blank must be installed in slot B to ensure sufficient airflow through the enclosure during operation. For 5U84 enclosures, a controller module must be installed in both slot A and slot B. These same 2U and 5U chassis form factors are used for the supported expansion enclosures; but with I/O modules instead of controller modules.

  • Page 8: Operation

    When the hardware installation is complete, use the PowerVault Manager to configure, monitor, and manage the storage system. The controller module also supports a command-line interface (CLI) for command line entry and scripting. For details, see the Dell PowerVault ME5 Series Storage System CLI Guide for your system. Operation...
  • Page 9 Figure 2. 2U12 enclosure system—rear orientation Figure 3. 2U24 enclosure system—front orientation The 2U24 controller enclosure is equipped with dual-controllers. Figure 4. 2U24 enclosure system—rear orientation Storage system hardware...

  • Page 10: Enclosure Variants

    Figure 5. 5U84 enclosure system—front orientation The 5U84 controller enclosure is equipped with dual-controllers. Figure 6. 5U84 enclosure system—rear orientation Enclosure variants The 2U chassis can be configured as a controller enclosure ME5012/ME5024, or an expansion enclosure ME412/ME424. The 5U chassis can be configured as a controller enclosure ME5084 or an expansion enclosure ME484.

  • Page 11: Enclosure Core Product

    Table 1. 2U12 enclosure variants (continued) Product Configuration PCMs Controller modules and IOMs ME412 12 Gb/s direct dock SAS drives The redundant PCMs must be compatible modules of the same type. The supported controller modules are 4-port FC SFP+, 4-port iSCSI SFP28, 4-port 10Gbase-T iSCSI, 4-port mini-SAS HD. The supported IOMs are used in expansion enclosures for adding additional storage.

  • Page 12: Enclosure Front Panel

    2U enclosure front panel In the following figures, integers on disks indicate drive slot numbering sequence. Figure 7. 2U12 enclosure system—front panel components Figure 8. 2U24 enclosure system—front panel components NOTE: ● For information about enclosure front panel LEDs, see 2U enclosure Ops panel.
  • Page 13 Figure 10. 2U expansion enclosure—rear panel components 1. PCM 0 2. IOM A 3. PCM 1 4. IOM B 2U enclosure rear panel components This section describes the controller module, expansion enclosure IOM, and power cooling module components for 2U enclosures.

  • Page 14: 5U84 Enclosure Core Product

    Power cooling module The following figure shows the power cooling module (PCM) used in controller enclosures and optional expansion enclosures. The PCM includes integrated cooling fans. The example shows a PCM oriented for use in the left PCM slot of the enclosure rear panel.

  • Page 15: 5U84 Enclosure Front Panel

    5U84 enclosure front panel Figure 14. 5U84 enclosure—front panel components 1. 5U84 enclosure drawer (slot 0 = top drawer) 2. 5U84 enclosure drawer (slot 1 = bottom drawer) This figure shows a plan view of an enclosure drawer that is accessed from the enclosure front panel. The conceptual graphics are simplified for clarity.
  • Page 16 Figure 16. 5U84 controller enclosure—rear panel components 1. Controller module A 2. Controller module B 3. FCM 0 4. FCM 4 5. PSU 0 6. PSU 1 Figure 17. 5U84 expansion enclosure—rear panel components 1. IOM A 2. IOM B 3.
  • Page 17 Figure 18. Controller module details 1. Host ports 2. USB serial port (service only) 3. USB serial port (CLI) 4. Ethernet port for management network 5. SAS expansion port Expansion module The 5U84 expansion enclosure uses the same IOMs that are used by 2U12 and 2U24 enclosures. The following figure shows the IOM used in supported expansion enclosures for adding storage.

  • Page 18: 5U84 Enclosure Chassis

    The 5U84 enclosures use separate CRU modules for power supply and cooling/circulation, respectively. The power supply module provides the enclosure with power connection and a power switch. The fan cooling module is smaller than the PCM, and five of them are used within the 5U enclosure to provide sufficient airflow throughout the enclosure. Fan cooling module The following figure shows the fan cooling module (FCM) used in 5U controller enclosures and optional 5U expansion enclosures.
  • Page 19 A drawer is designed to support its own weight, plus the weight of installed DDICs, when fully opened. CAUTION: The sideplanes on the enclosure drawers are not hot swappable or customer serviceable. Safety features ● To prevent the rack from tipping, slide only one enclosure out of the rack at a time. ●...

  • Page 20: Operators (Ops) Panel Leds

    Operators (Ops) panel LEDs Each ME5 Series enclosure features an Operators (Ops) panel located on the chassis left ear flange. This section describes the Ops panel for 2U and 5U enclosures. 2U enclosure Ops panel The front of the enclosure has an Ops panel that is located on the left ear flange of the 2U chassis. The Ops panel is a part of the enclosure chassis, but is not replaceable on-site.

  • Page 21: Enclosure Ops Panel

    5U enclosure Ops panel The front of the enclosure has an Ops panel that is located on the left ear flange of the 5U chassis. The Ops panel is part of the enclosure chassis, but is not replaceable on-site. Figure 24. Ops panel LEDs—5U enclosure front panel Table 5.

  • Page 22: Gb/S Controller Module Leds

    Figure 25. Controller module – rear orientation Each controller module maintains VPD (Vital Product Data) in EEPROM devices. In a dual-controller module system, controller modules are interconnected by SBB-defined I2C buses on the midplane. In this way, the SBB module can discover the type and capabilities of the partner SBB module, and vice versa, within the enclosure.
  • Page 23 Table 6. Common controller module LEDs (continued) Description Color Status Cache status Green On—Cache contains unwritten data, controller module is functioning properly Fast flash (1s:1s)—Cache is active, cache flush in progress Slow flash (3s: 1s)—Cache self-refresh in progress after cache flush Off—Cache is clear or system is coming online Ethernet management port Amber...

  • Page 24: Cache Status Led Details

    Figure 29. 10Gbase-T iSCSI ports Description Color Status iSCSI 10Gbase-T link speed Green On—10GbE link speed Amber On—1GbE link speed None Off—Not connected or link is down iSCSI 10Gbase-T link Green On—Connected, link is up activity Flashing—Link activity Off—Not connected or link is down The following figure shows the host port LEDs on a 12 Gb/s SAS controller module: Figure 30.

  • Page 25: Controller Failure When A Single-Controller Is Operational

    Cache status behavior If the LED is blinking evenly, a cache flush is in progress. When a controller module loses power and write cache is dirty (contains data that has not been written to disk), the supercapacitor pack provides backup power to flush (copy) data from write cache to memory.

  • Page 26: Chapter 2: Troubleshooting And Problem Solving

    Use the PowerVault Manager to configure and provision the system upon completing the hardware installation. Configure and enable event notification to be notified when a problem occurs that is at or above the configured severity. See the Dell PowerVault ME5 Series Storage System Administrator’s Guide for more information.

  • Page 27: Performing Basic Steps

    Use the CLI As an alternative to using the PowerVault Manager, you can run the show system CLI command to view the health of the system and its components. If any component has a problem, the system health is in a Degraded, Fault, or Unknown state, and those components are listed as Unhealthy Components.

  • Page 28: Host I/O

    ● Informational – A configuration or state change occurred, or a problem occurred that the system corrected. No immediate action is required. The event logs record all system events. Review the logs to identify fault and cause of the failure. For example, a host could lose connectivity to a disk group if a user changes channel settings without taking the storage resources that are assigned to it into consideration.

  • Page 29: Enclosure Pcm Leds

    Table 9. Ops panel functions—2U enclosure front panel (continued) Indicator Description Color Status Unit identification Green Dual seven-segment display that shows the numerical position of the display (UID) enclosure in the cabling sequence. The UID is also called the enclosure ID. The controller enclosure ID is 0.

  • Page 30: Enclosure Disk Drive Carrier Module Leds

    Table 11. Ops panel LED states (continued) System Power Module Fault Identity Associated Status (Green/Amber) (Amber) (Blue) display LEDs /Alarms Blink Enclosure identification or invalid ID selected Actions: ● If the Ops panel Module Fault LED is on, check the module LEDs on the enclosure rear panel to narrow the fault to a CRU, a connection, or both.

  • Page 31: Io Module Leds

    Table 12. Drive carrier LED states (continued) Activity LED (Green) Fault LED (Amber) Status/condition* Blink off with activity Available Blink off with activity Storage system: Initializing Blink off with activity Storage system: Fault-tolerant Blink off with activity Storage system: Degraded (not critical) Blink off with activity Blinking: 3s on/ 1s off Storage system: Degraded (critical)

  • Page 32: Gb/S Controller Module Leds

    12 Gb/s controller module LEDs The diagrams with tables that immediately follow provide descriptions for the different controller modules that can be installed into the rear panel of the controller enclosures. NOTE: Consider the following when viewing the controller module diagrams on the following pages: ●...
  • Page 33 Table 14. Common controller module LEDs (continued) Description Color Status None Off—Not connected or link is down The following figure shows the host port LEDs on a 32Gb/s Fibre Channel controller module: Figure 34. 32Gb/s Fibre Channel ports Description Color Status Fibre Channel link activity Green...

  • Page 34: 5U84 Enclosure Leds

    Figure 37. 12 Gb/s SAS ports Description Color Status SAS port status Green On—Connected, link is up Green or amber Flashing—Link activity Amber On—Connected, partial link is up None Off—Not connected or link is down 5U84 enclosure LEDs When the 5U84 enclosure is powered on, all LEDs turn on for a short period to ensure that they are working. NOTE: This behavior does not indicate a fault unless LEDs remain lit after several seconds.

  • Page 35: Me5084 Psu Leds

    Table 15. Ops panel functions – 5U enclosure front panel (continued) Indicator Description Color Status Top Drawer Fault Amber Constant or blinking: fault present in drive, cable, or sideplane (drawer 0) Bottom Drawer Fault Amber Constant or blinking: fault present in drive, cable, or sideplane (drawer 10) ME5084 PSU LEDs The following table describes the LED states for the PSU: Table 16.

  • Page 36: Me5084 Drawer Leds

    Table 18. Ops panel LED states (continued) Status/description Module Amber indicates a fault in a controller module, IOM, PSU, or FCM. Check the drawer LEDs for indication of a Fault disk fault. Logical Amber indicates a fault from something other than firmware (usually a disk, an HBA, or an internal or external status RAID controller).

  • Page 37: 5U84 Controller Module And Iom Leds

    Table 20. DDIC LED states Fault LED (Amber) Status/description* Off (disk module/enclosure) Not present Blinking: 1s on/1s off Identify Any links down: On Drive link (PHY lane) down Fault (leftover/failed/locked-out) Available Storage system: Initializing Storage system: Fault-tolerant Storage system: Degraded (non-critical) Blinking: 3s on/1s off Storage system: Degraded (critical) Storage system: Quarantined...
  • Page 38 Table 21. Troubleshooting 2U alarm conditions (continued) Status Severity Alarm Enclosure configuration error (VPD) Fault – critical Low warning temperature alert Warning High warning temperature alert Warning Over-temperature alarm Fault – critical C bus failure Fault – loss of redundancy Ops panel communication error (I Fault –...

  • Page 39: Troubleshooting 5U Enclosures

    Thermal alarm Table 24. Thermal alarm recommended actions Symptom Cause Recommended action 1. Ops panel Module Fault LED is Internal temperature 1. Verify that the local ambient environment temperature is amber. exceeds a preset within the acceptable range. threshold for the 2.

  • Page 40: If The Enclosure Does Not Initialize

    Thermal considerations Thermal sensors in the 5U84 enclosure and its components monitor the thermal health of the storage system. NOTE: ● Exceeding the limits of critical values will activate the over-temperature alarm. ● For information about 5U84 enclosure alarm notification, see 5U alarm conditions.
  • Page 41 Host-side connection troubleshooting featuring 10Gbase-T and SAS host ports The following procedure applies to ME5 Series controller enclosures employing external connectors in the host interface ports. The external connectors include 10Gbase-T connectors in iSCSI host ports and 12 Gb SFF-8644 connectors in the HD mini-SAS host ports.
  • Page 42 ● Blinking – Cache data is being written to the controller module. ● Flashing at 1/10 second on and 9/10 second off – Cache is being refreshed by the supercapacitor. ● Off – Cache is clean (no unwritten data). 4. Remove expansion cable and inspect for damage. 5.

  • Page 43: Chapter 3: Module Removal And Replacement

    Module removal and replacement This chapter provides procedures for replacing CRUs (customer-replaceable units), including precautions, removal instructions, installation instructions, and verification of successful installation. Each procedure addresses a specific task. Topics: • ESD precautions • Dealing with hardware faults • Firmware updates •...

  • Page 44: Dealing With Hardware Faults

    If you do not have any of the suggested equipment for proper grounding, have an authorized technician install the part. For more information about static electricity or assistance with product installation, contact customer support. For additional information, see www.dell.com/support. Dealing with hardware faults Ensure that you have obtained a replacement module of the same type before removing any faulty module.

  • Page 45: Installing A Firmware Bundle

    Installing a firmware bundle In the PowerVault Manager, use the Maintenance > Firmware > System tab to install firmware bundles obtained from Dell and then activate a particular bundle. Review the following points before updating system firmware: ● Firmware update typically takes 5 minutes for a controller with current CPLD firmware, or up to 20 minutes for a controller with downlevel CPLD firmware.

  • Page 46: Using The Cli

    ● If an iSCSI port is connected to a Microsoft Windows host, the following event is recorded in the Windows event log: Initiator failed to connect to the target. ● See the Dell PowerVault ME5 Series Storage System Administrator’s Guide for additional information. Using the CLI 1.

  • Page 47: Attach Or Remove The Front Bezel Of A 2U Enclosure

    Table 26. ME5 Series 2U controller enclosure models (continued) Model Description Form factor Drives ME5024 Fibre Channel (32 Gb/s) SFP 2U24 Up to 24 2.5" (SFF) drives ME5024 iSCSI (25 GbE) SFP 2U24 Up to 24 2.5" (SFF) drives ME5024 iSCSI 10Gbase-T (10 Gb/s or 1 Gb/s) 2U24 Up to 24 2.5"...

  • Page 48: Replacing A Drive Carrier Module In A 2U Enclosure

    ● When moving FDE-capable disk drives for a disk group, stop I/O to the disk group before removing the drive carrier modules. Import the keys for the disk drives so that the drive content becomes available. See the Dell PowerVault ME5 Series Storage System Administrator’s Guide or Dell PowerVault ME5 Series Storage System CLI Guide for more...
  • Page 49 Figure 42. Removing an LFF drive carrier module (2 of 2) 3. Remove the drive carrier module from the drive slot. CAUTION: To ensure optimal cooling throughout the enclosure, blank drive carrier modules must be installed in all unused drive slots. Installing an LFF drive carrier module Perform the following steps to install an LFF drive carrier module in a 2U enclosure: 1.
  • Page 50 5. Continue to push firmly until the latch handle fully engages. You should hear a click as the latch handle engages and holds the handle closed. Figure 45. Installing an LFF drive carrier module (2 of 2) 6. Use the PowerVault Manager or CLI to verify the following: ●...
  • Page 51 Figure 47. Removing an SFF drive module carrier (2 of 2) 3. Remove the drive carrier module from the drive slot. CAUTION: To ensure optimal cooling throughout the enclosure, blank drive carrier modules must be installed in all unused drive slots. Installing an SFF drive carrier module Perform the following steps to install an SFF drive carrier module in a 2U enclosure: 1.

  • Page 52: Replacing A Ddic In A 5U Enclosure

    Figure 49. Installing an SFF drive carrier module (1 of 2) 4. Push the drive carrier module further into the enclosure until the latch handle starts to engage. 5. Continue to push firmly until the latch handle fully engages. You should hear a click as the latch handle engages and holds the handle closed.
  • Page 53 ● When moving FDE-capable disk drives for a disk group, stop I/O to the disk group before removing the DDICs. Import the keys for the disk drives so that the drive content becomes available. See the Dell PowerVault ME5 Series Storage System Administrator’s Guide or Dell PowerVault ME5 Series Storage System CLI Guide for more information.
  • Page 54 4. Remove the protective film from the upper assembly of the DDIC. 5. Slide the upper assembly of the DDIC onto the mounting bracket with the 2.5" disk drive 6. Secure the upper assembly to the mounting bracket using the supplied screws. Module removal and replacement...
  • Page 55 7. Attach the appropriate drive size label to the label location on top of the upper assembly. Installing a replacement 3.5" disk drive into a DDIC Each replacement disk drive is shipped with a new disk drive in carrier (DDIC). Install the replacement disk drive in the DDIC before opening the drawer of the enclosure to remove the failed drive.
  • Page 56 4. Slide the upper assembly of the DDIC onto the disk drive. 5. Secure the upper assembly to the disk drive using the supplied screws. 6. Attach the appropriate drive size label to the label location on top of the upper assembly. Module removal and replacement...
  • Page 57 Accessing the drawers of a 5U84 chassis The replacement procedure for DDICs must be completed within two minutes of opening a drawer. Opening a drawer 1. Verify that the anti-tamper locks are not engaged. The red arrows on the locks point inwards if the locks are disengaged as shown in the following figure.
  • Page 58 Figure 53. Opening a drawer (2 of 2) NOTE: The drawer must not remain open for more than two minutes while the enclosure is powered on. Closing a drawer 1. Press and hold the black latches on the sides of the open drawer in each extended top rail. The previous diagram shows a magnified detail of a slide latch, which resides on the left and right drawer rails.
  • Page 59 4. Close the drawer. Populating drawers The general guidelines for populating a drawer with DDICs are provided in the Dell PowerVault ME5 Series Storage System Deployment Guide. Additional guidelines are provided for replacing disk drives in previously populated drawers, or populating enclosures delivered with the half-populated enclosure configuration option.

  • Page 60: Replacing A Controller Module Or Iom

    Contact your account manager for part numbers. ● If the two groups of disk drives have different firmware, all disk drives must be updated with current/compatible firmware. See the Dell PowerVault ME5 Series Storage System Administrator’s Guide or online help for additional information about updating firmware.
  • Page 61 NOTE: If the Partner Firmware Update (PFU) feature is not enabled, update the firmware on the replacement controller module. For more information updating the firmware, see the Dell PowerVault ME5 Series Storage System Administrator's Guide. 5. Remove the second controller module from the enclosure.
  • Page 62 5. Grasp the module latch between the thumb and forefinger, and squeeze the flange and handle together to release the latch handle, and swing the latch handle out to release the controller module from its seated position. 6. Swing the latch handle open, then grip the latch handle and slide the controller module forward from the slot. Figure 57.
  • Page 63 1. If the controller module is still operational, record the IP addresses and settings of the storage system in the System Information Worksheet, which is located in the Dell PowerVault ME5 Series Storage System Deployment Guide. 2. Use the PowerVault Manager or CLI to shut down the storage system.
  • Page 64 Before you begin any procedure, see precautions. NOTE: For instructions on performing the following steps, see the Dell PowerVault ME5 Series Storage System Deployment Guide. 1. Examine the controller module for damage, and closely inspect the interface connector. Do not install the controller module if the pins are bent.

  • Page 65: Replacing A Power Cooling Module (Pcm) In A 2U Enclosure

    5. Place both hands on the IOM body, and pull it straight out of the enclosure such that the IOM remains level during removal. Installing an IOM Before you begin any procedure, see precautions. 1. Examine the IOM for damage, and closely inspect the interface connector. Do not install the IOM if the pins are bent. 2.

  • Page 66: Replacing A Power Supply Unit (Psu) In A 5U Enclosure

    Figure 61. Removing a power cooling module NOTE: This figure shows a controller enclosure with two 4-port SAS controller modules. However, this procedure applies to all 2U controller enclosures and expansion enclosures. 8. Grip the handle and pull the power cooling module out of the enclosure, taking care to support the base of the module with both hands as you remove it from the enclosure.
  • Page 67 Removing a power supply unit Before removing the power supply unit (PSU), disconnect the power from the PSU by either the mains switch (where present) or by physically removing the power source in order to ensure your system has warning of imminent power shutdown. Make sure that you correctly identify the faulty PSU before beginning the procedure.

  • Page 68: Replacing A Fan Cooling Module (Fcm) In A 5U Enclosure

    Figure 64. Install a PSU 3. Slide the PSU into the slot until the latch clicks home. 4. Connect the AC power cord. 5. Move the power switch on the PSU to the On position. 6. Wait for the Power OK LED on the newly inserted PSU to illuminate green.. ●...

  • Page 69: Completing The Component Installation Process

    Figure 65. Removing an FCM 4. While supporting the FCM with both hands, remove it from the enclosure. Installing a fan cooling module You can hotswap the replacement of a single fan cooling module. However, if you are replacing multiple fan cooling module, the enclosure must be powered off using an orderly shutdown using the management interfaces.

  • Page 70: Verifying Component Operation

    ● Between the controller enclosure and the host. 2. Reconnect power cables to the storage enclosures. Verifying component operation 1. Restart system devices by moving the power switch on the power supply to the On position in the following sequence: a.

  • Page 71: Performing Updates In Powervault Manager After Replacing An Fc Or Sas Hba

    1. For an FC HBA, update the zoning if a switch is used, then update the host/initiator grouping in PowerVault Manager. 2. For a SAS HBA, update the host/initiator grouping in PowerVault Manager. For details about managing hosts and host groups in PowerVault Manager, see the Dell PowerVault ME5 Series Storage System Administrator’s Guide.

  • Page 72: Chapter 4: Events And Event Messages

    Events and event messages When an event occurs in a storage system, an event message is recorded in the system event log. Depending on the event notification settings of the system, the event message can also be sent to users using email, and to host-based applications using SNMP.

  • Page 73: Events

    Events Table 28. Event descriptions and recommended actions Number Severity Description/Recommended actions Critical This event severity has the following variants: 1. The disk group is online and cannot tolerate another disk failure, and no spare of the proper size and type is present to automatically reconstruct the disk group. ●...
  • Page 74 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● The CLI trust command might be able to recover some of the data in the disk group. See the CLI help for the trust command. Contact technical support for help to determine if the trust operation applies to your situation and for help to perform it.
  • Page 75 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ If the indicated disk failed for one of these reasons—excessive media errors, imminent disk failure, possible hardware failure, disk is not supported, too many controller- recoverable errors, illegal request, due to being degraded, or due to being too slow— replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity.
  • Page 76 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Look for another event logged at approximately the same time that indicates a disk failure, such as event 8, 55, 58, or 412. Follow the recommended actions for that event. Info.
  • Page 77 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Info. The indicated disk is no longer designated as a spare. Recommended actions: ● No action is required. Info. Disk group verification has started. Recommended actions: ●...
  • Page 78 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Check that there is a module or blank plate in every module slot in the enclosure. ● If none of these explanations apply, replace the disk or controller module that logged the error.
  • Page 79 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This event is logged with Warning severity to provide information that may be useful to technical support, but no action is required now. It will be logged with Error severity if it is necessary to replace the controller module.
  • Page 80 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● The first time this event is logged with Warning severity, if the indicated disk is not running the latest firmware, update the disk firmware. ● If this event is logged with Warning severity for the same disk more than five times in one week, and the indicated disk is running the latest firmware, replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity.
  • Page 81 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. The two controllers are communicating with each other and cache redundancy is enabled. Recommended actions: ● No action is required. Info. The FC loop ID for the indicated disk group was changed to be consistent with the IDs of other disk groups.
  • Page 82 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. Info. The current controller has unkilled the partner controller. The other controller will restart. Recommended actions: ● No action is required. Info.
  • Page 83 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Error Both controllers in an Active-Active configuration have the same serial number. Non-unique serial numbers can cause system problems. For example, WWNs are determined by serial number. Recommended actions: ●...
  • Page 84 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Warning The link for the indicated host port has unexpectedly gone down. This can affect host mappings. Recommended actions: ● Look for corresponding event 111 and monitor excessive transitions indicating a host- connectivity or switch problem.
  • Page 85 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. Info. The Management Controller is about to restart. Recommended actions: ● No action is required. Info. This event is logged when the IP address used for management of the system has been changed by a user or by a DHCP server (if DHCP is enabled).
  • Page 86 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. Error A failure occurred when trying to write to the Storage Controller (SC) flash chip. Recommended actions: ● Replace the controller module that logged this event. Error A correctable ECC error occurred in Storage Controller CPU memory more than once during a 12-hour period, indicating a probable hardware fault.
  • Page 87 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions higher firmware level failed, the surviving controller at the lower firmware level cannot read the metadata in disks that have failed over. Recommended actions: ● If this occurs after a firmware update, it indicates that the metadata format changed, which is rare.
  • Page 88 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Check for other events that indicate faults in the system and follow the ￭ recommended actions for those events. But, if the event indicates a failed disk and the recommended action is to replace the disk, do NOT replace the disk at this time because it may be needed later for data recovery.
  • Page 89 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. All disk channels have been paused. I/O will not be performed on the disks until all channels are unpaused. Recommended actions: ● If this event occurs in relation to disk firmware update, no action is required. When the condition is cleared, event 183 is logged.
  • Page 90 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If event 193 has not been logged since this event was logged, the over-temperature condition probably still exists and should be investigated. Another over-temperature event was probably logged at approximately the same time as this event (such as event 39, 40, 168, 307, 469, 476, or 477).
  • Page 91 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Warning An environmental change occurred that allows write-back cache to be enabled, but the auto- write-back preference is not set. The environmental change is also logged at approximately the same time as this event (event 191, 193, 195, 199, 201, or 241).
  • Page 92 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data. Recommended actions: ● Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module, expansion module, or power supply.
  • Page 93 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Monitor the error trend and whether the number of errors approaches the total number of bad-block replacements available. Info. A scrub-disk job logged with event 208 has completed and found no errors, or a disk being scrubbed (with no errors found) has been added to a disk group, or a user has aborted the job.
  • Page 94 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Info. Snapshot reset has completed. Recommended actions: ● No action is required. Info. Roll back of data in the indicated volume to data in the indicated snapshot has completed. Recommended actions: ●...
  • Page 95 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Check the license for what is allowed for the platform, make corrections as appropriate, and reinstall. Warning A timeout occurred while flushing the eMMC. Recommended actions: ● Restart the Storage Controller that logged this event. ●...
  • Page 96 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. Info. After a valid license is installed, this event is logged for each licensed feature to show the new license value for that feature. The event specifies whether the feature is licensed, whether the license is temporary, and whether the temporary license is expired.
  • Page 97 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity. ● Configure the disk as a spare. Info.
  • Page 98 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions or has not been programmed. Therefore, the MAC address is derived by using the controller serial number from flash. This event is only logged one time during bootup. Recommended actions: ●...
  • Page 99 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This event will most commonly occur after a power loss if the real-time clock battery has failed. The time may have been set to a time that is up to 5 minutes before the power loss occurred, or it may have been reset to 1980-01-01 00:00:00.
  • Page 100 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Check for any obstructions to the airflow. ● Check that there is a module or blank plate in every module slot in the enclosure. If the problem persists, replace the controller module that logged the error. Info.
  • Page 101 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing.
  • Page 102 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If event 359 has been logged for the indicated channel, indicating the condition no longer exists, no further action is required. ● If the condition persists, this indicates a hardware problem in one of the controller modules or in the controller enclosure midplane.
  • Page 103 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. Error An uncorrectable ECC error occurred in Storage Controller CPU memory more than once, indicating a probable hardware fault. Recommended actions: ●...
  • Page 104 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If event 37 was not logged, spare space was not available for reconstruction. Replace the failed disk with one of the same type and the same or greater capacity. Reconstruction should start and event 37 should be logged automatically.
  • Page 105 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This event indicates that a problem reported by event 460 is resolved. Recommended actions: ● No action is required. Error The indicated virtual pool reached its storage limit. There are three thresholds, two of which are user-settable.
  • Page 106 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. Addition of the indicated disk group completed successfully. Recommended actions: ● No action is required. Info. FPGA temperature has returned to the normal operating range and the speed of buses connecting the FPGA to downstream adapters has been restored.
  • Page 107 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Check that the storage system’s fans are running. ● Check that the ambient temperature is not too warm. The controller enclosure operating range is 5°C to 35°C (41°F to 95°F). The expansion enclosure operating range is 5°C to 40°C (41°F to 104°F).
  • Page 108 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Replace the controller module that logged this event. Error An invalid expansion-module connection was detected for the indicated disk channel. An egress port is connected to an egress port, or an ingress port is connected to an incorrect egress port. Recommended actions: ●...
  • Page 109 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Turn off the power for the controller enclosure, wait a few seconds, then turn it back ￭ Wait for the controller module to restart, then sign in again. ￭...
  • Page 110 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions The controller that logs this event indicates which channel (path) has the problem. For example, if the B controller logs the problem, the problem is in the chain of cables and expansion modules connected to the B controller module.
  • Page 111 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. IBEEM logged this event after monitoring the PHY for 30 minutes. Recommended actions: ●...
  • Page 112 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Be sure to record the lock key passphrase and the new lock ID. Info. The FDE import lock key has been set by a user. This is normally used to import into the system an FDE disk that was locked by another system.
  • Page 113 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. The system that was in the Full Disk Encryption degraded state is no longer degraded. The system has returned to normal operations. Recommended actions: ● No action is required. Error An error occurred while accessing the midplane SEEPROM to store or fetch Full Disk Encryption keys.
  • Page 114 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions The drawer has powered up. Disks in the drawer may take a few minutes to spin up. A rescan must complete before the updated drawer information will be available. Recommended actions: ●...
  • Page 115 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Info. The indicated volume, which was corrupted, has been recovered. Recommended actions: ● After verifying volume recovery, complete disk group recovery by running the 'recover disk- group complete' command. Info.
  • Page 116 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● The PSU in an enclosure does not have power supplied to it or has a hardware failure. ● The PSU is running with corrupted firmware. Recommended actions: ●...
  • Page 117 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ If the partner FRU is not degraded, remove and reinsert the indicated FRU. ○ If these recommended actions do not resolve the issue, the indicated FRU has probably failed and should be replaced When the problem is resolved, an event with the same code will be logged with Resolved severity.
  • Page 118 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Warning A temperature sensor is not within normal operating temperature thresholds but is within safe operating limits; or, a temperature sensor has been uninstalled. Recommended actions: ● If a temperature sensor has exceeded the normal operating range but is within safe operating limits.
  • Page 119 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ Check that the indicated FRU is in the indicated enclosure. ○ If the FRU is not in the enclosure, install the FRU immediately. ○ If the FRU is in the enclosure, ensure that the FRU is fully seated in its slot and that its latches are locked.
  • Page 120 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If uninstalled, the expander associated with the sideplane or drawer will have to be installed. Contact technical support. Otherwise, replace the module that contains the indicated expander. This could be a sideplane or a drawer. Contact technical support for replacement of the module containing the drawer expander.
  • Page 121 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions When the problem is resolved, an event with the same code will be logged with Resolved severity. Resolved A SES alert for a current sensor in the indicated enclosure has been resolved. Recommended actions: ●...
  • Page 122 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions If the snapshot space limit policy is set to delete snapshots, the system will begin to delete snapshots according to the snapshot retention priority setting until the snapshot space usage drops below the configured limit.
  • Page 123 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Info. A replication set was deleted. Recommended actions: ● No action is required. Error A replication failed to start. The replication was unsuccessful due to the condition specified within the event. Reasons for replication failure include but are not limited to shutdown of the secondary system, a loss of communication across the peer connection (which may be due to CHAP configuration changes), or a pool out-of-space condition.
  • Page 124 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions During the Failback Restore operation, the replication direction for a replication set was not reversed due to a failure. Recommended actions: ● If an issue with the peer connection was reported, check that appropriate interface cables are connected to the host ports defined in the peer connection.
  • Page 125 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● To restore the disk group, use the CLI dequarantine command to dequarantine the disk group. If more than one disk group is quarantined you must individually dequarantine each disk group, whether it is fault tolerant or not.
  • Page 126 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ If the disk group is still quarantined after performing the preceding steps, shut down both controllers and then power down the entire storage system. Power it back up, beginning with any disk enclosures (expansion enclosures), then the controller enclosure.
  • Page 127 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● When the problem is resolved, an event with the same code will be logged with Resolved severity. Resolved A previous Warning or Error condition for the Midplane Interconnect element has been resolved. The Midplane Interconnect element reports status associated with the interface between the SBB I/O module and the midplane.
  • Page 128 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Error A back-end cabling error was detected. Recommended actions: ● If the message says both controllers are connected with a undefined error type, one of the cables is incorrectly connected to a controller egress port forming a loop in the SAS topology.
  • Page 129 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● An unreachable SMTP server or a difference between the sender and SMTP server domains. ● Improper configuration. Recommended actions: ● Verify the configured parameters and ask the recipients to confirm that they received the message.
  • Page 130 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This event indicates that the available space in the system is insufficient to provide the level of full fault tolerance that is specified by the target spare capacity. Spare capacity availability can be influenced by operations that require available space in the system, such as reconstructing data from a failed disk.
  • Page 131 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If you receive this event when no new enclosures or IOMs have been added, please contact support. Info A disk has started a remanufacture/rebuild operation. The operation will result in reduced capacity.
  • Page 132 Warning A controller firmware update is available for your system. Recommended actions: ● Go to https://dell.com/support, enter your service tag and download the update. You can then use the Update Firmware function in PowerVault Manager to perform the update. Warning A disk firmware update is available for your system.
  • Page 133 Table 28. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. Events and event messages...

  • Page 134: Appendix A: Connecting To The Cli

    Connecting to the CLI You can access the CLI using a micro USB cable and terminal emulation software. 1. Connect a micro USB cable from a computer to the CLI port on controller module A . 2. Start a terminal emulator and configure the following display settings and the connection settings: Table 29.

  • Page 135: Microsoft Windows Drivers

    Supported host applications The following terminal emulator applications can be used to communicate with an ME5 Series controller module: Table 31. Supported terminal emulator applications Application Operating system PuTTY Microsoft Windows (all versions) Minicom Linux (all versions) Command-line interface When the computer detects a connection to the emulated serial port, the controller awaits input of characters from the computer using the command-line interface.

  • Page 136: Appendix B: Technical Specifications

    Technical specifications Enclosure dimensions Table 33. 2U12 and 2U24 enclosure dimensions Specification inches Height 87.9 mm 3.46 in Width 483 mm 19.01 in Depth (2U12) 618.7 mm 24.36 in Depth (2U24) 547.8 mm 21.56 in NOTE: ● The 2U12 enclosure uses 3.5" LFF disks. ●...
  • Page 137 Table 35. 2U12, 2U24, and 5U84 enclosure weights (continued) CRU/component 2U12 (kg/lb) 2U24 (kg/lb) 5U84 (kg/lb) EBOD enclosure (fully populated with 28/62 25/55 130/287 modules: maximum weight) NOTE: ● Weights shown are nominal, and subject to variances. ● Weights may vary due to different controller modules, IOMs, and power supplies; and differing calibrations between scales.
  • Page 138 Power cooling module Specifications for the PCM are provided in the following table. Table 38. 2U Power cooling module specifications Specification Measurement/description Dimensions (size) 84.3 mm high x 104.5 mm wide x 340.8 mm long ● X-axis length: 104.5 mm (4.11 in) ●...
  • Page 139 Table 39. 5U84 Power supply unit specifications (continued) Specification Measurement/description ● 91% @ 100% load Holdup time 5 ms from ACOKn high to rails out of regulation (see SBB v2 specification) Main inlet connector IEC60320 C20 with cable retention Weight 3 kg (6.6 lb) Cooling fans Two stacked fans: 80 mm x 80 mm x 38 mm (3.1 in.

  • Page 140: Appendix C: Standards And Regulations

    Standards and regulations Potential for radio frequency interference USA Federal Communications Commission (FCC) NOTE: This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
  • Page 141 Electromagnetic compatibility (EMC) compliance Table 41. EMC compliance standards System product type Standards approval Conducted emissions limit CFR47 Part 15B Class A levels EN 55032 CISPR Class A Radiated emissions limit levels CFR47 Part 15B Class A EN 55032 CISPR Class A Harmonics and flicker EN 61000-3-2/3 Immunity limit levels...

This manual is also suitable for:

Powervault me5012Powervault me5024Powervault me5084

Table of Contents