Click to Rate and Give Feedback
TechNet
TechNet Library
 The Deployment Architecture
The Deployment Architecture
Cc539133.chm_head_left(en-us,TechNet.10).gif Cc539133.chm_head_middle(en-us,TechNet.10).gif Cc539133.chm_head_right(en-us,TechNet.10).gif
The Deployment Architecture

The following figure describes the deployment architecture. In this deployment walkthrough you will deploy each of the servers shown below into a lab environment.

Cc539133.CMSU_Graphics_DW_Config_Full_w_Servers(en-us,TechNet.10).gif

Figure: Deployment architecture

Deployment Network Architecture

The solution architecture calls for a three-tiered, four-zone network architecture, in which each zone consists of servers in a single subnet or a virtual local area network (VLAN) spanned across multiple subnets. However, given that lab networks vary widely, as do production networks, the deployment walkthrough will only loosely represent this model. There are no requirements in this walkthrough for routers or other network hardware or for separate subnets. Instead, the suggestion is to assign each server an IP address in a Class A network (Subnet Mask 255.0.0.0) in which the third octet reflects the zone. For example, a server in zone 3 may have an IP address of 10.0.3.5 whereas a server in zone 2 will have an IP address of 10.0.2.5. The following table describes a sample Deployment Walkthrough IP addressing scheme.

Table: Deployment Walkthrough IP Addressing Scheme

ZoneSubnet maskIP range
1255.0.0.010.0.1.x
2255.0.0.010.0.2.x
3255.0.0.010.0.3.x
4255.0.0.010.0.4.x

In this model each server is deployed with a single Public Network Interface card, with the exception of the clustered servers which still require a Private Interface for heartbeat traffic.

© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker