Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators

Because the focus of this book is deploying Windows Server 2003 on ProLiant servers, it's important to provide you with information on the ProLiant server line as an aid to selecting ProLiant servers for various roles in the Windows Server 2003 enterprise. Although I recognize that with the evolution of ProLiant server development, it's impossible for printed media to keep up, the ProLiant line of servers has been designed to maintain model identification as much as possible to minimize name changes and still identify new servers. For instance, the ProLiant DL380 line has been produced for a number of years and gone through several model numbers, but still maintains the DL380 name. New models are identified as "generation" numbers . For instance, the DL380 G1 was generation 1, whereas the next version was identified as DL380 G2. The basic characteristics, as described in this section, remain the same as well as the intended use.

Of course, it's best to get the latest hardware information from the ProLiant server Web site at http://www.hp.com/servers/proliant .

Ultra -Dense ProLiant Blade Servers (BL)

Although the blade server architecture might seem new, HP began pioneering enterprise blade server design for industry standard applications in 2001. HP moved to the second phase of blades in August 2002 as the first major vendor to bring multiprocessor blades to enterprise customers. Today, HP delivers a rather diverse line of blade products including the ProLiant BL-e class, single processor, ultra-dense, front-end blades; and advanced ProLiant BL-p class dual and, quad-processor blades for midtier and back-end applications. The newer BL-p class server blades are regarded as "enterprise class" servers.

The basic idea behind blade servers is consolidation. The first time I saw a blade server, it was difficult to imagine you could have a server that looked about the same size as a high-end video card ten years ago. It is truly impressive to see a comparison of the amount of space that regular servers take, as opposed to the same number of blades in an enclosure. Let's look at some basic features of blades to help you evaluate their potential value in your enterprise.

By allowing servers to share resources provided by an enclosure, individual servers can be made much more compact. The architecture not only allows you to put a lot more processing power into a smaller space, but its modular design also simplifies deployment. In terms of hardware, two basic components are in a blade server solution: the blades themselves and the enclosure that houses them. The enclosure connects the blades installed to the shared resources, and the enclosure can be configured for I/O options according to your needs. The blades are complemented by automated deployment software that utilizes scripting or drive imaging to rapidly deploy a server. Over a gigabit Ethernet connection using drive imaging, a server can be deployed in ten minutes. Blade servers save space, drastically reduce cabling, and simplify installation and the processes in deploying and managing servers. The ProLiant BL-p series offers multiple processors, the benefits of the blade architecture, and many of the enterprise class server features found in ProLiant 300 and 500 series rack mount servers. As an example, the BL20p blade delivers these enterprise-class capabilities:

• Dual-processor capability

• 8GB memory capacity

• Integrated Smart Array 5i Plus

• Dual 3.5-inch SCSI Hot Plug drive bays

• Dual Fiber Channel ports, optional for redundant SAN connections

• Three 10/100/1000T Ethernet ports

• One iLO (integrated Lights-Out) advanced management port

• Rack-centralized external shared redundant hot-plug power

These capabilities make the BL20p blades ideal for hosting these applications:

• Web-hosting

• E-commerce

• Computational cluster

• Terminal Server Farm

• AV, streaming media

• Messaging front-end and mobility

• Small database

• Application server

Add in the benefit of storage consolidation to ProLiant BL-p class blade servers by attaching and even booting blades from a SAN, and you can build a robust and rapidly adaptable infrastructure. For some really cool ideas on using blade servers in advanced architectures and configurations, check http://www.phptr.com/title/0131467581 for technical papers on "Automated Provisioning with ProLiant Servers." I have included additional information about the ProLiant blade servers and options in Appendix B, "ProLiant Product Details."

Server Classes

Server classes are defined in the Microsoft Systems Architecture Internet Data Center (MSA IDC) documentation, which includes recommended applications for each class of server. For example, ProLiant BL-p class blade servers meet or exceed the requirement to fill the following roles:

• Internet Security and Authentication (ISA) server firewall server

• Microsoft Internet Information Services (IIS) Web server

• AD DCs

• Application Center 2003 staging servers

• Microsoft Operations Manager (MOM) server

• NetIQ AppManager management server

• DNS server

• File Transfer Protocol (FTP) server

• Simple Mail Transfer Protocol (SMTP) Server

This definition is used to demonstrate how the BL-p series blade features meet data center server classification.

That document actually identifies several ProLiant models into their classifications of basic, light, medium, and heavy duty. I have included ProLiant server model descriptions in Appendix B, classified as one of these four levels of servers.

The MSA IDC documentation uses server class definitions to define and categorize server capabilities.

The ProLiant Servers in this section are classified based on this documentation, which offers a well-defined , comprehensive, and structured approach to cover all aspects of building an IDC based on industry standards. The MSA IDC documentation is available at the Microsoft Web site.