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.
|
- Navigate this page:
- 17. Unique Plug and Play ID is provided for each system device and add on device
- 18. “PNP” vendor code is used only to define a legacy device’s Compatible ID
- “Headless Server” Requirements
- 19. IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements
- 20.2. IA-32 system without management service processor provides properly configured legacy serial port
- 20.3. IA-32 system headless connections are null modem cables that support Carrier Detect signal
Plug and Play RequirementsThis section defines the specific requirements for Plug and Play. 16. System and device configuration meet Plug and Play requirementsRequired Windows 2000 Server implements complete support for Plug and Play configuration. Each bus and device provided in a server system must meet the current Plug and Play specifications related to its class, including:
Note: Standard system devices are excluded from the Plug and Play requirement. The system can reserve static resources for devices such as programmable interrupt controllers (PICs) 1 and 2, timer (8254 2), keyboard controller (8042), real-time clock, DMA page registers, and DMA controllers 1 and 2. For IA-32 systems, these fixed resources are located at I/O addresses under 100h and can also include a NMI. Also, this requirement does not apply to devices that are completely invisible to the operating system, such as out-of-band systems management devices or I2O hidden devices; however, these devices still must properly reserve resources using ACPI methods to avoid potential conflicts. 17. Unique Plug and Play ID is provided for each system device and add on deviceRequired Each device connected to an expansion bus must be able to supply its own unique identifier, as defined in the current Plug and Play specification for the bus that it uses. The following defines the specific requirements for Plug and Play device IDs:
The following are exceptions to the requirements for a unique Plug and Play ID:
In addition, if an OEM uses a proprietary mechanism to assign asset or serial numbers to hardware, this information must be available to the operating system using Windows hardware instrumentation technology. 18. “PNP” vendor code is used only to define a legacy device’s Compatible IDRequired All legacy devices not enumerated by the system board set interface must not use “PNP” in their vendor and device codes. The PNP vendor code is reserved for Microsoft and vendors whose hardware is specifically assigned a particular ID. Other hardware can use a PNP code only when defining a device’s Compatible ID (CID) and only after first indicating the device’s Hardware ID in the Plug and Play header.
To permit remote management of a system, it is required that all Enterprise class IA-32 servers provide headless server capabilities complying with at least one of the solutions described in guidelines #20, 21, and 22. This is recommended for Basic and SOHO class systems, and is expected to become a requirement for these classes in a future version of this guide. The three cases that these guidelines describe are, respectively: 1: The case where headless out-of-band remote management is provided by serial port hardware only. 2: The case where such capabilities are provided by a management service processor that provides external serial support, either as a sole connection or in addition to other types of connections. 3: The case where such capabilities are provided by a management service processor that provides no external serial connection capabilities. 20. IA-32 system that implements headless capabilities without management service processor provides serial headless supportRequired if system implements headless support without a management service processor This guideline addresses the minimum capabilities needed for serial headless server support if a system implements a solution for headless support but does not include a management service processor. This requirement is an optional solution to the basic requirement stated in “#19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements.” 20.1. IA-32 system without management service processor supports BIOS redirection of console output to the headless serial portIA-32 systems must provide the redirection capabilities documented in “#13.4 IA-32 BIOS boot system firmware supports console redirection to a serial port, if serial headless server support is implemented in the system.” Recommendation Recommended: Use COM1 as the headless serial port. 20.2. IA-32 system without management service processor provides properly configured legacy serial portFor use with the headless server capabilities of Windows Whistler, IA-32 systems must provide a legacy serial port that is addressable at either COM1 (03F8h) or COM2 (02F8h), configured to the default settings of 9600 bps, 8 bits, no parity, and 1 stop bit. This port must also comply with the requirements for legacy serial ports elsewhere in this document. Note: Future versions of Windows will provide additional physical connection choices for headless servers. 20.3. IA-32 system headless connections are null modem cables that support Carrier Detect signalCables used for connection to a Windows Whistler headless server on a serial port must be null modem cables that provide support for the Carrier Detect signal. Carrier Detect is required because Windows will not provide console I/O if Carrier Detect is not active. 21. IA-32 system that implements management service processor and external serial headless capability supports required external serial port and remote system resetRequired if the service processor exposes a UART interface via hardware to the operating system or if the serial port is the only full-time management connection This guideline addresses the minimum capabilities needed for headless server support with service processors that provide external serial capabilities. This requirement is an optional solution to the basic requirement stated in “#19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements.” Management service processors that provide both serial and LAN-based full-time management connections but do not provide an internal 16550 UART hardware interface (i.e. Service Processor does not provide a serial port interface or the serial port interface is provided by a Windows driver and is not available before Windows is loaded) must provide at least the capabilities in this guideline for the serial connection (except 21.2), or must provide the capabilities outlined in #22 “IA-32 system that implements a management service processor but no external serial connection meets reset and display redirection requirements” for the alternate LAN-based management connection. It is recommended that service processors with both types of the above ports provide both sets of capabilities.
21.1. IA-32 system with management service processor and external serial headless capability supports BIOS redirection of console output, plus serial port and serial headless cabling requirementsSystems with service processors that provide external serial support must meet the requirements in guideline “#20. IA-32 system that implements headless capabilities without management service processor provides serial headless support,” plus the additional requirements listed in this guideline. 21.2. IA-32 system with management service processor and external serial headless capability supports sharing of the service processor serial port with WindowsIf a management service processor provides a serial port interface externally, this port must allow unconstrained communication between an external device (such as a management platform) and Windows. This communication path must be available as soon as the loader is called. The shared serial port must be locatable via the mechanism described in Serial Port Console Redirection Table. Additionally, the service processor must comply with the requirements of Extensions to the VT100 Terminal Definition. The service processor may interrupt Windows’ use of the shared port per the mechanisms required in Extensions to the VT100 Terminal Definition. The serial port must not appear altered in any fashion from the perspective of Windows when the port is in use by the service processor. Also, the service processor’s output to the serial port must comply with Extensions to the VT100 Terminal Definition. 21.3. IA-32 system with management service processor and external serial headless capability supports remote system reset capabilitiesThe management service processor must support a remote system reset capability as described in Extensions to the VT100 Terminal Definition. 22. IA-32 system that implements a management service processor but no external serial connection meets reset and display redirection requirementsRequired if system implements headless support with a management service processor This requirement is an optional solution to the basic requirement stated in “#19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements.” For enhanced out-of-band management capabilities, systems can provide a management service processor. This processor can enable such advanced capabilities as remote system reset and assistance with disaster recovery. Note that an IA-32 system is not required to provide a management service processor. This guideline addresses the minimum capabilities needed for headless server support with service processors but no external serial connection capabilities. The management service processor must support a remote system reset capability. This capability may be provided through OEM-specific mechanisms.
Recommended: Systems with service processors provide display redirection capabilities for both text and graphics modes. 23. Uninterruptible power supply that has pass-through legacy serial port supports sharing of pass-through serial port with Windows headless capabilitiesRecommended If an uninterruptible power supply (UPS) uses an external pass-through serial port interface, this port should allow unconstrained communication among the system for which the UPS provides backup power, a management platform, and Windows. The UPS may interrupt Windows’ use of the pass-through port per the mechanisms required in Extensions to the VT100 Terminal Definition. Additionally, the UPS should comply with the requirements of Extensions to the VT100 Terminal Definition. The entire end-to-end pass-through serial path should present the serial signals from the platform under management to the management console as though from a serial port through a null modem cable as described in “#20.3 IA-32 system headless connections are null modem cables that support Carrier Detect signal.”
Directory: download download -> Performance Tuning Guidelines for Windows Server 2008 May 20, 2009 Abstract download -> Northern England’s set-jetting locations download -> Bbc archives: Beyond the programme download download -> Occupational health and safety download -> Dynatest 3031 lwd light Weight Deflectometer download -> Forth coming competitive exams download -> English Olympiad Tasks: 10 th form Аудіювання, 10 клас. Текст download -> Brush High School Morning Announcements Friday, September 05, 2014 all school download -> Year 9 The Arts — Music download -> Years 7 and 8 standard elaborations — Australian Curriculum: Music draft Download 1.64 Mb. Share with your friends:
|