CCNA Learning notes 7--Dynamic routing protocol concepts and RIP

Routing protocols are used to automatically determine paths and maintain routing tables between routers

After the path is determined, the router can route the routed protocol: that is, the IP protocol can be forwarded

Work Step: Receive routing information from other routers

Pass routing information Like other routers

Based on the routing information received, the optimal path to the destination network is calculated and the routing table is generated.

Respond to network topology changes in a timely manner, generating new routing tables and declaring topology change information to other routers

Summary: Automatic collection of information, according to their own algorithm to calculate the optimal path, generate a routing table, periodic update and trigger updates and redness

Static routing protocol, dynamic routing protocol

Distance vector protocol: Every day the router relies on its own neighboring routers on the routing information, and two of his neighboring routers are also learning routes through their own neighboring routers.

You only need to maintain neighboring routers

Typical: RIP

Link state protocol: A router running a link-state protocol divides the router into areas, collects all the link state information within the region, and generates a network topology based on the state information, and each router calculates the route based on the topology.

Need to maintain the entire topology in the area

Typical: OSPF

A class of routing protocol, Wu class routing protocol

Internal Gateway Protocol (IGP) exchanges routing information within the same home-made system

Typical: OSPF

The External Gateway Protocol (EGP) is used to exchange routing information between different homemade systems

Typical: BGP

Self-made systems: Network collections using the same network routing criteria

IGP runs within an autonomous system

EGP connects to different autonomous systems.

RFC definition of AS: A group of managed routers that use the same internal gateway Protocol and uniform Metrics to group as internal routes and use the external gateway protocol to route packets to other as.

Consistent routing table entry---convergence

Network completion convergence, each router has a complete routing table

Convergence times (convergence time) changes from network topology to entire network all routers know the time for this change

For IGP, the shorter the convergence time is ideal; not for the EGP (the range of EGP, the small changes have a large influence on the performance of the equipment, all as long as the stability of the more ideal).

Summary

{Summary

{Select

{static {floating

{{Load

Route {{Recursive

{

{{Distance vector: RIP.} Advanced distance vector (blend): EIGRP

{{IGP}

{dynamic {link state: OFPF ISIS

{EGP:BGP (distance vector protocol with path information)

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Ideas for learning protocols: RIP

1: Classification distance vector; IG; P No class

2: Package UDP520

3: Updated address 224.0.0.9

4: Route Update Method timed 30 sec + Full UPDATE, trigger update

5:ad value (distinguishes between different protocols, the smaller the higher the priority) 120. Direct-Connect AD is 0

6: Measure (differentiate the same protocol) hop count Max 15, 16 Hop unreachable, hop count equal load balancer

AD: Direct Connect 0

Static use of local exit 0; Use next-hop address 1

EIGRP Rollup 5

External BGP 20

Internal EIGRP 90

IGRP 100

OSPF 11

Is-is 115

RIP 120

EGP 140

ODR 160

External EIGRP 170

Internal BGP 200

RIP protocol (Routing information protcol) Slow convergence

The RIP protocol automatically updates the 224.0.0.9 as the target IP, and the router that runs the RIP protocol automatically receives the information that is carried by the 224.0.0.9 address.

Timed + Full Update wastes bandwidth resources when there are too many routing entries

Configuration

Router RIP

Ver 2

No auto

Network x.x.x.x Main class networks announce that only direct connect

A direct-attached main class network, not a route for advertised announcements. It's a range of announcements.

One of the interfaces in the range is enabled for RIP, which ultimately advertises the direct-attached routes generated under this interface

To view a command:

Show IP Procol

Show ip route or sho IP route rip

Debug IP Rip

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/74/D7/wKioL1YrNtijkZbJAAHM_h0VcV0673.jpg "title=" QQ picture 20151024154815.jpg "alt=" Wkiol1yrntijkzbjaahm_h0vcv0673.jpg "/>

DEBUP command: Monitor internal processes (such as RIP send and receive updates)

After the event occurs, the resulting log

Continuously generated log information until the debug command is turned off no debug

Note: Debug should be turned off after debugging is complete

No debug RIP

No Debug All

When the debug information is too many no debug all need to blind hit

RIP anti-ring method

Hop count: Prevent infinite loops

horizontal split: Resolves messages sent from their own interfaces, and the information is wrong

Trigger Update: The resolution period is too long and the cycle cannot converge

Route poisoning: Resolve a failed network connection because the horizontal split cannot sync to another router, causing the data to loop on the network

suppress timers: Resolves an unstable network connection in the network causing an inability to converge and a loop occurs. This method has been canceled

The maximum hop count does not resolve the loop, only alleviates the effect of the loop

Horizontal split: Routes received from one interface are not sent from the same interface

Route poisoning: When a route disappears, triggering an update, the disappearing route that is carried on the update is set to Infinity 16. Then the whole network spreads.

Toxicity reversal: Confirmation of route poisoning (only if a route poisoning occurs for IPv4) because RIP uses UDP520, it is unreliable, so in order to confirm that a routed neighbor that knows about poisoning has received, prevent a loop from being received that continues to use this disappearing route.

If the other person does not reverse the toxicity, the poison route will immediately send a poison route again.

Update Timer: 30 seconds

Invalid timer: 6 times times 180 seconds when a failed route is kept for 180 seconds before it is deleted

Flash Timer: After 180 seconds of failure routing has not been updated, is set to possiblely down will wait 60 seconds to completely delete

Timer can be modified, it is recommended not to modify, if you modify all RIP network to change time basic update invalid Holddown flush

Auto Summary

Points:

What do you summarize? Summarize self-proclaimed routes, redistribute routes, routes learned from neighbors

How many bits are rolled up? Summarize to main class

Where to summarize? For an environment that is connected to a subnet, advertise the detail route and reach the network boundary before the rollup occurs

Network boundary: In a continuous subnet environment will not be aggregated, such as 3.1.1.1/8 upload to 2.1.23.1/24

In a disjoint subnet environment, which is the boundary of the main class network, it is aggregated. For example 3.1.1.1/8 to 22.1.1.1/24

Manual Rollup:

In routing out direction do

All routes can be summarized

Command: Interface under IP summary-address rip .....

Example: 3.1.1.1----3.1.1.6; 3.1.1.0 255.255.255.248 after summary

Summary features:

The rollup suppresses all of the included details

The aggregated route produces a measure that is the smallest of all the details

If none of the details are included, the rollup disappears. Vanishing part does not affect the rollup

RIP produces default routes

Role: Default-information originate under the Border gateway write RIP process, then all routers connected to the gateway will automatically generate a day default route 0.0.0.0 to the next hop through RIP.

Authentication: The purpose is only to exchange routing information between routers that do authentication

PlainText and MD5

The default does not do authentication

Step: 1: Open authentication under the interface

2: Global: Configure Key Chain key

3: Called Under interface

Key-id inconsistency is also possible, but the proposal has been. Passwords must be consistent.

CCNA Learning Note 7--Dynamic routing protocol concepts and RIP