Exploration 4: Escenario de Frame-Relay,
agregado de una nueva sucursal
Fecha: 14 de Mayo del 2011
(parte 1)
21 de Mayo del 2011 (parte 2)
Instructor: Ernesto Vilarrasa
Escenario original: en este escenario se demostraba que dos empresas pueden convivir en un ambiente FR
con los mismos
direccionamientos IP sin verse entre si (siempre y cuando el SW frame-relay
esté bien configurado).
Nos centraremos en la empresa B (en la parte inferior del escenario) y en Córdoba (el nodo principal)
Cordoba#sh running-config(configuración
original)
!
hostname Cordoba
!
interface FastEthernet0/0
ip address
10.0.0.1 255.255.255.0
!
interface Serial0/0/0
ip address 192.168.0.2
255.255.255.252
encapsulation frame-relay
!
router eigrp 100
network
10.0.0.0 0.0.0.255
network
192.168.0.0 0.0.0.3
no
auto-summary
!
ip classless
!
end
Nos centraremos en la actualización de Córdoba (casa central), ya que se le agregará una
nueva sucursal, tenemos dos opciones.
Escenario
modificado: (opción
1) es la menos elegante, ya que debemos disponer de dos enlaces seriales (más
costoso)
Para la
sucursal 2:
Para Córdoba:
Las interconectamos entre si:
Cordoba(config)#interface Serial0/0/1
Cordoba(config-if)#ip address 192.168.0.6 255.255.255.252
Cordoba(config-if)#enca frame-relay
Cordoba(config-if)# no shut
Cordoba(config-if)#exit
Cordoba(config)#router
eigrp 100 (debemos dar el alta de la sucursal en
el
Cordoba(config-router)#net
192.168.0.4 0.0.0.3 protocolo de enrutamiento)
Cordoba(config-router)#exit
%LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0/1, changed state to up
Cordoba(config-if)#^Z
Cordoba#
%DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor
192.168.0.5 (Serial0/0/1) is up: new adjacency
Cordoba#sh ip route
---resumido---
10.0.0.0/24 is subnetted, 3 subnets
C
10.0.0.0 is directly connected, FastEthernet0/0
D
10.0.1.0 [90/2172416] via 192.168.0.1, 00:02:22, Serial0/0/0
D
10.0.2.0 [90/2172416] via 192.168.0.5, 00:00:38, Serial0/0/1
192.168.0.0/30 is subnetted, 2 subnets
C
192.168.0.0 is directly connected, Serial0/0/0
C
192.168.0.4 is directly connected, Serial0/0/1
Cordoba#
Escenario modificado: (opción 2) es la más elegante, utilizamos sólo un enlace
serial (menos costoso)
Para ello, configuramos sub-interfaces tanto en el router
como en el SW frame-relay
Para
Córdoba: (sucursal
2 sigue igual)
Las
interconectamos entre si:
Cordoba#conf t (debemos dar el alta de la sucursal en el protocolo de
enrutamiento)
Enter configuration commands, one per line. End with CNTL/Z.
Cordoba(config)#router
eigrp 100
Cordoba(config-router)#net
192.168.0.4 0.0.0.3
Cordoba(config-router)#exit
Cordoba(config)#int
s0/0/0
Cordoba(config-if)#no
ip address
%DUAL-5-NBRCHANGE:
IP-EIGRP 100: Neighbor 192.168.0.1 (Serial0/0/0) is down: interface down
Cordoba(config-if)#exit
Cordoba(config)#int
s0/0/0.400 point-to-point
%LINK-5-CHANGED: Interface
Serial0/0/0.400, changed state to up
%LINEPROTO-5-UPDOWN: Line
protocol on Interface Serial0/0/0.400, changed state to up
Cordoba(config-subif)#ip
add 192.168.0.2 255.255.255.252
Cordoba(config-subif)#frame-relay
interface-dlci 400
Cordoba(config-subif)#no
shut
Cordoba(config-subif)#
%DUAL-5-NBRCHANGE:
IP-EIGRP 100: Neighbor 192.168.0.1 (Serial0/0/0.400) is up: new adjacency
Cordoba(config-subif)#exit
Cordoba(config)#int
s0/0/0.401 point-to-point
%LINK-5-CHANGED: Interface
Serial0/0/0.401, changed state to up
%LINEPROTO-5-UPDOWN: Line
protocol on Interface Serial0/0/0.401, changed state to up
Cordoba(config-subif)#frame-relay
interface-dlci 401
Cordoba(config-subif)#ip
add 192.168.0.6 255.255.255.252
Cordoba(config-subif)#^Z
Cordoba#
%SYS-5-CONFIG_I:
Configured from console by console
Cordoba#
%DUAL-5-NBRCHANGE:
IP-EIGRP 100: Neighbor 192.168.0.5 (Serial0/0/0.401) is up: new adjacency
Cordoba#
Verificamos
alcanzar la sucursal 2: (esta no aparecerá en la tabla de enrutamiento)
(no se mencionó antes para estudiar
primero FR, esto es secundario ya que es de CCNA2)
Cordoba#sh ip ro
---resumido---
10.0.0.0/8 is variably
subnetted, 3 subnets, 2 masks
D 10.0.0.0/8 [90/2172416] via
192.168.0.5, 00:00:05, Serial0/0/0.401
C 10.0.0.0/24 is directly connected,
FastEthernet0/0
D 10.0.1.0/24 [90/2172416] via
192.168.0.1, 00:00:30, Serial0/0/0.400
192.168.0.0/30 is subnetted, 2 subnets
C 192.168.0.0 is directly connected,
Serial0/0/0.400
C 192.168.0.4 is directly connected,
Serial0/0/0.401
Observamos
que Frame-Relay está OK:
Cordoba#sh frame-relay
map
Serial0/0/0.400 (up): point-to-point dlci, dlci 400, broadcast,
status defined, active
Serial0/0/0.401
(up): point-to-point dlci, dlci 401, broadcast, status defined, active
Cordoba#
Cordoba#
Buscamos
la falla en la sucursal 2:
B_Suc2#sh frame-relay
map
Serial0/0/0 (up): ip
192.168.0.6 dlci 100, dynamic, broadcast, CISCO, status defined, active
B_Suc2#sh frame-relay
pvc
PVC Statistics
for interface Serial0/0/0 (Frame Relay DTE)
DLCI = 100,
DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts
14055 output pkts 32795 in bytes 1096228
out bytes
6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts
0 out FECN pkts 0 out BECN pkts 0
in DE pkts
0 out DE pkts 0
out bcast pkts
32795 out bcast bytes 6216155
B_Suc2#sh ip route
---resumido---
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
ya que hay redes
discontiguas)
D 10.0.0.0/24 [90/2172416] via 192.168.0.6, 00:00:34, Serial0/0/0
D 10.0.1.0/24 [90/2684416] via
192.168.0.6, 00:00:34, Serial0/0/0
C 10.0.2.0/24 is directly connected, FastEthernet0/0
192.168.0.0/24 is variably subnetted, 3
subnets, 2 masks
D 192.168.0.0/24 is a
summary, 00:06:42, Null0
D 192.168.0.0/30 [90/2681856] via
192.168.0.6, 00:00:34, Serial0/0/0
C
192.168.0.4/30 is directly connected, Serial0/0/0
B_Suc2#
B_Suc2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
B_Suc2(config)#router
eigrp 100
B_Suc2(config-router)#no
auto-summary
B_Suc2(config-router)#
%DUAL-5-NBRCHANGE:
IP-EIGRP 100: Neighbor 192.168.0.6 (Serial0/0/0) is up: new adjacency
B_Suc2(config-router)#^Z
B_Suc2#
%SYS-5-CONFIG_I:
Configured from console by console
B_Suc2#
B_Suc2#sh ip route
---resumido---
10.0.0.0/24 is subnetted, 3 subnets(vemos
correctamente las tres redes)
D 10.0.0.0 [90/2172416] via 192.168.0.6, 00:00:08, Serial0/0/0
D 10.0.1.0 [90/2684416] via 192.168.0.6, 00:00:08, Serial0/0/0
C 10.0.2.0 is directly connected, FastEthernet0/0
192.168.0.0/30 is subnetted, 2 subnets
D 192.168.0.0 [90/2681856] via
192.168.0.6, 00:00:08, Serial0/0/0
C 192.168.0.4 is directly connected,
Serial0/0/0
B_Suc2#
Cordoba#sh ip ro
---resumido---
10.0.0.0/24 is subnetted, 3 subnets
C 10.0.0.0 is directly connected,
FastEthernet0/0
D 10.0.1.0 [90/2172416] via 192.168.0.1,
00:01:27, Serial0/0/0.400
D 10.0.2.0 [90/2172416]
via 192.168.0.5, 00:00:14, Serial0/0/0.401
192.168.0.0/30 is subnetted, 2 subnets
C 192.168.0.0 is directly connected,
Serial0/0/0.400
C 192.168.0.4 is directly connected,
Serial0/0/0.401
Cordoba#
B_Suc2#sh
running-config
!
hostname B_Suc2
!
interface FastEthernet0/0
ip address 10.0.2.1 255.255.255.0
!
interface Serial0/0/0
ip address 192.168.0.5 255.255.255.252
encapsulation frame-relay
!
router eigrp 100
network 10.0.2.0 0.0.0.255
network 192.168.0.4 0.0.0.3
no auto-summary
!
ip classless
!
end
Rosario#sh runn
!
hostname Rosario
!
interface FastEthernet0/0
ip address 10.0.1.1 255.255.255.0
!
interface Serial0/0/0
ip address 192.168.0.1 255.255.255.252
encapsulation frame-relay
!
router eigrp 100
network 10.0.1.0 0.0.0.255
network 192.168.0.0 0.0.0.3
no auto-summary
!
ip classless
!
end
Cordoba#sh
running-config
!
hostname Cordoba
!
interface FastEthernet0/0
ip address 10.0.0.1 255.255.255.0
!
interface Serial0/0/0
no ip address (fundamental)
encapsulation frame-relay (fundamental)
!
interface Serial0/0/0.400 point-to-point
ip address 192.168.0.2 255.255.255.252
frame-relay interface-dlci 400 (fundamental,
ya que debemos definir cual DLCI
! corresponde a cada IP para el ARP inverso)
interface Serial0/0/0.401 point-to-point
ip address 192.168.0.6 255.255.255.252
frame-relay interface-dlci 401
!
router eigrp 100
network 10.0.0.0 0.0.0.255
network 192.168.0.0 0.0.0.3
network 192.168.0.4 0.0.0.3
no auto-summary (fundamental)
!
ip classless
!
end
Configuración multipoint: en esta topología, la nube FR pertenece a la misma red 192.168.0.0 /29
(antes 192.168.0.0 /30 y 192.168.0.4 /30) también por una cuestión de Packet Tracer deberemos migrar
a OSPF
por problemas de horizonte dividido:
Cordoba#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Cordoba(config)#no interface Serial0/0/0.401 point-to-point
Cordoba(config)#no interface Serial0/0/0.400 point-to-point
Cordoba(config)#
Configuramos:
!
interface Serial0/0/0.400 multipoint
ip address 192.168.0.1 255.255.255.248 (cambiamos
IP y máscara)
frame-relay map ip 192.168.0.2 400 broadcast (mapa FR estático, ya que
frame-relay map ip 192.168.0.3
401 broadcast debemos definir a cual IP
exit llegamos
por cada DLCI)
!
router eigrp 100 (igual para todos los
routers, según corresponda)
no net 192.168.0.0 0.0.0.3
no net 192.168.0.4 0.0.0.3
net 192.168.0.0 0.0.0.7
exit
Cordoba#sh ip route (aparecen todas las
redes)
---resumido---
10.0.0.0/24 is subnetted, 3
subnets
C 10.0.0.0 is directly
connected, FastEthernet0/0
D 10.0.1.0 [90/2172416]
via 192.168.0.2, 00:03:41, Serial0/0/0.400
D 10.0.2.0 [90/2172416]
via 192.168.0.3, 00:01:10, Serial0/0/0.400
192.168.0.0/29 is
subnetted, 1 subnets
C 192.168.0.0 is directly
connected, Serial0/0/0.400
Cordoba#
Rosario#sh ip route (10.0.2.0/24 no
aparece)
---resumido---
10.0.0.0/24 is subnetted, 2
subnets
D 10.0.0.0 [90/2172416]
via 192.168.0.1, 00:00:16, Serial0/0/0
C 10.0.1.0 is directly
connected, FastEthernet0/0
192.168.0.0/29 is
subnetted, 1 subnets
C 192.168.0.0 is directly
connected, Serial0/0/0
Rosario#
B_Suc2#sh ip route (10.0.1.0/24 no
aparece)
---resumido---
10.0.0.0/24 is subnetted, 2
subnets
D 10.0.0.0 [90/2172416]
via 192.168.0.1, 00:00:05, Serial0/0/0
C 10.0.2.0 is directly
connected, FastEthernet0/0
192.168.0.0/29 is
subnetted, 1 subnets
C 192.168.0.0 is directly
connected, Serial0/0/0
B_Suc2#
Cordoba(config)#int s0/0/0 (también
probamos con...)
Cordoba(config-if)#no ip split-horizon (...y
con...)
Cordoba(config-if)#no ip split-horizon eigrp 100 (...y con...)
Cordoba(config-if)#no ip split-horizon verdura (...packet tracer...)
Migramos
a OSPF: para mitigar este problema...
Córdoba:
!
interface Serial0/0/0.400 multipoint
ip ospf network broadcast
exit
no router eigrp 100
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.0.7 area 0
network 10.0.0.0 0.0.0.255 area 0
!
Rosario:
!
interface Serial0/0/0
ip address 192.168.0.2 255.255.255.248
encapsulation frame-relay
ip ospf network broadcast
!
no router eigrp 100
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.0.7 area 0
network 10.0.1.0 0.0.0.255 area 0
Suc 2:
!
interface Serial0/0/0
ip address 192.168.0.3 255.255.255.248
encapsulation frame-relay
ip ospf network broadcast
!
no router eigrp 100
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.0.7 area 0
network 10.0.2.0 0.0.0.255 area 0
Cordoba#sh ip route
---resumido---
10.0.0.0/24 is subnetted, 3 subnets
C 10.0.0.0 is
directly connected, FastEthernet0/0
O 10.0.1.0
[110/65] via 192.168.0.2, 00:02:09, Serial0/0/0.400
O 10.0.2.0
[110/65] via 192.168.0.3, 00:02:59, Serial0/0/0.400
192.168.0.0/29 is subnetted, 1 subnets
C 192.168.0.0 is directly connected,
Serial0/0/0.400
Cordoba#
Rosario#sh ip route
---resumido---
10.0.0.0/24 is subnetted, 3 subnets
O 10.0.0.0 [110/65] via 192.168.0.1,
00:03:06, Serial0/0/0
C 10.0.1.0 is directly connected,
FastEthernet0/0
O 10.0.2.0 [110/65] via 192.168.0.3,
00:03:06, Serial0/0/0
192.168.0.0/29 is subnetted, 1 subnets
C 192.168.0.0 is directly connected,
Serial0/0/0
Rosario#
B_Suc2#sh ip route
---resumido---
10.0.0.0/24 is subnetted, 3 subnets
O 10.0.0.0 [110/65] via 192.168.0.1,
00:04:48, Serial0/0/0
O 10.0.1.0 [110/65] via 192.168.0.2,
00:03:58, Serial0/0/0
C 10.0.2.0 is directly connected,
FastEthernet0/0
192.168.0.0/29 is subnetted, 1 subnets
C 192.168.0.0 is directly connected,
Serial0/0/0
B_Suc2#
(2011) Speak about frame relay may scare the pretty girls
Rosario, Argentina