V5R2 Windows Administration, Microsoft Clustering IBM Corporation j02_wclusaug20.prz 08/22/02 1

Transcription

1 V5R2 Windows Administration, Microsoft Clustering j02_wclusaug20.prz 08/22/02 1

2 Agenda Windows Administration Run a Windows command Server Integration Software Miscellaneous enhancements: Auto Cartridge Loader (ACL) for 3570, 3580 and 3590 devices for backup/restore operations Windows system drive can now be up to 64,000 MB Windows Cluster Support j02_wclusaug20.prz 08/22/02 2

3 Notes: Agenda This foils summarizes most of the windows integration enhancements for V5R2. Following foils expand on the new service wizards and support for Microsoft clustering support. Miscellaneous enhancements discussed only on this foil are: Auto Cartridge Loader: Customers who have systems with large amounts of data often have Auto Cartridge Loader (ACL) tape devices (3570, 3580 and 3590) for use with backup/restore operations. Support is now added in the Windows integration product for ACLs to automatically load the next tape cartridge in the magazine during backup/restore operations initiated from the Windows Server. Windows system drive can now be up to 64,000 MB j02_wclusaug20.prz 08/22/02 3

4 Windows Administration enhancements Run a Windows command on a managed server Install, uninstall Latest Version Latest Service Pack Hot Fix j02_wclusaug20.prz 08/22/02 4

5 Notes: Windows Administration enhancements In V5R2 iseries Navigator Windows Administration adds the ability to easily run a command on a selected Windows server and get assistance as shown in this foil, with installing and uninstalling Windows operating system: Latest Version Latest Service Pack Hot Fix As you can see you also can install the latest version and service pack in a single link from iseries Navigator. The Microsoft Cluster support, as described in the following foils, can be managed from iseries Navigator the same way other Windows servers are managed. The Microsoft Clustering server(s) can be managed the same way a standard Windows server is administered under iseries Navigator is installed - start, shutdown, status, and so on. Microsoft Cluster Services functions are configured and managed directly through the Microsoft interface - not through iseries Navigator. From the iseries interface, the cluster server looks just like any other Windows server. Additionally, user administration enhancements include support for organizational units and improved control of domain enrollment processing. j02_wclusaug20.prz 08/22/02 5

6 Microsoft Clustering Service iseries Windows integration support for Microsoft Clustering Service Support for Windows 2000 Advanced Server or Windows.NET Enterprise Server Two IXS (resource type 2890 or 2892) Two xseries servers attached via IXA (resource type 2689) Utilize the 16 new shared storage spaces that are available with V5R2 The storage spaces can be switched and the applications can be automatically restarted to reduce the length of the system outage Storage spaces must reside in same iseries partition j02_wclusaug20.prz 08/22/02 6

7 Notes: Microsoft Clustering Service A server cluster is a group of independent servers running Cluster service and working collectively as a single system. Every single server in the cluster is called a cluster node. Server clusters provide high-availability, scalability, and manageability for resources and applications by grouping multiple servers running Windows 2000 Advanced Server or Windows.NET Enterprise Server. The purpose of server clusters is to preserve access from clients to applications and resources during failures and planned outages. If one of the servers in the cluster is unavailable due to failure or maintenance, resources and applications move to another available cluster node. While Cluster Service does not guarantee non-stop operation, it provides availability sufficient for most applications if you have to rely on non-stable Windows applications. Cluster service can monitor applications and resources, automatically recognizing and recovering from many failure conditions. This provides greater flexibility in managing the workload within a cluster, and improves overall availability of the system. Windows 2000 and.net support two different cluster technologies which can be used independently or in combination: Cluster service This service is primarily to provide failover support for applications such as databases, messaging systems, and file/print services. Cluster service support 2-node failover clusters in Windows 2000 Advanced Server and 4-node clusters in Windows.NET Enterprise Server. Network Load Balancing This service balances incoming IP traffic across clusters of up to 32 nodes. Network Load Balancing enhances both the availability and scalability of Internet server-based programs such as Web servers, streaming media servers, and Terminal Services. j02_wclusaug20.prz 08/22/02 7

8 Some Terminology Cluster and cluster operations: Form a cluster Join a cluster Node and node-to-node communication Quorum Resource Shared drives j02_wclusaug20.prz 08/22/02 8

9 Notes: Some Terminology Forming a cluster The first node of a cluster to install the Cluster service attempts to gain control of the quorum resource and forms the cluster by creating cluster recovery databases. Windows 2000 Advanced server allows for two-node clusters while Windows.NET Enterprise Server allows for four-node clusters. Joining a cluster Additional nodes join an existing cluster when they can communicate with another active clustered node and can validate the node name and version compatibility. Node A node is a network server that participates in a Windows cluster. A cluster is formed by joining together two or more network servers from the same iseries server partition. All jointed network servers share a common quorum resource drive, which appears on a shared SCSI bus, and can communicate with each other through the Virtual Ethernet. Each node can detect the other nodes as they join or leave the cluster. Node-to-node communication Internal communication between clustered nodes uses the Virtual Ethernet as the private network (or interconnect) that carries the heartbeat. The Cluster service on each node uses a heartbeat to keep track of the current state of the nodes within the cluster. The Cluster service uses the heartbeat to: Determine when a failover to another node should occur Synchronize the cluster databases on each node Verify node failures during a cluster configuration change. The private network uses the single network Virtual Ethernet model. Quorum Resource Every cluster contains a single drive designated as the quorum resource. The quorum resource is a shared disk where the Cluster Services write log files and configuration parameters to. The information on this disk is used in case of failure of one node to resume the operations on the remaining nodes. Therefore the quorum resource must be accessible from all cluster nodes at the same time. In the iseries this disk type is implemented by a special type of Network Storage Space. This Network Storage Space should be named as the cluster is named and the recommended size is 505 MB or larger. Shared drives Network server storage spaces can be linked as shared using the Add Server Storage Link (ADDNWSSTGL ACCESS(*SHRUPD)) parameters once a quorum resource drive has been created and linked to a node. Drives which are shared appear to Windows as though they were on a common shared storage bus and can be controlled as separate resources by the Cluster service. These drives can be failed over to another node in the cluster. j02_wclusaug20.prz 08/22/02 9

10 Planning Number of used static IP addresses Cluster s unique network name Cluster s IP address Virtual Ethernet Port to use Disks to be shared in the cluster User profile the cluster service runs under Applications to run on the cluster j02_wclusaug20.prz 08/22/02 10

11 Notes: Planning Number of used static IP addresses According to the number of nodes you want to have in the cluster you must have a sufficient number of unique IP addresses. These are for example for a two node cluster: Two external IP addresses for the both nodes (under these addresses you can reach each single node over the network) One external IP address for the cluster (under this address you can manage the cluster and this address is always reachable as long as the cluster is up and working) Two internal IP addresses for the two ends of the virtual internal LAN connection, the so called private LAN. Cluster s unique network name You must define a unique name for the cluster on your network. Under this name you will find the cluster in your network neighborhood. Cluster s IP address For management purposes and to realize a high available connection to one of the cluster nodes, the cluster must have its own external IP address. Virtual Ethernet Port to use You have to decide which of the ten available internal virtual ethernet ports you want to use for the private network connection. All nodes must make use of the same interface out of (VRTETH0 to VRTETH9). Disks to be shared in the cluster Think about which data should be managed by the cluster. Select only the really important data to be steadily available. At least one disk, the quorum disk, must be managed by the cluster on the shared bus. User profile the cluster service runs under Define a new user profile with administrative privileges like Clusteradmin or anything like this. The user is needed for the configuration and the start of the cluster service, because the cluster service registers itself with that user name to the servers. This user name and password must be the same on all existing cluster nodes. If you install domain member servers as a cluster you can create this user prior to the cluster installation. Otherwise you have to do the actual creation of the user before the final cluster service installation. Applications to run on the cluster If you want to run applications in an high availability scenario, these needs further more planning. Refer to Microsoft s documentation or the vendors documentation what to do to enable the application in a cluster. j02_wclusaug20.prz 08/22/02 11

12 Install Windows Cluster Service Installing on a new Windows server Easiest way to configure INSWNTSVR command Cluster name (CLU) parameter Name that the cluster will be known by Cluster configuration (CLUCFG) parameter Used to define the cluster Used to configure the quorum resource Clustering connection port Requires matching Virtual Ethernet port Additional configuration steps on Windows console Before installing Windows Cluster Service on Windows side j02_wclusaug20.prz 08/22/02 12

13 Notes: Install Windows Cluster Service Use the Install Windows Server (INSWNTSVR) command with the following parameters that specify the cluster configuration information: Cluster name (CLU) parameter The Cluster name (CLU) parameter provides the name that the cluster will be known by. This is used by administrators to connect to the cluster and represents the group of independent network server nodes which will work together as a single system. The name entered for the cluster name is also used as the name of the network server storage space that is created and will serve as the quorum resource for the cluster. Cluster configuration (CLUCFG) parameter The Cluster configuration parameter (CLUCFG) is used to define the cluster and configure the quorum resource network server storage space. Additionally, this information is used to validate that any secondary nodes have the proper OS/400 configuration necessary to create the virtual cluster connections for the shared storage devices and the Virtual Ethernet port that will be used for the private clustering interconnect. The cluster configuration value of *CLU will retrieve the cluster configuration from the existing quorum resource network server storage space specified on the CLU parameter, Note: The clustering connection port requires configuration of a matching Virtual Ethernet port. After you run the INSWNTSVR command (and the Windows install completes) and before you install the Windows Clustering service on the Windows side, you must perform additional configuration steps on the Windows console. j02_wclusaug20.prz 08/22/02 13

14 Install Windows Cluster Service Install on an existing Windows server Create a storage space Quorum resource *NTFSQR format Configure virtual ethernet connection port Matches the connection port for quorum storage space Link the quorum drive to the NWSD *SHRUPD Additional configuration steps on Windows console Before installing Windows Cluster Service on Windows side j02_wclusaug20.prz 08/22/02 14

15 Notes: Install Windows Cluster Service You can install Windows Cluster service on an existing Windows 2000 Advanced server that runs on a supported file server resource with V5R2 Integration for Windows Server software. If you installed the server before V5R2, ensure that the server has performed an Install release from iseries. This ensures the availability of all server functions required to install the Windows Cluster service. To install Windows Cluster service on an existing server, perform the following tasks: Create a storage space (quorum resource): The first step is to create a storage space to use as the quorum resource. To create a storage space, use the Create NWS Storage space (CRTNWSSTG) CL command and specify the special format *NTFSQR. The name of the network server storage space should match the name of the cluster you are creating. The recommended size is 505 MB or larger. The command prompts for the following cluster information, which you need to provide: Cluster domain name Virtual Ethernet connection port IP Address for the Windows cluster Subnet mask for the Windows cluster Configure the Virtual Ethernet connection port The next step is to configure the Virtual Ethernet connection port that you want to use for the private cluster communication. The Virtual Ethernet port that you use must match the connection port you specify with the quorum resource network server storage space. Link the quorum resource drive to the network server description Link the quorum resource storage space to the network server by using the Add Server Storage Link (ADDNWSSTGL) command, using ACCESS(*SHRUPD), DYNAMIC(*YES) and DRVSEQNBR(*QR). Note: During installation of Cluster service on the first node, all other nodes must be varied off prior to Windows booting. Additional shared storage devices can be created and linked at this time. All shared storage spaces must be *NTFS and linked with ACCESS(*SHRUPD) After you complete the steps above and before you install the Windows Clustering service on the Windows side, you must perform some additional configuration steps on the Windows console. j02_wclusaug20.prz 08/22/02 15

16 Preparing Windows Format the quorum resource as NTFS Label same name as the cluster Same name as the quorum resource storage space Configure private network adapter For use by Windows Cluster service j02_wclusaug20.prz 08/22/02 16

17 Notes: Preparing Windows After you install the Windows server, you need to prepare the server to install the Windows Cluster service. To prepare Windows before you install the Windows Cluster service, perform the following tasks: The first step to prepare Windows for a Windows Cluster installation is to format the quorum resource as NTFS. Formatting the quorum resource is not only required to install the Windows Cluster service, it is also the first step when installing the first node of a cluster. The quorum resource appears as an unformatted E: drive. You should format the volume and label it using the same name as the cluster, which is also the name of the quorum resource network server storage space name. Also format any other shared storage spaces at this time. It is also recommended that you assign a fixed drive letter to this drive and any other shared storage drives. Note: The drive letter assigned to all storage spaces on the shared storage bus must be the same on all nodes of the cluster. Next, configure the private network adapter for use by the Windows Cluster service by completing the following steps on the first node in your cluster: In Windows, right-click My Network Places and select Properties Right-click the Local Area Connection 2 icon. Note: Which network adapter is private and which is public depends on how you configured the server. This information assumes the following: The first network adapter (Local Area Connection) is connected to the public network by using a physical LAN adapter under the Integrated Windows server The second network adapter (Local Area Connection 2) is the Virtual Ethernet adapter configured as the cluster configuration connection port that you want to use as the private cluster network The third network adapter (Local Area Connection 3) is the private Virtual Ethernet point-to-point connection to OS/400 and should not be enabled for any clustering use The number and order of network adapters may not be the same, depending on the physical and virtual configuration of the server and the network. Click Status to display the Local Area Connection 2 Status window, which shows the connection status, as well as the speed of connection. In the Local Area Connection 2 Status window, click Properties. In the Properties dialog box, make sure that the contents of the Connect using field contains IBM iseries Virtual Ethernet x, where x matches the *VRTETHx that you specified for the cluster configuration connection port. Click Close, then click Close again. For clarity, you should rename your Local Area Network Icons. For example, you might want to change the name of Local Area Connection 2 to something like 'Private Cluster Connection'. The following foils show an example sequence of Windows Cluster Services configuration with the window sequence indicated by the red numbers within the circles. j02_wclusaug20.prz 08/22/02 17

18 Run the Cluster Service Configuration Wizard 1 of 6 Configure First Cluster Node j02_wclusaug20.prz 08/22/02 18

19 Run the Cluster Service Configuration Wizard 2 of 6 Configure First Cluster Node 6 5 j02_wclusaug20.prz 08/22/02 19

20 Run the Cluster Service Configuration Wizard 3 of 6 Configure First Cluster Node j02_wclusaug20.prz 08/22/02 20

21 Run the Cluster Service Configuration Wizard 4 of 6 Configure First Cluster Node j02_wclusaug20.prz 08/22/02 21

22 Run the Cluster Service Configuration Wizard 5 of 6 Join Cluster Nodes 1 2 j02_wclusaug20.prz 08/22/02 22

23 Run the Cluster Service Configuration Wizard 6-6 Join Cluster Nodes 3 4 j02_wclusaug20.prz 08/22/02 23