IBM TS7600 with ProtecTIER Software Upgrade Manual page 36

22
IBM System Storage TS7600 with ProtecTIER: Software Upgrade Guide
+------------------------------------------+
1) Check if RAS is running
2) Start RAS
3) Stop RAS
4) Get RAS Version
5) Get PT Code Version
6) Display Firmware Levels
7) Manage Configuration (...)
8) check PT Services Status (...)
9) System Health Monitoring (...)
10) Problem management (...)
11) Call Home Commands (...)
12) Collect Logs (...)
E) Exit
+------------------------------------------+
>>> Your choice?
4. Select the Check if RAS is running option. Type: 1 <enter>.
v If RAS has been configured and is running, the following messages display:
Begin Processing Procedure
RAS is running
a. Exit the RAS Menu. Type: E <enter>.
b. Go on to step 5.
v If RAS has not been configured and is not running, the following messages
display:
Begin Processing Procedure
RAS is down
a. To configure RAS on the server, follow the instructions in Appendix H,
"Making a server connection through the Remote Supervisor Adapter
(RSA)," on page 83.
b. Return to this page and go on to step 5.
5. Verify that you are connected to the proper server, and then stop the vtfd and
cluster services on that server. Enter the following commands:
service vtfd stop <enter>
service ptcluster stop <enter>
6. Disconnect the USB keyboard and monitor from Server B and connect them to
Server A.
7. Repeat steps 1 on page 21 through 5 to verify previous RAS configuration and
stop the vtfd and ptcluster services on Server A.
8. When RAS configuration is verified and services are stopped on both servers,
stay logged in to Server A, leave the keyboard and monitor connected, and go
on to step 16 on page 23 to start the ProtecTIER v3.1.x.x upgrade.
9. Check the /install directory for the presence of .tar files for code levels older
than the one currently running on the server. If older .tar files exist, remove
them along with the directories that were created when those levels of code
were expanded. This helps maintain available space within the root (/) file
system. If the files are allowed to accumulate and fill up the root file system,
unexpected server restarts can occur.