The requirements in this section apply to the following storage-related plug-ins for Novell iManager in OES:
Storage plug-in
Distributed File Services plug-in (NetWare)
Archive Versioning plug-in (NetWare)
File Protocols (CIFS) plug-in (NetWare)
Clustering plug-in
IMPORTANT:The storage-related 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.
Any patches and support packs for storage-related plug-ins that were released after OES SP2 requires iManager 2.6. For information about installing iManager 2.6, see the Novell iManager 2.6 Installation Guide
The storage-related plug-ins for OES SP1 and SP2 require Novell iManager 2.5 or later. The features in these plug-ins are not compatible with earlier releases of iManager. For information on how to upgrade to iManager 2.5, see
Upgrading to iManager 2.5
in the
Novell iManager 2.5 Installation Guide
.
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 the supported languages. To avoid problems, in your Web browser, click , then set the first language preference in the list to a supported language.
NOTE:This issue was resolved for the Archive Versioning plug-in for iManager 2.5 in OES SP1.
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 you use must be loaded and running on both the iManager server and the target server you want to manage.
Table 6-1 Interoperability of Protocols for the 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 OpenWBEM, 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 or the target server you want to manage are NetWare 6.5 SP3 or NetWare 6.5 SP2.
You cannot run the Enterprise Volume Management System Graphical User Interface (EVMSGUI) at the same time that iManager or NSSMU is running. If you use EVMSGUI ( evmsgui command) to manage NSS devices, close any instance of iManager or NSSMU, and vice versa.