HP ProLiant CL1850 Compaq ProLiant CL1850 Software User Guide - Page 27

Configuring the Cluster for NetWare 4.2, Preparations for Installing NHAS

Get HP ProLiant CL1850 PDF manuals and user guides View all HP ProLiant CL1850 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

System Setup and Configuration for Novell NetWare 2-5 Configuring the Cluster for NetWare 4.2 Novell High Availability Server (NHAS) is the software needed to run the clustering aspect of the ProLiant CL1850 when running NetWare 4.2. This software must be installed after each server node has NetWare 4.2 loaded and at least one volume from the shared storage array has been mounted to each server node. NHAS will allow you to accomplish the following: s Configure the cluster s Pause the cluster s Manual failover s Manual failback s Automatic failover s Automatic failback For instructions on NHAS installation and detailed use of these functions, please refer to the Novell High Availability Server User's Guide from Novell. Preparations for Installing NHAS The following is a list of preparations needed prior to installation of NHAS. s Check network connections to and from each server using Display Servers command at NetWare console. s Use the Config command to check all IP addresses and to make sure there is a network connection bounded to the IPX protocol for the Direct Link. Label this network port as such for simplicity in recognition during the NHAS installation. A second network connection should exist for public NetWare Link. s Be sure to allocate and mount at least one shared volume for each server by using the Volume Options in the Install utility. Multiple volumes will imply the same rule. Try to gauge which applications will be installed so the volumes' File Compression and Block Suballocation settings are appropriate. Otherwise, you will need to reinstall NHAS later. s Each server in the cluster must have an internal hard drive that is not part of the shared subsystem. A SYS: volume on the shared subsystem would be confusing and potentially damaging.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
System Setup and Configuration for Novell NetWare
2-5
Configuring the Cluster for NetWare 4.2
Novell High Availability Server (NHAS) is the software needed to run the
clustering aspect of the ProLiant CL1850 when running NetWare 4.2. This
software must be installed after each server node has NetWare 4.2 loaded and
at least one volume from the shared storage array has been mounted to each
server node. NHAS will allow you to accomplish the following:
■
Configure the cluster
■
Pause the cluster
■
Manual failover
■
Manual failback
■
Automatic failover
■
Automatic failback
For instructions on NHAS installation and detailed use of these functions,
please refer to the
Novell High Availability Server User’s Guide
from Novell.
Preparations for Installing NHAS
The following is a list of preparations needed prior to installation of NHAS.
■
Check network connections to and from each server using Display
Servers command at NetWare console.
■
Use the Config command to check all IP addresses and to make sure
there is a network connection bounded to the IPX protocol for the Direct
Link. Label this network port as such for simplicity in recognition
during the NHAS installation. A second network connection should
exist for public NetWare Link.
■
Be sure to allocate and mount at least one shared volume for each server
by using the Volume Options in the Install utility. Multiple volumes will
imply the same rule. Try to gauge which applications will be installed so
the volumes’ File Compression and Block Suballocation settings are
appropriate. Otherwise, you will need to reinstall NHAS later.
■
Each server in the cluster must have an internal hard drive that is not
part of the shared subsystem. A SYS: volume on the shared subsystem
would be confusing and potentially damaging.