chapter 1 introduction - dell · prescriptive architecture guide, chapter 1, introduction 1 the msa...

Version 1.5

Chapter 1 Introduction

Prescriptive Architecture Guide

Abstract

This chapter provides the information necessary to begin deploying the Microsoft® Systems Architecture (MSA) Internet Data Center (IDC) infrastructure, including lists of hardware and software used in the test implementation. All personnel involved in the deployment process should read this chapter.

Copyright © 2002 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. Trademark Information EMC2, EMC, and Symmetrix are registered trademarks and EMC Enterprise Storage, The Enterprise Storage Company, The EMC Effect, Connectrix, CLARiiON, EMC ControlCenter, ESN Manager,and EMC Navisphere are trademarks of EMC Corporation. Microsoft, Windows, Windows NT, Active Directory, ActiveX, JScript, NetMeeting, SQL Server, and Visual Basic are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

EXECUTIVE SUMMARY.........................................................1 Implementation Task Order 2 Who Should Perform Each Task 4

CHAPTER SUMMARIES.........................................................5

HARDWARE AND SOFTWARE USED TO BUILD THE ENVIRONMENT.................................................................8 Standard Hardware Builds 8

STORAGE HARDWARE USED ................................................9 EMC CLARiiON FC4700 and Dell|EMC FC4700 9 Connectrix DS-16B2 (Brocade SilkWorm 3800) 9

SERVER HARDWARE USED ................................................10 Dell PowerEdge 1650 10 Dell PowerEdge 6450 10 Dell PowerEdge 8450 11

MANAGEMENT SERVER STORAGE AND SOFTWARE PLACEMENT ..................................................................12

Management Software Placement 12

NETWORK HARDWARE USED.............................................13

STANDARD SOFTWARE BUILDS .........................................14 Software Used 14

DOCUMENTATION OVERVIEW ...........................................15

AUDIENCE.........................................................................16

STYLE CONVENTIONS........................................................17

APPENDIXES.....................................................................18 Appendix 1.1 – Software and Hardware Requirements 18 Appendix 1.2 – Architecture Diagram 18

CONTENTS

Prescriptive Architecture Guide, Chapter 1, Introduction 1

The MSA IDC is a program developed by Microsoft with the goal of architecting, developing, validating, and documenting a set of IT infrastructure architectures. These architectures include servers, storage, networking infrastructure, software, and other tools and scripts.

The Internet Data Center architecture aims to provide the knowledge and resources necessary for rapid and reliable deployment of an Internet Data Center, and the following tenets underpin each component of the IDC architecture:

• Availability — Components of the architecture provide redundancy or functional specialization to contain faults. The architecture is designed for 7x24x365 availability.

• Scalability — All components of the architecture support scaling to provide continuous growth to meet user demand and business requirements.

• Utilization — The architecture is optimized to maximize the utilization of the network, server, and storage resources.

• Consolidation — The architecture supports the tenets of logical, physical, and workload consolidation to promote centralized and consistent operational processes.

• Manageability — Ease of configuration, ongoing health monitoring, failure detection, and policy-based management are vital to the goals making the IDC architecture easy to manage.

• Security — The architecture must provide an end-to-end security model that protects data and the infrastructure from malicious attacks or theft.

• Price/Performance — The architecture must deliver the greatest value for the customer environment by maximizing performance and minimizing unnecessary costs.

Businesses are under increasing pressure to provide scalable, reliable, services on the Internet in a secure and controlled manner. To meet these objectives, organizations are building Internet data centers that exist as intermediate networks between the Internet and the corporate environment. We have assembled a team of world-class partners across the technology industry to build, test, validate, and provide a means for customers to deploy the Internet Data Center:

• Avanade — Avanade creates value for its customers by designing, building, and deploying customized, reliable architectures and scalable infrastructures to increase profitability, improve speed-to-market, and accelerate growth.

EXECUTIVE SUMMARY

2 Microsoft Systems Architecture Internet Data Center

• Brocade — Brocade provides a reliable storage network infrastructure for enterprise applications for business continuance, storage consolidation, and reduced backup times – this provides increased ROI through improved storage efficiency.

• Dell — Dell PowerEdge Servers are optimized for the demands of the Internet Data Center. Dell is a leader in price performance and Dell’s direct model offer’s customers the speed and agility required in today’s business environment

• EMC — EMC CLARiiON and Dell|EMC storage provide high availability and scalability to the IDC while protecting your information. EMC AutoIS software enables simple, automated and open management of information for the IDC.

• Emulex — Emulex is the leading supplier of Fibre Channel Host Bus Adapters. These HBAs offload the server from the management of I/O. Emulex HBAs enable better system availability and greater IT productivity, as well as support the scalable data requirements of the Internet Data Center.

• Nortel Networks — Nortel Networks Intelligent Internet portfolios add brains to bandwidth making networks smarter from edge to edge enabling the IDC network to operate with an exceptional level of security, performance, agility, and efficiency.

This Internet Data Center architecture was specifically designed to meet the needs of a high traffic B2B and B2C customers such as e-tailers, on-line banking and on-line exchanges. In addition, through the global load balancing capabilities, this solution is particularly suited for geographical dispersed data centers and sites that support long running and high valued transactions. Specific networking decisions were made to meet the needs of this expanded, demanding customer set.

Many of the processes involved have been automated, particularly those relating to deploying the Microsoft® Windows® 2000 operating system. This automation ensures that each of your servers, in both your test and production environments, is built in a consistent and reproducible manner.

Implementation Task Order Deploying a major e-commerce infrastructure can be a complex and time-consuming process. Fortunately, the Internet Data Center architecture provides a set of tools and documents that makes the process considerably easier. It is still important, however, that the tasks involved are performed in a logical order to ensure that all the dependencies relating to a specific task are addressed before the new task commences.


In summary the task order is:

Step What Where Why How Group/ Category

1 Deploy the network

Nortel Network Equipment

Connectivity require for deployment of all other components

Chapter 2 Network

2 Deploy Enterprise Storage Management Components 1)ESN Manager 2)Navisphere Manager

MSA02, MSA03

These are the minimum components required to perform SAN Zoning and Volume creation for the other servers in the SAN

Chapter 3 Management

3 Configure Enterprise Storage

All CLARiiON attached servers described in Chapter 3

Required for Distribution Share, AD, MS APF Data

Chapter 3 Storage

4 Deploy remote management

All Dell servers

To aid in remaining deployment tasks

Chapter 7 Management

5 Domain Controllers

MSADC1, MSADC2

So all servers can join domain, policy and security deployment

Chapter 4 Infrastructure

6 Deploy remaining Management components

As specified Complete management software deployment

Chapters 3, 6, 9, 10

Management

7 Deploy web servers

MSAWEB01 – MSAWEB33

Create Web Tier Chapter 6 Web

8 Deploy SQL Server

MDSDNODE1, MSADNODE2

For Database applications

Chapter 5 Data

9 Deploy COM+ objects

All Web Servers

Implement Web Applications

Chapter 6 Infrastructure

10 Transition to Production-Level security

Network, Active Directory

Prep for Testing and Production Implementation

Chapter 11

Infrastructure

11 Deploy the Production Network

Nortel Network Equipment

Connectivity/Security implementation into production for all of the components

Chapters 7,8

Network

12

Perform functionality tests

Across Environment

Validate build-out and prepare for Production

Chapter 12

Test

13 Implement Environment into Production

Across Environment

Complete Implementation

N/A N/A

After steps 1-5 have been completed, it may be possible to perform some of the remaining tasks in parallel, with the final security configuration and checks being performed last. However, it is also likely that space and access constraints may not allow this. If this is the case, perform each chapter’s tasks in their numbered order.


Who Should Perform Each Task The chapters in the Internet Data Center Prescriptive Architecture Guide are designed so they can be given separately to the personnel responsible for deploying a particular feature of the infrastructure. As a result, different chapters require different skill sets, which are detailed in the chapter summaries in the following section.


The Prescriptive Architecture Guide consists of the following chapters, each of which describes in detail a particular feature of the Internet Data Center implementation.

Chapter 1, Introduction: This chapter is suitable for all the implementation personnel and should be required reading since it provides an overview of the whole building and deployment process.

Chapter 2, Installing Network Devices: This chapter describes the implementation process for installing networking devices for the Internet Data Center. Included with this chapter are appendixes that provide technical details, such as network diagrams and device configurations. This chapter is designed for a qualified network engineer experienced with the network equipment used within the Internet Data Center environment. Knowledge of Windows 2000 or the programs being used is not necessary, although would be beneficial for troubleshooting.

Chapter 3, Building the Storage Architecture: This chapter describes the process for configuring the prescribed storage architecture of the MSA Internet Data Center to include the recommended EMC Enterprise Storage hardware and software, Connectrix DS-16B2 switches and Dell servers. This includes installing and initializing software, configuring volumes and zoning. This documentation requires an understanding of switched fabrics and zoning.

Chapter 4, Building the Servers: This chapter describes the methods of Microsoft Windows 2000 deployment used in the Internet Data Center architecture and describes in detail the automated, unattended installation process used to ensure rapid deployment of the architecture and to provide consistency between the test and production environments. However, because an automated procedure may not be suitable for every implementation, detailed step-by-step, manual instructions are also provided in Appendix 4.1. Building the Servers. The implementer should be a Microsoft Certified System Engineer (MCSE) or have equivalent knowledge and experience with Windows 2000 and Active Directory. In addition, a strong knowledge of Windows 2000 networking and a basic understanding of the hardware used are required.

Chapter 5, Building the SQL Server 2000 Clusters: This chapter describes setting up Windows clustering with the Windows 2000 operating system and failover clustering with Microsoft SQL Server™. This complex process involves the installation of software components in a strict sequence and also involves detailed hardware and network planning. This chapter requires an understanding of Microsoft clustering technologies and experience in deploying Microsoft SQL Server™. In addition, the documentation requires an understanding of the Storage Area Network (SAN) technologies used in the Internet Data Center environment.

CHAPTER SUMMARIES


Chapter 6, Deploying the Content Management Solution: The base Internet Data Center is designed to allow additional components to be installed as required. The content management solution detailed in this chapter is the first of these additional components. This chapter provides the step-by-step instructions required to successfully deploy a content management infrastructure using Microsoft Application Center 2000 for staging Web and COM+ applications. This chapter requires an understanding of, and experience in, implementing Microsoft Application Center 2000.

Chapter 7, Deploying the Remote Management Infrastructure: This chapter describes the installation and configuration of remote management technologies in the Internet Data Center environment, and focuses in detail on Windows 2000 Terminal Services and Dell Remote Assistant Cards (DRAC). This chapter assumes a basic understanding of Terminal Services. In addition, familiarity with Dell remote assistant hardware would be useful.

Chapter 8, Deploying the Firewalls: This chapter describes the process for installing the various firewalls used for security in the Internet Data Center architecture, and provides details on the implementation of the various firewall configurations used in the architecture. The implementer should have a strong networking background and a high level of Windows 2000 knowledge. The processes described in this chapter require experience with implementing Virtual Private Networking (VPN) solutions by using Nortel Networks Contivity products with particular emphasis on setting IPSec Tunneling.

Chapter 9, Deploying Operations Manager: The ability to monitor and track the status of the Internet Data Center architecture hardware and software is an important area that should be integrated into the base architecture. This chapter details how such a monitoring and alerting infrastructure can be integrated into the Internet Data Center architecture. It covers the complete installation procedure for Microsoft Operations Manager 2000, including initial sizing, agent deployment, agent configuration, and rules customization. The implementer should have experience with Microsoft Operations Manager deployment.

Chapter 10, Deploying NetIQ AppManager: The implementation of NetIQ AppManager is a natural extension to the features provided by the monitoring and alerting infrastructure detailed in Chapter 9. This chapter describes the installation process of NetIQ AppManager, including customizations that were made specifically for the Internet Data Center environment. This chapter requires experience with and knowledge of deploying NetIQ AppManager alongside Microsoft Operations Manager.


Chapter 11, Implementing Security Policy: This chapter describes the implementation of the Internet Data Center security and authentication solutions and explains the various policies and detailed steps required to secure servers in the perimeter network. Details are also given on the steps required to install and configure components used to implement security and authentication in the Internet Data Center architecture. This chapter requires an in-depth understanding of Windows 2000 and security policy deployment. In addition, the implementer should have a good understanding of all the products concerned and be able to call upon the skills of the individual application specialists within the organization.

Chapter 12, Testing your Implementation: This chapter describes the steps that need to be taken to verify that a deployment of a base Internet Data Center is correctly done and performs to the required base specifications. The procedures in this chapter may be modified to accommodate any departures from the base configuration as needed, or a base environment may be built and tests may be performed on it before deviations are made. The processes described in this chapter require experience with implementing and managing a testing environment.


Although the MSA IDC environment can be constructed by using a variety of different hardware and software configurations, it is important to note that the script and build instructions included in the IDC documentation were developed and tested on a specific configuration. This section describes the details of the products used during the development of the MSA IDC environment to show the differences between the build details provided and your own equipment. For a summary table showing the hardware and software recommendations and options for the, refer to Appendix 1.1. For a diagram of the MSA IDC architecture, refer to Appendix 1.2.

Standard Hardware Builds During any large-scale deployment, it is useful to define standard hardware and software builds. A standard build can dramatically reduce the amount of effort required to implement and support your infrastructure by reducing the number of variables that exist. For example, in the MSA IDC environment, you will use boot floppy disks to connect to the server that contains the installation media. If each of the servers is built using the same combination of network cards, these floppy disks do not need to be individually tailored for every server. This reduces the amount of time required to perform the initial installation and reduces the amount of troubleshooting required.

It is unlikely that your implementation of the MSA IDC architecture will use exactly the same type of server for each role within the infrastructure. Each server type has different strengths and is appropriate for different roles. What is expected, however, is that servers of the same role will use an identical hardware build. For example, all the Web servers in the environment use the same server type and an identical hardware configuration. If you use the same hardware in your test network as well as in your production environment, you can rectify any build difficulties before you try your final implementation. This approach also means that you have a bank of production-ready spares in the event you have to invoke disaster recovery measures.

We do not expect your organization to use exactly the same hardware as is listed in this document. You may already have suitable hardware standards in place or have slightly different requirements. However, you should still try to establish a standard build for each server role. The MSA IDC architecture hardware list included allows you to see, at a glance, where the build scripts or configuration might differ from your hardware. Although this list can be used as the basis for an equipment order list, ensure that you have performed suitable volume and performance testing to guarantee that the server’s specifications meet your own requirements for the performance of the overall architecture.

HARDWARE AND SOFTWARE USED TO BUILD THE ENVIRONMENT


The storage infrastructure for the IDC environment is a SAN environment based on Connectrix DS-16B2 (Brocade Silkworm 3800) switches and FC4700 storage enclosures available as either CLARiiON or Dell|EMC branded systems.

EMC CLARiiON FC4700 and Dell|EMC FC4700

The CLARiiON is used for the Enterprise data storage solution.

• The CLARiiON is a full Fibre Channel array that delivers full redundancy, high availability, data integrity, and hot-swappable components.

• With the CLARiiON you can discover, monitor, and report on multiple arrays from your browser with EMC ControlCenter and Navisphere.

Connectrix DS-16B2 (Brocade SilkWorm 3800)

Connectrix DS-16B2 switches are used to connect the servers and data storage.

• The Connectrix DS-16B2 (Brocade SilkWorm 3800) is a 16-port Fibre Channel switch that supports link speeds up to 2 Gb/s.

• Each port automatically negotiates to the highest common speed of all devices connected to the port.

The Connectrix DS-16B2 includes the Brocade Fabric Operating System.

For more information about EMC storage systems and hardware, please visit the EMC Web site at http://www.emc.com.

STORAGE HARDWARE USED

http://www.emc.com/


Your organization may choose to implement a different hardware build depending on the result of your performance testing. If you need assistance sizing a particular server for your application, please visit http://www.dell.com/sizing. The following minimum configurations below are recommended for the environmental considerations tested in the Internet Data Center’s test scenarios.

Dell PowerEdge 1650

The Dell PowerEdge 1650 is used for the following servers in the Internet Data Center architecture:

• Web Servers • Active Directory Controllers • Microsoft Internet Information Services (IIS) Web servers • Domain Name System (DNS), File Transfer Protocol (FTP) and Simple

Mail Transfer Protocol (SMTP) servers

The 1U high, rack-mounting form factor makes these servers ideal for roles where scaling out needs to be an option. The server must meet the following minimum hardware requirements:

• RAM: 2 GB (MB) • Processor: 2x Intel Pentium III 1.13 Ghz • Hard Drive: 3 x 18.2 GB • Controllers: 1 x PowerEdge RAID Controller (not used for Web

servers) • Network Interface Cards (NICS): 2 x Intel Onboard Ethernet ports +

1 Dual Port Intel Ethernet Server NIC • Management: Dell Remote Assistant Card • Host Bus Adapter: EMULEX LP9000DC (not used for Web servers)

Dell PowerEdge 6450

The Dell PowerEdge 6450 is used for the management servers. The server must meet the following minimum hardware requirements:

• RAM: 4 GB • Processor: 1 x Intel Pentium Xeon 700 Mhz • Hard Drive: 3 x 18.2 GB • Controllers: 1 x PowerEdge RAID Controller • Network Interface Cards (NICS): 1 x Intel Onboard Ethernet ports +

2 Dual Port Intel Ethernet Server NIC • Microsoft Operations Manager (MOM) and NetIQ AppManager

management servers • Management: Dell Remote Assistant Card • Host Bus Adapter: EMULEX LP9002L

SERVER HARDWARE USED

http://www.dell.com/sizing


Dell PowerEdge 8450

The Dell PowerEdge 8450 is used in the Internet Data Center environment for the clustered computers running SQL Server. Using Windows 2000 Datacenter Server, this server hardware can be scaled up to take advantage of a maximum of eight processors and 32 GB of RAM. The basic server configuration must meet the following minimum hardware requirements:

• RAM: 4 GB • Processor: 8 x Intel Pentium Xeon 700 MHz • Hard Drive: 3 x 18.2 GB • Controllers: 1 x PowerEdge RAID Controller • NICS: 1 Dual Port Intel Ethernet Server NIC • Management: Dell Remote Assistant Card • Host Bus Adapter: EMULEX LP9002L

For more information about these servers, please visit the Dell Web site at: http://www.dell.com/servers.

The Dell Rack Advisor provides an excellent resource for designing your rack layout and provides information about power requirements, etc. The Dell Rack Advisor is available for download from the Dell Web site at: http://support.dell.com/us/en/filelib/download/index.asp?fileid=r39624

http://www.dell.com/servers

http://support.dell.com/us/en/filelib/download/index.asp?fileid=r39624


The Management Servers, except for MSA04, use EMC CLARiiON storage. The servers use Emulex LP9000 fibre channel adaptors, and present two I/O ports to the storage. Because this is a SAN, the Servers attach to CLARiiON storage via Brocade Fibre Channel Switches.

Each server attached to CLARiiON storage requires the appropriate Emulex LP9000 driver to be installed, as well as the CLARiiON Navisphere Agent. Also, because each server has two I/O ports, CLARiiON Application-Transparent Failover (ATF) is also required.

Note For more information on the MSA IDC Storage Environment, please refer to Chapter 3, “Deploying Enterprise Storage”.

Management Software Placement The management software components were placed on different servers to achieve a combination of performance and alignment of functional similarities. Also, some management software required a dedicated server.

The management servers are named MSA01, MSA02, MSA03 and MSA04. The management software is distributed across these servers as follows:

Server Software

MSA01 • Microsoft MOM (Microsoft Operations Manager)

MSA02 • Dell Management Server

• EMC ESN Manager

• EMC ECC (EMC Control Center)

• Microsoft APF (Automated Purposing Framework)

MSA03 • EMC Navisphere Manager

MSA04

• MOM Database

• NetIQ AppManager & Database

MANAGEMENT SERVER STORAGE AND SOFTWARE PLACEMENT


The Internet Data Center infrastructure also requires the following network hardware components:

• 2x Juniper Networks M5 Routers – These are used as edge routers to connect to the Internet service provider (ISP) in the Internet Data Center environment.

Note If your design requires the separation of the VPN traffic from that of the main site, you will require additional routers.

• 2x Nortel Networks Passport 8600 Switches – These switches sit at the center of the Internet Data Center environment and must provide support for a Virtual Local Area Network (VLAN) infrastructure and Layer-3 routing between VLANs.

• 2x Nortel Networks Alteon Web Switch Modules – These modules are installed within the Passport 8600s and sit at both the center of the Internet Data Center environment, and provide Virtual IP addresses to the Public side of your environment. These devices must support deep packet inspection, content redirection, server health checking, and scale larger than 32 servers per Server Load Balanced clusters.

• 2x Nortel Networks Contivity 4600 VPN Gateways – These VPN gateways sit between the public and private interfaces of your Internet Data Center. The VPN gateways need to provide a secured means of communication to your LDAP server. These gateways also provide Firewall functionality and are able to route between Virtual Local Area Networks (VLANs).

• 2x Nortel Networks Alteon Switched Firewalls - These Firewalls sit between your routers and DMZ, and between your DMZ and Internal Data Center. These firewalls must be stateful and partitioned.

Each of the network components is duplicated to provide resiliency. For more information about the specific configuration, refer to Chapter 2, "Implementing Network Devices," in this guide.

NETWORK HARDWARE USED


Just as a standard hardware build reduces support and implementation issues, having a standard software build ensures that servers are consistent and that builds are repeatable. The sample build scripts provided with the Appendices of this guide can be used for this purpose and will help ensure consistency and repeatability.

Software Used The following software was used to build the base Internet Data Center environment:

• Windows 2000 Server with SP2 • Windows 2000 Advanced Server with SP2 • SQL Server 2000 Enterprise Edition with SP2 • Microsoft Internet Explorer 6.0 In addition to the base architecture, the following software was used to provide the specific extensions required to fulfill the goals of a fully-featured Internet Data Center environment:

• Application Center 2000 for content replication • Microsoft Operations Manager 2000 • NetIQ AppManager v. 4.3 • EMC ControlCenter 5.0 • EMC ESN Manager 2.0 • EMC Navisphere 5.3.0

• Navisphere Manager 5.3.0

• Navisphere Host Agent 5.3.0

• Application-Transparent Failover (ATF) 2.1.6

STANDARD SOFTWARE BUILDS


The chapters in this Prescriptive Architecture Guide are intended to be used with the sample build and configuration scripts included in the various appendixes and the deployment kit. The relevant implementation personnel should read these chapters prior to implementation to develop a deeper understanding of the underlying installation processes.

The chapters in this guide assume that your implementation of the Internet Data Center will be based on the design documented in the Reference Architecture Guide chapters of this documentation series. A network map of the addressing and naming of individual devices is provided in the appendices, in case you have chosen to implement your own Internet Protocol (IP) addressing scheme or naming convention. The additional appendixes provide reference documents, example configuration files, and script files. These appendixes should provide the information necessary to tailor the build scripts or installation instructions to your specific environment. Additional information on these appendixes is provided at the end of the relevant chapter.

Because scripted installations are not suitable for every environment, the manual processes for the tasks performed are also provided. If you perform the processes manually, be careful to follow every step of every build. Also, be aware that manual builds considerably lengthen the deployment time required.

These Prescriptive Architecture Guide chapters do not include such details as assembling hardware, providing power, and connecting network cables. It is assumed that you will be familiar with your organization’s procedures and facilities for providing basic infrastructure. Similarly, you are expected to be aware of and address the issues of server placement and layout that your organization may face.

Note This Prescriptive Architecture Guide uses a set of IP addresses, server names and VLANs that are specific to this Internet Data Center architecture. Of note, the VLAN numbers are not the same as those as those included in the Microsoft Internet Data Center Reference Architecture Guide.

DOCUMENTATION OVERVIEW


This guide is primarily intended for System Implementers, IT professionals, and developers who are responsible for the building and deployment stages of application or infrastructure projects. This includes the following common job descriptions:

• Network engineers • Database administrators • Security consultants • Consultants who need knowledge-transfer tools for enterprise

customers and partners However, other readers involved in implementing an infrastructure project will find that this guide contains relevant and useful information. There are many roles in infrastructure development, and each person involved in the project requires different types and levels of information. For information about the roles involved in a software development project within the Microsoft Solutions Framework Team Model, refer to:

http://www.microsoft.com/business/services/mcsmsf.asp

AUDIENCE


This guide uses the following style conventions and terminology.

Element Meaning

bold font Characters that you type exactly as shown, including commands and switches. User interface elements are also bold.

Italic font Placeholder for variables for which you supply a specific value. For example, Filename.ext could refer to any valid file name for the case in question. New terminology also appears in italic on first use.

Monospace font Code samples.

%SystemRoot% The folder in which Windows 2000 is installed.

Note Alerts you to supplementary information.

Important Alerts you to supplementary information that is essential to the completion of a task.

STYLE CONVENTIONS


This section provides information about the appendix file that is provided for this chapter as part of the Internet Data Center documentation.

Appendix 1.1 – Software and Hardware Requirements This appendix is an Excel spreadsheet that provides a detailed breakdown of the software and hardware components that were used in the implementation of the Microsoft Internet Data Center architecture. These components are grouped to display which elements are required as part of the base architecture and which are optional components that can be employed to extend the base functionality. The appendix file is N- Hardware and Software requirements.xls.

Appendix 1.2 – Architecture Diagram This appendix is a diagram of the IDC architecture. The appendix file is Appendix_1.2_DC_Architecture.

APPENDIXES

chapter 1 introduction - dell · prescriptive architecture guide, chapter 1, introduction 1 the msa...

Documents