The following storage-related plug-ins for OES 2 and later require Novell iManager 2.7:
For more information about storage-related plug-ins, see Section 9.1.1, Understanding Storage-Related Plug-Ins.
The following table provides information about the protocols needed to use iManager when managing 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 7-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 NW 6.5 SP8: OpenWBEM Services Administration Guide.
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 NW 6.5 SP8: AFP, CIFS, and NFS (NFAP) Administration Guide.
NetWare Core Protocol™ (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.
Do not run the Enterprise Volume Management System (EVMS) management tools at the same time that iManager or NSSMU is running. Before you use evmsgui, close any instance of iManager or NSSMU, and vice versa.
Pool snapshots for NSS on Linux can be managed in NSSMU or iManager.
Pool snapshots for NSS on NetWare can be managed in iManager. NSSMU for NetWare does not provide a Snapshot option.
NSSMU for Linux does not support creating nested RAID 10 and 15 devices.