思科数据中心设计详解：加快部署的验证方案

需积分: 9 140 浏览量更新于2024-07-18 收藏 3.87MB PDF 举报

思科数据中心设计教程是一份详尽的指南，由Cisco Systems, Inc.编撰，专注于帮助用户理解和实施高效的数据中心架构设计。该教程发布于2008年5月，作为Cisco Validated Design的一部分，旨在通过系统化、测试过的解决方案，简化和加速客户部署过程。Cisco Validated Design是一个官方认可的程序，其设计、规格、陈述和建议均未经修改，以原始形式提供（"AS IS"），并明确表示可能存在的所有缺点和限制。在本教程中，读者可以了解到以下关键知识点： 1. **设计目标**：教程涵盖了如何创建一个可靠且可预测的数据中心基础设施，这包括性能优化、高可用性和能源效率等方面的设计原则。 2. **验证流程**：Cisco Validated Design强调了设计过程中严格的测试和验证步骤，确保解决方案不仅符合标准，而且在实际应用中表现出优良的性能和稳定性。 3. **技术覆盖**：内容涵盖了Cisco Data Center Infrastructure 2.5的相关技术和组件，如网络架构、存储、服务器、虚拟化技术、安全措施以及电源和冷却系统等。 4. **责任声明**：所有设计信息仅供参考，不承担任何法律责任，包括但不限于产品适合特定用途、无侵犯知识产权的保证。此外，教程明确指出，用户需自行承担与使用相关的设计可能导致的间接、特殊或附带损失，如数据丢失或利润损失。 5. **获取更多信息**：对于想要了解更多关于Cisco Validated Design的详细信息和最新进展，用户被鼓励访问Cisco官方网站（<http://www.cisco.com>）。 6. **联系信息**：提供了Cisco Americas Headquarters的地址、电话和传真号码，以便用户在需要时与公司取得联系。这份教程是为数据中心设计者、运维人员和系统集成商量身打造的实用资源，通过学习，读者可以掌握思科推荐的最佳实践，并在实际项目中实现高效、稳定的数据中心环境构建。

1-10

Cisco Data Center Infrastructure 2.5 Design Guide

OL-11565-01

Chapter 1 Data Center Architecture Overview

Data Center Design Models

Figure 1-6 takes the logical cluster view and places it in a physical topology that focuses on addressing

the preceding items.

Figure 1-6 Physical View of a Server Cluster Model Using ECMP

The recommended server cluster design leverages the following technical aspects or features:

• Equal cost multi-path—ECMP support for IP permits a highly effective load distribution of traffic

across multiple uplinks between servers across the access layer. Although

Figure 1-6 demonstrates

a four-way ECMP design, this can scale to eight-way by adding additional paths.

• Distributed forwarding—By using distributed forwarding cards on interface modules, the design

takes advantage of improved switching performance and lower latency.

• L3 plus L4 hashing algorithms—Distributed Cisco Express Forwarding-based load balancing

permits ECMP hashing algorithms based on Layer 3 IP source-destination plus Layer 4

source-destination port, allowing a highly granular level of load distribution.

• Scalable server density—The ability to add access layer switches in a modular fashion permits a

cluster to start out small and easily increase as required.

• Scalable fabric bandwidth—ECMP permits additional links to be added between the core and access

layer as required, providing a flexible method of adjusting oversubscription and bandwidth per

server.

In the preceding design, master nodes are distributed across multiple access layer switches to provide

redundancy as well as to distribute load.

Further details on multiple server cluster topologies, hardware recommendations, and oversubscription

calculations are covered in

Chapter 3, “Server Cluster Designs with Ethernet.”

143344

-way

CMP

ore

ccess

Front End

Back End High Speed Fabric

Master

Nodes

Computer Nodes

2-3

Cisco Data Center Infrastructure 2.5 Design Guide

OL-11565-01

Chapter 2 Data Center Multi-Tier Model Design

Data Center Core Layer

The data center core layer provides a fabric for high-speed packet switching between multiple

aggregation modules. This layer serves as the gateway to the campus core where other modules connect,

including, for example, the extranet, WAN, and Internet edge. All links connecting the data center core

are terminated at Layer 3 and typically use 10 GigE interfaces for supporting a high level of throughput,

performance, and to meet oversubscription levels.

The data center core is distinct from the campus core layer, with a different purpose and responsibilities.

A data center core is not necessarily required, but is recommended when multiple aggregation modules

are used for scalability. Even when a small number of aggregation modules are used, it might be

appropriate to use the campus core for connecting the data center fabric.

When determining whether to implement a data center core, consider the following:

• Administrative domains and policies—Separate cores help isolate campus distribution layers and

data center aggregation layers in terms of administration and policies, such as QoS, access lists,

troubleshooting, and maintenance.

• 10 GigE port density—A single pair of core switches might not support the number of 10 GigE ports

required to connect the campus distribution layer as well as the data center aggregation layer

switches.

• Future anticipation—The business impact of implementing a separate data center core layer at a later

date might make it worthwhile to implement it during the initial implementation stage.

Recommended Platform and Modules

In a large data center, a single pair of data center core switches typically interconnect multiple

aggregation modules using 10 GigE Layer 3 interfaces.

The recommended platform for the enterprise data center core layer is the Cisco Catalyst 6509 with the

Sup720 processor module. The high switching rate, large switch fabric, and 10 GigE density make the

Catalyst 6509 ideal for this layer. Providing a large number of 10 GigE ports is required to support

multiple aggregation modules. The Catalyst 6509 can support 10 GigE modules in all positions because

each slot supports dual channels to the switch fabric (the Catalyst 6513 cannot support this). We do not

recommend using non-fabric-attached (classic) modules in the core layer.

Note By using all fabric-attached CEF720 modules, the global switching mode is compact, which allows the

system to operate at its highest performance level.

The data center core is interconnected with both the campus core and aggregation layer in a redundant

fashion with Layer 3 10 GigE links. This provides for a fully redundant architecture and eliminates a

single core node from being a single point of failure. This also permits the core nodes to be deployed

with only a single supervisor module.

2-4

Cisco Data Center Infrastructure 2.5 Design Guide

OL-11565-01

Chapter 2 Data Center Multi-Tier Model Design

Data Center Core Layer

Distributed Forwarding

The Cisco 6700 Series line cards support an optional daughter card module called a Distributed

Forwarding Card (DFC). The DFC permits local routing decisions to occur on each line card via a local

Forwarding Information Base (FIB). The FIB table on the Sup720 policy feature card (PFC) maintains

synchronization with each DFC FIB table on the line cards to ensure accurate routing integrity across

the system. Without a DFC card, a compact header lookup must be sent to the PFC on the Sup720 to

determine where on the switch fabric to forward each packet to reach its destination. This occurs for both

Layer 2 and Layer 3 switched packets. When a DFC is present, the line card can switch a packet directly

across the switch fabric to the destination line card without consulting the Sup720 FIB table on the PFC.

The difference in performance can range from 30 Mpps system-wide to 48 Mpps per slot with DFCs.

With or without DFCs, the available system bandwidth is the same as determined by the Sup720 switch

fabric.

Table 2-1 summarizes the throughput and bandwidth performance for modules that support DFCs

and the older CEF256, in addition to classic bus modules for comparison.

Using DFCs in the core layer of the multi-tier model is optional. An analysis of application session flows

that can transit the core helps to determine the maximum bandwidth requirements and whether DFCs would

be beneficial. If multiple aggregation modules are used, there is a good chance that a large number of session

flows will propagate between server tiers. Generally speaking, the core layer benefits with lower latency and

higher overall forwarding rates when including DFCs on the line cards.

Traffic Flow in the Data Center Core

The core layer connects to the campus and aggregation layers using Layer 3-terminated 10 GigE links.

Layer 3 links are required to achieve bandwidth scalability, quick convergence, and to avoid path

blocking or the risk of uncontrollable broadcast issues related to extending Layer 2 domains.

The traffic flow in the core consists primarily of sessions traveling between the campus core and the

aggregation modules. The core aggregates the aggregation module traffic flows onto optimal paths to the

campus core, as shown in

Figure 2-2. Server-to-server traffic typically remains within an aggregation

module, but backup and replication traffic can travel between aggregation modules by way of the core.

Ta b l e 2-1 Performance Comparison with Distributed Forwarding

System Config with Sup720 Throughput in Mpps Bandwidth in Gbps

CEF720 Series Modules

(6748, 6704, 6724)

Up to 30 Mpps per system 2 x 20 Gbps (dedicated per slot)

(6724=1 x 20 Gbps)

CEF720 Series Modules with

DFC3

(6704 with DFC3, 6708 with

DFC3, 6724 with DFC3)

Sustain up to 48 Mpps (per slot) 2x 20 Gbps (dedicated per slot)

(6724=1 x 20 Gbps)

CEF256 Series Modules

(FWSM, SSLSM, NAM-2,

IDSM-2, 6516)

Up to 30 Mpps (per system) 1x 8 Gbps (dedicated per slot)

Classic Series Modules

(CSM, 61xx-64xx)

Up to 15 Mpps (per system) 16 Gbps shared bus (classic bus)

剩余179页未读，继续阅读

msf5211314

粉丝: 0
资源: 3

思科数据中心设计详解：加快部署的验证方案

Cisco数据中心实验手册图文并茂版非常详细

05数据中心网络与设计.pptx

Cisco数据中心基础教程

思科数据中心讲座：Nexus1000V入门与虚拟交换技术详解

Cisco网络设计基础教程（DESGN 640-864）第三版学习指南

深入解析思科Nexus 7000：数据中心核心交换机

深入理解思科Nexus 7000：数据中心核心交换机

思科视频教程

cisco cs-mars 教程

Cisco官方新版CCNP教程

最新资源