Laboratorio de enrutamiento con RIP
versión 1:
Clase de CCNA 2 del 30 de Abril del 2009,
academia Cisco, Rosario
Instructor: Ernesto Vilarrasa
Escenario/ Topología:
Este escenario es el propuesto por el capítulo
5 (enrutamiento RIPv1) de Exploration 2,
sección 5.4.1, con algunas variantes,
para darle un enfoque mas cercano a un caso real.
Diagrma
original
Diagrama
en pizarrón
Diagrama
en Packet Tracer ( layout decente )
Desarrollo:
Se configuraron dos routers Cisco 1800 como Cordoba y BsAs, un router 2501 como Rosario.
Entre Rosario y BsAs se configuraron S1 y S0/0/0 y Rosario y Cordoba las S0 y S0/0/0
Las interfaces locales se configuraron en Eth0 (2501) y Fa0/0 (1800)
Rosario:
Rosario#sh run
!
hostname Rosario
!
interface Ethernet0
ip address 172.30.3.1
255.255.255.0
no ip
directed-broadcast
!
interface Serial0
ip address 172.30.2.2
255.255.255.0
!
interface Serial1
ip address 192.168.4.9
255.255.255.252
!
router rip
network
172.30.0.0
network
192.168.4.0
!
Sucursal BsAs:
BSAS#sh run
!
hostname BSAS
!
interface FastEthernet0/0
ip address 192.168.5.1
255.255.255.0
!
interface Serial0/0/0
ip address 192.168.4.10
255.255.255.0
clockrate
64000
!
router rip
passive-interface FastEthernet0/0
network
192.168.4.0
network
192.168.5.0
!
Sucursal Cordoba:
cordoba#sh run
Building configuration...
!
hostname cordoba
!
interface FastEthernet0/0
ip address 172.30.1.1
255.255.255.0
!
interface Serial0/0/0
ip address 172.30.2.1
255.255.255.0
clockrate
64000
!
router rip
network
172.30.0.0
!
Verificación:
cordoba#sh ip route
...
Gateway of last resort is not set
172.30.0.0/16 is subnetted, 2 subnets
C
172.30.2.0/24 is directly connected, Serial0/0/0
C
172.30.1.0/24 is directly connected, FastEthernet0/0
R
192.168.4.0/24
[120/1] via 172.30.2.2, 00:00:19, Serial0/0/0
R 192.168.5.0/24 [120/2]
via 172.30.2.2, 00:00:19, Serial0/0/0
cordoba#
Rosario#sh ip route
...
Gateway of last resort is not set
172.30.0.0/16 is subnetted, 2 subnets
C
172.30.2.0 is directly connected, Serial0
R
172.30.1.0
[120/1] via 172.30.2.1, 00:02:37, Serial0
192.168.4.0/30
is subnetted, 1 subnets
C
192.168.4.8 is directly connected, Serial1
R
192.168.5.0/24
[120/1] via 192.168.4.10, 00:00:20, Serial1
Rosario#
BSAS#sh ip route
...
Gateway of last resort is not set
R
172.30.0.0/16 [120/1]
via 192.168.4.9, 00:00:06, Serial0/0/0
192.168.4.0/30 is subnetted, 1 subnets
C
192.168.4.8 is directly connected, Serial0/0/0
C
192.168.5.0/24 is directly connected, FastEthernet0/0
BSAS#
Conclusión: Se observa que RIPv1 es un protocolo con
clase, o sea respeta la máscara por defecto.
Pero si trabajamos con subredes, deberán tener TODAS
las mismas máscaras, en este caso /24 ya
que NO soporta VLSM.
En el resumen de rutas, se observa que la
máscara es /16 o sea, la original de una clase B
Observacion: las redes 192.168.4.0 y 5.0 son distintas
redes, no subredes, por lo que esto no es afectado.
MODIFICACION DEL ESCEMARIO A VLSM
El enlace Córdoba-Rosario se modificó a /30 ( dos hosts, un enlace Pto a Pto típico )
Córdoba:
!
interface Serial0/0/0
ip address 192.168.4.10 255.255.255.252
clockrate
64000
!
cordoba#sh ip route
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
C
172.30.2.0/30 is directly connected, Serial0/0/0
C
172.30.1.0/24 is directly connected, FastEthernet0/0
R
192.168.4.0/24 [120/1] via 172.30.2.2, 00:00:19, Serial0/0/0
R
192.168.5.0/24 [120/2] via 172.30.2.2, 00:00:19, Serial0/0/0
cordoba#
Rosario:
!
interface Serial0
ip address 172.30.2.2
255.255.255.252
no ip
directed-broadcast
no ip
mroute-cache
!
Rosario#sh ip route
172.30.0.0/30
is subnetted, 2 subnets
C
172.30.2.0 is directly connected, Serial0
R
172.30.1.0 [120/1] via 172.30.2.1, 00:02:37, Serial0
192.168.4.0/30 is subnetted, 1 subnets
C 192.168.4.8 is directly connected, Serial1
R
192.168.5.0/24 [120/1] via 192.168.4.10, 00:00:20, Serial1
Rosario#
VERIFICACION:
Desde BsAs se verificaca conectividad de extremo a extremo a Córdoba:
BSAS#ping 172.30.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout
is 2 seconds:
U.U.U
Success
rate is 0 percent (0/5)
Se realiza un rollback ( vuelta atrás en la
configuración ) que sirve de contraprueba:
En Córdoba:
cordoba#conf t
Enter configuration commands, one per line. End with CNTL/Z.
cordoba(config)#int s0/0/0
cordoba(config-if)#ip address 172.16.30.2.1 255.255.255.0
cordoba(config-if)#^Z
cordoba#
*May 2
09:16:30.823: %SYS-5-CONFIG_I: Configured from console by console
cordoba#
ANTES:
172.30.0.0/16
is variably subnetted, 2 subnets, 2 masks
C
172.30.2.0/30 is directly connected, Serial0/0/0
C
172.30.1.0/24 is directly connected, FastEthernet0/0
DESPUES:
172.30.0.0/24 is subnetted, 2 subnets
C
172.30.2.0 is directly connected, Serial0/0/0
C
172.30.1.0 is directly connected, FastEthernet0/0
En Rosario:
Rosario#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rosario(config)#int s0
Rosario(config-if)#ip address 172.30.2.2 255.255.255.0
Rosario(config-if)#^Z
Rosario#
09:17:29: %SYS-5-CONFIG_I: Configured from console by
console
BSAS#ping 172.30.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout
is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
BSAS#ping 172.30.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
BSAS#
Este escenario luego se modificó y adaptó el 2 de Mayo
a OSPF y encap-
sulación PPP para CCNA 4, disponible en http://www.vilarrasa.com.ar/lab_ppp.htm
__________________________________________________________________
Ernesto Vilarrasa evilarrasa@centroit.org.ar www.vilarrasa.com.ar