Module 3: Preparing for Cluster Service Installation Contents Overview Pre-Installation Requirements Identifying Hardware Considerations Assigning IP Addresses Within a Cluster 16 Assigning Names Within a Cluster 18 Determining Domain Considerations 20 Existing Services and Applications 23 Lab A: Configuring Advanced Server for Cluster Installation 24 Review 31 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2000 Microsoft Corporation All rights reserved Microsoft, Active Directory, BackOffice, Jscript, PowerPoint, Visual Basic, Visual Studio, Win32, Windows, Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries Other product and company names mentioned herein may be the trademarks of their respective owners Program Manager: Don Thompson Product Manager: Greg Bulette Instructional Designers: April Andrien, Priscilla Johnston, Diana Jahrling Subject Matter Experts: Jack Creasey, Jeff Johnson Technical Contributor: James Cochran Classroom Automation: Lorrin Smith-Bates Graphic Designer: Andrea Heuston (Artitudes Layout & Design) Editing Manager: Lynette Skinner Editor: Elizabeth Reese Copy Editor: Bill Jones (S&T Consulting) Production Manager: Miracle Davis Build Manager: Julie Challenger Print Production: Irene Barnett (S&T Consulting) CD Production: Eric Wagoner Test Manager: Eric R Myers Test Lead: Robertson Lee (Volt Technical) Creative Director: David Mahlmann Media Consultation: Scott Serna Illustration: Andrea Heuston (Artitudes Layout & Design) Localization Manager: Rick Terek Operations Coordinator: John Williams Manufacturing Support: Laura King; Kathy Hershey Lead Product Manager, Release Management: Bo Galford Lead Technology Manager: Sid Benavente Lead Product Manager, Content Development: Ken Rosen Group Manager, Courseware Infrastructure: David Bramble Group Product Manager, Content Development: Julie Truax Director, Training & Certification Courseware Development: Dean Murray General Manager: Robert Stewart Module 3: Preparing for Cluster Service Installation iii Instructor Notes Presentation: 60 Minutes Lab: 15 Minutes This module covers the information that is required to plan for the installation of Microsoft® Cluster service Requirements specific to server clusters include communication networks, shared disks, and data storage, in addition to hardware considerations for the operating system This module describes the naming and addressing conventions that the cluster components require Domain considerations are covered, in addition to issues relating to services and applications that were installed and running prior to installing Cluster service After completing this module, students will be able to: Determine the pre-installation considerations for a server cluster Identify hardware considerations Assign Internet Protocol (IP) addresses within a cluster Assign names within a cluster Determine domain considerations Determine pre-installation considerations for existing services and applications Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module Required Materials To teach this module, you need the following materials: Microsoft PowerPoint® file 2087A_02.ppt Access to the Hardware Compatibility List at www.microsoft.com/hcl Preparation Tasks To prepare for this module, you should: Read the materials for this module and anticipate questions students may ask Be familiar with the HCL Be familiar with the Fibre Channel technologies from the leading hardware vendors Practice the lab Be familiar with the gratuitous Address Resolution Protocol (ARP) procedure that Cluster service generates after a failover, and how that relates to routers and switches Study the review questions and prepare alternative answers for discussion iv Module 3: Preparing for Cluster Service Installation Module Strategy Use the following strategy to present this module: Students need to be aware of pre-installation requirements and considerations that will enable them to successfully install and deploy Cluster service Pre-Installation Requirements There is information regarding pre-installation tasks on the opening page of this section Be sure students are aware of the need to back up data and determine potential points of failure Additionally, students need to know about the special requirements of Cluster service for network connections, cluster disks (shared disks), and data storage • Cluster Network Requirements: Students need to be able to identify the public and private network methodology and what travels across those different networks and how they relate to a server cluster • Cluster Disk Requirements: Prior to the installation of Cluster service, the student must be able to verify that the server that the cluster will use meets the disk requirements Students need to configure the disks prior to installation of Cluster service Students can add disks to the cluster after they install the cluster, and the disks must meet the same requirements • Data Storage Requirements: Stress to the students that the operating system is on the local drives and that all of the partitions of the shared disks must have identical drive letters on each node of the cluster The local drives and partitions of the shared disk must be set up before installation Identifying Hardware Considerations Cluster service is more dependent on hardware than other software produced by Microsoft Because this dependency is such a critical issue, the hardware used should be on the HCL Students also need to consider hardware outside of the server cluster and how it may affect the performance of the cluster • Cluster Service Compatible Systems: Each node of a cluster requires a minimum set of hardware for Cluster service to install properly Stress to the students that this is an Enterprise solution and that the hardware should not be substandard • Routers, Switches, and Hubs: When a resource fails over, the node controlling the failed over group must send a gratuitous ARP update to let clients, switches, and routers know about the ARP update Some legacy switches and routers might not be able to accept this ARP update or forward it to clients Students need to be aware that there are more things controlling the outcome of a successful deployment besides the use of two servers and the software they are running • Network Cards: Cluster service does not require separate network cards for public and private communication, but you need to stress to students that it is highly recommended Using a single adapter for public and private communication can result in failovers of resources that are caused by traffic congestion on this single network Remind the students that there are many types of supported network cards, such as Ethernet, Fibre, and other specialized interconnects Module 3: Preparing for Cluster Service Installation v • Cluster Disks: Disks that are on the same bus between two servers are shared disks After Cluster service is installed, these disks will be referred to as cluster disks Considerations for these disks focus on throughput For instance, if disk access is a concern, you can use a faster disk or implement hardware Redundant Array of Independent Disks (RAID), or move the disk to another shared bus between the two nodes of a cluster if there is contention for the input/output (I/O) of the shared bus • Cluster Data Access: A server cluster can use a disk that is accessed through a small computer system interface (SCSI) or Fibre bus Most server cluster implementations use Fibre Assigning IP Addresses Within a Cluster: Cluster service needs a minimum of five static IP addresses Remind the students that although the private network can use automatic private addressing, which is a feature of Microsoft Windows® 2000, the servers will have faster startup times with a static address for the private network Assigning Names Within a Cluster: Cluster service uses network basic input/output system (NetBIOS) names for the administration of the cluster, virtual servers, and for nodes of the cluster Inform the student that as a best practice, they should use the cluster name for administration only, and they should treat virtual server names as a separate group of resources Determining Domain Considerations • In this section you will talk about how server clusters interact with a Windows 2000 domain, and what accounts students will need to create or manage prior to installing Cluster service • User Accounts: The two user accounts that are of concern prior to installation of server cluster are the account used to install the service, which needs to have administrative rights on each node of the cluster, and the service account, which also has to have administrative rights and the right to log on as a service • Computer Accounts: The nodes have computer accounts in the domain to which they belong, whether they are domain controllers or member servers It is a best practice to keep the member server computer accounts in their own organizational unit so that group policies not affect them Existing Services and Applications • If you are upgrading a server to become a node in a cluster, you need to consider whether the services and applications that are running on the server will work after the installation of Cluster service For example, Windows Internet Name Service (WINS) can continue to run outside the cluster on a server that is installed as a node Microsoft Exchange, however, will not run on a server that is upgraded to a server cluster environment and will fail Tell the students that extensive testing of applications and services needs to be done if the applications and services are running on a server that will be installed with Cluster service vi Module 3: Preparing for Cluster Service Installation Instructor Setup for a Lab Lab Strategy This lab is designed to prepare the servers for the installation of Cluster service In this lab the students will set up identical drive letters on each server in the cluster Then they will configure the private and public networks for cluster communications At the end of the second exercise, there is a closing exercise using the Pre-Installation Checklist This checklist will also serve as a job aid for students to use later on Lab A: Configuring Advanced Server for Cluster Installation To conduct this lab: Read though the lab carefully, paying close attention to the instructions and details Students work in teams of two, grouped together by their shared bus Help the students determine whether they are Node A or Node B In these exercises, students will perform all of the steps on both servers Familiarize the students with the Reference Table and how to find their computers in the table Allow some time to discuss the Pre-Installation Checklist Module 3: Preparing for Cluster Service Installation Overview Topic Objective To provide an overview of the module topics and objectives Lead-in This module outlines what you need to before installing Cluster service Pre-Installation Considerations Identifying Hardware Considerations Assigning IP Addresses Within a Cluster Assigning Names Within a Cluster Determining Domain Considerations Existing Services and Applications *****************************ILLEGAL FOR NON-TRAINER USE****************************** This module covers the information that is required to plan for the installation of Microsoft® Cluster service Requirements specific to server clusters include communication networks, shared disks, and data storage, in addition to hardware considerations for the operating system This module describes the naming and addressing conventions that the cluster components require Domain considerations are covered, in addition to issues relating to services and applications that were installed and running prior to installing Cluster service After completing this module, you will be able to: Determine the pre-installation requirements for a server cluster Identify hardware considerations Assign Internet Protocol (IP) addresses within a cluster Assign names within a cluster Determine domain considerations Determine pre-installation considerations for existing services and applications Module 3: Preparing for Cluster Service Installation Pre-Installation Requirements Topic Objective To determine the preinstallation considerations for a server cluster that will protect the components and data in case of a failure Client Client Client Client Client Client Lead-in A server cluster does not address single points of failure outside of the cluster You need to assess the current environment before you install a server cluster Client Client Router Router Server Server Power Power *****************************ILLEGAL FOR NON-TRAINER USE****************************** Before installing Cluster service you will need to plan for failures that could occur in the environment You also need to consider how the nodes in the cluster will communicate with each other, and how clients will access the server cluster Additionally, you must ensure that your system will have the shared disks and data storage that are required for a successful Cluster service installation Backup and Restore Clustering technology provides increased reliability; however, it is not designed to protect all of the components of your workflow in all circumstances For example, Cluster service is not an alternative to backing up data, because it protects only the availability of data, not the data itself Therefore, you need to plan for backup and restoration of data Risk Assessment It is recommended that prior to creating a cluster, you complete a risk assessment of your network to identify possible single point of failures that can interrupt access to network resources A single point of failure is any component in the environment that would block client access to data or applications if it failed Single points of failure can be hardware, software, or external dependencies Examples of single points of failure include dedicated wide area network (WAN) lines or the power supply from a utility company Uninterruptible Power Supply Another recommendation is to consider providing an uninterruptible power supply (UPS) protection for individual computers and the network, including hubs, bridges, and routers A UPS is just one more factor in configuring a total fault tolerant solution Many UPS solutions provide power for to 20 minutes, which is long enough for the Microsoft Windows® 2000 operating system to properly shut down when power fails Module 3: Preparing for Cluster Service Installation Cluster Network Requirements Topic Objective To describe how Cluster service uses public, private, and mixed networks for cluster and client communications Public Network Lead-in Mixed Network Server clusters use a network for communications You have three configuration options for server cluster communications Private Network Private Network Public or Mixed Network *****************************ILLEGAL FOR NON-TRAINER USE****************************** Delivery Tip Stress to the students that a dedicated public network will never transmit private communications – have at least one mixed network A cluster network has two primary types of communication The private communication provides online status and other cluster information to the nodes The public communication provides information between the client and virtual servers It is recommended that private network communications be physically separated from public network communications, but have the ability to use the mixed network to eliminate a single point of failure An alternative network type a mixed network, uses the public network for both private and public communications The advantage of a mixed network is that private network communications can be failed over to the public network If you dedicate a network to client-to-node communications, node-to-node communications cannot fail over to that network The mixed network configuration is the preferred configuration for a public network Network adapters, known to the cluster as network interfaces, attach nodes to networks You configure what types of communication will travel across the networks by using the cluster administration tools Module 3: Preparing for Cluster Service Installation Private Network The private network, also known as the interconnect in a server cluster, will potentially carry the following five types of information: Server heartbeats Each node in a cluster exchanges IP packets (approximately every 1.2 seconds) with the other node in the cluster determining if both nodes are running correctly The first node of the cluster to come online is the node that is responsible for sending out the heartbeats The second node begins to send heartbeats to inform the first node that the second node has come online If a node does not respond to the heartbeat, the working node identifies the unresponsive node as having failed If a node fails to detect six successive heartbeats from another node, the other node assumes that the unresponsive node is offline and tries to take ownership of the resources that the nonresponding node owns Note that failure to detect a heartbeat message can be caused by node failure, network interface failure, or network failure Replicated state information Every node in the cluster uses replicated state information to communicate which cluster groups and resources are running on all of the other nodes Cluster commands Cluster commands manage and change the cluster configuration An example of a cluster command would be any node-tonode communications regarding adding or removing a resource or failing over a group Application commands Cluster-aware applications send application commands through the interconnect to communicate with copies of an application running on multiple servers Application data Application data is when cluster-aware applications share data between nodes Note If the private network fails over to the public network, the Cluster service employs packet signing for node-to-node communications to provide additional security over the network Public Network The public network connection extends beyond the cluster nodes and is used for client-to-cluster communication The public network cannot function as a backup connection for node-to-node communication should the private network fail The network interface cards (NICs) for the public network must be on the same subnet 18 Module 3: Preparing for Cluster Service Installation Assigning Names Within a Cluster Topic Objective To determine user and computer account considerations when installing a cluster Lead-in There are three main types of names in a server cluster: The Node Name, the Cluster Name, and the Virtual Server Name All of the names are NetBIOS names; however Dynamic DNS can use them \\Cluster \\Cluster A Client can use \\NodeA to Manage NodeA A Client can use \\Accounting to access the Virtual Server A Client can use \\Cluster to Manage the Cluster \\Accounting \\Accounting \\NodeA \\NodeA \\NodeB \\NodeB *****************************ILLEGAL FOR NON-TRAINER USE****************************** When installing Cluster service, there are three types of names that you will assign to each part of the server cluster All of the names must conform to standard network basic input/output system (NetBIOS) naming conventions You will need to assign a Cluster service NetBIOS name to each of the following components: Node Name Each node of the cluster needs a server name or node name for management of the server Each node is listed in WINS, Dynamic DNS and Active Directory™ Users and Computers Cluster Name The cluster name refers to the first virtual server created during the installation of Cluster service The network administrator uses the cluster name to configure and administer the cluster If the network administrator has configured each node to use WINS and Dynamic DNS, the cluster name will also be registered on the network Cluster names are not listed in Active Directory Users and Computers Virtual Server Name Each virtual server needs a name that clients use to gain access to resources on virtual servers If the network administrator has configured the node to use WINS and DDNS, each virtual server name will also be listed Virtual server names are not listed in Active Directory Users and Computers Note In a Windows Internet Naming Service environment, Node Names, Cluster Names and Virtual Server Names register their name with the WINS server for NetBIOS name resolution Module 3: Preparing for Cluster Service Installation 19 The NetBIOS namespace within a network must be different from all of the other namespaces and is 16 characters in length Microsoft networking components, such as Windows 2000 and Windows 2000 Server services, allow the user or administrator to specify the first 15 characters of a NetBIOS name, but reserve the 16th character of the NetBIOS name to indicate a resource type (00-FF hex) You can register names as unique (one owner) or as group (multiple owners) names 20 Module 3: Preparing for Cluster Service Installation Determining Domain Considerations Topic Objective To determine user and computer account considerations when installing a cluster Lead-in User Accounts Computer Accounts Cluster Service uses a user account for a service account and a computer account for each node for the domain *****************************ILLEGAL FOR NON-TRAINER USE****************************** Prior to the installation of Cluster service, you must assign each server a computer account on the Windows 2000 domain Cluster service uses domain authentication to interact with the user accounts on the same domain There are two types of accounts: User accounts You use the administrator account for installation, and the service account for administration and maintenance of the server cluster Computer account The computer account identifies the computer as a member of the domain for administrative purposes You can install Cluster service on Windows 2000 or Microsoft Windows NT® version 4.0 domains, but you cannot install it to a workgroup environment because the service account cannot run on a local node A domain controller must validate the service account Module 3: Preparing for Cluster Service Installation 21 User Accounts Topic Objective To identify the user accounts that are required for installation and maintenance of Cluster service Administrator Account on Each Node Cluster Service Account Lead-in There are two user accounts for Cluster service – an Administrator account and a Service account *****************************ILLEGAL FOR NON-TRAINER USE****************************** There are two required accounts for the installation and maintenance of Cluster service: a user account with administrator rights and a service account Administrator account To install Cluster service, you will need to be logged on as a user with administrator’s rights on each node of the cluster The Cluster Installation Wizard verifies that the user has the appropriate permissions to install Cluster service.
Service account When you install Cluster service, you specify the domain user account under which Cluster service runs You use the service account to start and maintain Cluster service You can locate the service account on both nodes of a member server’s account database or on the Active Directory It is recommended that you locate this account in Active Directory.
The Service account must have the following user account settings: Log on as a service right Administrator privileges Password never expires User cannot change password 22 Module 3: Preparing for Cluster Service Installation Computer Accounts Topic Objective To explain why it is a best practice to install Cluster service on member servers with a separate organizational unit for all of the cluster nodes Domain Domain Organizational Organizational Units Units Lead-in Computer accounts are created in organizational units *****************************ILLEGAL FOR NON-TRAINER USE****************************** You install server cluster nodes as either Windows 2000 domain controllers or as member servers It is recommended that you install Cluster service on member servers to draw away the server workload from domain controller activity You integrate cluster nodes in Active Directory as computer objects The server cluster name and all of the defined virtual servers in the cluster are not represented as computer objects However, you can publish resources, such as file shares, in Active Directory Note It is recommended that you create a separate organizational unit for all of the cluster nodes, to keep them separated from any group policies that might affect servers in Active Directory Node Domain Roles Both nodes should have the same domain role, either both member servers in the same domain or both domain controllers in the same domain Cluster nodes should not hold Flexible Single Master Operations roles, such as the Primary Domain Controller (PDC) emulator Module 3: Preparing for Cluster Service Installation 23 Existing Services and Applications Topic Objective To determine considerations for services and applications that are currently running on servers that will be installed as nodes of a server cluster Lead-in Pre-Cluster Pre-Cluster Server A running: WINS DNS DHCP Cluster Installed Cluster Installed Node A running: WINS DNS DHCP Virtual Server running: DHCP You need to determine which applications and services will migrate to a cluster Server B running: Exchange Node B: Exchange Fails *****************************ILLEGAL FOR NON-TRAINER USE****************************** Delivery Tip A computer running Windows 2000 is called a server When the Cluster service is installed, the computer is called a node Existing applications and services running on a server prior to the formation of a cluster are not normally impacted by the installation of Cluster service However, before installing Cluster service, you need to test the applications and services to ensure that they will continue to provide full functionality when the servers are installed in the cluster Some applications and services continue to run on the server post-installation, but will not take advantage of the functionality of Cluster service until they are migrated into the cluster You cannot migrate other applications into a server cluster and must uninstall them prior to installing Cluster service For example, in this slide, prior to installing Cluster service, Server A is running WINS, DNS, and DHCP You can migrate all three as a resource into the server cluster after you install Cluster service on Node A Node B is running Microsoft Exchange, which you cannot migrate into a cluster If you install Cluster service on the resource is in the process of being brought online Node B, Exchange will fail Prior to installing Cluster service on a server, you need to check with the software licensing requirements of the vendors whose applications and services are running on that server 24 Module 3: Preparing for Cluster Service Installation Lab A: Configuring Advanced Server for Cluster Installation Topic Objective To prepare the classroom computers for the installation of Cluster service Lead-in In this lab, you will prepare the student for the installation of Cluster service *****************************ILLEGAL FOR NON-TRAINER USE****************************** Objectives After completing this lab, you will be able to: Set up a shared disk for cluster installation Set up public and private networks for cluster installation Prerequisites • Before working on this lab, you must be familiar with the concepts in Course 2087A, Module 3, “Preparing for Cluster Service Installation.” Lab Setup To complete this lab, you need the following: Two computers running Microsoft Windows 2000 Advanced Server, each with a small computer system interface (SCSI) adapter installed Each computer in a student pair must have a different SCSI ID A shared external SCSI disk Each computer is connected to the shared disk with SCSI cables The shared external SCSI disk ID must be different than either of the SCSI cards of the computers in the student pair Two network adapter cards in each node of the cluster Module 3: Preparing for Cluster Service Installation Scenario You will start the lab with nothing installed except Windows 2000 Advanced Server, which is installed as a member server in the NWTRADERS domain You will work individually to prepare your computer to participate in the cluster You will set up a common drive letter on the disk that is shared by the two computers in the cluster and configure the public and private networks Your lab computers have been assigned a NetBIOS name The following exercises will refer to your computers as NodeA and NodeB Estimated time to complete this lab: 15 minutes 25 26 Module 3: Preparing for Cluster Service Installation Exercise Set up Shared Disk for Cluster Installation In this exercise, you will configure a common drive letter that Cluster service will use during the installation Applications store data on drive letters not disks For a cluster-aware application that is installed on both nodes to access data that is stored on the shared disk, both nodes in the cluster must use the same drive letter To set up a shared disk for cluster installation Complete this task from both the NodeA and NodeB computers Log on to your domain as Administrator with a password of password Click Start, point to Programs, point to Administrative Tools, and then click Computer Management In Computer Management, click Disk Management Verify that the Type for Disk is Basic Right-click Disk 1, and then click Change Drive Letter and Path In the Change Drive Letter and Paths for Disk dialog box, click Edit In the Edit Drive Letter or Path dialog box, click the Assign a drive letter drop-down box and select drive W:, and then click OK In the Confirm dialog box, click Yes Close Computer Management Module 3: Preparing for Cluster Service Installation 27 Exercise Set up Public and Private Networks for Cluster Installation In this exercise you will determine which network card that you will use for the public and private network cluster networks The classroom is configured to use a static IP number for the public network and automatic addressing for the private network You will configure the TCP/IP address To set up public and private networks for cluster installation Complete this task from both the NodeA and NodeB computers Click Start, point to Settings, and then click Control Panel Double-click Network and Dial-up Connections Right-click Local Area Connection, and then click Properties Write down the network card from the Connect using: box From the Local Area Connection Properties dialog box, double-click Internet Protocol [TCP/IP] Write down the IP address from the Use the following IP address: dialog box If Obtain an IP address automatically is selected, write down DHCP Click OK from the Internet Protocol (TCP/IP) Properties dialog box Click OK from the Local Area Connection Properties dialog box Right-click Local Area Connection, and then select Rename 10 Local Area Connection is selected If you wrote DHCP in step 6, rename Local Area Connection to Cluster Private If you wrote a static TCP/IP number in step 6, rename the connection to Cluster Public 11 Right-click Local Area Connection 2, and then click Properties 12 Write down the name of the network card from the Connect using: box 13 From the Local Area Connection Properties dialog box, double-click Internet Protocol [TCP/IP] 14 Write down the IP address from the Use the following IP address: dialog box If Obtain an IP address automatically is selected, write down DHCP _ 15 Click OK from the Internet Protocol (TCP/IP) Properties dialog box 16 Click OK from the Local Area Connection Properties dialog box 17 Right-click Local Area Connection 2, and then select Rename 18 Local Area Connection is selected If you wrote DHCP in step 14, rename Local Area Connection to Cluster Private If you wrote a static TCP/IP number in step 14, rename the connection to Cluster Public 19 Close all of the windows 28 Module 3: Preparing for Cluster Service Installation Exercise Using the Pre-Installation Checklist In this exercise, you will work with your partner to fill out the Pre-Installation Checklist This checklist is intended to help you plan your Cluster service installation Use the following Reference Table to fill in the names and IP addresses Reference Table Cluster Service Account: NWTRADERS\ClustService Quorum Disk: W:\ Server Name Node Name Cluster Name Cluster IP Virtual Server Virtual Server IP Vancouver NodeA NaCluster1 192.168.x.50 Sales 192.168.x.101 Denver NodeB NaCluster1 192.168.x.50 Sales 192.168.x.101 Acapulco NodeA NaCluster2 192.168.x.52 Marketing 192.168.x.103 Miami NodeB NaCluster2 192.168.x.52 Marketing 192.168.x.103 Lisbon NodeA EuCluster1 192.168.x.54 Engineering 192.168.x.105 Bonn NodeB EuCluster1 192.168.x.54 Engineering 192.168.x.105 Stockholm NodeA EuCluster2 192.168.x.56 Finance 192.168.x.107 Moscow NodeB EuCluster2 192.168.x.56 Finance 192.168.x.107 Bangalore NodeA AsCluster1 192.168.x.58 Support 192.168.x.109 Singapore NodeB AsCluster1 192.168.x.58 Support 192.168.x.109 Manila NodeA AsCluster2 192.168.x.60 Sustaining 192.168.x.111 Tokyo NodeB AsCluster2 192.168.x.60 Sustaining 192.168.x.111 Perth NodeA SPCluster1 192.168.x.62 Research 192.168.x.113 Brisbane NodeB SPCluster1 192.168.x.62 Research 192.168.x.113 Auckland NodeA SPCluster2 192.168.x.64 Qcontrol 192.168.x.115 Suva NodeB SPCluster2 192.168.x.64 Qcontrol 192.168.x.115 Lima NodeA SaCluster1 192.168.x.66 ITServer 192.168.x.117 Santiago NodeB SaCluster1 192.168.x.66 ITServer 192.168.x.117 Caracas NodeA SaCluster2 192.168.x.68 HRServer 192.168.x.119 Montevideo NodeB SaCluster2 192.168.x.68 HRServer 192.168.x.119 Casablanca NodeA AfCluster1 192.168.x.70 ComServer 192.168.x.121 Tunis NodeB AfCluster1 192.168.x.70 ComServer 192.168.x.121 Khartoum NodeA AfCluster2 192.168.x.72 AdminServer 192.168.x.123 Nairobi NodeB AfCluster2 192.168.x.72 AdminServer 192.168.x.123 Module 3: Preparing for Cluster Service Installation Job Aid: Pre-Installation Checklist You not need to complete each item in this Job Aid in any specific order However, you should complete each item before installing Cluster service Software Requirements Windows 2000 Advanced Server installed on all of the computers in the cluster Both nodes of the Cluster are configured as member servers or domain controllers A name resolution method, such as Domain Name System (DNS), or Windows Internet Naming System (WINS) DNS Server WINS Server (Optional) Terminal Services remote administration mode to allow remote cluster administration is recommended Hardware Requirements The hardware for a Cluster service node must meet the hardware requirements for Windows 2000 Advanced Server An internal hard drive with Windows 2000 Advanced Server installed The boot disk cannot be on the shared storage bus, which is described later A separate PCI storage host adapter (SCSI or Fibre Channel) for the shared bus This is a separate bus from the operating system Two PCI network adapters on each computer in the cluster: one for client-to-node and one for node-to-node communications An HCL-approved external disk storage unit that connects to all of the computers This storage unit will be used as the shared disk A device that supports a hardware level redundant array of independent disks (RAID) is recommended Storage cables to attach the shared storage device to all of the computers Refer to the manufacturers’ instructions for configuring storage devices All hardware should be identical, slot for slot, card for card, for all of the nodes Using identical hardware will make configuration easier and eliminate potential compatibility problems 29 30 Module 3: Preparing for Cluster Service Installation Network Requirements A unique NetBIOS cluster name Cluster Name At least five unique, static IP addresses: two for the network adapters on the private network, two for the network adapters on the public network, and one for the cluster itself Node A Public IP Address: Node B Public IP Address: Cluster IP Address: Node A Private Address: Automatic Private Addressing Node B Private Address: Automatic Private Addressing As a best practice use static IP addresses for the Private Address A domain user account for Cluster service is recommended (all nodes must be members of the same domain) Cluster Service Account: Shared Disk Requirements: All shared disks, including the quorum disk, must be physically attached to the shared bus Cluster disk drive letter(s): Verify that you can see all of the nodes from disks attached to the shared bus You can check to see all of the nodes at the host adapter setup level Refer to the manufacturer’s documentation for adapter-specific instructions You must assign unique SCSI identification numbers to SCSI devices and properly terminate the devices, as per manufacturer’s instructions You must configure all of the shared disks as basic (not dynamic) You must format all of the partitions on the disks as NTFS Module 3: Preparing for Cluster Service Installation 31 Review Topic Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Pre-Installation Considerations Identifying Hardware Considerations Assigning IP Addresses Within a Cluster Assigning Names Within a Cluster Determining Domain Considerations Existing Services and Applications 1.***************************ILLEGAL FOR NON-TRAINER USE****************************** Your manager is concerned that if the private network fails, the cluster will fail, and a single point of failure is not acceptable for a cluster solution What you need to tell your manager to assure her that Cluster service can recover from a private network failure? The private network can fail over to the public network A colleague is trying to add a shared disk on a cluster The shared disk is formatted as file allocation table (FAT) and is a basic disk Why can’t your colleague use this disk? A shared disk must be a basic disk and be formatted NTFS You are setting up a server cluster with a SCSI solution for your shared bus All hardware is on the HCL, the shared bus is properly terminated, the shared disk ID is 4, each server can see the shared disk while the other server is offline, but when both servers are online, the shared disk is unavailable to either server Why is the shared disk unavailable to both servers? Both server SCSI controllers are set to the same SCSI ID You are trying to install Cluster service on two Windows 2000 Advanced Servers in a workgroup, but are unsuccessful Why? Windows 2000 Cluster service must be installed on servers that are members of a domain THIS PAGE INTENTIONALLY LEFT BLANK ... Compatibility List for Cluster service Module 3: Preparing for Cluster Service Installation Cluster Service Compatible Systems Topic Objective To list the hardware requirements for Cluster service Lead-in... with Cluster service vi Module 3: Preparing for Cluster Service Installation Instructor Setup for a Lab Lab Strategy This lab is designed to prepare the servers for the installation of Cluster service. .. within a cluster Determine domain considerations Determine pre -installation considerations for existing services and applications 2 Module 3: Preparing for Cluster Service Installation Pre-Installation