Begin by logging into your control station as nasadmin and then issue a root. Stop the connect home service using the command as shown. Then stop the email user service using the command as shown. Verify that the email user service has been stopped. Use the nas_server command to view the status of your blades. If your primary has not failed over, use the server_standby command to fail over to the standby prior to removing the primary blade.
Once the blade has failed over to the standby, issue the command to halt the primary. Make sure to use the full name of the primary or you will halt the standby and cause an interruption to the service. When the blade is fully halted, follow the instructions in the procedure to remove the original hardware and replace it with the new hardware. When the new hardware is in place, run the /nasmcd/sbin/getreason command to view the state of the new blade.
Power on the blade using the command shown. Use the slot number of the primary blade. If you are unsure of the slot number, use the nas_server-info-all command to verify. Run the watch/nas/sbin/getreason command to watch the primary blade reboot. This will take a few minutes. When the primary blade has finished rebooting, run the command as shown to initialise the new blades management module.
Next, run the command to verify the management module was correctly set up. Run the command to initialise the new blade as shown. This will take a few minutes. Once the blade has fully initialized, run the server_standby command to fail back to the primary. Begin the ntv time service on the blade using the command as shown.
When finished, run the nas_check up command to perform a health check on the system and verify that any errors are resolved by this procedure. This will take a few minutes. When finished, resolve any errors or warnings given by the health check and start the connect home service. Perform a test of the service to verify that it is operational.
Enable the email user service. In our case, the service was never configured and therefore does not need to be enabled. When finished, exit from your PuTTY session.
