Dell EMC PowerVault ME4 Series Storage System Owner’s Manual December 2020 Rev.
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. © 2018 – 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Storage system hardware............................................................................................. 5 Locate the service tag....................................................................................................................................................... 5 Enclosure configurations...................................................................................................................................................
Chapter 3: Module removal and replacement............................................................................... 43 ESD precautions................................................................................................................................................................ 43 Dealing with hardware faults.......................................................................................................................................... 44 Firmware updates.......................
1 Storage system hardware This chapter describes the front-end and back-end components of ME4 Series enclosures. Some of the modules within the enclosure are replaceable as described in Module removal and replacement on page 43. The types of modules and other components that can be replaced are defined below: ● CRU: Customer-replaceable Unit ● FRU: Field-replaceable Unit (requires service expertise) The terms CRU and FRU are used throughout this document.
These same chassis form factors are used for the supported expansion enclosures; but with I/O modules instead of controller modules. The 2U12 and 2U24 enclosures support single or dual-controller module configurations, but the 5U84 enclosure only supports a dual-controller module configuration. If a partner controller module fails, the storage system will fail over and run on a single controller module until the redundancy is restored.
Enclosure management The enclosure is mechanically and electrically compliant with the Storage Bridge Bay (SBB) v 2.1 specification. SBB modules actively manage the enclosure. Each module has a SAS expander with its own storage enclosure processor (SEP) that provides a SES target for a host to interface to, through the ANSI SES (SCSI Enclosure Services) standard. If one of these modules fails, the other module continues to operate.
Figure 2. 2U12 enclosure system—rear orientation The 2U12 controller enclosure in 2U12 enclosure system—rear orientation on page 8 is equipped with 2 controllers (4–port FC/ ISCSI model shown). Figure 3. 2U24 enclosure system—front orientation 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 front bezel of a 2U enclosure The following figure shows a partial view of a 2U12 enclosure: Figure 7. Attaching or removing the 2U enclosure front bezel To attach the front bezel to the 2U enclosure: 1. 2. 3. 4.
To remove the bezel from the 2U enclosure, reverse the order of the preceding steps. NOTE: See Enclosure variants for details about various enclosure options. 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 and 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.
Table 3. 5U84 enclosure variants Product Configuration PSUs 1 FCMs 2 Controller modules and IOMs 3 ME4084 12 Gb/s direct dock SFF SAS 2 5 2 ME484 12 Gb/s direct dock SFF SAS 2 5 2 1 Redundant PCMs must be compatible modules of the same type (both AC). 2 The fan control module (FCM) is a separate CRU (not integrated into a PCM). 3 Supported controller modules include 4-port FC/iSCSI, 4-port HD mini-SAS, and 4-port iSCSI 10Gbase-T.
2U enclosure rear panel Alphabetic designators on controller modules or IOMs and numeric designators on PCMs indicate slot sequencing for the modules used in 2U enclosures. Controller modules, IOMs, and PCMs are available as CRUs. The ME4 Series RBODs use 4-port controller modules. These RBODs support the ME412/ME424/ME484 EBODs for optionally adding storage. Figure 10. 2U controller enclosure—rear panel components (4-port FC/iSCSI) 1. Power cooling module slot 0 3. Controller module slot A 2.
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. In this orientation, the controller module latch shown at the bottom of the module and it is in a closed/locked position.
Figure 16. 4-port mini-SAS HD controller module detail 1. 3. 5. 7. Back-end expansion SAS port USB serial port (CLI) 3.5 mm serial ports (service only) SAS ports (ports 3, 2, 1, 0) 2. Ethernet port used by management interfaces 4. 3.5 mm serial port (CLI) 6. Reset button Expansion enclosure IOM The following figure shows the IOM used in supported expansion enclosures for adding storage. Ports A/B/C ship configured with 12 Gb/s mini-SAS HD (SFF-8644) external connectors. Figure 17.
Figure 18. Power cooling module (PCM) 1. 3. 5. 7. PCM OK LED (Green) Fan Fail LED (Amber/blinking amber) On/Off switch Release latch 2. AC Fail LED (Amber/blinking amber) 4. DC Fail LED (Amber/blinking amber) 6. Power connector LED behavior: ● If any of the PCM LEDs are illuminated amber, a module fault condition or failure has occurred. ● For a detailed description of PCM LED behavior, see 2U enclosure LEDs on page 34.
5U84 enclosure front panel Figure 19. 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. NOTE: See 5U84 enclosure DDIC LEDs on page 38 for 5U84 (LFF disks) DDIC LED behavior. Figure 20. 5U84 enclosure system - plan view of drawer accessed from front panel 1.
Figure 21. 5U84 controller enclosure—rear panel components (4-port FC/iSCSI) 1. 3. 5. 7. 9. Controller module slot A FCM slot 0 FCM slot 2 FCM slot 4 PSU slot 1 2. 4. 6. 8. Controller module slot B FCM slot 1 FCM slot 3 PSU slot 0 Figure 22. 5U84 controller enclosure—rear panel components (4-port SAS) 1. 3. 5. 7. 9. Controller module slot A FCM slot 0 FCM slot 2 FCM slot 4 PSU slot 1 2. 4. 6. 8.
Figure 23. 5U84 controller enclosure—rear panel components (4-port iSCSI 10Gbase-T) 1. 3. 5. 7. 9. Controller module slot A FCM slot 0 FCM slot 2 FCM slot 4 PSU slot 1 2. 4. 6. 8. Controller module slot B FCM slot 1 FCM slot 3 PSU slot 0 Figure 24. 5U84 expansion enclosure—rear panel components 1. 3. 5. 7. 9. IOM slot A FCM slot 0 FCM slot 2 FCM slot 4 PSU slot 1 2. 4. 6. 8.
Expansion module The 5U84 expansion enclosure uses the same IOMs that are used by 2U12 and 2U24 enclosures. Power supply module This figure shows the power supply unit that is used in 5U controller enclosures and optional 5U84 expansion enclosures. Figure 25. Power supply unit (PSU) 1. 3. 5. 7. Module release latch PSU Fault LED (Amber/blinking amber) Power OK LED (Green) Power switch 2. Handle 4. AC Fail LED (Amber/blinking amber) 6.
5U84 enclosure chassis The 5U84 enclosure includes the following features: ● 5U84 chassis configured with up to 84 LFF disks in DDICs. See 5U84 enclosure system - plan view of drawer accessed from front panel on page 16. ● 5U84 chassis configured with SFF disks in 2.5" to 3.5" hybrid driver carrier adapter. ● 5U84 empty chassis with midplane, module runner system, and drawers.
Figure 27. Drawer bezel details 1. 3. 5. 7. 9. Left side Anti-tamper lock Drawer fault Cable fault Drawer pull handle 2. 4. 6. 8. Right side Sideplane OK/Power Good Logical fault Drawer activity NOTE: For descriptions of drawer LED behavior, see Drawer LED states on page 38. Operator (Ops) panel LEDs Each ME4 Series enclosure features an Ops panel located on the chassis left ear flange. This section describes the Ops panel for 2U and 5U enclosures.
Table 4. Ops panel functions (continued) No. Indicator Status ● Blinking amber: logical fault (2 seconds on, 1 second off) 3 Unit identification display (UID) Green (seven-segment display: enclosure sequence) 4 Identity ● Blinking blue (0.25 Hz): system ID locator is activated ● Off: Normal state System power LED (green) LED displays green when system power is available. LED is off when system is not operating.
Table 5. Ops panel functions (continued) No.
Figure 30. 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.
Table 6. ME4 Series controller modules (FC and iSCSI SFPs) LEDs (continued) LED Description Definition 4 Fault ● Off —The controller is operating normally. ● Amber—A fault has been detected or a service action is required. ● Blinking amber—Hardware-controlled power-up or a cache flush or restore error. 5 OK to remove ● Off—The controller is not prepared for removal. ● Blue—The controller module is prepared for removal. 6 Identify White—The controller module is being identified.
Table 7. ME4 Series 10Gbase-T controller module LEDs (continued) LE D 2 Description Definition ● Link Activity ● Blinking green—The link has I/O activity. Host 10Gbase-T iSCSI ● Off—The link is not established, or the link is down. ● Green—The link is up at 10 Gb negotiated speed. ● Amber—The link is up at 1 Gb negotiated speed. Link Speed 3 OK ● Green—The controller is operating normally. ● Blinking green—System is booting. ● Off—The controller module is not OK, or is powered off.
Table 8. ME4 Series SAS controller module LEDs LE D Description Definition 1 Host 12 Gb SAS 1-2 ● Green—The port is connected and the link is up. ● Amber—Partial link exists (one or more lanes down). ● Blinking green or amber—Host link activity is detected. ● Link Status ● Link Activity 2 OK ● Green—The controller is operating normally. ● Blinking green—System is booting. ● Off—The controller module is not OK, or is powered off. 3 Fault ● Off—The controller is operating normally.
Table 9. Cache Status LED – power on behavior Item Display states reported by Cache Status LED during power on sequence Display state 0 1 2 3 4 5 6 7 Component VP SC SAS BE ASIC Host Boot Normal Reset Blink pattern On 1/Off 7 On 2/Off 6 On 3/Off 5 On 4/Off 4 Solid/On Steady On 5/Off 3 On 6/Off 2 Once the enclosure has completed the power on sequence, the Cache Status LED displays Solid/On (Normal), before assuming the operating state for cache purposes.
CAUTION: For single-controller module configuration only, to preserve the existing data stored in the CompactFlash, you must transport the CompactFlash from the failed controller module to the replacement controller module. This procedure is outlined in the 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.
Table 10. LEDs: Rear panel Cache Status (continued) Status Action Cache status LED blinks at a 1:1 rate - 2 Hz, and the controller does not boot. You may need to replace the controller module. Cache status LED blinks at a 1:1 rate - 1 Hz, and the controller boots. The system is in self-refresh mode. If the problem persists, replace the controller module.
2 Troubleshooting and problem solving These procedures are intended to be used only during initial configuration, for the purpose of verifying that hardware setup is successful. They are not intended to be used as troubleshooting procedures for configured systems using production data and I/O.
● ● ● ● Use the PowerVault Manager Use the CLI Monitor event notification View the enclosure LEDs Use the PowerVault Manager The PowerVault Manager uses health icons to show OK, Degraded, Fault, or Unknown status for the system and its components. The PowerVault 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.
Use the PowerVault Manager to verify any faults found while viewing the LEDs. The PowerVault Manager is also a good tool to use in determining where the fault is occurring if the LEDs cannot be viewed due to the location of the system. This web application provides you with a visual representation of the system and where the fault is occurring. The PowerVault Manager also provides more detailed information about CRUs, data, and faults. Review the event logs The event logs record all system events.
LEDs LED colors are used consistently throughout the enclosure and its components for indicating status: ● ● ● ● Green – Good or positive indication Blinking green/amber – Non-critical condition Amber – Critical fault Blue – Controller module or IOM identification 2U enclosure LEDs 2U enclosure PCM LEDs Under normal conditions, the power cooling module (PCM) OK LEDs will be a constant green. Table 11.
Table 12. Ops panel LED states (continued) System Power (Green/Amber) Module Fault (Amber) Identity (Blue) LED display Associated LEDs /Alarms Status -- -- -- 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. ● Check the event log for specific information regarding the fault, and follow any Recommended Actions.
Table 13.
5U84 enclosure PSU LEDs See Power supply module on page 19 for a visual description of the Power Supply Unit (PSU) module faceplate. Table 15. PSU LED states CRU Fail (Amber) AC Missing Power (Amber) (Green) Status On Off Off No AC power to either PSU On On Off PSU present, but not supplying power or PSU alert state. (usually due to critical temperature) Off Off On Mains AC present, switch on. This PSU is providing power.
CAUTION: The sideplanes on the enclosure drawers are not hot swappable or customer serviceable. 5U84 enclosure drawer LEDs See 5U84 enclosure drawers on page 20 for a visual description of the Drawer LED inserts located on each drawer bezel. Table 18. Drawer LED states LED Status/description Sideplane OK/Power Good Green if the sideplane is working and there are no power problems. Drawer Fault Amber if a drawer component has failed.
Table 19. DDIC LED states (continued) Fault LED (Amber) Status/description* Blinking: 3s on/1s off Storage system: Degraded (critical) Off Storage system: Quarantined Blinking: 3s on/1s off Storage system: Offline (dequarantined) Off Storage system: Reconstruction Off Processing I/O (whether from host or internal activity) *If multiple conditions occur simultaneously, the LED state will behave as indicated by the condition listed earliest in the table, as rows are read from top to bottom.
Table 20. 2U alarm conditions (continued) Status Severity Alarm Insufficient power available Warning None For details about replacing modules, see Replacing a controller module or IOM in a 2U or 5U enclosure on page 61. NOTE: Using the PowerVault Manager, monitor the storage system event logs for information about enclosure-related events, and to determine any necessary recommended actions. PCM faults Table 21.
Table 23. Thermal alarm recommended actions Symptom Cause Recommended action 4. Check for excessive re-circulation of heated air from rear to front. Use of the enclosure in a fully enclosed rack is not recommended. 5. If possible, shut down the enclosure and investigate the problem before continuing. Troubleshooting 5U enclosures The table describes common problems that can occur with your enclosure system, together with possible solutions.
CLI port connections ME4 Series Storage System controllers feature a CLI port employing a 3.5mm stereo plug and a mini-USB Type B form factor. For more information about connecting a serial cable, see Connecting to the CLI port using a serial cable on page 153. Temperature sensors Temperature sensors throughout the enclosure and its components monitor the thermal health of the storage system. Exceeding the limits of critical values causes a notification to occur.
3 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.
● Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet when standing on conductive floors or dissipating floor mats. ● Use conductive field service tools. ● Use a portable field service kit with a folding static-dissipating work mat. 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.
Shutting down attached hosts To replace modules in a 2U controller enclosure that has one controller module, you must shut down all of the attached hosts before shutting down the controller module. To replace the sideplane in a 5U84 enclosure, you must shut down all of the attached hosts before shutting down the controller modules. CAUTION: The sideplanes on the enclosure drawers are not hot swappable or customer serviceable.
● As an alternative to using the PowerVault Manager, you can run the CLI show system command to view the health of the system and its components. If any component has a problem, the system health will be Degraded, Fault, or Unknown. If you discover a problem component, follow the actions in its Health Recommendations field to resolve the problem.
5-This model uses SFF-8644 connectors and qualified cable options for host connection. Attach or remove the front bezel of a 2U enclosure The following figure shows a partial view of a 2U12 enclosure: Figure 37. Attaching or removing the 2U enclosure front bezel To attach the front bezel to the 2U enclosure: 1. 2. 3. 4. Locate the bezel, and while grasping it with your hands, face the front panel of the 2U12 or 2U24 enclosure.
Replacing an LFF drive carrier module The replacement procedures for LFF drive carrier modules are the same for SFF modules, except that the LFF drive carrier modules are mounted horizontally. Removing an LFF drive carrier module Perform the following steps to remove an LFF drive carrier module from a 2U enclosure: 1. Press the latch on the drive module carrier to open the handle. Figure 38. Removing an LFF drive carrier module (1 of 2) 2. Gently move the drive carrier module approximately 25 mm (1 in.
Installing an LFF drive carrier module Perform the following steps to install an LFF drive carrier module in a 2U enclosure: 1. Press the latch on the drive module carrier to open the handle. Figure 40. LFF drive carrier module in open position 2. Insert the drive carrier module into the enclosure. 3. Gently slide the drive carrier module into the enclosure until it stops moving. Figure 41. Installing an LFF drive carrier module (1 of 2) 4.
● 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 mounted vertically. Removing an SFF drive carrier module Perform the following steps to remove an SFF drive carrier module from a 2U enclosure: 1. Press the latch on the drive module carrier to open the handle. Figure 43. Removing an SFF drive module carrier (1 of 2) 2.
Figure 45. SFF drive carrier module in open position 2. Insert the drive carrier module into the enclosure. 3. Gently slide the drive carrier module into the enclosure until it stops moving. Figure 46. 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. Figure 47.
Replacing a blank drive carrier module Ensure optimal cooling throughout the enclosure by installing blank drive carrier modules into all unused drive slots. To remove a blank drive carrier module, press the latch on the module and pull the module out of the drive slot. To install a blank drive carrier module, insert the module into the drive slot and push the module into the drive slot to secure it in place.
5. Drawer Fault 7. Cable Fault 9. Drawer pull handle 6. Logical Fault 8. Drawer Activity 2. Push the drawer latches inward and hold them as shown in the following figure. Figure 49. Opening a drawer (1 of 2) 3. Pull the drawer outward until it locks at the drawer stops as shown in the following figure. The drawer is shown empty, which is how the enclosure is delivered. A drawer slide rail latch detail is inset. Figure 50.
● If the slot number is known, see 5U84 enclosure system - plan view of drawer accessed from front panel on page 16, which provides a view of a drawer that is dual-indexed with top drawer (left integer) and bottom drawer (right integer) slot numbering. ● If the disk drive has failed, a fault LED is lit on the front panel of the affected drawer. ● If the disk drive has failed, the Drive Fault LED on the DDIC is lit amber. 2. Open the drawer that contains the DDIC to remove. 3.
2. Insert the SAS connector into the new DDIC. 3. Insert the 3.5" adapter with the 2.5" disk drive into the new DDIC and connect the disk drive to the SAS connector.
4. Attach the bottom bracket to the new DDIC. 5. Secure the disk drive in the new DDIC using the four screws shipped with the new DDIC.
6. Attach the appropriate disk drive size label to the new DDIC. Installing a replacement 3.5" disk drive into a new DDIC Each replacement disk drive is shipped with new disk drive in carrier (DDIC). Install the replacement disk drive in the new DDIC before opening the drawer of the enclosure to remove the failed drive. 1. Remove the protective plastic from the new DDIC. 2. Insert the SAS connector into the new DDIC.
3. Insert the disk drive into the new DDIC and connect the disk drive to the SAS connector. . 4. Attach the bottom bracket to the new DDIC.
5. Secure the disk drive in the new DDIC using the four screws shipped with the new DDIC. 6. Attach the appropriate disk drive size label to the new DDIC.
Installing a DDIC in a 5U enclosure Failed disk drives must be replaced with approved disk drives. Contact your service provider for details. 1. Align the DDIC with the target drive slot as shown in Removing a DDIC (2 of 2) on page 54 and insert it into the drive slot. 2. Lower the DDIC into the drive slot. a. Push the DDIC downwards and hold it down. b. Move the slide latch in the direction shown in the following figure: Figure 53. Installing a DDIC a. Slide latch (slides left) b.
The drawers must be populated with DDICs in whole rows. Each drawer contains 3 rows of 14 DDICs. Rules and assumptions are listed: ● ● ● ● The minimum number of DDICs in an enclosure is 28. The number of rows must not differ by more than 1 between the top and bottom drawers.
Replacing controller modules in a dual-controller module enclosure Removing a controller module from an operational enclosure significantly changes air flow within the enclosure. Slot openings must be populated by controller modules for the enclosure to cool properly. Leave the controller modules in the enclosure until you are ready to install a replacement controller module. When two controller modules are installed in an enclosure, the controller modules must be the same model type.
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. Place both hands on the controller module body, and pull it straight out of the enclosure such that the controller module remains level during removal.
NOTE: In a dual-controller module system in which PFU is enabled, the system automatically updates the firmware on a replacement controller module. Replacing a controller module in a single-controller module enclosure Follow these guidelines when replacing a controller module in a single-controller module enclosure: 1.
NOTE: The previous figures show a 4-port SAS controller module. However, all of the controller modules use the same latching mechanism. 4. Swing the latch handle open, then grip the latch handle and ease the controller module forward from the slot. 5. Place both hands on the controller module body, and pull it straight out of the enclosure such that the controller module remains level during removal.
1. Examine the controller module for damage, and closely inspect the interface connector. Do not install the controller module if the pins are bent. 2. With the latch in the open position, grasp the controller module using both hands and align it for insertion into the target slot. 3. Ensuring that the controller module is level, slide it into the enclosure until it stops. A controller module that is only partially seated prevents optimal performance of the controller enclosure.
Figure 57. Removing an IOM from an enclosure 4. NOTE: Removing an IOM from an enclosure on page 67 shows a 4-port SAS controller module instead of an IOM. However, an IOM uses the same latching mechanism as the controller module. 5. Swing the latch handle open, then grip the latch handle and ease the IOM forward from the slot. 6. Place both hands on the IOM body, and pull it straight out of the enclosure such that the IOM remains level during removal.
Removing a PSU Before removing the 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 step procedure. CAUTION: Removing a power supply unit significantly disrupts the enclosure’s airflow. Do not remove the PSU until you have received the replacement module.
Installing a PSU If replacing both PSUs, the enclosure must be powered off via an orderly shutdown using the management interfaces. 1. Make sure that the PSU is switched off. 2. Orient the PSU for insertion into the target slot on the enclosure rear panel, as shown in Removing a PSU (2 of 2) on page 68. 3. Slide the PSU into the slot until the latch clicks home. 4. Connect the AC power cord. 5. Move the PSU power switch to the On position. 6.
Figure 61. 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; however, if replacing multiple FCMs, the enclosure must be powered off using an orderly shutdown using the management interfaces. 1. Orient the FCM for insertion into the target slot on the enclosure rear panel, as shown in Removing an FCM (2 of 2) on page 70. 2.
Before removing the PCM, disconnect the power from the PCM 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. Ensure that you correctly identify the faulty PCM before beginning the step procedure. 1. Stop all I/O from hosts to the enclosure. See Shutting down attached hosts on page 45. NOTE: This step is not required for hot-swapping. However, it is required when replacing both PCMs at once. 2.
9. If replacing two PCMs, repeat steps 5 through 8. Installing a PCM Refer to Removing a PCM (1 of 2) on page 71 and Removing a PCM (2 of 2) on page 71 when performing this procedure, but ignore the directional arrows—since you will insert the module into the slot rather than extract. NOTE: Handle the PCM carefully, and avoid damaging the connector pins. Do not install the PCM if any pins appear to be bent. 1. Check for damage, especially to all module connectors. 2.
Using LEDs This section describes the LEDs used to verify component operation. These LEDs are located on the enclosure front and rear panels. Verify front panel LEDs Front panel LEDs reside on the Ops panel located on the left ear flange. Disk LEDs are located on the carrier modules. ● Verify that the System Power On/Standby LED is illuminated green, and that the Module Fault LED is not illuminated. ● Verify that the enclosure ID LED located on the left ear is illuminated green.
4 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 host-based applications (using SNMP or SMI-S). NOTE: A best practice is to enable notifications to be sent for events having a severity Warning and higher.
Events Table 27. Event descriptions and recommended actions Number Severity 1 Critical Description/Recommended actions 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. ● If the indicated disk group is RAID 6, it is operating with degraded health due to the failure of two disks.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions is available, so no user data is lost. Data will be lost only if multiple disk failures occur in rapid succession so there is not enough time to migrate the data, or if there is insufficient space to fit the data in another tier, or if failed disks are not replaced promptly by the user. Recommended actions: ● The CLI trust command might be able to recover some of the data in the disk group.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Reconstruction of a disk group failed. The indicated disk was being used as the target disk for reconstructing the indicated disk group. While the disk group was reconstructing, another disk in the disk group failed and the status of the disk group went to OFFL (offline). The indicated disk has a status of LEFTOVR (leftover).
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Disk group reconstruction starts automatically. This event indicates that a problem reported by event 8 is resolved. Recommended actions: ● No action is required. 16 Info. The indicated disk has been designated a global spare. Recommended actions: ● No action is required. 18 Error Disk group reconstruction completed with errors.
Table 27. Event descriptions and recommended actions (continued) Number Severity Info. Description/Recommended actions Disk group verification failed immediately, was aborted by a user, or succeeded. Recommended actions: ● No action is required. 23 Info. Disk group creation has started. Recommended actions: ● No action is required. 25 Info. Disk group statistics were reset. Recommended actions: ● No action is required. 28 Info. Controller parameters have been changed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If multiple disks report this condition there could be a problem in the environment. ● If one disk reports this condition, there could be a problem in the environment or the disk has failed. 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).
Table 27. Event descriptions and recommended actions (continued) Number Severity 49 Info. Description/Recommended actions A lengthy SCSI maintenance command has completed. (This typically occurs during disk firmware update.) Recommended actions: ● No action is required. 50 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.
Table 27. Event descriptions and recommended actions (continued) Number Severity 54 Info. Description/Recommended actions Battery needs replacing. The battery provides backup power for the real-time (date/time) clock. In the event of a power failure, the date and time will revert to 1980-01-01 00:00:00. Recommended actions: ● Replace the controller module that logged this event. 55 Warning The indicated disk reported a SMART event. A SMART event indicates impending disk failure.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 61 Error The controller reset a disk channel to recover from a communication error. This event is logged to identify an error trend over time. Recommended actions: ● If the controller recovers, no action is required. ● View other logged events to determine other action to take. 62 Warning The indicated dedicated spare disk or global spare disk has failed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If you want hosts to access the volume data in the inserted disks, map the volume with a different LUN. 76 Info. The controller is using default configuration settings. This event occurs on the first power up, and might occur after a firmware update.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 84 Warning The current controller that logged this event forced the partner controller to fail over. Recommended actions: ● Download the debug logs from your storage system and contact technical support. A service technician can use the debug logs to determine the problem. 86 Info. Host-port or disk-channel parameters have been changed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● If the requested configuration changes did not occur, make the changes again and then use a user-interface command to shut down the Storage Controller and then restart it. 103 Info. The name has been changed for the indicated volume. Recommended actions: ● No action is required. 104 Info. The size has been changed for the indicated volume.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● This event is probably caused by equipment outside of the storage system, such as faulty cabling or a faulty switch. ● If the problem is not outside of the storage system, replace the controller module that logged this event. Info. The link for the indicated host port has gone down because the controller is starting up. Recommended actions: ● No action is required. 114 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity 140 Info. Description/Recommended actions The Management Controller is about to restart. Recommended actions: ● No action is required. 141 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). This event is also logged during power up or failover recovery, even when the address has not changed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 157 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. 158 Error A correctable ECC error occurred in Storage Controller CPU memory more than once during a 12-hour period, indicating a probable hardware fault.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Usually, the controller at the higher firmware level can read metadata written by a controller at a lower firmware level. The reverse is typically not true. Therefore, if the controller at the higher firmware level failed, the surviving controller at the lower firmware level cannot read the metadata in disks that have failed over.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Reseat any disks in the quarantined disk group that are reported as missing or failed in the user interface. (Do NOT remove and reinsert disks that are not members of the disk group that is quarantined.) ￭ Check that the SAS expansion cables are connected between each enclosure in the storage system and that they are fully seated.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 181 Info. One or more configuration parameters associated with the Management Controller (MC) have been changed, such as configuration for SNMP, SMI-S, email notification, and system strings (system name, system location, etc.). Recommended actions: ● No action is required. 182 Info. All disk channels have been paused.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If event 191 is not logged within 5 minutes after this event, the supercapacitor has probably failed and the controller module should be replaced. 191 Info. The auto-write-through trigger event that caused event 190 to be logged has been resolved. Recommended actions: ● No action is required. 192 Info. The controller module's temperature has exceeded the normal operating range.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● If event 201 has not been logged since this event was logged, the fan probably does not have a health of OK and the cause should be investigated. Another fan event was probably logged at approximately the same time as this event (such as event 168). See the recommended actions for that event. 201 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity 206 Info. Description/Recommended actions Disk group scrub has started. 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. ● Media errors for all RAID levels including RAID 0 and non-RAID disk groups. When errors are detected, they are automatically corrected.
Table 27. Event descriptions and recommended actions (continued) Number Severity 208 Info. Description/Recommended actions A scrub-disk job has started for the indicated disk. The result will be logged with event 209. Recommended actions: ● No action is required. 209 Error A scrub-disk job logged with event 208 has completed and found one or more media errors, SMART events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant disk group, data may have been lost.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 214 Info. The creation of snapshots is complete. The number of snapshots is indicated. Additional events give more information for each snapshot. Recommended actions: ● No action is required. 215 Info. Snapshots that were previously created are now committed and ready for use. Additional events give more information for each snapshot.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 225 Error A copy-on-write failure occurred when copying data from a master volume to a snapshot. Due to a problem accessing the snap pool, the write operation could not be completed to the disk. Data is left in cache. Recommended actions: ● Delete all snapshots for the master volume and then convert the master volume to a standard volume.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Notification only; no action was taken. ● All snapshots were invalidated. ● Snap-pool expansion was requested Recommended actions: ● If the policy is to halt writes, then you must free up space in the snap pool by deleting snapshots. 232 Warning The maximum number of enclosures allowed for the current configuration has been exceeded.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 238 Warning An attempt to install a licensed feature failed due to an invalid license. Recommended actions: ● Check the license for what is allowed for the platform, make corrections as appropriate, and reinstall. 239 Warning A timeout occurred while flushing the CompactFlash.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions 247 Warning The FRU ID SEEPROM for the indicated field replaceable unit (FRU) cannot be read. FRU ID data might not be programmed. FRU ID data includes the worldwide name, serial numbers, firmware and hardware versions, branding information, etc. This event is logged once each time a Storage Controller (SC) is started for each FRU that is not programmed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This can occur when a snapshot is taken by an application, such as the VSS hardware provider, that is timing-sensitive and needs to take a snapshot in two stages. After the snapshot is committed and event 258 is logged, the snapshot can be used. Recommended actions: ● No action is required. 257 Info. The indicated snapshot has been prepared and committed and is ready for use.
Table 27. Event descriptions and recommended actions (continued) Number Severity 268 Info. Description/Recommended actions A volume-copy operation for the indicated volume has completed. Recommended actions: ● No action is required. 269 Error A partner firmware update operation could not be performed. This event has these variants: 1. 2. 3. 4. 5. System health is insufficient to support firmware partner update. System has unwritable cache data present.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Disabled because of error count interrupts ● Disabled because of excessive PHY change counts ● PHY is ready but did not pass COMINIT Recommended actions: ● If none of the preceding reasons apply, no action is required. ● If any of the preceding reasons are indicated and the event occurs shortly after the storage system is powered up, do the following: ○ Shut down the Storage Controllers.
Table 27. Event descriptions and recommended actions (continued) Number Severity 279 Info. Description/Recommended actions A mirror component break command completed. Recommended actions: ● No action is required. 280 Info. A mirror component split command completed. Recommended actions: ● No action is required. 281 Info. A mirror set join command completed. Recommended actions: ● No action is required. 282 Info. A mirror component rejoin command completed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 292 Info. ilvering completed for a mirror component. Recommended actions: ● No action is required. 293 Info. Silvering was aborted for a mirror component. Recommended actions: ● No action is required. 294 Info. A break command completed for a mirror component. Recommended actions: ● No action is required. 295 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity 302 Info. Description/Recommended actions DDR memory clock frequency has changed to high. Recommended actions: ● No action is required. 303 Info. DDR memory clock frequency has changed to low. Recommended actions: ● No action is required. 304 Info. The controller has detected I 2 C errors that may have been fully recovered. Recommended actions: ● No action is required. 305 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If the ping operation failed, check connectivity between the storage system and the remote host. 312 Info. This event is used by email messages and SNMP traps when testing notification settings. This event is not recorded in the event log. Recommended actions: ● No action is required. 313 Error The indicated controller module has failed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Upgrade the controller firmware to a version whose SC is compatible with the indicated database version. ○ If no records were added, the database becomes accessible and remains intact. ○ If records were added, the database becomes accessible but contains only the new records. 352 Info. Expander Controller (EC) assert data or stack-dump data are available.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If the condition persists, this indicates a hardware problem in one of the controller modules or in the controller enclosure midplane. For help identifying which FRU to replace, see Troubleshooting and problem solving on page 31. 359 Info. All PHYs that were down for the indicated disk channel have recovered and are now up. Recommended actions: ● No action is required. 360 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Warning An uncorrectable ECC error occurred in Storage Controller CPU memory. 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. Recommended actions: ● No action is required. 400 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 414 Error A request to create a replication set failed. This operation is not permitted if the specified volume is already in a replication set or is not a master volume. Recommended actions: ● If the volume is a master volume and is not in a replication set, retry the operation. 415 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 420 Error A request to add a secondary volume failed. This can occur for several reasons, such as: ● ● ● ● ● ● The volume is already a replication volume. The volume is not local to the system. The communication link is busy or experienced an error. The volume is not the same size as the existing volume or is no longer in the set.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions A communication error occurred when sending information between storage systems. Recommended actions: ● Check your network or fabric for abnormally high congestion or connectivity issues. 428 Info. A replication was suspended by a user. Recommended actions: ● No action is required. 429 Info. A replication was resumed by a user. Recommended actions: ● No action is required. 430 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Update the firmware on one or both systems so they are running the same version. ● Check your network or fabric for abnormally high congestion or connectivity issues. 436 Warning Firmware in the remote system is incompatible with firmware in the local system so they cannot communicate with each other to perform replication operations.
Table 27. Event descriptions and recommended actions (continued) Number Severity 443 Error Description/Recommended actions The firmware for the indicated enclosure is not supported in this configuration. The firmware for the indicated enclosure does not support this enclosure for use as an expansion chassis. Its firmware supports this enclosure only as a direct attached JBOD. Recommended actions: ● Replace the indicated enclosure. It is not supported. 444 Info. A snap pool is running out of space.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 453 Info. A remote volume was successfully reattached to a replication set. Recommended actions: ● No action is required. 454 Info. A user changed the drive-spin-down delay for the indicated disk group to the indicated value. Recommended actions: ● No action is required.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions severity if the high threshold is exceeded and the virtual pool is overcommitted. Overcommitted means that the total committed size of all virtual volumes exceeds the physical space in the virtual pool. If the storage usage drops below a threshold, event 463 is logged. Recommended actions: ● You should immediately take steps to reduce storage usage or add capacity.
Table 27. Event descriptions and recommended actions (continued) Number Severity 468 Info. Description/Recommended actions FPGA temperature has returned to the normal operating range and the speed of buses connecting the FPGA to downstream adapters has been restored. The speed was reduced to compensate for an FPGA over-temperature condition. This event indicates that a problem reported by event 469 is resolved. Recommended actions: ● No action is required.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● To allow the replication to proceed, resolve the problem that is preventing access to the secondary volume. 476 Warning The CPU temperature exceeded the safe range so the CPU entered its self-protection state. IOPS were reduced. The storage system is operational but I/O performance is reduced. Recommended actions: ● Check that the storage system’s fans are running.
Table 27. Event descriptions and recommended actions (continued) Number Severity 481 Error Description/Recommended actions The periodic monitor of CompactFlash hardware detected an error. The controller was put in write-through mode, which reduces I/O performance. 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.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● If event 204 is logged, follow the recommended actions for event 204. ● If event 204 is NOT logged, perform the following recommended actions: ○ If event 486 is not logged at approximately the same time as event 485, reinsert the removed controller module, shut it down, then remove it again.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 492 Info. The volumes in a volume group were ungrouped. Recommended actions: ● No action is required. 493 Info. A volume group was modified. Recommended actions: ● No action is required. 494 Info. Reinitialization of a snap pool completed. Recommended actions: ● No action is required.
Table 27. Event descriptions and recommended actions (continued) 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. This is known as slot affinity.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions The Expander Controller firmware detected an incompatibility with the midplane type. As a preventive measure, disk access was disabled in the enclosure. Recommended actions: ● If using a supported enclosure, update the storage system to the latest firmware. If using an unsupported enclosure, replace the unsupported enclosure with a supported one.
Table 27. 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. 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. 508 Error The indicated virtual pool went offline. All of its volumes also went offline. All data in the virtual pool has been lost.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 516 Error An FDE disk has been placed in the unavailable state. The related event message 518, which indicates that a disk operation failed, may provide additional information. Recommended actions: ● See the recommended action specified in the event message. 517 Info. A disk that was formerly in the FDE unavailable state is no longer unavailable.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions 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. ● If multiple disks report this condition there could be a problem in the environment. ● If one disk reports this condition, there could be a problem in the environment or the disk has failed.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions As a preventative measure, the local Expander Controller (EC) is holding the partner Expander Controller (EC) in a reset loop. Recommended actions: ● Remove the partner controller module from the enclosure. Boot the partner controller module in single-controller mode in a separate enclosure (without the controller module that reported this event). Load the latest compatible bundle version.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions 535 Warning A disk was placed into a FAILED state after the controller detected a protection information error. Recommended actions: ● Replace the failed disk and return the other controller to operation. 536 Info. A disk protection information error was detected by the controller, but retries were successful. No further recovery action was necessary.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions The system will attempt to meet the scrub duration goals by adjusting system resources, but factors such as the amount of data or abnormally high host activity may cause scrub operations to exceed the requested duration. Recommended actions: ● If this event occurs repeatedly, the scrub duration goal should be increased to increase the likelihood that the goal can be met.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If the EMP is unable to communicate with the indicated PSU: ○ Wait for at least 10 minutes and check if the error resolves. ○ 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 PSU. Ensure the partner PSU is not degraded.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ 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. ○ If the partner FRU is not degraded, remove and reinsert the indicated FRU.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ○ If the indicated FRU is the enclosure, set up a preventive maintenance window and power cycle the enclosure at that time. ○ 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.
Table 27. Event descriptions and recommended actions (continued) 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. ○ If this does not resolve the issue, the indicated FRU has probably failed and should be replaced.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● Replace the module that contains the indicated expander. This could be an IOM, sideplane or a drawer. Contact technical support for replacement of the module containing the drawer expander. CAUTION: The sideplanes on the enclosure drawers are not hot swappable or customer serviceable. ● If these recommended actions do not resolve the issue, contact technical support.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● A current sensor has been uninstalled. Recommended actions: ● If a current sensor has exceeded the defined warning threshold values: ○ 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, the indicated FRU has probably failed and should be replaced.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Warning An Enclosure Management Processor (EMP) reported an alert condition on a motion sensor. A drawer motion sensor has detected an excessive level of acceleration or deceleration. Recommended actions: ● To prevent physical damage to drawer components and drives, avoid using excessive force when removing or inserting drawers.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions The EMP is unable to communicate with the front panel ear LED. Recommended actions: ● Replace the chassis-and-midplane FRU for the indicated enclosure. ● When the problem is resolved, an event with the same code will be logged with Resolved severity. Info. An Enclosure Management Processor (EMP) reported an alert condition on the front panel ear LED.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions This event is the result of a hardware problem that has caused the controller to run slower than expected. The system works, but I/O performance is degraded. Recommended actions: ● Restart the controller that logged the event. If the problem persists, replace the controller module. 566 Info. One of the DDR ports has been busy for at least 5 minutes.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions snapshot space and should be monitored. If the storage usage drops below any threshold, event 572 is logged. Recommended actions: ● Reduce the snapshot space usage by deleting snapshots that are no longer needed. Info. Allocated snapshot space exceeded either the low or middle snapshot space threshold.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● Resolve the issue specified by the error message included with this event. Info. A replication was started. Recommended actions: ● No action is required. 579 Warning A replication completed with failure. The replication was unsuccessful due to the condition specified within the event.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions During the Failback Restore operation, the replication direction for a replication set was reversed. Recommended actions: ● No action is required. 584 Info. A peer connection was modified. Recommended actions: ● No action is required. 585 Info. A replication set was modified. Recommended actions: ● No action is required.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● For a fault tolerant disk group, run either scrub disk-groups for a virtual disk group or scrub vdisk with the fix parameter enabled for a linear disk group. This step will make the parity consistent with the existing user data, and is required to fix data integrity issues.
Table 27. Event descriptions and recommended actions (continued) 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.) ○ Check that no disks have been removed from the system unintentionally.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 602 Error, Warning An alert condition was detected on a Midplane Interconnect element. The Midplane Interconnect element reports status associated with the interface between the SBB I/O module and the midplane. This is typically some form of communication problem on the midplane interconnect. Recommended actions: ● Contact technical support.
Table 27. Event descriptions and recommended actions (continued) Number Severity 606 Error Description/Recommended actions A controller contains unwritten cache data for a volume, and its supercapacitor has failed to charge. Due to the supercapacitor failure, if the controller loses power, it will not have backup power to flush the unwritten data from cache to CompactFlash. Recommended actions: ● Verify that the cache-write policy is write-through for all volumes.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● If this does not resolve the issue, contact technical support. The enclosure must be replaced. Warning An alert condition was detected on a sideplane element. Recommended actions: ● The sideplane associated with the drawer must be installed. Contact technical support. CAUTION: The sideplanes on the enclosure drawers are not hot swappable or customer serviceable.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions ● No action is required. 616 Warning A rebalance operation for an ADAPT disk group has completed partially. Recommended actions: ● No action is required. Info. A rebalance operation for an ADAPT disk group has completed. Recommended actions: ● No action is required. 617 Warning The spare capacity goal is not met.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions Recommended actions: ● No action is required. 624 Warning The Top Level Assembly data was changed. Recommended actions: ● No action is required. 625 Warning The system brand was changed. Recommended actions: ● No action is required. 626 Info. Detected an unsupported TPID (midplane Type ID). Recommended actions: ● No action is required. 627 Info.
Table 27. Event descriptions and recommended actions (continued) Number Severity Description/Recommended actions 650 Warning A disk firmware update is available for your system. Recommended actions: ● Go to https://www.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.
The trust command attempts to resynchronize leftover disks to make any leftover disk an active member of the disk group. The trust command may be needed when a disk group is offline because there is no data backup. The trust command may also be needed as a last attempt to recover the data on a disk group. In this case, the trust command may work, but only if the leftover disk continues to operate.
A 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 . The mini-USB connector plugs into the USB CLI port as shown in the following figure: Figure 64.
Table 31. Terminal emulator connection settings (continued) Parameter Value Data bits 8 Parity None Stop bits 1 Flow control None 1 Your computer configuration determines which COM port is used for the Disk Array USB Port. 2 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.
Device driver/special operation mode Certain operating systems require a device driver or special mode of operation. The following table displays the product and vendor identification information that is required for certain operating systems: Table 33. USB identification code USB identification code type Code USB Vendor ID 0x210c USB Product ID 0xa4a7 Microsoft Windows drivers Dell EMC provides an ME4 Series USB driver for use in Windows environments.
Linux drivers Linux operating systems do not require the installation of an ME4 Series USB driver. However, certain parameters must be provided during driver loading to enable recognition of the mini-USB port on an ME4 Series controller module.
B Technical specifications Enclosure dimensions Table 34. 2U enclosure dimensions Specification mm inches Overall enclosure height (2U) 87.9 mm 3.46 in Width across mounting flange (located on front of chassis) 483 mm 19.01 in Width across body of enclosure 443 mm 17.44 in 2U12 – Depth from face of mounting flange to back of enclosure body 576.8 mm 22.71 in 2U24 – Depth from face of mounting flange to back of enclosure body 526 mm 20.
Enclosure weights Table 36. 2U12, 2U24, and 5U84 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 sled) 0.05/0.11 0.05/0.11 — Power Cooling Module (PCM) 3.5/7.7 3.5/7.7 — Power Supply Unit (PSU) — — 2.7/6 Fan Cooling Module (FCM) — — 1.4/3 SBB controller module (maximum weight) 2.6/5.8 2.6/5.8 2.6/5.
Table 38. Additional environmental requirements (continued) Specification Measurement/description Altitude, operating ● 2U enclosures: 0 to 3,000 meters (0 to 10,000 feet) ● Maximum operating temperature is de-rated by 5ºC above 2,133 meters (7,000 feet) ● 5U84 enclosures: -100 to 3,000 meters (-330 to 10,000 feet) ● Maximum operating temperature is de-rated by 1ºC above 900 meters (3,000 feet) Altitude, non-operating -100 to 12,192 meters (-330 to 40,000 feet) Shock, operating 5.
Table 39. 2U Power cooling module specifications (continued) Specification Measurement/description > 90% @ 50% load > 92% @ 50% load > 87% @ 100% load > 88% @ 100% load > 85% @ surge > 85% @ surge Harmonics Meets EN61000-3-2 Output +5 V @ 42A, +12 V @ 38A, +5 V standby voltage @ 2.
C 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.
Electromagnetic compatibility (EMC) compliance Table 42. EMC compliance standards System product type approval Standards Conducted emissions limit levels CFR47 Part 15B Class A 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 EN 55024 AC power cable specifications Table 43. United States of America – Must be NRTL Listed (National Recognized Test Laboratory – e.g.
