Cisco EIGRP Labs

Frame-relay:

: Configure Frame-relay SWITCH so that the Frame-relay PVC between R2,R3,R3 is Full-mesh. However, only the PVC shown in the figure can be used.

R2,R3,R4 Physical Interface Connection Framme-relay SWITCH

Between R4 and R5, use a PPP link. Please eliminate redundant 32-bit host routing

R1,R2,R3 's Ethernet ports are connected to a switch

Configure by IP address shown in the figure

Ensure each link can ping each other

R1-r5 each have a LO0, the address is: 10.10.x.x/24 (X is your router number)

Part 1---RIP

R1,r2,r3 runs RIP VERSION 2 and announces the direct-attached Ethernet network segment of LO0 and routers to rip

You can see each other's LO0 in the routing table of three routers.

On R1, add eight interfaace addresses with a minimal command line. The address is 100.1.1.1/24---100.1.8.1/24, the eight addresses that appear as external routes in R1 's RIP database

Only in R1 do the configuration, and use the fewest command line, so that R3 can see the eight segments of the seven, see 100.1.8.0/24 this route, and the odd route hop is 5, even route hop is 7, cannot use version, Offset-list

You cannot make any configuration in R2 , so that R2 cannot see the eight routes, but you can see the LO0 of R1,R3. Resolve this issue by using version 1 and resolving this issue

Part 2----EIGRP 100

R2,R3,R4 frame-relay Link Run eigrp 100,r4 LO0 (10.10.4.4) also declared to EIGRP 100 on R4 show ip eigrp neighbor can see two adjacency relationships

Use only one instruction to make EIGRP hello=5 hold between R2,r3,r4 time=15

The address of the R4 's Ethernet port is: 150.1.1.1/24, so that R4 and BB2 establish EIGRP adjacency, R4 will receive a lot of routes from BB2, including A,b,c class. With a minimal prefix command, only Class B routing is allowed to enter R4

The two-way redistribution of RIP and EIGRP on R2,R3 makes it invisible to R4 on any route of the 100.0.0.0 network segment. This solution cannot use Route-map or interface-based filtering, cannot pass metric methods, does not allow the use of distance, does not allow stubs

Extremely high security between the R2,R4

Add Lo1,ip address on R2 to 161.1.1.1/24, declaring it into EIGRP, at which point the R4 should only see three routes of the 161 segment: 161.1.0.0/16,161.1.0.0/18,161.1.0.0/20 three routes. Only 161.1.1.0/24 routes can be seen on the R1. make the appropriate configuration on the R2 only. Cannot use Route-map, interface-based filtering can be used

The LO0 of R3 is declared directly to EIGRP. Enables R4 to see two equivalent routes

Add a LO5 to the R3 with the address 5.5.5.5/32. Also announce to rip and EIGRP, configure on R3

Add a LO6 to the R3 with the address: 6.6.6.6/32 is also declared in Rip and EIGRP, so that R4 can see this route, the next hop points to R2, when the R2-R4 link is broken. R4 can reach this route through R3 and does not require a re-convergence, use distance 1XX to complete this task, and if you modify metric, you cannot use offset-list to not affect other routes

For the above question

What to do if you need to install two non-equivalent routes

What if a packet is required to use only the metric minimum route? No need to consider Route-map

R4 inject only one default route to BB2, do not inject routes to other routers, do not use any form of filtering, use the appropriate instructions to implement

Part 3---EIGRP 99

The PPP link between R4,R5 runs EIGRP 99. Use unicast to establish adjacency and put R5 's LO0 into the EIGRP process

Add a LO1 to the R5 with the address: 7.7.7.7/32 is the one that R4 sees as an external route 7.7.7.7/32[90/xxxxx]. R4 to R5 only to inject a default route, can not use Interface-summ also can not use distribute-list, can not use Route-map

The EIGRP 100 and EIGRP 99 are re-distributed in a bidirectional way on the R4. On R1 only one next hop to the 7.7.7.7/32 route to R2, if R2 unreachable, R1 can reach this route through R3. You can ping this route on the R1. Note that R2 and R3 can pass routes to each other, and this scenario may need to consider preventing routing loops, but not with offset-list, and cannot be modified on R1 distance

Cisco EIGRP Labs