Cisco IP Routing (ROUTE) Foundation Learning Guide

需积分: 9 171 浏览量更新于2024-07-27 收藏 10.17MB PDF 举报

"这是一份关于CCNP（思科认证网络专业人员）路由学习的英文资料，包含 Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide，主要针对642-902考试的基础学习内容。该书籍由Diane Teare编写，由Cisco Press出版，首次印刷于2010年6月。" 此资源是CCNP学习者的重要参考资料，特别是对初学者来说。CCNP是Cisco认证体系中的一个重要级别，专注于网络路由与交换技术，是专业人士提升网络技能的常见选择。"ROUTE"课程是CCNP认证中的核心部分，主要涉及实施IP路由的理论和实践知识。该书籍涵盖了以下关键知识点： 1. **IP路由基础**：书中可能介绍了IP路由的基本原理，包括路由选择协议如RIP（路由信息协议）、OSPF（开放最短路径优先）和BGP（边界网关协议）的工作机制。 2. **路由表管理**：可能包括如何配置和管理路由器，以及如何理解和解析路由表，以确保网络中的数据包正确转发。 3. **网络地址转换（NAT）**：可能会讲解如何使用NAT技术来解决IP地址空间的问题，以及配置和优化NAT的各种方法。 4. **网络故障排查**：书里可能涉及了诊断和修复网络问题的技巧，包括使用命令行接口（CLI）进行故障排除。 5. **IPv4和IPv6**：可能会涵盖两种版本的IP协议，包括地址规划、子网划分以及向IPv6过渡的策略。 6. **高级路由特性**：如多协议标签交换（MPLS）、策略路由、虚拟专用网络（VPNs）和QoS（服务质量）可能会有深入讨论。 7. **实验和案例研究**：通过实际操作和案例分析，帮助读者巩固理论知识并提升实践能力。 8. **考试准备**：作为针对642-902考试的学习指南，书里可能包含了考试复习策略，练习题和模拟试题，帮助考生熟悉考试格式和内容。阅读这本书，读者可以系统地学习和理解网络路由技术，为CCNP的ROUTE考试做好充分准备。同时，由于是Cisco官方出版，其内容权威且符合最新的技术标准。然而，需要注意的是，尽管这本书提供了详尽的信息，但读者仍需结合实践操作和持续学习，以全面掌握网络路由技术。

The Enterprise Campus functional area comprises the following modules:

• Building— Contains access switches and end-user devices (including PCs and IP phones).

• Building Distribution— Includes distribution multilayer switches to provide access between

workgroups and to the Core.

• Core— Also called the backbone, provides a high-speed connection between buildings themselves,

and between buildings and the Server Farm and Edge Distribution modules.

• Edge Distribution— The interface between the Enterprise Campus and the Enterprise Edge

functional areas. This module concentrates connectivity to and from all branches and teleworkers

accessing the campus via a WAN or the Internet.

• Server Farm— Represents the campus’s data center.

• Management— Represents the network management functionality, including monitoring, logging,

security, and other management features within an enterprise.

Figure 1-8 illustrates how the Building, Building Distribution, and Core modules map directly onto the

hierarchical model’s access, distribution, and core layers. The figure also shows how multiple buildings can be

represented by multiple sets of a Building and a Building Distribution module, with each connected to the

Core.

Figure 1-8. Multiple Buildings Represented Within the Enterprise Campus.

[View full size image]

During the network design, an implementation plan is created, as detailed in the next section.

Creating, Documenting, and Executing an Implementation Plan

An effective, documented, implementation plan is a result of good processes and procedures during network

design, deployment, and performance testing. This section describes approaches to creating an

implementation plan and its associated documentation.

Approaches to Creating an Implementation Plan

There are two approaches to implementing changes to a network: using an ad hoc approach or using a

structured approach.

In an ad hoc approach, the network engineer identifies the need for a change, such as a routing protocol

implementation, and implements the solution without planning any of the tasks. The many tasks such as

connectivity, addressing, routing, and security are implemented and configured as required. New equipment

may be added, and new offices may be deployed. With such an approach, it is more likely that scalability

issues, suboptimal routing, and security issues can occur. A good implementation plan is required to avoid

such difficulties.

In a structured approach, the network engineer identifies the need for a network upgrade (for example, a

new routing protocol implementation) and starts with planning as the first step. Based on the existing

topology, all potential changes are reviewed, and many considerations are taken into account. The design

and implementation plan are completed, and may include a new topology, an IP addressing plan, a solution

to scalability issues, a link utilization upgrade, remote network connectivity, and changes to other network

parameters. The design and implementation plan must meet both technical and business requirements. All

details are documented in the implementation plan before the implementation. After the successful

implementation, the documentation is updated to include the tools and resources used, and the

implementation results.

Many models and methodologies used in IT define a lifecycle approach using various processes to help

provide high-quality IT services. Network implementation, including an implementation plan, is just one part

of these models. The following are some examples of these models:

• The Cisco Lifecycle Services approach defines the minimum set of activities needed to help

customers successfully deploy and operate Cisco technologies and optimize their performance

throughout the lifecycle of the network. The Cisco Lifecycle Services approach defines six phases in

the network lifecycle and is referred to as the Prepare, Plan, Design, Implement, Operate, and

Optimize (PPDIOO) model. The implementation plan is part of the Design phase; implementation is of

course part of the Implement phase.

• IT Infrastructure Library (ITIL) is a framework of best practices for IT service management,

providing high-quality IT services that are aligned with business requirements and processes. The

implementation plan and implementation are part of ITIL best practices.

• The Fault, Configuration, Accounting, Performance, and Security (FCAPS) model is defined

by the International Organization for Standardization (ISO) and defines the minimum set of

categories needed for successful network management. Five different categories are defined: Fault

Management, Configuration Management, Accounting Management, Performance Management, and

Security Management. The implementation plan and implementation are part of the Configuration

Management category.

• The Telecommunications Management Network (TMN) model is similar to the FCAPS model

and defines a framework for the management of telecommunication networks. The

Telecommunications Standardization Sector (ITU-T) took the main aspects of the FCAPS Model and

refined it to create the TMN framework. The implementation plan and implementation are one of the

building blocks within the framework.

Each organization has unique requirements. The model and its elements chosen should fit the organization,

and its business and technical requirements. Different models may be combined and adapted for an optimal

fit. For example, the service components, processes, and procedures needed to create an implementation

plan successfully can be chosen to help ensure a successful implementation.

After the model has been selected, the cost-effective tools that support the model are chosen to allow a

successful deployment of Cisco technologies with optimized performance.

After the requirements, models, and tools have been defined and collected, the implementation plan can be

created.

Note

The Cisco Lifecycle Services (PPDIOO) approach is used in examples throughout this book.

Creating an Implementation Plan

As detailed in the Cisco Press book Authorized Self-Study Guide: Designing for Cisco Internetwork Solutions

(DESGN), Second Edition, the design methodology recommended for use with the PPDIOO model includes

three basic steps:

Step 1. Identify customer requirements: In this step, which is typically completed during the PPDIOO

Prepare phase, key decision makers identify the initial business and technical requirements. Based

on these requirements, a high-level conceptual architecture is proposed.

Step 2. Characterize the existing network and sites: The Plan phase involves characterizing sites and

assessing any existing networks, and performing a gap analysis to determine whether the existing

system infrastructure, sites, and operational environment can support the proposed system.

Characterization of the existing network and sites includes site and network audit and network

analysis. During the network audit, the existing network is thoroughly checked for integrity and

quality. During the network analysis, network behavior (traffic, congestion, and so forth) is

analyzed.

Step 3. Design the network topology and solutions: In this step, the detailed design of the network is

created. Decisions are made about networked infrastructure, infrastructure services, and

applications. The data for making these decisions is gathered during the first two steps.

A pilot or prototype network might be constructed to verify the correctness of the design and to

identify and correct any problems as a proof of concept before implementing the entire network.

A detailed design document is also written during this step; it includes information that has been

documented in the previous steps.

When the design is complete, the design implementation process is executed; this process includes the

following steps:

Step 1. Plan the implementation: During this step, the implementation plan is prepared in advance to

expedite and clarify the actual implementation. Cost assessment is also undertaken at this time.

This step is performed during the PPDIOO Design phase.

Step 2. Implement and verify the design: The actual implementation and verification of the design take

place during this step by building the network. This step maps directly to the Implement phase of

the PPDIOO methodology.

Step 3. Monitor and optionally redesign: The network is put into operation after it is built. During

operation, the network is constantly monitored and checked for errors. If troubleshooting problems

become too frequent or even impossible to manage, a network redesign might be required; this can

be avoided if all previous steps have been completed properly. This step is a part of the Operate

and Optimize phases of the PPDIOO methodology.

Thus, the process of creating the implementation plan is part of the Design phase. Before developing the

implementation plan, you must identify all the following information:

• Network specific information, and the activities and tasks associated with developing the

implementation plan— The network information includes the existing topology, equipment, and

software versions; the IP addressing plan; scalability requirements (summarization, stub areas, and

so on); the list of advertised networks; the link utilization; and the metric requirements for primary

and backup links. Other requirements to consider include site-specific implementation requirements,

the tools required, and specific commands (for configuration and verification) that should be used.

• The dependencies that your implementation plan development has on other service

components and the existing network—Implementation risks should be identified and a plan to

manage them established.

• The recommended resources to accomplish the activities and tasks associated with the

implementation plan development— The implementation schedule and the roles and

responsibilities of the resources should also be established.

Based on the information gathered, the network engineer determines the implementation tasks required. For

example, topology design, IP addressing, or any other changes might be required to the existing network.

After the implementation plan is developed, the solution is implemented and verified, and the documentation

is updated.

The following steps are completed during creation and execution of an implementation plan:

• Planning the implementation

• Selecting the tools and resources required

• Coordinating work with specialists

• Verifying the implementation

• Interpreting performance results

• Documenting the baseline, performance, and recommendations

The tasks in a site-specific implementation plan may include the following:

• Identifying applications and devices to be implemented

• Creating installation tasks and checklists

• Defining device configuration and software requirements

• Creating site-specific device configurations, installation tasks, and checklists

• Creating installation verification tests

Implementation Plan Documentation

The implementation plan documentation must be correct and up-to-date, because it is needed during both

implementation and verification. After implementation, all verification steps and results should be added to

the documentation so that it will be useful for troubleshooting, and for planning future upgrades and changes

to the network.

The documentation must also be accessible (for example, to troubleshooting engineers). The documentation

should contain all the current information about the equipment and configuration, and should include known

issues, the baseline status, and the details and results of the verification tasks.

剩余764页未读，继续阅读

sushi8750

粉丝: 2
资源: 4

Cisco IP Routing (ROUTE) Foundation Learning Guide

ccnp 考试指南 CCNP_Tshoot_642-832 CCNP_ROUTE_642-902

CCNP ROUTE 642-902 Official Certification Guide.pdf

CCNP+ROUTE+642-902学习指南 原版

CCNP ROUTE 642-902官方指南（EN）

EIGRP ccnp route

免费获取CCNP-640-504学习软件及考试用书

Cisco CCNP Route 642-902官方认证指南

CCNP RS v2.0 路由 ROUTE 300-101 官方认证指南 英文版

[2011新版英文]CCNP认证指南-全套

2010年新版CCNP中文教材(ROUTE+SWITCH+TSHOOT)

最新资源

CCNP+ROUTE+642-902学习指南原版

CCNP RS v2.0 路由 ROUTE 300-101 官方认证指南英文版