Enterprise and Mid-Range Server Platform
Processor Brick

Mid-range servers consist of the platform hardware and operating system that together support the operating environment for applications and databases that serve a smaller group of users.Because the distinctions between enterprise and mid-range servers depend on subjective estimates of workload magnitude, this brick addresses both enterprise and mid-range servers. These standards are meant to provide guidance when selecting a server for a new application or when upgrading the server environment for an existing application. It cannot replace the capacity planning and operational support analysis needed to ensure the new server environment (including storage subsystems and peripherals) that is not addressed here is capable of meeting the size, maintainability, performance, and availability requirements of the business. This brick provides baseline information and the future direction for deploying enterprise and mid-range servers at NIH in terms of the preferred hardware platform.

• IBM eServer zSeries is considered tactical and strategic because there is greater potential for new business for the zSeries than for any other mainframe technology. It is also being considered as a Linux server platform and for ongoing DB2 support.
• SGI MIPS Technologies are currently used in a CIT special purpose scientific environment and are therefore classified as containment.
• HP Alpha and HP PA-RISC product lines are classified as containment because, according to Gartner research and HP’s own published position, HP’s strategy for the Alpha product line is to support the install base of their existing customers and to enable transition of those customers to newer technologies.
• AMD Opteron processor will address enterprise server requirements, while AMD Athlon will address mid-range server requirements.
• Proprietary appliance servers are considered containment due to their specialized purpose.
• NIH will seek opportunities to pilot Blade server technologies at the enterprise level, leveraging lessons learned from smaller implementations.
• NIH should evaluate virtualization technologies and vendor strategies based on cost reduction (hardware, software and staffing — now and in the future) and agility improvements (flexibility to handle changing workload requirements without difficulty or significant expense). For the next several years, vendors will provide new virtualization solutions, which should be considered for deployment at NIH if they can deliver a shorter return on investment and ease future technology transitions.
• Tactical and strategic products were selected to leverage NIH's investment in products that are a proven fit for NIH's known future needs. Leveraging baseline products in the future will minimize the operations, maintenance, support and training costs of new products.
• Some baseline products have been designated retirement and containment. These products are either not as widely or successfully deployed at NIH, or they do not provide as much functionality, value, or Total Cost of Ownership as the selected tactical and strategic products.