Novell Cluster Services is a server clustering system that ensures high availability and manageability of critical network resources including data (file systems), applications, and services. It is a multinode clustering product for Linux that is LDAP enabled via Novell eDirectory and supports failover, failback, and migration (load balancing) of individually managed cluster resources.
Connection Magazine: Tech Talk #3 - Over and Over and Over and Over This is an excellent article about NCS. It covers some of the issues with running mixed NetWare/Linux NCS cluster.
Connection Magazine: Tech Talk #5 - Backup Backup A good overview of NCS. Has a section on clustering GroupWise.
Linux OES Product Documentation: OES Cluster Services 1.8 Administration Guide for Linux
NetWare OES Product Documentation: OES Cluster Services 1.8 Administration Guide for NetWare
NetWare OES Product Documentation: Novell Cluster Services 1.8 Resource Configuration Guide
NetWare 6.5 Product Documentation: Novell Cluster Services
NetWare 6 Product Documentation: Novell Cluster Services
NetWare 5.1 Product Documentation: Novell Cluster Services
Novell Documentation: GroupWise 6 Introduction to GroupWise 6 and Novell Cluster Services
Novell Documentation: ZENworks 6.5 Introduction to Novell Cluster Services and ZENworks Server Management
Novell Documentation: ZENworks for Servers 3 Introduction to Novell Cluster Services and ZENworks for Servers
iSCSI and SLP
Use of iSCSI implies TCP/IP and dual-homed servers. If you properly architect your iSCSI network, you'll have it completely segregated and inaccessible by your client workstations. However, blocking port 524 traffic via ACL, or hiding the network via routing rules is not enough.
NetWare will still present all of its addresses via SLP by default, even if some of them are unreachable. This can cause lengthy delays in service location, drive mappings, etc. To avoid problems with name resolution and login performance, be sure to use the NCP EXCLUDE IP ADDRESS and SLP EXCLUDE IP ADDRESS parameters. Populate them with the IP addresses of the iSCSI network interfaces, to keep clients and other servers on your LAN/WAN from trying to communicate with them on the network you've designated for iSCSI traffic only.