Administrative Tasks
| Problem | Solution |
|
|
|
|
| Step 8: Verify the availability of all |
|
| executables. |
(continued) |
| Step 9: Enable access to the remote host. |
| Step 10: Verify ownership and protection. | |
|
| |
|
| Note that the vswin software may not |
|
| initialize when executed on an IBM if the |
|
| binary file is not owned by root. |
|
|
|
| What is the graceful way | Perform the following procedure. This |
| to shutdown a | procedure assumes that the user is |
| workstation? | logged in as vsadm, and VolServ and |
|
| vswin are running. |
|
| Step 1: From a vsadm shell window, |
|
| gracefully shutdown VolServ by entering: |
|
| volserv |
|
| When VolServ completes its termination |
|
| procedures, a VolServ shut down |
Workstation |
| completed message is displayed and the |
| vsadm prompt reappears. The Volume | |
Shutdown |
| |
| Server SysLog Console window and | |
|
| archives Console windows disappear |
|
| during VolServ termination procedures |
|
| Step 2: On the Volume Server System |
|
| console, select the Options window in the |
|
| upper left and select Exit from the |
|
| |
|
| Step 3: Verify that it is OK to quit. |
|
| Step 4: The VolServ host can now be |
|
| gracefully shut down. |
|
|
|
Troubleshoot
601354 Rev A | Troubleshoot |