Breakthrough, iQ Expertise, iQ FastTrack, the iQ logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath,
Trang 1Text Part Number: Review Copy
Click Here to Post Review Comments
Trang 2The products and specifications, configurations, and other technical information regarding the products
in this manual are subject to change without notice All statements, technical information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied You must take full responsibility for their application of any products specified in this manual
LICENSE PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THE MANUAL, DOCUMENTATION, AND/OR SOFTWARE (“MATERIALS”) BY USING THE MATERIALS YOU AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS LICENSE IF YOU DO NOT AGREE WITH THE TERMS OF THIS LICENSE, PROMPTLY RETURN THE UNUSED
MATERIALS (WITH PROOF OF PAYMENT) TO THE PLACE OF PURCHASE FOR A FULL REFUND
Cisco Systems, Inc (“Cisco”) and its suppliers grant to you (“You”) a nonexclusive and nontransferable license to use the Cisco Materials solely for Your own personal use If the Materials include Cisco software (“Software”), Cisco grants to You a nonexclusive and nontransferable license to use the Software in object code form solely on a single central processing unit owned or leased by You or otherwise embedded in equipment provided by Cisco You may make one (1) archival copy of the Software provided You affix to such copy all copyright, confidentiality, and proprietary notices that appear on the original EXCEPT AS EXPRESSLY AUTHORIZED ABOVE, YOU SHALL NOT: COPY, IN WHOLE OR IN PART, MATERIALS; MODIFY THE SOFTWARE; REVERSE COMPILE
OR REVERSE ASSEMBLE ALL OR ANY PORTION OF THE SOFTWARE; OR RENT, LEASE, DISTRIBUTE, SELL, OR CREATE DERIVATIVE WORKS OF THE MATERIALS
You agree that aspects of the licensed Materials, including the specific design and structure of individual programs, constitute trade secrets and/or copyrighted material of Cisco You agree not to disclose, provide, or otherwise make available such trade secrets or copyrighted material in any form to any third party without the prior written consent of Cisco You agree to implement reasonable security measures to protect such trade secrets and copyrighted Material Title to the Materials shall remain solely with Cisco
This License is effective until terminated You may terminate this License at any time by destroying all copies of the Materials This License will terminate immediately without notice from Cisco if You fail
to comply with any provision of this License Upon termination, You must destroy all copies of the Materials
Software, including technical data, is subject to U.S export control laws, including the U.S Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries You agree to comply strictly with all such regulations and acknowledge that it has the responsibility to obtain licenses to export, re-export, or import Software
This License shall be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law If any portion hereof is found to be void or unenforceable, the remainin g provisions of this License shall remain in full force and effect This License constitutes the entire License between the parties with respect to the use of the Materials
Restricted Rights - Cisco’s software is provided to non-DOD agencies with RESTRICTED RIGHTS and its supporting documentation is provided with LIMITED RIGHTS Use, duplication, or disclosure by the U.S Government is subject to the restrictions as set forth in subparagraph “C” of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19 In the event the sale is to a DOD agency, the U.S Government’s rights in software, supporting documentation, and technical data are governed by the restrictions in the Technical Data Commercial Items clause at DFARS 252.227-7015 and DFARS 227.7202
DISCLAIMER OF WARRANTY ALL MATERIALS ARE PROVIDED “AS IS” WITH ALL FAULTS CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST
Trang 3cause harmful interference to radio communications Operation of this equipment in a residential area is likely t o cause harmful interference, in which case users will be required to correct the interference at their own expense
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio -frequency energy If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules These specifications are designed to provide reasonable protection against such interference in a residential installation However, there is no guarantee that interference will not occur in a particular installation
You can determine whether your equipment is causing interference by turning it off If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
• Turn the television or radio antenna until the interference stops
• Move the equipment to one side or the other of the television or radio
• Move the equipment farther away from the television or radio
• Plug the equipment into an outlet that is on a different circuit from the television or radio (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc could void the FCC approval and negate your authority to operate the product
The following third-party software may be included with your product and will be subject to the software license agreement:
CiscoWorks software and documentation are based in part on HP OpenView under license from the Hewlett-Packard Company HP OpenView is a trademark of the Hewlett-Packard Company Copyright
© 1992, 1993 Hewlett-Packard Company
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system All rights reserved Co pyright © 1981, Regents of the University of California Network Time Protocol (NTP) Copyright © 1992, David L Mills The University of Delaware makes
no representations about the suitability of this software for any purpose
Point-to-Point Protocol Co pyright © 1989, Carnegie-Mellon University All rights reserved The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission
The Cisco implementation of TN3270 is an adaptation of the TN3270, curses, and termcap programs developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system All rights reserved Copyright © 1981-1988, Regents of the University of California
Cisco incorporates Fastmac and TrueView software and the RingRunner chip in some Token Ring products Fastmac software is licensed to Cisco by Madge Networks Limited, and the RingRunner chip is licensed to Cisco by Madge NV Fastmac, RingRunner, and TrueView are trademarks and in some jurisdictions registered trademarks of Madge Networks Limited Copyright © 1995, Madge Networks Limited All rights reserved
XRemote is a trademark of Network Computing Devices, Inc Copyright © 1989, Network Computing Devices, Inc., Mountain View, California NCD makes no representations about the suitability of this software for any purpose
The X Window System is a trademark of the X Consortium, Cambridge, Massachusetts All rights reserved
Cisco Systems has more than 200 offices in the following countries and regions Addresses, phone numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices
Argentina Australia Austria Belgium Brazil Bulgaria Canada Chile China PRC Colombia Costa Rica Croatia Czech Republic Denmark Dubai, UAE Finland France Germany Greece Hong Kong SAR Hungary India Indonesia Ireland Israel Italy Japan Korea Luxembourg Malaysia Mexico The Netherlands New Zealand Norway Peru Philippines Poland Portugal Puerto Rico Romania Russia Saudi Arabia Scotland Singapore Slovakia Slovenia South Africa Spain Sweden Switzerland Taiwan Thailand Turkey Ukraine United Kingdom United States Venezuela Vietnam Zimbabwe
Copyright 2001, Cisco Systems, Inc All rights reserved AccessPath, AtmDirector, Browse
Trang 4Breakthrough, iQ Expertise, iQ FastTrack, the iQ logo, iQ Net Readiness Scorecard, MGX, the
Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath,
Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert Logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post -Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc and/or its affiliates in the U.S and certain other countries
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners The use of the word partner does not imply a partnership relationship between Cisco and any other company (0104R)
This Document is strictly controlled through the Cisco Learning Partner license agreement Accordingly, do not copy, print or distribute this preliminary document
Building Scalable Cisco Internetworks, Revision 1.2: Student Guide
Copyright 2001, Cisco Systems, Inc
All rights reserved Printed in USA
Trang 7
Creating Multiple OSPF Areas 6-4 Routing Table Results with Different Areas 6-14
Written Exercise: OSPF Operation Across Multiple Areas 6-20
Using and Configuring OSPF Multiarea Components 6-22
Written Exercise: Redistribution and Controlling Routing Update Traffic 8-43
Trang 8When Not to Use BGP 9-10
Trang 9Router Password Recovery Procedure B-2
Answers to Written Exercise: Comparing Routing Protocols C-2
Answers to Written Exercise: EIGRP Overview C-6
Answers to Written Exercise: OSPF Operation C-8
Answers to Written Exercise: OSPF Operation Across Multiple Areas C-10
Answers to Written Exercise: Redistribution and Controlling Routing Update
Answers to Written Exercise: BGP Terminology and Operation C-18
Answers to Written Exercise: BGP Route Reflectors and Policy Control C-21
Answers to Extending IP Addressing Written Exercise: Calculating Subnet
Answers to IP Access Lists Written Exercise: IP Extended Access Lists C-24
Laboratory Exercise 1: Configuring EIGRP C-25 Laboratory Exercise 2: Configuring OSPF for a Single Area C-25 Laboratory Exercise 3: Configuring OSPF for a Single Area in an NBMA
Laboratory Exercise 4: Configuring a Multiarea OSPF Network C-26 Laboratory Exercise 5: Configuring a Multiarea IS-IS Network C-26 Laboratory Exercise 6: Configuring Policy-Based Routing C-26 Laboratory Exercise 7: Configuring Route Redistribution between OSPF and
Laboratory Exercise 9: Configuring BGP Route Reflectors and Prefix-List
Laboratory Exercise 10: Configuring Multihomed BGP C-27 Laboratory Exercise 12: Super Lab Part I and Part II C-27
Trang 10Task 2: Enabling EIGRP Connectivity to the backbone_r1 Router D-7
Task 2: Enabling OSPF Connectivity to the Backbone_r1 Router D-15
Task 1: Enabling OSPF with Multiple Areas and Area Summarization D-29
Task 3: Enabling an OSPF Totally Stubby Area D-31 Task 4: Enabling OSPF Not-So-Stubby Area (Optional) D-32 Task 5: Enabling an OSPF Virtual Link to Support an OSPF Area not
Laboratory Exercise 5: Configuring a Multiarea IS-IS Network D-39
Trang 11Task 1: Enabling IS-IS within your pod D-42 Task 2: Enabling connectivity to the backbone_r1 router D-44
Task 5: Using IS-IS show and debug commands D-46
Task 2: Enabling Full-Mesh IBGP Within Your Pod (AS) D-68
Task 1: Enabling pxr1 to be the Route Reflector D-74
Laboratory Exercise 10: Configuring Multi-homed BGP D-78
Trang 14Objectives
21
This section lists the lesson objectives
22
Insert Slide here
n Explain basic OSI terminology and network layer protocols used in OSI
Upon completing this lesson, you will be able to:
protocols used in OSI
Integrated IS -IS and OSPF
plan for IS-IS deployment
Trang 15Objectives (cont.)
29
Insert Slide here
n Describe the concept of establishing adjacencies
database synchronization
network) modeling solutions in switched WAN networks
parameters, identify the steps to configure Cisco routers for proper Integrated IS-IS operation
operation of Integrated IS-IS on Cisco routers
Trang 16Introduction to OSI Protocols and IS-IS
39
Routing
40
Insert Slide here
The OSI protocols are part of an international program to develop data-networking protocols
ISO and OSI?
• The International Organization for Standardization (ISO) has been constituted to develop standards for data networking.
• The Open System Interconnection (OSI) protocols represent an international standardization program that facilitates multivendor equipment interoperability.
Trang 17Insert Slide here
The OSI protocol suite supports numerous standard protocols at the physical, data-link, network,
OSI Protocols (cont.)
OSI Protocols (cont.)
The OSI protocol suite supports:
• Numerous standard protocols at each layer of the OSI reference model
• OSI network-layer hierarchical addressing
• Two routing protocols at the network layer
Trang 18Insert Slide here
In an OSI network four significant architectural entities exist: hosts, areas, a backbone, and a
Terminology used in OSI
• End system (ES) is any nonrouting network nodes (host)
• Intermediate system (IS) is a router
• An area is a logical entity
– Formed by a set of contiguous routers, hosts, and the data links that connect them
• Domain is a collection of connected areas
Trang 19Insert Slide here
The OSI protocol suite supports numerous standard protocols at each of the seven OSI layers
OSI Protocol Suite and its Mapping to the
OSI Reference Model
OSI Protocol Suite and its Mapping to the
OSI Reference Model
Trang 20Insert Slide here
Connectionless Network Service (CLNS) uses a datagram data transfer service and does not
OSI Network Services—
What to Route in OSI Environment?
OSI Network Services—
What to Route in OSI Environment?
Two types of OSI network-layer services are available to the OSI transport layer:
• Connectionless Network Service (CLNS)
– CLNS performs datagram transport
• Connection-Mode Network Service (CMNS)
– CMNS requires explicit establishment
of paths between communicating layer entities
Trang 21transport-Insert Slide here
CONP is based on the X.25 Packet-Layer Protocol (PLP) and is described in the ISO 8208
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 10
OSI Network Services—
• CMNS performs functions related to the explicit establishment of paths via CONP
• When support is provided for CMNS, the routing uses the X.25 protocols as the relaying functions
Trang 22Insert Slide here
CLNP is an OSI network-layer protocol that carries upper-layer data and error indications over
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 11
OSI Network Services—
• CLNS provides network-layer services to the transport layer via CLNP
• When support is provided for CLNS, the routing uses routing protocols to exchange routing information
Trang 23Insert Slide here
The OSI protocol suite includes several routing protocols and one router discovery protocol
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 12
OSI Network Services—Routing
• IS-IS routing protocols : hierarchical (level-1, level-2 and level-3) routing between Intermediate Systems
Trang 24Insert Slide here
Each ES lives in a particular area OSI routing begins when the ESs discover the nearest IS by
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 13
OSI Network Services—OSI Routing
ES ES
Trang 25Insert Slide here
For routing in the ISO CLNS/CLNP environment, Cisco routers support these protocols:
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 14
OSI Network Services—IS-IS Routing
OSI Network Services—IS-IS Routing
Intermediate System to Intermediate
routing protocol in ISO CLNS environment for routing CLNP
• Link-state routing protocol in the OSI stack
Alternative to IS-IS protocols is deploying
Trang 26Insert Slide here
Various aspects of IS-IS are described in these ISO documents:
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 15
OSI Network Services—
Trang 27Insert Slide here
IS-IS is the dynamic link-state routing protocol for the OSI protocol stack As such, it distributes
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 16
Integrated IS-IS vs OSPF
version of IS-IS for mixed ISO CLNS and IP environments
• Integrated IS-IS (RFC 1195) represents
an alternative to OSPF in the IP world
• Integrated IS-IS and OSPF are both link-state protocols with similar:
– Link-state representation, aging, metrics
– Link-state databases, SPF algorithms
– Update, decision, and flooding processes
Trang 28Insert Slide here
Because the configuration of OSPF is based on a central backbone (area 0), with all other
– In OSPF the border is inside routers (ABRs)
– Each link belongs to one area
• In IS-IS the area borders lie on links
– Each IS-IS router belongs to exactly one level-2 area
– IS-IS allows a more flexible approach
to extending the backbone
Trang 29Insert Slide here
With regard to CPU use and the processing of routing updates, IS-IS is more efficient Not only
compared to many OSPF LSAs
Scalability of link-state protocols has been proved (live ISP backbones)
• Convergence capabilities are similar (same algorithm)
• OSPF has more features (route tags, Stub/NSSA, OSPF over Demand Circuit…)
Trang 30Operation of IS-IS
175
Insert Slide here
The LSPs, hello PDUs, and other routing PDUs are OSI-format PDUs; therefore, every IS-IS
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 20
OSI Address Assignment
OSI network-layer addressing is implemented with network service access point ( NSAP ) addresses
• NSAP address identifies any system
in OSI network
• Various NSAP formats for various systems
– Different protocols may use different representation of NSAP
Trang 31Insert Slide here
Cisco routers can route CLNS data that uses addressing conforming to the ISO 10589 standard
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 21
IS-IS NSAP Address—Structure
IS-IS NSAP Address—Structure
IS-IS (ISO/IEC 10589) distinguishes only three fields in NSAP address:
• Area Address : variable-length field composed of high-order octets, excluding System ID and SEL
• System ID : ES or IS identifier in an area;
fixed length of 6 octets in Cisco IOS
• NSEL : N-selector, service identifier
Trang 32Insert Slide here
An OSI NSAP address can be up to 20 octets long
IS-IS NSAP is divided into three parts
octets (maximum)
ISO-IGRP NSAP is divided as follows:
• Area Address , composed of the first two octets
of the NSAP after the System ID and NSEL fields
• Domain , composed of high order octets (from 1 to 11) of the NSAP, excluding the Area,
Trang 33Insert Slide here
If the upper-layer process ID is 00, then the NSAP refers to the device itself – that is, it is the
Network Entity Title
• Network Service Access Point (NSAP)—address which (at the network layer) includes a service identifier (“protocol number”)
• Network Entity Title (NET)—NSAP with service identifier of 00
– Used in routers since they implement network layer only (base for SPF calculation)
• The official NSAP prefixes are required for CLNS routing—AFI 49 (Authority and Format Identifier) denotes private address space
Trang 34Insert Slide here
NETs and NSAPs must specify all hex digits and must start and end on a byte boundary
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 24
OSI Addressing—NET and System
System ID normally six octets (on Cisco six!) and has to be the same length everywhere Examples: 47 0001 0000.0c12.3456 00
01 192 1 68 11 1 003 00 1047.0001 1234.5678.9101 00
Trang 35Insert Slide here
1 The NSAP 47.0001.aaaa.bbbb.cccc.00 consists of:
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 25
OSI Addressing—NSAP Examples
System ID = aaaa.bbbb.cccc, NSEL = 00
System ID = aaaa.bbbb.cccc, NSEL = 00
Trang 37Insert Slide here
The area-ID is associated with the IS-IS routing process – a router can be a member of only
© 2001, Cisco Systems, Inc BSCI v1.2— 7- 26
Identifying Systems in IS-IS
Identifying Systems in IS-IS
The area address uniquely identifies the routing area and the System ID identifies each node
• All routers within an area must use the same area address
• An ES may be adjacent to a level-1 router only if they both share a common area address
• Area address is used in level-2 routing
Trang 38Insert Slide here
The System ID must be unique inside an area It is customary to use either a MAC address
• System ID used in level-1 routing and has to
be unique within an area (and of same length)
• System ID has to be unique within level-2 routers that form routing domain
• General recommendation: domain-wide unique System ID
Trang 39Insert Slide here
Some more IS-IS terms are:
Interfaces uniquely identified by Circuit ID:
• One octet number on point-to-point interfaces (03)
• Circuit ID concatenated with 6 octet System ID
of a designated router on broadcast multiaccess networks to form 7 octet LAN ID-
Trang 40Insert Slide here
The diagram shows examples of NETs for routers in an IS-IS domain:
Identifying Systems—OSI Addressing in Network