Installation of FIXEdge server
on
Server Clusters
Requirements and guidelines 3
Requirements and Guidelines for Configuring Server Clusters 3
Software requirements and guidelines 3
Hardware requirements and guidelines 3
Network requirements and guidelines 4
Storage requirements and guidelines 5
Domain Controller installation 5
Server Configuration Overview 5
Server Disk Configuration 6
Server Installation 6
Creating a Cluster 10
Preparing to create a cluster 11
Installing the Windows Server2003 operating system 11
Setting up networks 11
Configuring up Remote Desktop 18
To set up a Cluster service user account 19
Setting up disks 20
Creating a new server cluster 22
Validating the cluster installation 27
Configuring subsequent nodes 27
Configuring the server cluster after installation 28
Quorum disk configuration 31
SCSI Drive Installations 32
Configuring SCSI devices 33
Testing the Server Cluster 33
Testing whether group resources can fail over 33
FIXEdge installation 33
Installation of FIXEdge as service 33
Installation of FIXEdge as console application 35
Resources 37
Requirements and guidelines
This guide provides system requirements, installation instructions, and other, step-by-step instructions that you can use to deploy server clusters with installed FIXEdge if you are using Microsoft® WindowsServer™2003, Enterprise Edition operating system.
The server cluster technology in WindowsServer2003, Enterprise Edition helps ensure that you have access to important server-based resources. You can use server cluster technology to create several cluster nodes that appear to users as one server. If one of the nodes in the cluster fails, another node begins to provide service. This is a process known as "failover." In this way, server clusters can increase the availability of critical applications and resources.
Also this guide explains how to install and configure the Microsoft Windows Server 2003, Enterprise Edition as a domain controller.
Full information about FIXEdge installation you can find in FIX Edge Quick Start Guide.
Requirements and Guidelines for Configuring Server Clusters
The section lists requirements and guidelines that will help you set up a server cluster with FIXEdge effectively.
Software requirements and guidelines
· You must have Windows Server 2003, Enterprise Edition installed on all computers in the cluster. We strongly recommend that you also install the latest service pack for Windows Server 2003. If you install a service pack, the same service pack must be installed on all computers in the cluster.
· All nodes in the cluster must be of the same architecture. You cannot mix x86-based, Itanium-based, and x64-based computers within the same cluster.
· Your system must be using a name-resolution service, such as Domain Name System (DNS), DNS dynamic update protocol, Windows Internet Name Service (WINS), or Hosts file. Hosts file is supported as a local, static file method of mapping DNS domain names for host computers to their Internet Protocol (IP) addresses. The Hosts file is provided in the systemroot\System32\Drivers\Etc folder.
· All nodes in the cluster must be in the same domain. As a best practice, all nodes should have the same domain role (either member server or domain controller), and the recommended role is member server. Exceptions that can be made to these domain role guidelines are described later in this document.
· When you first create a cluster or add nodes to it, you must be logged on to the domain with an account that has administrator rights and permissions on all nodes in that cluster. The account does not need to be a Domain Admin level account, but can be a Domain User account with Local Admin rights on each node.
Hardware requirements and guidelines
· An Intel processor–based server running Windows Server 2003 must have at least 128 megabytes (MB) of RAM. Microsoft also recommends that the server have several gigabytes of disk storage. In addition, servers should be equipped with high-speed network interface cards.
· For Windows Server 2003, Enterprise Edition Microsoft supports only complete server cluster systems chosen from the Windows Catalog. To determine whether your system and hardware components are compatible, including your cluster disks, see the Microsoft Windows Catalog at the Microsoft Web site. For a geographically dispersed cluster, both the hardware and software configuration must be certified and listed in the Windows Catalog. For more information, see article 309395, "The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog," in the Microsoft Knowledge Base.
· If you are installing a server cluster on a storage area network (SAN), and you plan to have multiple devices and clusters sharing the SAN with a cluster, your hardware components must be compatible. For more information, see article 304415, "Support for Multiple Clusters Attached to the Same SAN Device," in the Microsoft Knowledge Base.
· You must have two mass-storage device controllers in each node in the cluster: one for the local disk, one for the cluster storage. You can choose between SCSI, iSCSI, or Fibre Channel for cluster storage on server clusters that are running Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition. You must have two controllers because one controller has the local system disk for the operating system installed, and the other controller has the shared storage installed.
· You must have two Peripheral Component Interconnect (PCI) network adapters in each node in the cluster.
· You must have storage cables to attach the cluster storage device to all computers. Refer to the manufacturer's instructions for configuring storage devices.
· Ensure that all hardware is identical in all cluster nodes. This means that each hardware component must be the same make, model, and firmware version. This makes configuration easier and eliminates compatibility problems.
Network requirements and guidelines
· Your network must have a unique NetBIOS name.
· A WINS server must be available on your network.
· You must use static IP addresses for each network adapter on each node.
Important: Server clusters do not support the use of IP addresses assigned from Dynamic Host Configuration Protocol (DHCP) servers.
· The nodes in the cluster must be able to access a domain controller. The Cluster service requires that the nodes be able to contact the domain controller to function correctly. The domain controller must be highly available. In addition, it should be on the same local area network (LAN) as the nodes in the cluster. To avoid a single point of failure, the domain must have at least two domain controllers.
· Each node must have at least two network adapters. One adapter will be used exclusively for internal node-to-node communication (the private network). The other adapter will connect the node to the client public network. It should also connect the cluster nodes to provide support in case the private network fails. (A network that carries both public and private communication is called a mixed network.)
· If you are using fault-tolerant network cards or teaming network adapters, you must ensure that you are using the most recent firmware and drivers. Check with your network adapter manufacturer to verify compatibility with the cluster technology in Windows Server 2003, Enterprise Edition.
Note: Using teaming network adapters on all cluster networks concurrently is not supported. At least one of the cluster private networks must not be teamed. However, you can use teaming network adapters on other cluster networks, such as public networks.
Storage requirements and guidelines
· An external disk storage unit must be connected to all nodes in the cluster. This will be used as the cluster storage. You should also use some type of hardware redundant array of independent disks (RAID).
· All cluster storage disks, including the quorum disk, must be physically attached to a shared bus.
· Cluster disks must not be on the same controller as the one that is used by the system drive.
· You should create multiple logical unit numbers (LUNs) at the hardware level in the RAID configuration instead of using a single logical disk that is then divided into multiple partitions at the operating system level. We recommend a minimum of two logical clustered drives. This enables you to have multiple disk resources and also allows you to perform manual load balancing across the nodes in the cluster.
· You should set aside a dedicated LUN on your cluster storage for holding important cluster configuration information. This information makes up the cluster quorum resource. The recommended minimum size for the volume is 500 MB. You should not store user data on any volume on the quorum LUN.
· If you are using SCSI, ensure that each device on the shared bus (both SCSI controllers and hard disks) has a unique SCSI identifier. If the SCSI controllers all have the same default identifier (the default is typically SCSI ID 7), change one controller to a different SCSI ID, such as SCSI ID 6. If more than one disk will be on the shared SCSI bus, each disk must also have a unique SCSI identifier.
· Software fault tolerance is not natively supported for disks in the cluster storage. For cluster disks, you must use the NTFS file system and configure the disks as basic disks with all partitions formatted as NTFS. They can be either compressed or uncompressed. Cluster disks cannot be configured as dynamic disks. In addition, features of dynamic disks, such as spanned volumes (volume sets), cannot be used without additional non-Microsoft software.
· All disks on the cluster storage device must be partitioned as master boot record (MBR) disks, not as GUID partition table (GPT) disks.
Brief
Following is the brief installation scenario. To get more information how to perform particular action follow the link.
1. Install Windows 2003 Server Enterprise on all nodes of future cluster (Installing the Windows Server2003 operating system)
2. Setup network on the nodes: public, private. (Setting up networks)
a. Private network should support only TCP protocol. File sharing should be turned off.
3. Install Domain Controller if there is no domain controller in the network. (Domain Controller installation)
4. Add all nodes to the Active Directory
5. Create Cluster (Creating a Cluster)
6. Attach all nodes to the cluster (Configuring subsequent nodes)
a. Correct network cluster parameters (Setting up networks)
7. Attach Storage to the any node
8. Prepare Storage (SCSI Drive Installations)
a. Start Storage Administrator (CTRL+M at startup)
b. Install storage to work in cluster mode
i. Objects>Adapter>Initiator ID = 6
ii. Objects>Adapter>Cluster Mode = Enabled
iii. Objects>Adapter>Emulation = Mass Storage
c. Create RAID array
i. Configuration>New configuration
ii. select all hard drives (Space)
iii. Mark end of RAID array (Enter)
iv. Start configuration (Enter)
v. Select Array (Space)
vi. Accept Configuration (F10)
vii. Provide following settings (RAID=5) and choose "Accept"
viii. Initialize, (Space), (F10), Yes
9. Install FIXEdge on all nodes (FIXEdge installation)
10. Add Storage and two services FE and Apache to the cluster resources.
Domain Controller installation
If you have domain controller installed in you network skip this section and continue from Creating a Cluster chapter.
Server Configuration Overview
Figure 1 shows the basic server configuration.
Server Disk Configuration
To use a single server, you will need a server with either two disk drives or a single disk drive with two partitions.
The first disk or partition holds Windows Server 2003 and other files for the common infrastructure, such as the Windows Installer packages and application source files. The second disk or partition is reserved for Active Directory log files and procedures required by other step-by-step guides.
Each disk or partition must hold several gigabytes of information, and each disk or partition must be formatted for the NT file system (NTFS). The steps for creating and formatting partitions are contained in this guide.
Server Installation
If you have Windows 2003 Server installed go to the Configuring Your Server as a Domain Controller paragraph. To begin the installation procedure, boot directly from the Windows Server 2003 CD. Your CD-ROM must support bootable CDs.
Note: When you configure partitions and format drives, all data on the server hard drive is destroyed.
Beginning the Installation
Setup creates the disk partitions on the computer running Windows Server 2003, formats the drive, and then copies installation files from the CD to the server.
Note: These instructions assume that you are installing Windows Server 2003 on a computer that is not already running Windows. If you are upgrading from an older version of Windows, some of the installation steps may differ.
To begin the installation
1. / Insert the Windows Server 2003 CD in the CD-ROM drive.2. / Restart the computer. If prompted, press any key to boot from the CD.
The Windows Server 2003 installation begins.
3. / On the Welcome to Setup screen, press Enter.
4. / Review and, if acceptable, agree to the license agreement by pressing F8.
Note:If you had a previous version of Windows Server 2003 installed on this server, you might get a message asking if you want to repair the drive. Press Esc to continue and not repair the drive.
5. / Follow the instructions to delete all existing disk partitions. The exact steps will differ based on the number and type of partitions already on the computer. Continue to delete partitions until all disk space is labeled as Unpartitioned space.
6. / When all disk space is labeled as Unpartitioned space, press C to create a partition in the unpartitioned space on the first disk drive (as applicable).
7. / If your server has a single disk drive, split the available disk space in half to create two equal-sized partitions. Delete the total space default value. Type the value of half your total disk space at the Create partition of size (in MB) prompt, and the press Enter. (If your server has two disk drives, type the total size of the first drive at this prompt.)
8. / After the New <Raw> partition is created, press Enter.
9. / Select Format the partition using the NTFS file system <Quick>, and then press Enter.
Windows Server 2003 Setup formats the partition and then copies the files from the Windows Server 2003 Server CD to the hard drive. The computer restarts and the Windows Server 2003 Installation Program continues.