Storage systems that are supported for attachment to the
system are designed with
redundant components and access paths to enable concurrent maintenance. Hosts have continuous access
to their data during component failure and replacement.
The following categories represent the types of service actions for
storage systems:
- Controller code update
- Field replaceable unit (FRU) replacement
Controller code update
Ensure that you are familiar with the following guidelines for updating controller code:
- Check to see if the system supports concurrent maintenance for your storage system.
- Allow the storage system to coordinate the entire update process.
- If it is not possible to allow the storage system to coordinate the entire update process, complete the following steps:
- Reduce the storage system workload by 50%.
- Use the configuration tools for the storage system to manually fail over all logical units (LUs)
from the controller that you want to update.
- Update the controller code.
- Restart the controller.
- Manually failback the LUs to their original controller.
- Repeat for all controllers.
FRU replacement
Ensure that you are familiar with the following guidelines for replacing FRUs:
- If the component that you want to replace is directly in the host-side data path (for example,
cable, Fibre Channel port, or controller), disable the external data paths to prepare for update. To disable external data paths, disconnect
or disable the appropriate ports on the fabric switch. The system ERPs reroute access over the
alternate path.
- If the component that you want to replace is in the internal data path (for example, cache, or
drive) and did not completely fail, ensure that the data is backed up before you attempt to replace
the component.
- If the component that you want to replace is not in the data path (for example, uninterruptible power supply units, fans, or batteries), the
component is generally dual-redundant and can be replaced without more steps.