diff --git a/fern/docs/pages/welcome.mdx b/fern/docs/pages/welcome.mdx index dcc713b..902101b 100644 --- a/fern/docs/pages/welcome.mdx +++ b/fern/docs/pages/welcome.mdx @@ -32,6 +32,7 @@ git clone cd docs-starter ``` + @@ -81,6 +82,112 @@ fern generate --docs ``` + + + +As realm admin, run the `redcli` commands in the following procedure from any healthy node in your cluster. + + +**Procedure** + +1. Determine the failed fan number using the following CLI command: + + ```bash + redcli health event list -s CRITICAL + ``` + + The output of this command displays critical events, which include failed fans. + + For example, the following output shows that `(SYS_FAN_1)` failed: + + ``` + 2025-01-21 03:26:43.73 +0000 UTC │ CRITC │ memp-dh4-inf-cug-7 │ Sensor hmi/servers/ c804086d-aad1-4869-8d2d-bcdcf9460952/sensors/8(SYS_FAN_1) Reading(140 5) crossed LowerCritical Threshold(150) + ``` + + The number displayed in the event output corresponds to the number shown in [Motherboard Layout](#figure-motherboard-layout) in [step 6](#locate-failed-fan-step-6). + +2. Put the instance with the failure into maintenance mode: + + a. List all resources of type instance in your cluster. In the output, a status of `present` indicates that the instance is not in maintenance. + + ```bash + redcli instance list + ``` + + b. Put the instance into maintenance by specifying its instance number or host name: + + ```bash + redcli instance maintenance enter -i + ``` + + or + + ```bash + redcli instance maintenance enter -n + ``` + + c. List all resources of type instance in your cluster and verify that the status of the instance is `Maintenance`. + + ```bash + redcli instance list + ``` + +3. If the server with the failed fan is still running, power off the server by specifying its host name. + + ```bash + redcli server power -T -a off + ``` + + +4. Disconnect all power cords and cables. Ensure each cable is properly labeled to support correct reconnection in [step 11](#reconnect-power-cord-step-11). + +5. Pull the chassis from the rack and remove the top chassis cover, as follows: + + a. Use a screw driver to loosen the captive screw on the rear of the chassis [Loosen captive screw](#figure-loosen-captive-screw). + + + + + + b. Slide the cover towards the back of the chassis, and then lift the rear top cover up, as shown in [Remove rear top cover](#figure-remove-rear-cover). + + + + +6. Locate the failed fan using the fan number from step 1 and the [Motherboard Layout](#figure-motherboard-layout) diagram. + + + +7. Physically remove the failed fan, as follows: + + a. Disconnect the fan cable from the motherboard header. + + b. Lift the failed fan housing up and out of the chassis [Remove the failed fan](#figure-remove-failed-fan). + + + +8. Release the rubber screws and push pins from the failed fan, and then insert the same rubber screws and push pins on the replacement fan [Install rubber screws on replacement fan](#figure-install-rubber-screws). + + + +9. Physically install the replacement fan, as follows: + + a. Align the replacement fan with the vacant slot in the chassis. + + b. Carefully insert the fan housing into the slot until it clicks securely into place. Confirm the fan is secure and seated flush in the chassis. + + c. Reconnect the fan cables to the same fan headers on the motherboard, using the following precautions: + - Use care when inserting the fan connectors into the motherboard headers, as there are obstructions for some headers. + - Avoid bending pins on these connectors. + - Secure the cables using ties after fan replacement. + +10. Re-install the top chassis cover and push the chassis into the rack. + + +11. Reconnect the power cords and cables exactly as they were removed in [step 4](#disconnect-power-cords-step-4). + + + ## Next steps