Phasing out a component
Use the component_phaseout command to phase out a component.
component_phaseout component=ComponentId
Parameters
| Name | Description | Mandatory |
|---|---|---|
| component | Component identification. | Y |
This command instructs the system to stop using the component, where the component can be either a disk, module, switch, or UPS.
For disks, the system starts a process for copying the disk data, so that even without this disk, the system is redundant. The state of the disk after the command is Phasing-out.
The same process applies for data modules. The system starts a process for copying all the data in the module, so that the system is redundant even without this module. A data module phase-out causes a phase-out for all the disks in that module.
For UPSs and switches, the system configures itself to work without the component. There is no phase-out for power supplies, S Fps, or batteries.
Phasing out a module or a disk, if it results in the system becoming non-redundant, is not permitted. Components must be in either OK or a Phase In status.
Once the phase-out process is completed, the component's state is either Fail or Ready, depending on the argument markasfailed. If true, the phased-out component is marked as a failed component (in order to replace the component). If false, the phased-out component is in the Ready state.
Access control
| User Category | Permission |
|---|---|
| Storage administrator | Allowed |
| Application administrator | Disallowed |
| Security administrator | Disallowed |
| Read-only users | Disallowed |
| Operations administrator | Allowed |
| Host side accelerator client | Disallowed |
Return codes
- PHASEOUT_NOT_SUPPORTED_FOR_THIS_COMPONENT_TYPE
This component type cannot be phased out.
- PHASEOUT_WILL_MAKE_SYSTEM_NON_REDUNDANT
Cannot phase out the component because it will cause data to be unprotected.
- PHASEOUT_NOT_ALLOWED_IN_CURRENT_STATUS
Component cannot be phased out in its current status.
- COMPONENT_DOES_NOT_EXIST
Component does not exist.
- COMPONENT_TYPE_CANNOT_BE_PHASED_OUT_AS_FAILED
Components of this type cannot be phased out and marked as failed.
- MODULE_CANNOT_BE_PHASED_OUT_DUE_TO_MANAGEMENT_REQUIREMENT
Module cannot be phased out due to management requirement.
Troubleshooting: Contact support.
- CAN_NOT_PHASE_OUT_DISK_WITH_MARKASFAILED_NO
Disks cannot be phased out with markasfailed=no.
- COMPONENT_TYPE_MUST_BE_PHASED_OUT_AS_FAILED
Components of this type must be phased out as failed.
- USE_SERVICE_PHASEOUT_COMMAND
Command component_phaseout does not support services. Use service_phaseout.
- CONTAINING_COMPONENT_IN_WRONG_STATUS
Operation not allowed in current status of containing component.
- SUBCOMPONENT_IN_WRONG_STATUS
Operation not allowed in current status of a subcomponent.
- CONTROLLING_SERVICES_NOT_ALLOWED_FOR_USER_CATEGORY
Controlling services not allowed for user category.
- NOT_ALL_PSUS_OK
There are one or more PSUs disconnected or failed, this may cause the requested action to cause module failures.
Troubleshooting: Check that all PSUs are properly wired, and ensure that none is failed.
- SYSTEM_UPGRADE_CANCELED_BECAUSE_OF_NODE_FAILURE_DURING_UPGRADE
Last upgrade was canceled because a node failed while the upgrade process was running.
- FAILED_NOT_SUPPORTED_FOR_THIS_COMPONENT_TYPE
This component type cannot be failed.
- HOT_UPGRADE_IS_NOT_ONGOING
Hot upgrade is not currently ongoing.
- FIRMWARE_UPGRADE_IN_PROGRESS
Firmware upgrade in progress.
Troubleshooting: Contact support.
- CANNOT_WRITE_TO_KEY_REPOSITORY
Failed writing keys to the key repository.
Troubleshooting: Contact support.
- KEYSERVER_COMMUNICATION_GENERIC_ERROR
Cannot connect to an active key server.
Troubleshooting: Invoke encrypt_keyserver_list and event_list for more details.
- NO_MASTER_KEYSERVER_DEFINED
There is no master key server defined on the system.
Troubleshooting: Define a master key server by invoking encrypt_key server_update and try again.
- NO_LIVE_KEYSERVER_GATEWAY_NODE
There is no live key server gateway node on the system.
Troubleshooting: Restart the key server gateway node and try again.