Force Enable Module
Overview
When there is an isolated component from the storage system caused by an error, etc., this function forces the component to be enabled without replacing it (called "force enable" hereinafter).
This function is performed in a situation such as when there is a normal component which has been affected by a failed component and isolated from the storage system.
Availability of Force Enable (for the ETERNUS DX600 S6) (Force enable is possible: , Force enable is not possible or not applicable: -)
Component | Force Enable | ||
---|---|---|---|
Controller Enclosure (CE) | - | ||
Controller Module (CM) | |||
Memory | - | ||
BUD | |||
FAN Unit | - | ||
PCIe SW | - | ||
64G FC-CA | |||
SFP+ | |||
32G FC-CA | |||
SFP+ | |||
16G FC-CA | |||
SFP+ | |||
10G iSCSI-CA | |||
SFP+ | |||
SAS-DA | |||
Backend Cable | - | ||
NVMe-DA | |||
Backend Cable | - | ||
CBP | - | ||
Controller Enclosure Power Supply Unit (CPSU) | - | ||
Operation Panel (OPNL) | - | ||
Battery Unit | - | ||
Battery Control Unit (BCU) | - | ||
Battery Unit (BTU) | - | ||
Drive |
|||
Drive Enclosure (DE) | - | ||
Power Supply Unit (PSU) |
- | ||
Drive | |||
Panel | - | ||
I/O Module (IOM) | |||
Backend Cable (IN) | |||
Backend Cable (OUT) | |||
Power Cord | - |
Availability of Force Enable (for the ETERNUS DX8100 S6) (Force enable is possible: , Force enable is not possible or not applicable: -)
Component | Force Enable Module | ||
---|---|---|---|
Controller Enclosure (CE) | - | ||
Controller Module (CM) | |||
Memory | - | ||
BUD | |||
FAN Unit | - | ||
PCIe SW | - | ||
64G FC-CA | |||
SFP+ | |||
32G FC-CA | |||
SFP+ | |||
16G FC-CA | |||
SFP+ | |||
10G iSCSI-CA | |||
SFP+ | |||
Controller Enclosure Power Supply Unit (CPSU) | - | ||
Operation Panel (OPNL) | - | ||
Battery Unit | - | ||
Battery Control Unit (BCU) | - | ||
Battery Unit (BTU) | - | ||
Power Cord | - | ||
Drive | (*1) |
*1 | : | A component that is installed in the CE of the ETERNUS DX8100 S6. |
Availability of Force Enable (for the ETERNUS DX900 S6 or the ETERNUS DX8900 S6) (Force enable is possible: , Force enable is not possible or not applicable: -)
Component | Force Enable Module | ||
---|---|---|---|
Controller Enclosure (CE) | - | ||
Controller Module (CM) | |||
Memory | - | ||
BUD | |||
FAN Unit | - | ||
PCIe SW | - | ||
FRT Port | - | ||
Management Cable | - | ||
64G FC-CA | |||
SFP+ | |||
32G FC-CA | |||
SFP+ | |||
16G FC-CA | |||
SFP+ | |||
10G iSCSI-CA | |||
SFP+ | |||
SAS-DA | |||
Backend Cable | - | ||
NVMe-DA | |||
Backend Cable | - | ||
Controller Enclosure Power Supply Unit (CPSU) | - | ||
Operation Panel (OPNL) | - | ||
Battery Unit | - | ||
Battery Control Unit (BCU) | - | ||
Battery Unit (BTU) | - | ||
Power Cord | - | ||
Drive | |||
Frontend Enclosure (FE) | - | ||
Frontend Enclosure Power Supply Unit (FE PSU) | - | ||
Frontend Router (FRT) | |||
Frontend Cable | |||
Service Controller (SVC) | |||
Port | - | ||
Management Cable | - | ||
FE MP | - | ||
FE MP BRG | - | ||
Operation Panel (OPNL) | - | ||
FAN Unit (FANU) | - | ||
FPO-SW | - | ||
Drive Enclosure (DE) | - | ||
Power Supply Unit (PSU) |
- | ||
Drive | |||
Panel | - | ||
I/O Module (IOM) | |||
Backend Cable (IN) | |||
Backend Cable (OUT) | |||
Power Cord | - |
Force enable can be performed only on one component at a time.
- Not all components can be forcibly enabled by using this function. Refer to the following tables for the availability of force enable for each part.
When installing the component that cannot be forcibly enabled in the storage system, use the Hot Maintenance or the [Hot Preventive Maintenance] function.
- This function cannot be used under the following conditions:
The selected drive is not in the "Broken" or "Not Supported" state
A component (other than a drive) whose state is other than "Error" is selected
Operating Procedures
Select the component to perform the force enable on, and click [Force Enable] in [Action].
→ A confirmation screen appears.
Click the [OK] button.
→ The force enable starts.
Click the [Done] button to return to the screen when the target component was selected in Step 1.