Maintenance mode has changed as well this mode now

This preview shows page 6 - 7 out of 10 pages.

Maintenance mode has changed as well. This mode now basically shuts off health monitoring ona node for a period of time so that it does not fail while you work on it.Another new feature is support for Internet Protocol version 6 (IPv6). The IPv6 addressingprotocol is emerging as an important factor in the growth of the Internet. IPv6 specifiesaddresses that are 128 bits long, compared to IPv4 addresses, which are 32 bits long. Thisgreater address length allows for a much larger number of globally unique addresses toaccommodate the explosive growth of the Internet around the world.Importantly, IP address assignments via DHCP are also allowed in Windows Server 2008.Windows Server 2008 failover cluster nodes can also be on different logical subnets. If a givencluster node is configured to obtain its IP address via DHCP, then IP address resources willautomatically be generated using DHCP for dependencies on network name resources. This is a“per-interface” configuration: if a node uses a static address, then the IP address resource willallow for static addressing only. Interfaces that are not configured with a default gateway will beconfigured for internal cluster communications only and client access will not be allowed unlessa configuration change is made inside the snap-in for that network.These changes afford much more flexibility in implementing geographically dispersed clusters:administrators no longer have to stretch virtual local area networks (VLANs) across the WAN toaccommodate geographically distant servers that are on different subnets. Failover cluster nodescan now reside on completely different subnets. Moreover, the network latency requirements inWindows Server 2003 server clustering have been removed from Windows Server 2008 failoverclustering; the failover clustering heartbeat requirement has also become fully configurable.Geographically dispersed clusters are easier to deploy and more technically feasible withWindows Server 2008 failover clustering.Windows Server 2008 also features a new quorum model: Majority Quorum Model. Nodes inWindows Server 2003 R2 Enterprise Edition server clusters use a quorum to track which nodeowns a clustered application. The quorum is the storage device that must be controlled by theprimary node for a clustered application. Only one node at a time may own the quorum. Incontrast, the server clusters in Windows Server 2008 incorporate the benefits of single quorumdevice server clusters and Majority Node Set clusters from Windows Server 2003 R2 EnterpriseEdition.In Windows Server 2008, the term “quorum” refers to a majority of votes for which cluster nodecontrols the cluster and cluster resources, as opposed to being a reference to a particular diskresource in the cluster. By default, nodes and storage all get a vote in Windows Server 2008failover clusters. As long as a simple majority of votes are present, the cluster can stay up (forexample, a single node and shared storage, or both of the nodes without shared storage, in thecase of a two-node cluster). However, this is fully configurable: an administrator could set onlynodes to get votes, for example, in which case the quorum would behave similarly to a MajorityNode Set cluster in Windows Server 2003 R2 Enterprise Edition.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 10 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Fall
Professor
NoProfessor
Tags
Windows 2000

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture