6.1 Toolbar

The navigation pane includes its own toolbar that provides quick access to the most commonly used configuration tools for the Storage tab. Clicking on any of the icons provided in the toolbar opens a dialog or wizard that can guide you through the configuration process for that item. The following tools are available in this toolbar:

6.1.1 Discover File Server

To discover a file server:

  1. Make sure that your storage server exposes a writable file system to the storage network of your server pool.

  2. Select the Storage tab.

  3. Click Discover File Server Discover File Server icon. in the toolbar to start the Discover a File Server wizard.

  4. The File Server Parameters step is displayed in the wizard, where you enter the information necessary for Oracle VM Manager to discover the external storage mount points.

    Enter the storage information:

    • Storage Plug-in: The Oracle VM Storage Connect plug-in corresponding to the type of file server (generic NFS or vendor-specific). As Oracle VM Storage Connect plug-in are located on the Oracle VM Servers, this field is only populated if you have already performed Server Discovery. You cannot add storage without taking this step first.

    • Name: The name you wish to use to identify the file server.

    • Access Host (IP) Address: The host name or IP address of the server offering the file system.

    • Uniform Exports: If all Oracle VM Servers in all server pools have access to the same exports on the file server, leave this as the default (checked). If the file server is configured to offer different exports to different server pools, this box should be unchecked and, once you have completed the steps in the wizard, you need to configure Access Groups so that Oracle VM Manager can be made aware of export permissions. See Section 6.4.4, “Access Groups Perspective” for more information.

      Important

      Non-uniform exports are not intended for servers within the same server pool. Your NFS server should be configured to, at least, provide the same exports to all of the servers that belong to a particular clustered server pool.

    • Description: Optional information you would like to add about this file server.

    If you are adding a non-generic file server, for example a Sun ZFS Storage Appliance, also enter the additional plug-in options to enable Oracle VM Manager to access the file server's configuration management functions:

    • Admin Host: The host name or IP address where administrative access to the file server is allowed with appropriate credentials.

    • Admin User Name: A user name with administrator access to the file server.

    • Admin Password: The administrator password for the user name you entered.

    Click Next.

  5. The Add Admin Servers step is displayed in the wizard. If you are working with a non-clustered server pool, you may skip this step. Admin servers are designated Oracle VM Servers that are capable of logging into a storage array or file server to perform administrative functions such as extending a file system or creating a new LUN. In the case of an NFS file server, admin servers are only used to validate the file server. For backward compatibility reasons, admin servers are also capable of being used to perform file server refreshes in much the same way as refresh servers.

    Use the arrow buttons to move the required Oracle VM Servers from the Available Admin Server(s) box to the Selected Admin Server(s) box.

    Click Next.

  6. If you are using non-uniform file system exports (as selected in the first dialog of this wizard), the Select Refresh Servers step is displayed in the wizard. Refresh server are designated Oracle VM Servers that have visibility of one or more file systems on an NFS file server. These servers are used for file system refreshing across server pools.

    Each file system must be assigned at least one refresh server to allow for file system refreshing. During the refresh of a file server, the refresh servers are used to refresh all file systems used across all pools. For this reason it is critical that your refresh server list contains at least one server from each server pool.

    Important

    In some environments, it is plausible to expect that the file server is configured to provide different file system exports to different server pools. Therefore, it is possible that no single server has access to all of the exports provided by a file server. By assigning a server from each server pool to handle file system refreshes, Oracle VM can ensure that all file systems are refreshed across all server pools. If your environment is set up in such a way, you need to configure Access Groups so that the manager can be made aware of export permissions. See Section 6.4.4, “Access Groups Perspective” for more information.

    If you select the Refresh All option available in the context menu for Server Pools on the Servers and VMs tab, the configured refresh servers specified for each file system are used to perform a comprehensive file system refresh and you are not provided with an option to use one or more alternate refresh servers.

    In this dialog, you must include at least one server from each server pool that you intend to create. You may select more than one server from each server pool in order to ensure high availability, but adding more than two servers is superfluous.

    Note

    If you defined a group of admin servers in the previous step, for backward compatibility reasons, these servers are added to the refresh server list, and can be used to perform file server refreshes as well. This is not apparent in the Oracle VM Manager Web Interface.

  7. If you are using non-uniform file system exports (as selected in the first dialog of this wizard), click Finish to complete the wizard. A message is displayed to inform you that you should now create access groups for the file server. See Section 6.4.4, “Access Groups Perspective” for information on creating an access group. When at least one access group is configured, you should then refresh the file systems on the file server to make them available for use in Oracle VM Manager. Section 6.3.1.4, “Refresh File Server” for information on refreshing a file server.

    If you are using uniform file system exports, click Next to proceed to the Select File Systems step of the wizard. If any file systems contain existing virtual machine resources, select the corresponding check boxes to have Oracle VM Manager add the existing resources to the environment.

    At the top of the dialog box there is an option to provide a Name Filter. You can use this filter to specify search criteria to limit the objects displayed. See Section 1.16, “Name Filters” for more information.

    Click Finish to complete the file server registration.

    The new file server appears in the navigation pane, under File Servers.

    Note

    If you created shares to be used as server pool file systems, these are discovered in the same process. Since these file systems are relatively small, be sure to keep those available for the server pools and create storage repositories on the higher capacity file systems.

    At the end of the file server discovery a refresh operation is triggered to make sure all file systems available on the file server appear in Oracle VM Manager. When the operation is complete, and if you select the file server in the navigation pane, the available file systems appear in the File Systems overview table in the management pane.

    Warning

    If a server is unable to mount the file system for some reason, such as a permissions related issue, Oracle VM Manager does not report the failure as this would stop any further mounting. If a server is unable to access a file system the reason is reported in the /var/log/ovs-agent.log log file on the server.

6.1.2 Discover SAN Server

This first phase covers the discovery and registration part, meaning how you discover the container of the storage elements you intend to use in your environment.

Depending on the selected storage type and plug-in, you may be required to enter additional information than shown in this example (which uses an ISCSI SAN server) when registering your storage array, as shown in the following table.

Table 6.2 Required Information for Registering Different Storage Types

Information Field Required

Generic iSCSI

Vendor-specific iSCSI

Generic Fibre Channel

Vendor-specific Fibre Channel

Access host and port

Yes

Yes

No

No

Access credentials/CHAP

No

Optional

No

No

Administration information

No

Yes

No

Yes

Plug-in private data

No

Optional

No

Optional


To discover a storage array:

  1. Make sure that your storage server exposes raw disks (Fibre Channel SAN volumes, iSCSI targets and LUNs) to the storage network of your server pool.

  2. Select the Storage tab.

  3. Click Discover SAN Server Discover SAN Server icon. to start the Discover SAN Server wizard.

  4. The Discover SAN Server step is displayed in the wizard, where you enter the information necessary for Oracle VM Manager to discover the external storage elements.

    Enter the SAN storage information:

    • Name: The name you wish to use to identify the SAN server.

    • Description: Optional information you would like to add about this SAN server.

    • Storage Type: The array is either a fibre channel or an iSCSI storage server.

    • Storage Plug-in: The storage plug-in corresponding to the type of storage array, which is either generic iSCSI, or a vendor-specific iSCSI or fibre channel plug-in. As Oracle VM Storage Connect plug-in are located on the Oracle VM Servers, this field is only populated if you have already performed Server Discovery. You cannot add storage without taking this step first.

    • Plugin Private Data: Any vendor-specific Oracle VM Storage Connect plug-in data that may be required. This is not available to generic storage.

      Note

      When registering a vendor-specific storage array, be sure to double-check the information you entered in the plug-in private data field. Once the storage array is registered, this field can no longer be modified. If you need to update the plug-in private data, you must unregister and re-register the storage array.

    • Admin Host: The host name or IP address of the administration host. This is not available to generic storage.

    • Admin Username: The admin host username. This is not available to generic storage.

    • Admin Password: The password for the admin user. This is not available to generic storage.

    Click Next.

  5. The Access Information step is displayed in the wizard.

    Note

    This is not applicable to Fibre Channel storage arrays. Although Fibre Channel storage arrays have a host, they do not have an access host IP address defined in Oracle VM Manager, and as a result, specifying access information is not required.

    An access host is the IP address of the network interface that has access to the SAN server and creates a network path to the storage. In this dialog enter one or more access hosts to create network paths to the storage. To add multiple paths (for multipathing), add multiple access hosts. You must have at least one access host to the storage. On some ISCSI servers, only one access host is supported, so your screen may differ from the example in this step. If so, enter the access host IP address, access port and optionally the CHAP authentication details on the screen that you see, and the remaining parts of this step are not required to perform.

    If you want to use CHAP authentication to connect to the SAN server, check the Use CHAP check box.

    Click Create New Access Host Create New Acces Host icon to add access hosts for the SAN server.

    The Create Access Host dialog box is displayed.

    This figure shows the Create Access Host step in the Discover SAN Server wizard.

    Enter the IP address and access port of the host that has access to the SAN server. The default access port for iSCSI is 3260. If you checked CHAP authentication in the previous dialog, enter the username and password to access the storage. Click OK.

    Repeat this step for each access host, for example, you may have access hosts such as 10.172.76.130, 10.172.76.131, 10.172.77.130, and 10.172.77.131 to enable multipathing.

    When you have entered all access hosts, click Next.

  6. For most SAN servers the wizard moves straight to the Add Admin Servers step. However, if you have vendor-specific storage hardware with an admin host handling more than one storage array, such as certain HP EVAs and EMC arrays, you must enter the name of the array to be used for the new SAN server. The wizard recognizes this type of storage and displays the Set Storage Name step when applicable. Enter the storage name and click Next.

  7. The Add Admin Servers step is displayed in the wizard. If you are working with a non-clustered server pool, you may skip this step.

    Use the arrow buttons to move the required Oracle VM Servers from the Available Server(s) box to the Selected Server(s) box. This selects which Oracle VM Servers are to be made available to perform Oracle VM related admin operations on the SAN server. Click Next.

  8. The Manage Access Group step is displayed in the wizard.

    This final phase of the wizard offers you the access group configuration functionality. Within an access group you add the storage initiators to Oracle VM Servers to complete the storage configuration.

    Important

    You must add a storage initiator to an access group for each Oracle VM Server that you want to access the SAN server. If you do not add any storage initiators, Oracle VM cannot log in to the storage array and no LUNs can be accessed.

    A default access group may be created during the discovery process.

    • If no access group exists, you can create one from this dialog by clicking Create Access Group Create Access Group icon .

    • If you want to modify an existing access group for use with this SAN server, select it from the list and click Edit Access Group Edit Access Group icon .

    • If necessary, you can delete an access group by clicking Delete Access Group Delete Access Group icon.

    This example uses a generic ISCSI SAN server, so a default access group is created. Select the default access group in the table and click Edit Access Group Edit Access Group icon , then select the Storage Initiators tab in the Edit Access Group dialog box.

    This figure shows the Storage Initiators tab displayed in the Edit Access Group dialog box.

    Select and move the Oracle VM Servers into the Selected Storage Initiators box to add storage initiators to each Oracle VM Server. Click OK.

    The access group management functionality is also available outside this wizard. To access it, you must go to the Storage tab, select a SAN server in the navigation pane, and change the Perspective field in the management pane to Access Groups, as described in Section 6.6.4, “Access Groups Perspective”. Access group management for an individual Oracle VM Server is also described in Section 3.5.7.1, “View Access Groups for Selected Initiator”.

    Click Finish to complete the SAN server discovery operation.

    The new storage array appears in the navigation pane, under SAN Servers. Prior to the access group configuration, the Oracle VM Storage Connect plug-in established a link to the storage location. By configuring the access group(s), you grant one or more Oracle VM Servers access to the storage array, so that the storage elements or physical disks offered by the SAN server appear in Oracle VM Manager. Access group configuration and management is described in detail in the next section. The exception to the rule is the fibre channel storage array, which does not use the concept of access groups but offers its LUNs to all Oracle VM Servers connected to the fibre channel storage network.

    Note

    If you configured CHAP authentication for your SAN server and CHAP is not properly configured on your SAN storage device, or the authentication credentials that you provide for your Access Groups are incorrect, none of the LUNs or physical disks available on your SAN server are discovered and no error message is returned. You may need to check the logs on your SAN server to evaluate the required action that should be taken.