background image

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH

0096-0699-A

Save this file, HASERVER.INI, in the SYS:\SYSTEM directory. Whenever Server B
enters the recovery state, this script will have NHAS configure Server A to respond to all
client requests to 123.45.67.22.

4.

 

Create a file called 

FAIL2.NCF 

on Server B with the following entries (each command is

preceded by remarked comments):

# adds all secondary IP addresses

add secondary ipaddress 123.45.67.11

# displays all secondary IP addresses

display secondary ipaddress

Then on Server B, edit the file HASERVER.INI and modify the FailoverCommand
parameter, under the section [Server.PL7000-2], as shown below:

 FailoverCommand=FAIL2.NCF

Save this file, HASERVER.INI, in the SYS:\SYSTEM directory. Whenever Server B
enters the recovery state, this script will have NHAS configure Server B to respond to all
client requests to 123.45.67.11.

5.

 

Create a file called 

REC1.NCF 

on Server B with the following entries (each command is

preceded by remarked comments):

# adds all secondary IP addresses

del secondary ipaddress 123.45.67.11

# displays all secondary IP addresses

display secondary ipaddress

Then on Server B, edit the file HASERVER.INI and modify the RecoveryCommand
parameter, under the section [Server.PL7000-2], as shown below:

 RecoveryCommand=REC1.NCF

Save this file, HASERVER.INI, in the SYS:\SYSTEM directory. Whenever Server A
enters the recovery state, this script will have NHAS configure Server A to no longer
respond to client requests to 123.45.67.22.

6.

 

Create a file called 

REC2.NCF 

on Server A with the following entries (each command is

preceded by remarked comments):

# adds all secondary IP addresses

del secondary ipaddress 123.45.67.22

# displays all secondary IP addresses

display secondary ipaddress

Then on Server A, edit the file HASERVER.INI and modify the RecoveryCommand
parameter, under the section [Server.PL7000-1], as shown below:

 RecoveryCommand=REC2.NCF

Save this file, HASERVER.INI, in the SYS:\SYSTEM directory. Whenever Server B
enters the recovery state, this script will have NHAS configure Server B to no longer
respond to client requests to 123.45.67.11.

7.

 

Ping Server A with the virtual IP 123.45.67.11 from a client.

Accordingly, the client ping should receive a reply from the server (volume).

Summary of Contents for 5500R - ProLiant - 256 MB RAM

Page 1: ...Remote Console IRC Compaq SmartStart and Compaq Insight Manager The Compaq ProLiant Cluster for NetWare 4 2 is designed to help customers reduce the risk and costs of downtime due to hardware or software failures Benefits include Automatic failover protection In the event of a failure on one server the remaining server maintains availability of network data and resources Active servers Users can n...

Page 2: ...rks of their respective companies Compaq Contura Deskpro Fastart Compaq Insight Manager LTE PageMarq Systempro Systempro LT ProLiant TwinTray ROMPaq LicensePaq QVision SLT ProLinea SmartStart NetFlex DirectPlus QuickFind RemotePaq BackPaq TechPaq SpeedPaq QuickBack PaqFax Presario SilentCool CompaqCare design Aero SmartStation MiniStation and PaqRap registered United States Patent and Trademark Of...

Page 3: ...o clients As a cluster the group of servers and storage offers a level of availability greatly exceeding the reliability of a standalone server This translates into increased performance and greater data availability for end users The ProLiant Cluster for NetWare 4 2 extends the definition by providing the same level of reliability while maintaining distinct network entities for each server By def...

Page 4: ...asure of how well a computer system can continuously deliver services to clients This is dependent upon the system s ability to prevent or recover from failures or faults Scalability Clustering for scalability means increasing performance beyond that of a single computer node by adding more nodes to the cluster Performance scalability across cluster nodes is difficult to achieve and requires not o...

Page 5: ... SMP Industry standard non proprietary hardware requirements High availability and lower total cost of ownership through Support for Fiber Channel Arbitrated Loop FCAL Novell Directory Services NDS support NetWare Loadable Module NLM based installation Dynamic user licensing Application fallback via IP Novell s High Reliability Solution The ProLiant Cluster for NetWare 4 2 featuring Novell High Av...

Page 6: ...f the cluster since it prevents a split brain scenario wherein two servers may try to access the same data simultaneously obviously this could result in data corruption In the given configuration each server is operating in the costandby state that is independently but waiting for the other server to fail Compaq RAID Array 4000 Volume 1 Accessed by Node A only Volume 2 Accessed by Node B only Serv...

Page 7: ...rocess During a failover the remaining server must mount the new volumes launch any active server based applications that were running on the failed device and transfer security and license information NHAS also allows manual failover of shared volumes at any time by pressing F at the NHAS console By forcing a failover you can remove a server from the network for scheduled maintenance without inte...

Page 8: ...r or purchase a new Compaq server the following minimum hardware requirements must be met for a ProLiant Cluster for NetWare 4 2 configuration Compaq ProLiant Servers The primary components of a cluster are the servers The initial release of the ProLiant Cluster for NetWare 4 2 supports a two node cluster where each node is a server The key software component that imparts high availability to the ...

Page 9: ...Cluster for NetWare 4 2 deployment and the cornerstone of mission critical computing Compaq StorageWorks RAID Array 4000 Storage System The ProLiant Cluster for NetWare 4 2 is based on a cluster architecture known as Shared Storage Clustering in which clustered servers share access to a common set of hard drives Novell High Availability Server requires all shared data to be stored in an external s...

Page 10: ... as five Compaq RA4000s can be attached to the Fibre Channel Storage Hub 7 and with the Fibre Channel Storage Hub 12 up to ten Compaq RA4000s are supported In both cases two ports on the hubs are used by the server connections With the Compaq RA4000 connected to both servers through the Fibre Channel Storage Hub you can independently manage volumes on the servers in the cluster as needed by your a...

Page 11: ...ray controllers can be configured as a redundant pair such that one controller is a backup for the other as described under Redundant Fibre Channel Loop for Increased Availability below Compaq Fibre Channel Host Controller The host controller available as a PCI adapter interfaces between the server and the Fibre Channel Storage System through the fiber optic cable At least two PCI Fibre Channel Ho...

Page 12: ...a path over which nodes of a cluster communicate This type of communication is termed intra cluster communication The ProLiant Cluster for NetWare 4 2 uses the standard public network controller card NetWare Link an optional Dedicated Link and the Fibre Channel Disk Link to implement intra cluster communication At a minimum the interconnect consists of two network adapters one in each server and a...

Page 13: ...e your server load the system software and integrate Compaq utilities thereby ensuring that your server delivers maximum dependability and supportability For information concerning SmartStart refer to the Compaq Server Setup and Management pack Compaq System Configuration Utility The SmartStart and Support Software CD also contains the Compaq System Configuration Utility This utility is the primar...

Page 14: ...e Diskettes for Novell NetWare Novell SSD The Compaq SSD for Novell NetWare contains device drivers and utilities that enable you to take advantage of specific capabilities offered on Compaq products The drivers and utilities are provided for use only with Compaq hardware For additional details on the features contained in the Novell SSD visit http www compaq com support files server softpaqs Netw...

Page 15: ... the shared subsystem If NetWare is installed with the shared drive subsystem connected the installer should make sure that SYS volumes of both clustered servers are installed on the internal non shared drives Having the SYS volumes on the shared subsystem would be confusing and potentially damaging NetWare volumes can span multiple drives but if a volume spans more than one drive all of the drive...

Page 16: ...reen P Pauses the AutoSwitch feature When you press P the AutoSwitch feature is paused and automatic failover or rollback will not take place When you pause NHAS the status turns red to indicate that the server cannot change states To unpause the NHAS Console press p again Note that the Pause feature does not affect a transitional state For example once the failover process has reached the ENTERIN...

Page 17: ...us problem somewhere along the shared drive channel If the problem is in the channel between one server in the cluster and the shared drive subsystem then that server will be disarmed and its shared drives will have already become inaccessible The volumes will not be mounted on the other server unless all other links fail or a manual failover is invoked If the problem is in the shared subsystem th...

Page 18: ...lt Detection and Correction is available on all Compaq 10 100 Fast Ethernet products This feature reduces the possibility of downtime due to network failure by allowing the administrator to configure a redundant interconnect for each communication path In a redundant interconnect configuration each communication path is configured with a primary link and a backup link If a component in the primary...

Page 19: ... the one you want to launch del secondary ipaddress 123 45 67 8 These NCF batch files should be created in the search directory of each server node such as SYS SYSTEM Each server will have varying IP addresses input in their NCF files to discern which secondary IP addresses are to be deleted and which are to be kept during a failover and recovery IP handling during a failover should add the second...

Page 20: ...is License Number is used as the main Server License for this node during normal operating conditions RecoveryCommand REC1 NCF By specifying a command or an executable script when a server enters the RECOVERY STATE i e has failed it processes the commands listed here This specified command should call a file that contains all commands necessary for a successful IP failover FailoverCommand FAIL1 NC...

Page 21: ...this particular server PL7000 1 Volume VOL1 These Volume settings identify what should remain exclusive to this server Volume SYS These Volume settings identify what should remain exclusive to this server PrimaryLicense 60022796 This License Number is used to as the main Server License for this node during normal operating conditions RecoveryCommand REC1 NCF By specifying a command or an executabl...

Page 22: ...e NHAS from automatically mounting this volume HotfixIdentifier 258E5780 This value derived from the partition time stamp NetWare creates is used to recognize volumes for NHAS MountCommand By specifying a command or an executable script when a server dismounts this particular volume it processes the commands inputted here DismountCommand By specifying a command or an executable script when a serve...

Page 23: ...wing entries the lines beginning with are comments for explanation and clarity deletes the other server s secondary IP addresses del secondary ipaddress 123 45 67 11 adds all secondary IP addresses add secondary ipaddress 123 45 67 22 displays all secondary IP addresses display secondary ipaddress Then on Server B edit the file HASERVER INI and modify the CostandbyCommand parameter under the secti...

Page 24: ...el secondary ipaddress 123 45 67 11 displays all secondary IP addresses display secondary ipaddress Then on Server B edit the file HASERVER INI and modify the RecoveryCommand parameter under the section Server PL7000 2 as shown below RecoveryCommand REC1 NCF Save this file HASERVER INI in the SYS SYSTEM directory Whenever Server A enters the recovery state this script will have NHAS configure Serv...

Page 25: ...nd environments While none of these challenges is prohibitive certain steps or precautions are often necessary to accommodate the failover process Server Applications and the SYS Volume Some applications such as Netscape Fast Track Server write the executable files to the server s SYS volume In the event of a failover the surviving server would no longer be able to access the files on the downed s...

Page 26: ...ght delay in accessing the recovery server to the need for complete re logging into the system Other applications for example database servers must have clustering awareness built into them so that transactions can be rolled back and logs parsed to ensure data integrity is maintained Oracle on the other hand features complex transaction logging systems that maintain the integrity of the database i...

Page 27: ...drive failover to Server B the newly mounted volumes must be manually added using one of the Novell NDS administration utilities to reflect the changes Using NWAdmin is the recommended method Long name spaces Mac NFS etc on a shared volume will transfer during a failover but you need to make sure that the name space support modules for all name spaces in the cluster are loaded on all servers in th...

Page 28: ...e is used and a server fails information that is contained in the file cache and not yet written to disk is lost Configure the NetWare file cache to balance your performance needs against the possible loss of critical data For more information on tuning NHAS to your system requirements see the documentation accompanying the software Technical FAQs What happens to a client running server based appl...

Page 29: ...when a system running Novell High Availability Server fails Any print jobs still in RAM will be lost The other server will resume all others that have been written to disk when the volume is mounted on the other active server What is the slunbind command line parameter on the VINCAIPX line of the AUTOEXEC NCF With StandbyServer only one server is monitoring the other so monitoring communication is...

Reviews: