Cisco IP Routing学习指南：基础篇

需积分: 15 192 浏览量更新于2024-07-17 收藏 10.89MB PDF 举报

"Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide.pdf" 是一本关于准备Cisco 642-902考试的基础路由学习指南，由Diane Teare编写，由Cisco Press出版。这本书旨在为Cisco路由提供基础学习，涵盖了实施Cisco IP路由的相关知识。在描述中，提到了命令语法的约定，这些约定同样应用于IOS命令参考中： 1. **粗体**：表示需要按所示方式直接输入的命令和关键字。在实际配置示例和输出（而非一般命令语法）中，粗体表示用户手动输入的命令，如`show`命令。 2. **斜体**：表示需要你提供实际值的参数。 3. **竖线 (|)**：用于分隔互斥的替代元素。 4. **方括号 ([ ])**：表示可选元素。 5. **大括号 ({ })**：表示必需的选择。 6. **方括号内的大括号 ([{ }])**：表示在一个可选元素中必需做出的选择。这本书的主要内容可能包括但不限于以下方面： - 路由基本概念：介绍网络中的路由是什么，以及它是如何在不同网络之间传递数据包的。 - Cisco IOS基础：讲解Cisco Internetwork Operating System (IOS)的工作原理、命令行界面(CLI)的使用，以及如何通过CLI配置路由器。 - 路由协议：涵盖静态路由、RIP、OSPF、EIGRP等动态路由协议的原理和配置。 - 路由选择过程：解释如何根据路由表选择最佳路径。 - 邻居发现和邻居状态：涉及路由器如何发现和验证其邻接路由器。 - 路由汇总与CIDR：讨论如何减少路由表的大小，提高网络效率。 - 访问控制列表(ACLs)：如何使用ACL来过滤和控制网络流量。 - 路由策略和过滤：如何利用策略来控制路由信息的传播和接收。 - 路由重分布：当多个路由协议在同一个网络中运行时，如何将路由信息从一个协议重分布到另一个。 - 路由故障排查：如何识别和解决路由问题，以及使用`show`和`debug`命令进行诊断。 - 实战案例：可能包含配置示例和实践场景，帮助读者理解和应用所学知识。尽管书中警告和免责声明指出，虽然已尽力确保信息的完整性和准确性，但不保证适于特定用途，且不承担任何由于使用此书中的信息而产生的损失或损害的责任。这提醒读者在实际操作时应谨慎并结合其他资源进行学习。

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页未读，继续阅读

drjiachen

粉丝: 171
资源: 2139

Cisco IP Routing学习指南：基础篇

CCIE Routing and Switching Official Exam Certi（第二版）.pdf

Implementing Cisco IP Routing (ROUTE) Foundation Learning Guide

CCNP包括什么考试内容

NotImplementedError: PdfMerger.merge requires an object that PdfReader can parse. Typically, that is a Path or a string representing a Path, a file object, or an object implementing .seek and .read. Passing a PdfReader directly works as well.

Cannot define multiple Listeners on the same IP:port

给出自主机器学习的参考文献

what is the code of deep learning momentum

pytorch maml

最新资源