CCNP_BCMSN_Quick_Reference_Sheets_(Cisco-2007).pdf

The Evolving Network Model

VLAN Implementation

Spanning Tree

InterVLAN Routing

Layer 3 Redundancy

CCNP BCMSN

Quick Reference Sheets

Exam 642-812

Using Wireless LANs

VoIP in a Campus Network

Campus Network Security

Brent Stewart

Denise Donohue

ciscopress.com

[ 2 ]

ABOUT THE AUTHORS

CCNP BCMSN Quick Reference Sheets

About the Authors

Brent Stewart, CCNP, CCDP, MCSE, Certified Cisco Systems Instructor, is a network administrator

for CommScope. He participated in the development of BSCI, and has seperately developed training

material for ICND, BSCI, BCMSN, BCRAN, and CIT. Brent lives in Hickory, NC, with his wife,

Karen, and children, Benjamin, Kaitlyn, Madelyn, and William.

Denise Donohue, CCIE No. 9566, is a Design Engineer with AT&T. She is responsible for designing

and implementing data and VoIP networks for SBC and AT&T customers. Prior to that, she was a

Cisco instructor and course director for Global Knowledge. Her CCIE is in Routing and Switching.

[ 3 ]

ICONS USED IN THIS BOOK

CCNP BCMSN Quick Reference Sheets

Icons Used in This Book

Router

7507

Router

Multilayer Switch

with Text

Multilayer

Switch

Communication

Server

Switch

IDC

Internal Firewall

IDS

Web

Browser

Database

App Server

[ 4 ]

CHAPTER 1

CCNP BCMSN Quick Reference Sheets

The Evolving

Network Model

FIGURE 1-1 THE HIERARCHICAL DESIGN MODEL

Cisco has developed specific architecture recommendations for Campus,

Data Center, WAN, branches, and telecommuting. These recommendations

add specific ideas about how current technologies and capabilities match

the network roles within an enterprise.

Core

Distribution

Each of these designs builds on a traditional hierarchical design and

adds features such as security, Quality of Service (QoS), caching,

and convergence.

Access

The Hierarchical

Design Model

Cisco has used the three level Hierarchical Design Model for years.

This older model provided a high-level idea of how a reliable network

might be conceived, but it was largely conceptual because it did not

provide specific guidance. Figure 1-1 is a simple drawing of how the

three-layer model might have been built out. A distribution layer-3

switch would be used for each building on campus, tying together the

access-switches on the floors. The core switches would links the

various buildings together.

The hierarchical design model divides a network into three layers:

n Access—End stations attach to VLANs.

— Clients attach to switch ports.

— VLAN assigned/broadcast domains established.

— Built using low-cost ports.

n Distribution—Intermediate devices route and apply policies.

— VLANs terminated, routing between.

— Policies applied, such as route selection.

— Access-lists.

— Quality of Service (QoS).

[ 5 ]

CHAPTER 1

CCNP BCMSN Quick Reference Sheets

THE EVOLVING NETWORK MODEL

n Core—The backbone that provides a high-speed path between

distribution elements.

Enterprise Composite

Network Model

The newer Cisco model—the Enterprise Composite Model—is signifi-

cantly more complex and attempts to address the major shortcoming of

the Hierarchical Design Model by expanding the older version and

making specific recommendations about how and where certain

network functions should be implemented. This model is based on the

principles described in the Cisco Architecture for Voice, Video, and

Integrated Data (AVVID).

— Distribution devices are interconnected.

— High speed (there is a lot of traffic).

— No policies (it is tough enough to keep up).

Later versions of this model include redundant distribution and core

devices, and connections that make the model more fault-tolerant. A set

of distribution devices and their accompanying access layer switches

are called a switch block.

The Enterprise Composite Model is broken up into three large sections:

Problems with the

Hierarchical Design Model

This early model was a good starting point, but it failed to address key

issues, such as:

n Enterprise Campus—The portion of the design that is like the old

hiearchical model.

n Enterprise Edge—The connections to the public network.

n Service Provider Edge—The different public networks that are

attached.

n Where do wireless devices fit in?

The first section, the Enterprise Campus, looks like the old Hierarchical

model with some added details. The Enterprise Campus is shown in

Figure 1-2. It features six sections:

n How should Internet access and security be provisioned?

n How to account for remote-access, such as dial-up or virtual

private network (VPN)?

n Campus Backbone—The center of the network, like the old “core”.

n Where should workgroup and enterprise services be located?

n Building Distribution—Intermediate devices that route from the

core to access devices.

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: