A reference for Designing Servers and Peripherals for the Microsoft® Windows® 2000 Server Family of Operating Systems Intel Corporation and Microsoft Corporation Publication Date—June 30, 2000



Download 1.64 Mb.
Page3/38
Date31.01.2017
Size1.64 Mb.
#13957
1   2   3   4   5   6   7   8   9   ...   38

Legacy Reduction and Removal


The PC platform that is part of the heritage of today’s server systems has evolved by adding and retaining technologies. As a result, the evolution and “history” cycle for many technologies imposes a burden that impacts cost, performance, and support—particularly in the server marketplace where PC legacy items reduce the advantages brought by newer technologies. These legacy technologies are present in hardware, firmware, BIOS code, and operating systems.

The Hardware Design Guide for Windows 2000 Server continues to address the transition to newer technologies with the introduction of alternatives to serial port based debug for IA-32 platforms, Universal Serial Bus (USB), and other technologies.. In the future, more guidelines will be published to facilitate the continuing migration of older technologies out of the server platform. Intel and Microsoft welcome and invite input from the industry on legacy reduction in servers, and on issues that may need to be considered in future versions of the Hardware Design Guide.


How to Use This Guide


Read the first chapter for an overview, and read Chapters 2 and 3 to gain an understanding of the overall system requirements. Study the other chapters to understand details about specific device classes and issues for server hardware.

Chapter

Contents

Chapter 1: Overview of Server Design Issues

Presents overview of server classes and design issues.

Chapter 2: System Component Requirements

Presents general system requirements.

Chapter 3: Bus and Device Requirements

Presents general bus and device requirements for server systems.

Chapter 4: Networking and Communications Requirements

Defines basic feature requirements for network adapters and other related communications hardware.

Chapter 5: Storage Device Requirements

Defines requirements for controllers, hard drives, tape drives, CD drives, and related devices.

Chapter 6: Physical Design and Hardware Security Requirements

Defines requirements for physical design and hard­ware security, such as requirements for connectors, case and component locks, and so on.

Chapter 7: Reliability, Availability, and Serviceability Requirements

Provides design guidelines related to ease of use and ease of maintenance issues.

Appendix A: Server Requirements Checklist

Provides a summary checklist of requirements defined in these guidelines.

Glossary

Defines technical terms and acronyms related to hardware and Windows operating systems.

As co-authors of this design guide, Intel and Microsoft provide clarification and interpretation of the requirements and recommendations in this document. Please send questions or requests for clarification by e-mail to:

designguide@intel.com
serverdg@microsoft.com

Conventions Used in This Guide


The following conventional terms, symbols, abbreviations, and acronyms are used throughout this guide. In addition, see the Glossary later in this guide.

Conventional Terms


Add-on devices

Devices that are traditionally added to the base server system to increase functionality, such as audio, networking, graphics, and so on. Add-on devices fall into two categories: devices built onto the system board set and devices on expansion cards added to the system through a system-board connector such as Peripheral Component Interconnect (PCI).



Intel Architecture, IA-64, and IA-32

Refers to computers based on 64-bit and 32 bit microprocessors that use the Intel Architecture instruction set, such as Intel Pentium, Intel Pentium with MMX technology, Pentium Pro, Pentium II, Pentium II Xeon, Pentium III, Pentium III Xeon, Itanium, or compatible processors.



System devices

Also on-board devices. Refers to devices on the system board set such as interrupt controllers, keyboard controller, real-time clock, direct memory access (DMA) page registers, DMA controllers, memory controllers, floppy disk controller (FDC), AT-Attachment (ATA) ports, serial and parallel ports, PCI bridges, and so on. In today’s servers, these devices are typically integrated with the supporting chipset.



Windows 2000 or Windows 2000 Server

Refers to the Microsoft Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter operating system, including any add-on capabilities and any later versions of these operating systems.

The following describes the product name changes for operating systems based on Windows NT® technology offered after Windows NT 4.0.

Old New

Windows NT Windows 2000

Windows NT Server Windows 2000 Server

Windows NT Server, Enterprise Edition Windows 2000 Advanced Server

(no equivalent) Windows 2000 Datacenter Server
For a list of acronyms and definitions of technical terms, see the Glossary later in this guide.

Required vs. Recommended Features in This Guide


The system requirements defined in this publication provide guidelines for design­ing servers that deliver an enhanced user experience when implemented with Windows 2000 Server. These design requirements are not the basic system require­ments for running the Windows 2000 Server operating system. In this guide, hard­ware features are described as Required, Recommended, or Optional as follows:

  • Required. These basic hardware features must be implemented in order for hardware to qualify as being in compliance with Hardware Design Guide Version 3.0 for Windows 2000 Server requirements.

  • Recommended. These features add functionality supported by the Windows 2000 operating system. Recommended features take advantage of the native capabilities of hardware device drivers included with the operating system, usually without imposing major cost increases.

Notice that for compliance testing, if a recommended feature is implemented, it must meet the requirements for that feature that are defined in this guide. Some recommended features could become requirements in the future.

  • Optional. These features are neither required nor recommended, but if the feature is implemented in a system, it must meet the specified requirements to be in compliance with these guidelines. These features are not likely to become requirements in the future.

In this guide, the following terms are used in regard to the requirements:



  • Must: Required

  • Should: Recommended


Note: It is recognized that original equipment manufacturers (OEMs) supply systems with specific feature requirements to corporations, where customers integrate the desired solution on site. For example, a customer could specify a minimum configuration without disk drives.

Systems designed for specific corporate customers are exempt from related minimum requirements defined in this guide. Such exemptions are noted in this document. However, for compliance testing of these requirements, the system must include at least the minimum required components.




Download 1.64 Mb.

Share with your friends:
1   2   3   4   5   6   7   8   9   ...   38




The database is protected by copyright ©ininet.org 2024
send message

    Main page