[Lab1]-eigrp Test

1-EIGRP Test

EIGRP is an efficient routing protocol with the following features:

1. Establish and maintain neighbor relationships by sending and receiving Hello packets, and exchanging routing information;

2. Use multicast (224.0.0.10) or unicast for routing updates;

3. EIGRP has a management distance of 90 or 170;

4. Use trigger update to reduce bandwidth consumption;

5. Support variable eldest son netmask (VLSM), turn on Auto summary function by default;

6. Support IP, IPX, AppleTalk and many other network layer protocols;

7. For each network protocol, EIGRP maintains a separate neighbor table, topology table, and routing table;

8. EIGRP uses the diffusing Update algorithm (DUAL) to achieve rapid convergence. and ensure that there is no routing loop;

9. Store information about the entire network topology to quickly adapt to network changes;

10. Support for equivalent and non-equivalent load balancing;

11. Use Reliable Transfer Protocol (RTP) to ensure the reliability of routing information transmission;

12. Seamlessly connecting data link layer protocols and topologies, EIGRP does not require a 2-layer protocol for the OSI Reference Model

Special configuration.

1.1 EIGRP Unicast Update

R1 (f0/0)-----(F0/1) R2

EIGRP can not only multicast routing updates but also unicast routing updates, and the command must be done on all router

R1(config-router) #neighbor 12.1.1.2 f0/0 \ command is typed in routing mode
R2 (config-router) #neighbor 12.1.1.1 F0/1

But if there is a passive-interface command, neither unicast nor multicast can establish a neighbor

R2 (config) #router EIGRP 90

R2 (config-router) #passive-interface Default

R2 (config-router) #no passive-interface F0/1

Passive interface can be used when connecting clients to a general port

1.2 EIGRP Certification

R1 (f0/0)-----(F0/1) R2

EIGRP only supports MD5 authentication by default, and authentication must be done at both ends

R1/2 (config-if) #ip authentication mode EIGRP MD5 \ \ Interface to enable authentication

R1/2 (config-if) #ip authentication key-chain EIGRP fuyi/2 \ \ Call Key-chain on EIGRP authentication

R1 (config) #key chain Fuyi

R1 (Config-keychain) #key 0

R1 (Config-keychain-key) #key-string FUYICCNA \ \ Certification process is to take the minimum number of a key to verify ( and both ends must use the same key ID [key 0] to verify ), will not use Key1 or Key2 to go down to verify so we should be in the R2 configuration as follows

R2#sh Run | Se key Chain

Key Chain Fuyi2

Key 0 \ \

Key-string FUYICCNA

Key 1

Key-string FUYICCNA

Additional key configuration can also be connected to Send–lifetime and accept–lifetime to define the validity period of a key

1.3 EIGRP Manual Rollup

Topology diagram: R1 (e0/0)----(E0/1) R2 (e0/0)----(E0/1) R3

r1#sh IP int b

Interface ip-address OK? Method Status Protocol

ethernet0/0 12.1.1.1 YES Manual up

Loopback0 192.168.0.1 YES Manual up

Loopback1 192.168.1.1 YES Manual up

Loopback2 192.168.2.1 YES Manual up

Loopback3 192.168.3.1 YES Manual up

All-web-run EIGRP

Scenario One:

If the R1 EIGRP is declared, the net 192.168.0.0 0.0.255.255

So look at the routing table on R3.

R3#sh IP Rout EIGRP

D 192.168.0.0/24 [90/435200] via 23.1.1.2, 00:01:57, ETHERNET0/1

12.0.0.0/24 is subnetted, 1 subnets

D 12.1.1.0 [90/307200] via 23.1.1.2, 00:02:45, ETHERNET0/1

D 192.168.1.0/24 [90/435200] via 23.1.1.2, 00:01:57, ETHERNET0/1

D 192.168.2.0/24 [90/435200] via 23.1.1.2, 00:01:57, ETHERNET0/1

D 192.168.3.0/24 [90/435200] via 23.1.1.2, 00:01:57, ETHERNET0/1

Description Network It's R1 . Direct routing in 192.168.0.0/16 The routing information inside is declared out.

Scenario Two: in case 1 under the conditions of On R1 ( or R2 ) Add: Eigrp Rollup Routes

R1 (config-if) #ip summary-address EIGRP 90 192.168.0.0 255.255.252.0

R3#sh IP Rout EIGRP

12.0.0.0/24 is subnetted, 1 subnets

D 12.1.1.0 [90/307200] via 23.1.1.2, 00:08:54, ETHERNET0/1

D 192.168.0.0/22 [90/435200] via 23.1.1.2, 00:00:18, ETHERNET0/1

Description Manual rollup suppresses clear routing, produced a 192.168.0.0/22. the routing

also produces d 192.168.0.0/22 is a summary, 00:02:49, Null0 Prevent routing loops

then it means that the R1 Knock Network 192.168.0.0/16 is not in effect

another: That 's the problem, man. ask for the answer to the question. J

1.4 Eigrp injects a default route

650) this.width=650; "height=" 176 "title=" clip_image002 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/ M02/6e/22/wkiol1v1ds3dretnaabgxomy5-o262.jpg "border=" 0 "/>

3.3.3.3 is the internet

1.4.1 Redistribution Method

Redistribute static routes into EIGRP

R2 (config) #ip Route 0.0.0.0 0.0.0.0 s1/0

R2 (config) #router ei 90

R2 (config-router) #redistribute static

650) this.width=650; "height=" title= "clip_image004" style= "margin:0px;border:0px;padding-top:0px"; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M00/6e/22/wkiol1v1ds7zya5daae0qxix5xc926.jpg "border=" 0 "/>

1.4.2 Announces all 0 laws

In R2 write a static route to the Port (meaning the next hop is invalid, the previous blog has explained the reason), on EIGRP with network 0.0.0.0 declaration

< results do not show, the result is the same as the previous method >

1.4.3 Using IP default-network

Conditions for using this command:

Note that to be able to see the test results, be sure not to use the network 0.0.0.0 to announce the route

650) this.width=650, "height=", "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px;padding-right : 0px;padding-left:0px;background-image:none; "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/M01/6E/22/ Wkiol1v1ds6x5mg3aaciqnv0lis085.jpg "border=" 0 "/>

The R2 is configured as follows

IP default-network 3.0.0.0

IP Route 3.0.0.0 255.0.0.0 serial1/0

R2#sh Run | SE router ei

Router EIGRP 90

Network 3.0.0.0

Network 12.0.0.0

No auto-summary

650) this.width=650; "height=" "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M02/6e/22/wkiol1v1dtcy-_49aadbyqvjsqa682.jpg "border=" 0 "/>

1.5 EIGRP Load Balancing

Topology diagram

650) this.width=650; "height=" "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M00/6e/22/wkiol1v1dtgi85hraacsuhcfrwk828.jpg "border=" 0 "/>

1.5.1 Equivalent Load Balancing

The default EIGRP is turn on equivalent load balancing, because the value of variance is 1

EIGRP Maximum metric Variance 1

To facilitate the calculation of the metric value, we use the command to modify the K value

R1/2/3/4 (config-if) #router Eig 90

R1/2/3/4 (config-router) #metric weight 0 0 0 1 0 0

Default metric Calculation formula: metric= [10^7/bandwidth (min) + delay (sum)/10] * 256

See 3.3.3.3 's routing table on R1

D 3.3.3.0 [90/665600] via 14.1.1.4, 00:00:58, FASTETHERNET0/1

[90/665600] via 12.1.1.2, 00:00:58, fastethernet0/0

Let's figure out how the next 665600 came from.

Show Inter f0/0 s1/0 lo0

We can see the delay of each interface, so we add up the delay of these interfaces.

Metric The direction of the calculation is the direction of the routed interface (interface in direction)

6656600 = (20000 + 1000 + 5000)/10 * 256

1.5.2 non-equivalent load balancing

How do I turn on load balancing?

First load balancing occurs between S and FS, so the conditions for opening it are:

1 AD < (S) FD ===> is also a condition for becoming FS

2 FS FD < S FD * V value

Let's change the delay of the R2 to a little higher, and R4 the delay to a little.

R2 (config) #int s1/0

R2 (config-if) #delay 15 (actually 150 subtle, 10 times times the multiple relationship)

R4 (config-if) #delay 10

At the same time, let the V value not equal to 1 on R1

R1 (config) #router ei 90

R1 (config-router) #variance 2

Look at the topology table on R1

R1#sh IP eigrp topology

P 3.3.3.0/24, 1 successors, FD is 156160

Via 14.1.1.4 (156160/130560), FASTETHERNET0/1

Via 12.1.1.2 (157440/131840), fastethernet0/0

Conditions 1:131840 < 156160 meet the conditions of becoming FS

Condition 2:FD (primary) *variance >FD (Backup)

156160 * 2 > 157440

Show ip route to view results

Route filtering for 1.6 eigrp

Test requirements: Use of the test topology diagram, the entire network to run EIGRP

Open three Lookback ports in R1, 1.1.1.1 10.1.1.1 100.1.1.1 address respectively

650) this.width=650; "height=" 214 "title=" clip_image012 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/ M01/6e/22/wkiol1v1dtkcdwiiaacfmbugzpu239.jpg "border=" 0 "/>

Requires R3 to see only 100.1.1.1

Answer: Using Distribute-list

Use Access-list on R3, and then use Distribute-list in EIGRP protocol mode

R3#sh IP access-lists

Standard IP access list 10

Ten deny 1.1.1.0, wildcard bits 0.0.0.255 (4 matches)

Deny 10.1.1.0, wildcard bits 0.0.0.255 (4 matches)

Permit any (6 matches)

R3 (config) #router ei 90

R3 (config-router) #distribute-list

The test results are as follows:

650) this.width=650; "height=" 137 "title=" clip_image014 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image014 "src=" http://s3.51cto.com/wyfs02/ M02/6e/22/wkiol1v1dtsclb47aadxnpln7r0193.jpg "border=" 0 "/>

The use of 1.7 offset-list in EIGRP

After the experiment, we made the metric value of the 100.1.1.0 route from 23.1.1.2 to an instant increase to 600000

Command:

R3#sh IP access-lists

Standard IP access list 20

Permit 100.1.1.0, wildcard bits 0.0.0.255 (4 matches)

R3 (config) #router ei 90

R3 (config-router) # offset-list in 600000 serial1/0

View R3 's routing table again and discover that metric becomes 1265600 (665600+600000)

D 100.1.1.0 [90/1265600] via 23.1.1.2, 00:00:24, serial1/0

1.8 EIGRP stub

The Eigrp stub is a better way to avoid SIA because it can limit the scope of the query

The topology diagram is as follows:

650) this.width=650; "height=" "title=" clip_image016 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image016 "src=" http://s3.51cto.com/wyfs02/ M00/6e/22/wkiol1v1dtsbqjghaabkohntxum799.jpg "border=" 0 "/>

Turn off the LO 0 port of the R1, debug EIGRP packages can see that R1 will query the R2 for 1.1.1.0 's routed query message

*mar 1 07:49:08.142:eigrp:sending QUERY on fastethernet0/0

Typing on R2

R2 (config) #router Eig 90

R2 (Config-router) #eigrp stub

Mar 1 07:53:06.606:eigrp:received query on fastethernet0/0 NBR 12.1.1.2 "R1 will only receive the R2 query message, R1 will not send a query message to R2"

Of course, there's no R3 on the 1.1.1.0. This network segment route

But when we were in R1 the lo 0 under Mouth no shut after R3 never learn the 1.1.1.0 . the routing The reasons are as follows :

By default, stub router only passes straight and summarized routes

So to reveal 1.1.1.0 What is the solution?

We can use Leak-map

Step1:access-list

R2#sh IP access-lists

Standard IP access list 10

Permit 1.1.1.0, wildcard bits 0.0.0.255

Step2:route-map

R2 (config) #route-map Fuyi

R2 (config-route-map) #match IP address Fuyi

R2 (Config-route-map) #exit

STEP3: Call Route-map

R2 (config) #router EIGRP 90

R2 (Config-router) #eigrp stub leak-map Fuyi

Test results

650) this.width=650; "height=" 226 "title=" clip_image018 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/M01/6E/22/ Wkiol1v1dtbhab46aae7ssbqggg759.jpg "border=" 0 "/>

1.9 EIGRP Common commands

Show ip eigrp neighbors view eigrp Neighbor table

Show ip eigrp topology view EIGRP topology database

Show IP EIGRP interface View the status of the interface running the EIGRP routing protocol

Show IP EIGRP Traffic View statistics of packets sent and received by EIGRP

Debug EIGRP Neighbors View eigrp Dynamic building of neighbor relationships

Debug EIGRP Packets Displays the EIGRP packets sent and received

IP hello-interval eigrp configuration for the Hello send cycle of EIGRP

Hello hold time for IP hold-time eigrp configuration eigrp

Router EIGRP initiates the EIGRP routing process

No auto-summary off Auto Summary

IP Authentication Mode EIGRP configuration for EIGRP authentication modes

IP authentication key-chain EIGRP on the interface to raise the key chain

Variance Configuring non-equivalent load balancing

Delay under the delay configuration interface

Bandwidth bandwidth under the configuration interface

offset-list [access list number] in [values] [interface] Adjust metric value

IP summary-address eigrp Manual route Rollup

This article from the "Erick" blog, declined to reprint!

[LAB1]-EIGRP Test