Dell EMC ME4084 Owner's Manual
  1. Manuals
  2. Brands
  3. Dell EMC Manuals
  4. Storage
  5. ME4084
  6. Owner's manual

Dell EMC ME4084 Owner's Manual

Hide thumbs Also See for ME4084:
Table of Contents

Quick Links

Dell EMC PowerVault ME4 Series Storage
System
Owner's Manual
Table of Contents
loading

Related Manuals for Dell EMC ME4084

Summary of Contents for Dell EMC ME4084

  • Page 1 Dell EMC PowerVault ME4 Series Storage System Owner’s Manual...
  • Page 2 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.

  • Page 3: Table Of Contents

    Contents 1 Storage system hardware......................5 Locate the service tag................................5 Enclosure configurations..............................5 Upgrading to dual-controller configuration........................6 Enclosure management................................ 6 Operation....................................6 Attach or remove the 2U enclosure front bezel......................8 Enclosure variants................................. 9 2U enclosure core product..............................10 2U enclosure front panel...............................
  • Page 4 3 Module removal and replacement....................39 ESD precautions.................................. 39 Dealing with hardware faults..............................39 Firmware updates................................40 Configuring partner firmware update......................... 40 Continuous operation during replacement........................40 Shutting down attached hosts............................40 Shutting down a controller module........................... 40 Using the ME Storage Manager..........................40 Using the CLI...................................41 Verifying component failure..............................

  • Page 5: Storage System Hardware

    Setting Up • The QRL code contains information unique to your system. It can be found on the information tag and the Your Dell EMC PowerVault ME4 Series Storage System hard copy document provided with your ME4 Series enclosure. •...

  • Page 6: Upgrading To Dual-Controller Configuration

    The controller module also provides a command-line interface (CLI) to support command line entry and scripting. For details, see the Dell EMC PowerVault ME4 Series Storage System CLI Guide for your system. Operation...
  • Page 7 • Read the hazardous voltage warning label affixed to power cooling modules. CAUTION: 5U84 enclosures only • To prevent overturning, drawer interlocks stop users from opening both drawers at the same time. Do not attempt to force open a drawer when the other drawer in the enclosure is already open. In a rack containing more than one 5U84 enclosure, do not open more than one drawer per rack at a time.

  • Page 8: Attach Or Remove The 2U Enclosure Front Bezel

    Figure 4. 2U24 enclosure system—rear orientation The 2U24 controller enclosure is equipped with dual-controllers (4-port SAS model shown). Figure 5. 5U84 enclosure system—front orientation Figure 6. 5U84 enclosure system—rear orientation The 5U84 controller enclosure is equipped with dual-controllers (4-port FC/iSCSI model shown). Attach or remove the 2U enclosure front bezel The 2U12 controller enclosure in Attaching or removing the 2U enclosure front bezel...

  • Page 9: Enclosure Variants

    The 2U chassis can be configured as a controller enclosure ME4012/ME4024, or an expansion enclosure ME412/ME424 as shown in 2U12 enclosure variants 2U24 enclosure variants. The 5U chassis can be configured as a controller enclosure ME4084 or an expansion enclosure ME484 as shown in 5U84 enclosure variants.

  • Page 10: 2U Enclosure Core Product

    Product Configuration PSUs FCMs Controller modules and IOMs ME4084 12 Gb/s direct dock SFF SAS ME484 12 Gb/s direct dock SFF SAS -Redundant PCMs must be compatible modules of the same type (both AC). -The fan control module (FCM) is a separate CRU (not integrated into a PCM).

  • Page 11: 2U Enclosure Rear Panel

    • For information about enclosure front panel LEDs, see 2U enclosure Ops panel. • For information about disk LEDs for LFF and SFF disk modules, see Verify front panel LEDs. • For information about the optional 2U enclosure front bezel, see Figure 7.
  • Page 12 3. IOM slot A 4. IOM slot B 2U rear panel components This section describes the controller module, expansion enclosure IOM, and power cooling module components. Controller module The top slot for holding controller modules is designated slot A and the bottom slot is designated slot B. The face plate details of the controller modules show the modules aligned for use in slot A.
  • Page 13 Figure 16. 4-port mini-SAS HD controller module detail 1. Back-end expansion SAS port 2. Ethernet port used by management interfaces 3. USB serial port (CLI) 4. 3.5 mm serial port (CLI) 5. 3.5 mm serial ports (service only) 6. Reset button 7.

  • Page 14: 5U84 Enclosure Core Product

    3. Fan Fail LED (Amber/blinking amber) 4. DC Fail LED (Amber/blinking amber) 5. On/Off switch 6. Power connector 7. Release latch LED behavior: • If any of the PCM LEDs are illuminated amber, a module fault condition or failure has occurred. •...

  • Page 15: 5U84 Enclosure Rear Panel

    Figure 20. 5U84 enclosure system - plan view of drawer accessed from front panel 1. Drawer front panel (shown as an edge in plan view) 2. Direction into the enclosure drawer slot (slot 0 or 1) 5U84 enclosure rear panel Alphabetic designators on controller modules and IOMs, and numeric designators on PSUs (Power Supply Units) and FCMs (Fan Control Modules) indicate slot sequencing for modules used in 5U84 enclosures.
  • Page 16 Figure 22. 5U84 controller enclosure—rear panel components (4-port SAS) 1. Controller module slot A 2. Controller module slot B 3. FCM slot 0 4. FCM slot 1 5. FCM slot 2 6. FCM slot 3 7. FCM slot 4 8. PSU slot 0 9.
  • Page 17 Figure 24. 5U84 expansion enclosure—rear panel components 1. IOM slot A 2. IOM slot B 3. FCM slot 0 4. FCM slot 1 5. FCM slot 2 6. FCM slot 3 7. FCM slot 4 8. PSU slot 0 9. PSU slot 1 NOTE: 5U84 controller enclosures support dual-controller module configuration only.

  • Page 18: 5U84 Enclosure Chassis

    The 5U84 enclosures use separate CRU modules for power supply and cooling/circulation, respectively. Power supply unit (PSU) shows the power supply module, which provides the enclosure with power connection and a power switch. Fan cooling module (FCM) shows the fan cooling module that is used in 5U84 enclosures. The FCM is smaller than the PCM, and five of them are used within the 5U enclosure to provide sufficient airflow throughout the enclosure.

  • Page 19: Operator's (Ops) Panel Leds

    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. • The drawer locks into place when fully opened and extended. To reduce finger pinching hazards, two latches must be released before the drawer can be pushed back into the drawer slot within the enclosure.

  • Page 20: 5U Enclosure Ops Panel

    Table 4. Ops panel functions Indicator Status System power Constant green: at least one PCM is supplying power Off: system not operating regardless of AC present Status/Health Constant blue: system is powered on and controller is ready Blinking blue (2 Hz): Enclosure management is busy Constant amber: module fault present Blinking amber: logical fault (2 seconds on, 1 second off) Unit identification display (UID)

  • Page 21: Controller Modules

    Table 5. Ops panel functions Indicator Status Unit identification display (UID) Green (seven-segment display: enclosure sequence) System power on/Standby Constant green: positive indication Constant amber: system in standby (not operational) Module fault Constant or blinking amber: fault present Logical status Constant or blinking amber: fault present Top drawer fault Constant or blinking amber: fault present in drive, cable, or sideplane...
  • Page 22 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 Description Definition cache, so a green cache status LED does not, by itself, indicate that any user data is at risk or that any action is necessary. Off—In a working controller, cache is clean (contains no unwritten data). This is an occasional condition that occurs while the system is booting. Blinking green—A CompactFlash flush or cache self-refresh is in progress, indicating cache activity.
  • Page 24 LED Description Definition Blinking amber — Hardware-controlled power-up or a cache flush or restore error. OK to remove Off — The controller is not prepared for removal. Blue — The controller module is prepared for removal. Identify White — The controller module is being identified. Cache status Green —...
  • Page 25 LED Description Definition Blinking amber — Hardware-controlled power-up or a cache flush or restore error. OK to remove Off — The controller is not prepared for removal. Blue — The controller module is prepared for removal. Identify White — The controller module is being identified. Cache status Green —...

  • Page 26: Compactflash

    Dell EMC PowerVault ME4 Series Storage System Owner's Manual within the procedure for replacing a controller module. Failure to use this procedure will result in the loss of data stored in the cache module. The CompactFlash must stay with the same enclosure.

  • Page 27: Supercapacitor Pack

    9/10 second off. NOTE: Remove the CompactFlash memory card only if recommended by Dell EMC technical support. Transportable cache only applies to single-controller configurations. In dual-controller configurations featuring one healthy partner controller, there is no need to transport failed controller cache to a replacement controller because the cache is duplicated between the controllers, provided that the volume cache is set to standard on all volumes in the pool owned by the failed controller.

  • Page 28: Troubleshooting And Problem Solving

    Fault isolation methodology Dell EMC PowerVault ME4 Series Storage Systems provide many ways to isolate faults. This section presents the basic methodology used to locate faults within a storage system, and to identify the pertinent CRUs affected.

  • Page 29: Performing Basic Steps

    • View the enclosure LEDs Use the ME Storage Manager The ME Storage Manager uses health icons to show OK, Degraded, Fault, or Unknown status for the system and its components. The ME Storage Manager enables you to monitor the health of the system and its components. If any component has a problem, the system health will be Degraded, Fault, or Unknown.

  • Page 30: Leds

    • Critical. A failure occurred that may cause a controller to shut down. Correct the problem immediately. • Error. A failure occurred that may affect data integrity or system stability. Correct the problem as soon as possible. • Warning. A problem occurred that may affect system stability, but not data integrity. Evaluate the problem and correct it if necessary. •...

  • Page 31: 2U Enclosure Leds

    2U enclosure LEDs PCM LEDs Under normal conditions, the PCM OK LEDs will be a constant green. Table 11. PCM LED states PCM OK Fan Fail AC Fail DC Fail Status (Green) (Amber) (Amber) (Amber) No AC power on any PCM No AC power on this PCM only AC present;...
  • Page 32 • If the CRU Fault LED is on, a fault condition is detected. • Restart this controller from the partner controller using the ME Storage Manager or CLI. • If the restart does not resolve the fault, remove the IOM and reinsert it. Disk drive carrier module LEDs Disk drive status is monitored by a green LED and an amber LED mounted on the front of each drive carrier module, as shown in the following figure.

  • Page 33: 5U84 Enclosure Leds

    Activity LED (Green) Fault LED (Amber) Status/condition* *If multiple conditions occur simultaneously, the LED state behaves as indicated by the condition listed earliest in the table, as rows are read from top to bottom. Controller module and IOM LEDs Controller module and IOM LEDs pertain to controller modules and expansion modules, respectively. •...
  • Page 34 Fan cooling module LEDs Fan cooling module for a visual description of the Fan Cooling Module (FCM) faceplate. Table 16. FCM LED descriptions Status/description Module OK Constant green indicates that the FCM is working correctly. Off indicates the fan module has failed. Follow the procedure in Replacing a fan cooling module (FCM) to replace the fan controller module.

  • Page 35: Troubleshooting 2U Enclosures

    DDIC LEDs The DDIC supports LFF 3.5" and SFF 2.5" disks. The following figure shows the top panel of the DDIC as viewed when the disk is aligned for insertion into a drawer slot. Figure 36. LEDs: DDIC – 5U enclosure disk slot in drawer 1.

  • Page 36: Pcm Faults

    Table 20. 2U alarm conditions Status Severity Alarm PCM alert - loss of DC power from a single PCM Fault – loss of redundancy PCM fan fail Fault – loss of redundancy SBB module detected PCM fault Fault PCM removed Configuration error None Enclosure configuration error (VPD)

  • Page 37: Thermal Alarm

    Table 22. Thermal monitoring recommended actions Symptom Cause Recommended action If the ambient air is below 25ºC The first stage in the thermal 1. Check the installation for any airflow restrictions at either the (77ºF), and the fans are control process is for the fans to front or back of the enclosure.

  • Page 38: Thermal Considerations

    Status Severity Ops panel communication error (I Fault – critical RAID error Fault – critical SBB I/O module fault Fault – critical SBB I/O module removed Warning Drive power control fault Warning – no loss of drive power Drive power control fault Fault –...

  • Page 39: Module Removal And Replacement

    Module removal and replacement ESD precautions Before you begin any of the procedures, consider the following precautions and preventive measures. Preventing electrostatic discharge To prevent electrostatic discharge (ESD) from damaging the system, be aware of the precautions to consider when setting up the system or handling parts.

  • Page 40: Firmware Updates

    • The ME Storage Manager and CLI provide an option for enabling or disabling PFU for the partner controller as Dell EMC PowerVault ME4 Series Storage System Administrator’s Guide . To enable or disable the described in the setting via the CLI, use the set advanced-settings command, and set the partner-firmware-upgrade parameter. See Dell EMC PowerVault ME4 Series Storage System CLI Guide for more information about command parameter syntax.

  • Page 41: 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. Dell EMC PowerVault ME4 Series Storage System Administrator’s Guide for additional information. •...

  • Page 42: Attach Or Remove The 2U Enclosure Front Bezel

    5-This model supports 10Gb/s or 1Gb/s speeds (used for iSCSI host connection). Table 26. High-density ME4 Series enclosure models High-density 4-port controller enclosure matrix–5U ME4 Series (2.5"/3.5") 84-drive controller enclosures Model Description Form ME4084 Fibre Channel (16Gb/s) SFP 5U84 ME4084 Internet SCSI (10GbE) SFP 5U84 ME4084...

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

    Import the keys for the disk drives so that the drive content becomes available. See the Dell EMC PowerVault ME4 Series Storage System Administrator’s Guide or Dell EMC PowerVault ME4 Series Storage System CLI Guide for more information. Before you begin any of the procedures, see the precautions.
  • Page 44 Figure 39. 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 45 Figure 42. Installing an LFF drive carrier module (2 of 2) 6. Use the ME Storage Manager or CLI to verify the following: • Health of the new disk drive is OK • Green Disk Activity LED is on/blinking • Ops panel states show no amber module faults Replacing an SFF drive carrier module The replacement procedures for SFF drive carrier modules are the same for LFF modules, except that the SFF drive carrier modules are...
  • Page 46 Figure 44. 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 47 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 48 Figure 48. Removing and installing a 2.5-inch disk drive into a drive carrier module 1. Drive carrier module 2. Disk drive 3. Screws (4) Module removal and replacement...
  • Page 49 Figure 49. Removing and installing a 3.5-inch disk drive into a drive carrier module 1. Drive carrier module 2. Disk drive 3. Screws (4) Installing a disk into a drive carrier module Many repairs can only be performed by a certified service technician. Only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team.
  • Page 50 Figure 50. Removing a DDIC (1 of 2) 4. Pull the DDIC upwards and out of the drawer slot. Figure 51. Removing a DDIC (2 of 2) Module removal and replacement...
  • Page 51 Installing a replacement disk into the DDIC Replacement disk drives are not shipped with a new DDIC. The failed disk drive must be removed from its DDIC and the replacement disk drive must be installed in the DDIC. Module removal and replacement...
  • Page 52 Module removal and replacement...
  • Page 53 4. Close the drawer. Populating drawers The general guidelines for populating a drawer with DDICs are provided in the Dell EMC PowerVault ME4 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 54: Replacing A Controller Module Or Iom

    • Bottom drawer–back row Replacing a Controller Module or IOM The 2U enclosures support single or dual-controller module configurations. The 5U84 enclosures support only dual-controller module configurations. If a controller module fails, the controller will fail over and run on a single controller module until the redundancy is restored. For 2U enclosures, an controller module must be installed in slot A, and either a controller module or controller blank must be installed in slot B to ensure sufficient air flow through the enclosure during operation.
  • Page 55 Figure 53. CompactFlash memory card location 1. CompactFlash memory card 2. Controller module viewed from back Confirm that transporting CompactFlash is the appropriate action to take as discussed in the ME4 Series Storage System Deployment Guide. Refer to CompactFlash memory card location when performing the step-procedure below.
  • Page 56 Figure 54. Removing a controller module from an enclosure NOTE: Removing a controller module shows a 4-port SAS controller module. However, all of the controller modules use the same latching mechanism. 6. Swing the latch handle open, then grip the latch handle and ease the controller module forward from the slot. 7.
  • Page 57 Removing an IOM Before you begin any procedure, see precautions. NOTE: Considerations for removing IOM: • Expansion enclosures are equipped with two IOMs. You may hot-swap a single IOM in an operational enclosure. • If replacing both IOMs,—and the expansion enclosure is online—you can hot-swap the IOM in slot “A”, and then hot-swap the IOM slot “B”, verifying each module is recognized by the controller.

  • Page 58: Replacing A Power Supply Unit (Psu)

    3. Ensuring that the IOM is level, slide it into the enclosure as far as it will go. An IOM that is only partially seated will prevent optimal performance of the expansion enclosure. Verify that the IOM is fully seated before continuing.

  • Page 59: Replacing A Fan Cooling Module (Fcm)

    Figure 57. Removing a PSU (2 of 2) 9. While supporting the PSU with both hands, remove it from the enclosure. 10. If replacing both PSUs, repeat steps 5 through 9. NOTE: The PSU slot must not be empty for more than 2 minutes while the enclosure is powered. Installing a PSU If replacing both PSUs, the enclosure must be powered off via an orderly shutdown using the management interfaces.

  • Page 60: Replacing A Power Cooling Module (Pcm)

    Figure 58. Removing an FCM (1 of 2) 4. While supporting the FCM with both hands, remove it from the enclosure. Figure 59. Removing an FCM (2 of 2) NOTE: The FCM slot must not be empty for more than 2 minutes while the enclosure is powered. Installing an FCM You can hotswap the replacement of a single FCM;...
  • Page 61 Before you begin any of the procedures, see the precautions. NOTE: The illustrations show PCM module replacement within the right slot as you view the enclosure rear panel. To replace a PCM in the left slot, first rotate the module 180º about its longitudinal axis, so that it properly aligns with its connectors on the back of the midplane.

  • Page 62: Completing The Component Installation Process

    Figure 61. Removing a PCM (2 of 2) NOTE: The remove PCM illustrations show a chassis configured as a 4-port FC/iSCSI controller enclosure. The procedure applies to all 2U controller enclosures and expansion enclosures. 9. If replacing two PCMs, repeat steps 5 through 8. Installing a PCM Refer to Figure 60.

  • Page 63: Using Leds

    c) Data host last (if powered down for maintenance purposes). Allow time for each device to complete its Power On Self Tests (POST) before proceeding. 2. Perform a rescan to force a fresh discovery of all expansion enclosures connected to the controller enclosure. This step clears the internal SAS layout information, reassigns enclosure IDs, and ensures the enclosures are displayed in the proper order.

  • Page 64: Events And Event Messages

    Events and event messages When an event occurs in a storage system, an event message is recorded in the system’s event log and, depending on the system’s event notification settings, can also be sent to users (using email) and host-based applications (using SNMP or SMI-S). NOTE: A best practice is to enable notifications to be sent for events having severity Warning and higher.
  • Page 65 Number Severity Description/Recommended actions • If the indicated disk group is not RAID 6, it is operating with degraded health due to the failure of one disk. If a spare of the proper type and size is present, that spare is used to automatically reconstruct the disk group.
  • Page 66 Number Severity Description/Recommended actions Info. Either: • Disk group creation completed successfully. • Disk group creation failed immediately. The user was given immediate feedback that it failed at the time they attempted to add the disk group. Recommended actions: • No action is required.
  • Page 67 Number Severity Description/Recommended actions • If the associated disk group is offline and you do not want to use the trust command, perform these steps: • Delete the disk group (CLI remove disk-groups command). • Clear the indicated disk’s metadata so the disk can be re-used (CLI clear disk-metadata command).
  • Page 68 Number Severity Description/Recommended actions • Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module, expansion module, or power supply. • Check whether any disks in the disk group have logged SMART events or unrecoverable read errors. •...
  • Page 69 Number Severity Description/Recommended actions Recommended actions: • No action is required. Warning The sensors monitored a temperature or voltage in the warning range. When the problem is resolved, event 47 is logged for the component that logged event 39. If the event refers to a disk sensor, disk behavior may be unpredictable in this temperature range. Check the event log to determine if more than one disk has reported this event.
  • Page 70 Number Severity Description/Recommended actions Recommended actions: • No action is required. Error A correctable ECC error occurred in cache memory more than 10 times during a 24-hour period, indicating a probable hardware fault. Recommended actions: • Replace the controller module that logged this event. Warning A correctable ECC error occurred in cache memory.
  • Page 71 Number Severity Description/Recommended actions • Resolve any non-disk hardware problems, especially a cooling problem or a faulty power supply. • If the disk is in a disk group that uses a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a different disk group and replace the faulty disk.
  • Page 72 Number Severity Description/Recommended actions • If the failed disk was a global spare, configure the new disk as a global spare. • If the failed disk was a dedicated spare, configure the new disk as a dedicated spare for the same disk group.
  • Page 73 Number Severity Description/Recommended actions Recommended actions: • Replace each failed 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 74 Number Severity Description/Recommended actions Warning The mirrored configuration retrieved by this controller from the partner controller has a configuration level that is too high for the firmware in this controller to process. The local flash configuration will be used instead. Recommended actions: •...
  • Page 75 Number Severity Description/Recommended actions Info. The indicated volume has been deleted from the indicated pool. Recommended actions: • No action is required. Info. The statistics for the indicated volume have been reset. Recommended actions: • No action is required. Info. Ownership of the indicated disk group has been given to the other controller.
  • Page 76 Number Severity Description/Recommended actions • No action is required. Warning The controller has detected an invalid disk dual-port connection. This event indicates that a controller host port is connected to an expansion port, instead of to a port on a host or a switch. Recommended actions: •...
  • Page 77 Number Severity Description/Recommended actions Info. The Management Controller (MC) has re-established communication with the Storage Controller (SC). Recommended actions: • No action is required. Info. New firmware has been loaded in the Management Controller (MC). Recommended actions: • No action is required. Info.
  • Page 78 Number Severity Description/Recommended actions • If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN information for this controller module on all hosts that access it. Warning The host WWNs (node and port) previously presented by the partner controller module, which is currently offline, are unknown.
  • Page 79 Number Severity Description/Recommended actions • It contains data in a format that is not supported by this system. The controller does not support linear disk groups. Recommended actions: • If the disk group was quarantined because not all of its disks are accessible: •...
  • Page 80 Number Severity Description/Recommended actions • If the problem is not outside of the storage system, replace the controller module that logged this event. Info. The error statistics for the indicated disk have been reset. Recommended actions: • No action is required. Info.
  • Page 81 Number Severity Description/Recommended actions Info. The controller module's supercapacitor pack has started charging. This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache and put the system in write-through mode. When the fault is resolved, event 191 is logged to indicate that write-back mode has been restored.
  • Page 82 Number Severity Description/Recommended actions Info. A fan has failed. This indicates that a trigger condition has occurred that has caused the auto-write-through feature to disable write-back cache and put the system in write-through mode. When the fault is resolved, event 201 is logged to indicate that write-back mode has been restored.
  • Page 83 Number Severity Description/Recommended actions The scrub checks disks in the disk group for the following types of errors: • Data parity errors for a RAID 3, 5, 6, or 50 disk group. • Mirror verify errors for a RAID 1 or RAID 10 disk group. •...
  • Page 84 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. Warning A scrub-disk job logged with event 208 has been aborted by a user, or has reassigned a disk block.
  • Page 85 Number Severity Description/Recommended actions Info. An uncommitted snapshot has been deleted. Removal of the indicated snapshot completed successfully. Recommended actions: • No action is required. Error A supercapacitor failure occurred in the controller. Recommended actions: • Replace the controller module that logged this event. Warning The supercapacitor pack is near end of life.
  • Page 86 Number Severity Description/Recommended actions Error A roll back failed. Failed to execute roll back for a particular LBA (logical block address) range of the indicated parent volume. Recommended actions: • Restart the roll-back operation. Error A roll back failed to end because the snap pool could not be initialized. he roll back is in a suspended state. Recommended actions: •...
  • Page 87 Number Severity Description/Recommended actions Recommended actions: • All the snapshots associated with this snap pool are invalid and you may want to delete them. However, the data in the master volume can be recovered by converting it to a standard volume. Error An enclosure management processor (EMP) detected a serious error.
  • Page 88 Number Severity Description/Recommended actions This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache and put the system in write-through mode. When the fault is resolved, event 241 is logged to indicate that write-back mode has been restored. Recommended actions: •...
  • Page 89 Number Severity Description/Recommended actions • No action is required. Info. Data written to a snapshot after it was created has been deleted. The snapshot now represents the state of the parent volume when the snapshot was created. Recommended actions: • No action is required.
  • Page 90 Number Severity Description/Recommended actions Warning The indicated spare disk is missing. Either it was removed or it is not responding. Recommended actions: • Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity.
  • Page 91 Number Severity Description/Recommended actions Info. PHY fault isolation has been enabled or disabled by a user for the indicated enclosure and controller module. Recommended actions: • No action is required. Warning The indicated PHY has been disabled, either automatically or by a user. Drive PHYs are automatically disabled for empty disk slots or if a problem is detected.
  • Page 92 Number Severity Description/Recommended actions Recommended actions: • No action is required. Info. A mirror component break command completed. Recommended actions: • No action is required. Info. A mirror component split command completed. Recommended actions: • No action is required. Info. A mirror set join command completed.
  • Page 93 Number Severity Description/Recommended actions Info. Silvering was started for a mirror component. Recommended actions: • No action is required. Info. ilvering completed for a mirror component. Recommended actions: • No action is required. Info. Silvering was aborted for a mirror component. Recommended actions: •...
  • Page 94 Number Severity Description/Recommended actions Recommended actions: • No action is required. Info. DDR memory clock frequency has changed to low. Recommended actions: • No action is required. Info. The controller has detected I C errors that may have been fully recovered. Recommended actions: •...
  • Page 95 Number Severity Description/Recommended actions Recommended actions: • No action is required. Error The indicated controller module has failed. This event can be ignored for a single-controller configuration. Recommended actions: • If this is a dual-controller system, replace the failed controller module. The module’s Fault/Service Required LED will be illuminated (not blinking).
  • Page 96 Number Severity Description/Recommended actions • No action is required. Info. Expander Controller (EC) assert data and stack-dump data have been cleared. Recommended actions: • No action is required. Warning SAS topology has changed on a host port. At least one PHY has gone down. For example, the SAS cable connecting a controller host port to a host has been disconnected.

  • Page 97: Events (Continued)

    Number Severity Description/Recommended actions Recommended actions: • Take appropriate action based on the indicated problem. Info. A scheduled task was initiated. Recommended actions: • No action is required. Critical, Error, The scheduler experienced a problem with the indicated task. or Warning Recommended actions: •...
  • Page 98 Number Severity Description/Recommended actions • No action is required. Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a log-collection system. Recommended actions: • Transfer the log file to the log-collection system. Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data.
  • Page 99 Number Severity Description/Recommended actions • To make space for a new snapshot because the maximum number of replication snapshots per system was reached. • To make space for an unknown reason. A virtual snapshot was deleted because the user-specified snapshot space limit was exceeded. Recommended actions: •...
  • Page 100 Number Severity Description/Recommended actions • A primary volume conflict exists. • You cannot delete the volume from a remote system. • You cannot remove the volume because it is the primary volume. Recommended actions: • If any of the above problems exist, resolve them. Then repeat the remove operation with a valid volume. Info.
  • Page 101 Number Severity Description/Recommended actions Error A replication was aborted due to an error on a secondary volume. Recommended actions: • Verify that the secondary volume is valid and that the system where the volume resides is accessible. Info. A replication was skipped. Recommended actions: •...
  • Page 102 Number Severity Description/Recommended actions • The communication link is busy or experienced an error. • The snapshot being used for the replication is invalid. • There was a problem establishing proxy communication. • The replication is being automatically retried according to policies in place. If the issue is resolved before retries are exhausted, the replication will continue on its own.
  • Page 103 Number Severity Description/Recommended actions This can occur for several reasons, such as: • The communication link is busy or experienced an error. • The local initiator experienced an error. Recommended actions: • Verify that there are no network issues preventing communication between the local and remote storage systems.
  • Page 104 Number Severity Description/Recommended actions Recommended actions: • Ensure that all disks are installed and all enclosures are connected and powered on. When the problem is resolved, event 461 is logged. Info. The indicated disk group that was missing from the indicated virtual pool was recovered. This event indicates that a problem reported by event 460 is resolved.
  • Page 105 Number Severity Description/Recommended actions Info. The indicated virtual pool was deleted. Recommended actions: • No action is required. 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 106 Number Severity Description/Recommended actions Recommended actions: • No action is required. Info. Replication was queued because the secondary volume is in an offline state. Recommended actions: • To allow the replication to proceed, resolve the problem that is preventing access to the secondary volume.
  • Page 107 Number Severity Description/Recommended actions Recommended actions: • Restart the Storage Controller that logged this event. • If this event is logged again, shut down the Storage Controller and replace the CompactFlash. • If this event is logged again, shut down the Storage Controller and replace the controller module. Warning One of the PCIe buses is running with fewer lanes than it should.
  • Page 108 Number Severity Description/Recommended actions • If events 485 and 486 are both logged at approximately the same time, wait at least 5 minutes for the automatic recovery process to complete. Then sign in and confirm that both controller modules are operational.
  • Page 109 Number Severity Description/Recommended actions • No action is required. Info. Reinitialization of a snap pool completed. Recommended actions: • No action is required. Warning The algorithm for best-path routing selected the alternate path to the indicated disk because the I/O error count on the primary path reached its threshold.
  • Page 110 Number Severity Description/Recommended actions When a disk fails, reconstruction is performed using a spare disk. When the failed disk is replaced, the data that was reconstructed in the spare disk (and any new data that was written to it) is copied to the disk in the slot where the data was originally located.
  • Page 111 Number Severity Description/Recommended actions Recommended actions: • No action is required. Info. Service debug access to the system has been enabled or disabled by a user. Allowing service debug access may have security implications. After the diagnosis is complete you may want to disallow such access. Recommended actions: •...
  • Page 112 Number Severity Description/Recommended actions Recommended actions: • Ensure that the imported disk(s) are integrated into the system. Info. The system was set to the FDE secured state by a user. Full Disk Encryption is now enabled. Disks removed from this system will not be readable unless they are imported into another system.
  • Page 113 Number Severity Description/Recommended actions Error An error occurred while accessing the midplane SEEPROM to store or fetch Full Disk Encryption keys. The midplane’s memory is used to store the FDE lock key. Recommended actions: • The midplane may need to be replaced if the error persists. Warning A scrub-disk-group job encountered an error at the indicated logical block address.
  • Page 114 Number Severity Description/Recommended actions Error Expander Controller firmware detected that the partner Expander Controller (EC) firmware is incompatible with the enclosure. As a preventative measure, the Expander Controller (EC) disabled all PHYs and reported the short enclosure status page in the supported diagnostic list. Recommended actions: •...
  • Page 115 Number Severity Description/Recommended actions The indicated disk experienced a number of disk errors in excess of a configured threshold. Because the disk is part of a non-fault tolerant disk group, the system has set the disk status to degraded instead of failed. Recommended actions: •...
  • Page 116 Number Severity Description/Recommended actions Critical A data block in a volume was fenced by the controller due to lost data. This event describes volume information for a fenced data block. It is logged in conjunction with event 542, which describes disk group and disk information for the data block. Recommended actions: •...

  • Page 117: Events (Continued)

    Events (continued) Number Severity Description/Recommended actions Critical The read data path between the Storage Controller and the disk drives was detected to be unreliable. The Storage Controller took action to correct this. Recommended actions: • Replace the controller. Error An EMP reported one of the following for a power supply unit (PSU): •...
  • Page 118 Number Severity Description/Recommended actions • If a hardware failure has been detected and all fans in the indicated FRU have failed. • Inspect the system health information to determine which FRU contains the affected fans. Event 551 or 558 should give further information on the containing FRUs. •...
  • Page 119 Number Severity Description/Recommended actions • If the error persists, check that all modules in the enclosure are fully seated in their slots and that their latches, if any, are locked. • If this does not resolve the issue, note down the FRU. Ensure the partner FRU is not degraded. If the partner FRU is degraded, contact technical support.
  • Page 120 Number Severity Description/Recommended actions Recommended actions: If a voltage sensor has exceeded the normal operating range but is within safe operating limits: • Check that all modules in the enclosure are fully seated in their slots and that their latches are locked. •...
  • Page 121 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 122 Number Severity Description/Recommended actions Resolved A SES alert for a current sensor in the indicated enclosure has been resolved. Recommended actions: • No action is required. Error An Enclosure Management Processor (EMP) reported an alert condition on a fan control module. A fan module in the enclosure has failed.
  • Page 123 Number Severity Description/Recommended actions system to avoid risk of damage. Replace the chassis FRU immediately. If a temperature sensor reaches a shutdown value, the controller module will automatically shut down. For shutdown values, see information about temperature sensors in your product's installation guide. •...
  • Page 124 Number Severity Description/Recommended actions The EMP reported an alert condition in a drawer of the enclosure: • The drawer power is bad. • Both drawer slices are in reset or are not responding. Recommended actions: • Contact technical support. • When the problem is resolved, an event with the same code will be logged with Resolved severity.
  • Page 125 Number Severity Description/Recommended actions • No action is required. Error Allocated snapshot space exceeded the configured percentage limit of the virtual pool. 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 126 Number Severity Description/Recommended actions 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 127 Number Severity Description/Recommended actions 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. • If the appropriate cables are connected, check the cables and any network switches for problems. •...
  • Page 128 Number Severity Description/Recommended actions being quarantined. For example, if the disk group was reconstructing before being quarantined, the disk group will resume reconstructing where it stopped • For a linear disk group, if you want to find where parity is incorrect, use the CLI scrub vdisk command with the fix parameter disabled.
  • Page 129 Number Severity Description/Recommended actions • Check that the SAS expansion cables are connected between each enclosure in the storage system and that they are fully seated. (Do NOT remove and reinsert the cables because this can cause problems with additional disk groups.) •...
  • Page 130 Number Severity Description/Recommended actions • Contact technical support. Provide logs to technical support personnel for analysis. • 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 131 Number Severity Description/Recommended actions 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. Check back-end cabling from each controller egress port to determine the incorrect connection.
  • Page 132 Number Severity Description/Recommended actions • Verify the configured parameters and ask the recipients to confirm that they received the message. Info. An alert condition was detected on an internal chassis SAS connector. The event message specifies the location of the internal SAS connector in the chassis. Recommended actions: •...

  • Page 133: Events Sent As Indications To Smi-S Clients

    Management Controller configuration parameters were set. One or more configuration parameters associated with the Management Controller (MC) have been changed, such as configuration for SNMP, SMI-S (not supported on the ME4084), email notification, and system strings (system name, system location, etc.).

  • Page 134: Using The Trust Command

    Before trusting a disk group, carefully read the cautions and procedures for using the trust command in the Dell EMC PowerVault ME4 Series Storage System CLI Reference Guide and online help. If you are uncertain whether to use this command, contact technical support for assistance.

  • Page 135: A Connecting To The Cli Port Using A Serial Cable

    Connecting to the CLI port using a serial cable You can access the CLI using the 3.5mm Stereo plug or USB CLI port and terminal emulation software. 1. Connect the 3.5mm/DB9 serial cable from a computer with a serial port to the 3.5mm stereo plug CLI port on controller A. Alternatively, connect a generic mini-USB cable (not included) from a computer to the USB CLI port on controller A .

  • Page 136: Mini-Usb Device Connection

    Your computer configuration determines which COM port is used for the Disk Array USB Port. Verify the appropriate COM port for use with the CLI. 4. If necessary, press Enter to display login prompt. a) Type the user name of a user with the manage role at the login prompt and press Enter. b) Type the password for the user at the Password prompt and press Enter.

  • Page 137: Microsoft Windows Drivers

    Dell.com/support and search for ME4 Series USB driver. 2. Download the ME4 Series Storage Array USB Utility file from the Dell EMC support site. 3. Follow the instructions on the download page to install the ME4 Series USB driver. Known issues with the CLI port and mini-USB cable on Microsoft...

  • Page 138: B Technical Specifications

    Technical specifications Enclosure dimensions Table 30. 2U enclosure dimensions Specification Metric units Imperial units Overall enclosure height (2U) 87.9 mm 3.46 in Width across mounting flange (located on front of 483 mm 19.01 in chassis) Width across body of enclosure 443 mm 17.44 in 2U12 –...
  • Page 139 Enclosure weights CRU/component 2U12 (kg/lb) 2U24 (kg/lb) 5U84 (kg/lb) Storage enclosure (empty) 4.8/10.56 4.8/10.56 64/141 Disk drive carrier 0.9/1.98 0.3/0.66 0.8/1.8 Blank disk drive carrier (air management 0.05/0.11 0.05/0.11 — sled) Power Cooling Module (PCM) 3.5/7.7 3.5/7.7 — Power Supply Unit (PSU) —...
  • Page 140 Specification Measurement/description Altitude, non-operating -100 to 12,192 meters (-330 to 40,000 feet) Shock, operating 5.0 g, 10 ms, ½ sine pulses, Y-axis Shock, non-operating 2U enclosures: 30.0 g, 10 ms, ½ sine pulses 5U84 enclosures: 30.0 g, 10 ms, ½ sine pulses (Z-axis); 20.0 g, 10 ms, ½ sine pulses (X- and Y-axes) Vibration, operating 0.21 Grms 5 Hz to 500 Hz random...
  • Page 141 Specification Measurement/description Operating temperature 0 to 57ºC (32ºF to +135ºF) Hot pluggable Switches and LEDs AC mains switch and four status indicator LEDs Enclosure cooling Dual axial cooling fans with variable fan speed control Power supply unit Table 34. 5U84 Power supply unit specifications Specification Measurement/description Maximum output power...

  • Page 142: C Standards And Regulations

    System product type approval Specification Safety compliance UL 60950-1 second edition IEC 60950-1 EN 60950-1 Dell EMC compliance Table 36. Dell EMC compliance specifications System product type approval Specification Conducted emissions limit levels CFR47 Part 15B Class A Standards and regulations...
  • Page 143 System product type approval Specification EN55022 Class A CISPR Class A Radiated emissions limit levels CFR47 Part 15B Class A EN55022 Class A CISPR Class A Harmonics and flicker EN61000-3-2/3 Immunity limit levels EN55024 AC power cable specifications 1. United States of America – Must be NRTL Listed (National Recognized Test Laboratory – e.g., UL): Chassis form factor 2U12/2U24 5U84...

This manual is also suitable for:

Me4024Powervault me4 series

Table of Contents