Novell iManager is a Web browser-based tool used for configuring, managing, and administering Novell eDirectory™ objects on your network. The Storage plug-in is the primary tool used to manage NSS devices, software RAIDs, pools, and volumes.
Novell iManager gives you the ability to assign specific tasks or responsibilities to user accounts and to present the user with only the tools (with the accompanying rights) necessary to perform those sets of tasks. For more information, see the Novell iManager 2.5 Administration Guide .
NOTE:The storage-related plug-ins do not support Mobile iManager.
This section discusses the following:
The following table identifies the storage-related plug-ins for OES:
Table 3-1 Storage-Related Plug-Ins for iManager 2.5 and 2.6
IMPORTANT:These plug-ins share code in common in the storagemgmt.npm file. If you use more than one of these plug-ins, you should install, update, or remove them all at the same time to make sure the common code works for all plug-ins. If you remove only one of the plug-ins, it removes the common code and breaks the remaining installed plug-ins.
The requirements in this section apply to the following storage-related plug-ins for iManager 2.5:
Storage plug-in
Distributed File Services plug-in (NetWare)
File Protocols plug-in (NetWare)
Archive Versioning plug-in (NetWare)
Clustering plug-in
IMPORTANT:The Storage, Distributed File Services, File Protocols, Archive Versioning, and Cluster Services plug-ins share common code in the storagemgmt.npm file. If you use more than one of these plug-ins, you should install, update, or remove them all at the same time to make sure the common code works for all plug-ins. If you remove only one of the plug-ins, it removes the common code and breaks the remaining installed plug-ins.
The initial release of OES used iManager 2.0.2.
In OES SP1 and NetWare 6.5 SP4, the storage-related plug-ins were redesigned. Enhancements made to the plug-in are not backwards compatible. To take advantage of the changes, you must upgrade from iManager 2.0.2 to iManager 2.5 or later. For information, see
Upgrading to iManager 2.5
in the
Novell iManager 2.5 Installation Guide
.
In NetWare 6.5 SP6, the Distributed File Services plug-in was added. It requires iManager 2.6, which is shipped with the SP6 release.
For OES Linux, NSS requires that EVMS be the volume manager of devices that contribute space to NSS pools (and its NSS volumes), and to NSS software RAID devices. It does not recognize devices that are being managed by non-EVMS volume managers. Only unconfigured devices or EVMS-managed devices with free unconfigures space are available to you when you create or expand NSS pools and software RAID devices.
For information about how to make EVMS the volume manager for your existing non-EVMS devices, see Section C.3, Making Devices Available to EVMS.
The iManager plug-in might not operate properly if the highest priority Language setting for your Web browser is set to a language other than one of iManager’s supported languages. To avoid problems, in your Web browser, click , and then set the first language preference in the list to a supported language.
The following table provides information about the protocols needed to use iManager to manage storage in a heterogeneous environment. A protocol annotated with an asterisk is the default and is configured automatically on the servers. The protocols that you use must be loaded and running on both the iManager server and the target server that you want to manage.
Table 3-2 Interoperability of Protocols for iManager Server and Target Servers
Where WBEM is the default protocol, WBEM is loaded and runs automatically when you start the server. Otherwise, you must start WBEM to use the protocol.
IMPORTANT:If you receive file protocol errors, it might be because WBEM is not running.
To check the status of WBEM:
As root in a console shell, enter
rcowcimomd status
To start WBEM:
As root in a console shell, enter
rcowcimomd start
For information about installing WBEM, see “Setting Up OpenWBEM” in the OpenWBEM Services Administration Guide for OES .
Where it is available, CIFS must be configured before you can use it. An additional CIFS setup requirement for Field Patch 2B is noted where it is required. For information, see the OES Native File Access Protocols Guide .
NCP™ is the default protocol when the iManager server and target server are NetWare 6.5 SP3 or SP2.
You cannot run the Enterprise Volume Management System Graphical User Interface ( evmsgui) or other EVMS tools at the same time that iManager or NSSMU is running. If you use EVMSGUI to manage NSS devices, close any instance of iManager or NSSMU, and vice versa.
The Storage Management ( storagemgmt.npm) file contains common code that is shared by the following storage-related plug-ins:
Storage
Distributed File Services (NetWare)
File Protocols (NetWare)
Archive Versioning (NetWare)
Cluster Services
If you use more than one of these storage-related plug-ins, you should install, update, or remove the storagemgmt.npm file and all installed storage-related .npm files at the same time.
IMPORTANT:If you remove any one of the installed storage-related plug-ins, it removes the common code ( storagemgmt.npm) file, which breaks the remaining installed plug-ins.
The Novell Storage Services Management ( nssmgmt.npm) file contains the following storage-related plug-ins:
Storage: Use the Storage plug-in to manage NSS services (devices, software RAIDs, pools, and volumes) on NetWare 6.5, OES NetWare, and OES Linux. Information about using this plug-in is the focus of this guide.
Distributed File Services (NetWare): Use the Distributed File Services plug-in to manage Novell DFS for NSS volumes on NetWare 6.5 and later servers. Target NSS volumes can be on NetWare 6.0 or later servers and OES Linux servers. For information about using the DFS plug-in, see Section 20.0, Managing Distributed File Services for NSS Volumes (NetWare).
File Protocols (NetWare): Use the File Protocols plug-in for NetWare to manage CIFS, AFP, and NFS services for end users of data stored on your NetWare 6.0 and later servers. For information about using the File Protocols plug-in, see the OES Native File Access Protocols Guide .
The Archive Versioning Management ( arkmgmt.npm) file contains the Archive Versioning plug-in for Novell Archive and Version Services for NetWare. For information about using this plug-in, see the Novell Archive and Version Services 2.0 for NetWare Administration Guide for OES .
The Cluster Services Management ( ncsmgmt.npm) file contains the Clustering plug-in for managing Novell Cluster Services™. For information about using this plug-in, see the following:
Launch a Web browser.
Click , then enter
https://server-IP-address/nps/iManager.html
The URL is case sensitive. Replace server-IP-address with the actual server DNS name or IP address. For example:
https://192.168.1.1/nps/iManager.html
The iManager Login page opens.
Log in, using your administrator username and password, to the eDirectory tree that contains the server you want to manage.
In Novell iManager, you can access only the roles and tasks you are authorized to manage. For full access to all available Novell iManager features, you must log in as Supervisor of the tree.
This section contains the instructions for downloading and installing updates to storage-related plug-ins.
Click the link, log in, and review the download agreement.
If you do not have a Novell account, you can register for free.
On the system where Novell iManager is installed, download the storage-related NPM files as described in Section 3.1.3, NPM Files for Storage-Related Plug-Ins. Make sure to include the common code file called storagemgmt.npm. None of the storage-related plug-ins work without it.
NOTE:When downloading this iManager plug-in, the browser might rename the downloaded file by adding a .zip extension (i.e. pluginname.npm.zip). If this occurs, you can either install the .zip file in iManager, or you can rename the file and install it. Any plug-in with the additional .zip extension can still be installed with iManager without any additional steps.
You can leave the NPM files in the downloaded location, or move them to the iManager packages location.
If you do not have Role-based Services (RBS) configured for Novell eDirectory, install the NPM files as follows:
Download the NPM update files.
For information, see Downloading the Plug-In.
In a Web browser, log in to iManager on the system where you downloaded the NPM files.
For information about accessing iManager, see Section 3.1.4, Accessing Novell iManager.
Click the icon (person seated behind a desk).
Under , click .
Click , browse to select the nssmgmt.npm and storagemgmt.npm files, then click .
If you are using the Archive Versioning ( arkmgmt.npm) and Clustering ( ncsmgmt.npm) plug-ins, make sure to select their NPM files, too. When the page refreshes, it returns to the Available Novell Plug-in Modules page.
Select the plug-ins from the list of available modules, then click .
This install takes a few minutes. You should receive a message confirming a successful install.
Click to dismiss the message, then close iManager.
Restart Tomcat 4, using one of the following methods:
Tomcat sometimes requires several minutes to fully initialize. Wait at least 5 minutes before trying to log into iManager.
For more information, see
Downloading and Installing an NPM
in the
Novell iManager 2.5 Installation Guide
.
If you are running iManager in Assigned Mode and have RBS configured for eDirectory, complete the following steps to install the NPM files.
IMPORTANT:To re-install an existing plug-in, you must first delete the rbsModule object for that plug-in from eDirectory, using the task.
Download the NPM update file.
For information, see Downloading the Plug-In.
In a Web browser, log in to iManager as an RBS Collection Owner on the system where you downloaded the NPM file.
For information about accessing iManager, see Section 3.1.4, Accessing Novell iManager.
Click the icon (person seated behind a desk).
Under , click .
Click , browse to select the nssmgmt.npm and storagemgmt.npm files, then click .
If you are using the Archive Versioning ( arkmgmt.npm) and Clustering ( ncsmgmt.npm) plug-ins, make sure to select their NPM files, too. When the page refreshes, it returns to the Available Novell Plug-in Modules page.
Select the plug-ins from the list of available modules, then click .
This install takes a few minutes. You should receive a message confirming a successful install.
Click to dismiss the message, then close iManager.
Restart Tomcat 4, using one of the following methods:
Tomcat sometimes requires several minutes to fully initialize. Wait at least 5 minutes before trying to log into iManager.
After Tomcat initializes, in a Web browser, log in to iManager as a Collection Owner again.
Click the icon.
Under , select .
The table on the tabbed page displays modules ready to update.
Locate the collection where you want to install the plug-in, then click its number.
The plug-ins you added should be displayed under column.
Select the plug-ins.
Click .
Wait for the message, then click to continue.
The role and role should appear on the pane.
Access iManager, then log in to the eDirectory tree where the server you want to manage resides.
For information, see Section 3.1.4, Accessing Novell iManager.
In do one of the following:
Expand the role to reveal its main tasks.
Expand the role to reveal its main tasks.
As you work in the storage-related plug-ins, use the navigation links at the top of the page, referred to as “breadcrumbs,” to return to pages you recently visited, or use the links in . If you use the and features of your Web browser to navigate, iManager returns you to the initial page you encountered after login.
To activate the options on the selected page, select a server to manage.
For information, see Section 3.1.7, Selecting a Server to Manage.
Before you can access the management options on a selected task page, you must select a server to manage that is in the same Novell eDirectory tree where you are currently logged in.
Use one of the following methods to select a server in the tree where you are logged in:
Type the Novell eDirectory distinguished server name for the server you want to manage, then click . For example: svr1.company.
Click the icon to open the eDirectory Object Selector. Browse or search the list to locate the server you want to manage, then click the server name.
Click the icon to select a server you have recently managed.
Wait for iManager to retrieve information about that server and display the appropriate information to the task page you are in.
It might take several seconds to retrieve the information, depending on the size and complexity of your storage solution.
The Storage role comprises seven key tasks:
You can create and manage storage pools to efficiently use all free space. For NetWare, you can also enable the Pool Snapshot feature to preserve point-in-time views of data pools and to support data backup and recovery.
Use the following table to find information about subtasks available from the Pools task.
Table 3-3 Pool Management Tasks
|
Subtask |
Description |
Reference |
|---|---|---|
|
|
A list of all pools on the selected server. |
|
|
|
View information about a selected pool. |
|
|
|
Create a new pool on the selected server. |
|
|
|
Delete a selected pool and all of its volumes and their data. |
|
|
|
Rename a selected pool. |
|
|
|
Mount and activate a selected deactive or unmounted pool. |
|
|
|
Deactivate a selected active pool. |
|
|
|
Add more partitions from available devices to expand the size of a pool. |
|
|
|
Opens the Pool Snapshot Management page where you can create and manage pool snapshots. |
|
|
|
If a storage object is not recognized, update eDirectory objects to force recognition. |
|
|
|
View and salvage deleted volumes in a pool. |
Viewing, Salvaging, or Purging Deleted NSS Volumes in a Pool |
|
|
For a pool snapshot that is online as an active pool, take it offline. This does not delete the pool snapshot. |
|
|
|
View a list of the partitions comprising the pool’s storage space. |
|
|
|
View a list of all volumes on a selected pool. |
|
|
|
View a list of the devices that contribute space to a selected pool. |
You can create and manage NSS volumes, including their key attributes.
Use the following table to find information about subtasks available from the Volumes task.
Table 3-4 Volume Management Tasks
|
Subtask |
Description |
Reference |
|---|---|---|
|
|
View a list of volumes on the selected server. |
|
|
|
View information about a selected volume. |
|
|
|
Create a new unencrypted volume. |
Creating and Configuring Unencrypted NSS Volumes with iManager |
|
|
Delete a selected volume and all of its contents. |
|
|
|
Rename a selected volume. |
|
|
|
Mount and activate a deactive or unmounted volume. |
|
|
|
Deactivate an active volume. |
|
|
|
Mount an unmounted volume. (A volume must be mounted to view its details.) |
|
|
|
Dismount a mounted volume. |
|
|
|
Move a selected volume to reorganize and redistribute storage on the same server (or to other servers) in response to changing business needs. Use the DFS plug-in to manage Move Volume jobs. |
|
|
|
Split a selected volume to reorganize and redistribute storage on the same server (or to other servers) in response to changing business needs. Use the DFS plug-in to manage Split Volume jobs. |
|
|
|
View or set attributes for a volume, including the Lookup Name Space. View usage statistics for a volume. |
|
|
|
View and manage user quotas. |
|
|
|
Take a selected snapshot volume offline, where it remains active in the background. |
|
|
|
If a storage object is not recognized, update the eDirectory object to force recognition. |
The User Quotas task is available in Storage tasks list only in iManager 2.6 or later. Previously, this function was accessible only as a subtask on the page. An individual user can now log in to iManager under his or her own username to view the user’s user space restrictions.
NSS creates and deletes partitions for you when you work with software RAIDS and pools in iManager and NSSMU. To delete partitions manually, use the NSSMU Partitions page.
Use the following table to find information about subtasks available from the Partitions task.
You can create and manage software RAID 0, 1, and 5 devices to improve storage performance and reliability. You must use NSSMU to create a software RAID 10 or 15 pool.
Use the following table to find information about subtasks available from the Software RAIDs task.
Table 3-7 Software RAID Management Tasks
You can configure, mount, and maintain a wide selection of storage devices, including direct-attached-storage devices, network-attached storage devices, networked storage devices in a Fibre Channel or iSCSI storage area network (SAN), and hardware device arrays.
Use the following table to find information about subtasks available from the Devices task.
Table 3-8 Device Management Tasks
|
Subtask |
Description |
Reference |
|---|---|---|
|
|
A list of all local and external devices available on the selected server. |
|
|
|
View information about a selected device. |
|
|
|
Initialize the selected device by erasing its partition table and effectively destroying all its data. |
|
|
|
For network configurations with multiple paths between network devices, opens the Multipath page where you can set the primary path and path failover priorities for fault tolerance of connections between host bus adapters and storage devices. You can also bring paths up and down. |
|
|
|
Sets the connection to selected device to its user-defined default primary path. |
|
|
|
Resets the multipath priority settings for a selected device in the server registry to its user-defined defaults. |
Resetting the Server Registry with Default Priority Settings for a Device |
|
|
Enable device sharing to support high-availability server clusters. |
|
|
|
View a list of pools on a device. |
|
|
|
View information about partitions configured on a device. |
You can scan for devices on a NetWare server that were not found automatically by the Media Manager.
Use the following table to find information about subtasks available from the Scan for Devices task.
The Distributed File Services plug-in requires iManager 2.6 or later. The DFS role comprises four key tasks:
After you use the Move Volume or Split Volume tasks on the page, use to manage those jobs.
Table 3-10 Volume Job Control Tasks
Add or remove replica sites that host the VLDB services for a DFS management context.
Table 3-11 Manage Replica Sites Tasks
Create a DFS Management Context where you plan to use Novell Distributed File Services for NSS volumes.
Table 3-12 Create Management Context Tasks
Delete a DFS management context. This removes the context and the VLDB services from the replica sites.
Table 3-13 Delete Management Context Tasks