To begin a module replacement, log into your control station through serial or SSH as nasadmin then issue a root. Then check the status of your plates by issuing the nas_server-info-allcommand. If the module to be replaced is in the primary blade and it has not failed over to the standby, do so now using the server_standby command. Use the watch/nasmcd/getreason command to watch the primary blade reboot.
Halt the primary blade. Remember to use the full name of the primary or you will halt the standby blade and cause a service interruption. Use the nasmcd/getreason command to verify the blade is shut down. Perform the module replacement, then return to the CLI. Use the server_cpu command to reboot the primary blade. Remember to use the full name of the primary or you will reboot the standby blade and cause a service interruption.
Use the watch/nasmcd/getreason command to verify the blade is finished rebooting. This will take a few minutes. When the blade is finished rebooting, use the server_standby command to fail back to the primary. Use the watch/nasmcd/getreason command to watch the standby blade reboot.
This will take a few minutes. Start the connect home service and the email user service. In our case, the email user service was never configured and therefore does not need to be enabled. When finished, exit out of your PuTTY session.