Platform management information requirements are defined for two key areas:
Component instrumentation. Interfaces through which information is supplied by platform management components.
Management information providers. Interfaces used by applications to access platform management information.
192 System supports Windows hardware instrumentation implementation guidelines
This requirement is defined in Windows Hardware Instrumentation Implementation Guidelines, Version 1.0.
193 System includes driver support for WMI
Requirements and recommendations related to implementing WMI for Windows NT 5.0 are defined in the Windows Hardware Instrumentation Implementation Guidelines.
Support for Windows hardware instrumentation, CIM, and Win32 extension schema objects and data must be implemented as defined in the Windows Hardware Instrumentation Implementation Guidelines.
194 Management information service provider enabled by default
The management information service providers must be enabled on servers as defined in WHIIG.
Also, newly developed applications for managing WBEM-capable systems should be written to access those systems through industry-standard WBEM protocols and interfaces.
Part 2
SOHO and Enterprise Server Requirements
This part defines specific requirements for SOHO servers and Enterprise servers as they differ from the generic requirements defined in Part 1. Any requirements defined in this part supersede the equivalent requirements defined for Basic server systems in these guidelines.
Chapter 8 SOHO System Requirements 97
SOHO System Microprocessor Requirements 97
SOHO Memory Requirements 97
SOHO ACPI and Power Management Requirements 98
SOHO Bus and Device Requirements 100
SOHO Storage Device Requirements 101
SOHO Fibre Channel Controllers and Peripherals 101
SOHO Tape Drives 102
SOHO Reliability, Availability, and Serviceability Requirements 102
Chapter 9 Enterprise Server Requirements 103
Enterprise System Microprocessor Requirements 103
Enterprise System Memory Requirements 104
Enterprise Storage Device Requirements 104
Enterprise Tape Drives 104
Enterprise Reliability, Availability, and Serviceability Requirements 105
Enterprise Power Supply and Ventilation 105
Enterprise Fault-Tolerant Hardware 105
Chapter 8
SOHO System Requirements
This chapter defines the specific requirements for SOHO server systems.
Note: It is recognized that OEMs supply systems with specific feature requirements to corporations, which can include providing servers that do not include any memory pre-installed before shipping. However, for testing purposes, the system must include the minimum required components.
SOHO System Microprocessor Requirements
This section summarizes processor requirements for SOHO server systems.
195 SOHO system processor capabilities meet minimum requirements
180 MHz; 256K L2 cache required
|
|
|
Basic server requirements and recommendations for processor capabilities, L2 cache, and multiprocessor capabilities are the same for SOHO servers, with the exception of the minimum requirements for 180 MHz; 256K L2 cache.
SOHO Memory Requirements
This section defines minimum memory requirements for SOHO server systems.
196 SOHO system memory capacity meets minimum requirements
This requirement defines minimum RAM expansion for SOHO servers. For multiprocessor systems, 256 MB is required for each multiprocessor. All memory visible to the operating system as system memory must be cacheable.
SOHO ACPI and Power Management Requirements
This section defines the SOHO system and BIOS requirements for ACPI and OnNow power management.
197 SOHO system design meets ACPI 1.0 specification and related requirements
The system board on a SOHO server must support the Advanced Configuration and Power Interface Specification, Version 1.0 or higher. The following list indicates additional implementation details or differences for ACPI support on a SOHO server from those defined for Basic servers in Chapter 2, “Basic System Component Requirements.”
The required ACPI support for a SOHO server must include the following:
A power-management timer must be implemented as defined for Basic servers in Chapter 2, “Basic System Component Requirements.”
Support for a description table defining the complete hierarchy for system-board devices must be implemented as defined for Basic servers.
Bus and device enumeration using ACPI must be implemented as defined for Basic servers.
Thermal model and fan control, if implemented, must follow the implementation details defined for Basic servers and comply with Section 12 of the ACPI 1.0 specification.
At least one processor power state (either C1, C2 or C3) must be supported.
This system must not allow capabilities for disabling system ACPI support using CMOS or other means, as defined for Basic servers.
The following features are also required for SOHO servers, although similar features are only recommended or optional for Basic servers:
Power button must comply with the ACPI 1.0 specification, as described in the item, “Hardware design supports OnNow initiative,” later in this section. Either the ACPI-specified override mechanism or a separate reset switch must be supplied, and system control interrupt and necessary STS/EN bits must be provided.
Real-time clock alarm must support wake up based on a scheduled time and day of the month, with system control interrupt and necessary STS/EN bits provided. Notice that the day of month feature is defined as a requirement in this guide, although it is an optional ACPI 1.0 feature.
The S5 soft-off state must be supported, compliant with the ACPI 1.0 specification.
At least one of the S1, S2, or S3 sleep states must be implemented. Notice that one of these sleep states is required in this guide, although they are only recommended in the ACPI 1.0 specification. The S4 sleep states are not sufficient to meet this requirement.
Recommended: For maximum power savings and system response, support of the S3 sleep state is recommended.
If a USB host controller is present in the system, it must be able to wake the system using ACPI mechanisms, although this support is only recommended in the ACPI 1.0 specification.
Note: As with the related Basic server requirements, any other system-board power management or Plug and Play features must be implemented in compliance with the ACPI 1.0 specification, even if a particular feature is not a specific requirement or recommendation. This requirement also does not disallow the addition of proprietary value-added features that cannot be accomplished using ACPI.
198 SOHO hardware design supports OnNow initiative
The following support is required for SOHO server hardware in addition to OnNow hardware requirements defined for Basic server systems:
For SOHO server hardware, all devices and drivers must support the D0 and D3 power states consistent with the definitions in the Default Class Power Management Specification and the relevant device class power management reference specification, with implementation details and recommendations as defined for Basic server systems in Chapter 2, “Basic System Component Requirements.”
PCI, USB, and IEEE 1394 buses on the SOHO system must support power management requirements as defined in the related bus standards.
The user experiences the SOHO server as off when it is in a sleep state, with implementation details as defined for this optional Basic server features.
The user can easily see whether the server is working or sleeping. At a minimum, the SOHO server system must provide one or more indicators to show whether the system is in the working or sleep state, with all other implementation details as defined for this optional Basic server feature.
The user can easily control power through switches and software. The SOHO system must provide an easily accessible power switch that can be controlled by software and that supports the functionality required in Section 4.7.2.2.1 of the ACPI 1.0 specification.
To meet this requirement, an OnNow-capable SOHO server can have either a power button or sleep button. The recommended implementation for SOHO servers is to have both, following the implementation details as defined for this optional Basic server feature.
199 SOHO system startup meets requirements for OnNow support
This requirement does not apply for RISC-based servers, except for the initial requirement for fast POST. The following support is required for SOHO servers, although these capabilities are only optional features for Basic server systems:
Fast POST capabilities must be implemented, following implementation details and recommendations as defined optionally for Basic server systems in Chapter 2, “Basic System Component Requirements.”
Resume from sleep state (S1–S3) to operating system handoff must occur within 500 ms, following implementation details as defined optionally for Basic server systems. This requirement does not apply to the S4 state.
Minimal startup display must be implemented. System startup must draw the end user’s attention only in case of errors or when there is a need for user action, following implementation details and recommendations as defined optionally for Basic server systems.
|
