Figure 63. Installing the node
4. Pull the orange release trigger and push in gently to re-engage the locking mechanism.
If the black release tab comes out when pulled, the locking mechanism is not engaged.
Power up the node
Power up the node as described in Power control procedures.
Reimage the new internal M.2 boot module
Run the svc_repair command to begin the reimage to the new internal M.2 boot module.
About this task
NOTE:
Do not run svc_repair before inserting the node. Run this command only after you have inserted the node. The
node begins powering on when you have fully inserted it into the system.
Steps
1. Immediately after inserting the node, return to your SSH connection and run the svc_repair command from the surviving
node.
NOTE: Run the command immediately after inserting the node to prevent any possibility of a time out issue.
The reimage procedure takes approximately 40 to 50 minutes to complete.
2. Review the output of the svc_repair command. The output provides useful information as the procedure runs, so allow
the session to remain open so you can monitor the progress. The following output is an example. Your output may differ
depending on which node is being reimaged.
SVC:cyc@CHXXXXX-A ~]$ svc_repair
PLEASE READ CAREFULLY!!! Requested operation will reformat peer node, all data will
be removed
Print 'YES' (All caps) if you want to continue recovery:
YES
CSU - initiating peer recovery. running on node A, recovering node B (Your message
may differ)
CSU - creating grub config
CSU - starting recovery container (afeoscyc-mw.cec.lab.emc.com/centos7/
recovery:v7.6.1327915), and booting peer node from PXE
CSU - sending power cycle command to peer
Base enclosure service procedures
51