Laboratorio de enrutamiento con RIP
versión 1 y 2:
Clase de CCNA 2 del 31 de Octubre del 2009,
academia Cisco, Rosario
Instructor: Ernesto Vilarrasa
Escenario/ Topología:
Este escenario es el propuesto por el capítulo
7 (enrutamiento RIPv2) de Exploration 2 con algunas pequeñas variantes,
en las cuales fallan las rutas
remotas debido a que son discontínuas, además de jugar en contra la
sumarización, sólo siendo
posible deshabilitarlas en versión
2 de RIP.
Diagrama
en pizarrón
( No se registraron imágenes )
Diagrama
en Packet Tracer ( layout decente ) Errata: 172.30.300.1 /24 es obviamente un error,
Loop3 en Tucumán NO se implementó.
Desarrollo:
Las interfaces locales se configuraron en Fast 0/0 (Rosario) y Loopback 1 a 4 ( sucursales )
Las interfaces serial se configuraron como S0/0/0 ( sucursales ), S0/0/0 y S0/0/1 como DTE ( Rosario )
( Por cuestiones
prácticas sólo mostraremos las tablas de rutas )
Rosario:
Rosario#sh ip route
....
10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0
is directly connected, FastEthernet0/0
R
172.30.0.0/16 [120/1]
via 200.69.216.10, 00:00:00, Serial0/0/0 (
Ve las rutas destino 172.30.X.X
[120/1] via 200.69.216.6, 00:00:13, Serial0/0/1 tanto de Córdoba
como Tucumán por
200.69.216.0/30
is subnetted, 2 subnets igual, ya que ambas son un resumen )
C
200.69.216.4 is directly connected, Serial0/0/1
C
200.69.216.8 is directly connected, Serial0/0/0
Rosario#
Sucursal Cordoba:
Cordoba#sh ip route
...
R 10.0.0.0/8
[120/1] via 200.69.216.5, 00:00:14, Serial0/0/0
172.30.0.0/24
is subnetted, 4 subnets ( No aparecen las subredes
100, 200 de Tucumán )
C
172.30.1.0 is directly connected, Loopback1
C
172.30.2.0 is directly connected, Loopback2
C
172.30.3.0 is directly connected, Loopback3
C
172.30.4.0 is directly connected, Loopback4
200.69.216.0/30 is subnetted, 2 subnets
C
200.69.216.4 is directly connected, Serial0/0/0
R 200.69.216.8 [120/1] via 200.69.216.5,
00:00:14, Serial0/0/0
Cordoba#
Sucursal Tucumán:
Tucuman>sh ip route
....
R 10.0.0.0/8
[120/1] via 200.69.216.9, 00:00:11, Serial0/0/0
172.30.0.0/24 is subnetted, 2 subnets ( No aparecen
las rutas 1, 2, 3 y 4 de Córdoba )
C
172.30.100.0 is directly connected, Loopback1
C
172.30.200.0 is directly connected, Loopback2
200.69.216.0/30 is subnetted, 2 subnets
R
200.69.216.4 [120/1] via 200.69.216.9, 00:00:11, Serial0/0/0
C
200.69.216.8 is directly connected, Serial0/0/0
Tucuman>
Prueba
de conectividad desde PC en Rosario:
PC>ping 172.30.100.1 -n 100
Pinging 172.30.100.1 with 32 bytes of data:
Reply from 172.30.100.1: bytes=32 time=63ms
TTL=254 (
paquete sale por interfaz S 0/0/0 ( OK )
Reply from 200.69.216.6: Destination host
unreachable. ( paquete
sale por interfaz S 0/0/1
Reply from 172.30.100.1: bytes=32 time=47ms
TTL=254 debido
al resumen enviado por
Reply from 200.69.216.6: Destination host
unreachable. routers en Córdoba y Tucumán )
Reply from 172.30.100.1: bytes=32 time=63ms TTL=254
Reply from 200.69.216.6: Destination host
unreachable.
Reply from 172.30.100.1: bytes=32 time=47ms TTL=254
Reply from 200.69.216.6: Destination host unreachable.
Reply from 172.30.100.1: bytes=32 time=62ms TTL=254
Migración a RIP versión 2:
Obs:
la migración a versión
2 debe realizarse en TODOS los routers, de lo contrario
aparecerá el siguiente error en los equipos con
versión 2 recibiendo actualizaciones versión 1
Rosario#debug ip rip
RIP protocol debugging is on
Rosario#RIP: received v2 update from 200.69.216.6 on
Serial0/0/1
172.30.0.0/16 via 0.0.0.0 in 1 hops
RIP:
ignored v1 packet from 200.69.216.10 (illegal version) (
router que aún NO ha sido migrado )
RIP: sending
v2 update to 224.0.0.9 via FastEthernet0/0 (10.0.0.1)
RIP: build update entries
172.30.0.0/16 via 0.0.0.0, metric 2, tag
Para realizar el cambio de versión:
Tucuman#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Tucuman(config)#router rip
Tucuman(config-router)#version 2
Tucuman(config-router)#^Z
Verificación:
Rosario#sh ip prot
Routing Protocol is "rip"
.....
Default version control: send version 2, receive 2
Interface Send
Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Serial0/0/1 2 2
Serial0/0/0 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
200.69.216.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
200.69.216.6 120 00:00:05
200.69.216.10 120 00:00:05
Distance: (default is 120)
Rosario#
Rosario#sh ip ro
....
10.0.0.0/24 is subnetted, 1 subnets
C
10.0.0.0 is directly connected, FastEthernet0/0
R
172.30.0.0/16 [120/1]
via 200.69.216.6, 00:00:21, Serial0/0/1 ( RIP v2 no cambia el efecto del
resumen
[120/1] via 200.69.216.10, 00:00:00, Serial0/0/0 pero SI
permite deshabilitarlo )
200.69.216.0/30 is subnetted, 2 subnets
C
200.69.216.4 is directly connected, Serial0/0/1
C
200.69.216.8 is directly connected, Serial0/0/0
Rosario#
Modificación del autoresumen: ( sólo válido para RIP v2 , debe ser aplicado a todos los routers
del escenario )
Rosario(config)#router rip
Rosario(config-router)#no aut
Rosario(config-router)#no auto-summary
Rosario(config-router)#^Z
Tucuman(config)#router rip
Tucuman(config-router)#no auto
Tucuman(config-router)#no auto-summary
Tucuman(config-router)#^Z
Tucuman#
Cordoba(config)#router rip
Cordoba(config-router)#no auto
Cordoba(config-router)#no auto-summary
Cordoba(config-router)#^Z
Cordoba#
Cordoba#sh ip prot
.....
Automatic network summarization is not in
effect
.......
Cordoba# show ip route
.....
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
R
10.0.0.0/8 is possibly down, routing via 200.69.216.5,
Serial0/0/0 ( Se purgarán después del
R 10.0.0.0/24 [120/1] via 200.69.216.5, 00:00:17, Serial0/0/0 tiempo de
Flush 240 segundos ó
172.30.0.0/24
is subnetted, 6 subnets con el comando clear ip route * )
C
172.30.1.0 is directly connected, Loopback1
C
172.30.2.0 is directly connected, Loopback2
C 172.30.3.0
is directly connected, Loopback3
C
172.30.4.0 is directly connected, Loopback4
R
172.30.100.0
[120/2] via 200.69.216.5, 00:00:17, Serial0/0/0 (
se observan TODAS las rutas 172.30.X.X )
R
172.30.200.0
[120/2] via 200.69.216.5, 00:00:17, Serial0/0/0
200.69.216.0/30 is subnetted, 2 subnets
C
200.69.216.4 is directly connected, Serial0/0/0
R
200.69.216.8 [120/1] via 200.69.216.5, 00:00:17, Serial0/0/0
Cordoba#
Rosario# show ip route
.......
10.0.0.0/24 is subnetted, 1 subnets
C
10.0.0.0 is directly connected, FastEthernet0/0
172.30.0.0/16 is variably subnetted, 7 subnets, 2 masks
R
172.30.0.0/16 is possibly down, routing via 200.69.216.6,
Serial0/0/1 ( Se purgarán después del
is possibly down,
routing via 200.69.216.10, Serial0/0/0 tiempo de Flush 240 segundos )
R
172.30.1.0/24
[120/1] via 200.69.216.6, 00:00:01, Serial0/0/1
R
172.30.2.0/24
[120/1] via 200.69.216.6, 00:00:01, Serial0/0/1 ( se observan TODAS las rutas
172.30.X.X )
R
172.30.3.0/24
[120/1] via 200.69.216.6, 00:00:01, Serial0/0/1
R
172.30.4.0/24
[120/1] via 200.69.216.6, 00:00:01, Serial0/0/1
R
172.30.100.0/24
[120/1] via 200.69.216.10, 00:00:26, Serial0/0/0
R
172.30.200.0/24
[120/1] via 200.69.216.10, 00:00:26, Serial0/0/0
C
192.168.100.1 is directly connected, Loopback0
200.69.216.0/30 is subnetted, 2 subnets
C
200.69.216.4 is directly connected, Serial0/0/1
C 200.69.216.8
is directly connected, Serial0/0/0
Rosario#
Tucuman#sh ip ro
.....
10.0.0.0/24 is subnetted, 1 subnets
R
10.0.0.0 [120/1] via 200.69.216.9, 00:00:04, Serial0/0/0
172.30.0.0/24 is subnetted, 6 subnets
R
172.30.1.0
[120/2] via 200.69.216.9, 00:00:04, Serial0/0/0 (
se observan TODAS las rutas 172.30.X.X )
R
172.30.2.0
[120/2] via 200.69.216.9, 00:00:04, Serial0/0/0
R
172.30.3.0
[120/2] via 200.69.216.9, 00:00:04, Serial0/0/0
R
172.30.4.0 [120/2]
via 200.69.216.9, 00:00:04, Serial0/0/0
C
172.30.100.0 is directly connected, Loopback1
C
172.30.200.0 is directly connected, Loopback2
200.69.216.0/30 is subnetted, 2 subnets
R
200.69.216.4 [120/1] via 200.69.216.9, 00:00:04, Serial0/0/0
C
200.69.216.8 is directly connected, Serial0/0/0
Tucuman#
PC>ping 172.30.100.1
Pinging 172.30.100.1 with 32 bytes of data:
Reply from 172.30.100.1: bytes=32 time=62ms TTL=254
Reply from 172.30.100.1: bytes=32 time=47ms TTL=254
Reply from 172.30.100.1: bytes=32 time=62ms TTL=254
Reply from 172.30.100.1: bytes=32 time=63ms TTL=254
__________________________________________________________________
Ernesto Vilarrasa evilarrasa@centroit.org.ar www.vilarrasa.com.ar
(2010) Crazy tales for sleep from uncle Ernest
Rosario, Argentina