ROUTE: Implementing Cisco IP Routing Course 1: Routing Services

ROUTE: Implementing Cisco IP Routing Course 1: Routing Services Slide 1 ROUTE: IMPLEMENTING CISCO IP ROUTING Course 1: Routing Services __________...
Author: Adrian Edwards
13 downloads 3 Views 549KB Size
ROUTE: Implementing Cisco IP Routing Course 1: Routing Services

Slide 1

ROUTE: IMPLEMENTING CISCO IP ROUTING Course 1: Routing Services

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 2

Course 1 Objectives 

Describe common enterprise traffic requirements and network design models.



Describe how to create a plan for implementing routing services in an enterprise network.



Review the fundamentals of routing and compare various routing protocols.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 3

Topic A

Complex Enterprise Network Frameworks, Architectures, and Models

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 4

Traffic Conditions in a Converged Network 

Converged networks support the following types of traffic:   

  





Routing protocol traffic Network management traffic Transactional traffic Mission-critical traffic Voice and video traffic Voice applications traffic

The listed traffic has great effects on network performance and security. Cisco has developed the Intelligent Information Network (IIN) in order to enhance enterprise networks.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 5

IIN: Cisco Intelligent Information Network 

IIN or Intelligent Information Network:  



Plays an active role in delivering services and applications. Bridges and extends intelligence across infrastructure layers and multiple products.

The Intelligent Information Network consists of three phases in which functionality can be integrated with to the infrastructure in the forms of:   

Integrated applications Integrated services Integrated transport

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 6

Three Phases of the Intelligent Information Network 

Phase 1: Integrated transport 





Integrates video, voice, and data transport into one modular and standards-based network in order to generate enterprise-wide efficiencies and simplify network management.

Phase 2: Integrated services 

Integrated services help to unify data center server capacity and storage.



The Intelligent Information Network provides business continuity in order to survive local systems failure. This can be achieved thanks to shared resources across the Intelligent Information Network.

Phase 3: Integrated applications 

This phase optimizes application performance and delivers networked applications to users in an efficient way in order to making the network application aware.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 7

Three Phases of the Intelligent Information Network Graph



Phase 1: Integrated Systems



Phase 2: Integrated Services



Phase 3: Integrated Applications

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 8

Cisco SONA Framework 

SONA or Cisco Service-Oriented Network Architecture is an architectural framework used to provide operational efficiency through standardization and virtualization and create a flexible and dynamic architecture. 





SONA provides blueprints guidance, and best practices for connecting applications and network services enabling business solutions. In the SONA framework, the common element that connects and enables all components of the information technology infrastructure is the network.

SONA enables corporations to achieve their business goals by leveraging:   

The experience of Cisco and its partners The proven Cisco architectures The extensive Cisco product-line services

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 9

Cisco SONA Framework Layers



Application Layer



Interactive Services Layer



Networked Infrastructure Layer

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 10

Networked Infrastructure Layer

SONA: Networked Infrastructure Layer

Campus

Branch

Server

Data Enterprise WAN/MAN Teleworker Center Edge Storage

Clients

Intelligent Information Network

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 11

SONA: Interactive Services Layer

Security Services Mobility Services

Application-Oriented Networking Voice &

Infrastructure Services

Storage Services

Collaboration Services

Compute Services Identity Services

Network Infrastructure Virtualization

Adaptive Management Services

Services Management Services Virtualization

Interactive Services Layer

Advanced Analytics & Decision Support

Application Delivery

Infrastructure Management

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 12

PLM

CRM

ERP

HCM

Procurement

SCM

Collaboration Layer

Application Layer

SONA: Application Layer

Instant Unified Messaging Messaging

IPCC

IP Phone

Meeting Place Video Delivery

Middleware & Application Platforms

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 13

Business Applications

Collaboration Layer

Application Layer

Updated SONA Framework

Applications Collaboration Applications

Internally Developed

Commercial Applications

Software as a Service (SaaS)

Composite Apps / SOA

Middleware & Application Platforms Core Common Services

Adaptive Management Services

Interactive Services Layer

Networked Infrastructure Layer

Transport

Virtualization

Clients

Management

Storage

Security

Server

Application Delivery

Places in the Network

Mobility

Infrastructure Services

Real Time Communication

Application Networking Services

Physical Infrastructure

Cisco designs, tests, and validates sets of modular, connected infrastructure elements organized by places in Cisco designs, tests, and validates sets of modular, infrastructure elements organized by places in theconnected network (PINs). the network (PINs).

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 14

Updated SONA Framework Continued Applications Commercial Applications

Internally Developed

Exposed Real Time Communication

Mobility

Multimedia Bridge

Location Telemetry

Multimedia Record & Playback Presence Session Control

Session Management Topology Management Voice Recognition

Context Aware Mobile Intelligent Routing

Application Delivery

Security AAA Policy

Compression

Device ID Management End Point Attack Prevention

Management Configuration

Virtualization

End Point Posture Validation

Caching

Data Loss Prevention Firewall Intrusion/Anomaly Detection

Transport

VPN

Multicast

Accounting

VLAN

Provisioning

VSAN

Network Heuristics

Performance

Switch

Virus Protection

ContentBased Routing

Protocol Optimization

Composite Apps / SOA

Transparent Core Common Services

XML Processing

Content Distribution

Software as a Service (Saas)

Fault Discovery Power Management

Intrusion Prevention

Service Partitioning I/O Load Balancing

Switching Routing Transcoding Quality of Service

Filtering Encryption/ Decryption

Physical Infrastructure

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 15

Cisco Enterprise Architecture Network Locations of SONA Network Infrastructure Layer    

Campus Data Center Branch Teleworker

Enterprise Architecture enables organizations to:  



Grow Optimize Protect

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 16

Campus Architecture Provides:  Flexibility  Integrated security  QoS  Multicast  Automatic procedures  High availability

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 17

Branch Architecture



Central configuration and management



Integration



Head-office support

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 18

Data Center Architecture



Scalability



Load balancing



Redundancy



Adaptive network architecture

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 19

Teleworker Architecture



Campus security policies



Centralized management



Enterprise Branch-of-One

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 20

Cisco Hierarchical Network Model 



The three-layer hierarchical model is used to design networks. The three-layer model consists of the: Access layer  Distribution layer  Core layer 



This flexible modular framework allows for better implementation and troubleshooting.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 21

Hierarchical Campus Model

Workgroup Access

Access

Policy-Based Connectivity

Distribution

High-Speed Switching

Core

Edge Distribution Module

Server Farm

Departmental Switch Block

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 22

The Hierarchical Model in a Wide Area Network

Core Layer

Distribution Layer

Distribution Layer

Access Layer Access Layer

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 23

The Enterprise Composite Network Model



The following three functional areas are a result of the network division carried by the Enterprise Composite Network Model: 1- Enterprise Campus 2- Enterprise Edge 3- Service Provider Edge

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 24

Topic B

Creating, Documenting, and Executing an Implementation Plan

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 25

Creating an Implementation Plan



A well written implementation plan is a result of good procedures and processes during network design, deployment, and testing.



There are two approaches to making network changes: Structured approach  Ad-hoc approach 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 26

Structured Approach

  



Considerations are taken into account Changes to network parameters Meeting both business and technical requirements Documentation and implementation

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 27

Ad-hoc Approach

  

The many tasks that do not require planning With such an approach, issues can occur An effective implementation plan is needed to avoid issues

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 28

Methodologies and Models 



In the industry, there are various methodologies and models used to depict a lifecycle approach. Examples of current major models: 



Telecommunications Standardization Sector (ITU-T)

The Telecommunications Management Network (TMN) model 

International Organization for Standardization (ISO)

The Fault, Configuration, Accounting, Performance, and Security (FCAPS) model  IT Infrastructure Library (ITIL)  The Cisco Lifecycle Services (PPDIOO) model 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 29

Cisco Lifecycle Services (PPDIOO) Model The Cisco Lifecycle Services approach or PPDIOO model consists of six phases in the network lifecycle:  Step 1: Identify customer requirements  Step 2: Characterize the existing network and sites  Step 3: Design the network topology and solutions  Step 4: Plan the implementation  Step 5: Implement and verify the design  Step 6: Monitor and optionally redesign

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 30

Implementation Plan Documentation 

The implementation plan documentation includes the following elements:   

   



Photos and screen shots Performance measurement and results Verification tasks Implementation plan tasks Resources required Tools required Network information

Once the verification information is added at the end of the project, the documentation creation process is deemed complete or finished.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 31

Sample Implementation Plan 







  

Project contact list (listing involved employees or team members) Statements of work (listing the role of each employee or team member) Equipment, location of project site, and premises related information Resources, material, and tools Project related assumptions Detailed tasks to be completed in the project Network staging plan

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 32

Example of Project Contact List   

  

  

  

Project manager name: Project manager phone: Project manager email: Network engineer name: Network engineer phone: Network engineer email: Network designer name: Network designer phone: Network designer email: Network technician name: Network technician phone: Network technician email:

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 33

Example of Implementation Task List 

       

Step 1: Access the switch management interface Step 2: Backup the IOS Step 3: Update the IOS Step 4: Disable all unused access ports Step 5: Deploy the extra switch Step 5: Configure an Accounting VPN Step 6: Configure a VoIP VPN Step 7: Verify configuration and record the results Step 8: Backup the running config on both switches

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 34

Example of Tools Required 

  

Item 1: Ethernet cable, 25 meters Item 2: Laptop to manage switch configuration Item 3: Console port cable Item 4: 16 port switch

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 35

Example of Equipment Floor Plan 

    



Location address: Building (in case of multiple buildings): Floor number: Suite number: Room number: Installation position: Rack and shelf numbers:

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 36

Topic C

Overview of IP Routing

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 37

IP Routing 

A router can be made aware of non-directly attached networks in two ways: Dynamic routing: the router learns from other routers.  Static routing: a network engineer inputs the information by manually configuring the router. 



Routing tables contain both dynamic and static routes.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 38

Dynamic Routing 

    



The dynamic routing protocols that do not call for human configuration are: IS-IS OSPF EIGRP RIPv1 RIPv2

Routing protocols use interface speed, and hop counts as measurements to determine their metrics. They then exchange their metrics or distance to various destinations.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 39

Static Routing Static routes are configured with the IP Route command.  For example: Router(config)# ip route prefix mask address interface dhcp distance name next-hop-name permanent track number tag tag 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 40

Third Option: OnDemand Routing 

Known as the Cisco On-Demand Routing (ODR) feature. 







ODR requires a lot less admin configuration than static route and uses a lot less overhead than dynamic routing.

It only functions in hub-and-spoke networks and uses CDP for this purpose. It is configured by using the Router ODR global config command on the hub router and shows as an O under the routing table. It has an administrative distance of 160.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 41

Link-State Versus Distance Vector Protocols 

Link-state routing protocol:  



Routers send the state of their own interfaces to all other area routers whenever there is a change. Routers use the received information above to recalculate the best path to each network and then save this received information to their routing tables.

Distance vector protocol:  

Routers send their entire routing tables or a portion of them to their neighboring routers on a periodic basis. The received updates are used by routers to determine whether any changes need to be made to their routing tables.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 42

Classless Versus Classful Routing 

Classless Routing Protocol: RIPv2, EIGRP, OSPF, IS-IS, and BGP are classless routing protocols.  Routing updates sent include the subnet mask.  Supports VLSM. 



Classful Routing Protocol: RIP Version 1 (RIPv1) is a classful routing protocol.  Routing updates sent do not include the subnet mask.  Does not support VLSM. 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 43

Discontiguous Subnets - Classful Routing 

Discontiguous networks are not supported by classful routing protocols.



Example of a discontiguous network: 192.168.1.0 /24

192.168.2.0 /24

Fa0/0

Fa0/0

R1

R2

R3

172.16.1.0 /24

RIPv1 update 172.16.0.0

172.16.2.0 /24

RIPv1 update 172.16.0.0

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 44

Discontiguous Subnets - Classless Routing 

Discontiguous networks are supported by classless routing protocols

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 45

IP classless Command 

When the ip classless global config command is applied, it alters the behavior of a classful routing protocol.



Classful protocols are programmed to assuming that if a router knows one or more network subnets of a classful network such as 10.0.0.0, then it knows all existing subnets on that network.



IP classless is enabled by default and not to be disabled with IOS release 12.0 and all newer releases.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 46

Automatic Route Summarization 

This does not apply to classless routing as this feature is disabled. The IS-IS and OSPF routing protocols do not offer automatic network summarization option.  The EIGRP and RIPv2 run network summarization automatically to maintain backward compatibility with the IGRP and RIPv1 routing protocols.  We can always use the no auto-summary router configuration command in order to disable automatic summarization on the EIGRP and RIPv2 routing protocols. 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 47

Criteria of Routing Table 

By considering the following four points, routing protocols can chose the best route selected from various routing protocols for destinations: Prefix  Metric  Administrative distance  Valid next-hop IP address 

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 48

Administrative Distance 





Administrative distance is used by a Cisco Router to select the best path when it learns of various possible routes to the desired destination with the same prefix from various routing protocols. Administrative distance is used to rate the believability of a routing protocol. A default administrative distance value has been assigned to each routing protocol by Cisco. 

Routing protocols are prioritized in the order of most to least believable.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 49

Administrative Distances

The Route Source

Corresponding Default Distance



Connected interface



0



Static route out an interface



0



Static route to a next-hop address



1



EIGRP summary route



5



External BGP



20



Internal EIGRP



90



IGRP



100



OSPF



110



IS-IS



115



RIPv1, RIPv2



120



Exterior Gateway Protocol (EGP)



140



ODR



160



External EIGRP



170



Internal BGP



200



Unknown



255

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 50

Floating Static Route 



Static routes always have priority over dynamic routes. We can always create a floating static route to alter this default router behavior by simply reconfiguring the administrative distance of the static route to a less believable or higher distance that the dynamic route. This enables the modified route to float. This is configured on a static route by using the ip route command with the distance parameter.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Slide 51

Course 1 Summary 

Describe common enterprise traffic requirements and network design models.



Describe how to create a plan for implementing routing services in an enterprise network.



Review the fundamentals of routing and compare various routing protocols.

_____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

Review Questions: 1. Converged networks contain a variety of different types of traffic. Which of the following is one of those types? A. Routing Protocol Traffic B. Routed Protocol Traffic C. Network Administration Traffic D. Non-Mission Critical Traffic 2. What is one of the three phases of the Intelligent Information network? A. Integrated Protocols B. Integrated Applications C. Integrated Systems D. Integrated Transmission 3. Campus architecture provides which of the following? A. Interoperability B. Integrated Systems C. QoC D. High Availability 4. Which of the following does Branch Architecture offer? A. Active interaction B. Decentralized configuration and management C. Integration D. Independent support 5. True or False: Data Center Architecture allows for growth. A. True B. False

Answer Key: 1. A Routing Protocol Traffic is a type of traffic contained on a converged network. 2. B Integrated Applications is one of the three phases of the Intelligent Information network. The other two are Integrated Services and Integrated Transport. 3. D Campus architecture provides high availability. 4. C Branch Architecture offers integration. 5. A True. Data Center Architecture offers scalability, and therefore allows for growth.