To configure OpenVault for use with COPAN MAID, do the following:
 | Note: The example output for some commands shown here has been edited for length and readability. |
You will use the ov_shelf(8) command to add the required library control program (LCP), drive control programs (DCPs), and OpenVault drive group for each MAID shelf. From the node that owns the shelf, enter the following command once for each MAID shelf:
ownernode# ov_shelf create shelfID |
For example, if the parallel data mover node node1 owns shelves 0 and 1, and node2 owns shelves 2 and 3:
node1# ov_shelf create C00 node1# ov_shelf create C01 node2# ov_shelf create C02 node2# ov_shelf create C03 |
| Note: Before ov_shelf takes any action, it verifies that there will be no conflicts with existing volumes at your site. If it detects a potential conflict, it will exit with an error. Because you already verified that there would be no problems by using the precheck operation in “Selecting Appropriate Cabinet Identifiers” in Chapter 2, you should not see any errors. |
Following is an example of the steps you will take to add an unprivileged and a privileged instance of the dmf application to OpenVault, using an example host named dmfserver as the OpenVault server. The characters ### in the right margin highlight comments related to the steps, which follow the example.
dmfserver# ov_admin ### STEP 1 Name where the OpenVault server is (or will be) listening? [dmfserver] ### STEP 2 OpenVault Configuration Menu for server "dmfserver" Configuration on Machines Running LCPs and DCPs 1 - Manage LCPs for locally attached Libraries 2 - Manage DCPs for locally attached Drives Configuration on Admin-Enabled Machines 11 - Manage Cartridge Groups 12 - Manage Drive Groups 13 - Import Media Configuration on the OpenVault Server Machine 21 - Manage Applications 22 - Manage OpenVault Client Machines q - Exit. Which operation would you like to do: 21 ### STEP 3 Manage Applications Menu 1 - Create a new Application 2 - Delete an Application 3 - Show all existing Applications 4 - Activate another Application Instance for an existing Application 5 - Deactivate an Application Instance 6 - Show all activated Application Instances r - Return to Main Menu. q - Exit. Which operation would you like to do: 4 ### STEP 4 Select the Application for which you want to activate a new Instance 1 - dmf 2 - ov_umsh r - Return to Previous Menu. q - Exit. Which operation would you like to do: 1 ### STEP 5 Enter the name of the Host where an instance of Application "dmf" will run [dmfserver] * ### STEP 6 Enter the Application's instance name or "*" [] * ### STEP 7 Should this Instance of the Application "dmf" be "privileged"? [No] ### STEP 8 What security key will the Application use [none] ### STEP 9 Unprivileged Instance "*" of Application "dmf" was successfully activated on "dmfserver". Press enter to continue... Manage Applications Menu 1 - Create a new Application 2 - Delete an Application 3 - Show all existing Applications 4 - Activate another Application Instance for an existing Application 5 - Deactivate an Application Instance 6 - Show all activated Application Instances r - Return to Main Menu. q - Exit. Which operation would you like to do: 4 ### STEP 10 Select the Application for which you want to activate a new Instance 1 - dmf 2 - ov_umsh r - Return to Previous Menu. q - Exit. Which operation would you like to do: 1 ### STEP 11 Enter the name of the Host where an instance of Application "dmf" will run [dmfserver] * ### STEP 12 Enter the Application's instance name or "*" [] * ### STEP 13 Should this Instance of the Application "dmf" be "privileged"? [No] yes ### STEP 14 What security key will the Application use [none] ### STEP 15 Privileged Instance "*" of Application "dmf" was successfully activated on "dmfserver". Press enter to continue... Manage Applications Menu 1 - Create a new Application 2 - Delete an Application 3 - Show all existing Applications 4 - Activate another Application Instance for an existing Application 5 - Deactivate an Application Instance 6 - Show all activated Application Instances r - Return to Main Menu. q - Exit. Which operation would you like to do: q ### STEP 16 |
Comments:
Log in to the OpenVault server and invoke the OpenVault administration tool ov_admin(8).
Enter the name associated with the IP address on which the OpenVault server is listening.
Enter 4 to activate another application instance for an existing application.
Enter the wildcard * character to allow the dmf application to be used from any host. Alternatively, you can repeat these steps to create a privileged and an unprivileged application instance for each system that DMF runs on (each DMF server and each parallel data mover node).
Enter the wildcard * character for the application instance name.
Optionally provide a security key to prevent unauthorized clients from masquerading as the dmf application. SGI recommends that you do this if you used the wildcard in step 6. You must use this same key when later running dmov_keyfile.
Enter 4 again to activate another application instance for an existing application.
Enter the wildcard * character to allow the dmf application to be used from any host. (See step 6.)
Enter the wildcard * character for the application instance name.
Optionally provide a security key. (See step 9.)
For more details, see OpenVault Administrator Guide for SGI InfiniteStorage.