Frram Rela

CCNA Lab – Frame Relay en Routers Cisco en topología hub-and-spoke

Posted in cisco, Networking, Sistemas, Utilidades, virtualización on Nov 2nd, 2010

Fuente: Cisco Networking Academia – Supplemental Activities for CCNA – Configuring Frame-

Relay

ConfiguringFrameRelay.zip : ConfiguringFrameRelay

CCNA Lab – Frame Relay en Routers Cisco en topología hub-and-spoke

Escenario:

1

http://www.javcasta.com/blog/wp-content/uploads/2010/11/ConfiguringFrameRelay.zip

http://www.javcasta.com/category/virtualizacion/

http://www.javcasta.com/category/utilidades/

http://www.javcasta.com/category/sistemas/

http://www.javcasta.com/category/networking/

http://www.javcasta.com/category/cisco/

http://www.javcasta.com/2010/11/02/ccna-lab-frame-relay-en-routers-cisco-en-topologia-hub-and-spoke/


http://www.javcasta.com/blog/wp-content/uploads/2010/11/frame-relay-1.jpg

Una topología en estrella tipo Hub-and-Spoke

Un FR hub router R1

Un Switch Frame Relay

Tres FR spoke routers R2,R3,R4

Configurando la interfaz física Frame Relay en Router R1?123

R1(config)# interface serial0/0/0R1(config-if)# encapsulation frame-relayR1(config-if)# no shutdown

Configurando las subinterfaces en R1?123456789101112

R1(config)# interface Serial0/0/0.102 point-to-pointR1(config-subif)# ip address 10.0.1.1 255.255.255.252R1(config-subif)# frame-relay interface-dlci 102R1(config-subif)# exitR1(config)# interface Serial0/0/0.103 point-to-pointR1(config-subif)# ip address 10.0.1.5 255.255.255.252R1(config-subif)# frame-relay interface-dlci 103R1(config-subif)# exitR1(config)# interface Serial0/0/0.104 point-to-pointR1(config-subif)# ip address 10.0.1.9 255.255.255.252R1(config-subif)# frame-relay interface-dlci 104R1(config-subif)# exit

Configurando enrutamiento estático en R1 para alcanzar las LANs de cada router spoken?123

R1(config)# ip route 10.20.20.0 255.255.255.0 10.0.1.2R1(config)# ip route 10.30.30.0 255.255.255.0 10.0.1.6R1(config)# ip route 10.40.40.0 255.255.255.0 10.0.1.10

Configurar enrutamiento e interfaces FR en los router Spoke

Configurar el interfaz físico Frame Relay en los router spoke?123

R2(config)# interface serial0/0/0R2(config-if)# encapsulation frame-relayR2(config-if)# no shutdown

2





Configurar el subinterfaz en R2?1234

R2(config)# interface Serial0/0/0.101 point-to-pointR2(config-subif)# ip address 10.0.1.2 255.255.255.252R2(config-subif)# frame-relay interface-dlci 101R2(config-subif)# exit

Configurando ruta por defecto en R2?1 R2(config)# ip route 0.0.0.0 0.0.0.0 10.0.1.1

Se repiten los pasos de R2 en R3 y R4?12345678

R3(config)# interface serial0/0/0R3(config-if)# encapsulation frame-relayR3(config-if)# no shutdownR3(config)# interface Serial0/0/0.101 point-to-pointR3(config-subif)# ip address 10.0.1.6 255.255.255.252R3(config-subif)# frame-relay interface-dlci 101R3(config-subif)# exitR3(config)# ip route 0.0.0.0 0.0.0.0 10.0.1.5

?12345678

R4(config)# interface serial0/0/0R4(config-if)# encapsulation frame-relayR4(config-if)# no shutdownR4(config)# interface Serial0/0/0.101 point-to-pointR4(config-subif)# ip address 10.0.1.10 255.255.255.252R4(config-subif)# frame-relay interface-dlci 101R4(config-subif)# exitR4(config)# ip route 0.0.0.0 0.0.0.0 10.0.1.9

Verificar Conectividad

Prueba de capa de aplicación: telnet

Prueba de capa de red: ping, traceroute

Verificando en R1 la conexión a los routers spoken

R1# show frame-relay map

R1(config)#do sh frame-relay map

Serial0/0/0.102 (up): point-to-point dlci, dlci 102, broadcast, status defined, active

3







Ver los LMI

R1# show frame-relay lmi

…

Ver los PVC

R1# show frame-relay pvc

4

Configuración Frame relayEl primer paso dentro de la configuración de Frame-Relay es el de la activaciónde la interfaz que conecta a dicho router con una CSU/DSU, conectada a su vez con el switch del proveedor.Además de la dirección IP correspondiente se debe establecer el tipo de encapsulación:

•IETF para equipos No cisco.

•Cisco para equipos cisco, en el caso de elegir esta encapsulación no hará falta especificarla.

Router(config)#interface Serial 1Router(config-if)#ip address [direction IP+máscara]Router(config-if)#encapsulation frame-relay [cisco/ietf]Router(config-if)#bandwidth [valor del ancho de banda en Kbps]Si fuera necesario, según la versión de IOS, configurar LMI:

Router(config-if)#frame-relay lmi-type [cisco/anci/q933a]

ARP inverso está activado por defecto, si fuera necesario activarlo:

Router(config-if)#frame-relay inverse-arp [protocolo] [dlci]

Donde:

protocolo: IP, IPX, appletalk, decnet, etc

dlci: numero de dlci de la interfaz local, valor entre el 16 y 1007.

Configuración estática de Frame-RelayCuando un router no soporta ARP inverso, o cuando se quiere controlar el tráfico sobre los circuitos virtuales se debe definir estáticamente una tabla de dirección remota y su DLCI.

A partir de la configuración básica se agrega le mapeo estático:Router(config-if)#frame-relay map [protocolo][dirección destino][DLCI local][broadcast][ietf/cisco][payload-compress paket-by-paket]

5

Donde se define el tipo de protocolo, la dirección IP del destino y el DLCI local. Con dispositivos Cisco no es necesaria la configuración de la encapsulación, mientras que con dispositivos no Cisco se debe utilizar IETF. Los parámetros restantes son opcionales y habilitan el envío de difusiones y la compresión de sobrecarga.

configuración subinterfaces

Al establecer una conexión con un CSU/DSU se pueden abastecer varios PVC en una sola conexión física. Para este fin es necesario configurar subinterfaces que actúen como interfaces lógicas conectadas a los PVC.

Una subinterfaz no tiene forma predeterminada de conexión y puede configurase como:

Punto a punto: cada subinterfaz establece una conexión PVC directa punto a punto con su correspondiente router remoto. El tráfico de actualización de enrutamiento NO está sujeto a la regla del horizonte dividido.

Multipunto: una subinterfaz establece múltiples conexiones PVC a través de la nube Frame-Relay a varias interfaces físicas o subinterfaces de los routers remotos. El tráfico de actualización de enrutamiento está sujeto a la regla del horizonte dividido.Proceso de configuración de subinterfaces: Seleccione la interfaz en la que creará las subinterfaces y verifique la NO existencia de direccionamiento de capa tres. Configure la encapsulación Frame-Relay correspondiente en dicha interfaz. Seleccione la subinterfaz y si se utilizará como punto a punto o multipunto, rango de 0-4.294.967.295. Recuerde que no tienen valor predeterminado. Configure el valor de DLCI local en la subinterfaz, rango de 16-1007.

Comandos de configuración de subinterfaces:

Router(config)#interface Serial [número]Router(config-if)#no ip addressRouter(config-if)#encapsulation frame-relayRouter(config-if)#exitRouter(config)#interface serial [número.número de subinterfaz]

6

[multipoint/point-to-point]Router(config-subif)#frame-relay interface-dlci [DLCI local]

Verificación de la configuración

show interfcace serial nº pto: Muestra la información relativa a los DLCIs usados en la interface. show frame-relay traffic: Muestra las estadísticas globales de Frame Relay desde la última reinicialización del router. clear frame-relay inarp: Borra los mapeos Frame Relay creados dinámicamente. show frame-relay lmi: Muestra las estadísticas sobre la LMI (Local Management Interface) show frame-relay map: Muestra las entradas de mapeo actuales y la info sobre las conexiones. show frame-relay pvc: Muestra las estadísticas sobre los circuitos virtuales permanentes(PVCs) para las interfaces Frame Relay.

Solución de problemas

debug frame-relay: Muestra información sobre los paquetes recibidos en la interface Frame Relay. debug frame-relay lmi: Muestra información de los paquetes LMI intercambiados entre el router y el proveedor del servicio.

7

CONFIGURACION DE FRAME RELAY CON SUBINTERFACES PUNTO A PUNTO

Cuando configuramos una Frame Relay con subinterface se debe de asociar el DLCI o DLCI's en cada interface usando el siguiente comando.

Router (config) # interface serial [slot_#/] port_#. subinterface_# point-to-point|multipoint

Router (config-subif) # frame-relay interface-dlci local_DLCI_#

Si tiene un interface punto a punto asignará un solo circuito virtual y un DLCI solo DLCI a cada lado.

Si tiene un interface multipunto puede asignarles varios DLCI's.

Generalmente se asigna el mismo número de circuito virtual que al DLCI, aunque comos sabemos pueden ser diferentes.

Asegurese de que configura el direccionamiento al subinterface, no al interface físico.

CONFIGURACION DE FRAME RELAY CON SUBINTERFACES PUNTO A PUNTO

En este ejemplo asimismo que el LMI se detectara automáticamente.

8

Aquí no configuraremos las rutas estáticas en los routers B y C, ya que cada interface d cada Router tiene una subred diferente.

CONFIGURACION DEL ROUTER A

RouterA(config)# interface serial 0

RouterA(config-if)# encaspulation frame-relay ietf

RouterA(config-if)# no shutdown

RouterA(config-if)# exit

RouterA(config)# interface serial0.1 point-to-point

RouterA(config-subif)# ip address 192.168.1.1 255.255.255.0

RouterA(config-subif)# frame-relay interface-dlci 101

RouterA(config-subif)# exit

RouterA(config)# interface serial0.2 point-to-point

RouterA(config-subif)# frame-relay interface-dlci 201

RouterA(config-subif)# ip address 192.168.2.1 255.255.255.0

CONFIGURACION DEL ROUTER B

RouterB(config)# interface serial 0

RouterB(config-if)# encaspulation frame-relay ietf

RouterB(config-if)# ip address 192.168.1.2 255.255.255.0

RouterB(config-if)# no shutdown

RouterB(config-if)# exit

RouterB(config)# interface ethernet 0




9

CONFIGURACION DEL ROUTER C

RouterB(config)# interface serial 0

RouterB(config-if)# encaspulation frame-relay ietf




RouterB(config)# interface ethernet 0




Lo único que cambia entre la configuración del router a y router B son sus direcciones privadas de sus redes y las IP's que se unen al router A, que como se ve, es diferente a la IP del router B, ya que se trata de diferentes subredes.

10

Configuring Frame Relay in Point-to-Point topology on Cisco IOS.Posted on May 14, 2010

Configuring Frame Relay on Cisco Systems router is not so difficult and

takes several minutes. My virtual lab consists of Dynamips network

simulator running on Ubuntu. Here is the topology we will use:

In Frame Relay Point-to-Point topology every pair of routers have their

own subnet (usually /30). It is not a good solution if you are running out of

IP addresses in your network – in every subnet used for connecting routers,

2 of 4 available addresses are wasted for network address and broadcast

address.

However configuring Frame Relay with point-to-point sub-interfaces avoids

problem of split horizon rule that can appear when using distance vector

routing protocols such as RIP orEIGRP.

Synopsis:

What we are going to do is configure routers R1, R2 and R3 with point-to-

point sub-interfaces. We will use inverse ARP for IP to DLCI mapping. We

will also configure Frame Relay switch (FRSWITCH). So, let’s get this

network started!

11

http://reecon.wordpress.com/2010/05/14/configuring-frame-relay-in-point-to-point-topology-on-cisco-ios/

http://reecon.files.wordpress.com/2010/05/zrzut_ekranu.png

First, we will configure Frame Relay switch. After enabling switching on

router we will make some routes and specify interface type to be a DCE

(by default a router is considered to be a DTE device).

FR-SWITCH(config)#frame-relay switching

FR-SWITCH(config)#int s 1/0

FR-SWITCH(config-if)#encapsulation frame-relay

FR-SWITCH(config-if)#frame-relay intf-type dce

FR-SWITCH(config-if)#frame-relay route 102 interface serial 1/1 201

FR-SWITCH(config-if)#frame-relay route 103 interface serial 1/2 301

FR-SWITCH(config-if)#no shutdown

FR-SWITCH(config-if)#int serial 1/1



FR-SWITCH(config-if)#frame-relay route 201 interface s1/0 102


FR-SWITCH(config-if)#no sh

FR-SWITCH(config-if)#int s 1/2





FR-SWITCH(config-if)#no sh

To examine and verify route statements type show frame-relay route

FR-SWITCH#show frame-relay route

Input Intf Input Dlci Output Intf Output Dlci Status

Serial1/0 102 Serial1/1 201 active



12




Now we have to configure3 remaining routers. Configuration on each

router will be very similar – after enabling FR encapsulation we will specify

interface DLCI and IP address.

R2(config)#int s 1/0

R2(config-if)#encapsulation frame-relay

R2(config-if)#no ip add

R2(config-if)#clock rate 128000

R2(config-if)#no sh

R2(config)#int s 1/0.201 point-to-point

R2(config-subif)#ip add 10.1.1.2 255.255.255.252

R2(config-subif)#frame-relay interface-dlci 201

R2(config)#int s1/0.203 point-to-point



On router R1:


R1(config-if)#encap frame


R1(config-if)#no sh




R1(config)#int s1/0.103 point-to-point


13


And on R3:


R3(config-if)#enc frame

R3(config-if)#enc frame-relay


R3(config-if)#no sh







Now, we can examine FR map f.e on R1:

R1#sh frame-relay map

Serial1/0 (up): ip 0.0.0.0 dlci 103(0x67,0x1870) broadcast, CISCO, status

defined, active

Serial1/0 (up): ip 0.0.0.0 dlci 102(0x66,0x1860) broadcast, CISCO, status

defined, active

Serial1/0.102 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast

status defined, active

Serial1/0.103 (up): point-to-point dlci, dlci 103(0x67,0x1870), broadcast

status defined, active

Everything seems valid all circuits are in active state. Let’s perform a ping.

R1#ping 10.1.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:

!!!!!

14

Success rate is 100 percent (5/5), round-trip min/avg/max = 48/80/108 ms

Our network works. That’s all about Frame Relay in Point-to-Point topology.

Lab Frame-Relay sobre GNS3

Primero armar una topologia como muestra el grafico:

Configuracion del dispositivo Frame-Relay:

Configurarlo igual que en la siguiente imagen:

15

Configuracion de los 3 Routers:

Router1

Código:

Router(config)# interface Serial0/0Router(config-if)# no ip addressRouter(config-if)# encapsulation frame-relay

Router(config)# interface Serial0/0.1 point-to-pointRouter(config-if)# ip address 192.168.100.1 255.255.255.252Router(config-if)# frame-relay interface-dlci 101


16

Router2

Código:

Router(config)# interface Serial0/0Router(config-if)# no ip addressRouter(config-if)# encapsulation frame-relay


Router3

Código:

Router(config)# interface Serial0/0Router(config-if)# no ip addressRouter(config-if)# encapsulation frame-relay Router(config)# interface Serial0/0.1 point-to-pointRouter(config-if)# ip address 192.168.100.6 255.255.255.252Router(config-if)# frame-relay interface-dlci 203

Esta es una guia basica de Frame-Relay pero es bastante clara. La arme usando una

que encontre que me gusto.

Espero que les sirva.

http://eduangi.org/node189.html

Ejemplo de Configuración de OSPF en Modo Point-to-Point en Subinterfaces Frame Relay

Router(config)#interface Serial0

Router(config-if)#no ip address

17

http://eduangi.org/node189.html

Router(config-if)#encapsulation frame-relay

Router(config)#interface Serial0.1 point-to-point

Router(config-subif)#ip address 10.1.1.1 255.255.255.0

Router(config-subif)#frame-relay interface-dlci 51

Router(config)#interface Serial0.2 point-to-point

Router(config-subif)#ip address 10.1.2.1 255.255.255.0

Router(config-subif)#frame-relay interface-dlci 52

Hasta aquí sería la configuración de los subinterfacesRouter(config)#router ospf 1

Router(config-router)#network 10.1.0.0 0.0.255.255

Frame Relay point-to-multipint + OSPFTodos son Router c7200IOS (tm) 7200 Software (C7200-IK9S-M), Version 12.2(40a), RELEASE SOFTWARE (fc1)GNS3

TOPOLOGIA

18

Asi debemos configurar el switch FRAME-RELAY

Configuracion R1

hostname R1!interface Loopback0ip address 192.168.1.3 255.255.255.0!interface Serial1/0ip address 192.168.192.1 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0!

19

http://4.bp.blogspot.com/-eaWqZqsMrSY/Tp3rZsdyq1I/AAAAAAAACHw/vvhKOYzbftk/s1600/Pantallazo-2.png

http://4.bp.blogspot.com/-WHaj1EBReoI/Tp3tVkS2xtI/AAAAAAAACH8/weVaOPS8Rww/s1600/Pantallazo.png

router ospf 1log-adjacency-changesnetwork 192.168.1.0 0.0.0.255 area 0network 192.168.192.0 0.0.0.255 area 0

Configuracion R2

hostname R2!interface Loopback0ip address 192.168.200.1 255.255.255.0!interface Serial1/0ip address 192.168.192.2 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0!router ospf 1log-adjacency-changesnetwork 192.168.200.0 0.0.0.255 area 0network 192.168.192.0 0.0.0.255 area 0

Configuracion R3

hostname R3!interface Loopback0ip address 192.168.232.1 255.255.255.0!interface Serial1/0ip address 192.168.192.4 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0!router ospf 1log-adjacency-changesnetwork 192.168.232.0 0.0.0.255 area 0network 192.168.192.0 0.0.0.255 area 0__________________________________________________________________________Otra manera de hacerlo es configurando un Router como switch frame-relay

20

De esta manera fue configurado dejo un vistaso al running-config

hostname Switch-RF!frame-relay switching!interface Serial1/0no ip addressencapsulation frame-relayserial restart-delay 0clock rate 64000frame-relay intf-type dceframe-relay route 102 interface Serial1/1 201frame-relay route 103 interface Serial1/2 301!interface Serial1/1no ip addressencapsulation frame-relayserial restart-delay 0clock rate 64000frame-relay intf-type dceframe-relay route 201 interface Serial1/0 102!interface Serial1/2no ip addressencapsulation frame-relayserial restart-delay 0clock rate 64000frame-relay intf-type dceframe-relay route 301 interface Serial1/0 10

21

http://3.bp.blogspot.com/-9pnEKNyKN7c/Tp3_SNj3w-I/AAAAAAAACII/5UHqmzqUTYo/s1600/Pantallazo-3.png

***El resto de los Router's (R1,R2 y R3) quedan igual a la configuracion anterior, o si queremos agregamos los mapas de frame-relay manualmente de la siguiente manera en cada una de las interfaces de los Router's:

R1interface Serial1/0ip address 192.168.192.1 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0frame-relay map ip 192.168.192.2 102 broadcastframe-relay map ip 192.168.192.4 103 broadcast

R2interface Serial1/0ip address 192.168.192.2 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0frame-relay map ip 192.168.192.1 201 broadcast

R3interface Serial1/0ip address 192.168.192.4 255.255.255.0encapsulation frame-relayip ospf network point-to-multipointserial restart-delay 0frame-relay map ip 192.168.192.1 301 broadcast

Frame-relay malla completa

22

CONFIGURACION

1ro configuraremos el Switch FRL

Router(config)#hosname FRL FRL(config)#frame-relay switching

Ahora configurar las interfaces con las DLCI's

interface Serial0/0 no ip address encapsulation frame-relay serial restart-delay 0 clock rate 64000 frame-relay intf-type dce frame-relay route 102 interface Serial1/1 201 frame-relay route 103 interface Serial1/2 301 frame-relay route 104 interface Serial1/3 401 ! interface Serial0/1 no ip address encapsulation frame-relay serial restart-delay 0 clock rate 64000 frame-relay intf-type dce frame-relay route 201 interface Serial1/0 102 frame-relay route 203 interface Serial1/2 302 frame-relay route 204 interface Serial1/3 402 ! interface Serial0/2 no ip address encapsulation frame-relay serial restart-delay 0 clock rate 64000 frame-relay intf-type dce

23

http://1.bp.blogspot.com/-ih02AlrL53U/Tpnakg8_4lI/AAAAAAAACHk/9Pdq0fZ-VCU/s1600/FRL-maya%2Bcomplet.png

frame-relay route 301 interface Serial1/0 103 frame-relay route 302 interface Serial1/1 203 frame-relay route 304 interface Serial1/3 403 ! interface Serial0/3 no ip address encapsulation frame-relay serial restart-delay 0 clock rate 64000 frame-relay intf-type dce frame-relay route 401 interface Serial1/0 104 frame-relay route 402 interface Serial1/1 204 frame-relay route 403 interface Serial1/2 304

Congif R1

interface Serial1/0 ip address 192.168.0.1 255.255.255.0 encapsulation frame-relay serial restart-delay 0 frame-relay lmi-type cisco

Config R2


Config R3


Config R4

interface Serial1/0 ip address 192.168.0.4 255.255.255.0

24

encapsulation frame-relay serial restart-delay 0 frame-relay lmi-type cisco

Point to Multipoint Frame Relay Topology

As you have already seen we will configure R1 interface as multipoint but R2 and R3 as

point-to-point. Note that by default Split Horizon Rule is in effect on interfaces and EIGRP

traffic between R2 Lan and R3 Lan would not be advertisted if we will not disable this rule

on R1 S0/0.1 subinterface. To get this working you have to do next configurations:

First we need to configure interfaces, subinterfaces, Frame Relay Encapsulation and Frame

Relay mapping for our Routers

25

R1

interface Loopback0

ip address 192.168.1.1 255.255.255.0

interface Serial0/0

no ip address

encapsulation frame-relay

interface Serial0/0.1 multipoint

ip address 192.168.0.1 255.255.255.248

no ip split-horizon eigrp 1

frame-relay map ip 192.168.0.2 102 broadcast


R2

interface Loopback0

ip address 192.168.2.1 255.255.255.0

interface Serial0/0

no ip address


26

interface Serial0/0.1 point-to-point

ip address 192.168.0.2 255.255.255.248

frame-relay interface-dlci 201

R3

interface Loopback0

ip address 192.168.3.1 255.255.255.0

interface Serial0/0

no ip address



ip address 192.168.0.3 255.255.255.248


Now we can configure EIGRP to route traffic between Routing Devices

R1

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.1.0

no auto-summary

R2

27

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.2.0

no auto-summary

R3

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.3.0

no auto-summary

Let’s check Routing tables on R2, R3 and to verify ping between R2 and R3

show ip route output

R2 to R3 LAN ping output

28

http://www.getnetworking.net/wp-content/uploads/2011/08/show_ip_route.png

This OSPF network type behaves like a hybrid between multipoint non-broadcast and point-

to-multipoint because DR/BDR election does not happen (multipoint non-broadcast) and

Neighbor discovery the same (point to multipoint) which results from ‘nonbroadcast’

keyword in router configuration command. So, if neighbor discovery doesn’t take place we

must add them manually under router configuration section.

With these in mind I will start to set up our lab, will use the same topology like in previous

articles. In next picture you have the topology.

OSPF Point to Multipoint Non Broadcast over Frame Relay

R1 has Permanent Virtual Circuits (PVC) with all other routers while others have only with

R1. In table below you see PVC on R1.

29

http://www.getnetworking.net/tutorials/ospf-point-to-multipoint-over-frame-relay

http://www.getnetworking.net/tutorials/ospf-point-to-multipoint-over-frame-relay

http://www.getnetworking.net/tutorials/ospf-non-broadcast-over-frame-relay

R1 to DLCI

R2 1002

R3 1003

R4 1004

R2, R3 and R4 all have only one PVC to conect to R1. DLCI of this PVC is 1001. R2, R3

and R4 are in the same subnet and to reach each other we’ll add some mappings which will

go to R1 as a transit point. Next you see configurations for routers with interfaces, OSPF,

PVCs and mappings configured. Highlighted with red are OSPF network type

configurations.

R1

R1(config)#interface loopback 0

R1(config-if)#ip address 192.168.1.1 255.255.255.0

R1(config)#interface Serial0/0


R1(config)#interface s0/0.1 multipoint

R1(config-subif)#ip address 10.0.0.1 255.255.255.248

R1(config-subif)#ip ospf network point-to-multipoint non-broadcast


R1(config-fr-dlci)#frame-relay interface-dlci 1003


30

R1(config)#router ospf 1

R1(config-router)#router-id 1.1.1.1

R1(config-router)#network 10.0.0.0 0.0.0.7 area 0


R1(config-router)#neighbor 10.0.0.4



R2

2

R2(config)#interface Loopback0




R2(config-if)#no shutdown

R2(config)#interface Serial0/0.1 multipoint



R2(config-subif)#frame-relay map ip 10.0.0.3 1001


31







R3












32






R4












33






Further I will show results of ‘show ip route’ command on R4 and a ping to R3 loopback

interface.

IP routes on R4

Ping Results from R4 to R3 loopback interface

34

In this lab we’ll use the same topology as in the previous one, where we talked about how to

configure OSPF on nonbroadcast network type. In Point to Multipoint OSPF behaves

opposite to the Non Broadcast network type, namely here OSPF does not elect a DR/BDR

but neighbor discovery proccess takes place. So, in this case we shouldn’t add neighbors

manually. In topology below you see that interfaces of all routers which communicate

through Frame Relay are in the same subnet and each of them has a LAN connected

simulated by Loopback interface.

OSPF point to multipoint over FrameRelay

35

http://www.getnetworking.net/tutorials/ospf-non-broadcast-over-frame-relay

DLCI mappings are the same like in previous article. In table below you see them on R1. R1 has PVC with all

routers, but the others have only with R1 and this DLCI is 1001 on all other Routers (R2, R3, R4).

R1 to DLCI

R2 1002

R3 1003

R4 1004

In next listings you see configuration for routers.

R1







R1(config-subif)#ip ospf network point-to-multipoint





36




R2















37


R3
















R4

38
















I highlighted with red command where we configure OSPF network type ”ip ospf network

point-to-multipoint”. You will see in next screenshots that for this kind of OSPF network

there is not such a concept like Designated Router or Backup Designated Router.

39

Neighbors on R1 and R4

As you can see in place where should be mentioned DR/BDR or DROTHER there is a dash.

Now let’s check if we have routes from R4 to other Routers and we’ll try a ping test.

IP routes on R4

40

Ping Results from R4 to R3

Everything is fine and ping works well from R4 to R3. This is what we needed to get into this

network. Good luck to you!

Frame Relay Point to Point with EIGRP

41

As you already have seen we have here a HUB and Spoke topology, R1 is used as HUB

Router and R2 with R3 are used as Spoke Routers. To get this working you have to do next

configurations:

First we need to configure interfaces, subinterfaces and Frame Relay Encapsulation for our

Routers

R1

interface Serial0/0

no ip address



ip address 192.168.0.1 255.255.255.0



ip address 192.168.1.1 255.255.255.0


R2

interface Serial0/0

no ip address


42


ip address 192.168.0.2 255.255.255.0


R3

interface Serial0/0

no ip address



ip address 192.168.1.2 255.255.255.0


Now we can configure EIGRP to route traffic between Spoke Routers

R1

router eigrp 1

network 192.168.0.0

network 192.168.1.0

no auto-summary

R2

router eigrp 1

network 192.168.0.0

43

no auto-summary

R3

router eigrp 1

network 192.168.1.0

no auto-summary

44

45

OSPF non-broadcast network type over Frame Relay

In this topology only R1 has PVCs with each Router. In next table is shown DLCI mappings for them.

R1 to DLCI

R2 1002

R3 1003

R4 1004

On R2, R3 and R4 DLCI to R1 is the same: 1001. How I said before, between R2-R3, R3-

R4, R2-R4 there is not PVC connection and will not add each other in neighbor list except

R1. In turn on R1 will add in neighbor list all Routers. Also we need to add DLCI mappings

on FR Switch Like in picture below.

Frame Relay mapping

Now we’ll configure Routers with DLCI assigned on interfaces and OSPF neighbors manually added. R1



46















R2




47





R2(config-subif)#ip ospf priority 0







R3






48










R4









49







With red we have highlighted OSPF priority configuration, we have done that because we

want R1 to be Designated Router. In this topology where all Routers are in the same

subnet we need a designated router for this subnet, PVC with all routers has only R1 that’s

why we have configured OSPF priority 0 to other routers, with priority 0 Router will not be a

DR or BDR (Backup Designated Router). Now it’s time to see the results we got. In next

screenshots are shown Neighbors relationships formed, routes learned by R2 and Ping

results from R2 to R4.

Neighbors on R1 and R2

50

IP routes on R2

Ping Results from R2 to R4

From the pictures everything is fine except Ping from R2 to R4 loopback interface. If you look in Routing Table you see that next hop to go to 192.168.4.1 is Router R4 (10.0.0.4), but there is no any PVC between these two routers and that’s why ping to R4 failed. If we add Frame Relay mappings on R2, R3 and R4 to each other, ping will work fine. In next configs we added mappings. R2




R3

51




R4




And now the results:

Ping Results after adding Frame Relay mappings

Results are as expected by using Frame Relay mapping with the same DLCI that goes to

R1.

52

Point to Multipoint Frame Relay Topology

As you have already seen we will configure R1 interface as multipoint but R2 and R3 as

point-to-point. Note that by default Split Horizon Rule is in effect on interfaces and EIGRP

traffic between R2 Lan and R3 Lan would not be advertisted if we will not disable this rule

on R1 S0/0.1 subinterface. To get this working you have to do next configurations:

First we need to configure interfaces, subinterfaces, Frame Relay Encapsulation and Frame

Relay mapping for our Routers

53

R1

interface Loopback0

ip address 192.168.1.1 255.255.255.0

interface Serial0/0

no ip address


interface Serial0/0.1 multipoint

ip address 192.168.0.1 255.255.255.248

no ip split-horizon eigrp 1



R2

interface Loopback0

ip address 192.168.2.1 255.255.255.0

interface Serial0/0

no ip address


54


ip address 192.168.0.2 255.255.255.248


R3

interface Loopback0

ip address 192.168.3.1 255.255.255.0

interface Serial0/0

no ip address



ip address 192.168.0.3 255.255.255.248


Now we can configure EIGRP to route traffic between Routing Devices

R1

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.1.0

no auto-summary

R2

55

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.2.0

no auto-summary

R3

router eigrp 1

network 192.168.0.0 0.0.0.7

network 192.168.3.0

no auto-summary

Let’s check Routing tables on R2, R3 and to verify ping between R2 and R3

show ip route output

R2 to R3 LAN ping output

56

http://www.getnetworking.net/wp-content/uploads/2011/08/show_ip_route.png

Documents

Frram Rela