Problemas de configuración de RIPv2

1. En packet tracer, montar el siguiente esquema de red.

 1. Configurar RIPv2 y mostrar las tablas de enrutamiento de los routers
con show ip routers

ROUTER1:
R1#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 21 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.30.0.0
Passive Interface(s):
GigabitEthernet0/1
Routing Information Sources:
Gateway Distance Last Update
10.1.1.2 120 00:00:15
Distance: (default is 120)
R1#

R1#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks

C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.1/32 is directly connected, Serial0/0/0
R 10.2.2.0/30 [120/1] via 10.1.1.2, 00:00:22, Serial0/0/0
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.30.10.0/24 is directly connected, GigabitEthernet0/1
L 172.30.10.1/32 is directly connected, GigabitEthernet0/1
R 209.165.201.0/24 [120/1] via 10.1.1.2, 00:00:22, Serial0/0/0

R1#

ROUTER2:
R2#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 16 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 2 2
Serial0/0/1 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
209.165.201.0
Passive Interface(s):
GigabitEthernet0/0
Routing Information Sources:
Gateway Distance Last Update
10.2.2.1 120 00:00:03
10.1.1.1 120 00:00:25
Distance: (default is 120)
R2#
R2# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks

C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.2/32 is directly connected, Serial0/0/0
C 10.2.2.0/30 is directly connected, Serial0/0/1
L 10.2.2.2/32 is directly connected, Serial0/0/1
R 172.30.0.0/16 [120/1] via 10.2.2.1, 00:00:16, Serial0/0/1
[120/1] via 10.1.1.1, 00:00:12, Serial0/0/0
209.165.201.0/24 is variably subnetted, 2 subnets, 2 masks
C 209.165.201.0/24 is directly connected, GigabitEthernet0/0
L 209.165.201.1/32 is directly connected, GigabitEthernet0/0

R2#

ROUTER3:
R3#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 17 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/1 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.30.0.0
Passive Interface(s):
GigabitEthernet0/1
Routing Information Sources:
Gateway Distance Last Update
10.2.2.2 120 00:00:26
Distance: (default is 120)
R3#
R3#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 3 subnets, 3 masks

R 10.1.1.0/30 [120/1] via 10.2.2.2, 00:00:05, Serial0/0/1
C 10.2.2.0/24 is directly connected, Serial0/0/1
L 10.2.2.1/32 is directly connected, Serial0/0/1
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.30.30.0/24 is directly connected, GigabitEthernet0/1
L 172.30.30.1/32 is directly connected, GigabitEthernet0/1
R 209.165.201.0/24 [120/1] via 10.2.2.2, 00:00:05, Serial0/0/1

R3#

2. ¿Identificas algún posible problema en las tablas de los routers mostradas

en el ejercicio 1? ¿A qué se debe ese problema?

SI, hay rutas iguales que posee balanceo de carga

3. Puedes hacer ping entre el PC-A y el PC-B. Muéstralo

C:\>ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Reply from 209.165.201.2: bytes=32 time=1ms TTL=126

Request timed out.
Reply from 209.165.201.2: bytes=32 time=1ms TTL=126
Request timed out.

Ping statistics for 209.165.201.2:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Sobre los pings he de destacar que si incluía la red 209.165.201.0 dentro del RIPV2
de R2 solo perdia la mitad de los paquetes y por el contrario si no lo añado pierde
todos los paquetes.
 4. Puedes hacer ping entre el PC-B y el PC-C. Muéstralo

C:\>ping 172.30.30.3

Pinging 172.30.30.3 with 32 bytes of data:

Reply from 10.1.1.1: Destination host unreachable.

Reply from 172.30.30.3: bytes=32 time=3ms TTL=126
Reply from 10.1.1.1: Destination host unreachable.
Reply from 172.30.30.3: bytes=32 time=4ms TTL=126

Ping statistics for 172.30.30.3:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 7ms

C:\>

Sobre los pings he de destacar que si incluía la red 209.165.201.0 dentro del RIPV2
de R2 solo perdia la mitad de los paquetes y por el contrario si no lo añado pierde
todos los paquetes.

5. Puedes hacer ping entre el PC-A y el PC-C. ¿Qué ocurre?

C:\>ping 172.30.30.3

Pinging 172.30.30.3 with 32 bytes of data:

Request timed out.

Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.30.30.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>
 6. Puedes explicar que ocurre en la tabla de routers del router 2

Ocurre lo siguiente:
R2#debug ip rip
RIP protocol debugging is on
R2#RIP: received v2 update from 10.2.2.1 on Serial0/0/1
172.30.0.0/16 via 0.0.0.0 in 1 hops
RIP: received v2 update from 10.1.1.1 on Serial0/0/0
172.30.0.0/16 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (10.1.1.2)
RIP: build update entries
10.2.2.0/30 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/1 (10.2.2.2)
RIP: build update entries
10.1.1.0/30 via 0.0.0.0, metric 1, tag 0

7. ¿Qué router o qué routers hace el resumen automático de rutas y crean a

superred?

Los 3 routers hacen el resumen automático

a. ¿por qué lo hace?

Lo hacen para reducir el numero de redes en la tabla de enrutamiento que nos

muestra

8. En los router R1 y R3 desactiva el resumen automático de rutas y por tanto la

creación automática de superredes.

Router Rip

no auto-summary

- Muestra ahora la tabla del router R1. ¿Ves algún cambio? ¿puedes hacer ping
desde el pc-A al pc-C. ¿por qué?
CONFIGURACIÓN ROUTER1:

R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#exit
R1(config)#end
R1#
%SYS-5-CONFIG_I: Configured from console by console

R1#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks

C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.1/32 is directly connected, Serial0/0/0
R 10.2.2.0/30 [120/1] via 10.1.1.2, 00:00:03, Serial0/0/0
172.30.0.0/16 is variably subnetted, 4 subnets, 3 masks
R 172.30.0.0/16 [120/2] via 10.1.1.2, 00:00:03, Serial0/0/0
C 172.30.10.0/24 is directly connected, GigabitEthernet0/1
L 172.30.10.1/32 is directly connected, GigabitEthernet0/1
R 172.30.30.0/24 [120/2] via 10.1.1.2, 00:02:59, Serial0/0/0

R1#
HAGO PING:
C:\>ping 172.30.30.3

Pinging 172.30.30.3 with 32 bytes of data:

Reply from 172.30.30.3: bytes=32 time=2ms TTL=125

Reply from 172.30.30.3: bytes=32 time=5ms TTL=125
Reply from 172.30.30.3: bytes=32 time=2ms TTL=125
Reply from 172.30.30.3: bytes=32 time=2ms TTL=125

Ping statistics for 172.30.30.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 5ms, Average = 2ms
 C:\>
Hemos quitado el resumen de redes y ahora los paquetes pueden detectar por donde
pasar.

9. Vuelve a realizar el ejercicio, pero usando el protocolo de enrutamiento

dinámico OSPF. Configuración OSPF (página 29- primer cuadro). Con OSPF,
comprueba que el sistema sale correcto, es decir, la tabla del R1.

ROUTER1:
R1# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks

C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.1/32 is directly connected, Serial0/0/0
O 10.2.2.0/30 [110/128] via 10.1.1.2, 00:13:48, Serial0/0/0
172.30.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.30.10.0/24 is directly connected, GigabitEthernet0/1
L 172.30.10.1/32 is directly connected, GigabitEthernet0/1
O 172.30.30.0/24 [110/129] via 10.1.1.2, 00:08:08, Serial0/0/0
O 209.165.201.0/24 [110/65] via 10.1.1.2, 00:10:42, Serial0/0/0

R1#COMPROBACIÓN:
R1#show ip protocols

Routing Protocol is "ospf 1"

Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 172.30.10.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
172.30.10.0 0.0.0.255 area 0
10.1.1.0 0.0.0.3 area 0
Routing Information Sources:
Gateway Distance Last Update
172.30.10.1 110 00:11:39
172.30.30.1 110 00:06:00
209.165.201.1 110 00:06:56
Distance: (default is 110)

R1#
OTRO:
!
router ospf 1
log-adjacency-changes
network 172.30.10.0 0.0.0.255 area 0
network 10.1.1.0 0.0.0.3 area 0
!

ADEMAS:
C:\>ping 172.30.30.3

Pinging 172.30.30.3 with 32 bytes of data:

Reply from 172.30.30.3: bytes=32 time=2ms TTL=125

Reply from 172.30.30.3: bytes=32 time=6ms TTL=125
Reply from 172.30.30.3: bytes=32 time=5ms TTL=125
Reply from 172.30.30.3: bytes=32 time=2ms TTL=125

Ping statistics for 172.30.30.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 6ms, Average = 3ms

C:\>