Wednesday, March 23, 2011

Lab 63 - RIPv2 Split-Horizon

Prerequisites: CCNP level skills.

Topology

Pic. 1 - Topology Diagram.
Icons designed by: Andrzej Szoblik - http://www.newo.pl

Task1
Configure RIPv2 in the given topology (pic. 1). Ensure full reachability between all subnets. Make sure RIPv2 does not send updates out the Loopback interfaces.

Lab Solution

Task1
Configure RIPv2 in the given topology (pic. 1). Ensure full reachability between all subnets. Make sure RIPv2 does not send updates out the Loopback interfaces.

R1 Configuration:
!
router rip
 version 2
 passive-interface Loopback0
 network 10.0.0.0
 network 172.16.0.0
 no auto-summary
!


R2 Configuration:
!
router rip
 version 2
 passive-interface Loopback0
 network 10.0.0.0
 network 172.16.0.0
 no auto-summary
!


R3 Configuration:
!
router rip
 version 2
 passive-interface Loopback0

 network 10.0.0.0
 network 172.16.0.0
 no auto-summary
!


Verification:
Pic. 2 - R1's RIPv2 Details.

Pic. 3 - R2's Routing Table.
Notice!
R2 can reach subnets advertised by R3. RIP Split-Horizon is DISABLED on Frame-Relay link (R1 S0/0) by default. There is no need to configure that. The below line (highlighted) is only true for RIP, but not for EIGRP.

Pic. 4 - Split-Horizon on R1.

Notice!
Since the next hop towards 10.1.3.0/24 is: 10.1.0.3, there must be frame-relay mapping configured between the spokes.

R2 Frame-Relay Configuration:
!
interface Serial0/0
 ip address 10.1.0.2 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 10.1.0.1 201 broadcast
 frame-relay map ip 10.1.0.3 201
 no frame-relay inverse-arp
!


R3 Frame-Relay Configuration:
!
interface Serial0/0
 ip address 10.1.0.3 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 10.1.0.1 301 broadcast
 frame-relay map ip 10.1.0.2 301
 no frame-relay inverse-arp
!