To begin a control station replacement, open a serial session then log in as nasadmin and issue a root. Stop the connect home and email user services. Verify that the email user service has been stopped. Run the nasmcd/getreason command to view the status of the Celerra.
Run the pre-upgrade health check script that comes with the Celerra procedure generator. If you receive an error, use the tar command to unzip the health check script again then re-run it. Enter the appropriate version of code. This will take several minutes. When the health check is complete, it will backup several important files into one file. Resolve any errors returned by the health check as necessary.
Backup the contents of several directories as shown here. Run the nas_version command to ensure the version you will be recovering with is the same version running on the control station now. Run the server_version command to make sure the version of code you are recovering for the blades is the same version. Here they are running the patch so we need to determine the file they are booting from. In this case, it is nas.exe.
Next, run the tar command to zip the nas.exe file into a separate file so it can be backed up. To backup the files, open up a sftp session using a program like WinSCP, login as root, navigate to /home/nasadmin then copy the files from the control station to another location such as your laptop or machine on site. Remember to change the transfer settings to binary. Once the files are safely backed up to another location, shut down the control station using the halt command.
Replace the physical hardware and cable in the new hardware. Open a new serial connection using PuTTY. Insert a CD or DVD with the same version of code as noted in the previous step, then reboot the new control station. When the control station brings up this menu, type in recover. Typing in anything else here could cause data loss. When asked if this is a secondary control station, type yes or no depending on whether you are replacing CS0 or CS1.
The control station will install the OS on the hardrive then reboot. After the reboot, when you see this screen, answer no. Answering yes could cause data loss. Confirm the recovery install. Answer whether the control station is a secondary based on whether you are replacing CS0 or CS1. Answer yes to configure LAN networking for the control station. Set up the networking configuration based on the customer's information.
Answer yes or no based on the number of plates in the cabinet. After this question, the script will continue on and recover the rest of the information necessary. When the script is finished, it will run a health check on the system to verify everything is operational. When the health check is finished, log in to the control station as root and reboot the control station. Log in as nasadmin and then issue a root.
Because you have just rebooted the control station, you will see a warning about nas services not being started. This is expected. Use the watch/nasmcd/getreason command to watch the control station finish booting. This will take several minutes. Run the nas_checkup command to verify everything is working properly in the system. This will take several minutes. Review the output of the health check.
Resolve any errors before continuing. Open a WinSCP session to your control station. Transfer the files that were backed up and the beginning of the procedure back to the control station. Remember to set the transfer settings to binary. When finished, close the WinSCP session. Back in your serial session, verify that you have root privileges and that nas services are started. Verify the files that you have copied back to the control station are present.
Make a directory to which you can restore the files. Use the tar command to unzip the backup files into their appropriate directories. Remember to restore the naspatch if there was one prior to the control station replacement. Verify that the connect home settings are still there. Perform a test of connect home. Verify that the version of code running on the control station and blades match. When finished, log out of your PuTTY session.
