XtremIO Maintenance: Source Notes on Technician Advisor and FRU Workflows
The source discusses first- and second-generation EMC XtremIO all-flash arrays and the author’s service experience, mainly first-generation systems with Technician Advisor (TA) 2.8. Its speculation about product succession to PowerStore/PowerMax is not a current product-roadmap statement.
1. Use the supported component-replacement workflow
The author strongly warns against ad-hoc hot removal, including redundant power components, and reports latent problems/double-fault risks after bypassing preparation. Interpret that warning as a requirement to use the exact supported FRU procedure. It does not independently establish that every component on every XtremIO generation is physically non-hot-swappable or that every replacement requires a complete array shutdown.
2. Match TA to the array and XMS
The source mentions TA 2.x, 3.x and 4.x and says each must match the applicable XtremIO/XMS software. It describes TA 2.8 as common in its first-generation cases, states that TA does not support XtremIO earlier than 2.4, and notes that a newer TA is not automatically compatible with every older array. These are archived source claims; obtain the actual authorized tool and current service compatibility information for the target system.
3. Manual replacement command names
The source lists these XMS command names. They are a command inventory, not a sequence to execute:
replace-bbu
replace-infiniband-switch
replace-dae
replace-infiniband-switch-fan-module
replace-dae-controller
replace-infiniband-switch-prepare
replace-dae-controller-prepare
replace-infiniband-switch-psu
replace-dae-fan-pair
replace-local-disk
replace-dae-prepare
replace-ssd
replace-dae-psu
replace-ssd-prepare
replace-dae-row-controller
replace-storage-controller
replace-dae-row-controller-prepare
replace-storage-controller-prepare
replace-dimm
replace-storage-controller-psu
replace-dimm-prepareThe author reserves manual command-based servicing for personnel who understand component preparation, replacement order and post-service state updates. A name alone does not provide prerequisites or a safe physical-removal procedure.
4. TA 2.8 capabilities described by the source
- View/rotate the cluster/X-Brick component model.
- Run the health-check script (HCS).
- Check cluster cabling/connectivity.
- Upload and run authorized signed scripts, including the described encryption-partition initialization capability.
- Import/export configuration to another cluster or the same cluster, including the source’s DR configuration-copy example.
- Change XMS and/or cluster IP configuration.
- Guide storage-controller, DIMM, battery-backup-unit and SSD replacement.
- Guide supported online expansion from one X-Brick to two, two to multiple, or a larger multi-brick cluster.
These are listed functions, not authorization to perform them without checking hardware/software support, data protection and the task-specific procedure.
5. Original English TA interface

Connection choices are XMS over LAN or a storage-controller tech port. Passwords remain masked; no working credential is supplied. The Chinese text in the watermark is the original author’s name and remains as attribution.

The source shows TA V2.8.0 and cluster version 4.0.10-33. The existing PSNT masking is preserved; the author watermark remains. This demonstrates that captured interface, not a certified compatibility matrix.
6. When a check or script blocks servicing
Identify the failed prerequisite and obtain vendor-supported remediation. The source says some checks may be bypassable but others must be resolved; it gives no bypass procedure. Do not infer that a skipped check is harmless. Incorrect sequencing can cause failed service or data loss. This article does not invent a skip-check command.
Attribution and changes
Translated/adapted from StorageExpert’s CSDN article, declared CC BY-SA 4.0. Changes: English translation, condensed personal/promotional remarks and explicit qualifications to broad hot-swap, roadmap and tool-compatibility claims. A matching public official English FRU workflow was not retrieved; use the authorized manufacturer procedure for the actual service task.